Messages 5.3
Uploaded by
Marcelo Castillo LeytonMessages 5.3
Uploaded by
Marcelo Castillo LeytonTivoli Storage Manager
Version 5.3
Messages
SC32-9090-02
Tivoli Storage Manager
Version 5.3
Messages
SC32-9090-02
Note! Before using this information and the product it supports, be sure to read the general information under Appendix E, Notices, on page 1033.
Sixth Edition (December 2004) This edition applies to Version 5 Release 3 of the IBM Tivoli Storage Manager and IBM Tivoli Storage Manager Extended Edition for AIX, HP-UX, Linux, Sun Solaris, Windows, and z/OS (5608-ISM, 5608ISX, 5698-A13, 5698-A11); IBM Tivoli Storage Manager for Space Management (5608HSM); IBM Tivoli Storage Manager for Storage Area Networks (5608-SAN ); IBM Tivoli Storage Manager for Mail (5698-APE); IBM Tivoli Storage Manager for Databases (5608-APD); IBM Tivoli Storage Manager for Application Servers (5608-APW); IBM Tivoli Storage Manager for Hardware (5608-APH); IBM Tivoli Storage Manager for Enterprise Resource Planning (5608-APR); IBM Tivoli Storage Manager for Data Retention (5608TDR); IBM Tivoli Storage Manager for Data Retention for z/OS (5698A25); IBM Tivoli Storage Manager for Mail System for z/OS (5698A12); and to any subsequent releases until otherwise indicated in new editions or technical newsletters. Order publications through your sales representative or the branch office serving your locality. Your feedback is important in helping to provide the most accurate and high-quality information. If you have comments about this book or any other Tivoli Storage Manager documentation, please see Support Information on page viii. Copyright International Business Machines Corporation 1993, 2004. 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 Referenced z/OS System Publications . . . . vii Related IBM Publications . . . . . . . . . vii Accessing Publications Online . . . . . . . viii Ordering Publications . . . . . . . . . viii Tivoli Technical Training . . . . . . . . . . viii Support Information . . . . . . . . . . . viii Searching knowledge bases . . . . . . . . ix Obtaining fixes . . . . . . . . . . . . ix Contacting IBM Software Support . . . . . . x Conventions Used in This Guide . . . . . . . xi Typeface Conventions . . . . . . . . . . xi Operating System-dependent Variables and Paths xii
Part 2. Server Messages . . . . . . 11
Chapter 3. Common and Platform Specific Messages (ANR0100ANR9999) . . . . . . . . . 13 Chapter 4. Client Events Logged to Server (ANE40004999). . . . . . . 605
Part 3. Client and Data Protection for Lotus Notes Messages . . . . 611
Chapter 5. Client and Data Protection for Lotus Notes Messages (ANS0100ANS9999) . . . . . . . . 613
New, Changed, and Deleted Messages xiii
New, Changed, and Deleted Server Messages . . . xiii New Server Messages . . . . . . . . . xiii Changed Server Messages . . . . . . . . xv Deleted Server Messages . . . . . . . . . xvi New, Changed, and Deleted Client Messages . . . xix New Client Messages . . . . . . . . . . xix Changed Client Messages . . . . . . . . xxii Deleted Client Messages . . . . . . . . xxiv
Part 4. Data Protection Products Messages . . . . . . . . . . . . 753
Chapter 6. Data Protection for Lotus Domino (ACD0000ACD9999) . . . . 755 Chapter 7. Data Protection for Microsoft Exchange Server (ACN0000ACN9999) . . . . . . . . 775 Chapter 8. Data Protection for Microsoft SQL Server (ACO0000ACO9999) . . . . . . . . 791 Chapter 9. Data Protection for Oracle (ANU0000ANU9999) . . . . . . . . 807 Chapter 10. Data Protection for mySAP.com Technology for DB2 UDB (BKI0000BKI9999) . . . . . . . . . 819 Chapter 11. Data Protection for mySAP.com Technology for Oracle (BKI0000BKI9999) . . . . . . . . . 839 Chapter 12. Data Protection for EMC Symmetrix for mySAP.com Technology (IDS0000IDS0999) . . . . 859
Summary of Changes to IBM Tivoli Storage Manager Version 5 . . . . . xxv
Technical Changes for Version 5 Release 3 December 2004 . . . . . . . . . . . . . xxv Technical Changes for Version 5 Release 2 January 2004 . . . . . . . . . . . . . xxix
Part 1. Introduction . . . . . . . . . 1
Chapter 1. Introduction . . . . . . . . 3
Messages Not Appearing in This Publication Understanding Messages . . . . . . . Message Format . . . . . . . . . . . . . . . . 3 . 4 . 4
Chapter 2. Obtaining Help for IBM Tivoli Storage Manager . . . . . . . . . . . 7
Internet and IBMLink Assistance . . . Internet . . . . . . . . . . . IBMLink/ServiceLink . . . . . . Describing the Error with Keywords . . Component Identification Keyword . . Type-of-Failure Keyword . . . . . Command Keyword . . . . . . . Function Keyword . . . . . . . Obtaining Online HELP (Get Help on Error Messages) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7 7 7 8 8 9 9
. 9
Copyright IBM Corp. 1993, 2004
iii
Chapter 13. Data Protection for Enterprise Storage Server for mySAP.com Technogy for DB2 UDB (EEP0020EEP7900) and (IDS1000IDS2999) . . . . . . . . . 865 Chapter 14. Data Protection for Enterprise Storage Server for mySAP.com Technolgy for Oracle (EEO0020EEO7900) and (IDS1000IDS1999) . . . . . . . . . 903 Chapter 15. Data Protection for Enterprise Storage Server for DB2 UDB (EEP0000EEP9999) . . . . . . 933 Chapter 16. Data Protection for Enterprise Storage Server for Oracle (EEO0000EEO9999) . . . . . . . . 957
Appendix B. Allocating Additional Server Memory . . . . . . . . . . 1019 Appendix C. I/O Error Code Descriptions for Server Messages . . 1021
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 . . . . . . 1022 . 1022 1023 . 1024 . 1025 . 1026 . 1029
Appendix D. Device Errors in AIX Version 4 System Error Log . . . . 1031 Appendix E. Notices . . . . . . . . 1033
Programming Interface . Trademarks . . . . . . . . . . . . . . . . . . . . . 1034 . 1035
Part 5. Appendixes . . . . . . . . 979
Glossary . . . . . . . . . . . . . 1037 Appendix A. API Return Codes with Explanations. . . . . . . . . . . . 981
iv
IBM Tivoli Storage Manager: Messages
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 IBM Tivoli Storage Management Products License Information IBM Tivoli Storage Manager Messages 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 OS/400 PASE Administrators Guide IBM Tivoli Storage Manager for OS/400 PASE Administrators Reference IBM Tivoli Storage Manager for OS/400 PASE 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 Order Number GH09-4572 GC32-0767 GC32-0768 GC32-0769 GC32-1597 GC32-0772 GC32-0773 GC32-1598 GC23-4690 GC23-4691 GC32-1599 GC32-0775 GC32-0776 GC32-1603 GC23-4694 GC23-4695 GC23-4696 GC32-0778 GC32-0779 GC32-1601 GC32-0782 GC32-0783 GC32-1602
Copyright IBM Corp. 1993, 2004
The following table lists Tivoli Storage Manager storage agent publications.
Publication Title IBM Tivoli Storage Manager for SAN for AIX Storage Agent Users Guide IBM Tivoli Storage Manager for SAN for HP-UX Storage Agent Users Guide IBM Tivoli Storage Manager for SAN for Linux Storage Agent Users Guide IBM Tivoli Storage Manager for SAN for Sun Solaris Storage Agent Users Guide IBM Tivoli Storage Manager for SAN for Windows Storage Agent Users Guide Order Number GC32-0771 GC32-0727 GC23-4693 GC32-0781 GC32-0785
The following table lists Tivoli Storage Manager client publications.
Publication Title Order Number
IBM Tivoli Storage Manager for Space Management for UNIX and Linux: GC32-0794 Users Guide IBM Tivoli Storage Manager for Macintosh: Backup-Archive Clients Installation and Users Guide IBM Tivoli Storage Manager for NetWare: Backup-Archive Clients Installation and Users Guide IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive Clients Installation and Users Guide IBM Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and Users Guide IBM Tivoli Storage Manager Using the Application Program Interface GC32-0787 GC32-0786 GC32-0789 GC32-0788 GC32-0793
The following table lists publications for application protection products.
Publication Title IBM Tivoli Storage Manager for Application Servers: Data Protection for WebSphere Application Server Installation and Users Guide IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server Installation and Users Guide IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX and Linux Installation and Users Guide IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for Windows Installation and Users Guide IBM Tivoli Storage Manager for Databases: Data Protection for Informix Installation and Users Guide IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection for mySAP.com Installation and Users Guide for DB2 IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection for mySAP.com Installation and Users Guide for Oracle IBM Tivoli Storage Manager for Hardware: Data Protection for EMC Symmetrix for R/3 Installation and Users Guide Order Number SC32-9075 SC32-9059 SC32-9064 SC32-9065 SH26-4095 SC33-6341 SC33-6340 SC33-6386
vi
IBM Tivoli Storage Manager: Messages
Publication Title
Order Number
IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise Storage SC32-9060 Server for DB2 UDB Installation and Users Guide IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise Storage SC32-9061 Server Databases (Oracle) Installation and Users Guide IBM Tivoli Storage Manager for Hardware: Data Protection for IBM Enterprise Storage Server for mySAP.com Technology Installation and Users Guide for DB2 UDB IBM Tivoli Storage Manager for Hardware: Data Protection for IBM Enterprise Storage Server for mySAP.com Technology Installation and Users Guide for Oracle IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino for UNIX, Linux, and OS/400 Installation and Users Guide IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino for Windows Installation and Users Guide IBM Tivoli Storage Manager for Mail: z/OS Edition Licensed Program Specifications IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Installation and Users Guide SC33-8204
SC33-8205
SC32-9056 SC32-9057 GC32-0838 SC32-9058
Referenced z/OS System Publications
The following table lists referenced z/OS publications.
Publication Title DFSMS/MVS DFSMSrmm Guide and Reference DFSMS/MVS DFSMSrmm Implementation and Customization Guide OS/390 Security Server (RACF) Security Administrators Guide z/OS SecureWay Security Server RACF Security Administrators Guide Order Number SC26-4931 SC26-4932 SC28-1915 SA22-7683
Related IBM Publications
The following table lists related IBM hardware products publications.
Title IBM Magstar 3494 Tape Library Introduction and Planning Guide IBM 3490E Model E01 and E11 Users Guide IBM 3495 Tape Library Dataserver Models L20, L30, L40, and L50 Operators Guide IBM Magstar MP 3570 Tape Subsystem Operators Guide IBM TotalStorage Tape Device Drivers Installation and Users Guide IBM TotalStorage Enterprise Tape System 3590 Operator Guide IBM Magstar 3494 Tape Library Dataserver Operator Guide IBM TotalStorage Enterprise Tape System 3592 Operator Guide Order Number GA32-0279 GA32-0298 GA32-0235 GA32-0345 GC35-0154 GA32-0330 GA32-0280 GA32-0465
About this Guide
vii
Accessing Publications Online
The product CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. To access the publications using a Web browser, open the infocenter.html file. The file is in the appropriate publications directory on the product CD. IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: http://www.ibm.com/software/tivoli/library/ Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click the <Tivoli Storage Manager> link to access the product library at the Tivoli software information center. Note: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your local paper.
Ordering Publications
You can order many Tivoli publications online at the following Web site: www.elink.ibmlink.ibm.com/public/ applications/publications/cgibin/pbi.cgi You can also order by telephone by calling one of these numbers: v In the United States: 800-879-2755 v In Canada: 800-426-4968 In other countries, see the following Web site for a list of telephone numbers: http://www.ibm.com/software/tivoli/order-lit/
Tivoli Technical Training
For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: http://www.ibm.com/software/tivoli/education
Support Information
This section describes the following options for obtaining support for IBM products: v Searching knowledge bases on page ix v Obtaining fixes on page ix v Contacting IBM Software Support on page x
viii
IBM Tivoli Storage Manager: Messages
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.
Search the information center on your local system or network
IBM Tivoli Storage Manager provides an information center on a CD. You can run the information center from the CD, or copy it to your local computer or an intranet server. You can use the search function of this information center to query conceptual information, instructions for completing tasks, reference information, and support documents.
Search 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. To search multiple Internet resources for your product, go to the support web site for the product www.ibm.com/software/sysmgmt/products/ support/IBMTivoliStorageManager.html and look for the section to search the support knowledge base. From this section, you can search a variety of resources including: v IBM technotes v IBM downloads v IBM Redbooks v Forums and newsgroups
Obtaining fixes
A product fix might be available to resolve your problem. You can determine what fixes are available for your IBM software product by checking the product support Web site: 1. Go to the IBM Software Support Web site (http://www.ibm.com/software/support). 2. Under Products A - Z, select your product name. This opens a product-specific support site. 3. Under Self help, follow the link to All Updates, where you will find a list of fixes, fix packs, and other service updates for your product. For tips on refining your search, click Search tips. 4. Click the name of a fix to read the description and optionally download the fix. To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps: 1. From the support page for any IBM product, click My support in the upper-right corner of the page. 2. If you have already registered, skip to the next step. If you have not registered, click register in the upper-right corner of the support page to establish your user ID and password. 3. Sign in to My support. 4. On the My support page, click Edit profiles in the left navigation pane, and scroll to Select Mail Preferences. Select a product family and check the appropriate boxes for the type of information you want. 5. Click Submit. 6. For e-mail notification for other products, repeat Steps 4 and 5.
About this Guide
ix
For more information about types of fixes, see the Software Support Handbook (http://techsupport.services.ibm.com/guides/handbook.html).
Contacting IBM Software Support
IBM Software Support provides assistance with product defects. Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have: v For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows or UNIX operating systems), enroll in Passport Advantage in one of the following ways: Online: Go to the Passport Advantage Web page (www.lotus.com/services/passport.nsf/WebDocs/ Passport_Advantage_Home) and click How to Enroll By phone: For the phone number to call in your country, go to the IBM Software Support Web site (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region. v For IBM eServer software products (including, but not limited to, DB2 and WebSphere products that run in zSeries, pSeries, and iSeries environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eServer software products, go to the IBM Technical Support Advantage Web page (http://www.ibm.com/servers/eserver/techsupport.html). If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to the contacts page of the IBM Software Support Handbook on the Web (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region for phone numbers of people who provide support for your location. Follow the steps in this topic to contact IBM Software Support: 1. Determine the business impact of your problem. 2. Describe your problem and gather background information. 3. Submit your problem to IBM Software Support.
Determine the business impact of your problem
When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem you are reporting. Use the following criteria:
Severity 1 Critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. Significant business impact: The program is usable but is severely limited. Some business impact: The program is usable with less significant features (not critical to operations) unavailable.
Severity 2 Severity 3
IBM Tivoli Storage Manager: Messages
Severity 4
Minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented.
Describe your problem and gather background information
When explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions: v What software versions were you running when the problem occurred? v Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. v Can the problem be re-created? If so, what steps led to the failure? v Have any changes been made to the system? (For example, hardware, operating system, networking software, and so on.) v Are you currently using a workaround for this problem? If so, please be prepared to explain it when you report the problem.
Submit your problem to IBM Software Support
You can submit your problem in one of two ways: v Online: Go to the Submit and track problems page on the IBM Software Support site (http://www.ibm.com/software/support/probsub.html). Enter your information into the appropriate problem submission tool. v By phone: For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook on the Web (techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region. If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround for you to implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions. For more information about problem resolution, see Searching knowledge bases and Obtaining fixes.
Conventions Used in This Guide Typeface Conventions
This guide uses the following typeface conventions: Bold v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text
About this Guide
xi
Italic v v v v Words defined in text Emphasis of words (words as words) New terms in text (except in a definition list) Variables and values you must provide
Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options
Operating System-dependent Variables and Paths
v Command to be entered on the AIX Linux HP-UX Sun SolarisWindows OS/400 system command line:
===> wrkcfgsts *dev *tap > dsmadmc
v IBM Tivoli Storage Manager command to be entered on the PASE command line:
> dsmserv
Note: The PASE command line is accessed with the OS/400 CALL QP2TERM command. v Command to be entered on the command line of an administrative client:
query devclass
v Command to be entered on the command line of a desktop machine that has an administrative client installed:
> dsmadmc -mountmode
xii
IBM Tivoli Storage Manager: Messages
New, Changed, and Deleted Messages
This section contains lists of the new, changed, and deleted messages for the server and for the client.
New, Changed, and Deleted Server Messages
This section contains lists of the new, changed, and deleted server messages.
New Server Messages
These are the new server messages. ANR0115W ANR0116W ANR0147E ANR0148I ANR0273W ANR0274E ANR0474W ANR0565W ANR1345I ANR1774E ANR2656E ANR2657E ANR2658E ANR2659E ANR2660E ANR2661E ANR2798E ANR2799W ANR3530E ANR3531E ANR3532E ANR3533E ANR3534E ANR3535E ANR3536E ANR3537E ANR3538E ANR4485I ANR4486I ANR4487I ANR4488I ANR4489I
Copyright IBM Corp. 1993, 2004
ANR4490I ANR4491I ANR4492I ANR4493I ANR4494I ANR4495E ANR4496E ANR4497E ANR4724E ANR4871I ANR4872E ANR4873E ANR4874I ANR4875I ANR4876W ANR4877E ANR4878I ANR4879I ANR4880I ANR4881E ANR4882E ANR4883I ANR4884W ANR4885E ANR4886E ANR4887E ANR4888E ANR4889E ANR7813W ANR8557W ANR8558E ANR8685I ANR8686I
xiii
ANR8687E ANR8971E ANR0134W ANR0379W ANR0952W ANR0953W ANR0954W ANR1014W ANR1081E ANR1082E ANR1083E ANR1084E ANR1085E ANR1086E ANR1087E ANR1088E ANR1089E ANR1090E ANR1091E ANR1092E ANR1093E ANR1121E ANR1122E ANR1123E ANR1124E ANR1125E ANR1126E ANR1127E ANR1128E ANR1129E ANR1130E ANR1131E ANR1132E ANR1133E ANR1134E ANR1135E ANR1176I ANR1295W ANR1296W ANR1297E ANR1426I ANR1427E ANR1786W ANR1787W ANR1788W
ANR1789W ANR1790W ANR1791W ANR1792W ANR2665W ANR2666W ANR2759I ANR2760E ANR2761I ANR2762I ANR2763E ANR2764E ANR2765E ANR2766W ANR2776I ANR2777I ANR2778I ANR2779I ANR2797E ANR4498E ANR4526E ANR4539E ANR4540E ANR4541E ANR4542E ANR4543E ANR4544E ANR4545E ANR4940E ANR4943E ANR4944E ANR4964I ANR4965E ANR4966E ANR4967W ANR4968W ANR4969W ANR4970E ANR4971E ANR4972E ANR7814I (HP) ANR8223W (HP) ANR8284E (HP) ANR8284E (LINUX) ANR8384E
xiv
IBM Tivoli Storage Manager: Messages
ANR8385E ANR8386W ANR8387I ANR8388E ANR8973E ANR9676E (HP)
ANR9676E (LINUX) ANR9677E (LINUX) ANR9678E (HP) ANR9678E (LINUX) ANR9903W (HP) ANR9904W (HP)
Changed Server Messages
These are the changed server messages. ANR0117E ANR0118W ANR0119W ANR0120I ANR0121E ANR0122E ANR0123E ANR0124W ANR0125W ANR0126W ANR0128W ANR0140I ANR0141E ANR0142I ANR0143E ANR0144E ANR0145E ANR0146E ANR0381I ANR0387I ANR0388I ANR0389W ANR0397I ANR0398W ANR0399I ANR0496E ANR0502E ANR0558W ANR0559E ANR1161W ANR1298W ANR1299E ANR1344I ANR1552W ANR1613E ANR1614E ANR1615E ANR1616W ANR1617W ANR1618W ANR1619E ANR1620E ANR1621E ANR1622E ANR1623E ANR1784I ANR2541E ANR2542E ANR2543E ANR2547E ANR4479I ANR4480I ANR4481I ANR4482I ANR4483I ANR4484I ANR4739E ANR4741W ANR4742W ANR4743W ANR4744W ANR4799E ANR8555E ANR8556E ANR8939E ANR0115W ANR0116W ANR0390W ANR0867E ANR0887E ANR1080W ANR1120W ANR1163W
New, Changed, and Deleted Messages
xv
ANR1257W ANR2152E ANR2208I ANR2514E ANR2661E ANR2663I ANR4481I ANR4482I ANR4520I ANR4523I ANR4525E ANR4930I ANR4931I ANR5331S (MVS) ANR8214E (HP) ANR8222W (HP)
ANR8383E ANR8686I (AIX) ANR8827E ANR0826I ANR1788W ANR1789W ANR1790W ANR6927W ANR6928W ANR0826I ANR1788W ANR1789W ANR1790W ANR6927W ANR6928W
Deleted Server Messages
These are the deleted server messages. ANR7811I ANR7812I ANR1081W ANR1082W ANR1083W ANR1084W ANR1085W ANR1086W ANR1087W ANR1088W ANR1089W ANR1090W ANR1091W ANR1092W ANR1093W ANR1121W ANR1122W ANR1123W ANR1124W ANR1125W ANR1126W ANR1127W ANR1128W ANR1129W ANR1130W ANR1131W ANR1132W ANR1133W ANR1134W ANR1135W ANR4522I ANR4940W ANR8300E (PASE) ANR8301E (PASE) ANR8302E (PASE) ANR8305E (PASE) ANR8306I (PASE) ANR8307I (PASE) ANR8309E (PASE) ANR8350E (PASE) ANR8374E (PASE) ANR8375E (PASE) ANR8378I (PASE) ANR8379I (PASE) ANR8400I (PASE) ANR8408E (PASE) ANR8419E (PASE) ANR8439I (PASE) ANR8440E (PASE) ANR8441E (PASE) ANR8446I (PASE) ANR8451I (PASE) ANR8452E (PASE)
xvi
IBM Tivoli Storage Manager: Messages
ANR8453E (PASE) ANR8454E (PASE) ANR8462I (PASE) ANR8470W (PASE) ANR8471E (PASE) ANR8474E (PASE) ANR8476E (PASE) ANR8493I (PASE) ANR8494E (PASE) ANR8500E (PASE) ANR8745E (PASE) ANR8749E (PASE) ANR8753W (PASE) ANR8760I (PASE) ANR8761I (PASE) ANR8762I (PASE) ANR8767I (PASE) ANR8769E (PASE) ANR8770W (PASE) ANR8771E (PASE) ANR8772I (PASE) ANR8773E (PASE) ANR8776W (PASE) ANR8777E (PASE) ANR8779E (PASE) ANR8781E (PASE) ANR8783E (PASE) ANR8784E (PASE) ANR8786I (PASE) ANR8787W (PASE) ANR8788W (PASE) ANR8789W (PASE) ANR8790I (PASE) ANR8791E (PASE) ANR8792E (PASE) ANR8793E (PASE) ANR8794E (PASE) ANR8795I (PASE) ANR8797W (PASE) ANR8798W (PASE) ANR8799I (PASE) ANR8800I (PASE) ANR8801I (PASE) ANR8802E (PASE) ANR8803I (PASE)
ANR8804I (PASE) ANR8805I (PASE) ANR8806E (PASE) ANR8807W (PASE) ANR8808E (PASE) ANR8809I (PASE) ANR8810I (PASE) ANR8811E (PASE) ANR8812E (PASE) ANR8813W (PASE) ANR8814I (PASE) ANR8815I (PASE) ANR8816E (PASE) ANR8817E (PASE) ANR8818E (PASE) ANR8819E (PASE) ANR8820W (PASE) ANR8821E (PASE) ANR8822E (PASE) ANR8823E (PASE) ANR8824E (PASE) ANR8826E (PASE) ANR8827E (PASE) ANR8828E (PASE) ANR8829I (PASE) ANR8830E (PASE) ANR8831W (PASE) ANR8835W (PASE) ANR8836E (PASE) ANR8837E (PASE) ANR8838E (PASE) ANR8839W (PASE) ANR8840E (PASE) ANR8842E (PASE) ANR8843E (PASE) ANR8844E (PASE) ANR8845E (PASE) ANR8847E (PASE) ANR8850I (PASE) ANR8851E (PASE) ANR8852E (PASE) ANR8853E (PASE) ANR8854E (PASE) ANR8855E (PASE) ANR8856E (PASE)
New, Changed, and Deleted Messages
xvii
ANR8857I (PASE) ANR8858W (PASE) ANR8859W (PASE) ANR8860W (PASE) ANR8861I (PASE) ANR8862I (PASE) ANR8863I (PASE) ANR8864I (PASE) ANR8865W (PASE) ANR8866E (PASE) ANR8867I (PASE) ANR8868E (PASE) ANR8870E (PASE) ANR8871I (PASE) ANR8872E (PASE) ANR8873E (PASE) ANR8901E (PASE) ANR8902W (PASE) ANR8903E (PASE) ANR8904I (PASE) ANR8905I (PASE) ANR8906I (PASE) ANR8907E (PASE) ANR8908I (PASE) ANR8909I (PASE) ANR8910I (PASE) ANR8911W (PASE) ANR8912E (PASE) ANR8913I (PASE) ANR8914I (PASE) ANR8915I (PASE) ANR8916I (PASE) ANR8917I (PASE) ANR8918I (PASE) ANR8919I (PASE) ANR8920I (PASE) ANR8921E (PASE) ANR8922I (PASE) ANR8923I (PASE) ANR8925W (PASE) ANR8926W (PASE) ANR8927W (PASE) ANR8928W (PASE) ANR8929E (PASE) ANR8930W (PASE)
ANR8931W (PASE) ANR8932W (PASE) ANR8933W (PASE) ANR8934W (PASE) ANR8935E (PASE) ANR8936W (PASE) ANR8937W (PASE) ANR9710E (PASE) ANR9711E (PASE) ANR9712E (PASE) ANR9713E (PASE) ANR9714E (PASE) ANR9715E (PASE) ANR9716E (PASE) ANR9717E (PASE) ANR9718E (PASE) ANR9719E (PASE) ANR9720I (PASE) ANR9721E (PASE) ANR9722I (PASE) ANR9723I (PASE) ANR9724I (PASE) ANR9725E (PASE) ANR9726E (PASE) ANR9727E (PASE) ANR9728E (PASE) ANR9729E (PASE) ANR9730I (PASE) ANR9731I (PASE) ANR9732I (PASE) ANR9733I (PASE) ANR9734I (PASE) ANR9735I (PASE) ANR9736E (PASE) ANR9737I (PASE) ANR9738I (PASE) ANR9739I (PASE) ANR9740E (PASE) ANR9741E (PASE) ANR9742E (PASE) ANR9743I (PASE) ANR9744E (PASE) ANR9745E (PASE) ANR9746E (PASE) ANR9747I (PASE)
xviii
IBM Tivoli Storage Manager: Messages
ANR9748I (PASE) ANR9749I (PASE) ANR9750I (PASE) ANR9751E (PASE) ANR9752E (PASE) ANR9753E (PASE) ANR9754I (PASE) ANR9755E (PASE) ANR9756I (PASE) ANR9757E (PASE) ANR9758W (PASE) ANR9759E (PASE) ANR9760I (PASE) ANR9773E (PASE) ANR9774W (PASE) ANR9775E (PASE) ANR9776I (PASE) ANR9778E (PASE) ANR9779E (PASE) ANR9780E (PASE)
ANR9781E ANR9782E ANR9783E ANR9784E ANR9785E ANR9786E ANR9787E
(PASE) (PASE) (PASE) (PASE) (PASE) (PASE) (PASE)
ANR9788E (PASE) ANR9789E (PASE) ANR9790W (PASE) ANR9791I (PASE) ANR9792E (PASE) ANR9794E (PASE) ANR9795E (PASE) ANR9796E (PASE) ANR9797E (PASE) ANR9798E (PASE) ANR9799E (PASE) ANR4972E
New, Changed, and Deleted Client Messages
This section contains lists of the new, changed, and deleted client messages.
New Client Messages
These are the new client messages. ANS0311E ANS0312E ANS0313E ANS0314E ANS0350E ANS0351E ANS0352E ANS0353E ANS0354E ANS0355E ANS0356E ANS0357E ANS0358E ANS0359E ANS0420W ANS1015E ANS1020E ANS1021E ANS1155E ANS1341E ANS1384E ANS1385E ANS1386E ANS1387E ANS1388E ANS1389W ANS1391W ANS1392W ANS1393W ANS1394E ANS1395E ANS1396E ANS1397W ANS1398E ANS1399W ANS1400W ANS1401W ANS1402W ANS1408W
New, Changed, and Deleted Messages
xix
ANS1461E ANS1462E ANS1463E ANS1464S ANS1465E ANS1466E ANS1467E ANS1468E ANS1469E ANS1471E ANS1472E ANS1519E ANS1523E ANS1532E ANS1533E ANS1534E ANS1535E ANS1536E ANS1537E ANS1538E ANS1539E ANS1540E ANS1551E ANS1552W ANS1553W ANS1554W ANS1555E ANS1556E ANS1557W ANS1558W ANS1560W ANS1562E ANS1563W ANS1565E ANS1566E ANS1600E ANS1601E ANS1602E ANS1603E ANS1604E ANS1605E ANS1606E ANS1607E ANS1608E ANS1609E
ANS1610E ANS1611E ANS1612E ANS1613E ANS1614E ANS1615E ANS1616E ANS1617E ANS1618E ANS1619E ANS1800W ANS1813E ANS1977E ANS1978E ANS1979E ANS1980E ANS1981E ANS1986E ANS1988W ANS1999E ANS2038W ANS2700E ANS2701E ANS2702E ANS2703E ANS2704E ANS2705S ANS2706E ANS2707E ANS2708E ANS2709W ANS2710W ANS2711W ANS2712W ANS2713E ANS2714W ANS2798E ANS2799E ANS4020E ANS4021E ANS4039E ANS4500E ANS4501E ANS4502E ANS4503E
xx
IBM Tivoli Storage Manager: Messages
ANS4504E ANS4505E ANS4506E ANS4507E ANS5215E ANS5216E ANS7533E ANS8050E ANS8776E ANS8777E ANS8778E ANS8779E ANS8780E ANS8781E ANS8782E ANS8783E ANS8784E ANS8785E ANS8786E ANS8787E ANS8788E ANS8789E ANS8790E ANS8791E ANS8792E ANS8793E ANS8794E ANS8795E ANS8818E ANS8819E ANS8820E ANS8821E ANS8822E ANS8823E ANS8824E ANS8825E ANS8826E ANS8827E ANS8828E ANS8829E ANS8830E ANS8831E ANS8832E ANS8833E ANS8834E
ANS8835E ANS8836E ANS8837E ANS8838E ANS8839E ANS8840E ANS8841E ANS8842E ANS8843E ANS8844E ANS8845E ANS8846E ANS8847E ANS8848E ANS8849E ANS8850E ANS8851E ANS8852E ANS8853E ANS8854E ANS8855E ANS8856E ANS8857E ANS8858E ANS8859E ANS8939E ANS8945E ANS9417W ANS9474E ANS9475E ANS9554E ANS9842E ANS9845E ANS10888W ANS13053E ANS14044E ANS14045E ANS14046E ANS14047E ANS18772W ANS18773W ANS18774W ANS18980W ANS18991W ANS19011W
New, Changed, and Deleted Messages
xxi
ANS19036W ANS19046E ANS19108E
ANS19109E ANS19110E ANS19111E
Changed Client Messages
These are the changed client messages. ANS0236E ANS0254E ANS1000E ANS1007E ANS1010E ANS1026E ANS1028S ANS1029E ANS1030E ANS1031E ANS1033E ANS1035S ANS1047E ANS1050E ANS1061E ANS1071E ANS1075E ANS1096S ANS1101E ANS1102E ANS1107E ANS1108E ANS1115W ANS1116E ANS1120E ANS1126E ANS1127E ANS1128S ANS1129S ANS1133W ANS1145E ANS1149E ANS1151E ANS1153E ANS1185W ANS1193E ANS1213W ANS1219E ANS1220E ANS1228E ANS1232E ANS1233E ANS1235E ANS1237E ANS1238S ANS1243E ANS1245E ANS1263E ANS1264E ANS1300E ANS1304W ANS1305E ANS1306E ANS1315W ANS1326S ANS1332E ANS1352E ANS1366E ANS1371E ANS1373W ANS1376W ANS1377W ANS1380W ANS1381W ANS1482E ANS1486E ANS1487E ANS1489E ANS1498E ANS1506E ANS1512E ANS1546W ANS1547W ANS1549E ANS1550E ANS1814E ANS1929E ANS1932E ANS1948E
xxii
IBM Tivoli Storage Manager: Messages
ANS1949E ANS1950E ANS1951E ANS1971E ANS1972E ANS2025E ANS5003S ANS5004S ANS5006W ANS5007W ANS5020E ANS5091S ANS5093S ANS5122E ANS5124S ANS5128E ANS5129E ANS5139E ANS5152S ANS5164E ANS5166E ANS5179E ANS5206E ANS5222E ANS7421W ANS7564E ANS7642E ANS7660E ANS7701E ANS8046E ANS8047E ANS8049E ANS8053E ANS8055E ANS9021E ANS9022E ANS9025W ANS9054E ANS9058E ANS9064E ANS9075W ANS9094W ANS9142W ANS9147E ANS9148E
ANS9149E ANS9152E ANS9153E ANS9154E ANS9155E ANS9157W ANS9158W ANS9159E ANS9160E ANS9162E ANS9183E ANS9203E ANS9240W ANS9251E ANS9254E ANS9267E ANS9280E ANS9311E ANS9402E ANS9424E ANS9432E ANS9462E ANS9502W ANS9519W ANS9520E ANS9521E ANS9523E ANS9526E ANS9527E ANS9528W ANS9529W ANS9530W ANS9531E ANS9532W ANS9533W ANS9535E ANS9542E ANS9543W ANS9545E ANS9732E ANS9735E ANS9736E ANS9737E ANS9738S ANS9740S
New, Changed, and Deleted Messages
xxiii
ANS9741E ANS9742E ANS9799W ANS9800W ANS9801W ANS9802W ANS9803W ANS9804W ANS9805W ANS9806W ANS9808W ANS9809W ANS9824W ANS9840W ANS9841E ANS9843E ANS9844E
ANS9846W ANS9848W ANS9852E ANS9853W ANS9854W ANS9908E ANS9961E ANS14000E ANS14014E ANS14015E ANS14022E ANS14031E ANS14036E ANS14900W ANS14988W ANS14999E
Deleted Client Messages
These are the deleted client messages. ANS1050S ANS5166E ANS5179E
xxiv
IBM Tivoli Storage Manager: Messages
Summary of Changes to IBM Tivoli Storage Manager Version 5
This section summarizes the changes that were made to the IBM Tivoli Storage Manager product.
Technical Changes for Version 5 Release 3 December 2004
The following changes have been made to the product for this edition: Accurate SAN Device Mapping Device IDs within a SAN environment change when a reset or other environmental changes occur. With accurate SAN device mapping, Tivoli Storage Manager can now detect SAN changes and automatically make the appropriate processing changes to the server definitions. QUERY SAN can now be issued to display all devices on the SAN, along with information such as the path, device-type, and serial number. See the Administrators Guide and the Administrators Reference for more information. ACSLS Library Support Enhancements Library support has been enhanced to allow the sharing of ACSLS libraries. This implementation will provide the basic support to share ACSLS libraries across Tivoli Storage Manager servers in the same way that SCSI libraries are shared. Support for LAN-Free data movement using libraries that are controlled by StorageTeks ACSLS interface has also been provided. As a result, the use of a third party product is now optional. See the Administrators Guide and the Administrators Reference for more information. Activity Log Management The activity log can now be managed based either on maximum size for the log or retention time. The new option for size-based activity log management gives administrators greater control over the amount of space the activity log occupies. Additional information about the activity log is now displayed when the server status is queried. See the Administrators Guide and the Administrators Reference for more information. Check-In and Check-Out Enhancements The amount of user intervention required for check in and check out functions has been reduced. See the Administrators Guide and the Administrators Reference for more information. Collocation by Group Collocation by group is now supported. Groups of nodes can be defined, and the server can then collocate data based on these groups. Collocation by group can yield the following benefits: v Reduce unused tape capacity by allowing more collocated data on individual tapes v Minimize mounts of target volumes
Copyright IBM Corp. 1993, 2004
xxv
v Minimize database scanning and reduce tape passes for sequential-to-sequential transfer Note: During collocation processing the message ANR1142I will be replaced with ANR1176I. See the Administrators Guide and the Administrators Reference for more information. Communications Options There is now a shared memory communications option between the Tivoli Storage Manager server for Windows and the backup-archive client for Windows. It can be used to perform backups, archives, restores, and retrieves. You can also enable the shared memory communication protocol in the Windows storage agent for communication with the Windows backup-archive client.There is now a shared memory communications option between the Tivoli Storage Manager server for Linux and the backup-archive client for Linux. It can be used to perform backups, archives, restores, and retrieves. You can also enable the shared memory communication protocol in the Linux storage agent for communication with the Linux backup-archive client. Note: While using shared memory, if a message queue must be created, but the system limit for the maximum number of message queues (MSGMNI) will be exceeded if a message queue is created, the following message will be issued:
ANR9999D shmcomm.c(1598): ThreadId<39> Error from msgget (2), errno = 28
To find the maximum number of message queues allowed on your system, issue the following command:
cat /proc/sys/kernel/msgmni
To increase the maximum number of message queues on your system, issue the following command:
sysctl -w kernel.msgmni=n
where n is the maximum number of message queues (MSGMNI) you want to be allowed by the system. See the Administrators Reference for more information. Database Reorganization Periodically reorganizing the servers database can improve performance. A new command has been added that allows administrators to determine the estimated space saved by reorganization of the database. The process can be queried to monitor the commands progress and, when finished, the results can be viewed by querying the database in detailed format. See the Administrators Guide and the Administrators Reference for more information. Disk-only Backup Disk-only backup has been enhanced in order to take advantage of the inexpensive disk storage currently available in the market. These improvements to sequential-access FILE device type and random-access DISK device class storage include:
xxvi
IBM Tivoli Storage Manager: Messages
v The ability to create large, sequential-access FILE-type storage pools using a single FILE device-class definition that specifies two or more directories. v The ability to create and format two or more private FILE- or device-type volumes in a single step. v The ability to use enhanced space trigger functionality to automatically allocate space for private volumes in sequential-access FILE device type and random-access DISK device class storage pools. This will reduce the potential for disk fragmentation and maintenance overhead. See the Administrators Guide and the Administrators Reference for more information. Enhancements for Server Migration and Reclamation Processes Administrators can now control and schedule routine server operations by configuring migration and reclamation schedules to run during convenient server activity times. The number of off-site volumes can also be limited in order for reclamation to be completed within a desired amount of time. These new features allow for better utilization of available tape drives and FILE volumes. See the Administrators Guide and the Administrators Reference for more information. IBM 3592 WORM Support Tivoli Storage Manager now supports the 3592 WORM tape device. See the Administrators Guide and the Administrators Reference for more information. Increased Block Size for Writing to Tape The maximum transfer length for all host bus adapters has increased. The block size used by the Tivoli Storage Manager sever on Windows for writing data to certain types of tape drives has also increased. Increasing the transfer length increases the rate at which data is processed for backups, archives, restores, and retrieves. The maximum supported transfer length is now 256 KB. See the Administrators Guide and the Administrators Reference for more information. LAN-free Environment Configuration Enhancements have been made to allow you to quickly determine if your LAN-free environment has been configured correctly. You can request validation for one client node and one storage agent. When validation is requested, a detailed report is generated explaining why the storage pool is or is not LAN-free capable. As a result, you can determine if there is a setting or configuration issue on the server preventing LAN-free data movement. See the Administrators Guide and the Administrators Reference for more information. New Interface to Manage Servers: Administration Center The Administration Center is a Web-based interface that can be used to centrally configure and manage IBM Tivoli Storage Manager Version 5.3 servers. This new interface replaces the administrative Web interface. The Administration Center is installed as an IBM Integrated Solutions Console component. The Integrated Solutions Console allows you to create custom
Summary of Changes to IBM Tivoli Storage Manager Version 5
xxvii
solutions by installing components provided by one or more IBM applications. See the Installation Guide for installation information. See the Administrators Guide and the Administrators Reference for more information. NDMP Operations NDMP operations for backup of NAS file servers have been enhanced to support the following functions: v Directory-level backup of NAS data, which enables the division of a file system backup operation among several NDMP backup operations as well as several tape drives. This enhancement will reduce backup and restore times. v The ability to separate the snapshot creation process from the actual backup of the data. Snapshots can be taken any time, while the backup to tape can be deferred to a more convenient time. See the Administrators Guide and the Administrators Reference for more information. SCSI Library Enhancements You can now define a 3592 drive to an SCSI library. See the Administrators Reference for more information. Server Processing Control in Scripts Administrators can automate routine server operations. In server scripts, commands can now be processed in serial and parallel. This enables multiple processes to run concurrently, which reduces data transfer time. See the Administrators Guide and the Administrators Reference for more information. Simultaneous Write Inheritance Improvements The simultaneous write function lets you write data simultaneously to primary storage pools and up to three copy storage pools, increasing your level of data protection and reducing the time required for storage pool backup. In version 5.3, when a data storage operation switches from a primary storage pool to the next primary storage pool in the storage pool hierarchy, the next storage pool inherits the list of copy storage pools and the value of the COPYCONTINUE parameter from the primary storage pool. One benefit of this design is that it reduces the likelihood that mount points have to be released and reacquired when the server switches from one primary storage pool to another. See the Administrators Guide and the Administrators Reference for more information. Space Triggers for Mirrored Volumes Space triggers for mirrored volumes have been enhanced, allowing administers to specify an expansion prefix for new mirrored volumes. See the Administrators Guide and the Administrators Reference for more information. Storage Agent and Library Sharing Failover Failover for an AIX HACMP environment has been updated to include failover in a library sharing or storage agent environment. Tivoli Storage Manager can determine which devices need to be reset on startup of the server or storage agent. A target reset will then be performed on only those devices.
xxviii
IBM Tivoli Storage Manager: Messages
See the Administrators Guide and the Administrators Reference for more information. Support for Multiple Tivoli Storage Manager Client Nodes Backup from multiple nodes to be stored as a single target node in the server database is now allowed. With the consolidation of data under a single target node on the server, directories and files can be easily found when restore operations are necessary. It is also no longer necessary for physical machines to share password files, because password management and Tivoli Storage Manager server authentication is now handled by clients (independent of relationships with other nodes). See the Administrators Guide and the Administrators Reference for more information. Tivoli Storage Manager Scheduling Flexibility Tivoli Storage Manager schedule capability now allows for more useful calendar-type administrative and client scheduling. There is now the flexibility to schedule most repetitive items and even some holidays, such as: v run on the last Friday of every month v run on the first Sunday of every quarter v run on every day in the last week of year See the Administrators Guide and the Administrators Reference for more information.
Technical Changes for Version 5 Release 2 January 2004
The following changes have been made to the product for this edition: NDMP Support Tivoli Storage Manager now supports backup via NDMP for NAS file servers that comply with NDMP standards and are neither EMC Celerra nor Network Appliance file servers. NAS vendors now can use a certification process in order to ensure NAS file servers are compatible with Tivoli Storage Manager. Disaster Recovery Manager With this function you can prepare a disaster recovery plan to help you recover your Tivoli Storage Manager servers, clients, and data in the case of a disaster. You can also use the function to manage your offsite recovery media and automate some recovery procedures. IBM Tivoli Storage Manager for Data Retention Tivoli Storage Manager for Data Retention provides enhancements to Tivoli Storage Manager Extended Edition to prevent critical data from being erased or rewritten. This new product helps meet additional requirements defined by regulatory agencies for retention and disposition of data. These enhancements include new functionality and new device support and are delivered in these key areas: Data retention protection This feature prevents deliberate or accidental deletion of data until its specified retention criterion is met. Event-based retention policy In some cases, retention must be based on an external event such as closing a brokerage account. Tivoli Storage Manager for Data
Summary of Changes to IBM Tivoli Storage Manager Version 5
xxix
Retention supports event-based retention policy to allow data retention to be based on an event other than the storage of the data. Deletion hold In order to ensure that records are not deleted when a regulatory retention period has lapsed but other legal requirements mandate that the records continue to be maintained, Tivoli Storage Manager for Data Retention includes deletion hold. Using this feature will prevent stored data from being deleted until the hold is released. Operational Reporting The Operational Reporting feature automates daily monitoring tasks and generates reports indicating whether a server requires attention. This feature reduces the amount of time required to administer Tivoli Storage Manager. IBM 3592 Support Tivoli Storage Manager now supports IBM 3592 devices. The 3592 device has fast access capability that gives users the option of scaling down tape capacities in order to get improved data access response times. See the Administrators Reference for more information. EMC Centera Support Tivoli Storage Manager now supports the EMC Centera V2.0 storage device. Centera devices provide retention protection for archiving fixed content digital data records. Together Tivoli Storage Manager for Data Retention and Centera devices provide a foundation storage system that allows mission-critical data to be retained for a mandated period of time without the possibility of being rewritten or erased. Centera devices can also be used as a standard storage device if no mandatory retention requirements exist for the data. To enable Centera support for data retention protection, use the new commands, DEFINE DEVCLASS CENTERA and SET ARCHIVERETENTION PROTECTION. Sony AIT50 and AIT100 WORM Media Support Tivoli Storage Manager now supports the Sony AIT50 and AIT100 WORM (write once, read many) media technology. To enable this support, the DEFINE DEVCLASS (8MM) command has a new parameter.
xxx
IBM Tivoli Storage Manager: Messages
Part 1. Introduction
Copyright IBM Corp. 1993, 2004
IBM Tivoli Storage Manager: Messages
Chapter 1. Introduction
IBM Tivoli Storage Manager (Tivoli Storage Manager) is an enterprise-wide storage management application for the network. It provides automated storage management services to multivendor workstations, personal computers, and local area network (LAN) file servers. 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 product (application product) 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. Message number ANR7831I and numbers in the range ANR79008199 are AS/400 platformspecific messages and are not published in this manual. You can obtain the explanation for these messages using AS/400 commands such as WRKMSGD to get to the "Work with Message Descriptions" panel.
Copyright IBM Corp. 1993, 2004
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 may send statistics to the server providing information about a backup or restore. These statistics are informational messages that may be enabled or disabled to the various event logging receivers. These messages are not published in this manual. v Messages that begin with prefix ANR originate from the server. v Messages that begin with prefix ANS are from one of the following clients: Administrative clients Application program interface clients Backuparchive clients Space Manager (HSM) clients Data Protection for Lotus Notes v Messages that begin with prefix ACD are from Data Protection for Lotus Domino. 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.com for DB2 UDB and Data Protection for mySAP.com for Oracle. v Messages that begin with prefix DKP and are in range 00019999 are from Data Protection for WebSphere Application Server. v Messages that begin with prefix EEO and are in range 00009999 are from Data Protection for ESS for Oracle. v Messages that begin with prefix EEP and are in range 00009999 are from Data Protection for ESS for DB2 UDB. v Messages that begin with prefix IDS and are in range 00000999 are from Data Protection for EMC Symmetrix for R/3. v Messages that begin with prefix IDS and are in range 10001999 are from Data Protection for IBM ESS for mySAP.com for DB2 UDB and Data Protection for IBM ESS for mySAP.com for Oracle.
Message Format
The following examples describe the Tivoli Storage Manager message format:
IBM Tivoli Storage Manager: Messages
The callouts to the right identify each part of the format.
Message Prefix Message Number Message Type* ANR 0992 I Server installation complete. Explanation: The server installation procedure has completed successfully. The server is now available for normal operation. System Action: Server completes installation processing. Message Text
Explanation
System Action
User Response: None. * I = Information E = Error S = Severe Error W = Warning K = Kernel message that originates from the hierarchical storage management (HSM) client
User Response
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. The server and client messages fall into the following categories: v Common messages that pertain to all Tivoli Storage Manager server platforms v Platform specific messages that pertain to each operating environment for the server and the client v Messages that pertain to application clients
How to Read a Return Code Message
Many different commands can generate the same return code. The following examples are illustrations of two different commands issued that result in the same return code; therefore, you must read the descriptive message for the command.
Chapter 1. Introduction
Example One for QUERY EVENT Command:
Example Two for DEFINE VOLUME Command:
IBM Tivoli Storage Manager: Messages
Chapter 2. Obtaining Help for IBM Tivoli Storage Manager
This section describes the following: v How to obtain help with processing errors by using Internet and IBMLink/ServiceLink v How to describe errors with keywords v How to obtain online message help v What information to have available when you contact your service representative
Internet and IBMLink Assistance
Tivoli Storage Manager message help explanations may suggest that you contact your service representative for additional help with processing errors. Online help is available through Internet and IBMLink/ServiceLink.
Internet
You can get additional information through an anonymous FTP server, ftp.software.ibm.com. Tivoli Storage Manager information is in the /storage/tivoli-storage-management directory. A newsgroup, [email protected], is implemented by a third party. IBM supports this newsgroup on a best-effort basis only.
IBMLink/ServiceLink
If your installation has access to IBMLink/ServiceLink, an interactive online database program, you can: v Search for an existing authorized program analysis report (APAR) that is similar to your problem. v Search for an available program temporary fix (PTF) for the existing APAR. v Order the PTF if it is available. v Create an Electronic Technical Response (ETR) problem report to get assistance from an Tivoli Storage Manager service representative.
Describing the Error with Keywords
When you use IBMLink/Servicelink or call your service representative, accurately describe the problem so that the service representative may quickly help you solve the problem. Identify the processing error with a full set of keywords whenever possible. A keyword is a word or an abbreviation used to describe a single aspect of a program failure. Each keyword describes an aspect of a processing error. The following example displays the necessary set of keywords:
56480200n R312 type command function
Where 56480200n
Copyright IBM Corp. 1993, 2004
Represents Component identification keyword
Where R312 type command function
Represents Release level keyword Type-of-failure keyword Command keyword Function keyword
Component Identification Keyword
The component identifiers for Tivoli Storage Manager are 5698-ISM and 5698-ISX, with the exceptions listed below:
Component Tivoli Storage Manager for Space Management Tivoli Storage Manager for Storage Area Networks Tivoli Storage Manager for Mail Tivoli Storage Manager for Databases Tivoli Storage Manager for Application Servers Tivoli Storage Manager for Hardware Tivoli Storage Manager for Enterprise Resource Planning Component ID 5698-HSM
5698-SAN
5698-APE 5698-APD
5698-APW
5698-APH
5698-APR
Type-of-Failure Keyword
The following keywords identify the type of failure that may occur:
Keyword ABENDxxx INCORROUT LOOP Description Use this keyword when the system ends abnormally. Use this keyword when incorrect output is received or expected output is missing. Use this keyword if a part of the program code runs endlessly; include situations in which a part of the output repeats continuously. Use this keyword when a message: v Indicates an internal program error v Is issued in a set of conditions that should not cause it to be issued v Contains invalid or missing data See Understanding Messages on page 4 for a description of the message format. Use this keyword when you receive no response within a reasonable time that can be perceived as poor response or poor performance.
MSGANRnnnnt (or) MSGANSnnnnt
WAIT
IBM Tivoli Storage Manager: Messages
Keyword xxxxxxxxxx (Documentation)
PERFM
Description Use this keyword when a programming problem appears to be caused by incorrect, missing, or ambiguous information in one of the Tivoli Storage Manager publications. Enter the order number of the publication in place of xxxxxxxxxx. Include the letter prefix and version number, but omit all hyphens, for example, GC35040500. Refer to IBM Tivoli Storage Manager Publications on page v for a list of the Tivoli Storage Manager publications. Use this keyword as a closing code for an APAR.
Command Keyword
Build keywords based on Tivoli Storage Manager commands. Refer to Administrators Reference for a list of the commands.
Function Keyword
Use keywords that refer to basic Tivoli Storage Manager functions such as backup, retrieve, archive, recover, migrate, and export-import.
Obtaining Online HELP (Get Help on Error Messages)
Use the HELP command on the server console or administrative command line client to display information about server and administrative command line client messages. Use the HELP command on the backup-archive client to display information about backup-archive client messages. The Help error message number command displays the help text specific to the error message. You can get help information on server messages (prefixed by ANR), and administrative command line and backup-archive client messages (prefixed by ANS or ANE) except those specific to the administrative graphical user interface client.
Chapter 2. Obtaining Help for IBM Tivoli Storage Manager
10
IBM Tivoli Storage Manager: Messages
Part 2. Server Messages
Copyright IBM Corp. 1993, 2004
11
12
IBM Tivoli Storage Manager: Messages
Chapter 3. Common and Platform Specific Messages (ANR0100ANR9999)
This chapter contains the common and platform-specific server messages. The organization of the messages are grouped by the message prefix ANR and documented in ascending numeric order. If a message is platform specific and a duplicate, the appropriate platform name is added after the message number and it is also documented alphabetically by platform name.
ANR0100E Source file(line number): Error error code creating table table name. ANR0104E Source file(line number): Error error code 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. System Action: The activity that generated this error fails. User Response: Contact your service representative. ANR0101E Source file(line number): Error error code opening table table name.
Explanation: An internal error has occurred in an 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. User Response: Contact your service representative. ANR0105E Source file(line number): Error setting search bounds for table table name.
Explanation: An internal error has occurred in an attempt to access 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. User Response: Contact your service representative. ANR0102E Source file(line number): Error error code inserting row in table table name.
Explanation: An internal error has occurred in an attempt to access data in 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. User Response: Contact your service representative. ANR0106E Source file(line number): Unexpected error error code fetching row in table table name.
Explanation: An internal error has occurred in an attempt to add data to a server database table. This message always accompanies another error message and provides more detail about that error. System Action: The activity that generated this error fails. User Response: Contact your service representative. ANR0103E Source file(line number): Error error code updating row in table table name.
Explanation: An internal error has occurred in an attempt to access data in 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. User Response: Contact your service representative. ANR0107W Source file(line number): Transaction transaction ID was not committed due to an internal error.
Explanation: An internal error has occurred in an attempt to update data in 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. User Response: Contact your service representative.
Copyright IBM Corp. 1993, 2004
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 ANR0116W
System Action: The activity that generated this error fails. User Response: Contact your service representative. ANR0108E Source file(line number): could not start a new transaction. BEGINNODEID and ENDNODEID, or neither of them. ANR0112E Command: The specified BEGINNODEID node id is greater than the ENDNODEID node id.
Explanation: An error occurred while attempting to start a new transaction. Possibly there is not enough memory. System Action: The activity that generated this error 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.
Explanation: Either the BEGINNODEID or the ENDNODEID is invalid because the value of the BEGINNODEID is greater than the ENDNODEID. System Action: The server fails the command. User Response: Reissue the command, specifying the ENDNODEID to be greater than the BEGINNODEID, or both to be equal. ANR0115W The server script script name attempted to start more parallel commands than are allowed for a single script. A single script is limited to parallel command limit parallel commands.
Explanation: An error occurred while attempting to load the cryptography module. 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. Use the ACCEPT DATE command to establish the current date as valid.
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 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 disable for client access. Server expiration 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 command to enable the server for client sessions. ANR0111E Command: The BEGINNODEID and ENDNODEID are both required to be specified.
Explanation: The server waits for all previous parallel commands started by the script to complete. When all previous parallel commands are complete, the server allows the script to continue. The script can attempt to start more parallel commands. If the limit is exceeded, the command will run serially. System Action: The server waits for all previous parallel commands before allowing the script to continue. User Response: Reduce the number of parallel commands or scripts that are running on the server at any one time.
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
14
IBM Tivoli Storage Manager: Messages
ANR0117E ANR0125W
ANR0117E The server contains stored data. Archive data retention protection cannot be changed. ANR0121E command is not allowed when archive data retention is enabled.
Explanation: The archive data retention protection state cannot be changed while the server contains any backup, archive, or space-managed data. System Action: Processing continues. 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 specified command is not allowed when archive data retention protection is enabled on the server. System Action: Processing continues. User Response: None. ANR0122E command: A node cannot be assigned to a new domain when archive data retention is enabled.
Explanation: A previously defined node cannot be assigned to a new domain when archive data retention protection is enabled on the server. System Action: Processing continues. User Response: None. ANR0123E command: A device type of SERVER is not allowed when archive data retention is enabled.
Explanation: The client options INCLUDE and EXCLUDE are not valid and have been replaced by the combined INCLEXCL. If INCLUDE and EXCLUDE are used in client option sets, use the INCLEXCL option along with the specific include or exclude option that you want the clients to use. System Action: The option is ignored and is not sent to the client. The server continues processing. User Response: Client options INCLUDE and EXCLUDE are not valid; use the INCLEXCL option along with the specific include or exclude option that you want the clients to use. ANR0119W The client option client option is not valid and will not be sent to the client. Delete it from client option set.
Explanation: The specified device type is not allowed when archive data retention protection is enabled on the server. System Action: Processing continues. User Response: None. 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 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 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. User Response: None. ANR0125W DELETE FILESPACE filespace name for node node name contains retention protected data and cannot be deleted.
Explanation: The archive data retention protection state has been set. System Action: Processing continues. User Response: None.
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: v Archive retention protection is enabled and the objects retention period has not elapsed. v The object is part of a deletion hold. System Action: The file space is not deleted. User Response: None.
Chapter 3. Common and Platform Specfic Messages
15
ANR0126W ANR0134W
ANR0126W DELETE VOLUME: Volume volume name contains retention protected data and can not be deleted. 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 DiagnosticID: Server DB space exhausted.
Explanation: The specified volume cannot be deleted because it contains one or more objects that must be retained because of one of the following: v Archive retention protection is enabled and the objects retention period has not elapsed. v The object is part of a deletion hold. System Action: Processing continues. User Response: None. ANR0127E command to another server is not allowed when data retention protection is enabled on the target server.
Explanation: There is no space to write data to the server database. System Action: The activity that generated this error 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 DiagnosticID: Memory allocation failed: object object name, size size.
Explanation: The specified command is not allowed when data retention protection is enabled on the target server. System Action: Processing continues. User Response: None. ANR0128W The previous database upgrade did not complete successfully.
Explanation: The server cannot obtain enough memory to create the object named. System Action: The activity that generated this error 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. ANR0133E Error loading module modname: error string
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. System Action: Processing continues. 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 Database upgrade completed successfully.
Explanation: The error specified by error string occurred when the server attempted to load module modname System Action: Server operation continues, but the function provided by the module is not available. User Response: Refer to the error string and correct the condition causing the load to fail. ANR0134W There is an error reading from standard input; the console input daemon stopped.
Explanation: The requested database upgrade operation completed successfully. System Action: Processing continues. User Response: None. ANR0130E DiagnosticID: Server LOG space exhausted.
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.
Explanation: There is no space to write data to the server recovery log. System Action: The activity that generated this error fails. User Response: To increase the amount of log space
16
IBM Tivoli Storage Manager: Messages
ANR0140I ANR0195W
ANR0140I Command: success. Node node_id_1 is granted proxy authority to node node_id_2. ANR0145E Command: failed. Node node_id_1 already has been granted proxynode authority to node node_id_2.
Explanation: The command was successful. System Action: The server performs the command. User Response: None. ANR0141E Command: failed. Node node_id_1 was not granted proxynode authority to node node_id_2.
Explanation: The command failed because a proxy relationship between the two nodes already exists. System Action: The server fails the command, but does not change the existing association. User Response: None. ANR0146E Command: failed. Node node_id_1 was not granted proxynode authority to itself.
Explanation: The command fails if either of the nodes do not exist, or if the administrator issuing the command does not have sufficient authority. System Action: The server fails the command. 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 failed because a node cannot have a proxy relationship defined to itself. System Action: The server fails the command. User Response: None. 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 was successful. System Action: The server performs the command. User Response: None. ANR0143E Command: failed. Proxynode authority for node node_id_1 has not been revoked to node node_id_2.
Explanation: The command failed because one of the nodes has not been defined to the server. System Action: The server fails the command. User Response: Verify that both nodes have been defined to the server, and then issue the command again. ANR0148I Command: No proxy relationships were found.
Explanation: The command fails if the administrator issuing the command does not have sufficient authority. System Action: The server fails the command. 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 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: No proxy relationships were found. System Action: None. User Response: None. 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. System Action: The server will fail the command. User Response: Retry the command. ANR0195W Attempting to remove extraneous database entries for volume volume name.
Explanation: The command failed because one of the nodes has not been defined to the server. System Action: The server fails the command. User Response: Verify that both nodes have been defined to the server and then issue the command again.
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.
Chapter 3. Common and Platform Specfic Messages
17
ANR0196I ANR0203W
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. 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 server successfully removed extraneous database entries for the specified volume. 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 Removal of extraneous database entries for volume volume name failed due to contention with other server processes or activities.
Explanation: The amount of space allocated to the recovery log is shown. System Action: None. User Response: None. ANR0201I Database assigned capacity is size megabytes.
Explanation: The server was not able to remove extraneous database entries for the specified volume. This was due to contention with another server process or activity. System Action: System operation continues and this volume still has extraneous database entries. User Response: It is possible that future server activities or processes will select this volume and attempt to repair it. If this occurs and the future attempt is successful, no further action is needed. The server administrator should review the activity log for the time that the repair was attempted and try to determine what caused the contention. If you are unable to determine the cause of the contention of the problem persists, please contact your service representative for additional assistance. ANR0198E Removal of extraneous database entries for volume volume name failed.
Explanation: The amount of space allocated to the database is shown. System Action: None. User Response: None. ANR0202W 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 Database volume volume name varied offline due to excessive write errors.
Explanation: The server was not able to remove extraneous database entries for the specified volume. System Action: System operation continues and this volume still has extraneous database entries. User Response: The server administrator should review the activity log for the time that the repair was attempted and try to determine the cause of the failure. If you are unable to determine the cause of the contention of the problem persists, please contact your service representative for additional assistance.
Explanation: The database volume shown has been varied offline because too many write errors have been encountered. System Action: If available, a mirrored copy of the volume is used. User Response: Correct the cause of the write errors.
18
IBM Tivoli Storage Manager: Messages
ANR0204W ANR0213W
ANR0204W Recovery log volume volume name varied offline due to excessive read errors. User Response: See accompanying messages for information about the volume in error. ANR0209E Page address mismatch detected on recovery log volume volume name, logical page logical page number (physical page physical page number); actual: logical page number.
Explanation: The recovery log volume shown has been varied offline because too many 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. ANR0205W Recovery log volume volume name varied offline due to excessive write errors.
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. User Response: See accompanying messages for information about the volume in error. ANR0210S Inconsistency found in LVM data page page number - partial write detected.
Explanation: The recovery log volume shown has been varied offline because too many write errors have been encountered. System Action: If available, a mirrored copy of the volume is used. User Response: Correct the cause of the write errors. ANR0206W Partial write detected on database volume volume name, logical page logical page number (physical page physical page number).
Explanation: During a write of an LVM internal page, an error occurs so that the page is not completely written to disk. System Action: The failed I/O operation is retried on a mirrored volume. User Response: See accompanying messages for information about the volume in error. ANR0211S Inconsistency found in LVM data page page number - page address mismatch (actual page number).
Explanation: During a write of a database page, an error occurred so that the page was not completely written to disk. System Action: The failed I/O operation is retried on a mirrored volume. User Response: See accompanying messages for information about the volume in error. ANR0207E 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 an LVM internal page, the page does not contain the expected page address. System Action: The failed I/O operation is retried on a mirrored volume. User Response: See accompanying messages for information about the volume in error. ANR0212E Unable to read disk definition file file specification.
Explanation: During a read of a database page, the page does not contain the expected page address. System Action: The failed I/O operation is retried on a mirrored volume. User Response: See accompanying messages for information about the volume in error. ANR0208W Partial write detected on recovery log volume volume name, logical page logical page number (physical page physical page number).
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. 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: During a write of a recovery log page, an error occurs so that the page is not completely written to disk. System Action: The failed I/O operation is retried on a mirrored volume.
Explanation: An error occurs trying to update the disk definition file. System Action: None.
Chapter 3. Common and Platform Specfic Messages
19
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. ANR0219I Unable to install recovery log volume volume name - capacity must be at least 5 megabytes.
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. ANR0215W Recovery log volume volume name is in the offline state - VARY ON required.
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 Synchronization of database volume volume name started as process process ID.
Explanation: At system startup, the server finds that the recovery log volume shown is in the offline state. 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.
Explanation: A background process was started to synchronize the contents of the database volume shown with its copy volume. The background process was assigned the process ID shown. System Action: The background process starts to synchronize the volume and server operation continues. User Response: The administrator may query the status of the background process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command. ANR0221I Synchronization of recovery log volume volume name started as process process ID.
Explanation: At system startup, the server finds that the database volume shown is not synchronized. System Action: A process is started to synchronize the volume. User Response: None. ANR0217I Recovery log volume volume name is in the stale state - synchronization process started.
Explanation: A background process was started to synchronize the contents of the recovery log volume shown with its copy volume(s). The background process was assigned the process ID shown. System Action: The background process starts to synchronize the volume and server operation continues. 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. ANR0222E Error action disk definition file file specification.
Explanation: At system startup, the server finds that the recovery log volume shown is not synchronized. System Action: A process is started to synchronize the volume. User Response: None. ANR0218I Unable to install database volume volume name - capacity must be at least 5 megabytes.
Explanation: An error occurred creating or changing the disk definition file. System Action: None. 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: An attempt has been made to add a database volume that is smaller than the server minimum. System Action: The volume is not added. User Response: Increase the size of the volume or supply another larger volume.
Explanation: The disk definition file cannot be written. System Action: Installation ends.
20
IBM Tivoli Storage Manager: Messages
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. 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. User Response: None. ANR0235I Synchronization complete for recovery log volume volume name.
Explanation: The specified volume name was specified more than once in the server installation execution. System Action: Installation ends. User Response: Reinitialize the server install specifying a unique name for each database and recovery log volume. ANR0230E Synchronization process failed for database volume volume name.
Explanation: The synchronization process for the recovery log volume named has finished successfully. System Action: The volume is varied online. User Response: None. ANR0240E Deletion 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.
Explanation: The process that was attempting to delete the database volume shown has failed. System Action: The volume is not deleted. User Response: See accompanying messages for more information. ANR0241E Deletion process failed for recovery log volume volume name.
Explanation: The process that was attempting to synchronize the recovery log volume shown has failed. System Action: The volume is in the stale state. User Response: See accompanying messages for more information. ANR0232I Synchronization process canceled for database volume volume name.
Explanation: The process that was attempting to delete the recovery log volume shown has failed. System Action: The volume is not deleted. User Response: See accompanying messages for more information. ANR0242I Deletion process canceled for database volume volume name.
Explanation: The process that was attempting to synchronize the database volume shown has been canceled. System Action: The volume is in the stale state. User Response: If desired, issue a VARY ONLINE command to start another synchronize process. ANR0233I Synchronization process canceled for recovery log volume volume name.
Explanation: The process that was attempting to delete the database volume shown has been canceled. System Action: The volume is not deleted. User Response: None. ANR0243I Deletion process canceled for recovery log volume volume name.
Explanation: The process that was attempting to synchronize the database volume shown has been canceled. System Action: The volume is in the stale state. User Response: If desired, issue a VARY ONLINE command to start another synchronize process.
Explanation: The process that was attempting to delete the recovery log volume shown has been canceled. System Action: The volume is not deleted. User Response: None.
Chapter 3. Common and Platform Specfic Messages
21
ANR0244I ANR0252E
ANR0244I Deletion complete for database volume volume name. ANR0249E Error reading logical page logical page number (physical page physical page number) from recovery log volume volume name.
Explanation: The delete process for the database volume named has finished successfully. System Action: The volume is deleted. User Response: None. ANR0245I Deletion complete for recovery log volume volume name.
Explanation: An error has been encountered when attempting to read a page from the specified recovery log volume. System Action: The failed I/O operation is retried on a mirrored volume, if available. User Response: See accompanying messages for 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 Recovery log page logical page number successfully read from an alternate copy on volume volume name.
Explanation: The delete process for the recovery log volume named has finished successfully. System Action: The volume is deleted. User Response: None. ANR0246E Error reading logical page logical page number (physical page physical page number) from database volume volume name.
Explanation: An error has been encountered when attempting to read a page from the specified database volume. System Action: The failed I/O operation is retried on a mirrored volume, if available. User Response: See accompanying messages for 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. 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. System Action: Processing continues. User Response: None. 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. 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 (physical page physical page number) to database volume volume name.
Explanation: After a read error, the server is able to read the desired page from another synchronized mirrored volume. System Action: Processing continues. User Response: None. ANR0248E Unable to read database page logical page number from any alternate copy.
Explanation: An error has been encountered when attempting to write a page to the specified database volume. System Action: If a mirrored volume is available then the failing volume is forced into the offline state. User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.
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 synchronized state. This message is normally preceded by a message indicating which volume failed. System Action: Processing is ended. User Response: You can repair the failed volume by halting the server and correcting the volume errors.
22
IBM Tivoli Storage Manager: Messages
ANR0253E ANR0261I
ANR0253E Unable to write database page logical page number to any alternate copy. ANR0257E Error writing physical page physical page number to restart/checkpoint area on recovery log volume volume name.
Explanation: After a write error, the server is unable to write the desired page to another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed. System Action: Processing is ended. User Response: Repair the failed volume. ANR0254E Error writing logical page logical page number (physical page physical page number) to recovery log volume volume name.
Explanation: An error has been encountered when attempting to write a page to the specified database volume. System Action: If a mirrored volume is available, the failing volume is forced into the offline state. User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online. ANR0258E Unable to write complete restart/checkpoint information to disk.
Explanation: An error has been encountered when attempting to write a page to the specified recovery log volume. System Action: If a mirrored volume is available, the failing volume is forced into the offline state. User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online. ANR0255E Unable to write recovery log page logical page number to any alternate copy.
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. System Action: Processing is ended. User Response: Repair the failing volume. ANR0259E Unable to read complete restart/checkpoint information from any database or recovery log volume.
Explanation: After a write error, the server is unable to write the desired page to another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed. System Action: Processing is ended. User Response: You can repair the failed volume by halting the server and correcting the volume errors. ANR0256E Error writing physical page physical page number to restart/checkpoint area on database volume volume name.
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. ANR0260I Database page logical page number successfully resynchronized.
Explanation: An error has been encountered when attempting to write a page to the specified database volume. System Action: If a mirrored volume is available, the failing volume is forced into the offline state. User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.
Explanation: After detecting a partially-written database page, the server is able to rewrite the page by using a synchronized mirror copy. System Action: Processing continues. User Response: None. 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. System Action: Processing continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
23
ANR0265E ANR0274E
ANR0265E Log disk processing failed: sufficient memory is not available. ANR0270E Process for Database volume volume name terminated - thread resource 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.
Explanation: During installation for the indicated volume, the server cannot start a thread to service I/O requests. System Action: Server installation stops. 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. Restart the server installation process. ANR0271E Maximum number of recovery log volumes exceeded.
Explanation: At server installation, the server is unable to process the server database disks due to insufficient memory. System Action: Server installation stops. User Response: Restart the server installation process with more memory available. ANR0267E Log volume volume name is not available.
Explanation: More recovery log volumes have been specified than the server can manage. System Action: Server installation stops. User Response: Reduce the number of recovery log volumes specified. Restart the server installation process. ANR0272E Maximum number of database volumes exceeded.
Explanation: The specified volume cannot be found during installation. System Action: Server installation stops. User Response: Determine the reason the disk is unavailable, and correct the problem. Restart the server installation process. ANR0268E Database volume volume name is not available.
Explanation: More database volumes have been specified than the server can manage. System Action: Server installation stops. 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 specified volume cannot be found during installation. System Action: Server installation stops. 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: 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: During installation for the indicated volume, the server cannot start a thread to service I/O requests. System Action: Server installation stops. 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. Restart the server installation process.
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.
24
IBM Tivoli Storage Manager: Messages
ANR0285I ANR0292W
ANR0285I Database page shadowing started using file file name. scsi bus, or a failure in a device controller. Please try to identify the cause of the partial write and take the appropriate action to prevent this from occurring in the future. ANR0289W Damaged database pages were successfully replaced using contents of page shadow file.
Explanation: The database page shadowing function was started. The file specified is used to store the shadowed database pages. System Action: None. User Response: None. ANR0286W Database page shadowing using file file name failed to start.
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. User Response: None. ANR0290W Failure occurred attempting to replace one or more damaged database pages using the contents of the page shadow file.
Explanation: The database page shadowing function could not start. An error has been encountered accessing the page shadow file specified. System Action: None. 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. ANR0287W Contents of the page shadow file file name are not valid.
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. User Response: None. ANR0291E Error writing to database page shadow file.
Explanation: The database page shadowing function could not use the contents of the existing file. Restart recovery using this file is not possible. System Action: The server attempts to start without having the database page shadow file available. User Response: The database page shadow file contents are not valid. This can be caused by: a partial write to the page shadow file itself, the file being manipulated by a process outside of the server, the file being overlayed by a different file, or the file could have been erased. ANR0288W One or more database pages in the last batch written is corrupt - contents of database page shadow file will be used to fix the page or pages.
Explanation: The server encountered an error writing to the database page shadow file. The page shadowing for the server is currently disabled. System Action: Database page shadowing for the server will remain disabled until the server is halted and restarted. User Response: Check the file specified as the database page shadow file. It may be that there is not enough space for the file. If enough space is available, check the filesystem, drive, or disk that it resides on for an indication of the error. Once the error preventing the server from writing to the page shadow file has been resolved, restart the server. ANR0292W Database page shadow file file name does not exist.
Explanation: 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
Explanation: The server attempted to use the page shadow file referenced but was unable to open the file. The file does not exist. System Action: The server will continue to operate and will attempt to create this as a new database page shadow file. User Response: None.
Chapter 3. Common and Platform Specfic Messages
25
ANR0300I ANR0314W
ANR0300I Recovery log format started; assigned capacity count megabytes. ANR0307I Recovery log extend in progress; count megabytes of count formatted.
Explanation: Initial formatting of the server recovery log has started. System Action: The log is formatted for use by the server. User Response: None. ANR0301I Recovery log format in progress; count megabytes of count.
Explanation: As a result of an EXTEND LOG command, the additional recovery log pages are being formatted. System Action: Formatting continues. User Response: None. ANR0309I Recovery log extend terminated process canceled.
Explanation: The amount of the server recovery log shown has been successfully formatted. System Action: Formatting continues. User Response: None. ANR0302I Recovery log formatting took mseconds milliseconds.
Explanation: The process started as a result of an EXTEND LOG command and has been canceled. System Action: The EXTEND command is ended. User Response: None. ANR0311I Recovery log reduce in progress; count megabytes of count moved.
Explanation: Formatting of the recovery log has completed and took the number of milliseconds shown. System Action: None. User Response: None. ANR0303I Format rate: rate pages/second.
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. User Response: None. ANR0313I Recovery log reduce terminated process canceled.
Explanation: During formatting, the formatter processed the number of pages indicated each second. System Action: None. User Response: None. ANR0304I Page service time: rate ms.
Explanation: The process started as a result of a REDUCE LOG command and has been canceled. System Action: The REDUCE command is ended. User Response: None. ANR0314W Recovery log usage exceeds utilization percentage % of its assigned capacity.
Explanation: During formatting, the formatter required the number of milliseconds indicated to process each page. System Action: None. User Response: None. ANR0305I Recovery log format complete.
Explanation: This message is issued to notify the administrator that the server recovery log utilization exceeds 90% or more of its assigned capacity. System Action: Server operation continues. 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
Explanation: Formatting of the server recovery log completed successfully. System Action: None. User Response: None. ANR0306I Recovery log volume mount in progress.
Explanation: During restart, the server is mounting required recovery log volumes. System Action: None. User Response: None.
26
IBM Tivoli Storage Manager: Messages
ANR0320W ANR0354I
lower the database backup trigger if one is defined Refer to the DEFINE DBBACKUPTRIGGER or UPDATE DBBACKUPTRIGGER commands. ANR0320W Storage agent storage agent is not able to use device class device class for storage pool storagepool for LAN-Free data movement operations. If this was a no-query restore operation, the data was not restored by the storage agent using LAN-Free data transfer. If the client node is allowed to read data over the LAN, the data was restored over the LAN. If the operation failed because the client node is not allowed to read data over the LAN, consider updating the DATAREADPATH setting for this node by using the UPDATE NODE command. If this was an operation performed by an agent node with proxy node authority to a target node, the session failed with a protocol error. The operation was attempted by a version 5.3 or higher client and server, but the storage agent is not able to support this operation. To allow an agent node to perform operations for a target node, the storage agent must be upgraded to version 5.3.0 or later. ANR0350I Recovery checkpoint started.
Explanation: The storage agent referenced is not able to perform LAN-Free data movement operations using this storage pool and device class. The storage agent is back-level and is not able to support LAN-Free operations using this device class. System Action: LAN-Free data movement operations are not performed. The operations are either sent via the LAN or else proxied by the storage agent directly to the server. 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. 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: During server initialization, the process of bringing the server database back to a state of consistency has begun. System Action: None. User Response: None. ANR0351I Recovery checkpoint complete.
Explanation: During server initialization, the process of bringing the server database back to a state of consistency has completed successfully. System Action: None. User Response: None. ANR0352I Transaction recovery complete.
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
Explanation: During server initialization, the process of recovering any incomplete transactions has completed successfully. System Action: None. User Response: None. ANR0353I Recovery log analysis pass in progress.
Explanation: During server initialization, the process of analyzing the server recovery log has begun. System Action: None. User Response: None. ANR0354I Recovery log redo pass in progress.
Explanation: During server initialization, the process of committing incomplete transactions has begun. System Action: None. User Response: None.
Chapter 3. Common and Platform Specfic Messages
27
ANR0355I ANR0364W
ANR0355I Recovery log undo pass in progress. ANR0361E Database initialization failed: error initializing database page allocator.
Explanation: During server initialization, the process of rolling back incomplete transactions has begun. System Action: None. User Response: None. ANR0356I Recovery log compression started.
Explanation: During server initialization, the server database initialization fails because the page allocator cannot be started. System Action: Initialization fails. User Response: Contact your service representative. ANR0362W Database usage exceeds utilization percentage % of its assigned capacity.
Explanation: The process of removing unneeded data from the server recovery log has begun. System Action: None. User Response: None. ANR0357I Recovery log compression ended.
Explanation: This message is issued to notify the administrator that the server database utilization exceeds 80% or more of its assigned capacity. System Action: Server operation continues. User Response: Depending upon the size of your database, add database volumes, or extend the database, or both, before it fills completely. The server expiration process may also free up database space making it available to other server processes. Refer to the EXPIRE INVENTORY, DEFINE DBVOL, and EXTEND DB commands for more information on these operations. ANR0363I Database was automatically upgraded to the server program level.
Explanation: The process of removing unneeded data from the server recovery log has completed. System Action: None. User Response: None. ANR0358E Database initialization failed: sufficient memory is not available.
Explanation: During server initialization, the server database fails initialization because 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: This message is issued to notify the 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. System Action: Server operation continues. 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.
Explanation: During server initialization, the server database initialization fails because the required restart record cannot be read. System Action: Initialization fails. User Response: Contact your service representative. ANR0360E Database initialization failed: database size mismatch; LVM size = size, expected size = size.
Explanation: During server initialization, the server database initialization fails because the size of the database does not match its prior size. System Action: Initialization fails. User Response: Contact your service representative.
Explanation: This message is issued to notify the administrator that the server has detected a zero bit mismatch error during a RESTORE DB process. The recovery process is the database must be restored with a process that includes a DSMSERV FORMAT. Either the data base volumes must be formatted then a DSMSERV RESTORE DB performed from a data base backup that does not have this problem, or a DSMSERV UNLOADDB followed by the formatting, then a DSMSERV LOADDB. Do not use DSMSERV DUMPDB on the data base for this recovery. System Action: Server RESTORE DB continues. User Response: Perform one of the data base recovery
28
IBM Tivoli Storage Manager: Messages
ANR0379W ANR0385I
actions after the RESTORE DB completes. 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. System Action: Server operation continues. User Response: The QUERY DB command (FORMAT=DETAILED) can be used to to display the current values for the buffer pool statistics. ANR0382I The database maximum utilization statistic was successfully reset.
Explanation: The server detected a deadlock situation between a number of processes attempting to access database information. A lock request for one of the processes will be denied to resolve the database deadlock. When the server processes encounter a database deadlock, they usually try to run the function that was in progress when the deadlock was encountered again. Not all process can explicitly try an operation again. For example, migration and reclamation will eventually try again. However, something like a delete volume run in a macro will only be tried again if the delete command is reissued either in the macro or the command line. System Action: A lock request fails for one of the deadlocked processes. Server operation continues. User Response: If a process can 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: The database maximum utilization statistic has been reset by the RESET DBMAXUTILIZATION command to the current utilization. System Action: Server operation continues. User Response: The QUERY DB command (FORMAT=DETAILED) can be used to 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 the RESET LOGMAXUTILIZATION command to the current utilization. System Action: Server operation continues. 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. System Action: Server operation continues. User Response: The QUERY LOG command (FORMAT=DETAILED) can be used to display the current value for recovery log consumption. ANR0385I Could not free sufficient buffers to reach reduced BUFPoolsize.
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: 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. User Response: None.
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.
Chapter 3. Common and Platform Specfic Messages
29
ANR0386I ANR0392I
ANR0386I The BUFPoolsize has been changed to buffer pool size. 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 BUFPoolsize option has been changed to the indicated value. System Action: Server operation continues. User Response: None. 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 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 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. 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 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. System Action: None. 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 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 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. System Action: None. 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
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.
30
IBM Tivoli Storage Manager: Messages
ANR0393I ANR0399I
System Action: None. 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. ANR0396W Management class management class with destination storage pool for operation type operations is not lanfree capable for node node name using storage agent storage agent because no online paths are available.
Explanation: The storage pool is not capable of lanfree data transfer operations for this node name using this storage agent. System Action: None. 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 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. ANR0397I Session session number for node agent_node has begun a proxy session for node target_node.
Explanation: The storage pool is capable of lanfree data transfer operations for this node name using this storage agent. System Action: None. User Response: None. ANR0394W Management class management class with destination storage pool for operation type 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. System Action: None. 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 Management class management class with destination storage pool for operation type operations is not lanfree capable for node node name using storage agent storage agent because this destination is configured for simultaneous write.
Explanation: A client session has begun proxy operations. System Action: The server granted a proxy session to a client node. User Response: None. ANR0398W Session session number for node agent_node has failed to begin a proxy session for node target_node.
Explanation: The storage pool is not capable of lanfree data transfer operations for this node name using this 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. System Action: None. 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.
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. User Response: None. ANR0399I Session session number for node 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
Chapter 3. Common and Platform Specfic Messages
31
ANR0400I ANR0408I
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. User Response: None. ANR0400I Session session number started for node node name (client platform) (communication method). ANR0404I Session session number ended for node node name (client platform) (WDSF client).
Explanation: A WDSF client session has completed normally. System Action: Server operation continues. User Response: None. ANR0405I Session session number ended for administrator administrator ID (client platform).
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. User Response: None.
Explanation: An administrative client session has completed normally. System Action: Server operation continues. User Response: None. ANR0406I Session session number started for node node name (client platform) (communication method communication address).
ANR0401I
Session session number started 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 this session are included in the message. System Action: The server begins a communications session to service the client node. User Response: None.
Explanation: A new client session has been initiated by the specified node. The session number, client platform type, communication method and address used by this session are included in the message. System Action: The server begins a communications session to service the client node. User Response: None. ANR0407I Session session number started for administrator administrator ID (administrators platform) (communication method communication address).
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. System Action: The server begins a communications session to service the administrator client. User Response: None.
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. System Action: The server begins a communications session to service the administrator client. User Response: None. ANR0408I Session session number started for server server name (servers platform) (communication method) for purpose.
ANR0403I
Session session number ended for node node name (client platform).
Explanation: A client session has completed normally. System Action: Server operation continues. User Response: None.
Explanation: A new server session has been initiated by the specified server for the specified purpose. The session number, servers platform type and communication method used by this session are included in the message. System Action: The server begins a communications session to service the administrator client. User Response: None.
32
IBM Tivoli Storage Manager: Messages
ANR0409I ANR0418W
ANR0409I Session session number ended for server server name (client platform). ANR0414I Session session number for node node name is restoring backup set: node node name, set filespace name.
Explanation: A server has completed normally. System Action: Server operation continues. User Response: None. ANR0410E EXPORT operation to server server name rejected - administrator administrator is not authorized to perform the import operation on the target server.
Explanation: This message logs information about a backup set restored by a node. System Action: Server operation continues. User Response: None. ANR0415I Session session number proxied by storage agent name started for node node name.
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. System Action: Server operation continues. User Response: None.
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. System Action: Server operation continues. User Response: None. ANR0416W Session session number for node node name not allowed to operation using path data transfer path.
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 session attempted this operation using the specified data transfer path. This operation is not permitted for this client. System Action: Server operation continues. 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 Session session number for node node 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. System Action: Server operation continues. User Response: None. ANR0412I Session session number for 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. System Action: Server operation continues. User Response: None. ANR0413I Session session number for administrator administrator name logged in as node node name is restoring backup set: node node name, set filespace name.
Explanation: This session attempted an operation that needed a data transfer path that this node is not allowed to use. System Action: This client session terminates. User Response: Refer to the ANR0416W message that was issued for this client session to determine which operation and data transfer path was attempted. ANR0418W Session session number for administrator administrator name (client platform) is refused because an incorrect password was submitted.
Explanation: This message logs information about a backup set restored by an administrator logged in for a node. System Action: Server operation continues. User Response: None.
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.
Chapter 3. Common and Platform Specfic Messages
33
ANR0419W ANR0425W
System Action: The server will continue to deny access attempts by this client until a valid password is submitted. User Response: Enter the proper password. If you have forgotten the password, contact an authorized administrator, who can assign a new password using the UPDATE ADMIN command. ANR0419W Administrative client userid administrative ID cannot be used when authentication is on. 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. ANR0423W Session session number for administrator administrator ID (client platform) refused administrator name not registered.
Explanation: The server refuses a request for a client (administrative) session because the user ID specified cannot be used when authentication of IDs is in effect. SERVER_CONSOLE is an administrative ID that has this restriction. System Action: Server operation continues. User Response: Use an administrative ID that was registered for this server and that has a password. ANR0420W Session session number for node node name (client platform) refused - server disabled for user access.
Explanation: The server refuses a request to start an administrative session because the administrator name is not registered in the server database. System Action: Server operation continues. User Response: Register the administrator name with the server before establishing a session. An authorized administrator must use the REGISTER ADMIN command to register the administrator with the server. ANR0424W Session session number for node node name (client platform) refused - invalid password submitted.
Explanation: The server refuses a request for a client (backup-archive) session because the server is currently disabled for client access. System Action: Server operation continues. 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 Session session number for node node name (client platform) refused - sign-on protocol violation.
Explanation: The server refuses a request to start a client session because an invalid password has been submitted by the client during sign-on processing. The server will continue to deny access attempts by this client until a valid password is submitted. System Action: Server operation continues. User Response: Enter the proper password. If the password has been forgotten by the user, an authorized administrator can assign a new password by using the UPDATE NODE command. ANR0425W Session session number for node node name (client platform) refused - password has expired.
Explanation: The server refuses a request for a client session because sign-on protocol has been violated. System Action: Server operation continues. 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 Session session number for node node name (client platform) refused - node name not registered.
Explanation: The server refuses the specified session because the administrator or client nodes password has expired. System Action: Server operation continues. 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 or UPDATE ADMIN command.
Explanation: The server refuses a request to start a client session because the client node name is not registered in the server database. System Action: Server operation continues.
34
IBM Tivoli Storage Manager: Messages
ANR0426W ANR0433W
ANR0426W Session session number for node node name (client platform) refused - open registration not permitted. ANR0430W Session session number for node node name (client platform) refused - node name is locked.
Explanation: The server refuses a client session because an open registration action has been attempted and the server is running with CLOSED registration. System Action: Server operation continues. User Response: Ask an authorized administrator to submit the request using the REGISTER NODE or REGISTER ADMIN command. ANR0427W Session session number for node node name (client platform) refused - server version is down-level with this client.
Explanation: The server refuses the specified client session because the node is locked from server access (with the LOCK NODE command). System Action: Server operation continues. 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 a client session because the client program version level is newer than that supported by the server program. System Action: Server operation continues. User Response: Apply service to the server program to make it compatible with the newer client program, or use an older client program to contact the server. ANR0428W Session session number for node node name (client platform) refused - client is down-level with this server version.
Explanation: The server refuses the specified administrative session because the administrator is locked from server access (with the LOCK ADMIN command). System Action: Server operation continues. 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 Session session number for node node name (client platform) refused insufficient memory.
Explanation: The server refuses a client session because the client program version level is older than that supported by the server program. For certain problems (such as the compression fix), once a node connects to the server using the newer client, the server records this fact and will not let this node back off this client version to a version that does not include the fix. System Action: Server operation continues. User Response: Apply service to the client program to make it compatible with the newer server program. ANR0429W Session session number for node node name (client platform) refused - maximum server sessions (max sessions allowed) exceeded.
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. 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. ANR0433W Session session number for node or administrator ID (client platform) refused insufficient recovery log space.
Explanation: The server refuses the specified client or administrative session because the maximum number of concurrent client sessions has been exceeded. System Action: Server operation continues. 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.
Explanation: The server ends the specified client or administrative session because sufficient log space is not available to complete a database transaction. System Action: The server ends the session and continues operation. User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes using the DEFINE LOGVOLUME command, and extend the size of the log using the EXTEND LOG command.
Chapter 3. Common and Platform Specfic Messages
35
ANR0434W ANR0441W
ANR0434W Session session number for node or administrator ID (client platform) refused insufficient database space. 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. ANR0438W 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 ends the specified client or administrative session because sufficient database space is not available to complete a database transaction. System Action: The server ends the session and continues operation. User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes using the DEFINE DBVOLUME command, and extend the size of the database using the EXTEND DB command. ANR0435W Session session number for node node name (client platform) refused - internal error detected.
Explanation: The server refuses a client archive 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. ANR0439W Session session number backup operation for client client node name (client platform) has been denied - Server is not in compliance with license terms.
Explanation: The server ends the specified session because an internal logic error is detected. System Action: The server ends the session and continues operation. 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.
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 Protocol error on session session number for node client node name (client platform) invalid verb header received.
Explanation: The server refuses a client session 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. System Action: Server operation continues. 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 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 service representative. ANR0441W Protocol error on session session number for node client node name (client platform) invalid data length received.
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.
Explanation: The server detects a protocol error on the specified session because an invalid verb length has
36
IBM Tivoli Storage Manager: Messages
ANR0442W ANR0448W
been received from 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 service representative. ANR0442W Protocol error on session session number for node client node name (client platform) excessively large verb received. ANR0445W Protocol error on session session number for node client node name (client platform) maximum group transaction size exceeded.
Explanation: The server detects a protocol error on the specified session because the client has attempted to group more than the maximum database update operations in a single database transaction. 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 service representative. 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 server detects a protocol error on the specified session because an invalid verb length has been received from 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 service representative. ANR0443W Protocol error on session session number for node client node name (client platform) invalid field name field found in verb name verb (offset offset position).
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. 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 Session session number space management migration operation for client client node name (client platform) has been denied - Server is not in compliance with license terms.
Explanation: The server detects a protocol error on the specified session because an invalid field has been found in a verb sent from the client node. 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 service representative. ANR0444W Protocol error on session session number for node client node name (client platform) out-of-sequence verb (type verb name) received.
Explanation: The server detects a protocol error on the specified session because a verb has been received that does not adhere to the client-server exchange sequence. System Action: The server ends the client session. 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.
Explanation: The server refuses a client space management migration 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, archive, or space-managed file migration. User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance. ANR0448W Session session number space management migration operation for client client node name (client platform) has been denied - server is not licensed for space management support.
Explanation: The server refuses a client space management migration operation because the server is not licensed to support space-managed clients.
Chapter 3. Common and Platform Specfic Messages
37
ANR0449W ANR0454E
System Action: Server operation continues. 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 Session session number space management migration operation for client client node name (client platform) is in violation of server license terms server is not licensed for space management support. ANR0452W Session for server server name refused server name not defined for server to server communications.
Explanation: The server refuses a request to start a 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. System Action: Server operation continues. User Response: Register the server names on both 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. ANR0453W Server to server session refused - no password defined.
Explanation: The server warns about a client space management migration operation because the server is not licensed to support space-managed clients. System Action: Server operation continues. 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. ANR0450W Session session number for server server name (client platform) refused - server name not defined for server to server communications.
Explanation: The server to server session cannot be initiated because no server password has been defined for this server. System Action: Server operation continues. 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 refuses a request to start a server session because the requesting server name is not defined in the server database, or the requesting server definition does not have a SERVERPASSWORD. System Action: Server operation continues. 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. ANR0451W Session session number for server server name (server platform) refused - invalid password submitted.
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. 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
Explanation: The server refuses a request to start a 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. System Action: Server operation continues. 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.
38
IBM Tivoli Storage Manager: Messages
ANR0455W ANR0462W
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. ANR0459W Signon for administrator administrator name refused - invalid administrator name and/or password submitted.
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. System Action: The server ends the client session. User Response: Enter commands through the SNMP administrative interface which are macros defined on the server. ANR0456W Session rejected for server name server name at High level address Low level address does not match.
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. System Action: Server operation continues. 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. 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. 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. ANR0457W Session for server server name refused crossdefine is not allowed on this server.
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: Server operation continues. User Response: The client program user must specify a different node name for the client in the client options file. ANR0461W Open registration failed for session session number for node node name (client platform) - policy domain STANDARD does not exist.
Explanation: The server refuses a request to start a 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. System Action: Server operation continues. 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 server refuses a client session during 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. System Action: Server operation continues. 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 Open registration failed for session session number for node node name (client platform) - invalid node name.
Explanation: The storage agent attempted to contact a Database Server, but the server contacted was not at the correct level. System Action: The Storage Agent terminates. User Response: Specify a correct Database Server in the devconfig file for the Storage Agent.
Explanation: The server refuses a client session during open registration because the node name specified by the client is not valid.
Chapter 3. Common and Platform Specfic Messages
39
ANR0463W ANR0474W
System Action: Server operation continues. 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 Open registration failed for session session number for node node name (client platform) - invalid password. ANR0466E The SETSTORAGESERVER command did not complete successfully.
Explanation: The SETSTORAGESERVER command encountered an error and did not complete successfully. System Action: Storage agent operation terminates. User Response: Please review prior error messages and take the necessary corrective actions. ANR0467I The SETSTORAGESERVER command completed successfully.
Explanation: The server refuses a client session during open registration because the password name specified by the user is not valid. System Action: Server operation continues. User Response: Specify a password that uses valid characters and is less than the maximum length in size. Refer to Backup-Archive Clients Installation and Users Guide for a description of the password restrictions. ANR0464W Open registration failed for session session number for node node name (client platform) - exceeded number of nodes available under license terms.
Explanation: The SETSTORAGESERVER command has completed successfully, and the appropriate device configuration files have been updated. System Action: Storage agent operation terminates. User Response: None ANR0468E Server-to-server export and import not allowed with server server name. Export server is at version export version; import server is at version import version.
Explanation: The server detected an attempt to register more nodes than allowed by the terms of the current license. System Action: Server operation continues, but the REGISTER NODE command fails, and the node is not registered. User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance. ANR0465W Open registration failed for session session number for node node name (client platform) - policy domain STANDARD does not have an ACTIVE policy set.
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 Session session number for node node name (client platform) refused - client is not configured for archive retention protection.
Explanation: The server refuses a client session during 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. System Action: Server operation continues. 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.
Explanation: The server refuses a client session because the client is not configured for archive retention protection. System Action: Server operation continues. User Response: Either disable archive retention protection on the server or configure the client for archive retention protection. ANR0474W Session session number for administrator 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
40
IBM Tivoli Storage Manager: Messages
ANR0475W ANR0480W
port numbers are used for administrative and client sessions (controlled by the TCPPORT and TCPADMINPORT options), and option ADMINONCLIENTPORT is set to NO, administrative sessions can be started only on the port used for administrative sessions (as specified by the TCPADMINPORT option). System Action: Server operation continues. 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 Session session number for node node name (client platform) refused - node is not allowed to initiate sessions on administrative port. with the server. For example, a node id of type NAS can only sign on with a platform type of TSMNAS, all other node types cannot use this platform type. System Action: The session request is refused. The server operation continues. User Response: Verify that the Id used by a client to sign on has the proper platform type. ANR0478W Session request refused. Server is running in standalone mode.
Explanation: A client has requested a session with the server. The server is running in a mode in which it cannot start client sessions. System Action: The session request is refused. The server operation continues. 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 Session session number for server server name (server platform) terminated connection with server severed.
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. System Action: Server operation continues. 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. ANR0476W Session session number for node node name (client platform) refused - node is not allowed to initiate sessions.
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. 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 Session session number for node node name (client platform) terminated connection with client severed.
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. System Action: Server operation continues. 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.
Explanation: The specified client session is ended because the communications link has been closed by a network error or by the client program. System Action: Server operation continues. 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
Chapter 3. Common and Platform Specfic Messages
41
ANR0481W ANR0487W
ANR0481W Session session number for node node name (client platform) terminated - client did not respond within commtimeout seconds seconds. ANR0484W Session session number for node node name (client platform) terminated protocol violation detected.
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 Session session number for node node name (client platform) terminated - idle for more than idletimeout minutes minutes.
Explanation: The server ends the specified session because a communications protocol error by the client has been detected. System Action: The server ends the client session. 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. ANR0485W Session session number for node node name (client platform) terminated sufficient memory is not available.
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. 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. ANR0486W Session session number for node node name (client platform) terminated internal error detected.
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. System Action: Server operation continues. 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 Session session number for node node name (client platform) terminated - forced by administrator.
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 operation continues. User Response: Contact your service representative. ANR0487W Session session number for node node 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.
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. User Response: None.
42
IBM Tivoli Storage Manager: Messages
ANR0488W ANR0493I
ANR0488W Session session number for node node 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. ANR0490I Canceling session session number for node node name (client platform) .
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 operation continues. 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 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. System Action: The session is canceled and server operation continues. User Response: None. 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. System Action: Server operation continues. 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. ANR0493I Restore session session number canceled.
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. System Action: The session request is refused. The server operation continues. 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.
Explanation: The specified session was canceled with the CANCEL RESTORE command. System Action: The restore session is canceled and server operation continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
43
ANR0494I ANR0511I
ANR0494I Volume volume name in use. Session session number for node node name (client platform) being preempted by higher priority operation. ANR0501W Transaction failed for session session number for node node name (client platform) - invalid policy binding specified.
Explanation: When a high 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 ends a database update transaction for the specified session because an invalid management class has been specified for a file or directory object. System Action: The specified session is ended and server operation continues. User Response: Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative. ANR0502E Transaction failed for session session number for node node name (client platform) - A storage pool for the target destination is associated with a device class that has a Centera device type.
Explanation: The server cannot cancel the session specified in the CANCEL SESSION command. System Action: Server operation continues. 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 client client node name (client platform) has been denied because verb (type verb name) is not allowed when archive retention is active.
Explanation: The server ends a database update transaction for the specified session because an invalid management class has been specified. Centera device types may be used only for archive objects. System Action: The specified session is ended and server operation continues. 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. ANR0510I Session session number opened input volume volume name.
Explanation: The server refuses the specified client operation because archive retention protection is active. System Action: Server operation continues. User Response: Do not send the specified operation to the server when archive retention protection is active. ANR0500W Transaction failed for session session number for node node name (client platform) - invalid password submitted.
Explanation: The indicated session has opened the specified volume for input processing. System Action: Processing continues. User Response: None. ANR0511I Session session number opened output volume volume name.
Explanation: The server ends a password update transaction because the user has not correctly specified the current password. System Action: Server operation continues. 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.
Explanation: The indicated session has opened the specified volume for output processing. System Action: Processing continues. User Response: None.
44
IBM Tivoli Storage Manager: Messages
ANR0512I ANR0523W
ANR0512I Process process number opened input volume volume name. specified storage pool must be created by an authorized administrator. ANR0521W Transaction failed for session session number for node node name (client platform) - object excluded by size in storage pool pool name and all successor pools.
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. System Action: Processing continues. User Response: None. 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. System Action: Processing continues. User Response: None. ANR0514I Session process number closed volume volume name.
Explanation: The server ends a database update 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. System Action: The specified session is ended and server operation continues. User Response: If the client is not using compression to send files to the host, turn compression on for the client (using the UPDATE NODE command) to try and resolve the problem. Otherwise, the maximum file size for one or more of the storage pools in the storage hierarchy can be increased to accommodate the file. An authorized administrator can increase the MAXSIZE parameter by issuing the UPDATE STGPOOL command. ANR0522W Transaction failed for session session number for node node name (client platform) - no space available in storage pool pool name and all successor pools.
Explanation: The indicated session has finished using the specified volume. System Action: Processing continues. User Response: None. 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. System Action: Processing continues. User Response: None. ANR0520W Transaction failed for session session number for node node name (client platform) - storage pool pool name is not defined.
Explanation: The server ends a database update 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. System Action: The specified session is ended and server operation continues. 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 Transaction failed for session session number for node node name (client platform) - error on output storage device.
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. System Action: Server operation continues. 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
Explanation: The server ends a database update transaction for the specified client because an I/O error has been encountered by the server in writing to a device.
Chapter 3. Common and Platform Specfic Messages
45
ANR0524W ANR0530W
System Action: The specified session is ended and server operation continues. User Response: Query the activity log to find messages preceding this one that specify the failing device. Storage pool volumes can be varied offline (by using the VARY command), or the server may need to be halted to correct the hardware problem. After the problem is corrected, the client should retry the operation. ANR0524W Transaction failed for session session number for node node name (client platform) - data transfer interrupted. ANR0527W Transaction failed for session session number for node node name (client platform) - sufficient database space is not available.
Explanation: The server ends a database update transaction for the specified session because sufficient database space is not available on the server. System Action: The server ends the specified session and server operation continues. User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used. ANR0528W Transaction failed for session session number for node node name (client platform) - thread resource not available.
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. System Action: The session is canceled and server operation continues. User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the client operation again if the problem can be resolved. ANR0525W Transaction failed for session session number for node node name (client platform) - storage media inaccessible.
Explanation: The server ends a database update transaction for the specified session because sufficient memory is not available for starting additional processes on the server. System Action: The server ends the specified session and server operation continues. 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. ANR0529W Transaction failed for session session number for node node name (client platform) - insufficient memory.
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. User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The 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 Transaction failed for session session number for node node name (client platform) - sufficient recovery log space is not available.
Explanation: The server ends a database update transaction for the specified session because sufficient memory is not available on the server. System Action: The server ends the specified session and server operation continues. 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. ANR0530W Transaction failed for session session number for node node name (client platform) - internal server error detected.
Explanation: The server ends a database update transaction for the specified session because sufficient log space is not available on the server. System Action: The server ends the specified session and server operation continues. User Response: An authorized administrator can issue 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.
Explanation: The server ends a database update transaction for the specified session because an internal logic error is detected. System Action: The server ends the specified session and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the
46
IBM Tivoli Storage Manager: Messages
ANR0531W ANR0535W
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 Transaction failed for session session number for node node name (client platform) - invalid file space identifier specified by client. ANR0534W Transaction failed for session session number for node node name (client platform) - size estimate exceeded and server is unable to obtain additional space in storage pool pool name.
Explanation: The server ends a database update 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 server operation continues. 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 DiagnosticID: Transaction transaction ID was aborted for session session number for node node name (client platform).
Explanation: The server ends a database update 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: The specified session is ended and server operation continues. If pool name is a random access storage pool with caching enabled, it is also possible that additional space can be made available in this storage pool by eliminating cached files. When the server allocates space based on the size estimate provided by the client, it frees space occupied by cached files if this space is needed to obtain the estimated space. However, if the server later determines that the file size estimate was too low, it attempts to obtain additional space that is not utilized, but does not delete cached files to do so. If the client sending the data has the option COMPRESSALWAYS YES set, it is possible that a file grew during the compression operation and when the client sent it to the server it exceeded the space available in storage pool pool name. User Response: This message may indicate that there is no additional space in pool name. The following are possible circumventions: An authorized administrator can issue the DEFINE VOLUME command to add storage to this pool. If the suspected cause of the failure is that pool name is a DISK storage pool and that space in use by cached files was not freed, turn off caching for the storage pool and issue the MOVE DATA command for the volumes in pool pool name. If the suspected cause of the failure is that a file grew in size during compression on the client, another possible circumvention is to set the COMPRESSALWAYS option in the client options file to NO and retry the operation. This may allow the client to accurately report the file size and possibly avoid the out of space condition in the storage pool. ANR0535W Transaction failed for session session number for node node name (client platform) - insufficient mount points available to satisfy the request.
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. System Action: The activity that generated this error fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR0533W Transaction failed for session session 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. System Action: The server ends the specified session and server operation continues. 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.
Explanation: The server was unable to allocate sufficient mount points to process the transaction. System Action: The operation is ended and server operation continues. User Response: If necessary, make more mount points available.
Chapter 3. Common and Platform Specfic Messages
47
ANR0536W ANR0544W
ANR0536W Transaction failed for session session number for node node name (client platform) - downlevel client does not support format of stored files. ANR0541W Retrieve or restore failed for session session number for node node name (client platform) - error on input storage device.
Explanation: A client attempts to perform an operation involving files that are stored in a format that is not supported by that client level. System Action: The operation is ended and server operation continues. User Response: Upgrade the client to a later level. ANR0537E Transaction failed for session session number for node node name (client platform) - filespace name cannot be renamed from or to a unicode name.
Explanation: The server ends a client retrieval or restore operation for the specified session because an I/O error has been encountered by the server in reading from a device. System Action: The server ends the specified session and server operation continues. User Response: Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down by using the HALT command to correct the hardware problem. After the problem is corrected, the client may try the operation again. ANR0542W Retrieve or restore failed for session session number for node node name (client platform) - storage media inaccessible.
Explanation: The server ends a database update transaction for the specified session because a file space was attempted to be renamed to or from unicode. System Action: The server ends the specified transaction and server operation continues. User Response: Do not attempt to rename a unicode file space to a non-unicode name or a non-unicode file space to a unicode name. ANR0538I A resource waiter has been aborted.
Explanation: The server ends a client retrieval or restore operation for the specified session because a needed storage pool volume has been varied offline or the storage pool is unavailable. System Action: The server ends the specified session and server operation continues. 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 Retrieve or restore failed for session session number for node node name (client platform) - data transfer interrupted.
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. ANR0540W Retrieve or restore failed for session session number for node node name (client platform) - data integrity error detected.
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. System Action: The session is canceled and server operation continues. User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the client operation again, if the problem can be resolved. ANR0544W Retrieve or restore failed for session session number for node node name (client platform) - thread resource not available.
Explanation: The server ends a file retrieval operation for the specified session because an internal database integrity error has been encountered on the server. System Action: The server ends the specified session and continues operation. User Response: Contact your service representative.
Explanation: The server ends a file retrieval or restore operation for the specified session because sufficient
48
IBM Tivoli Storage Manager: Messages
ANR0545W ANR0551E
memory is not available for starting additional processes on the server. System Action: The server ends the specified session and server operation continues. 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. ANR0545W Retrieve or restore failed for session session number for node node name (client platform) - insufficient memory. ANR0548W Retrieve or restore failed for session session number for node node name (client platform) processing file space filespace filespace id for file file name stored as storage repository - 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. System Action: The server ends the specified session and continues operation. 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. ANR0549W Transaction failed for session session number for node node name (client platform) - no existing restore session found.
Explanation: The server ends a file retrieval or restore operation for the specified session because sufficient memory is not available on the server. System Action: The server ends the specified session and server operation continues. 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. ANR0546W Retrieve or restore failed for session session number for node node name (client platform) - internal server error detected.
Explanation: A client attempted to start an additional no query restore session to increase restore throughput, but the original restore session was not found. System Action: The operation is ended and server operation continues. 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. ANR0550E The client operation failed for session session number for node node name (client platform) - see previous error messages.
Explanation: The server ends a file retrieval or restore operation for the specified session because an internal logic error is detected in the server program. System Action: The server ends the specified session and continues operation. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0547E Invalid data was encountered in the command processor output stream: output formatting terminated for the last command entered.
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. System Action: The operation is ended and server operation continues. 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 session number for node node name (client platform) - lock conflict.
Explanation: The server console session encounters an error in formatting output from a command. System Action: The command output is discarded and server operation continues. 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.
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.
Chapter 3. Common and Platform Specfic Messages
49
ANR0552E ANR0558W
System Action: The server does not process the command. User Response: Try the command again at a later time. ANR0552E Client operation failed for session session number for node node name (client platform) - destination storage pool storage pool was skipped. ANR0555E command name: The parameter name parameter cannot be specified when the TOSERVER parameter is specified.
Explanation: The command failed because the TOSERVER parameter was not specified. System Action: The command fails and server operation continues. 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: The indicated client operation failed because the destination storage pool was skipped. A storage pool may be skipped because it does not have enough available space, or because it has a MAXSIZE value that is less than the size of the object to be inserted. System Action: The operation fails. 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 Client operation failed for session session number - Administrator administrator name does not have adequate authority over node node name.
Explanation: When importing files and merging them into existing file spaces, the DATES=RELATIVE parameter value cannnot be specified. System Action: The command fails and server operation continues. 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 particular platform. ANR0557I Import command: An invalid export record (version version, copy type copy type, object type object type) was found.
Explanation: The specified administrator does not have the proper authority necessary to perform this operation on the specified node. System Action: The server does not perform the query. User Response: Issue the command from a properly authorized administrator ID, or contact the system administrator to have additional authority granted to the current administrator ID. ANR0554E command name: The parameter name parameter is only valid if the TOSERVER parameter is 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. System Action: Server operation continues. User Response: Issue QUERY ACTLOG to determine the source of the error. ANR0558W Import processing did not create a proxynode association for nodes node_id_target and node_id_agent.
Explanation: The command failed because the TOSERVER parameter was not specified. System Action: The command fails and server operation continues. 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.
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. User Response: Verify that both nodes were imported properly and issue the import command again. Or, use the GRANT PROXYNODE command to manually
50
IBM Tivoli Storage Manager: Messages
ANR0559E ANR0570E
create the proxynode association. ANR0559E Too many domains are specified on the EXPORT NODE command. inventory expiration processes are running; these processes can delete data storage files during retrieval. Reissue the restore or retrieve operation and specify a different file version. ANR0567W Retrieve or restored failed for session session number for node node name (client platform) - insufficient mount points available to satisfy the request.
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 was unable to allocate sufficient mount points to process the retrieve or restore operation. System Action: The operation is ended and server operation continues. User Response: If necessary, make more mount points available. ANR0568W Session session number for admin admin name (client platform) terminated connection with client severed.
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. ANR0565W Retrieve or restore failed for session session number for node node name (client platform). The storage volume volume name is inaccessible.
Explanation: The specified admin session is ended because the communications link has been closed by a network error or by the client program. System Action: Server operation continues. 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: The server ends a client retrieval or restore operation for the specified session because a needed storage pool volume has been varied offline. System Action: The server ends the specified session and server operation continues. User Response: Use the VARY ONLINE command to vary offline storage volumes online, and make them available to client nodes for file storage. ANR0566W Retrieve or restore failed for session session number for node node name (client platform) - file was deleted from data storage during retrieval.
Explanation: An error occurred. The object for node name, identified by type, file space and object name was not processed. System Action: Server action is defined by the error that occurred. User Response: Issue QUERY ACTLOG to determine 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: The server ends a file retrieval operation for the specified session because the file has been deleted from data storage by another process before retrieval is complete. System Action: The server ends the specified session and continues operation. User Response: Contact your administrator to find out if DELETE FILESPACE, DELETE VOLUME, or
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
Chapter 3. Common and Platform Specfic Messages
51
ANR0571E ANR0576E
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 Export command: Invalid value for PERUNITS parameter detected while exporting administrative schedule schedule name - default or existing value is used during import. User Response: None. 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 schedule schedule name. System Action: Processing of the command continues. If a later command is issued that causes the data to be imported, the default or existing values are used for DURATION, DURUNITS, PERIOD, and PERUNITS. User Response: If the data is imported with a later command, verify that the correct values for DURATION, DURUNITS, PERIOD, and PERUNITS are used for this schedule. ANR0575E Import command: Invalid value for DAYOFWEEK parameter in exported data for administrative schedule schedule name.
Explanation: During processing of command export command, an invalid value is encountered for the PERUNITS parameter for administrative schedule schedule name. System Action: Export processing continues, but the 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 schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the PERUNITS value after import processing has been performed. ANR0572E Export command: Invalid value for DAYOFWEEK parameter detected while exporting administrative schedule schedule name - default or existing value is used during import.
Explanation: During preview processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name. System Action: Processing of the command continues. If a later command is issued that causes the data to be imported, the default or existing DAYOFWEEK value is used. User Response: If the data is imported with a later command, verify that the correct DAYOFWEEK value is used for this schedule. ANR0576E Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data - administrative schedule schedule name defined with default values for DURATION, DURUNITS, PERIOD, and PERUNITS.
Explanation: During processing of command export command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name. System Action: Export processing continues, but the exported data contains an unknown DAYOFWEEK value for this schedule. If this data is imported, the 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 after import processing has been performed. ANR0573I Export/import command: Processing administrative schedule schedule name.
Explanation: During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for administrative schedule schedule name. System Action: Processing of the command continues, by using the default values for DURATION, DURUNITS, PERIOD, and PERUNITS. User Response: Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary.
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.
52
IBM Tivoli Storage Manager: Messages
ANR0577E ANR0582E
ANR0577E Import command: Invalid value for DAYOFWEEK parameter in exported data - administrative schedule schedule name defined with default DAYOFWEEK value. ANR0580E Export command: Invalid value for 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.
Explanation: During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name. System Action: Processing of the command continues, by using the default DAYOFWEEK value for this schedule. User Response: Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary. ANR0578E Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data - existing values for DURATION, DURUNITS PERIOD, and PERUNITS for administrative schedule schedule name were not updated.
Explanation: During processing of command export command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name in domain domain name, policy set policy set name. System Action: Export processing continues, but the 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. Alternatively, use the export data with the unknown value, and check and update the SPACEMGTECHNIQUE value after import processing has been performed. ANR0581E Export command: Invalid value for MIGREQUIRESBKUP 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.
Explanation: During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for administrative schedule schedule name. System Action: Processing of the command continues, by using the existing values for DURATION, DURUNITS, PERIOD, and PERUNITS. User Response: Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary. ANR0579E Import command: Invalid value for DAYOFWEEK parameter in exported data - existing DAYOFWEEK value for administrative schedule schedule name was not updated.
Explanation: During processing of command export command, an invalid value is encountered for the MIGREQUIRESBKUP parameter for management class management class name in domain domain name, policy set policy set name. System Action: Export processing continues, but the 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. Alternatively, use the export data with the unknown value, and check and update the MIGREQUIRESBKUP value after import processing has been performed. ANR0582E Import command: Invalid value for SPACEMGTECHNIQUE parameter in exported data for management class management class name in domain domain name, set policy set name.
Explanation: During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name. System Action: Processing of the command continues, 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.
Explanation: During preview processing of command import command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name, in policy domain domain name, policy set policy set name. System Action: Processing of the command continues.
Chapter 3. Common and Platform Specfic Messages
53
ANR0583E ANR0588E
If a later command is issued that causes the data to be imported, the default or existing SPACEMGTECHNIQUE value is used. User Response: None. If the data is imported with a later command, verify that the correct SPACEMGTECHNIQUE value is used for this management class. ANR0583E Import command: Invalid value for SPACEMGTECHNIQUE parameter in exported data - management class management class name in domain domain name, set policy set name defined with default SPACEMGTECHNIQUE value. 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 MIGREQUIRESBKUP value is used for this management class. ANR0586E Import command: Invalid value for MIGREQUIRESBKUP parameter in exported data - management class management class name in domain domain name, set policy set name defined with default MIGREQUIRESBKUP value.
Explanation: During processing of command import command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name, in policy domain domain name, policy set policy set name. System Action: Processing of the command continues, 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. ANR0584E Import command: Invalid value for SPACEMGTECHNIQUE parameter in exported data - SPACEMGTECHNIQUE value for management class management class name in domain domain name, set policy set name was not updated.
Explanation: During processing of command import command, an invalid value is encountered for the MIGREQUIRESBKUP parameter for management class management class name, in policy domain domain name, policy set policy set name. System Action: Processing of the command continues, by using the default MIGREQUIRESBKUP value for this management class. User Response: Verify that the correct MIGREQUIRESBKUP value has been used for this management class. Update this value, if necessary. ANR0587E Import command: Invalid value for MIGREQUIRESBKUP parameter in exported data - MIGREQUIRESBKUP value for management class management class name in domain domain name, set policy set name was not updated.
Explanation: During processing of command import command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name, in policy domain domain name, policy set policy set name. System Action: Processing of the command continues, by using the existing 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. ANR0585E Import command: Invalid value for MIGREQUIRESBKUP parameter in exported data for management class management class name in domain domain name, set policy set name.
Explanation: During processing of command import command, an invalid value is encountered for the MIGREQUIRESBKUP parameter. System Action: Processing of the command continues, by using the existing MIGREQUIRESBKUP value for this management class. User Response: Verify that the correct MIGREQUIRESBKUP parameter has been used for this management class. Update this value, if necessary. ANR0588E Import command: Server is down-level compared to export data version version number.
Explanation: An attempt is made to import data to a down-level server. The server on which the import is performed must be at the same or later level than the server from which the data was exported. System Action: The import process ends and server operation continues. User Response: Import to a server that is at the same or later level than the server from which the export was performed.
Explanation: During preview processing of command import command, an invalid value is encountered for the MIGREQUIRESBKUP parameter for management class management class name, in policy domain domain name, policy set policy set name. System Action: Processing of the command continues.
54
IBM Tivoli Storage Manager: Messages
ANR0589E ANR0596W
ANR0589E Import command: Preview processing terminated abnormally - server is down-level. ANR0593E Export/import command: Invalid value for NOSPAN parameter - parameter value.
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 operation continues. User Response: Import to a server that is at the same or later level than the server from which the export was performed. ANR0590E Import command: Processing terminated abnormally - server is down-level.
Explanation: The value (parameter value) specified for the NOSPAN parameter in command export/import command is not a valid value for this parameter. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a 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 device class: NOSPAN parameter can only be used with a 3590 device class.
Explanation: Processing for the command import command ends when it is determined that the server is down-level compared to the export data. System Action: Import processing ends and server operation continues. User Response: Import to a server that is at the same or later level than the server from which the export was performed. ANR0591E Export/import command: Invalid value for FILELIST parameter - parameter value.
Explanation: The device class specified must be a 3590 device class when NOSPAN is set to True. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a 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: The value (parameter value) specified for the FILELIST parameter in command export/import command is not a valid value for this parameter. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid FILELIST parameter. For information on valid values for the FILELIST parameter for the command, refer to the Administrators Reference for your particular platform. ANR0592E Export/import command: Invalid value for table of contents parameter - parameter value.
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. System Action: Server operation continues. 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: The value (parameter value) specified for the table of contents (TOC) parameter in command export/import command is not a valid value for this parameter. System Action: The command fails and server operation continues. 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.
Explanation: While attempting to import a spaced-managed object, the server discovers that the object already exists. The space-managed object is skipped. System Action: Server operation continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
55
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. 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. User Response: None. ANR0601I Export command: No policy sets found in policy domain domain name for exporting.
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.
Explanation: The background export process does not find any policy sets defined in domains matching domain name. System Action: The export process continues and no policy sets are exported from the domain. User Response: None. ANR0602I Export command: No management classes were found in policy domain domain name for exporting.
Explanation: During import processing, the server 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: The background export process does not find any management classes defined in policy domains matching domain name. System Action: The export process continues and no management classes are exported from the domain. User Response: None. ANR0603I Export command: No copy groups were found in policy domain domain name for exporting.
Explanation: The background export process does not find any copy groups defined in policy domains matching domain name. System Action: The export process continues and no copy groups are exported from the domain. User Response: None. ANR0604I Export command: No schedules were found in policy domain domain name for exporting.
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.
Explanation: The background export process does not find any schedules defined for policy domains matching domain name. System Action: The export process continues and no schedules are exported for the domain. User Response: None.
56
IBM Tivoli Storage Manager: Messages
ANR0605I ANR0614I
ANR0605I Export command: No schedule associations were found in policy domain domain name for exporting. ANR0610I Command started by administrator name as process process ID.
Explanation: The background export process does not find any schedule node associations defined for policy domains matching domain name. System Action: The export process continues and no schedule associations are exported for the domain. User Response: None. ANR0606I Export command: No node definitions were found for exporting.
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. System Action: Server operation continues. 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 Command started by administrator name as process process ID has ended.
Explanation: The background export process does not find any node definitions to export as specified in the command export command. System Action: The export process continues. User Response: None. ANR0607I Export command: No administrator definitions were found for exporting.
Explanation: The background process to service the command command by administrator administrator name has completed processing. System Action: The specified process ends, and server operation continues. User Response: None. ANR0612I Import command: Reading EXPORT SERVER data from server server name exported export date export time.
Explanation: The background export process does not find any administrator definitions to export as specified in the command export command. System Action: The export process continues. User Response: None. ANR0608I Export command: No file spaces were found for exporting.
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. User Response: None. ANR0613I Import command: Reading EXPORT POLICY data from server server name exported export date export time.
Explanation: The background export process does not find any file space definitions to export as specified in the command export command. System Action: The export process continues. User Response: None. 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. System Action: Server operation continues. 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.
Explanation: The background import process to service the command import command is importing information exported from server server name with the EXPORT POLICY command on export date at export time. System Action: Import processing continues. User Response: None. ANR0614I Import command: Reading EXPORT ADMIN data from server server name exported export date export time.
Explanation: The background import process to service the command import command is importing information exported from server server name with the
Chapter 3. Common and Platform Specfic Messages
57
ANR0615I ANR0622I
EXPORT ADMIN command on export date at export time. System Action: Import processing continues. User Response: None. ANR0619I ANR0615I Import command: Reading EXPORT NODE data from server server name exported export date export time. Command: Processing canceled before completion. number of bytes copied, are displayed on the server console following this message. User Response: None.
Explanation: The background import process to service the command import command is importing information exported from server server name with the EXPORT NODE command on export date at export time. System Action: Import processing continues. User Response: None. ANR0616I Export/import command: Preview processing completed successfully.
Explanation: The background process to service the command command has been canceled with the CANCEL PROCESS command. System Action: Processing for the command command ends. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message. User Response: None. ANR0620I Export/import command: Copied number domain(s).
Explanation: The background export or import process to service the command export/import command in preview (Preview=Yes) mode has completed successfully. System Action: Export or import processing for the 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. User Response: None. ANR0617I Export/import command: Processing completed with status status.
Explanation: The background export or import process to service the command export/import command 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0621I Export/import command: Copied number policy sets.
Explanation: The background export or import process to service the command export/import command has completed with status status. If the status is INCOMPLETE, some files have been skipped due to errors reading or writing the file. System Action: Export or import processing for the 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. User Response: None.
Explanation: The background export or import process to service the command export/import command 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 Preview=Yes is specified in the command export/import command. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0622I Export/import command: Copied number management classes.
ANR0618I
Export/import command: Preview processing canceled before completion.
Explanation: The background export or import process to service the command export/import command in preview (Preview=Yes) mode has been canceled with the CANCEL PROCESS command. System Action: Export or import processing for the command ends. Statistics on the projected number and type of objects moved, together with the projected total
Explanation: The background export or import process to service the command export/import command copies number management class 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. System Action: Export or import processing for the
58
IBM Tivoli Storage Manager: Messages
ANR0623I ANR0630I
command completes. Server operation continues. User Response: None. ANR0627I ANR0623I Export/import command: Copied number copy groups. Export/import command: Copied filespace number file spaces archive number archive files, backup number backup files, and spacemg number space managed files. User Response: None.
Explanation: The background export or import process to service the command export/import command copies number copy group definitions from either 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0624I Export/import command: Copied number schedules.
Explanation: The background export or import process to service the command export/import command 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0629I Export/import command: Copied number bytes of data.
Explanation: The background export or import process to service the command export/import command copies number schedule definitions from either 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0625I Export/import command: Copied number administrators.
Explanation: The background export or import process to service the command export/import command 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0630I Export/import command: Copied number kilobytes of data.
Explanation: The background export or import process to service the command export/import command copies number administrator definitions from either the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0626I Export/import command: Copied number node definitions.
Explanation: The background export or import process to service the command export/import command 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None.
Explanation: The background export or import process to service the command export/import command 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. System Action: Export or import processing for the command completes. Server operation continues.
Chapter 3. Common and Platform Specfic Messages
59
ANR0631I ANR0637I
ANR0631I Export/import command: Copied number megabytes of data. System Action: Export or import processing for the command completes. Server operation continues. User Response: Examine the server messages issued prior to this message to view the error. Use the QUERY ACTLOG command to view the activity log and search for messages. ANR0635I Export/import command: Processing node node name in domain domain name.
Explanation: The background export or import process to service the command export/import command copies number megabytes 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0632I Export/import command: Copied number gigabytes of data.
Explanation: The background export or import process to service the command export/import command is currently processing the client node definition information for node node name. The node will be imported to domain domain name. System Action: Export or import processing for the command continues. User Response: None. ANR0636I Import command: Processing file space filespace name for node node name as file space new filespace name.
Explanation: The background export or import process to service the command export/import command copies number gigabytes 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0633I Export/import command: Copied number terabytes of data.
Explanation: The background export or import process to service the command export/import command copies number terabytes 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0634I Export/import command: Detected number errors.
Explanation: The background import process to 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 .
Explanation: The background export or import process to service the command export/import command 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.
Explanation: The background export or import process to service the command export/import command is currently processing client node file space information for file space filespace name belonging to client node node name. System Action: Export or import processing for the command continues. User Response: None.
60
IBM Tivoli Storage Manager: Messages
ANR0638I ANR0645I
ANR0638I Export/import command: Processing administrator administrator name. definition information for management class class name belonging to policy set set name in policy domain domain name. System Action: Export or import processing for the command continues. User Response: None. ANR0643I Export/import command: Processing archive copy group in domain domain name, set set name, management class class name.
Explanation: The background export or import process to service the command export/import command is currently processing the administrator definition information for administrator administrator name. System Action: Export or import processing for the command continues. User Response: None. ANR0639I Export/import command: Processing domain domain name.
Explanation: The background export or import process to service the command export/import command is currently processing the policy domain definition information for domain domain name. System Action: Export or import processing for the command continues. User Response: None.
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. User Response: None. ANR0644I Export command: Processing copy group of unknown type in domain domain name, set set name, management class class name.
ANR0640I
Export/import command: Processing policy set set name in policy domain domain name.
Explanation: The background export or import process to service the command export/import command is currently processing the policy set definition information for policy set set name belonging to policy domain domain name. System Action: Export or import processing for the command continues. User Response: None. ANR0641I Export/import command: Processing management class class name in domain domain name, set set name.
Explanation: The background export or import 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. System Action: Export or import processing for the command continues. The import or export process assumes that the copy group is a backup copy group. User Response: After policy definitions are imported, use the QUERY MGMTCLASS and QUERY 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 Export/import command: Processing schedule schedule name in domain domain name.
Explanation: The background export or import process to service the command export/import command is currently processing the management class definition information for management class class name belonging to policy set set name in policy domain domain name. System Action: Export or import processing for the command continues. User Response: None. ANR0642I Export/import command: Processing backup copy group in domain domain name, set set name, management class class name.
Explanation: The background export or import process to service the command export/import command is currently processing the schedule definition information for schedule schedule name belonging to policy domain domain name. System Action: Export or import processing for the command continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
Explanation: The background export or import process to service the command export/import command is currently processing the backup copy group
61
ANR0646I ANR0652W
ANR0646I Export/import command: message ANR0650W IMPORT: Archive copygroup copy group name in management class management class name for domain domain name is not defined, default management class will be used.
Explanation: The background export or import process to service the command export/import command has received the message message from the server. System Action: Export or import processing for the 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: During import processing, the server 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. System Action: The default management class for the nodes policy domain is bound to the archive 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 management class or copy group for the domain, and process the import operation again. ANR0651W IMPORT: Backup copygroup copy group name in management class management class name for domain domain name is not defined, default management class will be used.
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. System Action: Server operation continues. User Response: None. ANR0648I 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. System Action: Server operation continues. User Response: None. ANR0649I Import command: Domain domain name does not exist - the system will attempt to import node node name to domain STANDARD.
Explanation: During import processing, the server finds that a management class or copy group bound to a backup 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 backup file copy 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 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.
Explanation: The background import process to service the command import command is currently 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.
Explanation: During import processing, the server 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. 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. 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
62
IBM Tivoli Storage Manager: Messages
ANR0653W ANR0659W
the 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 management class management class name in this domain cannot be imported. 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.
Explanation: During import processing, the server finds that a management class or copy group bound to a backup 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 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. 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 management class or copy group for the domain, and process the import operation again. ANR0655W Command: Retrieve or restore failed - file was deleted from data storage during retrieval.
Explanation: During import processing, the server encounters an invalid file space authorization rule type for the indicated file space and node. System Action: Server operation continues. 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.
Explanation: The server ends a file retrieval operation for the specified command because the file has been deleted from data storage by another process before retrieval is complete. System Action: The server ends the command and continues operation. 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 command after these processes have been completed or canceled. ANR0656W Export/import command: Skipped archive number archive files, backup number backup files, and spacemg number space managed files.
Explanation: During processing of command export 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. System Action: Processing of the command continues. 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 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.
Explanation: The background export or import process to service the command export/import command 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 specified in the command export/import command. System Action: Export or import processing for the command completes. Server operation continues.
Explanation: During processing of command export 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. System Action: Processing of the command continues. 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.
Chapter 3. Common and Platform Specfic Messages
63
ANR0660E ANR0666W
ANR0660E Command: Insufficient memory available in accessing data storage. interrupted. Reissue the command command after the problem is resolved. ANR0664E Export/import command: Media not accessible 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 and server operation continues. 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. ANR0661E Command: Internal error encountered 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. User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage. ANR0665W Import command: Transaction failed storage pool pool name is not defined.
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 accessing data storage.
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 server operation continues. 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. ANR0666W Import command: Transaction failed object excluded by size in storage pool pool name and all successor pools.
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. v Incompatible storage pool data format. System Action: The command command operation ends and server operation continues. User Response: Query the activity log to find messages preceding this one to determine the cause of the error. After the problem is corrected, the command can be retried. ANR0663E Command: Data transfer was interrupted in accessing data storage.
Explanation: The server ends a database update 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. System Action: The import operation is ended and server operation continues. 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.
Explanation: The database transaction associated with command command operation failed because data transfer to or from data storage was interrupted by an external event. System Action: The command command operation is ended and server operation continues. User Response: Examine the messages issued prior to this message to determine why the data transfer was
64
IBM Tivoli Storage Manager: Messages
ANR0667W ANR0674W
ANR0667W Import command: Transaction failed - no space available in storage pool pool name and all successor pools. User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage. ANR0671W Export/import command: Transaction failed - sufficient recovery log space is not available.
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. System Action: The import operation is ended and server operation continues. User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. ANR0668W Export/import command: Transaction failed - error on output storage device.
Explanation: The server ends a database update transaction for an export or import operation because sufficient log space is not available on the server. System Action: The server ends the export or import operation and server operation continues. User Response: An authorized administrator can issue the DEFINE LOGVOLUME command to add volumes 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 Export/import command: Transaction failed - sufficient database space is not available.
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. System Action: The server ends the export or import operation and server operation continues. User Response: Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down by using the HALT command to correct the hardware problem. After the problem is corrected, the client may be able to try the operation again. ANR0669W Export/import command: Transaction failed - data transfer interrupted.
Explanation: The server ends a database update transaction for an export or import operation because sufficient database space is not available on the server. System Action: The server ends the export or import operation and server operation continues. User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and the EXTEND DB command to extend the size of the log so that the new volumes are used. ANR0673W Export/import command: Data storage retrieve or restore failed - data integrity error detected.
Explanation: The database transaction associated with an export or import operation failed because data transfer to or from data storage was interrupted by an external event. System Action: The export or import operation is ended and server operation continues. User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the export/import operation again after problem is resolved. ANR0670W Export/import command: Transaction failed - storage media inaccessible.
Explanation: The server ends an export or import operation because an internal database integrity error has been encountered on the server. System Action: The server ends the export or import operation and continues operation. User Response: Contact your service representative. ANR0674W Export command: Retrieve failed - error on input storage device.
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.
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.
Chapter 3. Common and Platform Specfic Messages
65
ANR0675E ANR0684E
System Action: Export processing skips this file, and continues operation. User Response: Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down with the HALT command to correct the hardware problem. ANR0675E EXPORT/IMPORT: Error starting the Export/Import Session. ANR0679E EXPORT/IMPORT: Communications Failure in Receiving verb type verb.
Explanation: The server export/import process encounters a communications error in using the verb type verb to transfer information to or from the server. System Action: The export or import process ends and server operation continues. User Response: Contact your service representative. ANR0681E EXPORT/IMPORT: Authentication Failure.
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. System Action: The export or import process ends and server operation continues. 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. ANR0676E EXPORT/IMPORT: Invalid Communications Buffer State in SEND.
Explanation: The server export/import process encounters an authentication error in transferring information to or from the server. System Action: The export or import process ends and server operation continues. User Response: Contact your service representative. ANR0682E EXPORT/IMPORT: Communications Failure in Sending verb type verb (command).
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 server operation continues. User Response: Contact your service representative. ANR0677E EXPORT/IMPORT: Invalid Communications Buffer State in RECEIVE.
Explanation: The server export/import process encounters a communications error in using the verb type verb to issue command command. System Action: The export or import process ends and server operation continues. User Response: Contact your service representative. ANR0683E EXPORT/IMPORT: Receive Buffer overflow.
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 server operation continues. User Response: Contact your service representative.
Explanation: The server export/import process encounters an overflow error in transferring information to or from the server. System Action: The export or import process ends and server operation continues. User Response: Contact your service representative. ANR0684E EXPORT/IMPORT: Communications failure: bad verb received (verb type).
ANR0678E
EXPORT/IMPORT: Communications Failure in Sending verb type verb.
Explanation: The server export/import process encounters a communications error in using the verb type verb to transfer information to or from the server. System Action: The export or import process ends and server operation continues. User Response: Contact your service representative.
Explanation: The server encounters an invalid communications verb during export or import processing and is not able to continue processing. System Action: The export or import process ends and server operation continues. User Response: Contact your service representative.
66
IBM Tivoli Storage Manager: Messages
ANR0685E ANR0692E
ANR0685E EXPORT/IMPORT: Internal error: Invalid table output handle detected. ANR0689W 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.
Explanation: The server export/import process encounters an internal error in transferring information to or from the server. System Action: The export or import process ends and server operation continues. User Response: Contact your service representative. ANR0686E Export/import command: Transaction failure - could not start database transaction.
Explanation: During import processing, the server 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 Export/import command: Transaction failure - server aborted the transaction (abort code).
Explanation: During processing of command export/import command, a database transaction cannot be started in the server database. System Action: Processing of the command terminates. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0687E Export/import command: Transaction failure - could not commit database transaction.
Explanation: During processing of command export/import command, a database transaction cannot be committed in the server database. The reason code abort code is returned. System Action: Processing of the command ends. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0691E Export command: Error abort code writing export data.
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. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0688E Export/import command: Transaction failure - commit called when no transaction started.
Explanation: During processing of command export command, an input/output error occurs when writing the exported information to the export media. System Action: Processing of the command ends. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0692E Command: Out of space on sequential media, scratch media could not be mounted.
Explanation: During processing of command export/import command, a database transaction cannot be started in the server database. System Action: Processing of the command ends. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.
Explanation: During command command processing, the process encounters an out-of-space condition writing to the sequential media. Command command
Chapter 3. Common and Platform Specfic Messages
67
ANR0693E ANR0699E
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. ANR0696E Export command: Output table error encountered - 0 columns reported in the table.
Explanation: During processing of command export command, an unexpected error is detected. System Action: Processing of the command ends. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0697E Export command: Output table error encountered - not positioned to the first column in the table.
Explanation: During processing of command import command, an input/output error occurs when reading the exported information from the export media. System Action: Processing of the command ends. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0694E Import command: Invalid record format (format code) detected on import.
Explanation: During processing of command export command, an unexpected error is detected. System Action: Processing of the command ends. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0698E Export/import command: Invalid value for FILEDATA parameter - parameter value.
Explanation: During processing of command import command, an invalid record type is detected when reading the exported information from the export media. System Action: Processing of the command ends. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0695E Export command: Unexpected error error code encountered in receiving table output data.
Explanation: The value (parameter value) specified for the FILEDATA parameter in command export/import command is not a valid value for this parameter. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid FILEDATA parameter. For information on valid values for the FILEDATA parameter for the command, refer to the Administrators Reference for your particular platform. ANR0699E Export/import command: Device class DISK cannot be specified for this command.
Explanation: During processing of command export command, an unexpected error is detected. System Action: Processing of the command ends. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.
Explanation: The DEVCLASS value DISK cannot be specified for the command export/import command. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server.
68
IBM Tivoli Storage Manager: Messages
ANR0700E ANR0709E
ANR0700E Export/import command: Invalid value for PREVIEW parameter - parameter value. valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server. ANR0707E Export command: The FILESPACE parameter cannot be specified.
Explanation: The value (parameter value) specified for the PREVIEW parameter in command export/import command is not a valid value for this parameter. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid PREVIEW parameter. For information on valid values for the PREVIEW parameter for the command, refer to the Administrators Reference for your particular platform. ANR0701E Export/import command: Invalid value for SCRATCH parameter - parameter value.
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. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid FILEDATA parameter. For information on valid parameter values for the command, refer to the Administrators Reference for your particular platform. ANR0708E Import command: The FILESPACE parameter cannot be specified unless the FILEDATA parameter specifies that files should be imported.
Explanation: The value (parameter value) specified for the SCRATCH parameter in command export/import command is not a valid value for this parameter. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid SCRATCH parameter. For information on valid values for the SCRATCH parameter for the command, refer to the Administrators Reference for your particular platform. ANR0705E Export command: The VOLUMENAMES parameter must be specified when SCRATCH=NO is specified.
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 FILEDATA parameter is specified with a value other than NONE. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid FILEDATA parameter. For information on valid parameter values for the command, refer to the Administrators Reference for your particular platform. ANR0709E Command: No matching nodes registered in the specified domains.
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. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid VOLUMENAMES parameter. For information on valid parameter values for the command, refer to the Administrators Reference for your particular platform. ANR0706E Export command: A device class must be specified unless PREVIEW=YES is specified.
Explanation: The DOMAIN parameter has been specified for this command, but no nodes matching the node name specification are found in the domains specified. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a 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.
Explanation: The DEVCLASS parameter is not specified in the command export command. Unless PREVIEW=YES is specified, a DEVCLASS value must be specified. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a
Chapter 3. Common and Platform Specfic Messages
69
ANR0710E ANR0717E
ANR0710E Command: Unable to start background process. ANR0714E Import command: The EXTFILE device class cannot be specified when the VOLUMENAMES parameter is specified.
Explanation: The server command processor is not able to start a background process to perform the command command. System Action: The command process ends and server operation continues. 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. ANR0711E Import command: Unable to start import process.
Explanation: An invalid combination of parameters has been entered for command import command. The EXTFILE device class cannot be used in combination with the VOLUMENAMES parameter. System Action: The command fails and server operation continues. User Response: Reissue the command with the correct syntax. ANR0715E Import command: A device class must be specified.
Explanation: The server import command processor is not able to start a background process to perform the import operation. System Action: The export or import process ends and server operation continues. 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. ANR0712E Import command: Invalid value for DATES parameter - parameter value.
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. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a 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 value (parameter value) specified for the DATES parameter in command import command is not a valid value for this parameter. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid DATES parameter. For information on valid values for the DATES parameter for the command, refer to the Administrators Reference for your particular platform. ANR0713E Import command: Invalid value for REPLACEDEFS parameter - parameter value.
Explanation: The command import command encounters invalid data on the export media while trying to import server information. System Action: The command fails and server operation continues. 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 Export/import command: Preview processing terminated abnormally communications send or receive failed.
Explanation: The value (parameter value) specified for the REPLACEDEFS parameter in command import command is not a valid value for this parameter. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid REPLACEDEFS parameter. For information on valid values for the REPLACEDEFS parameter for the command, refer to the Administrators Reference for your particular platform.
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 and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the
70
IBM Tivoli Storage Manager: Messages
ANR0718E ANR0724E
activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0718E Export/import command: Processing terminated abnormally communications send or receive failed. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0722E Export/import command: Processing terminated abnormally - unexpected verb received from server.
Explanation: Processing for the command export/import command ends when an internal communications error is encountered in the server. System Action: Export/import processing is ended and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0719E Export/import command: Preview processing terminated abnormally insufficient memory.
Explanation: Processing for the command export/import command ends when an internal communications error is encountered in the server. System Action: Export/import processing ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0723E Export/import command: Preview processing terminated abnormally transaction failure.
Explanation: Processing for the command export/import command in preview mode is ended because sufficient memory is not available on the server. System Action: Export/import processing is ended and server operation continues. 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. ANR0720E command: Processing terminated abnormally - insufficient memory.
Explanation: Processing for the command export/import command in preview mode ends when a database transaction error is encountered in the server. System Action: Export/import processing ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0724E Export/import command: Processing terminated abnormally - transaction failure.
Explanation: Processing for the command ends because sufficient memory is not available on the server. System Action: Command processing is ended and server operation continues. 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. ANR0721E Export/import command: Preview processing terminated abnormally unexpected verb received from server.
Explanation: Processing for the command export/import command ends when a database transaction error is encountered in the server. System Action: Export/import processing ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.
Explanation: Processing for the command export/import command in preview mode ends when an internal communications error is encountered in the server. System Action: Export/import processing ends and server operation continues.
Chapter 3. Common and Platform Specfic Messages
71
ANR0725E ANR0731E
ANR0725E Export/import command: Preview processing terminated abnormally authentication failure. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0729E Import command: Syntax error from command server command.
Explanation: Processing for the command export/import command in preview mode ends when an authentication error is encountered in the server. System Action: Export/import processing ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0726E Export/import command: Processing terminated abnormally - authentication failure.
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. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. 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.
Explanation: Processing for the command export/import command ends when an authentication error is encountered in the server. System Action: Export/import processing ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0727E Export/import command: Preview processing terminated abnormally internal error.
Explanation: Processing for the command import command ends when an internal command error is encountered in the server. System Action: Import processing ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0731E Import command: Invalid value for COMPRESSION parameter in exported data for node node name.
Explanation: Processing for the command export/import command in preview mode ends when an internal error is encountered in the server. System Action: Export/import processing ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0728E Export/import command: Processing terminated abnormally - internal error.
Explanation: During preview processing of command import command, an invalid value is encountered for the COMPRESSION parameter for node node name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing COMPRESSION value is used. User Response: None. If the data is imported with a later command, verify that the correct COMPRESSION value is used for this node.
Explanation: Processing for the command export/import command ends when an internal error is encountered in the server. System Action: Export/import processing ends and server operation continues.
72
IBM Tivoli Storage Manager: Messages
ANR0732E ANR0739E
ANR0732E Import command: Invalid value for ARCHDELETE parameter in exported data for node node name. ANR0736E Import command: Invalid value for BACKDELETE parameter in exported data - node node name registered with default BACKDELETE value.
Explanation: During preview processing of command import command, an invalid value is encountered for the ARCHDELETE parameter for node node name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing ARCHDELETE value is used. User Response: None. If the data is imported with a later command, verify that the correct ARCHDELETE value is used for this node. ANR0733E Import command: Invalid value for BACKDELETE parameter in exported data for node node name.
Explanation: During processing of command import command, an invalid value is encountered for the BACKDELETE parameter for node node name. System Action: Processing of the command continues, by using the default BACKDELETE value for this node. User Response: Verify that the correct BACKDELETE value has been used for this node. Update this value, if necessary. ANR0737E Import command: Invalid value for COMPRESSION parameter in exported data - existing COMPRESSION value for node node name was not updated.
Explanation: During preview processing of command import command, an invalid value is encountered for the BACKDELETE parameter for node node name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing BACKDELETE value is used. User Response: None. If the data is imported with a later command, verify that the correct BACKDELETE value is used for this node. ANR0734E Import command: Invalid value for COMPRESSION parameter in exported data - node node name registered with default COMPRESSION value.
Explanation: During processing of command import command, an invalid value is encountered for the COMPRESSION parameter for node node name. System Action: Processing of the command continues, by using the existing COMPRESSION value for this node. User Response: Verify that the correct COMPRESSION value has been used for this node. Update this value, if necessary. ANR0738E Import command: Invalid value for ARCHDELETE parameter in exported data - existing ARCHDELETE value for node node name was not updated.
Explanation: During processing of command import command, an invalid value is encountered for the COMPRESSION parameter for node node name. System Action: Processing of the command continues, 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 Import command: Invalid value for ARCHDELETE parameter in exported data - node node name registered with default ARCHDELETE value.
Explanation: During processing of command import command, an invalid value is encountered for the ARCHDELETE parameter for node node name. System Action: Processing of the command continues, by using the existing ARCHDELETE value for this node. User Response: Verify that the correct ARCHDELETE value has been used for this node. Update this value, if necessary. ANR0739E Import command: Invalid value for BACKDELETE parameter in exported data - existing BACKDELETE value for node node name was not updated.
Explanation: During processing of command import command, an invalid value is encountered for the ARCHDELETE parameter for node node name. System Action: Processing of the command continues, by using the default ARCHDELETE value for this node. User Response: Verify that the correct ARCHDELETE value has been used for this node. Update this value, if necessary.
Explanation: During processing of command import command, an invalid value is encountered for the BACKDELETE parameter for node node name. System Action: Processing of the command continues, by using the existing BACKDELETE value for this node. User Response: Verify that the correct BACKDELETE
Chapter 3. Common and Platform Specfic Messages
73
ANR0740E ANR0745E
value has been used for this node. Update this value, if necessary. ANR0740E Import command: Invalid value for TYPE parameter in exported data for copy group copy group name in domain domain name, set policy set name, management class management class name - backup is assumed. ANR0743E Import command: Invalid value for 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.
Explanation: During processing of command import 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. System Action: Processing of the command continues. 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 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 - archive is assumed.
Explanation: During preview processing of command import command, an invalid value is encountered for the MODE parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing MODE value is used. User Response: None. If the data is imported with a later command, verify that the correct MODE value is used for this archive copy group. ANR0744E Import command: Invalid value for MODE parameter in exported data for backup copy group copy group name in domain domain name, set policy set name, management class management class name.
Explanation: During processing of command import 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. System Action: Processing of the command continues. Based upon other copy group parameters, a copy group type of archive is assigned. User Response: Verify that the assigned TYPE value of archive for this copy group is correct. ANR0742E 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.
Explanation: During preview processing of command import command, an invalid value is encountered for the MODE parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing MODE value is used. User Response: None. If the data is imported with a later command, verify that the correct MODE value is used for this backup copy group. ANR0745E Import command: Invalid value for 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.
Explanation: During processing of command import 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. System Action: Processing of the command continues. However, this copy group is not imported because a TYPE value cannot be assigned. User Response: Manually define this copy group, if necessary.
Explanation: During preview processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing SERIALIZATION value is used. User Response: None. If the data is imported with a later command, verify that the correct SERIALIZATION value is used for this archive copy group.
74
IBM Tivoli Storage Manager: Messages
ANR0746E ANR0751E
ANR0746E Import command: Invalid value for SERIALIZATION parameter in exported data for backup copy group copy group name in domain domain name, set policy set name, management class management class name. ANR0749E Import command: Invalid value for SERIALIZATION parameter in exported data - archive copy group copy group name in domain domain name, set policy set name, management class management class name defined with default SERIALIZATION value.
Explanation: During preview processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing SERIALIZATION value is used. User Response: None. If the data is imported with a later command, verify that the correct SERIALIZATION value is used for this backup copy group. ANR0747E Import command: Invalid value for MODE parameter in exported data archive copy group copy group name in domain domain name, set policy set name, management class management class name defined with default MODE value.
Explanation: During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues, by using the default SERIALIZATION value for this archive copy group. User Response: Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary. ANR0750E Import command: Invalid value for SERIALIZATION parameter in exported data - backup copy group copy group name in domain domain name, set policy set name, management class management class name defined with default SERIALIZATION value.
Explanation: During processing of command import command, an invalid value is encountered for the MODE parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues, by using the default MODE value for this archive copy group. User Response: Verify that the correct MODE value has been used for this copy group. Update this value, if necessary. ANR0748E Import command: Invalid value for MODE parameter in exported data backup copy group copy group name in domain domain name, set policy set name, management class management class name defined with default MODE value.
Explanation: During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues, by using the default SERIALIZATION value for this backup copy group. User Response: Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary. ANR0751E Import command: Invalid value for MODE parameter in exported data existing MODE value for archive copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.
Explanation: During processing of command import command, an invalid value is encountered for the MODE parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues, 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.
Explanation: During processing of command import command, an invalid value is encountered for the MODE parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues, by using the existing MODE value for this archive copy group.
Chapter 3. Common and Platform Specfic Messages
75
ANR0752E ANR0757E
User Response: Verify that the correct MODE value has been used for this copy group. Update this value, if necessary. ANR0752E Import command: Invalid value for MODE parameter in exported data existing MODE value for backup copy group copy group name in domain domain name, set policy set name, management class management class name was not updated. System Action: Processing of the command continues, by using the existing SERIALIZATION value for this backup copy group. User Response: Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary. ANR0755E Import command: Invalid value for ACTION parameter in exported data for schedule schedule name in domain domain name.
Explanation: During processing of command import command, an invalid value is encountered for the MODE parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues, by using the existing 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. ANR0753E Import command: Invalid value for SERIALIZATION parameter in exported 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.
Explanation: During preview processing of command import command, an invalid value is encountered for the ACTION parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing ACTION value is used. User Response: If the data is imported with a later command, verify that the correct ACTION value is used for this schedule. ANR0756E Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data for schedule schedule name in domain domain name.
Explanation: During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name. System Action: Processing of the command continues, by using the existing SERIALIZATION value for this archive copy group. User Response: Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary. ANR0754E Import command: Invalid value for SERIALIZATION parameter in exported data - existing SERIALIZATION value for backup copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.
Explanation: During preview processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues. If a later command 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. ANR0757E Import command: Invalid value for DAYOFWEEK parameter in exported data for schedule schedule name in domain domain name.
Explanation: During preview processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing DAYOFWEEK value is used. User Response: If the data is imported with a later command, verify that the correct DAYOFWEEK value is used for this schedule.
Explanation: During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.
76
IBM Tivoli Storage Manager: Messages
ANR0758E ANR0764E
ANR0758E Import command: Invalid value for ACTION parameter in exported data schedule schedule name in domain domain name defined with default ACTION value. ANR0761E Import command: Invalid value for ACTION parameter in exported data existing ACTION value for schedule schedule name in domain domain name was not updated.
Explanation: During processing of command import command, an invalid value is encountered for the ACTION parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues, 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 Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data - schedule schedule name in domain domain name defined with default values for DURATION, DURUNITS, PERIOD, and PERUNITS.
Explanation: During processing of command import command, an invalid value is encountered for the ACTION parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues, 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 Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data - existing values for DURATION, DURUNITS PERIOD, and PERUNITS for schedule schedule name in domain domain name were not updated.
Explanation: During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues, by using the default values for DURATION, DURUNITS, PERIOD, and PERUNITS. User Response: Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary. ANR0760E Import command: Invalid value for DAYOFWEEK parameter in exported data - schedule schedule name in domain domain name defined with default DAYOFWEEK value.
Explanation: During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues, by using the existing values for DURATION, DURUNITS, PERIOD, and PERUNITS. User Response: Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary. ANR0763E Import command: Invalid value for DAYOFWEEK parameter in exported data - existing DAYOFWEEK value for schedule schedule name in domain domain name was not updated.
Explanation: During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues, by using the default DAYOFWEEK value for this schedule. User Response: Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary.
Explanation: During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues, 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. ANR0764E Import command: Invalid lock status detected while importing node node name - this node will not be locked.
Explanation: During processing of command import command, an invalid value is encountered for the lock status for node node name.
Chapter 3. Common and Platform Specfic Messages
77
ANR0765E ANR0769E
System Action: Processing of the command continues, 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. 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, use the export data with the unknown value, and check and update the MODE value after import processing has been performed. ANR0768E Export command: Invalid value for SERIALIZATION parameter detected while exporting copy group copy group name in domain domain name, set policy set name, management class management class name - default or existing value is used during import.
Explanation: During processing of command import command, an invalid value is encountered for the lock status for administrator administrator name. System Action: Processing of the command continues, but the administrator is not locked. User Response: An administrator with the proper authorization must issue the LOCK ADMIN command, if necessary. ANR0766E Export command: Invalid value for TYPE parameter detected while exporting copy group copy group name in domain domain name, set policy set name, management class management class name - system will attempt to assign value during import.
Explanation: During processing of command export command, an invalid value is encountered for the SERIALIZATION parameter for copy group copy group name, in domain domain name, policy set policy set name, management class management class name. System Action: Export processing continues, but the exported data contains an unknown SERIALIZATION value for this copy group. If this data is imported, the default or existing SERIALIZATION value is used. User Response: Update the SERIALIZATION value for this copy group and restart the export command. Alternatively, use the export data with the unknown value, and check and update the SERIALIZATION value after import processing has been performed. ANR0769E Export command: Invalid value for ACTION parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.
Explanation: During processing of command export command, an invalid value is encountered for the TYPE parameter for copy group copy group name, in domain domain name, policy set policy set name, management class management class name. System Action: Export processing continues, but the 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. User Response: Delete and define this copy group to eliminate the invalid data, and then restart the export command. Alternatively, use the export data with the unknown value, and the system will attempt to assign a TYPE during import processing. ANR0767E Export command: Invalid value for MODE parameter detected while exporting copy group copy group name in domain domain name, set policy set name, management class management class name - default or existing value is used during import.
Explanation: During processing of command export command, an invalid value is encountered for the ACTION parameter for schedule schedule name in domain domain name. System Action: Export processing continues, but the 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 schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the ACTION value after import processing has been performed.
Explanation: During processing of command export command, an invalid value is encountered for the MODE parameter for copy group copy group name in domain domain name, policy set policy set name, management class management class name. System Action: Export processing continues, but the exported data contains an unknown MODE value for
78
IBM Tivoli Storage Manager: Messages
ANR0770E ANR0775E
ANR0770E Export command: Invalid value for DURUNITS parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import. after import processing has been performed. ANR0773E Export command: Invalid lock status detected while exporting administrator administrator name - this administrator will not be locked during import.
Explanation: During processing of command export command, an invalid value is encountered for the DURUNITS parameter for schedule schedule name in domain domain name. System Action: Export processing continues, but the exported data contains an unknown DURUNITS value for this schedule. If this data is imported, the default or existing DURUNITS value is used. User Response: Update the DURUNITS value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the DURUNITS value after import processing has been performed. ANR0771E Export command: Invalid value for PERUNITS parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.
Explanation: During processing of command export command, an invalid value is encountered for the lock status for administrator administrator name. System Action: Export processing continues, but the exported data contains an unknown lock status for this administrator. If this data is imported, the administrator will not be locked. User Response: An administrator with the proper authorization must issue the LOCK NODE or UNLOCK NODE command to achieve the desired lock status, and then restart the export command. Alternatively, use the export data with the unknown status, and issue a LOCK ADMIN or UNLOCK ADMIN command after import processing has been performed. ANR0774E Export command: Invalid value for COMPRESSION parameter detected while exporting node node name - default or existing value is used during import.
Explanation: During processing of command export command, an invalid value is encountered for the PERUNITS parameter for schedule schedule name in domain domain name. System Action: Export processing continues, but the exported data will contain an unknown PERUNITS value for this schedule. If this data is imported, the default or existing PERUNITS value is used. User Response: Update the PERUNITS value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the PERUNITS value after import processing has been performed. ANR0772E Export command: Invalid value for DAYOFWEEK parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.
Explanation: During processing of command export command, an invalid value is encountered for the COMPRESSION parameter for node node name. System Action: Export processing continues, but the 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. Alternatively, use the export data with the unknown value, and check and update the COMPRESSION value after import processing has been performed. ANR0775E Export command: Invalid lock status detected while exporting node node name - this node will not be locked during import.
Explanation: During processing of command export command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in domain domain name. System Action: Export processing continues, but the exported data contains an unknown DAYOFWEEK value for this schedule. If this data is imported, the default or existing DAYOFWEEK value is used. 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
Explanation: During processing of command export command, an invalid value is encountered for the lock status for node node name. System Action: Export processing continues, but the 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
Chapter 3. Common and Platform Specfic Messages
79
ANR0776E ANR0783E
import processing has been performed. ANR0776E Export command: Invalid value for ARCHDELETE parameter detected while exporting node node name - default or existing value is used during import. System Action: The command command is ended and server operation continues. 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.
Explanation: During processing of command export command, an invalid value is encountered for the ARCHDELETE parameter for node node name. System Action: Export processing continues, but the exported data contains an unknown ARCHDELETE value for this node. If this data is imported, the default or existing ARCHDELETE value is used. User Response: Update the ARCHDELETE parameter for this node and restart the export command. Alternatively, use the export data with the unknown value, and check and update the ARCHDELETE value after import processing has been performed. ANR0777E Export command: Invalid value for BACKDELETE parameter detected while exporting node node - default or existing value is used during import.
Explanation: The server export/import process encounters an internal error in establishing an intermemory communications session with other server components. System Action: The export or import process ends and server operation continues. 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. If the error is not resolved, contact your service representative. ANR0781E Export/import command: Process aborted server sign on failed.
Explanation: During processing of command export command, an invalid value is encountered for the BACKDELETE parameter for node node name. System Action: Export processing continues, but the exported data contains an unknown BACKDELETE value for this node. If this data is imported, the default or existing BACKDELETE value is used. User Response: Update the BACKDELETE parameter for this node and restart the export command. Alternatively, use the export data with the unknown value, and check and update the BACKDELETE value after import processing has been performed. ANR0778E Command: Error encountered in accessing data storage - device class device class name is not defined.
Explanation: The server export/import process encounters an internal error in establishing an intermemory communications session with other server components. System Action: The export or import process ends and server operation continues. User Response: Contact your service representative. ANR0782E Export/import command: Process aborted a server data storage session could not be established (rc return code).
Explanation: The server export/import process encounters an internal error in establishing a session with the data storage services. System Action: The export or import process ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0783E Export/import command: Process aborted a server data storage Export/Import stream could not be established (rc return code).
Explanation: During command command processing, an error occurred because the specified device class is not defined. System Action: The command command is ended and server operation continues. User Response: Make sure the specified device class is defined. ANR0779E Command: Error encountered in accessing data storage - disk volume specified.
Explanation: During command command processing, an error occurred because a specified volume is a disk volume rather than a tape volume.
Explanation: The server export/import process encounters an internal error in establishing a session with the data storage services.
80
IBM Tivoli Storage Manager: Messages
ANR0784E ANR0790E
System Action: The export or import process ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0784E Export/import command: Process aborted internal error detected with the Export/Import level: level number. ANR0787E Import command: Import of file space filespace name in node node name aborted by server (abort reason).
Explanation: The server import process encounters an internal error in importing file space filespace name for client node node name. The reason code abort reason is encountered. System Action: The export or import process ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0788E Import command: Error error code during import of data storage data.
Explanation: The server export/import process encounters an internal error in evaluating the export/import level (SERVER, NODE, ADMIN, POLICY). System Action: The export or import process ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0785E Import command: Invalid record type xrecord type read from export data.
Explanation: The server import process encounters an internal data storage error. The error code error code is encountered. System Action: The export or import process ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0789E Import command: Failure in normalizing transaction identifier for sending to the server.
Explanation: The server export/import process encounters an internal error in reading data from the export media. An invalid record type of record type is encountered during the read operation. System Action: The export or import process ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0786E Import command: Invalid export version version number in exported data.
Explanation: The server import process encounters an internal database transaction error in importing information into the server database. System Action: The export or import process ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0790E Import command: Error in absorbing data records.
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. System Action: The export or import process ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.
Explanation: The server import process encounters an internal error in importing information into the server database. System Action: The export or import process ends and server operation continues.
Chapter 3. Common and Platform Specfic Messages
81
ANR0791E ANR0797E
User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0791E Export/import command: Protocol error verb verb type with length verb length received, expected expected type. to examine messages prior to this error to determine the cause of the data storage failure. If you find and resolve the error, retry the export or import operation. If you cannot find the error, contact your service representative for assistance in resolving the problem. ANR0794E Export/import command: Processing terminated abnormally - error accessing data storage.
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. System Action: The export or import process ends and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. 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: The server encountered an internal error in accessing data storage while executing an import or export operation. System Action: The export or import 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 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 Command: Error encountered in accessing 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. System Action: The command command operation is ended and server operation continues. User Response: Issue the command with a valid volume name. ANR0796E Command: Error encountered in accessing data storage - insufficient number of mount points available for removable media.
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. 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 Export/import command: Preview processing terminated abnormally error accessing data storage.
Explanation: During command command processing, the server cannot allocate sufficient mount points. System Action: The command command operation is ended and server operation continues. User Response: If necessary, make more mount points available. ANR0797E Command: Error encountered in accessing data storage - required volume was not mounted.
Explanation: The server encountered an internal error in accessing data storage while executing an import or export preview operation. System Action: The export or import operation is ended and server operation continues. User Response: Use the QUERY ACTLOG command
Explanation: During command command processing, a required volume cannot be mounted. The mount request may have been canceled. System Action: The command command operation is ended and server operation continues.
82
IBM Tivoli Storage Manager: Messages
ANR0798E ANR0804I
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. ANR0801I DELETE FILESPACE filespace name for node node name started as process process ID.
Explanation: During import processing, a volume has been mounted but cannot be used. System Action: The import operation is ended and server operation continues. 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 Command: Error encountered in accessing data storage - volume already in use.
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. System Action: The server starts a background process to perform the operation in response to a request from the client node. User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. 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: During command command processing, a 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. System Action: The command command operation is ended and server operation continues. User Response: Specify a volume that is not in use or defined in a storage pool, and that has not been previously used for an export, database dump, or database backup operation as recorded in the server volume history information. Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export, database dump, or database backup operations. ANR0800I Command command for node node name started as process process ID.
Explanation: A 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. User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR0803I DELETE FILESPACE filespace name (backup data) for node node name started.
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.
Explanation: A background server process has started (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. System Action: The background process deletes backup objects for the specified file space while server operation continues. User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR0804I DELETE FILESPACE filespace name (archive data) for node node name started.
Explanation: A background server process has 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
Chapter 3. Common and Platform Specfic Messages
83
ANR0805I ANR0814I
archive objects for all file spaces that belong to the node are deleted. System Action: The background process deletes archive objects for the specified file space while server operation continues. User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR0805I DELETE FILESPACE filespace name canceled for node node name: number of objects objects deleted. ANR0812I 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: 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 operation continues. User Response: No action is required. An authorized administrator can issue the DELETE FILESPACE command to delete remaining objects in the file space. ANR0806I DELETE FILESPACE filespace name complete for node node name: number of objects objects deleted.
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 server operation continues. 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 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: A server process deleting file space data for the node specified has completed. The total number of objects deleted is reported in the message. System Action: The server process is ended and server operation continues. User Response: None. ANR0811I Inventory client file expiration started as process process ID.
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. User Response: None.
Explanation: The inventory file expiration process was canceled by an administrator. The number of objects examined and deleted prior to the cancelation are reported. A total error count is also displayed. System Action: The server ends the file expiration process. User Response: None. 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
84
IBM Tivoli Storage Manager: Messages
ANR0815I ANR0823E
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 information online or see Appendix A. Allocating Additional Server Memory. ANR0815I Expiration retry in progress. 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 server operation continues. User Response: None. ANR0820I Sorting information for number objects has been deleted.
Explanation: The server is retrying an operation during client file roll-off processing. Expiration retry processing occurs when the server database is full, the log is full, or sufficient server memory is not available to continue processing. System Action: The roll-off operation is retried. User Response: 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 information online or see Appendix A. Allocating Additional Server Memory. ANR0816I Expiration retry was successful.
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. User Response: None. 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. User Response: Contact your service representative. ANR0822I command: Filespace filespace name (fsId=filespace id) successfully renamed to new filespace name for node node name.
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. User Response: None. ANR0818I Waiting to retry expiration because of insufficient resources.
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 User Response: None. ANR0823E command: Filespace filespace name cannot be renamed to new filespace name, a filespace with this name already exists for node node name.
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. User Response: Use the QUERY ACTLOG command to examine messages issued prior to this one, which indicated the resource that is not available to the
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.
Chapter 3. Common and Platform Specfic Messages
85
ANR0824I ANR0831W
User Response: Reissue the command with a different target filespace name ANR0824I Delete Filespace filespace name (space-managed data) for node node name started. The number of objects deleted before the operation ended are reported in the message. System Action: The server process is ended and server operation continues. 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: A background server process has 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. System Action: The background process deletes space-managed objects for the specified file space while server operation continues. User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR0826I DELETE FILESPACE filespace name for node node name encountered a transaction failure.
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. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid combination of parameters. ANR0830W Management class class name in domain domain name used by node node name in file space filespace name is no longer active, or no longer has a BACKUP copy group: DEFAULT management class attributes will be used for expiration.
Explanation: A background server process that has been deleting file space data for the indicated node encountered a transaction failure. System Action: The server process is retried if the maximum number of retry attempts have not been exceeded. User Response: Transaction failure usually indicates that a database deadlock was detected during file space deletion. These deadlock conditions are sometimes encountered when multiple file space deletion processes are running at the same time. No action is required unless the DELETE FILESPACE terminates without completing the deletion process (see message ANR0828). ANR0827I DELETE FILESPACE filespace name will be retried for node node name.
Explanation: 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.
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. User Response: None. ANR0828W DELETE FILESPACE filespace name for node node name terminated before completion due to transaction failure: number of objects objects deleted.
Explanation: A background server process that has been deleting file space data for the indicated node is terminated prematurely because of transaction failure.
Explanation: During policy roll-off processing, the 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
86
IBM Tivoli Storage Manager: Messages
ANR0832W ANR0835W
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. 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 backup copy group. ANR0832W Management class class name in domain domain name used by node node name in filespace filespace name is no longer active, or no longer has an ARCHIVE copy group: DEFAULT management class attributes will be used for expiration. may use the DEFINE COPYGROUP, DEFINE 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. System Action: Server operation continues; the expiration process will be retried after the stated delay. 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. ANR0835W Management class class name in domain 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.
Explanation: During policy roll-off processing, the server found a client file copy whose management class or archive copy group no longer exists. System Action: The server obtains the DEFAULT management class for the specified domain and uses its archive copy group retention parameter 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. 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.
Explanation: During policy roll-off processing, the server found a management class or backup copy group or archive copy group that no longer exists. When a management class or backup copy group no longer exists, the number of backup client file copies that have been deleted using the default management class or the retention grace period is displayed in the message. When a management class or archive copy group no longer exists, the number of archive client files that have been deleted using the default management class or the retention grace period is displayed in the message. System Action: The server obtains the DEFAULT management class for the specified domain and uses its 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
Chapter 3. Common and Platform Specfic Messages
Explanation: During policy roll-off processing, the server found a client file copy whose management class or archive copy group no longer exists. The DEFAULT management class for the indicated policy domain does 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. User Response: No action is required. A policy administrator with authority over the specified domain
87
ANR0836W ANR0845E
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. User Response: None. ANR0840I Converting group table information for node node.
Explanation: The group table information for the displayed node is being converted. System Action: Server processing continues User Response: None. ANR0841I Conversion for node Node name will be undone.
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: The indicated node is converted. This status will be undone before the update archive operation can be performed. System Action: Processing continues. User Response: None. 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. Server processing continues. User Response: Check previous error messages. ANR0843I Command: the update archive operation for node node name completed successfully.
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. User Response: None. ANR0838I Pass pass of group table conversion processing beginning.
Explanation: The update archive operation for the specified node completed successfully. System Action: The update archive operation ends. User Response: None. ANR0844E Command: node name is not a backup-archive node.
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. User Response: None. ANR0839I Pass pass of group table conversion processing complete.
Explanation: The specified node name is not a backup-archive node. System Action: Processing fails for the command. Server operation continues. User Response: Reissue the command with a valid node name. ANR0845E Undo conversion processing for node node name did not complete (result).
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.
Explanation: UNDO ARCHCONVERSION was issued for the specified node. The specified error occurred. System Action: Processing continues.
88
IBM Tivoli Storage Manager: Messages
ANR0847I ANR0854E
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. ANR0851E Cannot start delete file space thread for node node name.
Explanation: The indicated DELETE FILESPACE process cannot be started on the server. Sufficient memory on the server may not be available. System Action: The DELETE FILESPACE command is ended and server processing continues. 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. ANR0852E Command: No matching file spaces found for node node name.
Explanation: The CLEANUP BACKUPGROUPS has finished processing, and has deleted the specified number of orphan groups and members. System Action: Processing continues. User Response: None. 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. ANR0849E Command: Not permitted for node Node Name - node of type SERVER.
Explanation: The server did not find any file spaces for the node indicated matching the names specified in the command. System Action: The server ends the command. User Response: Enter the command with file space names that refer to defined file spaces for the specified node. Note that file space names are case sensitive. Enter them by using exactly the same uppercase and lowercase characters that match the file space name defined on the server. Use the QUERY FILESPACE command to determine which file spaces are defined for a node on the server. ANR0853E Transaction failed in file space deletion, DELETE FILESPACE process aborted.
Explanation: 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.
Explanation: A database transaction fails while the server is deleting file space data. System Action: The server ends the file space deletion process. 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. ANR0854E Inventory file space query failure, DELETE FILESPACE process aborted.
Explanation: The indicated DELETE FILESPACE process cannot be started on the server. System Action: The DELETE FILESPACE command is ended and server processing continues. 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.
Explanation: The server encounters an error in querying the inventory database during a file space deletion process. System Action: The server ends the file space deletion process. 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
Chapter 3. Common and Platform Specfic Messages
89
ANR0855E ANR0861E
be isolated and resolved, contact your service representative. ANR0855E Server LOG space exhausted, DELETE FILESPACE process aborted. be isolated and resolved, contact your service representative. ANR0859E Data storage object erasure failure, DELETE FILESPACE process aborted.
Explanation: Insufficient server log space has been encountered during file space deletion processing. System Action: The server ends the file space deletion process. 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 can extend the size of the log by using the EXTEND LOG command. ANR0856E Server database space exhausted, DELETE FILESPACE process aborted.
Explanation: The server encounters an error in removing file copies from data storage during file space deletion processing. System Action: The server ends the file space deletion process. 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. 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.
Explanation: Insufficient server database space has been encountered during file space deletion processing. System Action: The server ends the file space deletion process. User Response: To increase the amount of database space available to the server, an authorized administrator can add log volumes using the DEFINE DBVOLUME command and can extend the size of the database using the EXTEND DB command. ANR0857E Data storage session failure, DELETE FILESPACE process aborted.
Explanation: The server encounters an internal error during file expiration processing. The number of files examined and deleted prior to the error are reported. A total error count is also displayed. System Action: The server ends the expiration process. 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. ANR0861E Transaction failed in expiration, inventory expiration aborted.
Explanation: The server encounters an error accessing data storage during file space deletion processing. System Action: The server ends the file space deletion process. 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. ANR0858E Inventory object search failure, DELETE FILESPACE process aborted.
Explanation: The server encounters a database transaction failure during policy roll-off processing. System Action: The server ends roll-off processing. 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.
Explanation: The server encounters an error accessing the inventory database during file space deletion processing. System Action: The server ends the file space deletion process. 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
90
IBM Tivoli Storage Manager: Messages
ANR0862E ANR0868E
ANR0862E Expiration processing suspended insufficient memory. memory, allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see Appendix A. Allocating Additional Server Memory. If the error cannot be isolated and resolved, contact your service representative. ANR0866E Expiration processing retries failed - no success after maximum retries retries.
Explanation: The server ends policy roll-off processing because sufficient server memory is not available. System Action: The server ends policy roll-off processing and server operation continues. 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. ANR0863E Expiration processing suspended insufficient DB space.
Explanation: Server policy roll-off processing ends because retry processing has not been successful in expiring client file copies from the server database. System Action: The server ends policy roll-off processing and server operation continues. 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 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 information online or see Appendix A. Allocating Additional Server Memory. If the error cannot be isolated and resolved, contact your service representative. ANR0867E Unable to open policy domain for node node name during server operation.
Explanation: The server ends policy roll-off processing because sufficient server database space is not available. System Action: The server ends policy roll-off processing and server operation continues. 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 can extend the size of the database using the EXTEND DB command. ANR0864E Expiration processing suspended insufficient LOG space.
Explanation: The server ends policy roll-off processing because sufficient server log space is not available. System Action: The server ends policy roll-off processing and server operation continues. 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 can extend the size of the log by using the EXTEND LOG command. ANR0865E Expiration processing failed - internal server error.
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 server operation continues. 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. ANR0868E Cannot find management class name for ID management class ID.
Explanation: Server retry processing during policy roll-off fails. System Action: The server ends policy roll-off processing. 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 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
Explanation: Policy roll-off processing on the server encounters an error while obtaining policy information. System Action: The server ends roll-off processing and server operation continues. 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
Chapter 3. Common and Platform Specfic Messages
91
ANR0869E ANR0875E
be isolated and resolved, contact your service representative. ANR0869E Cannot find policy domain for node node ID. 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. ANR0873E Invalid copy type encountered in expiring files: copytype ID
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 server operation continues. 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. ANR0870E Cannot find node name for node node ID.
Explanation: Policy roll-off processing on the server encounters a database error in obtaining copy group information. System Action: The server ends roll-off processing and server operation continues. 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. ANR0874E Backup object object.ID not found during inventory processing.
Explanation: Policy roll-off processing on the server encounters a database error in obtaining information for a client node. System Action: The server ends roll-off processing and server operation continues. 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. ANR0871E Cannot find file space name for node node ID, file space file space ID.
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. 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. ANR0875E Archive object object.ID not found during expiration processing.
Explanation: Policy roll-off processing on the server encounters a database error in obtaining information for a client node. System Action: The server ends roll-off processing and server operation continues. 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. ANR0872E Grace Period retention for domain domain name could not be obtained.
Explanation: Policy roll-off processing on the server encounters a database error in obtaining archive information in data storage. System Action: The server ends roll-off processing and server operation continues. 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.
Explanation: Policy roll-off processing on the server encounters a database error in obtaining GRACE PERIOD values for the specified policy domain. System Action: The server ends roll-off processing and server operation continues.
92
IBM Tivoli Storage Manager: Messages
ANR0876E ANR0884E
ANR0876E Data storage erasure failed during expiration processing. activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR0880E Filespace command: No matching file spaces.
Explanation: Policy roll-off processing on the server encounters a database error while deleting information from data storage. System Action: The server ends roll-off processing and server operation continues. 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. ANR0877E Copy type not backup for object object.ID.
Explanation: The server did not find any file space names matching the specifications entered in the filespace command. System Action: Server operation continues. 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.
Explanation: Policy roll-off processing on the server encounters a database error in accessing inventory information. System Action: The server ends roll-off processing and server operation continues. 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. ANR0878E Entry for backup object object.ID not found.
Explanation: The server encounters an internal error in accessing policy information. System Action: The operation is ended and server operation continues. User Response: Contact your service representative. ANR0882E Policy Error: Unable to open policy domain for node node name during client inventory query processing.
Explanation: Policy roll-off processing on the server encounters a database error in accessing inventory information. System Action: The server ends roll-off processing and server operation continues. 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. ANR0879E Error opening inventory file space query.
Explanation: The server encounters an internal error in accessing policy information. System Action: The client operation is ended and server operation continues. User Response: Contact your service representative. ANR0883E Cannot obtain node name for node node ID.
Explanation: The server encounters an internal error in accessing client node information. System Action: The operation is ended and server operation continues. User Response: Contact your service representative. ANR0884E Error code during deletion of sorting information for number objects.
Explanation: Policy roll-off processing on the server encounters a database error in accessing inventory information. System Action: The server ends roll-off processing and server operation continues. 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
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 previous export operations.
Chapter 3. Common and Platform Specfic Messages
93
ANR0885I ANR0890I
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. 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. Then restart the server. If the error cannot be isolated and resolved, contact your service representative. 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. ANR0887E Management class class name in domain domain name used by node node name in 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.
Explanation: During policy roll-off processing, the 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. User Response: For programming support, contact your service representative. ANR0888E SQL commands cannot be issued from the server console.
Explanation: The background import process to service the command import command is currently processing the policy information for management class management class name in domain domain name and policy set policy set name. The management class is imported under the name new management class name. During import processing, management classes defined as either DEFAULT or GRACE_PERIOD must be renamed so that the management class does not conflict with existing server policy conventions. Import processing is then able to import file data by using the renamed management class. System Action: Import processing for the command continues. User Response: None. However, an administrator may want to examine the policy definitions for new management class name so they are aware of the management classes that may be used if the policy set containing this management class is activated. ANR0886E Management class class name in domain domain name used by node node name in 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.
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. System Action: The server ignores the command and continues processing. User Response: Issue the SQL command from an administrative client. 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. System Action: The server ignores the command and continues processing. 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, contact your service representative. ANR0890I Export/import command: Processing optionset optionset name.
Explanation: During policy roll-off processing, the 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 your service representative.
Explanation: The background export or import process to service the command export/import command is currently processing optionset definition information. System Action: Export or import processing for the command continues. User Response: None.
94
IBM Tivoli Storage Manager: Messages
ANR0891I ANR0900I
ANR0891I Export/import command: Copied number optionset definitions. additional storage to the server. For details, issue HELP MEMORY to display the information online or see Appendix A. Allocating Additional Server Memory. 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.
Explanation: The background export or import process to service the command export/import command copies number client optionset 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. System Action: Export or import processing for the command completes. Server operation continues. User Response: None. ANR0892I Export command: No matching optionsets found for exporting.
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. System Action: Processing continues. User Response: None. ANR0898I Node Node name has (Filespace count) 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).
Explanation: The background export process does not find any client optionsets for export command. System Action: The export process continues and no optionsets from the server. User Response: None. ANR0893I Are you sure that you want to accept the current system date as valid ?
Explanation: This message is displayed when the ACCEPT DATE command has been issued to confirm that you want to accept the date on the system as valid. 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 nt want to execute the command. ANR0894I Current system has been accepted as valid.
Explanation: The indicated update archive operation has completed processing a node for the UPDATE ARCHIVE SHOWSTATS command. The information displayed includes counts for the filespaces, directories and files. System Action: Processing continues. User Response: None. ANR0899I Node Node name has (Filespace count) filespaces. Command has deleted (Directory count) directories and found (File count) new files with no directories.
Explanation: This messages 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 User Response: None. ANR0895E Command: Cannot Start process name Process.
Explanation: The indicated update archive operation 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. System Action: Processing continues. User Response: None. ANR0900I Processing options file filespec.
Explanation: The indicated process cannot be started on the server. System Action: The specified command is ended and server processing continues. User Response: This usually indicates that sufficient server memory is not available on the server. Allocate
Explanation: At server initialization, the server is reading the server options file whose name is shown in the message.
Chapter 3. Common and Platform Specfic Messages
95
ANR0901W ANR0912I
System Action: The server reads and processes the options in this file. User Response: None. ANR0901W Invalid option statement found in file filespec. ANR0905W Options file filespec not found.
Explanation: At server initialization, the server is 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.
Explanation: While processing the server options file named, the server has encountered an invalid statement. The invalid statement type is shown in the message. The lines following this message provide more information. System Action: The server ignores the statement in error. Server initialization continues. The default value is used for any missing or ignored options. User Response: Ignore the error, or use a text editor to correct the error and restart the server. ANR0902W Unsupported keyword found in file filespec.
Explanation: At server initialization, the server is unable to process the server options file due to insufficient memory. System Action: Server initialization ends. User Response: Restart the server with more memory available. Refer to the Administrators Guide for your particular platform. ANR0910W Archive entries for nodeName are already converted.
Explanation: While processing the server options file 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. User Response: Ignore the error, or use a text editor to correct the error and restart the server. ANR0903W Excessive option statement found in file filespec.
Explanation: Archive entries for nodeName have already been converted to the description tables. They will not be converted again. System Action: Server operation continues. User Response: To force the reconversion of the archive entries for nodeName, use the FORCE=Yes 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: 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 Duplicate option statement found in file filespec.
Explanation: CONVERT ARCHIVE for the specified node completed successfully. The node can now query for archive objects specifying a non-wildcarded description. System Action: Processing continues. User Response: None. ANR0912I Undo conversion processing for node node name completed successfully. The node is no longer converted.
Explanation: While processing the server options file named, the server has encountered a duplicate statement of the type shown. System Action: The server ignores the duplicate statement. Server initialization continues. User Response: Ignore the error, or use a text editor to correct the error and restart the server.
Explanation: UNDO ARCHCONVERSION was issued for the specified node. The node will no longer use the archive description tables.
96
IBM Tivoli Storage Manager: Messages
ANR0913E ANR0922I
System Action: Processing continues. User Response: None. ANR0918E ANR0913E Archive conversion processing for node node name did not complete (result). Inventory operation for node node name terminated - lock conflict. or activate a policy set with fewer management classes.
Explanation: Archive conversion for the indicated node did not complete because of the specified result. System Action: Archive conversion ends. Server processing continues. 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: 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 size of the specified object exceeds the maximum size defined for that object. The server cannot handle the new object. System Action: The activity that generated this error fails. User Response: Determine why the new objects length exceeds the maximum specified for the object. Reduce the length of the object. ANR0915E Unable to open language language name for message formatting.
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. System Action: Server processing continues. User Response: If the error occurs during processing for an administrative command such as EXPORT NODE or RENAME FILESPACE, rename the filespace for the nodes in the list using a valid name. If found while processing a client request, contact your service representative. ANR0920I Tracing is now active to standard output.
Explanation: The server is unable to open the specified message repository. System Action: Server initialization continues with the default message repository. User Response: Ensure that a valid language is 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: In response to a TRACE START command, server trace records are being written to the standard output destination (usually the server console). System Action: None. User Response: None. ANR0921I Tracing is now active to file file spec.
Explanation: In response to a TRACE START command, server trace records are being written to the file named. System Action: None. User Response: None. ANR0922I Trace ended.
Explanation: The server has completed startup processing and is now ready for use. System Action: None. User Response: None. ANR0917W Session session number for node node name (client platform) - in domain domain name failed because of policy length.
Explanation: In response to a TRACE END command, server trace records are no longer being written. System Action: None. User Response: None.
Explanation: The client cannot handle very long policies. System Action: The client operation is ended and server operation continues. User Response: Upgrade the client to the latest level,
Chapter 3. Common and Platform Specfic Messages
97
ANR0923E ANR0939E
ANR0923E Tracing is inactive. 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.
Explanation: A TRACE END command has been entered, but tracing is not active. System Action: The command is ignored. User Response: If tracing is desired, use the TRACE ENABLE and TRACE START commands to activate server tracing. ANR0924E Tracing is already active to file file spec.
Explanation: A TRACE BEGIN command has been entered, but the server has insufficient memory available to activate tracing. System Action: The command is ignored.
Explanation: A TRACE BEGIN command has been entered, but tracing is already active to the file named. System Action: The command is ignored. 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.
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 TRACE BEGIN command has been entered, but tracing is already active to the standard output destination (usually the server console). System Action: The command is ignored. User Response: If the current trace output destination is acceptable, no action is required. Otherwise use the TRACE END command to stop tracing and then reissue the TRACE BEGIN command as desired. ANR0926E Missing or invalid TRACE command parameter.
Explanation: 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. ANR0937I Expiration process process ID is ending.
Explanation: The TRACE command issued contains an invalid parameter, or is missing a required parameter. System Action: The command is ignored. User Response: Reissue the command with the proper parameters. ANR0927E Unknown trace class keyword - class.
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. System Action: None. User Response: None. 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.
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. 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. System Action: The command is ignored.
Explanation: Export processing did not find the base object for the specified subfile. Export processing does not continue.
98
IBM Tivoli Storage Manager: Messages
ANR0940I ANR0949I
System Action: Export processing stops. Server operation continues. User Response: Audit the database to correct the entries. ANR0940I Cancel request accepted for process process ID. ANR0945W DiagnosticID: Transaction transaction ID was aborted for process process ID.
Explanation: An error is detected during transaction commit for the specified process. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The activity that generated this error fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR0946E Archive processing fails: Object objIdHi.objIdLo not found.
Explanation: A CANCEL PROCESS command has been entered for the specified process. Some processes will experience a delay before they terminate. This delay may be lengthy for processes that involve remote data movement. System Action: None. User Response: None. ANR0941I Command: Cancel for process process ID is already pending.
Explanation: A CANCEL PROCESS command has been entered for the specified process, but a cancel is already pending for that process. System Action: The server ignores the command. User Response: None. ANR0942E Command: Process process ID cannot be found.
Explanation: Archive processing fails because the specified object was not found. An archive request is completed in stages. The object may have been deleted by an archive delete request, delete filespace or expiration that began and completed between these stages. System Action: System processing continues. User Response: Check the client log for error and retry messages. Reissue the archive request if the retry failed. ANR0947E Error writing to trace file file spec.
Explanation: A CANCEL PROCESS command has been entered for the specified process, but the process is not active. Either the process has already ended or the wrong process number has been entered. System Action: The server ignores the command. User Response: If the wrong process number has been entered, reissue the command with the correct process number. ANR0943E Command: Process process ID could not be canceled.
Explanation: An error occurred while writing to the specified trace file. System Action: Trace is disabled. User Response: Check the file for proper access permissions, or for the out of space issue for the trace file. Once this is corrected, reissue the TRACE BEGIN command, specifying either the same or a different output file. ANR0948I Command: the update archive operation for node Node name has started as background process process ID.
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. User Response: None. ANR0944E Command: No active processes found.
Explanation: An update archive operation has started under the indicated background server process with the indicated process identifier. System Action: Server processing continues. User Response: None.
Explanation: A QUERY PROCESS command has been entered, and no processes are active. System Action: The server ignores the command. User Response: None.
ANR0949I
Command: the update archive operation 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.
Chapter 3. Common and Platform Specfic Messages
99
ANR0950I ANR0960I
System Action: Server processing continues. User Response: None. ANR0950I Command: the update archive operation for node Node name has been cancelled. System Action: The objects encryption keys are not modified. User Response: Contact your service representative. ANR0955I DELETE FILESPACE filespace name for node node name failed deletion because of a restartable restore session.
Explanation: The indicated update archive operation was cancelled. System Action: The update archive operation ends. Server processing continues. User Response: No action is required. An authorized administrator can re-issue the command at a later time, if appropriate. ANR0951I Command: the update archive operation for node Node name completed successfully.
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 ANR0958I CLEANUP BACKUPGROUPS evaluated objectcount group objects, found errorcount errors, and deleted deleted group objects with completion state state.
Explanation: An update archive operation completed successfully. System Action: The update archive operation ends. User Response: None. 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. User Response: None. ANR0953W Audit command: Redundant encryption keys for the archive object (object.ID) do not match.
Explanation: The CLEANUP BACKUPGROUPS utility ended with the presented state./p> System Action: Server operation continues. User Response: None. ANR0959I Conversion of grouping table is percent done percent complete.
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. User Response: Contact your service representative. ANR0954W Audit command: Redundant encryption keys for the backup object (object.ID) do not match.
Explanation: An internal data base table is being converted, and the conversion process is the indicated amount complete. System Action: Server processing continues. User Response: None. ANR0960I Process process ID waiting for mount point in device class device class name.
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.
Explanation: The process whose ID is shown has begun to wait for a mount point that can be used for a volume in the device class shown. System Action: The process waits for the mount point. User Response: Respond to any mount requests.
100
IBM Tivoli Storage Manager: Messages
ANR0961I ANR0981E
ANR0961I Process process ID waiting for multiple mount points in device class device class name. System Action: The process waits for the volume to become available. User Response: None. ANR0967I Process process ID waiting for access to output volume volume name.
Explanation: The process whose ID is shown has begun to wait for multiple mount points that can be used for a volume in the device class shown. System Action: The process waits for the mount points. User Response: Respond to any mount requests. ANR0962I Process process ID waiting for mount points in device classes device class name and device class name.
Explanation: The process whose ID is shown has begun to wait for availability of the output volume shown. System Action: The process waits for the volume to become available. User Response: None. ANR0969E The server database must be formatted and loaded or restored before the server can be started.
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. User Response: Respond to any mount requests. ANR0963I Process process ID waiting for mount of input volume volume name.
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: 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. ANR0980E The server database must be audited with FIX=YES before the server can be started.
Explanation: The process whose ID is shown has begun to wait for the mount of the input volume shown. System Action: The process waits for the mount. User Response: Respond to any mount requests. ANR0964I Process process ID waiting for mount of output volume volume name.
Explanation: The process whose ID is shown has begun to wait for the mount of the output volume shown. System Action: The process waits for the mount. User Response: Respond to any mount requests. ANR0965I Process process ID waiting for mount of scratch volume.
Explanation: The process whose ID is shown has begun to wait for the mount of a scratch volume. System Action: The process waits for the mount. User Response: Respond to any mount requests. ANR0966I Process process ID waiting for access to input volume volume name.
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. System Action: Server initialization stops. 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 process whose ID is shown has begun to wait for availability of the input volume shown.
Explanation: The server has been restarted after an incomplete RESTORE DB. In order to start the server,
Chapter 3. Common and Platform Specfic Messages
101
ANR0982E ANR0987I
you must restore to the database to a consistent state using the DSMSERV RESTORE DB command. System Action: Server initialization stops. User Response: Issue the DSMSERV RESTORE DB command. For complete details on this command, refer to the Administrators Reference. ANR0982E The server database must be initialized before the database can be loaded. ANR0985I Process process ID for process name running in the process state completed with completion state completion state at process start time.
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 to the Administrators Reference. ANR0983W 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: 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. System Action: None. User Response: If the completion state is FAILURE, then review the activity log and the event log to try to determine the cause of the failure. If the completion 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 Process process ID for process name 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.
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. User Response: Refer to installation instructions for specific information on precautionary measures that you may want to take to back up the database prior to upgrading it to the current server level. After you have taken these measures, start the server and specify the UPGRADEDB parameter. This parameter only needs to be specified once to start the server, and should NOT be included in any automated programs that start the server. ANR0984I Process process ID for process name started in the process state at process start time.
Explanation: 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. System Action: None. User Response: If the completion state is FAILURE, then review the activity log and the event log to try to determine the cause of the failure. If the completion 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. ANR0987I Process process ID for process name running in the process state processed items processed items with a completion state of completion 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. System Action: None. User Response: None.
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. System Action: None. User Response: If the completion state is FAILURE, then review the activity log and the event log to try to determine the cause of the failure. If the completion
102
IBM Tivoli Storage Manager: Messages
ANR0988I ANR0996W
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. ANR0988I Process process ID for process name running in the process state processed bytes processed bytes with a completion state of completion state at process start time. ANR0992I Server installation complete.
Explanation: The server installation procedure has completed successfully. The server is now available for normal operation. System Action: Server completes installation processing. User Response: None. ANR0993I Server initialization complete.
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. System Action: None. User Response: If the completion state is FAILURE, then review the activity log and the event log to try to determine the cause of the failure. If the completion 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. ANR0989E The server database must be loaded or restored before the server can be started.
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. User Response: None. ANR0994W This server has not been properly installed.
Explanation: The server was started for normal operation, but had not yet been installed. System Action: The server ends. 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.
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. System Action: Server initialization stops. 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: At server startup, the server has 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. System Action: The server ends. 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.
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. User Response: None. 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. User Response: None.
Explanation: At server startup, the server has discovered that the disk information was written by an earlier version of the server program and is not compatible with this version. System Action: The server ends. User Response: Install this version of the server to bring the information up to the level of the program being used.
Chapter 3. Common and Platform Specfic Messages
103
ANR1000I ANR1013I
ANR1000I Migration process process ID started for storage pool storage pool name automatically or manually, highMig=highMig value, lowMig=lowMig value, duration=duration. User Response: None. ANR1004I Server formatting complete, database ready for loading.
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. User Response: None. ANR1001I Migration process process ID ended for storage pool storage pool name.
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. System Action: Server completes formatting processing. User Response: The DSMSERV LOADDB or the DSMSERV RESTORE DB command is required to load the database before the server will be ready for use. For complete details on these commands, refer to the Administrators Reference. ANR1013I During a store operation, the server is switching to a next pool in the storage hierarchy. The next storage pool will inherit the simultaneous write configuration from the destination primary storage pool.
Explanation: 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. System Action: None. User Response: None. ANR1002I Migration for storage pool storage pool name will be retried in number of seconds seconds.
Explanation: If during a backup, archive, client migration, or server import operation, the server must write data to a next pool in a storage pool hierarchy, the following rules will apply: 1. If the destination storage pool specified in the management class copy group has one or more copy storage pools associated with it for simultaneous write operations: 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. d. If the primary storage pool specified in the management class copy group does not have copy pools associated with it for simultaneous write operations: 1) The server will write the data to the next storage pool. 2) 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
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: 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.
104
IBM Tivoli Storage Manager: Messages
ANR1014W ANR1024W
Guide for details about simultaneous write configurations. ANR1014W The copy storage pool pool name is either not available, or does not have enough space for a simultaneous write operation. ANR1021W Migration process process ID terminated for storage pool storage pool name storage media inaccessible.
Explanation: During migration for the indicated 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. User Response: None. ANR1022W Migration process process ID terminated for storage pool storage pool name excessive read errors encountered.
Explanation: During a backup, archive, client migration, or import operation that is using simultaneous write, the server cannot write data to the specified copy storage pool. Possible reasons include: v The storage pool is unavailable. v There is not enough space available in the specified copy 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. v If the value of the COPYCONTINUE attribute of the destination primary pool is NO, the server will fail the transaction and discontinue the operation. Refer to the Administrators Guide for details about the simultaneous write COPYCONTINUE attribute. User Response: Ensure the copy storage pool is set for READWRITE access. If needed, make more space available in the copy storage pool. After the problem is corrected, take one of the following actions: v If the value of the COPYCONTINUE attribute of the 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. v If the value of the COPYCONTINUE attribute of the 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, read errors occur that prevented the migration from continuing. System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration. User Response: If possible, correct the cause of the read errors. ANR1023W Migration process process ID terminated for storage pool storage pool name excessive write errors encountered.
Explanation: During migration for the indicated storage pool, write errors occur that prevent the migration from continuing. System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration. User Response: If possible, correct the cause of the write errors. ANR1024W Migration process process ID terminated for storage pool storage pool name - data transfer interrupted.
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. User Response: None.
Explanation: During migration for the indicated storage pool, a data transfer operation was interrupted and could not be continued. 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.
Chapter 3. Common and Platform Specfic Messages
105
ANR1025W ANR1032W
User Response: If possible, correct the cause of the interruption. ANR1025W Migration process process ID terminated for storage pool storage pool name insufficient space in subordinate storage pool. System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. User Response: If necessary, make more server database space available. ANR1029W Migration process process ID terminated for storage pool storage pool name - lock conflict.
Explanation: During migration for the indicated 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. System Action: The indicated migration process ends. The server waits for the retry period to expire and then 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 Migration process process ID terminated for storage pool storage pool name unable to move file to subordinate storage pool due to exclusion by size.
Explanation: During migration for the indicated storage pool, the server needs to obtain a lock that is not available. System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration. User Response: Wait for the server to retry the migration. ANR1030W Migration process process ID terminated for storage pool storage pool name - thread resource not available.
Explanation: During migration for the indicated 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. System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration. User Response: Use the UPDATE STGPOOL command to change the next storage pool maximum file size or to change the next storage pool target. ANR1027W Migration process process ID terminated for storage pool storage pool name sufficient recovery log space is not available.
Explanation: During migration for the indicated storage pool, the server cannot start a thread for the migration process. System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration. User Response: Wait for the server to retry the migration. If the error persists, it may indicate a shortage of server memory. ANR1031W Migration process process ID terminated for storage pool storage pool name sufficient memory is not available.
Explanation: During migration for the indicated storage pool, the server runs out of recovery log space. System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. User Response: If necessary, make more server recovery log space available. ANR1028W Migration process process ID terminated for storage pool storage pool name sufficient database space is not available.
Explanation: During migration for the indicated storage pool, there is not enough server memory available. System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. User Response: If necessary, make more memory available to the server. ANR1032W Migration process process ID terminated for storage pool storage pool name internal server error detected.
Explanation: During migration for the indicated storage pool, the server runs out of database space.
Explanation: During migration for the indicated storage pool, the server encounters an internal error.
106
IBM Tivoli Storage Manager: Messages
ANR1033W ANR1059I
System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration. User Response: Contact your service representative. ANR1033W Migration process process ID terminated for storage pool storage pool name transaction aborted. ANR1041I Space reclamation ended for volume volume name.
Explanation: Space reclamation for the volume named is complete. System Action: None. User Response: None. ANR1042I Space reclamation for storage pool storage pool name will be retried in number of seconds seconds.
Explanation: During migration for the indicated 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. System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. ANR1034W Files stored on volume volume name cannot be migrated - volume is offline or access mode is unavailable or destroyed.
Explanation: Because of a problem encountered 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. User Response: If possible, correct the condition that has stopped reclamation. ANR1043I Space reclamation retry delay ended; checking volume reclamation status for storage pool storage pool name.
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: 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. User Response: None. ANR1044I Removable volume volume name is required for space reclamation.
Explanation: During space reclamation processing, the server determines that a removable volume is required in order to complete processing. System Action: The server attempts to mount the removable volume. User Response: Respond to any mount request for the indicated volume. 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: 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. User Response: None.
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
Chapter 3. Common and Platform Specfic Messages
107
ANR1060W ANR1068W
trees specified by the administrator will be restored to the indicated destination. System Action: The indicated process is started. User Response: None. ANR1060W Error initiating space reclamation for storage pool storage pool name - lock conflict. 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. System Action: The indicated process is started. User Response: None. ANR1065I Restore of NAS node nodename, file system file system, started as process process ID by administrator administrator. A full image for this file system will be restored to destination destination.
Explanation: While attempting to initiate space reclamation for the indicated storage pool, the server needs to obtain a lock that is not available. System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again. User Response: Wait for the server to retry the reclamation. ANR1061W Error initiating space reclamation for storage pool storage pool name - sufficient memory is not available.
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. User Response: If necessary, make more memory available to the server. ANR1062W Error initiating space reclamation for storage pool storage pool name - internal server error detected.
Explanation: A restore is started for the indicated file system of a NAS node. The operation is initiated by the administrator shown. The restore will be performed using a full image of this file system. The file system will be restored to the indicated destination. System Action: The indicated process is started. User Response: None. ANR1066I Restore of NAS node nodename, file system file system, started as process process ID by administrator administrator. A full image plus a differential image for this file system will be restored to destination destination.
Explanation: During an attempt to initiate space reclamation for the indicated storage pool, an internal server error is encountered. System Action: Space reclamation stops. The server will wait for the retry period to expire and then tries the reclamation again. User Response: Contact your service representative.
Explanation: A restore is started for the indicated file system of a NAS node. The operation is initiated by the administrator shown. The restore will be performed using a full image plus a differential image of this file system. The file system will be restored to the indicated destination. System Action: The indicated process is started. User Response: None. ANR1067I Operation process process ID completed.
ANR1063I
Full backup of NAS node nodename, file system file system, started as process process ID by administrator administrator.
Explanation: The indicated operation completed. System Action: The indicated process ends. User Response: None. ANR1068W Operation process process ID terminated process cancelled.
Explanation: A full backup is started for the indicated file system of a NAS node. The operation is initiated by the administrator shown. System Action: The indicated process is started. User Response: None.
Explanation: During the indicated operation, a background process was cancelled. System Action: The indicated process ends.
108
IBM Tivoli Storage Manager: Messages
ANR1069E ANR1079I
User Response: None. ANR1069E Operation process process ID terminated insufficient number of mount points available for removable media. ANR1074E Operation process process ID terminated sufficient database space is not available.
Explanation: During the indicated operation, the server runs out of database space. System Action: The indicated process ends. User Response: If necessary, make more server database space available. ANR1075E Operation process process ID terminated lock conflict.
Explanation: During the indicated operation, the server could not allocate sufficient mount points for the volumes required. System Action: The indicated process ends. User Response: If necessary, make more mount points available. ANR1070E Operation process process ID terminated write errors encountered.
Explanation: During the indicated operation, the server needs to obtain a lock that is not available. System Action: The indicated process ends. User Response: Restart the operation. ANR1076E Operation process process ID terminated sufficient memory is not available.
Explanation: During the indicated operation, write errors prevent the operation from continuing. System Action: The indicated process ends. User Response: If possible, correct the cause of the errors and restart the operation. ANR1071E Operation process process ID terminated read errors encountered.
Explanation: During the indicated operation, not enough server memory is available. System Action: The indicated process ends. User Response: If necessary, make more memory available to the server, and then restart the operation. ANR1077E Operation process process ID terminated transaction aborted.
Explanation: During the indicated operation, read errors prevent the operation from continuing. System Action: The indicated process ends. User Response: If possible, correct the cause of the errors and restart the operation. ANR1072E Operation process process ID terminated insufficient space in destination storage pool.
Explanation: During the indicated operation, 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. System Action: The indicated process ends. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. ANR1078E Operation process process ID terminated internal server error detected.
Explanation: During the indicated operation, there is not enough space available in the destination storage pool. System Action: The indicated process ends. User Response: Make more space available in the storage pool and restart the operation. ANR1073E Operation process process ID terminated sufficient recovery log space is not available.
Explanation: During the indicated operation, the server encounters an internal error. System Action: The indicated process ends. User Response: Contact your service representative. ANR1079I Server-free backup of node nodename, file system file system, started as process process ID by administrator administrator.
Explanation: During the indicated operation, the server runs out of recovery log space. System Action: The indicated process ends. User Response: If necessary, make more server recovery log space available.
Explanation: The administrator initiates a server-free backup of the nodes file system. System Action: The indicated process is started.
Chapter 3. Common and Platform Specfic Messages
109
ANR1080W ANR1087E
User Response: None. ANR1080W Space reclamation is ended for volume volume name. The process is canceled. ANR1084E Space reclamation is ended for volume volume name. Excessive write errors were encountered.
Explanation: During space reclamation for the indicated volume, the process performing the reclamation has been canceled. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: None. ANR1081E Space reclamation is ended for volume volume name. Storage media is inaccessible.
Explanation: During space reclamation for the indicated volume, write errors occur that prevent reclamation from continuing. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: If possible, determine and correct the cause of the write errors. ANR1085E Space reclamation is ended for volume volume name. Data transfer was interrupted.
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 processes will continue the reclamation. User Response: None. ANR1082E Space reclamation is ended for volume volume name. There is an insufficient number of mount points available for removable media.
Explanation: During space reclamation for the indicated volume, a data transfer operation has been interrupted and cannot be continued. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: If possible, determine and correct the cause of the interruption. ANR1086E Space reclamation is ended for volume volume name. There is insufficient space in storage pool.
Explanation: During space reclamation for the indicated volume, the server could not allocate sufficient mount points for the volumes required. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: If necessary, make more mount points available. ANR1083E Space reclamation is ended for volume volume name. Excessive read errors were encountered.
Explanation: During space reclamation for the indicated volume, the server determines that data cannot be moved from the volume due to insufficient space on other volumes in the storage pool. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: Make more space available on other volumes in the storage pool. ANR1087E Space reclamation is ended for volume volume name. Sufficient recovery log space is not available.
Explanation: During space reclamation for the indicated volume, read errors occur that prevent reclamation from continuing. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: If possible, determine and correct the cause of the read errors.
Explanation: During space reclamation for the indicated volume, the server runs out of recovery log space. System Action: Space reclamation stops. User Response: If necessary, make more server recovery log space available.
110
IBM Tivoli Storage Manager: Messages
ANR1088E ANR1094E
ANR1088E Space reclamation is ended for volume volume name. Sufficient database space is not available. ANR1092E Space reclamation is ended for volume volume name. An internal server error was detected.
Explanation: During space reclamation for the indicated volume, the server runs out of database space. System Action: Space reclamation stops. User Response: If necessary, make more server database space available. ANR1089E Space reclamation is ended for volume volume name. There is a lock conflict.
Explanation: During space reclamation for the indicated volume, the server encounters an internal error. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: Contact your service representative. ANR1093E Space reclamation is ended for volume volume name. The transaction is ended.
Explanation: During space reclamation for the indicated volume, the server needed to obtain a lock that is not available. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: Wait for the server to try the reclamation again. ANR1090E Space reclamation is ended for volume volume name. Thread resource is not available.
Explanation: During space reclamation for the indicated volume, the server detected an error while attempting to commit a transaction. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. ANR1094E Invalid destination storage pool storage pool name specified for storage of an object using data mover data mover.
Explanation: During space reclamation for the indicated volume, the server cannot start a thread for the reclamation process. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: Wait for the server to try the reclamation again. If the error persists, it might indicate a shortage of server memory. ANR1091E Space reclamation is ended for volume volume name. Sufficient memory is not available.
Explanation: While attempting to store an object using the indicated data mover, the server determined that the indicated storage pool was invalid for this operation. The indicated storage pool is used because it is specified as the copy group destination of the assigned management class. This storage pool could be invalid for any of the following reasons: v The storage pool is not defined v The storage pool is a random-access storage pool and this operation requires a sequential-access storage pool v The storage pool is not a primary storage pool v The storage pool has a NATIVE or NONBLOCK data format, which is not supported for this operation v The storage pool is not a NONBLOCK data format, which is required for server-free operations v The data format of the storage pool does not match the data format of the data mover System Action: The operation fails. User Response: This message usually indicates a configuration problem with either the storage pool or the policy. Ensure that the destination storage pool has appropriate attributes, including data format, for this operation. Check the copy group of the assigned management class. If the destination is incorrect, either
Chapter 3. Common and Platform Specfic Messages
Explanation: During space reclamation for the indicated volume, there was not enough server memory available. System Action: Space reclamation of the volume stops. If other reclamation processes are running, these processes will continue the reclamation. User Response: If necessary, make more memory available to the server.
111
ANR1095E ANR1103E
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. ANR1099E Operation process process ID terminated thread resource not available.
Explanation: During the indicated operation, the server cannot start a thread. System Action: The indicated process ends. 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: 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. System Action: The operation fails. User Response: Allow the current operation to complete before starting a new operation for this node and file space. ANR1096E Operation process process ID terminated storage media inaccessible.
Explanation: 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. User Response: None. 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. System Action: None. User Response: None. ANR1102I Removable volume volume name is required for migration.
Explanation: During the indicated operation, a required volume cannot be mounted. System Action: The indicated process ends. User Response: If possible, correct the problem and restart the operation. ANR1097E Operation process process ID terminated data transfer interrupted.
Explanation: During migration processing, the server determines that a removable volume is required in order to complete processing. System Action: The server attempts to mount the removable volume. User Response: Respond to any mount request for the indicated volume. ANR1103E Operation process process ID terminated server-free input/output errors encountered.
Explanation: During the indicated operation, a data transfer operation is interrupted and cannot be continued. System Action: The indicated process ends. User Response: If possible, correct the problem and restart the operation. ANR1098E Operation process process ID terminated file deleted from data storage during retrieval.
Explanation: During the indicated operation, input/output errors were encountered which prevent the operation from continuing. System Action: Server processing continues. User Response: Check previous messages for problem determination information.
Explanation: During the indicated operation, a file was deleted from data storage during retrieval. System Action: The indicated process ends. User Response: None.
112
IBM Tivoli Storage Manager: Messages
ANR1104E ANR1110E
ANR1104E Operation process process ID terminated NDMP session errors encountered. v The storage pool is not a primary storage pool v The storage pool has a data format other than NATIVE or NONBLOCK System Action: The operation fails. User Response: This message usually indicates a configuration problem with either the storage pool or the policy. Ensure that the 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: During the indicated operation, the NDMP session with the NAS file server reported errors which prevent the operation from continuing. System Action: The indicated process ends. 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 assigned management class. This storage pool could be invalid for any of the following reasons: v The storage pool is not defined v The storage pool is not a primary storage pool v The storage pool has a data format other than NATIVE or NONBLOCK System Action: The operation continues because TOC creation is preferred, but not required. A TOC will not be created for the stored image object. User Response: This message usually indicates a configuration problem with either the storage pool or 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 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 creation is preferred, but not required. A TOC will not 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. 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.
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. System Action: The operation continues because TOC creation is preferred, but not required. A TOC will not 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. ANR1110E Command: A table of contents was requested, but there is no table of contents destination storage pool specified. The table of contents can not be created and the operation fails.
Explanation: While 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 assigned management class. This storage pool could be invalid for any of the following reasons: v The storage pool is not defined
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.
Chapter 3. Common and Platform Specfic Messages
113
ANR1115W ANR1124E
System Action: The operation fails. 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. If a TOC is not required, change the value of the TOC parameter on the command. ANR1115W Error initiating migration for storage pool storage pool name - lock conflict. User Response: None. ANR1121E Migration is ended for volume volume name - storage. Media is inaccessible.
Explanation: During migration for the indicated volume a required volume cannot be mounted. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. User Response: None. ANR1122E Migration is ended for volume volume name. An insufficient number of mount points are available for removable media.
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 the retry period to expire and then tries the migration again. User Response: Wait for the server to retry the migration. ANR1116W Error initiating migration for storage pool storage pool name - sufficient memory is not available.
Explanation: During migration for the indicated volume the server could not allocate sufficient mount points for the volumes required. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. User Response: If necessary, make more mount points available. ANR1123E Migration is ended for volume volume name. Excessive read errors were encountered.
Explanation: While trying to start migration for the indicated storage pool, there is not enough server memory available. System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again. User Response: If necessary, make more memory available to the server. ANR1117W Error initiating migration for storage pool storage pool name - internal server error detected.
Explanation: During migration for the indicated volume, read errors occurred that prevent the migration from continuing. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. User Response: If possible, correct the cause of the read errors. ANR1124E Migration is ended for volume volume name. Excessive write errors were encountered.
Explanation: While trying to start migration for the indicated storage pool, the server encounters an internal error. System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again. User Response: Contact your service representative. ANR1120W Migration is ended for volume volume name. The process is canceled.
Explanation: During migration for the indicated volume, write errors occurred that prevent the migration from continuing. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. User Response: If possible, correct the cause of the write errors.
Explanation: During migration for the indicated 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.
114
IBM Tivoli Storage Manager: Messages
ANR1125E ANR1133E
ANR1125E Migration is ended for volume volume name. Data transfer is interrupted. ANR1129E Migration is ended for volume volume name. Sufficient database space is not available.
Explanation: During migration for the indicated volume a data transfer operation was interrupted and could not be continued. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. User Response: If possible, determine and correct the cause of the interruption. ANR1126E Migration is ended for volume volume name. There is insufficient space in subordinate storage pools.
Explanation: During migration for the indicated volume pool, the server runs out of database space. System Action: Migration stops. User Response: If necessary, make more server database space available. ANR1130E Migration is ended for volume volume name. There is a lock conflict.
Explanation: During migration for the indicated volume, the server needs to obtain a lock that is not available. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. User Response: Wait for the server to try the migration again. ANR1131E Migration is ended for volume volume name. A thread resource is not available.
Explanation: During migration for the indicated volume, the server cannot move the data from the volume because there is not enough space on the next storage pool to hold it. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. 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. ANR1127E Migration is ended for volume volume name. - The server is unable to move files to subordinate storage pools because the files are too large.
Explanation: During migration for the indicated volume, the server cannot start a thread for the migration process. System Action: Migration of the volume stops. If other migration processes are running, these processes will 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 Migration is ended for volume volume name. Sufficient memory is not available.
Explanation: During migration for the indicated volume, the server cannot move the data from the volume because a file size is larger than allowed on the next storage pool. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. User Response: Use the UPDATE STGPOOL command to change the next storage pool maximum file size or to change the next storage pool target. ANR1128E Migration is ended for volume volume name. Sufficient recovery log space is not available.
Explanation: During migration for the indicated volume, there is not enough server memory available. System Action: Migration stops. User Response: If necessary, make more memory available to the server. ANR1133E Migration is ended for volume volume name. An internal server error is detected.
Explanation: During migration for the indicated volume, the server runs out of recovery log space. System Action: Migration stops. User Response: If necessary, make more server recovery log space available.
Explanation: During migration for the indicated volume, the server encounters an internal error. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. User Response: Contact your service representative.
Chapter 3. Common and Platform Specfic Messages
115
ANR1134E ANR1147W
ANR1134E Migration is ended for storage pool storage pool name. There is an insufficient number of mount points available for removable media. ANR1143W Move data process terminated for volume volume name - process canceled.
Explanation: During migration for the indicated storage pool the server could not allocate sufficient mount points in the next storage pool. System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again. User Response: If necessary, make more mount points available. ANR1135E Migration is ended for volume volume name. The transaction is ended.
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. User Response: None. ANR1144W Move data process terminated for volume volume name - storage media inaccessible.
Explanation: During migration for the indicated volume, the server detected an error while attempting to commit a transaction. System Action: Migration of the volume stops. If other migration processes are running, these processes will continue migration. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. ANR1140I Move data process started for volume volume name (process ID process ID).
Explanation: During move data processing for the indicated volume, a required volume cannot be mounted. System Action: The server ends the MOVE DATA command. User Response: None. ANR1145W Move data process terminated for volume volume name - insufficient number of mount points available for removable media.
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. User Response: None. ANR1141I Move data process ended for volume volume name.
Explanation: During move data processing for the indicated volume, the server could not allocate sufficient mount points for the volumes required. System Action: The server ends the MOVE DATA command. User Response: If necessary, make more mount points available. ANR1146W Move data process terminated for volume volume name - excessive read errors encountered.
Explanation: The MOVE DATA command for the volume shown completes. System Action: None. User Response: None. ANR1142I Moving data for collocation cluster cluster number of total clusters on volume volume name.
Explanation: During move data processing for the indicated volume, read errors occurred that prevented the move from continuing. System Action: The server ends the MOVE DATA command. User Response: If possible, correct the cause of the read errors and then reissue the MOVE DATA command. ANR1147W Move data process terminated for volume volume name - excessive write errors encountered.
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. System Action: None. User Response: None.
Explanation: During move data processing for the indicated volume, write errors occurred that prevented the move from continuing.
116
IBM Tivoli Storage Manager: Messages
ANR1148W ANR1154W
System Action: The server ends the MOVE DATA command. User Response: If possible, correct the cause of the write errors and then reissue the MOVE DATA command. ANR1148W Move data process terminated for volume volume name - data transfer interrupted. System Action: The server ends the MOVE DATA command. User Response: If necessary, make more server recovery log space available. ANR1152W Move data process terminated for volume volume name - sufficient database space is not available.
Explanation: During move data processing for the indicated volume a data transfer operation was interrupted and could not be continued. System Action: The server ends the MOVE DATA command. User Response: If possible, determine and correct the cause of the interruption. ANR1149W Move data process terminated for volume volume name - insufficient space in target storage pool.
Explanation: During move data processing for the indicated volume, the server runs out of database space. System Action: The server ends the MOVE DATA command. User Response: If necessary, make more server database space available. ANR1153W Move data process terminated for volume volume name - lock conflict.
Explanation: During move data processing for the indicated volume, the server cannot move the data from the volume, because there is not enough space on the destination storage pool to hold it. System Action: The server ends the MOVE DATA command. User Response: Make more space available in the next storage pool, or specify a storage pool with more space, and reissue the MOVE DATA command. ANR1150W Move data process terminated for volume volume name - unable to move file to target storage pool due to exclusion by size.
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. . System Action: The server ends the MOVE DATA 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 Move data process terminated for volume volume name - thread resource not available.
Explanation: During move data processing for the indicated volume, the server cannot move the data from the volume because a file size is larger than allowed on the next storage pool. System Action: The server ends the MOVE DATA command. User Response: Use the UPDATE STGPOOL command to change the next storage pool maximum file size or to change the next storage pool target, and then reissue the MOVE DATA command. ANR1151W Move data process terminated for volume volume name - sufficient recovery log space is not available.
Explanation: During move data processing for the indicated volume, the server cannot start a thread for the migration process. System Action: The server ends the MOVE DATA command. User Response: Reissue the MOVE DATA command. If the error persists, it may indicate a shortage of server memory.
Explanation: During move data processing for the indicated volume, the server runs out of recovery log space.
Chapter 3. Common and Platform Specfic Messages
117
ANR1155W ANR1163W
ANR1155W Move data process terminated for volume volume name - sufficient memory is not available. 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 move data processing for the indicated volume, there is not enough server memory available. System Action: The server ends the MOVE DATA command. User Response: If necessary, make more memory available to the server, and then reissue the MOVE DATA command. ANR1156W Move data process terminated for volume volume name - internal server error detected.
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 move data processing for the indicated volume, the server encounters an internal error. System Action: The server ends the MOVE DATA command. User Response: Contact your service representative. ANR1157I Removable volume volume name is required for move process.
Explanation: During move data or move node data processing, the server determines that the indicated removable volume is required in order to complete processing. System Action: The server attempts to mount the removable volume. User Response: Respond to any mount request for the indicated volume. ANR1160W Transaction was aborted for volume volume name.
Explanation: During reclamation, a file is encountered that was previously found to be damaged. If this file is part of an aggregate, the entire aggregate was previously marked damaged, possibly because an integrity error was detected for some other file within the aggregate. System Action: The damaged file is not moved. User Response: Audit the indicated volume with FIX=NO to verify that the file is damaged. The audit will reset the file status if the file is found to be undamaged during the audit. If the file is part of an aggregate, the audit will reset the aggregate status if the entire aggregate is found to be undamaged. If this volume is in a primary storage pool that has previously been backed up to a copy storage pool, attempt to restore damaged files by using the RESTORE STGPOOL command. ANR1163W Offsite volume volume name still contains files which could not be moved.
Explanation: An error was detected during transaction commit. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The activity that generated this error fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.
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
118
IBM Tivoli Storage Manager: Messages
ANR1165E ANR1168W
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. System Action: None. 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. v Make the primary volumes available and reissue a MOVE DATA command to reclaim the volume. v Delete the files by using the DELETE VOLUME command. If, 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. server. If this file is part of an aggregate, the process could not locate an undamaged copy of the aggregate to which the file belongs. System Action: The file will skipped and will not be moved from the offsite volume. User Response: The indicated storage pool is a primary pool that contains a damaged copy of the file. The only usable copy of the file may now only reside on the offsite volume that was involved in the move data process. If you bring this volume back onsite, you can recreate the file in the primary pool by using the RESTORE STGPOOL command. After the restore, you can reissue the MOVE DATA command. ANR1167E Space reclamation for offsite volume(s) 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 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 moved from the offsite volume. User Response: The indicated storage pool is a primary pool that contains a damaged copy of the file. The only usable copy of the file may now only reside on 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: The server has detected an error for the indicated file. System Action: The file will be marked damaged in the server database, and will not be accessed for future operations. If this file is part of an aggregate, the entire aggregate will be marked damaged. If a usable copy of the file exists in another storage pool, that copy may be accessed for future operations involving the file. User Response: If the indicated storage pool is a primary pool, and a usable copy of the file exists in a copy storage pool, you can recreate the file in the primary pool using the RESTORE STGPOOL command. If the indicated storage pool is a copy storage pool, it is possible that the primary copy of the file is usable, but was not accessed because the access mode for the primary storage pool or volume is unavailable. If this is the case, the primary copy of the file may be made accessible by changing the access mode of the primary pool or volume. ANR1166E Move Data for offsite volume cannot copy damaged file in storage pool storage pool name: Node node name, Type file type, File space filespace name, fsId filespace id, File name file name.
Explanation: 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 integrity error was detected for some other file within the aggregate. System Action: The damaged file will not be 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, you can also attempt to restore damaged files by using the
Chapter 3. Common and Platform Specfic Messages
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
119
ANR1169W ANR1174W
RESTORE STGPOOL command. ANR1169W Lock conflict on movement of offsite file - file is skipped. 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 moved from the offsite volume. User Response: The indicated storage pool is a 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: 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: 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 moved from the offsite volume. User Response: The indicated storage pool is a 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 RESTORE STGPOOL command. ANR1174W One or more cached files were not deleted on volume volume name.
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. 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: 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.
Explanation: A move data process for an offsite volume cannot locate a copy of the specified file in any
120
IBM Tivoli Storage Manager: Messages
ANR1175W ANR1211I
ANR1175W Volume volume name contains files which could not be reclaimed. messages that give additional information about the failed transaction. System Action: The server operation that encountered this error during data storage processing fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. ANR1186I Restore of node nodename, file system file system, started as process process ID by administrator administrator. A full image for this file system will be restored to destination destination.
Explanation: 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. User Response: v Use the UPDATE VOLUME command to set the volume access to readonly. v Try using the MOVE DATA command to manually reclaim the volume. v If files still exist on the volume, audit the volume using AUDIT VOLUME FIX=YES. v Try using the MOVE DATA command again. v Use the RESTORE VOLUME command to restore files marked damaged. ANR1176I Moving data for collocation set set number of total sets on volume volume name.
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. System Action: The indicated process is started. User Response: None. ANR1199I Removable volume volume name is required for audit process.
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. System Action: None. User Response: None. ANR1180W Access mode for volume volume name has been set to unavailable due to file read or integrity errors.
Explanation: During audit volume processing for the indicated volume, the server determines that a removable volume is required in order to complete processing. System Action: The server attempts to mount the removable volume. User Response: Respond to any mount request for the indicated volume. ANR1210I Backup of primary storage pool primary pool name to copy storage pool copy pool name started as process process ID.
Explanation: A process has been started to back up a primary storage pool to the indicated copy storage pool. 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. User Response: None. ANR1211I Backup preview of primary storage pool primary pool name to copy storage pool copy pool name started as process process ID.
Explanation: During processing of a storage pool volume, input/output or other errors occur that force the server to mark the volume unavailable for further processing. System Action: The server sets the volume status to unavailable. User Response: Correct the errors that set the volume to unavailable, or use the DELETE VOLUME command to remove it from the system. ANR1181E DiagnosticID: Data storage transaction transaction ID was aborted.
Explanation: A preview process has been started to back up a primary storage pool to the indicated copy storage pool. System Action: Preview information about the backup operation is collected and displayed, but files are not backed up.
Chapter 3. Common and Platform Specfic Messages
Explanation: A database transaction failed because of an error that was detected during data storage processing. This message should be preceded by other
121
ANR1212I ANR1221E
User Response: None. ANR1212I Backup process process ID ended for storage pool storage pool name. User Response: None. ANR1217E Command: Process process ID terminated insufficient number of mount points available for removable media.
Explanation: A backup process for the named primary storage pool has ended. System Action: None. User Response: None. ANR1213I Backup process process ID terminated for storage pool storage pool name - process canceled.
Explanation: During backup processing, the server could not allocate sufficient mount points for the volumes required. System Action: The indicated backup process ends. User Response: If necessary, make more mount points available. ANR1218E Command: Process process ID terminated excessive read errors encountered.
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. User Response: None. 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: During backup processing, read errors occur that prevent the backup from continuing. System Action: The indicated backup process ends. User Response: If possible, correct the cause of the read errors and reissue the backup command. ANR1219E Command: Process process ID terminated excessive write errors encountered.
Explanation: During backup processing, write errors occur that prevent the backup from continuing. System Action: The indicated backup process ends. User Response: If possible, correct the cause of the write errors and reissue the backup command. ANR1220E Command: Process process ID terminated data transfer interrupted.
Explanation: Backup processing for the specified storage pool has ended with the results shown. System Action: None. User Response: Examine previous messages to determine whether all backup processes ended successfully. ANR1215I Backup preview of primary storage pool primary pool name to copy storage pool copy pool name has ended. Files Backed Up: number of files, Bytes Backed Up: number of bytes.
Explanation: During backup processing, a data transfer operation was interrupted and could not be continued. System Action: The indicated backup process ends. User Response: If possible, correct the cause of the interruption and reissue the backup command. ANR1221E Command: Process process ID terminated insufficient space in target copy storage pool.
Explanation: Backup preview processing for the specified storage pool has ended with the results shown. System Action: None. User Response: None. ANR1216E Command: Process process ID terminated storage media inaccessible.
Explanation: During backup processing, the server cannot copy data to the copy storage pool because not enough space is available in the copy storage pool. System Action: The indicated backup process ends. User Response: Make more space available in the copy storage pool and reissue the backup command, or reissue the backup command and specify another copy storage pool with more space.
Explanation: During backup processing, a required volume could not be mounted. System Action: The indicated backup process ends.
122
IBM Tivoli Storage Manager: Messages
ANR1222E ANR1231I
ANR1222E Command: Process process ID terminated sufficient recovery log space is not available. User Response: Contact your service representative. ANR1228I Removable volume volume name is required for storage pool backup.
Explanation: During backup processing, the server runs out of recovery log space. System Action: The indicated backup process ends. User Response: If necessary, make more server recovery log space available. ANR1223E Command: Process process ID terminated sufficient database space is not available.
Explanation: During processing of a BACKUP STGPOOL command, the server determines that a removable volume is required. System Action: Unless this is a preview process, the server attempts to mount the removable volume. User Response: Respond to any mount request for the indicated volume. ANR1229W 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 backup processing, the server runs out of database space. System Action: The indicated backup process ends. User Response: If necessary, make more server database space available. ANR1224E Command: Process process ID terminated lock conflict.
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 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: During backup processing, the server needs to obtain a lock that is not available. System Action: The indicated backup process ends. User Response: Reissue the backup command. ANR1225E Command: Process process ID terminated thread resource not available.
Explanation: During backup processing, the server cannot start a thread. System Action: The indicated backup process ends. 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: 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 v The primary file has been identified as having data-integrity errors during a previous operation User Response: None.
Explanation: During backup processing, not enough server memory is available. System Action: The indicated backup process ends. User Response: If necessary, make more memory available to the server, and then reissue the backup command. ANR1227E Command: Process process ID terminated internal server error detected.
ANR1231I
Explanation: During backup processing, the server encounters an internal error. System Action: The indicated backup process ends.
Restore preview of primary storage pool primary pool name started as process process ID.
Explanation: A preview process has been started to restore a primary storage pool.
Chapter 3. Common and Platform Specfic Messages
123
ANR1232I ANR1239I
System Action: Preview information about the restore operation is collected and displayed, but files are not 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 User Response: None. ANR1232I Restore of volumes in primary storage pool primary pool name started as process process ID. 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. User Response: None. ANR1237I 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. System Action: Noncached files that reside on selected volumes in the primary storage pool are restored. User Response: None. ANR1233I Restore preview of volumes in primary storage pool primary pool name started as process process ID.
Explanation: During restore of volumes in the indicated primary storage pool, a process performing the restore has been canceled. System Action: If other restore processes are executing for the volumes, these processes continue. User Response: None. ANR1238I Restore of 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: A preview process has been started to restore one or more volumes in the indicated primary storage pool. System Action: Preview information about the restore operation is collected and displayed, but files are not restored. The restore preview includes noncached files that reside on selected volumes in the primary storage pool. User Response: None. ANR1234I Restore process process ID ended for storage pool storage pool name.
Explanation: Restore processing for the specified storage pool has ended with the results shown. System Action: None. User Response: Examine previous messages to 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: A restore process for the named primary storage pool has ended. System Action: None. User Response: None. ANR1235I Restore process process ID ended for volumes in storage pool storage pool name.
Explanation: Restore preview processing for the specified storage pool has ended with the results shown. System Action: None. User Response: None.
Explanation: A restore process for volumes in the named primary storage pool has ended. System Action: None. User Response: None.
124
IBM Tivoli Storage Manager: Messages
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. ANR1245E Command: Process process ID terminated excessive write errors encountered.
Explanation: During restore processing, write errors occur that prevent the restore from continuing. System Action: The indicated restore process ends. User Response: If possible, correct the cause of the write errors and reissue the restore command. ANR1246E Command: Process process ID terminated data transfer interrupted.
Explanation: Restore processing for volumes in the specified storage pool has ended with the results shown. System Action: None. User Response: Examine previous messages to 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: During restore processing, a data transfer operation was interrupted and could not be continued. System Action: The indicated restore process ends. User Response: If possible, correct the cause of the interruption and reissue the restore command. ANR1247E Command: Process process ID terminated insufficient space in target primary storage pool.
Explanation: Restore preview processing for volumes in the specified storage pool has ended with the results shown. System Action: None. User Response: None. ANR1242E Command: Process process ID terminated storage media inaccessible.
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. System Action: The indicated restore process ends. 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.
Explanation: During restore processing, a required volume could not be mounted. System Action: The indicated restore process ends. User Response: None. ANR1243E Command: Process process ID terminated insufficient number of mount points available for removable media.
Explanation: During restore processing, the server runs out of recovery log space. System Action: The indicated restore process ends. User Response: If necessary, make more server recovery log space available. ANR1249E Command: Process process ID terminated sufficient database space is not available.
Explanation: During restore processing, the server could not allocate sufficient mount points for the volumes required. System Action: The indicated restore process ends. User Response: If necessary, make more mount points available. ANR1244E Command: Process process ID terminated excessive read errors encountered.
Explanation: During restore processing, the server runs out of database space. System Action: The indicated restore process ends. User Response: If necessary, make more server database space available.
Explanation: During restore processing, read errors occur that prevent the restore from continuing. System Action: The indicated restore process ends. User Response: If possible, correct the cause of the read errors and reissue the restore command.
Chapter 3. Common and Platform Specfic Messages
125
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. ANR1256W ANR1251E Command: Process process ID terminated thread resource not available. Volume volume name contains files that could not be restored.
Explanation: During restore processing, the server needs to obtain a lock that is not available. System Action: The indicated restore process ends. User Response: Reissue the restore command.
Explanation: During restore processing, the server cannot start a thread. System Action: The indicated restore process ends. 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 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. System Action: None. 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 Storage pool backup 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 restore processing, there is not enough server memory available. System Action: The indicated restore process ends. User Response: If necessary, make more memory available to the server; and then reissue the restore command. ANR1253E Command: Process process ID terminated internal server error detected.
Explanation: During restore processing, the server encounters an internal error. System Action: The indicated restore process ends. User Response: Contact your service representative. ANR1254I Removable volume volume name is required for restore processing.
Explanation: During processing of a RESTORE STGPOOL or RESTORE VOLUME command, the server determines that a removable volume is required. System Action: Unless this is a preview process, the server attempts to mount the removable volume. User Response: Respond to any mount request for the indicated volume. ANR1255W Files on volume volume name cannot be restored - access mode is unavailable or offsite.
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 integrity error was detected for some other file within the aggregate. System Action: The damaged file will not be backed up. User Response: Audit the indicated volume with FIX=YES. The audit will verify whether or not the file
Explanation: During processing of a RESTORE STGPOOL or RESTORE VOLUME command, files on a copy storage pool volume cannot be restored because of the volumes access mode.
126
IBM Tivoli Storage Manager: Messages
ANR1258W ANR1265E
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 aggregate, the audit will reset the aggregate status if 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. 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.
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: The background process to service the command command has completed successfully. System Action: Processing for the 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. User Response: None. ANR1264I Command: Processing canceled before completion.
Explanation: The background process to service the command command has been canceled with the CANCEL PROCESS command. System Action: Processing for the command command ends. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message. User Response: None. ANR1265E Salvage volume command: Processing terminated abnormally - error accessing data storage.
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: The server encountered an internal error in accessing data storage while executing a salvage volume operation. System Action: The 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 you find and resolve the error, retry the operation. If you cannot find the error, contact your service representative for assistance in resolving the problem.
Chapter 3. Common and Platform Specfic Messages
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
127
ANR1266E ANR1274I
ANR1266E Salvage volume command: Processing terminated abnormally - volume not a storage pool volume. User Response: None. ANR1271I Salvage volume command: * number bytes recovered from volume volume.
Explanation: The server encountered an internal error 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. System Action: The command command operation is ended and server operation continues. User Response: Issue the command with a valid volume name. ANR1267I Salvage volume command: Processed number volume(s).
Explanation: The background process to service the command Salvage volume command recovered a file from the volume volume. The number of bytes recovered from the volume is listed. System Action: Salvage processing for the command completes. Server operation continues. User Response: None. ANR1272I Salvage volume command: * File is complete - it began and ended on volume volume.
Explanation: The background process to service the command Salvage volume command inspected number input volumes. System Action: Salvage processing for the command completes. Server operation continues. User Response: None. ANR1268I Salvage volume command: Recovered number byte(s).
Explanation: The background process to service the command Salvage volume command recovered a file from the volume volume. The file was completely contained on volume. System Action: Salvage processing for the command completes. Server operation continues. User Response: None. ANR1273I Salvage volume command: * File is incomplete - it began on volume volume but did not end.
Explanation: The background process to service the command Salvage volume command recovered number bytes worth of data. System Action: Salvage processing for the command completes. Server operation continues. User Response: None. ANR1269I Salvage volume command: Recovered number file(s).
Explanation: The background process to service the command Salvage volume command recovered a file from 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. System Action: Salvage processing for the command completes. Server operation continues. User Response: None. ANR1274I Salvage volume command: * File is incomplete - it ended on volume volume but did not begin there.
Explanation: The background process to service the command Salvage volume command recovered number files. System Action: Salvage processing for the command completes. Server operation continues. User Response: None. ANR1270I Salvage volume command: File (internal file identifierinternal file identifier) recovered.
Explanation: The background process to service the command Salvage volume command recovered a file from the volume volume. The file was not completely contained on volume. Although the file ended on this volume, it spanned in from a different volume. System Action: Salvage processing for the command completes. Server operation continues. User Response: None.
Explanation: The background process to service the command Salvage volume command recovered a file. The new file was given a new, system generated name based on the internal file identifier and the name of the volume from which the file was recovered. The internal file identifier is the identifier by which the file was known to the server before the file was deleted. System Action: Salvage processing for the command completes. Server operation continues.
128
IBM Tivoli Storage Manager: Messages
ANR1275I ANR1284I
ANR1275I Salvage volume command: * File is incomplete - it did not began or end on volume volume. value based on current sequential volume information. User Response: None. ANR1280E Command: Process process ID terminated transaction aborted.
Explanation: The background process to service the command Salvage volume command recovered a file from the volume volume. The file was not completely contained on volume. It spanned in from one volume and spanned out to a another. System Action: Salvage processing for the command completes. Server operation continues. User Response: None. ANR1276E Command: Process terminated - sufficient memory is not available.
Explanation: During backup processing, 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. System Action: The indicated backup process ends. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. ANR1281E Command: Process process ID terminated transaction aborted.
Explanation: During salvage processing, not enough server memory is available. System Action: The salvage process ends. User Response: If necessary, make more memory 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.
Explanation: During restore processing, 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. System Action: The indicated restore process ends. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. ANR1282I Logical occupancy is incorrect for storage pool storage pool name. Logical occupancy is being reset.
Explanation: The background process to service the command Salvage volume command was unable to recover any files because the default management class in the active policy set in policy domain does not contain an archive copy group. System Action: The salvage process ends. User Response: Add an archive copy group to the default management class in the active policy set of the specified domain, and then reissue the salvage command. ANR1278I Occupancy is incorrect for storage pool storage pool name. Occupancy is being reset.
Explanation: The server has detected incorrect logical occupancy information. System Action: The server recalculates the logical occupancy value based on current storage pool information. User Response: None. ANR1283I File count is incorrect for storage pool storage pool name - file count is being reset.
Explanation: The server has detected incorrect occupancy information. System Action: The server recalculates the occupancy value based on current storage pool information. User Response: None. ANR1279I Occupancy is incorrect for volume name volume name. Occupancy 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. User Response: None. ANR1284I Move node data started as process process ID.
Explanation: The server has detected incorrect occupancy information. System Action: The server recalculates the occupancy
Explanation: A process has been started to move data by node.
Chapter 3. Common and Platform Specfic Messages
129
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. ANR1296W Storage pool storage pool name does not contain WORM FILE volumes.
Explanation: A move node data process for the named storage pool has ended. System Action: None. User Response: None. ANR1289I Move node data process process ID terminated for the storage pool storage pool name - process canceled.
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. 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: 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. User Response: None. 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 unreadable files, Unreadable Bytes: number of bytes in unreadable files.
Explanation: Move node processing for the specified storage pool has ended with the displayed results. System Action: None. User Response: Examine previous messages to 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.
Explanation: Defining storage pools with RECLAMATION=SNAPLOCK is only supported on a server with archive data protection enabled.
130
IBM Tivoli Storage Manager: Messages
ANR1298W ANR1306I
System Action: The define storage pool command fails. User Response: Define the storage pool with RECLAMATIONTYPE=THRESHOLD on this server. Or else enable archive data retention protection on this server, and try the command again. ANR1298W 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. ANR1301I VARY OFFLINE command initiated for disk volume volume name.
Explanation: A VARY OFFLINE command has caused a vary-off process to be started for the volume specified. System Action: The volume is varied offline. User Response: None. ANR1302E Disk volume volume name is already online.
Explanation: A VARY ONLINE command specified a volume that was already online. System Action: None. User Response: None. ANR1303E Disk volume volume name is already offline.
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. System Action: The server continues operation, and the object is logically deleted within the server, but continues to occupy space in the Centera device. User Response: The server can continue to operate in spite of this error. Centera service can be required if the volume of unpurged objects becomes a problem. ANR1299E The server encountered an invalid storage format while attempting a partial object retrieve for object seg_id_hi,seg_id_lo.
Explanation: A VARY OFFLINE command specified a volume that was already offline. System Action: None. User Response: None. ANR1304E Disk volume volume name is currently in use.
Explanation: A VARY OFFLINE command specified a volume that is currently in use and cannot be varied offline at this time. System Action: None. 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: 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: The specified volume has been varied online as the result of a VARY ONLINE command. System Action: None. User Response: None. ANR1306I Disk volume volume name varied online (read-only).
Explanation: A VARY ONLINE command has caused a vary-on process to be started for the volume specified. System Action: The volume is varied online. User Response: None.
Explanation: The specified volume has been varied online in read-only mode as the result of a VARY ONLINE command. System Action: None. User Response: None.
Chapter 3. Common and Platform Specfic Messages
131
ANR1307I ANR1320W
ANR1307I Disk volume volume name varied offline. ANR1313E Vary-on failed for disk volume volume name - unsupported block size (block size).
Explanation: The specified volume has been varied offline as the result of a VARY OFFLINE command. System Action: None. User Response: None. ANR1308W Storage agent not sychronized with server - restart needed.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the volume is formatted with a block size that cannot be used. System Action: The volume is not varied online. User Response: Reformat the disk with a block size that is an evenly divisible by 4096. ANR1314E Vary-on failed for disk volume volume name - reduced capacity (was count blocks, now count blocks.
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. 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 the size of the volume does not match the size expected. System Action: The volume is not varied online. User Response: Restore the volume or otherwise correct the disk volume size, and reissue the command. ANR1315E Vary-on failed for disk volume volume name - invalid label block.
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 Vary-on failed for disk volume volume name - unable to access disk device.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the label block of the volume is invalid or cannot be read. System Action: The volume is not varied online. User Response: Restore or reformat the disk volume. ANR1316E Vary-on failed for disk volume volume name - internal error detected.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the server is unable to access the disk. System Action: The volume is not varied online. User Response: Attempt to determine the cause of the inability to access the volume and correct the problem. ANR1312E Vary-on failed for disk volume volume name - error reading disk.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but fails due to an internal server error. System Action: The volume is not varied online. User Response: Contact your service representative. ANR1320W Vary-on not possible for disk volume volume name - access state is unavailable.
Explanation: A VARY ONLINE command has been issued for the disk volume specified but the server encounters an error reading the disk. System Action: The volume is not varied online. User Response: Attempt to determine the cause of the read error and correct the problem.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the status of the volume is unavailable. System Action: The volume is not varied online. User Response: If necessary, use the UPDATE VOLUME command to change the status of the volume, and reissue the command.
132
IBM Tivoli Storage Manager: Messages
ANR1321W ANR1343I
ANR1321W Vary-on not possible for disk volume volume name - access state is destroyed. 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: A VARY ONLINE command has been issued for the disk volume specified, but the status of the volume is destroyed. System Action: The volume is not varied online. User Response: If necessary, use the UPDATE VOLUME command to change the status of the volume, and reissue the command. ANR1330E 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: The scratch volume specified has been added to the storage pool shown. System Action: None. User Response: None. ANR1341I Scratch volume volume name has been deleted from storage pool storage pool name.
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. 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: The scratch volume specified is no longer in use and has been removed from the indicated storage pool. System Action: None. User Response: None. 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: This message indicates the expected values when an invalid frame is detected. System Action: None. User Response: If contacting support, please provide the information from this message. ANR1339W Session session id underestimated a size allocation request - additional spaceMB more space was allocated to allow the operation to continue.
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. System Action: None. User Response: None. ANR1343I Unable to delete scratch volume volume name.
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. User Response: The installed version of the client for this node should be evaluated. In most cases, if a client
Explanation: A scratch volume cannot be deleted from the server and returned to scratch at this time because all the locks have not be released. A number of retries have been attempted. System Action: None User Response: The scratch volume will be automatically deleted when the server is restarted. Or, you may manually delete this volume later, using the DELETE VOLUME command.
Chapter 3. Common and Platform Specfic Messages
133
ANR1344I ANR1366W
ANR1344I Volume volume name cannot be reused. Remove the volume from server storage. System Action: None. User Response: None. ANR1362I Output volume volume name closed (full).
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. ANR1345I Volume volume name cannot be reused by other applications and will remain in the storage pool.
Explanation: During a sequential data operation, the volume specified has been closed because the volume is full. System Action: None. User Response: None. 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. System Action: None. User Response: None. ANR1364I Input volume volume name closed.
Explanation: During a sequential data operation, the volume specified has been closed because the operation is complete. System Action: None. User Response: None. ANR1365I Volume volume name closed (end reached).
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. ANR1360I Output volume volume name opened (sequence number sequence number).
Explanation: During a sequential data operation, the volume specified has been closed because processing of the volume is complete. System Action: None. User Response: None. ANR1366W Input volume volume name contains an invalid identifier.
Explanation: During a sequential data operation, the volume specified has been opened for output as the volume number shown. System Action: None. User Response: None. ANR1361I Output volume volume name closed.
Explanation: During a sequential data operation, the volume specified has been mounted but contains an invalid identifier. System Action: The volume is not used. User Response: Make sure you specified the correct volume for the operation. If a LOADDB operation was being performed on MVS, the command syntax may be specified by using a ddname or by specifying a device class name. You must use the same method that was used when the database was originally dumped. If you did not, this error message will be displayed. Try loading the data base by using the other method of syntax (ddname).
Explanation: During a sequential data operation, the volume specified has been closed because the export or dump is complete.
134
IBM Tivoli Storage Manager: Messages
ANR1367W ANR1404W
ANR1367W Import volume volume name was written by a different export process. ANR1400W Mount request denied for volume volume name - mount canceled.
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.
Explanation: The volume shown cannot be mounted because the mount request has been canceled. System Action: The volume is not mounted. User Response: None. ANR1401W Mount request denied for volume volume name - mount failed.
Explanation: The volume shown cannot be mounted 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. System Action: The volume is not mounted. 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 Mount request denied for volume volume name - volume unavailable.
Explanation: During a sequential data operation, the volume specified has been mounted but contains the wrong volume sequence number. System Action: The volume is not used. User Response: Supply the volume with the proper sequence number. The volume history file can help you choose the correct volume. ANR1369E Input volume volume name contains Version 1 dump.
Explanation: The volume shown cannot be mounted because it is not available. System Action: The volume is not mounted. User Response: None. ANR1403W Scratch volume mount request denied mount canceled.
Explanation: During a sequential data operation, the 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: A scratch volume cannot be mounted because the mount request has been canceled. System Action: The scratch volume is not mounted. User Response: None. ANR1404W Scratch volume mount request denied mount failed.
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 ended and server operation continues. User Response: Make more mount points available.
Explanation: A scratch volume cannot be mounted 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. System Action: The scratch volume is not mounted. User Response: If the device specifications (for example, DEFINE DEVCLASS) are in error, correct them and reissue the command that requested the volume to be mounted.
Chapter 3. Common and Platform Specfic Messages
135
ANR1405W ANR1416W
ANR1405W Scratch volume mount request denied no scratch volume available. ANR1411W Access mode for volume volume name now set to read-only due to write error.
Explanation: A scratch volume cannot be mounted because no scratch volume is available. System Action: The scratch volume is not mounted. User Response: None. ANR1406E Simultaneous write operation could not release all the acquired mount points.
Explanation: Because of an unrecoverable write error on the volume shown, the status of the volume has been set to read-only. System Action: None. User Response: None. ANR1412W Volume volume name access mode is unavailable.
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. User Response: None. ANR1409W Volume volume name already in use skipped.
Explanation: At server startup, the status of the indicated volume is unavailable. System Action: None. User Response: None. ANR1413W Volume volume name access mode is read-only.
Explanation: At server startup, the status of the indicated volume is read-only. System Action: None. User Response: None. ANR1414W Volume volume name access mode is read-only due to previous write error.
Explanation: During an export or database backup, a volume cannot be used because it is already defined in a storage pool, or has already been used by the current operation, or has been previously used by an export or database backup operation (as recorded in the volume history) or is in use by another process. System Action: The operation continues and the volume is skipped. User Response: Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export or database backup operations. If no volume names are displayed using the query commands described above, ensure that the volume identified in this message has not been specified or used more than once in the operation being performed. ANR1410W Access mode for volume volume name now set to unavailable.
Explanation: At server startup, the status of the 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: None. User Response: None. ANR1415W Volume volume name access mode is destroyed.
Explanation: At server startup, the status of the indicated volume is destroyed. System Action: None. User Response: None. ANR1416W Volume volume name access mode is offsite.
Explanation: The status of the volume shown has been set to unavailable. System Action: None. User Response: None.
Explanation: At server startup, the status of the indicated volume is offsite. System Action: None. User Response: None.
136
IBM Tivoli Storage Manager: Messages
ANR1417W ANR1425W
ANR1417W Access mode for volume volume name now set to read-only due to excessive read error. ANR1421W Read access denied for volume volume name - volume offline.
Explanation: Because of an numerous read errors on the volume shown, the status of the volume has been set to read-only. System Action: None. 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 attempt to access the named volume for reading failed because the volume is offline. System Action: The volume is not used. User Response: None. ANR1422W Read access denied for volume volume name - volume access mode=offsite.
Explanation: An attempt to access the named volume for reading failed because the volume status is offsite. System Action: The volume is not used for read access. User Response: None. ANR1423W Scratch volume volume name is empty but will not be deleted - volume access mode is offsite.
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. System Action: The server ignores the command and continues processing. User Response: Issue the command from an administrative client. ANR1419E command name : FROMDATE must be specified when FROMTIME is specified.
Explanation: The named scratch volume is empty but will not be deleted at this time because the access mode is offsite. System Action: The volume is not deleted. User Response: After bringing the volume onsite, change the access mode to read-only so the volume will be deleted. ANR1424W Read access denied for volume volume name - volume access mode=destroyed.
Explanation: A command that supports the FROMDATE and FROMTIME parameters was issued with the FROMTIME parameter specified, but without the FROMDATE parameter. When the FROMTIME parameter is used, the FROMDATE parameter must be specified. System Action: The server ignores the command and continues processing. User Response: Reissue the command with both the FROMDATE and FROMTIME parameters specified. ANR1420W Read access denied for volume volume name - volume access mode = unavailable.
Explanation: An attempt to access the named volume for reading failed because the volume status is destroyed. System Action: The volume is not used for read access. User Response: None. ANR1425W Scratch volume volume name is empty but will not be deleted - volume state is mountablenotinlib.
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. User Response: None.
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.
Chapter 3. Common and Platform Specfic Messages
137
ANR1426I ANR1434W
System Action: The volume is not deleted. 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 3. Check the volume back into the library using CHECKIN LIBVOL command ANR1426I All legacy FILE volumes have been marked FULL. ANR1431E An error occurred while writing to side A of volume volume name. An attempt will be made to write to side B of this volume.
Explanation: An error occurred while writing to side A of a two-sided volume. System Action: No additional data will be written to side A of this volume. Any remaining space on side A will not be used. An attempt will be made to use the reverse side (side B) of the volume. User Response: None required if the side B can be used successfully. However, the administrator should investigate the cause of the error and may want to move data from this volume. ANR1432I Updating device configuration information to defined files.
Explanation: As part of the conversion of the database to Tivoli Storage Manager version 5.3, all existing non-full volumes of devtype FILE have been marked FULL to keep them from being extended. System Action: All FILE volumes that were not already FULL have been marked FULL and cannot be appended to. User Response: None.
Explanation: The server is updating device configuration information for the files or data sets specified with the DEVCONFIG option in the server options file. System Action: Server operation continues. User Response: None. ANR1433I Device configuration information successfully written to file name.
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. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. Contact your service representative for further assistance. ANR1430W Retrieval request denied for storage pool storage pool name - access mode=unavailable.
Explanation: Device configuration information was successfully written to the file specified. System Action: Server operation continues. User Response: None. 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. System Action: Server operation continues. 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.
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.
138
IBM Tivoli Storage Manager: Messages
ANR1435E ANR1440I
ANR1435E Server could not write device configuration information to devconfig file name. proper authority to read from the defined device configuration files. ANR1438W Skipping device configuration file: 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 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. ANR1436E Device configuration file devconfig file name cannot be opened.
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. User Response: Examine error messages that may have 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 write device configuration information to device configuration files, the server cannot open the file name specified. System Action: The server does not write device configuration information to the file specified. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. After the problem has been corrected, use the BACKUP DEVCONFIG command to write device configuration information to the file. ANR1437E No device configuration files could be used.
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. User Response: Examine error messages that may have been displayed prior to this message for more information. ANR1440I All drives in use. Process process number being preempted by higher priority operation.
Explanation: When a high priority operation attempted to find an available drive, all the drives were in use. To make a drive available for this operation, the 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.
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. User Response: Examine error messages that may have been displayed prior to this message and correct any 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
Chapter 3. Common and Platform Specfic Messages
139
ANR1441I ANR1454I
ANR1441I Volume volume name is in use. Process process number being preempted by higher priority operation. ANR1449I command name: Beginning parallel SCRIPT command execution on line line number.
Explanation: When a high 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: This message is issued during a RUN 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. System Action: The operation fails. User Response: Reenter the command specifying a valid command name. ANR1451E command name: Invalid command: command.
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. System Action: The operation fails. 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.
Explanation: An invalid command was specified for a DEFINE, UPDATE, or DELETE SCRIPT command. System Action: The operation fails. User Response: Reenter the command specifying a valid server command. ANR1452E command name: Invalid line number: line number.
Explanation: This message is issued during a RUN command to indicate that thread resources are not available to run the command in parallel. The command will be executed serially. System Action: The SCRIPT continues. User Response: Increase the resources available to the server or reduce the number of parallel commands or scripts that are running on the server at any one time. ANR1448I command name: Beginning serial SCRIPT command execution on line line number.
Explanation: An invalid line number was specified for a DEFINE, UPDATE, or DELETE SCRIPT command. System Action: The operation fails. User Response: Reenter the command specifying a valid line number. ANR1453E command name: Command script command script name already exists.
Explanation: The script name specified in a DEFINE SCRIPT command already exists. System Action: The operation fails. User Response: Reenter the command specifying a different command name. ANR1454I command name: Command script command script name defined.
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.
Explanation: The script name specified in a DEFINE SCRIPT command was successfully defined. System Action: None
140
IBM Tivoli Storage Manager: Messages
ANR1455E ANR1465E
User Response: None ANR1455E command name: Command script command script name does not exist. System Action: None User Response: None ANR1461I command name: Executing command script command script name.
Explanation: The script name specified in a DEFINE, UPDATE, or DELETE SCRIPT command does not exist. System Action: The operation fails. User Response: Reenter the command specifying a different command name. ANR1456I command name: Command script command script name updated.
Explanation: The specified command script is being executed as a result of a RUN command. System Action: None User Response: None ANR1462I command name: Command script command script name completed successfully.
Explanation: The script name specified in an UPDATE SCRIPT command was successfully updated. System Action: None User Response: None ANR1457I command name: Command script command script name deleted.
Explanation: The specified command script, started with a RUN command, has successfully completed. System Action: None User Response: None ANR1463E command name: Command script command script name completed in error.
Explanation: The script name specified in a DELETE COMMAND command was successfully deleted. System Action: None User Response: None ANR1458I command name: Line line number was deleted from command script command script name.
Explanation: The specified command script, started with a RUN command, encountered errors. System Action: Part or all of the command lines in the script ended in error. Command processing is terminated. User Response: Examine the messages preceeding this message to determine the cause of the error. Correct the command script and reissue the command. ANR1464E command name: Command script command script name, line line number, parameter parameter number was not specified: command line.
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 ANR1459E command name: Command script command script name, line line number does not exist.
Explanation: All parameters required to execute a command script were not specified in the RUN command. System Action: The command fails. User Response: Reenter the RUN command specifying all required parameters. ANR1465E command name: Command script command script name, line line number, parameter is invalid: command line.
Explanation: The line in command script name specified in a UPDATE, or DELETE SCRIPT command does not exist. System Action: The operation fails. User Response: Reenter the command specifying a different line number. ANR1460I command name: Command script command script name copied to new command script name.
Explanation: An invalid parameter was encountered in a command script. System Action: The command fails. User Response: Correct the script definition and reexecute the RUN command.
Explanation: The specified command script was copied to a new script with the COPY SCRIPT command.
Chapter 3. Common and Platform Specfic Messages
141
ANR1466I ANR1475E
ANR1466I command name: Command script command script name, Line line number : command line. ANR1471E command name: Command script command script name completed in error (PREVIEW mode).
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 command name: Command script command script name, did not end in a non-continued line command line.
Explanation: The specified command script, started 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 command name: Command script command script name renamed to new command script name.
Explanation: The specified command script did not end in a line that had no continuation character (-). System Action: The command fails. User Response: Correct the specified script so that it ends in a line that is not continued to the next line. ANR1468E command name: Command script command script name, continued line is too long
Explanation: The specified command script was renamed with the RENAME SCRIPT command. System Action: None. User Response: None. ANR1473E command name: A command line cannot be specified when the FILE= parameter is used.
Explanation: The specified command script with continuation lines is too long to be executed. System Action: The command fails. User Response: Correct the specified command script so that it is shorter. ANR1469E command name: Command script command script name, Line line number is an INVALID command : command line.
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. System Action: The command fails. User Response: Reenter the command without the command line OR the FILE= parameter. ANR1474E command name: A line number cannot be specified when the FILE= parameter is used.
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. ANR1470I command name: Command script command script name completed successfully (PREVIEW mode).
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. System Action: The command fails. User Response: Reenter the command without the line number OR the FILE= parameter. ANR1475E command name: File file name could not be opened.
Explanation: The specified command script, started with a RUN command, has successfully completed. System Action: None. User Response: None.
Explanation: A filename was specified in a command but the specified file could not be opened by the server. System Action: The command fails. User Response: Examine any messages that might
142
IBM Tivoli Storage Manager: Messages
ANR1476E ANR1484I
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. 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. System Action: The command fails. User Response: Reenter the command specifying a shorter description. ANR1481E command name: A command line or description must be specified.
Explanation: The FILE= parameter was specified in a command but the specified file did not contain script command lines. System Action: The command fails. 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.
Explanation: An UPDATE SCRIPT command was specified with out a command line (script line) or description text. System Action: The command fails. User Response: Reenter the command specifying a command line or description text. ANR1482I 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. System Action: The command fails. User Response: Reenter the command specifyingthe proper value for the FORMAT parameter or do not specify the OUTPUTFILE parameter. ANR1478E command name: Error writing to file file name.
Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate that the target label for a GOTO statement was found. System Action: Command processing continues. User Response: None. ANR1483I command name: Line line number condition IF(condition) is NOT true statement is skipped.
Explanation: An error was encountered while writing to the file specified. System Action: The command fails. 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 command name: Query output was written to file file name.
Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate that the a return code condition check failed and the IF(..) statement is skipped. System Action: Command processing continues. User Response: None. ANR1484I command name: Line line number condition IF(condition) is TRUE statement will be executed.
Explanation: The output from the specified query was successfully written to the specified file. System Action: The command completes successfully. User Response: None.
Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate that the a return code condition check succeeded and the IF(..) statement is executed. System Action: Command processing continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
143
ANR1485I ANR1493E
ANR1485I command name: Ending SCRIPT with EXIT statement on line line number. ANR1490W command name: Command script command script name does not contain any commands.
Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate that an EXIT statement was encountered and SCRIPT termination will end. System Action: The SCRIPT command ends. User Response: None. ANR1486I command name: Executing line line number GOTO label name.
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: This message is issued during a RUN command (VERBOSE=YES) to indicate that a GOTO statment was encountered and processing will skip to the named label. System Action: SCRIPT processing continues. User Response: None. ANR1487I command name: Command return code is symbolic return code (return code severity).
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. System Action: The server ignores the command and continues processing. 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: This message is issued during a RUN command (VERBOSE=YES) to indicate the return code that was returned from the latest command. System Action: SCRIPT processing continues. User Response: None. ANR1488E command name: Line line number condition IF(condition) is not a valid condition.
Explanation: This message is issued if an IF() statement in a SCRIPT does not specify proper condition values. System Action: Command processing fails. User Response: Reenter the command using valid conditions for the IF() statement. ANR1489E command name: Line line number is a GOTO to a label (label name) that does not exist or is associated with a line prior to line line number.
Explanation: 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 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: 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.
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. System Action: The server does not process the command.
144
IBM Tivoli Storage Manager: Messages
ANR1494I ANR1504I
User Response: Issue the command from a properly authorized administrator ID, or contact the administrator that created the script. ANR1494I command name: Command return code is numeric return code. ANR1500I Policy domain domain name defined.
Explanation: In response to the DEFINE DOMAIN command, the policy domain domain name has been defined in the server database. System Action: Server operation continues. User Response: None. ANR1501I Policy domain domain name deleted.
Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate the numeric return code that was returned from the latest command. System Action: SCRIPT processing continues. User Response: None. ANR1495E command name: command script name is currently running. Update or delete can not be performed.
Explanation: In response to the DELETE DOMAIN command, the policy domain domain name has been deleted from the server database. All policy sets, management classes, copy groups, and schedules related to the domain have also been removed. System Action: Server operation continues. User Response: None. ANR1502I Policy domain domain name updated.
Explanation: An UPDATE or DELETE SCRIPT was attempted on a script that is currently running. System Action: The operation fails. User Response: Reenter the command when the script is not running. ANR1496I Explanation: The ISSUE MESSAGE command with a severity indicator of INFORMATION was issued. System Action: Server operation continues. User Response: None. ANR1497W Explanation: The ISSUE MESSAGE command with a severity indicator of WARNING was issued. System Action: Server operation continues. User Response: None.
Explanation: In response to the UPDATE DOMAIN command, the policy domain domain name has been updated in the server database. System Action: Server operation continues. User Response: None. ANR1503I Policy domain domain name copied to domain target domain.
Explanation: In response to the COPY DOMAIN command, the policy domain domain name has been copied to a new policy domain named target domain. All policy sets, management classes, and copy groups are also copied to the target domain policy domain. System Action: Server operation continues. User Response: None. ANR1504I Command: No matching domains.
ANR1498E Explanation: The ISSUE MESSAGE command with a severity indicator of ERROR was issued. System Action: Server operation continues. User Response: None. ANR1499S Explanation: The ISSUE MESSAGE command with a severity indicator of SEVERE was issued. System Action: Server operation continues. User Response: None.
Explanation: The server cannot find any policy domains with names that match the specification entered in the command command. System Action: Server operation continues. 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.
Chapter 3. Common and Platform Specfic Messages
145
ANR1505W ANR1513I
ANR1505W The BACKUP copy group in management class management class name 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. 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. System Action: The server does not process the command. User Response: Reissue the command with a valid retention period. ANR1510I Policy set set name defined in policy domain domain name.
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. System Action: Server operation continues. 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: 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. System Action: Server operation continues. User Response: None. 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. System Action: Server operation continues. User Response: None. ANR1512I Policy set set name updated in policy domain domain name.
Explanation: Server processing for the command command fails because the storage pool name pool name specified for the table of contents (TOC) destination is a copy pool. A copy storage pool is not a valid copy group TOC destination. System Action: The command fails and server operation continues. User Response: Reissue the command using a storage pool name that is not a copy pool. For a list of names of defined storage pools, issue the QUERY STGPOOL command. ANR1507I Table of contents load retention is set to number of minutes minutes.
Explanation: 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. System Action: Server operation continues. User Response: None. ANR1513I Policy set set name copied to set new set name in policy domain domain name.
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. System Action: None. User Response: None.
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. System Action: Server operation continues. User Response: None.
146
IBM Tivoli Storage Manager: Messages
ANR1514I ANR1531I
ANR1514I Policy set set name activated in policy domain domain name. ANR1521I 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. 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. User Response: None. ANR1515I Policy set set name validated in domain domain name (ready for activation).
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: Server operation continues. User Response: None. ANR1522I Management class class name updated in policy domain domain name, set set name.
Explanation: In response to the UPDATE MGMTCLASS command, the management class named class name has been updated in the policy domain domain name, policy set set name. System Action: Server operation continues. User Response: None. ANR1523I Management class class name copied to class new class name in policy domain domain name, set set name.
Explanation: This message may be displayed in response to a VALIDATE POLICYSET command. The policy set set name has been checked in the domain domain name to see if the management class and copy group definitions are adequate for activating the policy set. This message indicates that the policy set may be activated. Warning messages may be issued prior to this message if there are discrepancies in the policy set with respect to the set that is currently active in the policy domain. System Action: The server checks its definitions to determine the policy sets qualifications for activation. The server does not activate the policy set. User Response: If you are satisfied with any warning messages that may have been issued prior to this message concerning any possible discrepancies in the policy set, issue the ACTIVATE POLICYSET command to activate the policy set in the policy domain. Otherwise, correct the discrepancies prior to activating the policy set. Before the ACTIVATE POLICYSET command is used to activate the policy set, use the validate command to check policy set contents. ANR1520I Management class class name defined in policy domain domain name, set set name.
Explanation: In response to the COPY MGMTCLASS command, the management class named class name has been copied to a new management class named new 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. System Action: Server operation continues. User Response: None. ANR1530I Backup copy group group name defined in policy domain domain name, set set name, management class class name.
Explanation: In response to the DEFINE 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 policy domain domain name. System Action: Server operation continues. User Response: None. ANR1531I Backup copy group group name deleted from policy domain domain name, set set name, management class class 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. System Action: Server operation continues. User Response: None.
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
Chapter 3. Common and Platform Specfic Messages
147
ANR1532I ANR1551W
name belonging to policy domain domain name. System Action: Server operation continues. User Response: None. ANR1532I Backup copy group group name updated in policy domain domain name, set set name, management class class name. 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. User Response: None. 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.
Explanation: In response to the UPDATE COPYGROUP command, the backup copy group named group name has been updated in the management class named class name in the policy set set name belonging to policy domain domain name. System Action: Server operation continues. User Response: None. ANR1535I Archive copy group group name defined in policy domain domain name, set set name, management class class name.
Explanation: In response to the DEFINE 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 policy domain domain name. System Action: Server operation continues. User Response: None. ANR1536I Archive copy group group name deleted from policy domain domain name, set set name, management class class name.
Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET 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. System Action: Server operation continues. User Response: If you do not want files to be rebound to the default management class, define a management class with the name specified in the message for the policy set. To define the proper copy group attributes, reference the management class definition in the ACTIVE policy set or copy the management class class name from the ACTIVE policy set to policy set set name using the COPY MGMTCLAS command. ANR1551W BACKUP copygroup group name in management class class name is NOT defined in policy set set name but is defined in the ACTIVE policy set for domain domain name: files bound to this management class will no longer be backed up if/when set name is activated.
Explanation: In response to the DELETE COPYGROUP command, the archive 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. System Action: Server operation continues. User Response: None. ANR1537I Archive copy group group name updated in policy domain domain name, set set name, management class class name.
Explanation: In response to the UPDATE COPYGROUP command, the archive copy group named group name has been updated in the management class named class name in the policy set set name belonging to policy domain domain name. System Action: Server operation continues. User Response: None.
Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, the 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
148
IBM Tivoli Storage Manager: Messages
ANR1552W ANR1555W
domain domain name will no longer be eligible for backup processing. System Action: Server operation continues. 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 copy group group name in 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 no longer be archived if set name is activated. 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.
Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET 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. System Action: Server operation continues. User Response: To define a backup copy group for the management class, issue the DEFINE COPYGROUP command. To assign a different default management class for the domain, issue the ASSIGN DEFMGMTCLASS command. Take either action if you want files to be eligible for archive processing by default. ANR1555W The BACKUP copy group in management class management class name specifies a destination that 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 backup files to the server.
Explanation: This message can be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, the 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, files bound to management class class name in domain domain name will no longer be eligible for archive processing. System Action: Server operation continues. User Response: If you want files bound to this management class to be eligible for archive processing, use the DEFINE copy group command to define an archive copy group for management class class name. 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.
Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET 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. System Action: Server operation continues. 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.
Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET 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. System Action: Server operation continues. User Response: To locate the copy groups that refer to the undefined storage pool, issue the QUERY COPYGROUP command. To change the destination to refer to an existing storage pool, issue the UPDATE COPYGROUP command. To define the storage pool, an authorized administrator can issue the DEFINE STGPOOL command.
Chapter 3. Common and Platform Specfic Messages
149
ANR1556W ANR1560E
ANR1556W The ARCHIVE copy group in management class management class name specifies a destination that 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 archive files to the server. 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.
Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for set name, the server has found a archive copy group destination that references an undefined storage pool named pool name. 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. System Action: Server operation continues. User Response: To locate the copy groups that refer to the undefined storage pool, issue the QUERY COPYGROUP command. To change the destination to refer to an existing storage pool, issue the UPDATE COPYGROUP command. To define the storage pool, an authorized administrator can issue the DEFINE STGPOOL command. 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.
Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for set name, the 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. User Response: To locate the management class that refers to the copy storage pool, issue the QUERY MGMTCLASS command. To change the destination to 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.
Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for set name, the 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. User Response: To locate the management class that refers to the copy storage pool, issue the QUERY MGMTCLASS command. To change the destination to refer to a non-copy storage pool, issue the UPDATE MGMTCLASS command. ANR1560E Command: Invalid policy domain name domain name.
Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for set name, the 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. System Action: Server operation continues. User Response: To locate the management class that refers to the undefined storage pool, issue the QUERY MGMTCLASS command. To change the destination to refer to an existing storage pool, issue the UPDATE MGMTCLASS command. To define the storage pool, an authorized administrator can issue the DEFINE STGPOOL command.
Explanation: Server processing for the command 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. User Response: Reissue the command and specify a policy domain name that conforms to these name requirements. For information on the character and length specifications for valid policy domain names, refer to the Administrators Reference for your particular platform.
150
IBM Tivoli Storage Manager: Messages
ANR1561E ANR1567E
ANR1561E Command: Missing policy domain name. for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrators Reference for your particular platform. ANR1565E Command: Invalid policy set name - set name.
Explanation: Server processing for the command command fails because the required policy domain parameter has not been specified. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid policy domain name. ANR1562E Command: Policy domain description exceeds length limit characters.
Explanation: Server processing for the command command fails because the policy set name set 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. User Response: Reissue the command and specify a policy set name that conforms to valid name requirements. For information on the character and 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.
Explanation: Server processing for the command command fails because the policy domain description specified is longer than the length limit number of characters allowed. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a shorter policy domain description. ANR1563E Command: Invalid retention period for BACKRETN parameter - retention value.
Explanation: Server processing for the command command fails because the policy set description specified is longer than the length limit number of characters allowed. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a shorter policy set description. ANR1567E Command: Invalid management class name - class name.
Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the BACKRETN parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a 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 Command: Invalid retention period for ARCHRETN parameter - retention value.
Explanation: Server processing for the command command fails because the management class name class 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. User Response: Reissue the command and specify a management class name that conforms to valid name requirements. For information on the character and length specifications for valid management class names, refer to the Administrators Reference for your particular platform.
Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the ARCHRETN parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid ARCHRETN value. For valid ARCHRETN values
Chapter 3. Common and Platform Specfic Messages
151
ANR1568E ANR1574E
ANR1568E Command: Management class description exceeds length limit characters. 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. User Response: Reissue the command and specify a storage pool name that conforms to valid name requirements. For information on the character and length specifications for valid storage pool names, refer to the Administrators Reference for your particular platform. For a list of names of defined storage pools, issue the QUERY STGPOOL command. ANR1572E Command: Missing copy destination.
Explanation: Server processing for the command command fails because the management class description specified is longer than the length limit number of characters allowed. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a shorter management class description. Refer to the Administrators Guide for your particular platform for more information. ANR1569E Command: Invalid copy group name group name.
Explanation: Server processing for the copy group command command fails because the required copy group destination is not specified. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify the required copy group destination (DEST). ANR1573E Command: Invalid copy type - type value.
Explanation: Server processing for the command command fails because the copy group name group 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. User Response: Reissue the command and specify a copy group name that conforms to valid name requirements. For information on the character and length specifications for valid copy group names, refer to the Administrators Reference for your particular platform. ANR1570E Command: Invalid copy frequency frequency value.
Explanation: Server processing for the copy group command command fails because the value (type value) specified for the TYPE parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a 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.
Explanation: Server processing for the copy group command command fails because the value (frequency value) specified for the FREQUENCY parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid FREQUENCY value. For valid FREQUENCY values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrators Reference for your particular platform. ANR1571E Command: Invalid copy destination - pool name.
Explanation: Server processing for the copy group command command fails because the value (version value) specified for the VEREXISTS parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid VEREXISTS value. For valid VEREXISTS values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrators Reference for your particular platform.
Explanation: Server processing for the command command fails because the storage pool name pool name specified for the copy group destination or for the table of contents (TOC) destination does not contain valid
152
IBM Tivoli Storage Manager: Messages
ANR1575E ANR1581E
ANR1575E Command: Invalid version count for VERDELETED parameter - version value. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid RETVER value. For valid RETVER values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrators Reference for your particular platform. ANR1579E Command: Invalid copy mode - mode value.
Explanation: Server processing for the copy group command command fails because the value (version value) specified for the VERDELETED parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid VERDELETED value. For valid VERDELETED values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrators Reference for your particular platform. ANR1576E Command: Invalid retention period for RETEXTRA parameter - retention value.
Explanation: Server processing for the copy group command command fails because the value (mode value) specified for the MODE parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid MODE value. For valid MODE values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrators Reference for your particular platform. ANR1580E Command: Invalid copy serialization mode - serialization value.
Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the RETEXTRA parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid RETEXTRA value. For valid RETEXTRA values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrators Reference for your particular platform. ANR1577E Command: Invalid retention period for RETONLY parameter - retention value.
Explanation: Server processing for the copy group command command fails because the value (serialization value) specified for the SERIALIZATION parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid SERIALIZATION value. For valid SERIALIZATION values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrators Reference for your particular platform. ANR1581E Command: The option option is valid only for backup copy groups.
Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the RETONLY parameter is not valid. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify a valid RETONLY value. For valid RETONLY values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrators Reference for your particular platform. ANR1578E Command: Invalid version count for RETVER parameter - retention value.
Explanation: Server processing for the archive copy group command command fails because the option specified is only valid for backup copy group definitions. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server 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
Chapter 3. Common and Platform Specfic Messages
Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the RETVER parameter is not valid.
153
ANR1582E ANR1587E
valid archive copy group options, refer to the Administrators Reference and Administrators Guide for your particular platform. ANR1582E Command: The option option is valid only for archive copy groups. 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.
Explanation: Server processing for the backup copy group command command fails because the option specified is only valid for archive copy group definitions. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server 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.
Explanation: Server processing for the command 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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a policy set other than ACTIVE. To copy the ACTIVE policy set for a policy domain to another name so that commands may be used to change its contents, issue the COPY POLICYSET command. Then to activate the changes, issue the ACTIVATE POLICYSET command. ANR1586E Command: Invalid migration destination - pool name.
Explanation: Server processing for the archive copy 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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server 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 your particular platform. ANR1584E Command: Copy mode for archive copy groups must be ABSOLUTE - mode value is not valid.
Explanation: Server processing for the command command fails because the storage pool name pool name specified for the migration destination is a copy pool. A copy pool is not a valid migration destination. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command using a storage 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.
Explanation: Server processing for the archive copy 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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying ABSOLUTE for the MODE parameter, or omitting the
Explanation: Server processing for the command command fails because the storage pool name pool name specified for the copy group destination is a copy pool. A copy pool is not a valid copy group destination. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command using a storage pool name that is not a copy pool. For a list of names of defined storage pools, issue the QUERY STGPOOL command.
154
IBM Tivoli Storage Manager: Messages
ANR1590E ANR1596E
ANR1590E Command: Policy domain domain name is not defined. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server 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 Command: Policy domain domain name has no active policy set.
Explanation: Server processing for the command command fails because the policy domain name domain name specified does not refer to a defined policy domain in the server database. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a 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.
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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server 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.
Explanation: Server processing for the command command fails because the policy domain name domain name specified refers to a policy domain that is already defined in the server database. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a policy domain name that is not defined in the server database. For a list of the names of defined policy 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 command command fails because the policy set name set name specified does not refer to a defined set in policy domain domain name in the server database. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a 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 defined in policy domain domain name.
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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: To delete the policy set from the policy domain, issue the DELETE POLICYSET command. ANR1593E Command: Policy domain domain name still contains at least one node.
Explanation: Server processing for the command command fails because the policy set name set name specified refers to a policy set that is already defined in policy domain domain name. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a
Chapter 3. Common and Platform Specfic Messages
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 node. A policy domain cannot be deleted if one or more client nodes are still assigned to the domain.
155
ANR1597E ANR1603E
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. ANR1600E Command: Management class class name is already defined in policy domain domain name, set set name.
Explanation: Server processing for the command 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 policy domain domain name. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a management class name that is not defined in the policy set. For a list of the names of defined management classes in the policy domain and policy set, issue the QUERY MGMTCLASS command. ANR1602E Command: Backup copy group group name is not defined in policy domain domain name, set set name, management class class name.
Explanation: The policy set command failed because the set still contains at least one management class definition. System Action: The command fails and server operation continues. User Response: Remove the remaining management classes from the policy set and reissue the command. ANR1598E Command: No default management class has been assigned for policy set set name in domain domain name.
Explanation: Server processing for the command command fails because the policy set set name in policy domain domain name does not have a default management class assigned. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server 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.
Explanation: Server processing for the command 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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a 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.
Explanation: Server processing for the command 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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a 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.
Explanation: Server processing for the command 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 policy set set name belonging to policy domain domain name. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a copy group that is not defined in the policy set. For a list of the names of defined copy groups for
156
IBM Tivoli Storage Manager: Messages
ANR1604E ANR1610E
management classes in the policy domain and policy 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. ANR1607E Out of server DB space in accessing policy tables.
Explanation: The server ends a database update transaction for policy information because sufficient database space is not available on the server. System Action: The policy operation is ended and server operation continues. User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used. ANR1608E Error fetching entry for domain domain name, set set name.
Explanation: Server processing for the command 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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a 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. ANR1605E Command: Archive copy group group name is already defined in policy domain domain name, set set name, management class class name.
Explanation: An internal server database error occurs while retrieving policy information for policy set set name in domain domain name. System Action: The policy operation is ended and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR1609E Policy error: unable to find management class ID for class class name in policy set set name belonging to domain domain name.
Explanation: Server processing for the command command fails because the specified archive copy group named group name refers to a copy group that is already defined for management class class name in policy set set name belonging to policy domain domain name. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command specifying a copy group that is not defined in the policy set. For a list of the names of defined copy groups for management classes in the policy domain and policy set, issue the QUERY COPYGROUP command. ANR1606E Out of server LOG space in accessing policy tables.
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. System Action: The policy operation is ended and server operation continues. User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR1610E Internal Server error: invalid copy type copy type integer encountered in policy set validation.
Explanation: The server ends a database update transaction for policy information because sufficient log space is not available on the server. System Action: The policy operation is ended and server operation continues. User Response: An authorized administrator can issue 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.
Explanation: An internal server database error has been encountered while validating a policy set in response to the VALIDATE POLICYSET or ACTIVATE POLICYSET command. System Action: The policy operation is ended and server operation continues.
Chapter 3. Common and Platform Specfic Messages
157
ANR1611E ANR1616W
User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR1611E Command: Invalid management class name - management class name. ANR1614E Command: Invalid number of days for RETMIN parameter - days value.
Explanation: The command fails. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Issue the command again and specify a valid RETMIN value. For valid RETMIN values for the DEFINE copy group or UPDATE copy group commands, refer to the Administrators Reference. ANR1615E Command: RETVER of NOLIMIT cannot be specified with RETINIT value of EVENT.
Explanation: Server processing for the command command fails because the specified management class name may not be used as a management class name. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Reissue the command and specify another management class name. ANR1612E Command: Management class management class name in policy set set name, domain domain name specifies MIGREQUIRESBKUP=YES, but contains no backup copy group.
Explanation: Server processing for the copy group 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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Issue the command again and specify a valid RETVER or RETMIN value. For valid values for the DEFINE copy group or UPDATE copy group commands, refer to the Administrators Reference. ANR1616W Command: the specified RETMIN value (new days) will be ignored because the RETINIT value is CREATION for domain policy set management class.
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. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing 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.
Explanation: Processing for the copy group command command detected that a retain minimum number of days value was specified either with the retention initiation value of CREATION, or the current retention initiation value stored for the copy group is CREATION. The retain minimum number of days value is not used when the retention initiation value is CREATION. The copy group will be defined or updated, but the RETMIN value will not be stored. System Action: The copy group is defined or updated and system operation continues. User Response: The copy group will be defined or updated, but the retain minimum number of days value will not be stored. If you want to specify a retention initiation value of EVENT, issue the update command again.
Explanation: Server processing for the copy group command command fails because the value (retention initiation value) specified for the RETINIT parameter is not valid. System Action: The command fails. 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.
158
IBM Tivoli Storage Manager: Messages
ANR1617W ANR1622E
ANR1617W Command: the new RETVER value (new days) is less than the value previously stored (old days) for domain policy set management class. ANR1620E The new RETVER value (new days) is less than the value in the ACTIVE policy (old days) for domain policy set management class.
Explanation: Processing for the copy group command 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 operation continues. User Response: The copy group will be updated, but the copy group might fail validation when the policy set is validated or activated. ANR1618W Command: the new RETMIN value (new days) is less than the value previously stored (old days) for domain policy set management class.
Explanation: This message can be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, the 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. System Action: Server operation continues. 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.
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 operation continues. User Response: The copy group will be updated, but the copy group might fail validation when the policy set is validated or activated. ANR1619E The RETVER of NOLIMIT is not allowed with the RETINIT value of EVENT for domain policy set management class.
Explanation: This message can be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, the 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. System Action: Server operation continues. 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.
Explanation: This message can be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, 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. System Action: Server operation continues. User Response: Update the RETVER or REINIT values in the copy group. For valid values, refer to the Administrators Reference for your platform.
Explanation: This message can be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, the 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. System Action: Server operation continues. 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.
Chapter 3. Common and Platform Specfic Messages
159
ANR1623E ANR1642E
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. ANR1638W Error (error) occurred initializing the server machine GUID. Old value was old GUID.
Explanation: This message can be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, the 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. System Action: Server operation continues. User Response: Define an archive copy group in specified management class, then try the validation again. ANR1635I The server machine GUID, machine GUID, has initialized.
Explanation: An error occurred while initializing the server machine globally unique identifier (GUID). The old value is displayed. System Action: Server operation continues. User Response: Handle problems appropriately. A write error may occur because the server needs root authority to write the GUID. A read error may occur if the server does not have authority to read the GUID. Other error codes are received from the GUID utility. ANR1639I 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. System Action: Server operation continues. User Response: None. ANR1640E There is no data mover defined for node node name.
Explanation: The specified globally unique identifier (GUID) has initialized for the server machine. System Action: Server operation continues. User Response: None. ANR1636W The server machine GUID changed: old value (old value), new value (new value).
Explanation: To perform the requested operation, the specified node must have an associated data mover defined. 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.
Explanation: The globally unique identifier (GUID) has changed for the server machine. The old and new values are displayed. System Action: Server operation continues. User Response: None. ANR1637W Error (error) occurred initializing the server machine GUID.
Explanation: The node is not the correct type to be used with this command. System Action: The command fails. User Response: Re-run the command with a node of the correct type. ANR1642E command: The node node name is locked.
Explanation: An error occurred while initializing the server machine globally unique identifier (GUID). System Action: Server operation continues. 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.
Explanation: The node is locked and cannot be used in this command. System Action: The command fails. User Response: Unlock the node and re-run the command.
160
IBM Tivoli Storage Manager: Messages
ANR1643I ANR1650E
ANR1643I Command: All file spaces for node node name, will be moved. ANR1647E Cannot find file space name for node node ID, file space file space ID.
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. User Response: None. ANR1644E Command: Move node data operation already in progress for storage pool storage pool.
Explanation: The server could not obtain filespace information for that node. System Action: The server operation continues. 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. 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 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. System Action: The server does not process the 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 Command: Data for node node name, filespace filespace name, FSID filespace ID will be moved.
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: 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. User Response: None. ANR1646I Command: Node Node name, no filespaces found to move for this node.
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. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to continue or 'N' to end the process. ANR1650E Server server name is not defined.
Explanation: A node and filespace were entered in a MOVE NODEDATA command but no filespaces were found for the specifed node. System Action: The server continues to move other filespaces for any other nodes specified in the MOVE NODEDATA command. User Response: None.
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. System Action: The current action for the device class referring to this server fails. User Response: The device class referring to this node as the SERVERNAME should be updated to refer to a valid server entry. Specifically, it should refer to an
Chapter 3. Common and Platform Specfic Messages
161
ANR1651E ANR1659E
entry created using the DEFINE SERVER command. ANR1651E Server information for server name is not available. System Action: This DEFINE SERVER entry is written to the device configuration file without the password. User Response: The password needs to be specified after PASSWORD= for this DEFINE SERVER entry in the device configuration file. ANR1656E Failure writing server definitions to a device configuration file.
Explanation: The information for server name was not available. System Action: The current server action fails. User Response: Please review any other messages prior to this message to determine the cause of the failure. ANR1652E Server information for server name could not be read from a device configuration file.
Explanation: An error occurred writing the server information to a device configuration file. System Action: The BACKUP DEVCONFIG action fails. User Response: Check that the device configuration file exists and that the file system the file resides on is not out of space. ANR1657E Command: Invalid server or group name - server or group name.
Explanation: 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 Resource lock acquisition for server server name failed.
Explanation: The command shown specifies an invalid server or server group name. System Action: The server does not process the command. User Response: Reissue the command with a valid name. ANR1658E Command: Failure determining NODENAME for server server name.
Explanation: The acquisition of the resource lock for server server name failed. System Action: The current action for the device class referring to this server fails. 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: 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. System Action: The server does not process the command. User Response: Reissue the command with a valid 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: 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 Failure processing password for Server server name when writing a device configuration file.
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. System Action: The server does not process the command. User Response: To define the server or server group, reissue the command and specify a different name.
Explanation: An error occurred processing the password for server name while trying to write this information to a device configuration file.
162
IBM Tivoli Storage Manager: Messages
ANR1660I ANR1670E
ANR1660I Server server name defined successfully. User Response: Re-try the command specifying a different password. ANR1666E command: FILEAGGR not allowed with NODETYPE=SERVER.
Explanation: The requested server has been defined to the system in response to a DEFINE SERVER command. System Action: None. User Response: None. ANR1661I Server server name deleted.
Explanation: The FILEAGGR= parameter may not be specified with the NODETYPE=SERVER parameter also being specified. System Action: The command fails. 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: In response to a DELETE SERVER command, the requested server has been removed from the system. System Action: None. User Response: None. ANR1662I Server server name updated.
Explanation: One or more attributes of a server have been updated by an UPDATE SERVER command. System Action: None. User Response: None.
Explanation: The command is not permitted against the entry for node node name. This node entry has a NODETYPE of SERVER. System Action: The command fails. User Response: None. ANR1668E command: Not allowed for server server name.
ANR1663E
command: Server server name not defined
Explanation: The server server name is not defined to the system. System Action: The command fails. User Response: None. ANR1664W Command: Server server name is currently in use.
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. System Action: The command fails. User Response: If the specified server is the event server, and you want to delete it, issue the DELETE EVENTSERVER command and then reissue the DELETE SERVER command. To remove a node entry, issue the REMOVE NODE command for the specified name. ANR1669I Server event server name is defined as the event server.
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. System Action: The server does not process the 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: The specified server is defined. System Action: None. User Response: None. 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.
Explanation: An event server is already defined. System Action: The command fails. User Response: Delete the existing Event Server and try the command again.
Chapter 3. Common and Platform Specfic Messages
Explanation: An error occurred updating the password for server name. System Action: The command fails.
163
ANR1671I ANR1682E
ANR1671I The event server definition has been deleted. ANR1677I Server group server group name updated.
Explanation: The event server definition has been deleted. System Action: None. User Response: If an event server definition is desired, use the DEFINE EVENTSERVER command. ANR1672I No event server is currently defined.
Explanation: One or more attributes of a server group is updated by an UPDATE SERVERGROUP command. System Action: None. User Response: None. ANR1678I Server group original server group name renamed new server group name.
Explanation: A query was issued to get the name of the event server; however, no event server is currently defined. System Action: None. User Response: If an event server definition is desired, use the DEFINE EVENTSERVER command. ANR1673I Server group group name defined successfully.
Explanation: A server group is renamed by a RENAME SERVERGROUP command. The original name is not valid. System Action: None. User Response: None. ANR1679E Command: Server group server group name not defined.
Explanation: The server server group name is not defined to the system. System Action: The command fails. User Response: Retry the command specifying an existing group. ANR1680E Command: Member member name not defined in server group server group name.
Explanation: The requested server group is defined to the system in response to a DEFINE SERVERGROUP command. System Action: None. User Response: None. 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. System Action: None. User Response: None.
Explanation: The member member name is not defined in server group server group name. System Action: The command fails. User Response: Retry the command specifying an existing member of the group. ANR1681E Command: Member member name is already in server group server group name.
ANR1675I
Server group server group name deleted.
Explanation: The requested server is removed from the system in response to a DELETE SERVERGROUP command. System Action: None. User Response: None. ANR1676I Member member name deleted from server group server group name.
Explanation: The member member name is defined in server group server group name. System Action: The command fails. User Response: Retry the command and specify a new member name. ANR1682E A group cannot be a member of itself.
Explanation: The requested member is removed from the server group in response to a DELETE GRPMEMBER command, System Action: None. User Response: None.
Explanation: The member and group name are the same. A group may not be a member of itself. System Action: The command fails. User Response: Retry the command and specify another member name.
164
IBM Tivoli Storage Manager: Messages
ANR1683E ANR1692E
ANR1683E Command: Member member name not defined. ANR1688I Output for command command issued 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. System Action: The command fails. User Response: Retry the command specifying existing server or group. ANR1684E Route:command: Routed commands cannot be routed.
Explanation: This message marks the end of the output for the command specified that was issued against the indicated server. System Action: None. User Response: None. ANR1689E Output for command command issued against server server name terminated.
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 Server group server group copied to server group new server group.
Explanation: An error condition occurred causing the output for the command issued against the specified server to be terminated. System Action: None. 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: None. 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. ANR1691E Error receiving response from server server name for command command.
Explanation: This message is displayed in response to the COPY SERVERGROUP command. The server group named server group is copied to the server group named new server group. System Action: None. User Response: None. ANR1686I Member member name moved from server group group name to server group new group name.
Explanation: The requested member member name is moved from server group group name to the server group new server group in response to a MOVE GRPMEMBER command. System Action: None. User Response: None. ANR1687I Output for command command issued against server server name follows:
Explanation: An error was encountered receiving the response from the server indicated for the command that was issued against it. System Action: None. 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. ANR1692E Response for command command from server server name contains invalid data.
Explanation: The output for the command issued against the indicated server follows this message. System Action: None. User Response: None.
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.
Chapter 3. Common and Platform Specfic Messages
165
ANR1693E ANR1700E
User Response: Please contact your local service representative. ANR1693E Unable to issue command command against server server name - failure starting thread. 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: A thread could not be started to issue the specified command against the server indicated. System Action: This command is not issued against the server specified. The process will attempt to issue the command against any other servers that were specified for the command routing information. User Response: Examine the server messages issued prior to this message to determine the source of the error. Retry routing this command to the indicated server after the cause of the error has been determined 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 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. System Action: None. User Response: None. ANR1698I Command command was not issued against any other servers.
Explanation: The server indicated processed the command successfully. System Action: None. User Response: None. ANR1695W Server server name processed command command but completed with warnings.
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. System Action: None. 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 server indicated processed the command but encountered warnings. However, the warnings did not prevent the execution of the command. System Action: None. User Response: None. ANR1696E Server server name attempted to process command command but encountered errors.
Explanation: The route information was resolved to the number of servers indicated. The specified command will be issued against those servers. System Action: None. User Response: None. ANR1700E Unable to resolve route information to any server(s).
Explanation: The server indicated processed the command but encountered errors. These errors prevented the successful completion of the command. System Action: None. 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.
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. System Action: None. User Response: Examine the route information provided. Reissue the command providing correct route information.
166
IBM Tivoli Storage Manager: Messages
ANR1701E ANR1709E
ANR1701E Command: No matching servers defined. 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: No matching servers are found for the specified command. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify different servers. ANR1702W Skipping server name - unable to resolve to a valid server name.
Explanation: The ping command was able to establish a connection to the server specified. System Action: None. User Response: Check the activity log and server console for messages that indicate a failure or problem on the server issuing this command. Next, check the communication connection between the two srevers. And finally, verify the operation of the server specified. ANR1707I Server information not complete, crossdefine not allowed.
Explanation: The server name specified is being skipped because it could not be resolved to a valid server name. System Action: None. 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. System Action: None. User Response: 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. ANR1704E Failure obtaining credentials for administrator admin name.
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. System Action: The command fails. 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. ANR1708I Define server for Server name failed because the crossdefine failed.
Explanation: An error occurred obtaining the credentials for the administrator referenced. System Action: Command processing fails. User Response: 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 define server command failed because the crossdefine parameter was included, and the crossdefine was not successful. System Action: The command fails. User Response: Check this server, and the server being defined for other messages indicating the reason for the failure. ANR1709E Command.: Failure determining current usage for server or group name Server name.
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. System Action: None. User Response: Check the activity log and server console for messages that indicate a failure or problem on the server issuing this command. Next, check the communication connection between the two servers.
Explanation: The specified command failed to determine the current use of the server name or server group specified. System Action: The command fails. 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.
Chapter 3. Common and Platform Specfic Messages
167
ANR1710E ANR1718E
ANR1710E Command.: Name Name not valid for this command. User Response: Change the administrators password on the named configuration manager server. ANR1715E Event server cannot be deleted - it is currently active.
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. System Action: The command fails. User Response: Retry the command specifying the proper name. ANR1711E Error accessing the server or server group name Name.
Explanation: The event server cannot be deleted since it is currently active for event logging. System Action: The server does not delete the event server entry. User Response: In order to delete the event server, it must not be currently active for event logging. To stop event logging to the event server issue END EVENTLOGGING EVENTSERVER. Then reissue the DELETE EVENTSERVER command. ANR1716I Server cannot be crossdefined to itself, crossdefine not allowed.
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 opteration 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: An attempt was made to crossdefine the server to itself. System Action: The command fails. User Response: None. ANR1717E Command: Command failed Non-Compatible Filespace name types have been specified.
Explanation: Command routing is not allowed from the server console. System Action: The command is not executed. User Response: Reissue the command from an Administrative client. ANR1713I Command command issued against server server name.
Explanation: A server command has been entered but cannot be processed because Non-Compatible Filespace name types have been specified. System Action: The server does not process the 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 specified command has been sent to the indicated server. The command is to terminate the specified server, no confirmation will be recieved. System Action: None. User Response: None. ANR1714W 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 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. System Action: The server does not process the 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.
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.
168
IBM Tivoli Storage Manager: Messages
ANR1719E ANR1727E
ANR1719E Storage pool storage pool name specified on the MOVE NODEDATA command is not a valid pool name or pool type. already exists in the server database. System Action: Server operation continues. User Response: Correct the source name or destination name and re-enter this command. ANR1724W Command: Server server name is currently in use.
Explanation: If the source storage pool specified in the command is a primary storage pool, then the destination storage pool specified must also be a primary storage pool. If the source storage pool is a copy storage pool, then the specified destination storage pool must be the same storage pool as the source storage pool. System Action: The MOVE NODEDATA process fails. User Response: Provide a valid primary storage pool name as the destination storage pool if the source pool is a primary storage pool. If the source pool is a copy storage pool do not specify a destination pool, or, specify the same copy storage pool as the destination pool. ANR1720I A path from source name to destination name has been defined.
Explanation: The command shown specifies a server that is currently in use. The server is referenced in a PATH used for LANFree access to a FILE device type drive in a shared library. System Action: The server does not process the 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, 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.
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. System Action: Server operation continues. User Response: None. ANR1721I A path from source name to destination name has been deleted.
Explanation: In response to the DEFINE PATH command, a resource name was provided that has not been defined. System Action: Server operation continues. User Response: Define the source name or the destination name and re-enter this command. ANR1726E A operation using the path from sourcename to destname is currently being used.
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. System Action: Server operation continues. User Response: None. ANR1722I A path from source name to destination name has been updated.
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. System Action: The server ignores the command. 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.
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. System Action: Server operation continues. User Response: None. ANR1723E A path is already defined using source name and destination name.
Explanation: The path being updated or deleted does not exist. System Action: The server ignores the command. User Response: Reissue the command with a different source or destination name or define a new path.
Explanation: In response to the DEFINE PATH command, the server determines that a path with the same source name and the same destination name
Chapter 3. Common and Platform Specfic Messages
169
ANR1728E ANR1738I
ANR1728E The library libname is not a SCSI library. ANR1734E Data mover mover name is not defined.
Explanation: A drive that is to be used by a NAS data mover must be attached to a SCSI library. System Action: The server ignores the command. User Response: Reissue the command with a different drive name. ANR1729E A path using the data mover source name still exists.
Explanation: An UPDATE DATAMOVER command was entered for a data mover that does not exist in the server database. System Action: Server operation continues. User Response: Correct the data mover name or use the DEFINE DATAMOVER command to define a new data mover. ANR1735E Data mover data mover is currently being used.
Explanation: In the DELETE DATAMOVER command, the data mover name supplied is either the source or the destination in a path that still exists in the server database. System Action: Server operation continues. User Response: Delete the existing path and reissue this command. ANR1730I Data mover mover name has been defined.
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. System Action: The server ignores the command. User Response: Wait until the operation using this data mover is complete, or cancel the operation using this data mover, and then reissue the command. ANR1736E Command: Parameter parameter length is invalid.
Explanation: The data mover has been defined in the server database. System Action: Server operation continues. User Response: None. ANR1731I Data mover mover name has been deleted.
Explanation: The specified server command has been entered with a parameter that is longer or smaller in length than the allowed length. System Action: The server ignores the command. User Response: Reissue the command and enter the proper syntax. ANR1737E Command: Device name device specified is invalid.
Explanation: The data mover has been deleted in the server database. System Action: Server operation continues. User Response: None. ANR1732I Data mover mover name has been updated.
Explanation: The specified command has been entered with an invalid device name. System Action: The command failed. User Response: Reissue the command with a valid device name. ANR1738I Unable to begin a server-free operation with data mover data mover name; received error error.
Explanation: The data mover has been updated in the server database. System Action: Server operation continues. User Response: None. ANR1733E Data mover mover name is already defined.
Explanation: The server attempted to begin a server-free operation with the specified data mover but was unable to do so. System Action: Server operation continues. User Response: The server-free data movement will fail and the client may retry the request using LAN or LAN-free data transfer.
Explanation: A DEFINE DATAMOVER command was entered for a data mover that already exists in the server database. System Action: Server operation continues. User Response: Use the UPDATE DATAMOVER to change the attributes in this data mover. Otherwise use a different data mover name.
170
IBM Tivoli Storage Manager: Messages
ANR1739I ANR1748W
ANR1739I Unable to update configuration of data mover data mover name; received error error. 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: 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. System Action: Server operation continues. User Response: The data mover must finish its current operation before the configuration can be updated. The server-free data movement will fail and the client will retry the request using LAN or LAN-free data transfer. ANR1740E For the path defined from disk node name disk name received lun actual lun from client, expected expected lun.
Explanation: A path was being defined from a datamover to a destination and that destination has an incorrect world wide name specified. System Action: Server operation continues. User Response: Update the destinations definition with the correct world wide name. ANR1745I Unable to discover SAN devices. Function is busy.
Explanation: A client attempted to backup the disk, but the server path definition was different than that which was detected by the client. System Action: Server operation continues. 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: The SAN device discovery function is busy. The requested query cannot be completed at this time. System Action: Server operation continues. 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. System Action: Server operation continues. 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: A client attempted to backup the disk, but the server path definition was different than that which was detected by the client. System Action: Server operation continues. User Response: Correct the path definition from the disk to a datamover. ANR1742E The disk node name disk name is not online.
Explanation: An operation requested the specified disk. The disk cannot be used because it is not online. System Action: Server operation continues. 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: 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. System Action: Server operation continues. User Response: Verify that the serial number of the data mover definition is correct and that the data mover is operational. ANR1748W The disk node name disk name was not found on the SAN. The path definition for this disk has been marked offline.
Explanation: An operation requested the specified disk. The disk cannot be used because the path from the datamover to the disk is not online. System Action: Server operation continues.
Explanation: During device discovery on a storage area network a device was not found that has the same serial number as the disk defined to TSM. System Action: Server operation continues.
Chapter 3. Common and Platform Specfic Messages
171
ANR1749W ANR1759E
User Response: Verify that the serial number of the disk definition is correct and that the disk is operational. ANR1749W The drive library name drive name was not found on the SAN. The path definition for this drive has been marked offline. 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. System Action: Server operation continues. User Response: Correct the disk name or use the DEFINE DISK command to define a new disk. ANR1755I Disk disk name has been updated.
Explanation: During device discovery on a storage area network a device was not found that has the same serial number as the drive defined to TSM. System Action: Server operation continues. User Response: Verify that the serial number of the drive definition is correct and that the drive is operational. ANR1750E The server detected an internal error, return code = return code.
Explanation: In response to the UPDATE DISK command, the disk attributes have been updated in the server database. System Action: Server operation continues. User Response: None. ANR1756I Disk disk name has been deleted.
Explanation: An unexpected error occured during server operation. System Action: 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, retry the operation. If the failure cannot be found, contact your service representative for assistance in resolving the problem. ANR1751I Disk disk name has been defined.
Explanation: In response to the DELETE DISK command, the disk has been deleted in the server database. System Action: Server operation continues. User Response: None. ANR1757E A path using the disk disk name still exists.
Explanation: In response to the DEFINE DISK command, the disk has been defined in the server database. System Action: Server operation continues. User Response: None. ANR1752E Disk disk name is already defined.
Explanation: The name supplied in a DELETE DISK command is the destination in a path that still exists in the server database. System Action: Server operation continues. 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: A DEFINE DISK command was entered for a disk that already exists in the server database. System Action: Server operation continues. User Response: Use the UPDATE DISK command to change the attributes of this disk. Otherwise, use a different disk name. ANR1753E Disk disk name is currently being used.
Explanation: During a backup operation a path from the disk cannot be found. System Action: Server operation continues. 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: A disk was in use when the command was entered. The attributes of a disk may not be changed while it is being used. System Action: The server ignores the command. User Response: Wait until the operation using this disk is complete, or cancel the operation using this disk, and then reissue the command.
Explanation: The scsi address could not be determined for a device that is capable of performing datamover operations. System Action: The requested operation fails.
172
IBM Tivoli Storage Manager: Messages
ANR1760E ANR1766I
User Response: Verify that the hardware that can perform SCSI datamover operations is installed and powered on. ANR1760E Command: Command failed for node node name, filespace filespace name destination storage pool storage pool was skipped. System Action: The operation fails. 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. ANR1764E Command: Command failed - loadable module module name is not available.
Explanation: The indicated command failed because the destination storage pool was skipped. A storage pool may be skipped because it does not have enough available space, or because it has a MAXSIZE value that is less than the size of the object to be inserted. System Action: The operation fails. 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 Command: Command failed for node node name, filespace filespace name storage media is inaccessible.
Explanation: The indicated server command has failed because it requires the availability of the specified loadable module, but the module is not loaded. System Action: The operation fails. 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. System Action: The command fails. 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 indicated command failed because required storage media is unavailable. System Action: The operation fails. 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. ANR1762E Command: Command failed for node node name, filespace filespace name mount point unavailable.
Explanation: The indicated command failed because sufficient mount points are not available. System Action: The operation fails. 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.
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.
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.
Chapter 3. Common and Platform Specfic Messages
173
ANR1767W ANR1782W
ANR1767W A datamover with a online path to both the disk, nodename diskname, and the drive, libraryname drivename cannot be found. ANR1771E The path from remote server remote server name to destination destination name with the destination device type is not valid.
Explanation: To perform server-free data movement, a path must exist from the datamover to both the disk and the drive. If either path is not defined or is offline to all datamovers defined then the data movement cannot occur via server-free. System Action: The operation continues using another method. User Response: Define the appropriate paths from a datamover to the disks and drives. If a path is defined from a datamover to a drive in a library then all drives in that library should have paths defined from that same datamover. A path may have to be updated to specify online=yes. ANR1768E Command: The device name provided conflicts with a device name that is already in use.
Explanation: The 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. System Action: Server operation continues. User Response: Determine why the device type field of the destination device is not valid. ANR1772E The path from source source name to destination drive name is taken offline.
Explanation: The path is now marked offline. System Action: The path is inaccessible. User Response: Determine the reason the path is inaccessible, such as a hardware problem. Make any needed corrections. Then, issue the the UPDATE PATH command with the ONLINE=YES option to make the path online. ANR1773W Unable to update the path in the database path source name and drive drive name .
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 Command: Command failed - multiple actions between commit actions not allowed.
Explanation: The system is unable to update the path information in the database table. System Action: . User Response: None. ANR1774E The Query Status command failed, and server initialization has not completed. Allow server initialization to complete, and then try the command again.
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. System Action: The server does not process the 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: The command Query Status failed because server initialization has not completed. System Action: Server operation continues. User Response: Allow server initialization to complete, and then try the command again. ANR1782W ESTIMATE DBREORG process process number started - server performance may be degraded while this process is running.
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. System Action: Server operation continues. User Response: From the client, quit the current remote image request. Reissue the request, if desired.
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
174
IBM Tivoli Storage Manager: Messages
ANR1783E ANR1791W
database I/O and may impact other server operations and processes while it is running. User Response: This process may be monitored using the QUERY PROCESS command. If this process needs to be cancelled, issue the CANCEL PROCESS command. ANR1783E ESTIMATE DBREORG process process number failed and only evaluated pages evaluated database pages. ANR1786W HBAAPI not able to get adapter name.
Explanation: The HBAAPI function getAdapterName failed. The server will continue to next adapter. System Action: None. User Response: The SAN discovery might not work for this host bus adapter (HBA) . ANR1787W Not able to open adapter adapter name.
Explanation: The ESTIMATE DBREORG process failed to complete successfully. It only evaluated pages evaluated database pages. System Action: None. User Response: If the has been cancelled, this message will be issued. If this processed failed to process but was not cancelled, it is likely that it failed because it was not able to acquire access to the necessary database pages to perform the evaluation. Retry the operation. ANR1784I A database reorganization would reduce the database utilization by an estimated space recovered MB.
Explanation: The HBAAPI function to open the host bus adapter (HBA) failed. System Action: None. User Response: The SAN discovery will not work for this 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. Please login as root and retry. System Action: None. User Response: The SAN discovery will not work for this adapter. ANR1789W Get HBA target mapping failed.
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. ANR1785I ESTIMATE DBREORG process is already running.
Explanation: The HBAAPI function to get the target mapping failed. System Action: None. User Response: The SAN discovery will not work for this adapter. ANR1790W SAN discovery failed.
Explanation: SAN discovery failed. System Action: None. User Response: SAN discovery failed. This may be a problem with the HBA firmware, HBA or the HBA verdors HBAAPI driver. ANR1791W HBAAPI wrapper library file name failed to load or is missing.
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. System Action: None. User Response: Use the QUERY PROCESS command to monitor the existing process. If the existing process needs to be cancelled, issue the CANCEL PROCESS command.
Explanation: This library is provided by Tivoli Storage Manager. It is required for discovery of devices on a SAN. v For windows, the HBAAPI wrapper library is hbaapi.dll. v For AIX, the HBAAPI wrapper library is libHBAAPI.a.
Chapter 3. Common and Platform Specfic Messages
175
ANR1792W ANR1810E
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. ANR1800E Missing or invalid EVENTLOG command parameter.
Explanation: The event logging command issued contains an invalid parameter, or is missing a required parameter. System Action: The command is ignored. User Response: Reissue the command with the proper parameters. ANR1801E Eventlog command: Invalid event or event class - Event or event class name.
System Action: None. User Response: Make sure the HBAAPI wrapper library is in the same directory as the IBM Tivoli Storage Manager server executeable. 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 discovery of devices on a SAN. System Action: None. User Response: Make sure the HBAAPI file exist. You might need to go to the HBA vendors website and download the HBA driver. v For UNIX systems, This HBAAPI vendor librarys location is indicated in /etc/hba.conf. For example: qla2x00 /usr/lib/libqlsdm.so com.emulex.emulexapilibrary /usr/lib/libemulexhbaapi.so v For windows systems, 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 Make sure the HBAAPI file exists. If it does not, go to the host bus adapter (HBA) vendors website and download the HBA driver which include the HBAAPI library. Install the HBA driver. Refer to the HBA vendors HBA installation guide. ANR1793W TSM SAN discovery is not supported on this platform or this version of OS.
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. User Response: Reissue the command with the correct event or event class. 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. User Response: Check the file for proper access permissions, or specify a different file for logging. ANR1809E Insufficient memory to activate event logging.
Explanation: A BEGIN EVENTLOGGING command has been entered, but the server has insufficient memory available to activate logging. System Action: The command is ignored. User Response: If logging is required, make more memory available to the server then restart the server. ANR1810E Eventlog command: Invalid receiver receiverName.
Explanation: The SAN discovery for this platform is currently not supported. System Action: None. User Response: The 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.
Explanation: An event logging command has been entered which specifies an unknown event log receiver (maybe unknown just to this platform). System Action: The command is ignored for the invalid receiver. Any valid receivers specified are processed. User Response: Reissue the command with the correct receiver.
176
IBM Tivoli Storage Manager: Messages
ANR1822I ANR1842E
ANR1822I Event logging ended for the receiverName receiver. ANR1828E Eventlog command: No valid event specified.
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. System Action: None. User Response: None. ANR1823I Event logging ended for all receivers.
Explanation: An event logging command has been entered and no valid events or event classes were specified. System Action: The command is ignored. User Response: Reissue the command with the correct events or event classes. ANR1829E Eventlog command: Server events may not be disabled for the activity log receiver.
Explanation: In response to an END EVENTLOGGING command, event log records are no longer being output to any receiver. System Action: None. User Response: None. ANR1824E Event logging is inactive for the specified receiver.
Explanation: A DISABLE EVENT command has been entered for the activity log receiver. System Action: The command is ignored for the activity log receiver. Any valid receivers specified are processed. User Response: Reissue the command with the correct receiver. ANR1830E receiverName receiver options not defined in the server options file.
Explanation: An END EVENTLOGGING command has been entered, but logging is not active for the specified receiver. System Action: The command is ignored. User Response: If logging is desired, use the ENABLE EVENT and BEGIN EVENTLOGGING commands to activate event logging. ANR1825I Event logging active for the receiverName receiver.
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: In response to a BEGIN EVENTLOGGING command, event log records are now being output to the specified receiver. System Action: None. User Response: None. ANR1826I Event logging active for all receivers.
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. User Response: None. ANR1842E An error occurred on the receiverName receiver.
Explanation: In response to a BEGIN EVENTLOGGING command, event log records are now being output to all receivers. System Action: None. User Response: None. ANR1827E Eventlog command: No valid receiver specified.
Explanation: An error occurred on the specified receiver. System Action: The server no longer sends events to the receiver. User Response: Issue a BEGIN EVENTLOGGING command for the receiver to attempt to start logging events to the receiver again.
Explanation: An event logging command has been entered, and no valid receivers were specified. System Action: The command is ignored. User Response: Reissue the command with the correct receiver.
Chapter 3. Common and Platform Specfic Messages
177
ANR1843I ANR1856W
ANR1843I Event log receiver initialization in progress. to server. Either use shorter server names or change your configuration to reduce the number of hops. ANR1852E Unable to send header to TEC at TEC server rc return code
Explanation: Initialization is starting for the eventlog receivers. System Action: None. User Response: None. ANR1844I Eventlog command command processed.
Explanation: A network error has occurred in attempting to send the event header to the Tivoli Enterprise Console. System Action: None. User Response: Verify network connections and contact your service representative if this error persists. ANR1853E Unable to send data to TEC at TEC server rc return code
Explanation: The specified command was processed. System Action: None. User Response: If any previous messages indicate that parts of the command failed, reissue the command for those parts only. ANR1850E Circular event logging detected. The event server has previously handled event Event number from Source trail. To prevent looping, events which have already been logged by the event server are not sent again. Please correct the situation causing circular logging to avoid wasting system resources.
Explanation: A network error has occurred in attempting to send the event data to the Tivoli Enterprise Console. System Action: None. User Response: Verify network connections and contact your service representative if this error persists. ANR1854E Unable to flush data to TEC at TEC server rc return code
Explanation: The server is attempting to log an event which has previously been handled by the event server that is currently defined. System Action: The event is not sent to the event server. Other events will still be sent, and this message will be issued periodically if this situation is detected again. User Response: Determine what is wrong with the server to server event logging setup, and fix the problem. ANR1851E The source trail for server to server event logging has exceeded the maximum length of Maximum sourcetrail length bytes.
Explanation: A network error has occurred in attempting to flush data to the Tivoli Enterprise Console . System Action: None. User Response: Verify network connections and contact your service representative if this error persists. ANR1855E Failure validating protocol between client and server for node node on session session number
Explanation: While attempting to log an event to the event server, the server has found that the source trail length is too long. System Action: The server continues to try to send the event to the event server, but the source trail may be truncated and appear something like: name1>...>namex>namey where, is the originator of the event. is where intervening server name(s) have been left off the source trail.
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. System Action: None. User Response: Verify network connections and contact your service representative if this error persists. ANR1856W Command: No volumes selected to process.
name1 ...
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
User Response: Most likely you are using very long server names and/or have excessive hops from server
178
IBM Tivoli Storage Manager: Messages
ANR1857I ANR1996E
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. 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. 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: 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. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to audit the volume or 'N' to stop the process. ANR1858I AUDIT VOLUME will start count inspect processes.
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. System Action: None. User Response: None. ANR1995E Command: Invalid Formatsize value formatsize value for device class Device Class
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. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to audit the volume or 'N' to stop the process. ANR1859W Node node on session session id received CRC protocol validation information when it is not configured to do so.
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. System Action: The server does not process the command. User Response: Reissue the command with a Formatsize value which is less than the maximum capacity value of the storage pool. The maximum capacity can be displayed with the QUERY DEVCLASS classname F=D command. ANR1996E Command: Invalid volume name prefix volume name. Room for additional characters is required.
Explanation: The 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. System Action: The server operation continues. 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
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. System Action: The server does not process the command. User Response: Reissue the command with a prefix short enough to allow for the suffix. Three extra characters are needed for the suffix.
Chapter 3. Common and Platform Specfic Messages
179
ANR1997E ANR2007E
ANR1997E Command: The Formatsize parameter must be specified when more than 1 volume is created. ANR2002E Missing closing quote character.
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. System Action: The server does not process the command. User Response: Reissue the command with the Formatsize parameter or define a single volume without the Formatsize parameter. ANR1998E Command: Invalid value for parameter parameter - parameter value.
Explanation: A server command that contains a quoted parameter has been entered, but a matching closing quote is missing. System Action: The server ignores the command. User Response: Reissue the command with properly matched quotes. 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. System Action: The server ignores the command. User Response: Reissue the command and enter the proper syntax. ANR2004E Missing value for keyword parameter parameter.
Explanation: The value (parameter value) specified for the (parameter) parameter in command command is not a valid value for this parameter. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid parameter value. For information on valid values for the parameter for the command, refer to the Administrators Reference for your particular platform. ANR1999I Command completed successfully.
Explanation: A server command containing a keyword parameter has been entered, but the value for the parameter is missing. System Action: The server ignores the command. User Response: Reissue the command and supply a value for the keyword parameter. ANR2005E Keyword parameter character (=) may not be surrounded by blanks.
Explanation: Processing for the specified command completed successfully. System Action: Server processing continues. User Response: None. ANR2000E Unknown command - command.
Explanation: A server command contains a keyword parameter followed by an equal sign (=), but the equal sign is preceded or followed by a blank, or both. System Action: The server ignores the command.
Explanation: The specified command is not a valid server command. System Action: The server ignores the command. User Response: Reissue the correct command. ANR2001E Insufficient server memory to initiate command.
User Response: Reissue the command without blanks next to the equal sign. ANR2006E Activity log process was not started, the default output stream cannot be opened.
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. User Response: Contact your service representative. ANR2007E Activity log process was not started, due to an internal error.
Explanation: A command has been entered, but the server cannot obtain enough internal memory to process the command. System Action: The server ignores the command. 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.
Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot start due to a server internal error.
180
IBM Tivoli Storage Manager: Messages
ANR2008E ANR2014E
System Action: The server does not update the activity log. 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. ANR2008E Activity log process has stopped database transaction could not be started. 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.
Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot update the activity log due to a lack of database space. System Action: The server does not update the activity log. User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used. ANR2012W Activity log process has encountered unexpected table data output in the default output stream.
Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot continue due to a server transaction failure. This may be a memory shortage error. System Action: The server stops updating the activity log. 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. ANR2009E Activity log process has stopped database error.
Explanation: The process that monitors the default (console) output stream and maintains the activity log has detected invalid data in the console stream. System Action: The server stops updating the activity log. User Response: Contact your service representative. ANR2013E The activity log process has encountered unexpected output data in the console output stream. The process will be restarted.
Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot continue due to a server database error. System Action: The server stops updating the activity log. User Response: Contact your service representative. 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.
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. User Response: The server may be low on available memory. Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see Appendix A. Allocating Additional Server Memory. ANR2014E Activity log pruning process could not be started, due to an internal error.
Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot update the activity log due to a lack of recovery log space. System Action: The server does not update the activity log. User Response: An authorized administrator can issue 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.
Explanation: The process that removes expired records from the server activity log cannot begin execution due to a server internal error. System Action: The server does not prune the activity log. User Response: Examine the server messages issued prior to this message to determine the source of the
Chapter 3. Common and Platform Specfic Messages
181
ANR2015E ANR2025E
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. ANR2015E Activity log failure - database transaction could not be started. ANR2020E Command: Invalid parameter - parameter.
Explanation: The specified server command has been entered with an invalid parameter. System Action: The server ignores the command. User Response: Reissue the command and enter the proper syntax. ANR2021E Command: Missing subcommand keyword.
Explanation: The process that removes expired records 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. 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. ANR2016E Activity log failure - database error.
Explanation: The specified server command has been entered without a valid subcommand (second parameter). System Action: The server ignores the command. User Response: Reissue the command and enter the proper syntax. ANR2022E Command: One or more parameters are missing.
Explanation: The process that removes expired records from the server activity log has failed due to a server database error. System Action: The server ends activity log pruning. User Response: Contact your service representative. ANR2017I Administrator Administrator Name issued command: Command
Explanation: The specified server command has been entered without all required parameters. System Action: The server ignores the command. User Response: Reissue the command and enter the proper syntax. ANR2023E Command: Extraneous parameter parameter.
Explanation: This message records the fact that the named administrator issued the command specified. The messages is issued and logged to provide an audit trail for administrative commands. System Action: Server operation continues User Response: None. ANR2018E Administrator Command: Unicode conversion failed for argument Command Argument
Explanation: The specified server command contains more positional parameters than is allowed. System Action: The server ignores the command. User Response: Reissue the command and enter the proper syntax. ANR2024E Command: Too many parameters specified.
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. ANR2019I Command: No nodes updated.
Explanation: The specified server command contains more positional parameters than is allowed. System Action: The server ignores the command. User Response: Reissue the command and enter the proper syntax. ANR2025E Command: Command failed - server thread resource not available.
Explanation: An UPDATE NODE command has been entered, but no objects were updated. System Action: None. User Response: None.
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. System Action: The command is not executed. User Response: Reissue the command. If the
182
IBM Tivoli Storage Manager: Messages
ANR2026E ANR2034E
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. 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. System Action: The server does not process the COMMIT command. User Response: Stop the administrative session, restart it, and try the command again. If this problem persists, contact your service representative. ANR2031E Command: At least one attribute must be specified for update.
Explanation: A server command has been entered but cannot be processed because sufficient memory is not available to the server. System Action: The server does not process the command. 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. ANR2027E Command: Command failed - sufficient server recovery log space is not available.
Explanation: The specified UPDATE command has been entered, but no attributes have been specified for updating. System Action: The server ignores the command. User Response: Reissue the UPDATE command with one or more attributes to be updated. ANR2032E Command: Command failed - internal server error detected.
Explanation: A server command has been entered but cannot be processed because sufficient recovery log space is not available. System Action: The server does not process the command. User Response: An authorized administrator can issue 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. ANR2028E Command: Command failed - sufficient server database space is not available.
Explanation: An internal error has occurred during an attempt to process a server command. This message always accompanies another error message and provides more detail about that error. System Action: The server does not process the command. 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. ANR2033E Command: Command failed - lock conflict.
Explanation: A server command has been entered but cannot be processed because sufficient database space is not available. System Action: The server does not process the command. User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used. ANR2029E Command: Transaction failed; command not executed.
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. System Action: The server does not process the command. User Response: Try the command again at a later time. ANR2034E Command: No match found using this criteria.
Explanation: A command that is part of the current transaction has failed; therefore, any additional commands fail. System Action: The server does not process the command. User Response: Stop the administrative session, restart it, and try the command again. If this problem persists, contact your service representative.
Explanation: The specified command has been entered, but no objects that match the criteria can be found. System Action: None.
Chapter 3. Common and Platform Specfic Messages
183
ANR2035E ANR2041W
User Response: None. ANR2035E Command: Administrator administrator name is not authorized to issue this command. User Response: If necessary, reissue the command. If the command fails with the same error, wait for server activity to decrease and try again. ANR2039E Command: Process could not be started internal server error detected.
Explanation: The specified administrator has entered the indicated command, but this administrator does not 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. System Action: The server does not process the 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 Command: Process could not be started sufficient memory is not available.
Explanation: A background process cannot be started for the indicated command because an internal error has occurred. System Action: A new process is not started to execute this command. If other processes have been started for this command, these processes may execute successfully. 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. ANR2040W This command attempts to restore all files in storage pool storage pool which have previously been found to be damaged or which reside on a volume with access mode destroyed; existing references to files in storage pool storage pool will be deleted from the database after the files have been restored.
Explanation: A background process cannot be started for the indicated command because sufficient memory is not available to the server. System Action: A new process is not started to execute this command. 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. ANR2037E Command: Process could not be started lock conflict.
Explanation: A background process cannot be started for the indicated command because a required system resource is already locked by another command or process. System Action: A new process is not started to execute this command. If other processes have been started for this command, these processes may execute successfully. User Response: If necessary, try the command again at a later time. ANR2038E Command: Process could not be started server thread resource not available.
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. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to restore the storage pool, 'N' otherwise. ANR2041W 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: A background process cannot be started for the indicated command because no server thread is available. System Action: A new process is not started to execute this command. If other processes have been started for this command, these processes may execute successfully.
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
184
IBM Tivoli Storage Manager: Messages
ANR2042E ANR2051E
another location, the destroyed volume will be deleted from the database. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to restore the volumes, 'N' otherwise. ANR2042E Command: Copied parameter not valid for copy storage pool volume. User Response: None. ANR2047E Command: Optionset optionset name is already defined.
Explanation: A DEFINE OPTIONSET command has been entered that specifies an optionset name already defined to the server. System Action: The server does not process the command. User Response: To define the optionset, reissue the command and specify a different optionset name. ANR2048I Command: Optionset optionset name deleted.
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 storage pool. System Action: The server ignores the command. User Response: Reissue the command without the COPIED parameter. ANR2043E Command: WAIT parameter not allowed from server console.
Explanation: The requested option set has been deleted from the system in response to a DELETE OPTIONSET command. System Action: None. User Response: None. ANR2049E Command: Optionset optionset name is not defined.
Explanation: The WAIT parameter is not allowed for commands issued from the server console. System Action: The command is not executed. 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.
Explanation: The command shown specifies an optionset that is not defined in the server. System Action: The server does not process the command. User Response: None. ANR2050I Command: Option option name defined in optionset option set name.
Explanation: The set option command has been entered with an invalid value. System Action: The server does not process the command. User Response: Reissue the command with a valid value. ANR2045E Command: An error (error code) occurred during a write operation.
Explanation: The requested option has been added to the specified optionset in response to a DEFINE OPTIONSET command. System Action: None. User Response: None. ANR2051E Command: Option option name, sequence number sequence number is already defined in optionset option set name.
Explanation: The server detects an error while attempting a write operation. System Action: Server processing continues. 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 already exists in the optionset specified by the DEFINE CLIENTOPT command. System Action: The server does not process the command. User Response: None.
Explanation: The requested option set has been added to the system in response to a DEFINE OPTIONSET command. System Action: None.
Chapter 3. Common and Platform Specfic Messages
185
ANR2052E ANR2061I
ANR2052E Command: Option option name, sequence number sequence number is not defined in optionset option set name. ANR2057E Command: Invalid option value - option value.
Explanation: The requested option is not defined in the optionset specified by the DELETE CLIENTOPT command. System Action: The server does not process the command. User Response: None.
Explanation: The command shown specifies an invalid option value. System Action: The server does not process the command. User Response: Reissue the command with a valid option value. ANR2058W Command: Options file Filespec not found - user needs to update the file manually.
ANR2053I
Command: Option option name, sequence number sequence number, has been deleted from optionset option set name.
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. ANR2059W Command: Error occurs when writing to Filespec - user needs to update the file manually.
Explanation: The requested option has been deleted from the specified optionset in response to a DELETE CLIENTOPT command. System Action: None. User Response: None. ANR2054I Command: Optionset optionset name updated.
Explanation: The requested option set has been updated in the system in response to an UPDATE OPTIONSET command. System Action: None. User Response: None. ANR2055I Command: Optionset source optionset name copied to optionset target optionset name.
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: This message is displayed in response to the COPY OPTIONSET command. The optionset named source optionset name has been copied to the optionset named target optionset name. System Action: Server operation continues. User Response: None. The requested option set has been added to the system in response to a COPY OPTIONSET command. ANR2056E Command: Invalid option name - option name. Retry using the full optionname.
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. System Action: None. User Response: None. ANR2061I Node node name removed from policy domain domain name.
Explanation: The command shown specifies an invalid option name. System Action: The server does not process the command. User Response: Reissue the command with a valid option name.
Explanation: In response to a REMOVE NODE command, the requested backup-archive node has been removed from the system. System Action: None. User Response: None.
186
IBM Tivoli Storage Manager: Messages
ANR2062I ANR2074I
ANR2062I Node node name renamed to new node name. System Action: None. User Response: None. ANR2069I Administrator administrator ID removed.
Explanation: In response to a RENAME NODE command, the requested backup-archive node has been renamed to the new name shown. System Action: None. User Response: None. ANR2063I Node node name updated.
Explanation: In response to a REMOVE ADMIN command, the requested administrator ID has been removed from the system. System Action: None. User Response: None. ANR2070I Administrator administrator ID renamed to new administrator ID.
Explanation: One or more attributes of a backup-archive node have been updated by an UPDATE NODE command. System Action: None. User Response: None. ANR2064I Node node name locked.
Explanation: In response to a RENAME ADMIN command, the requested administrator ID has been changed to the new name shown. System Action: None. User Response: None. ANR2071I Administrator administrator ID updated.
Explanation: In response to a LOCK NODE command, the indicated backup-archive node has been locked. System Action: None. User Response: None. ANR2065I Node node name is already locked.
Explanation: One or more attributes of an administrative user have been updated by an UPDATE ADMIN command. System Action: None. User Response: None. ANR2072I Administrator administrator ID locked.
Explanation: The indicated backup-archive node referenced in the LOCK NODE command is already locked. System Action: None. User Response: None. ANR2066I Node node name unlocked.
Explanation: In response to a LOCK ADMIN command, the indicated administrator ID has been locked. System Action: None. User Response: None. ANR2073I Administrator administrator ID is already locked.
Explanation: In response to an UNLOCK NODE command, the indicated backup-archive node is unlocked. System Action: None. User Response: None. ANR2067I Node node name is already unlocked.
Explanation: The indicated administrator ID referenced in the LOCK ADMIN command is already locked. System Action: None. User Response: None. ANR2074I Administrator administrator ID unlocked.
Explanation: The indicated backup-archive node referenced in the UNLOCK NODE command is not locked. System Action: None. User Response: None. ANR2068I Administrator administrator ID registered.
Explanation: In response to an UNLOCK ADMIN command, the indicated administrator ID is unlocked. System Action: None. User Response: None.
Explanation: In response to a REGISTER ADMIN command, the requested administrator ID has been added to the system.
Chapter 3. Common and Platform Specfic Messages
187
ANR2075I ANR2085I
ANR2075I Administrator administrator ID is already unlocked. System Action: None. User Response: None. ANR2081I Analyst privilege granted to administrator administrator ID.
Explanation: The indicated administrator ID referenced in the UNLOCK ADMIN command is not locked. System Action: None. User Response: None. ANR2076I System privilege granted to administrator administrator ID.
Explanation: In response to a GRANT AUTHORITY command, analyst privilege class has been granted to the indicated administrator. System Action: None. User Response: None. ANR2082I Operator privilege granted to administrator administrator ID.
Explanation: In response to a GRANT AUTHORITY command, system privilege class has been granted to the indicated administrator. System Action: None. User Response: None. ANR2077I Unrestricted policy privilege granted to administrator administrator ID.
Explanation: In response to a GRANT AUTHORITY command, operator privilege class has been granted to the indicated administrator. System Action: None. User Response: None. ANR2083I System privilege revoked for administrator administrator ID.
Explanation: In response to a GRANT AUTHORITY command, unrestricted policy privilege has been granted to the indicated administrator. System Action: None. User Response: None. ANR2078I Restricted policy privilege granted to administrator administrator ID - policy domain domain name.
Explanation: In response to a REVOKE AUTHORITY command, system privilege class has been revoked from the indicated administrator. System Action: None. User Response: None. ANR2084I Policy privilege revoked for administrator administrator ID.
Explanation: In response to a GRANT AUTHORITY command, restricted policy privilege for the specified policy domain has been granted to the indicated administrator. System Action: None. User Response: None. ANR2079I Unrestricted storage privilege granted to administrator administrator ID.
Explanation: In response to a REVOKE AUTHORITY command, policy privilege class for all policy domains has been revoked from the indicated administrator. System Action: None. User Response: None. ANR2085I Restricted policy privilege revoked for administrator administrator ID - policy domain domain name.
Explanation: In response to a GRANT AUTHORITY command, unrestricted storage privilege has been granted to the indicated administrator. System Action: None. User Response: None. ANR2080I Restricted storage privilege granted to administrator administrator ID - storage pool storage pool name.
Explanation: In response to a REVOKE AUTHORITY command, restricted policy privilege for the specified policy domain has been revoked from the indicated administrator. System Action: None. User Response: None.
Explanation: In response to a GRANT AUTHORITY command, restricted storage privilege for the specified storage pool has been granted to the indicated administrator.
188
IBM Tivoli Storage Manager: Messages
ANR2086I ANR2096I
ANR2086I Storage privilege revoked for administrator administrator ID. ANR2091I Accounting parameter set to value.
Explanation: In response to a REVOKE AUTHORITY command, storage privilege class for all storage pools has been revoked from the indicated administrator. System Action: None. User Response: None.
Explanation: Accounting record generation has been turned on or off as indicated with the SET ACCOUNTING command. System Action: None. User Response: None. ANR2092I Password expiration period set to number of days days.
ANR2087I
Restricted storage privilege revoked for administrator administrator ID - storage pool storage pool name.
Explanation: In response to a REVOKE AUTHORITY command, restricted storage privilege for the storage pool indicated has been revoked from the indicated administrator. System Action: None. User Response: None. ANR2088I Analyst privilege revoked for administrator administrator ID.
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. System Action: None. User Response: None. ANR2093I Registration parameter set to registration method.
Explanation: Backup-archive node registration has been set to the method indicated with the SET REGISTRATION command. System Action: None. User Response: None. ANR2094I Server name set to server name.
Explanation: In response to a REVOKE AUTHORITY command, analyst privilege class has been revoked from the indicated administrator. System Action: None. User Response: None. ANR2089I Operator privilege revoked for administrator administrator ID.
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. System Action: None. User Response: None. ANR2095I Authentication parameter set to value.
Explanation: In response to a REVOKE AUTHORITY command, operator privilege class has been revoked from the indicated administrator. System Action: None. User Response: None. ANR2090I Activity log retention set to value for management by management style.
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. System Action: None. User Response: None. ANR2096I Server now enabled for backup/archive client access.
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. System Action: None. User Response: None.
Explanation: The server has been made available for use by backup-archive clients with the ENABLE command. System Action: None. User Response: None.
Chapter 3. Common and Platform Specfic Messages
189
ANR2097I ANR2106I
ANR2097I Server now disabled for backup/archive client access. ANR2103I Activity log pruning completed: number of records records removed.
Explanation: The server has been made unavailable for use by backup-archive clients with the DISABLE command. System Action: None. User Response: None. ANR2098E Command: Invalid URL specification url.
Explanation: All expired (older than the log archive retention value) server activity log records have been removed; the number of records deleted is shown. System Action: None. User Response: None. ANR2104I Activity log process restarted - recovered from an insufficient space condition in the Log or Database.
Explanation: The specified URL is too long. System Action: The server ignores the command. User Response: Reissue the command and enter a shorter URL value ANR2099I Administrative userid admininstrator name defined for OWNER access to node node name.
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. User Response: None. ANR2105W Command: Node was registered in excess of license terms - node registration will fail after 120% of the licensed quantity of nodes have been registered.
Explanation: 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. System Action: None. User Response: None. ANR2100I Activity log process has started.
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. System Action: Server operation continues. User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance. You may remove nodes to reduce the number of registered nodes or purchase additional client node connections. If additional nodes have been purchased, issue the AUDIT LICENSES command to resynchronize the server configuration with license terms. ANR2106I Server HALT command: Quiescing database update activity.
Explanation: The automatic server process that removes expired server activity log records has begun processing. System Action: None. User Response: None. 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. User Response: None. ANR2102I Activity log pruning started: removing entries prior to date time.
Explanation: The server is quiescing transactions that update the database so that the database is in a consistent state when the server is halted. This action occurs when HALT QUIESCE is specified to halt the server with the database in a consistent state. System Action: When database update transaction activity has been stopped, the server program ends. User Response: None.
Explanation: Server activity log records older than the date and time indicated are being removed from the activity log. System Action: None. User Response: None.
190
IBM Tivoli Storage Manager: Messages
ANR2107I ANR2115E
ANR2107I Server HALT command: Database update activity is now quiesced. CANCEL PROCESS command. Use the process ID number to specify this process. ANR2111W Command: There is no data to process for storage pool.
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. User Response: None. ANR2108I Server HALT command: Reattempting to quiesce database update activity.
Explanation: The indicated command does not have any data to process. This can occur if the command specifies an empty volume or pool. The command ends without starting a background process. System Action: None. User Response: None. ANR2112E Command: Volume volume name is not in a primary storage pool.
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. User Response: None. ANR2109I Server HALT command: Database update transaction activity could not be successfully quiesced.
Explanation: The command indicated specifies the 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. System Action: The server does not process the 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: 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. System Action: Server operation continues. 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.
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. System Action: The server does not process the 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. User Response: None. ANR2115E Command: Access mode for volume volume name cannot be changed to destroyed - volume is still online.
Explanation: A background process has been started to service the command command. The background process is defined as process process ID. System Action: The server processes the indicated command. User Response: To query the progress of the background process, use the QUERY PROCESS command. To cancel the background process, use the
Explanation: A RESTORE VOLUME command cannot change the access mode of the indicated volume to destroyed because the volume is still online. System Action: The server does not process the command.
Chapter 3. Common and Platform Specfic Messages
191
ANR2116E ANR2123E
User Response: Issue the VARY OFFLINE command, and reissue the RESTORE VOLUME command. ANR2116E Command: Access mode for volume volume name cannot be changed to destroyed - volume does not belong to a primary storage pool. ANR2120E Command: Invalid platform name platform name.
Explanation: The command shown specifies an invalid platform name. System Action: The server does not process the command. User Response: Reissue the command with a valid 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.
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. User Response: None. ANR2117E Command: Access mode for volume volume name cannot be changed to offsite - volume either does not belong to a copy storage pool or from a device class of DEVTYPE=SERVER.
Explanation: The access mode for the indicated volume cannot be changed to offsite because the volume either does not belong to a copy storage pool or is of a device class with a DEVTYPE of SERVER. System Action: The access mode for this volume is not changed. User Response: None.
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. System Action: Server operation continues. User Response: To provide for server database recovery should a hardware or software problem affect your database, use the BACKUP DB command to back up the database. ANR2122E command name: The DOMAINS parameter cannot be specified when the NODES parameter is specified.
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. 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: 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. System Action: The command fails. User Response: Reenter the command specifying either the NODES parameter or the DOMAINS parameter, but not both. ANR2123E command name: The NODES parameter cannot be specified when the DOMAINS parameter is specified.
Explanation: The option is updated in the server options file. System Action: Server continues. User Response: None.
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. System Action: The command fails. User Response: Reenter the command specifying either the NODES parameter or the DOMAINS parameter, but not both.
192
IBM Tivoli Storage Manager: Messages
ANR2124E ANR2134I
ANR2124E command name: Invalid Client authority specified: authority. ANR2129I Administrative userid admininstrator name defined ONLY for authority over node node name has been removed.
Explanation: An invalid client authority was specified in a GRANT AUTHORITY or REVOKE AUTHORITY command when the CLASS=NODE parameter was specified. System Action: The command fails. User Response: Reenter the command specifying a valid client authority. ANR2125I command name: Administrator administrator name was granted OWNER authority for client client name.
Explanation: The specified administrator has been removed because the client node was removed and the administrator onyly had OWNER access to the specified node. System Action: None. User Response: None. ANR2130S Early Product Version has Expired. Server is HALTing.
Explanation: The named administrator was granted OWNER authority over the named client node as the result of a GRANT AUTHORITY command. System Action: Processing continues. User Response: None. ANR2126I command name: Administrator administrator name was granted ACCESS authority for client client name.
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. ANR2131I Server password set.
Explanation: The named administrator was granted ACCESS authority over the named client node as the result of a GRANT AUTHORITY command. System Action: Processing continues. User Response: None.
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. System Action: None. User Response: None. ANR2132I Server hladdress set to hladdress.
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. System Action: Processing continues. User Response: None. ANR2128I command name: Access authority for node client node was revoked for administrator administrator.
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. System Action: None. User Response: None. 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. System Action: None. User Response: None. ANR2134I Server url set to url.
Explanation: ACCESS authority over the named client node was revoked from the named administrator as a result of a REVOKE AUTHORITY command. System Action: Processing continues. User Response: None.
Explanation: The url that other servers use to communicate with this server has been set to the value indicated with the SET SERVERURL command. System Action: None.
Chapter 3. Common and Platform Specfic Messages
193
ANR2135I ANR2144E
User Response: None. ANR2135I Crossdefine set to state. ANR2140E Command: Invalid activity log retention period - retention value.
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. System Action: None. User Response: None. ANR2136I Administrator administrator name already has POLICY access for domain policy domain name.
Explanation: A SET ACTLOGRETENTION command has been entered that specifies an invalid log retention period. System Action: The server does not process the command. User Response: Reissue the command with a valid retention period. ANR2141E Command: Invalid password expiration period - days value.
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. User Response: None.
Explanation: A SET PASSEXP command has been entered that specifies an invalid days value. System Action: The server does not process the command. User Response: Reissue the command with a password expiration period. ANR2142E Command: Invalid server name - server name.
ANR2137I
Administrator administrator name already has POLICY access for domain policy domain name to which node node name belongs.
Explanation: A SET SERVERNAME command has been entered that specifies an invalid server name. System Action: The server does not process the command. User Response: Reissue the command with a valid server name. ANR2143E Command: Invalid node name - node name.
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. User Response: None. ANR2138I Minimum password length set to length.
Explanation: The command shown specifies an invalid node name. System Action: The server does not process the command. User Response: Reissue the command with a valid node name. ANR2144E Command: Invalid password - password.
Explanation: The minimum length of a password a node or administrator may send to the server is indicated with the SET MINPWLENGTH command. System Action: None. User Response: None. ANR2139E Command: The value supplied for the minimum password length is not valid length.
Explanation: The command specifies an invalid node password. System Action: The server does not process the 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.
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. System Action: The server does not process the command. User Response: Reissue the command with a valid value.
194
IBM Tivoli Storage Manager: Messages
ANR2145E ANR2154E
ANR2145E Command: Contact information exceeds maximum characters characters. ANR2150E Command: Node node name is currently accessing the server.
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. System Action: The server does not process the 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 has an active session with the server. System Action: The server does not process the command. User Response: Reissue the command at a later time, or if necessary, cancel the current session and reissue the command. ANR2151E Command: Administrator administrator ID is currently accessing the server.
Explanation: The command shown specifies a node that is not registered with the server. System Action: The server does not process the command. User Response: None. ANR2147E Command: Node node name is already registered.
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. System Action: The server does not process the command. User Response: Reissue the command at a later time, or if necessary, cancel the current session and reissue the command. 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. System Action: The server does not process the command. User Response: To register the node, reissue the command and specify a different node name. ANR2148E Command: Administrator administrator ID is not registered.
Explanation: A REMOVE NODE command has been entered for a node for which the server is still storing backup or archive data, or both. System Action: The server does not process the command. User Response: To remove the node, delete all of its file spaces and any virtual file space mapping definitions from the server and reissue the command. ANR2153E Command: Invalid file space name filespace name.
Explanation: The command shown specifies an administrator ID that is not registered with the server. System Action: The server does not process the command. User Response: None. ANR2149E Command: Administrator administrator ID is already registered.
Explanation: The specified server command has been entered with a file space name that is longer than allowed. System Action: The server does not process the command. User Response: Reissue the command with a valid file space name. ANR2154E Command: Invalid administrator name administrator ID.
Explanation: A REGISTER ADMIN command has been entered that specifies an administrator ID already registered with the server. System Action: The server does not process the command. User Response: To register the administrator, reissue the command and specify a different administrator ID.
Explanation: The command shown specifies an invalid administrator ID. System Action: The server does not process the command.
Chapter 3. Common and Platform Specfic Messages
195
ANR2155E ANR2164E
User Response: Reissue the command with a valid administrator ID. ANR2155E Command: Invalid privilege class privilege class. System Action: The server does not process the command. User Response: None. ANR2160E Command: No new privileges granted to administrator administrator ID.
Explanation: A command specifies an invalid administrative privilege class. System Action: The server does not process the command. User Response: Reissue the command with a valid privilege class. ANR2156E Command: Administrator administrator ID has already been granted system privilege.
Explanation: A GRANT AUTHORITY command has been issued to grant authority to an administrator ID, but the administrator already has all privileges specified. System Action: The server does not process the command. User Response: None. ANR2161E Command: Only system privilege can be revoked for administrator administrator ID.
Explanation: A GRANT AUTHORITY command has been issued to grant system authority to an administrator ID that already has system authority. System Action: The server does not process the command. User Response: None. ANR2157E Command: Other privileges cannot be granted with system privilege.
Explanation: A REVOKE AUTHORITY command has been issued to revoke one or more of an administrators privileges, but the administrator has system authority. System Action: The server does not process the command. User Response: None. ANR2162E Command: No privileges revoked for administrator administrator ID.
Explanation: A GRANT AUTHORITY command has been issued to grant system authority to an administrator ID, and at the same time to grant other privileges. System Action: The server does not process the command. User Response: Reissue the GRANT AUTHORITY command specifying only system privilege class. ANR2158E Command: Policy domains cannot be specified for unrestricted policy administrator administrator ID.
Explanation: A REVOKE AUTHORITY command has been issued to revoke authority from an administrator ID, but the administrator does not have any of the privileges specified. System Action: The server does not process the command. User Response: None. ANR2163E Command: Command is invalid for administrator ID.
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. System Action: The server does not process the command. User Response: None. ANR2159E Command: Storage pools cannot be specified for unrestricted storage administrator administrator ID.
Explanation: The command specified cannot be issued for the server console. For instance, the server console administrator ID cannot be removed. System Action: The server does not process the command. User Response: None. ANR2164E Command: Command rejected administrator ID is the only system administrator.
Explanation: A REVOKE AUTHORITY command has been issued to revoke an administrators storage authority over a specific storage pool, but the administrator has unrestricted storage authority.
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.
196
IBM Tivoli Storage Manager: Messages
ANR2165E ANR2174E
System Action: The server does not process the 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. User Response: Reissue the command with a valid message number. ANR2170E Command: Invalid message search string argument - search string.
Explanation: A QUERY ACTLOG command has been entered that specifies an invalid begin date as a search criteria. System Action: The server does not process the command. User Response: Reissue the command with a valid begin date. ANR2166E Command: Invalid begin time - time.
Explanation: A QUERY ACTLOG command has been entered that specifies an invalid search string as a search criteria. System Action: The server does not process the command. User Response: Reissue the command with a valid search string. ANR2171E Command: Invalid time range - Begin: date time End: date time.
Explanation: A QUERY ACTLOG command has been entered that specifies an invalid begin time as a search criteria. System Action: The server does not process the command. User Response: Reissue the command with a valid begin time. ANR2167E Command: Invalid end date - date.
Explanation: A QUERY ACTLOG command has been 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. System Action: The server does not process the command. User Response: Reissue the command with a valid date/time range. ANR2172E Command: No matching administrators.
Explanation: A QUERY ACTLOG command has been entered that specifies an invalid end date as a search criteria. System Action: The server does not process the command. User Response: Reissue the command with a valid end date. ANR2168E Command: Invalid end time - time.
Explanation: The command shown specified an administrator ID that does not match any administrator registered with the server. System Action: The command is not executed. User Response: If desired, reissue the command with a different administrator ID. ANR2173E Command: Location information exceeds maximum characters characters.
Explanation: A QUERY ACTLOG command has been entered that specifies an invalid end time as a search criteria. System Action: The server does not process the command. User Response: Reissue the command with a valid end time. ANR2169E Command: Invalid message number message number.
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. System Action: The server does not process the 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.
Explanation: A QUERY ACTLOG command has been entered that specifies an invalid message number as a search criteria. System Action: The server does not process the command.
Explanation: The command shown specifies an administrator ID that is not registered with the server. The schedule and related command are not processed.
Chapter 3. Common and Platform Specfic Messages
197
ANR2175I ANR2182W
System Action: The server does not process the 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. ANR2179E Administrator administrator should have been locked, but was not.
Explanation: The indicated administrator reached the limit for consecutive invalid passwords and should have been locked. If it were locked, there would be no means to execute commands requiring system authority. System Action: The administrator session will be refused. User Response: Sign-on again using the correct password. ANR2180W Unable to update last access date for administrator administrator ID insufficient recovery log space.
Explanation: The maximum number of consecutive invalid passwords a node or administrator may send to the server is indicated with the SET INVALIDPWLIMIT command. System Action: None. User Response: None. ANR2176E Command: The value supplied for the 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 values are from 0 to 9999, inclusive. System Action: The server does not process the command. User Response: Reissue the command with a valid value. ANR2177I node/admin name has count invalid sign-on attempts. The limit is limit.
Explanation: While establishing an administrative session for the indicated ID, the server is unable to update the administrators date of last access due to insufficient recovery log space. System Action: The server establishes the administrative session, but the last access date is not updated. User Response: An authorized administrator can issue 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. ANR2181W Unable to update last access date for administrator administrator ID insufficient database space.
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. User Response: Before the client node is permitted to access the server, a properly authorized administrator 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: 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 administrative session, but the last access date is not updated. User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used. ANR2182W Unable to update last access date for administrator administrator ID - internal server error.
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. User Response: Before the client node is permitted to access the server, a properly authorized administrator must unlock the node or administrator with the UNLOCK NODE or UNLOCK ADMIN command.
Explanation: While establishing an administrative session for the indicated ID, the server cannot update the administrators date of last access due to a server internal error. System Action: The server establishes the
198
IBM Tivoli Storage Manager: Messages
ANR2183W ANR2189W
administrative session, but the last access date is not updated. 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. ANR2183W DiagnosticID: Transaction transaction ID was aborted. messages that give additional information about the failed transaction. System Action: The activity that generated this error fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR2187W Transaction was aborted for node/admin name.
Explanation: An error was detected during transaction commit. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The activity that generated this error fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR2184W DiagnosticID: Transaction transaction ID was aborted for command command.
Explanation: An error is detected during a transaction commit for the specified node or administrator name. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The activity that generated this error fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR2188W A Transaction was aborted. The activity is terminating.
Explanation: An error was detected during transaction commit for the specified server command. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The activity that generated this error fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR2185W Transaction was aborted for command command.
Explanation: An error is detected during a transaction commit. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The activity that generated this error ends. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR2189W DiagnosticID: Transaction transaction ID was aborted for node/admin name.
Explanation: An error was detected during transaction commit. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The activity that generated this error fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR2186W Transaction was aborted for session session number for node node name (client platform).
Explanation: An error is detected during a transaction commit for the specified node or administrator name. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The activity that generated this error fails. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.
Explanation: An error was detected during transaction commit. This message should be preceded by other
Chapter 3. Common and Platform Specfic Messages
199
ANR2190E ANR2199I
ANR2190E command: Device class DISK cannot be specified for this command. ANR2195E Command: Invalid option sequence number - option sequence number name.
Explanation: The DEVCLASS value DISK cannot be specified for the command. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server. ANR2191E command: Volume list contains defined and undefined volumes.
Explanation: The command shown specifies an invalid option sequence number. System Action: The server does not process the command. User Response: Reissue the command with a valid option sequence number. ANR2196E Command: Option name and/or Option value is missing for define.
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. System Action: The command fails and server operation continues. User Response: Reissue the command and specify a valid list of volumes. ANR2192E Command: Unable to start background process.
Explanation: The specified DEFINE command has been entered, but no attributes have been specified for the definition. System Action: The server does not process the command. User Response: Reissue the DEFINE command with one or more attributes to be defined ANR2197E Command: The value supplied for the WEB authentication time out is not valid - time-out value.
Explanation: The server command processor is not able to start a background process to perform the command command. System Action: The command process ends and server operation continues. 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. ANR2193E Command: Invalid option set name option set name.
Explanation: A SET WEBAUTHTIMEOUT command has been entered that specifies a value that is not valid. Valid values are from 0 to 9999, inclusive. System Action: The server does not process the command. User Response: Reissue the command with a valid value. ANR2198I Command: Web authentication time-out set to time-out value minutes.
Explanation: The command shown specifies an invalid option set name. System Action: The server does not process the command. User Response: Reissue the command with a valid option set name. ANR2194E Command: Invalid option set description - too long.
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. System Action: None. User Response: None. ANR2199I Password expiration period for node node name set to number of days days.
Explanation: The command shown specifies an invalid description. The description is too long. System Action: The server does not process the command. User Response: Reissue the command with a valid description.
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. System Action: None. User Response: None.
200
IBM Tivoli Storage Manager: Messages
ANR2200I ANR2211I
ANR2200I Storage pool storage pool name defined (device class device class name). ANR2207I Volume volume name updated.
Explanation: A DEFINE STGPOOL command has created the storage pool indicated of the device class shown. System Action: None. User Response: None. ANR2201I Storage pool storage pool name deleted.
Explanation: An UPDATE VOLUME command has updated the volume indicated. System Action: None. User Response: None. ANR2208I Volume volume name deleted from storage pool storage pool name.
Explanation: A DELETE STGPOOL command has deleted the storage pool indicated. System Action: None. User Response: None. ANR2202I Storage pool storage pool name updated.
Explanation: An UPDATE STGPOOL command has updated the storage pool indicated. System Action: None. User Response: None. ANR2203I Device class device class name defined.
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. v The volume was an empty scratch WORM FILE volume and deleted by RECLAMATION since the retention of the volume has expired. System Action: None. User Response: None. ANR2209W Volume volume name contains no data.
Explanation: A DEFINE DEVCLASS command has created the device class indicated. System Action: None. User Response: None. ANR2204I Device class device class name deleted.
Explanation: The AUDIT VOLUME or MOVE DATA command entered specifies a volume that contains no data. System Action: The server does not process the command. User Response: None. ANR2210I Vary online initiated for disk volume volume name.
Explanation: A DELETE DEVCLASS command has deleted the device class indicated. System Action: None. User Response: None. ANR2205I Device class device class name updated.
Explanation: An UPDATE DEVCLASS command has updated the device class indicated. System Action: None. User Response: None.
Explanation: A VARY ONLINE command for the volume shown is being processed, and if no errors occur the volume will be varied online. System Action: None. User Response: None. ANR2211I Vary offline initiated for disk volume volume name.
ANR2206I
Volume volume name defined in storage pool storage pool name (device class device class name).
Explanation: A DEFINE VOLUME command has defined the volume indicated in the storage pool shown that belongs to the device class shown. System Action: None. User Response: None.
Explanation: A VARY OFFLINE command for the volume shown is being processed and, if no errors occur, the volume will be varied offline. System Action: None. User Response: None.
Chapter 3. Common and Platform Specfic Messages
201
ANR2212I ANR2222I
ANR2212I Command: No volumes updated. ANR2218E Command: A device class must be specified.
Explanation: An UPDATE VOLUME command has been entered, but no objects were updated. System Action: None. User Response: None. ANR2213I Command: Storage pool storage pool name renamed to storage pool name.
Explanation: The DEVCLASS parameter is not specified in the command command name. A DEVCLASS value must be specified. System Action: The command fails. User Response: Reissue the command specifying a valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server. ANR2219I Discard Data process ended for volume volume name - volume is not deleted from storage pool storage pool name because the volume access is offsite.
Explanation: A RENAME STGPOOL command has been entered. The rename of the storage pool was successful. System Action: None. User Response: None. ANR2214E Command: Invalid backup set name backup set name.
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. System Action: None. User Response: To delete the volume, change the volume access to readwrite, readonly, or unavailable. ANR2220W This command will delete volume volume name from its storage pool after verifying that the volume contains no data.
Explanation: The command shown specifies an invalid backup set name. System Action: The command fails. User Response: Reissue the command with a valid 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. System Action: The command fails User Response: Reissue the command specifying a shorter description ANR2216E Command: Device class must be a sequential device class.
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: The device class specified on the command is not a sequential device class. System Action: The command fails User Response: Reissue the command specifying the name of a sequential device class ANR2217E Command: Invalid backup set retention period - retention value.
Explanation: A DELETE VOLUME command with the Discarddata=Yes 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. ANR2222I Discard Data process started for volume volume name (process ID process ID).
Explanation: Server processing for the backup set command command fails because the value (retention value) specified for the RETENTION parameter is not valid. System Action: The command fails User Response: Reissue the command specifying a valid RETENTION value.
Explanation: As a result of a DELETE VOLUME command with the Discarddata=Yes option, the process
202
IBM Tivoli Storage Manager: Messages
ANR2223I ANR2232W
whose ID is displayed has begun to delete the data on the volume shown. System Action: The server deletes the data on the volume. User Response: None. ANR2223I Discard Data process ended for volume volume name - volume deleted from storage pool storage pool name. ANR2227W Discard data process terminated for volume volume name - sufficient memory is not available.
Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended due to a shortage of memory. System Action: The server does not delete the volume. 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. ANR2228W Discard data process terminated for volume volume name - lock conflict detected.
Explanation: The process that deleted data for the volume shown has ended, and the volume has been deleted. System Action: None. User Response: None. ANR2224W Discard Data process terminated for volume volume name - process canceled.
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. User Response: None. ANR2225W Discard Data process terminated for volume volume name - volume still contains data.
Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended due to a locking conflict. System Action: The server does not delete the volume. User Response: Reissue the command at a later time. If this problem persists, contact your service representative. ANR2229W Discard data process terminated for volume volume name - internal server error detected.
Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended. However, the volume contains data. System Action: The server does not delete the volume. User Response: Contact your service representative. ANR2226W Discard data process terminated for volume volume name - sufficient recovery log space is not available.
Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended due to a server internal error. System Action: The server does not delete the volume User Response: Contact your service representative. ANR2232W This command will move all of the data stored on volume volume name to other volumes within the same storage pool; the data will be inaccessible to users until the operation completes.
Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended due to a shortage of recovery log space. System Action: The server does not delete the volume. User Response: An authorized administrator can issue 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.
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. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to continue with the command or 'N' to end the process.
Chapter 3. Common and Platform Specfic Messages
203
ANR2233W ANR2239W
ANR2233W 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. ANR2236W This command has removed administrator adminName. This administrator has defined or updated schedules. This WILL cause these schedules to fail in the future.
Explanation: A move data has been entered that will move data from the indicated volume to volumes in the storage pool shown. While the data is being moved it will not be available to users. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to continue with the command or 'N' to end the process. 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.
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 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. ANR2237W This command has revoked privileges for administrator adminName. This administrator has defined or updated schedules. This may cause these schedules to fail in the future.
Explanation: A HALT command has been entered. System Action: The administrator is asked whether to 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 REVOKE AUTHORITY command has been entered. System Action: The system removes the authority. User Response: None. 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 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. System Action: The system asks whether you wish to continue with the command. 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.
Explanation: A DELETE FILESPACE command has been entered. System Action: The system asks whether you wish to continue with the command. User Response: To process the DELETE FILESPACE command, enter 'Y'; otherwise, enter 'N'. ANR2239W This command will revoke privileges for administrator adminName. This administrator has defined or updated schedules. Revoking this authority may cause schedules to fail.
Explanation: A REVOKE AUTHORITY command has been entered. System Action: The system asks whether you wish to continue with the command.
204
IBM Tivoli Storage Manager: Messages
ANR2240I ANR2251I
User Response: To process the REVOKE AUTHORITY command, enter 'Y' to continue or 'N' to stop the process. ANR2240I Database volume volume name defined. User Response: None. ANR2246I Vary online process initiated for database volume volume name (process ID process ID).
Explanation: A DEFINE DBVOLUME command has defined the database volume indicated. System Action: None. User Response: None. ANR2241I Database volume copy volume name defined.
Explanation: In response to a VARY ONLINE command, the process with the process ID shown has been started to vary on the database volume indicated. System Action: None. User Response: None. ANR2247I Database volume volume name varied offline.
Explanation: A DEFINE DBCOPY command has defined the database volume indicated. System Action: None. User Response: None. ANR2242I Database volume copy volume name defined; synchronization process started (process ID process ID).
Explanation: A VARY OFFLINE command has put the indicated database volume into an offline state. System Action: None. User Response: None. ANR2248I Database assigned capacity has been extended.
Explanation: A DEFINE DBCOPY command has 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. System Action: None. User Response: None. ANR2243I Database volume volume name deleted.
Explanation: An EXTEND DB command has increased the storage capacity of the database. System Action: None. User Response: None. ANR2249I Database extension process initiated (process ID process ID).
Explanation: A DELETE DBVOLUME command has deleted the database volume indicated. System Action: None. User Response: None.
Explanation: In response to an EXTEND DB command, the process with the process ID shown has been started to extend the database. System Action: None. User Response: None. ANR2250I Database assigned capacity has been reduced.
ANR2244I
Delete process initiated for database volume volume name (process id process ID).
Explanation: A REDUCE DB command has decreased the storage capacity of the database. System Action: None. User Response: None. ANR2251I Database reduction process initiated (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. System Action: None. User Response: None. ANR2245I Database volume volume name varied online.
Explanation: In response to a REDUCE DB command, the process with the process ID shown has been started to reduce the database. System Action: None. User Response: None.
Explanation: A VARY ONLINE command has put the database volume indicated into an online state. System Action: None.
Chapter 3. Common and Platform Specfic Messages
205
ANR2252W ANR2260I
ANR2252W Database volume copy volume name is larger than volume volume name by count megabyte(s). User Response: Reissue the command and specify a valid RETENTION parameter. ANR2257E Command: Administrator administrator name is not authorized to issue this command for node node name.
Explanation: A DEFINE DBCOPY command has 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. User Response: None. 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: The specified administrator has entered the indicated command, but this administrator does not have the proper authority necessary to run the command for the indicated node. Note: This message can be issued as a result of the server option REQSYSAUTHOUTFILE YES being in effect. System Action: The server does not process the command for the indicated node. If multiple nodes were specified on the command, the server may continue processing the command for the other nodes. User Response: Examine previous messages for any additional information. Issue the command from a properly authorized administrator ID, or contact the system administrator to have additional authority granted to the current administrator ID. ANR2258E Command: Invalid summary retention period - retention value.
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. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to define the copy, 'N' otherwise. ANR2254E Command: The VOLUMENAMES parameter must be specified when SCRATCH=NO is specified.
Explanation: A SET SUMMARYRETENTION command has been entered that specifies an invalid retention period. System Action: The server does not process the command. User Response: Reissue the command with a valid retention period. ANR2259I Summary retention period set to number of days days.
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. System Action: The command fails. User Response: Reissue the command and specify a valid VOLUMENAMES parameter. ANR2255E Command: The VOLUMENAMES parameter must be specified.
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. System Action: None. User Response: None. ANR2260I Recovery log volume volume name defined.
Explanation: The VOLUMENAMES parameter must be specified to indicate the volumes that can be used for the command. System Action: The command fails. User Response: Reissue the command and specify a valid VOLUMENAMES parameter. ANR2256E Command: The RETENTION parameter must be specified.
Explanation: A DEFINE LOGVOLUME command has defined the recovery log volume indicated. System Action: None. User Response: None.
Explanation: The RETENTION parameter must be specified to indicate the retention period to be used for the command. System Action: The command fails.
206
IBM Tivoli Storage Manager: Messages
ANR2261I ANR2272W
ANR2261I Recovery log volume copy volume name defined. ANR2267I Recovery log volume volume name varied offline.
Explanation: A DEFINE LOGCOPY command has defined the recovery log volume indicated. System Action: None. User Response: None. ANR2262I Recovery log volume copy volume name defined; synchronization process started (process ID process ID).
Explanation: A VARY OFFLINE command has put the recovery log volume indicated into an offline state. System Action: None. User Response: None. ANR2268I Recovery log assigned capacity has been extended.
Explanation: A DEFINE LOGCOPY command has 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. System Action: None. User Response: None. ANR2263I Recovery log volume volume name deleted.
Explanation: An EXTEND LOG command has increased the storage capacity of the recovery log. System Action: None. User Response: None. ANR2269I Recovery log extension process initiated (process ID process ID).
Explanation: In response to an EXTEND LOG command, the process with the process ID shown has been started to extend the recovery log. System Action: None. User Response: None. ANR2270I Recovery log assigned capacity has been reduced.
Explanation: A DELETE LOGVOLUME command has removed the recovery log volume indicated. System Action: None. User Response: None. ANR2264I Delete process initiated for recovery log volume volume name (process id process ID).
Explanation: A REDUCE LOG command has decreased the storage capacity of the recovery log. System Action: None. User Response: None. ANR2271I Recovery log reduction process initiated (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. System Action: None. User Response: None. ANR2265I Recovery log volume volume name varied online.
Explanation: In response to a REDUCE LOG command, the process with the process ID shown has been started to reduce the recovery log. System Action: None. User Response: None. ANR2272W Recovery log volume copy volume name is larger than volume volume name by count megabytes.
Explanation: A VARY ONLINE command has put the recovery log volume indicated into an online state. System Action: None. User Response: None. ANR2266I Vary online process initiated for recovery log volume volume name (process ID process ID).
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. System Action: None. User Response: None.
Explanation: A DEFINE LOGCOPY command has 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. User Response: None.
Chapter 3. Common and Platform Specfic Messages
207
ANR2273W ANR2281I
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. User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command with the SPACEexpansion parameter to set a value greater than zero. ANR2278I Database Space trigger deleted.
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. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to define the copy or 'N' to stop the process. ANR2274I Data Base Space trigger defined and enabled.
Explanation: A DELETE SPACETRIGGER command has successfully completed for the database space trigger. Space expansions are no longer triggered automatically for the database. System Action: None. User Response: None. 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. System Action: None. User Response: None.
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. System Action: None. User Response: None. ANR2280I Full database backup started as process process ID.
ANR2275I
Data Base Space trigger defined, but is disabled.
Explanation: A database space trigger has been defined, but because the space expansion percentage is currently set to 0, the space trigger is disabled. System Action: None. 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: A background process was started to backup the contents of the database. The full database backup process was assigned the process ID shown. System Action: The database backup process starts and server operation continues. User Response: The administrator may query the status of the database backup process by using the QUERY PROCESS command, or cancel the process with the CANCEL PROCESS command. ANR2281I Incremental database backup started as process process ID.
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. System Action: None. User Response: None. ANR2277I Database Space trigger updated, but disabled.
Explanation: A background process was started to backup the contents of the database. The incremental database backup process was assigned the process ID shown. System Action: The database backup process starts and server operation continues. User Response: The administrator may query the status of the database backup process by using the QUERY PROCESS command, or cancel the process with the CANCEL PROCESS command.
Explanation: An UPDATE SPACETRIGGER command has successfully completed for the data base space trigger. However, the space expansion percentage is currently set to 0, which disables the space trigger. System Action: None.
208
IBM Tivoli Storage Manager: Messages
ANR2282I ANR2290W
ANR2282I Database backup trigger defined and enabled. User Response: None. ANR2287I Snapshot database backup started as process process ID.
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. System Action: None. User Response: None. ANR2283I Database backup trigger defined, but is disabled.
Explanation: A background process was started to backup the contents of the database. The snapshot database backup process was assigned the process id shown. System Action: The database backup process starts and server operation continues. User Response: The administrator may query the started process by using the QUERY PROCESS command, or may cancel the process using the CANCEL PROCESS command. ANR2288I Subfile set to state.
Explanation: A database backup trigger has been defined, but because the recovery log mode is currently set to NORMAL, the database backup trigger is disabled. Database backups can only be triggered when the log mode is set to ROLLFORWARD with a SET LOGMODE command. System Action: None. User Response: To activate the database backup trigger, use the SET LOGMODE ROLLFORWARD command. ANR2284I Database backup trigger updated and enabled.
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. System Action: None. User Response: None. ANR2289I Administrative userid admininstrator name defined for authority over node node name has not been removed.
Explanation: An UPDATE DBBACKUPTRIGGER command has successfully completed. The updated parameters specified on the command are used to automatically trigger database backups. System Action: None. User Response: None. ANR2285I Database backup trigger updated, but disabled.
Explanation: The specified administrator was not removed. System Action: None. User Response: None. ANR2290W Changing the log mode to NORMAL will prevent roll-forward recovery.
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. System Action: None. User Response: To activate the database backup trigger, use the SET LOGMODE ROLLFORWARD command. ANR2286I Database backup trigger deleted.
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. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to change the LOGMODE, 'N' otherwise.
Explanation: A DELETE DBBACKUPTRIGGER command has successfully completed. Database backups are no longer triggered automatically by recovery log utilization. System Action: None.
Chapter 3. Common and Platform Specfic Messages
209
ANR2291W ANR2299I
ANR2291W Changing the log mode to NORMAL will disable the database backup trigger. User Response: None. ANR2295I Log mode set to ROLLFORWARD; database backup trigger enabled.
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. System Action: The administrator is asked whether to 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: The mode for saving recovery log 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. System Action: None. User Response: None. ANR2296I Log mode set to NORMAL; database backup trigger disabled.
Explanation: Changing the recovery log mode from NORMAL to ROLLFORWARD causes a previously issued DEFINE DBBACKUPTRIGGER command to become effective, and immediately start a full database backup. Database backups can only be triggered when the recovery log mode is set to ROLLFORWARD with a SET LOGMODE command. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to change the log mode, 'N' otherwise. ANR2293I Only point-in-time database recovery is now possible.
Explanation: The mode for saving recovery log records has been set to NORMAL mode, and the defined database backup trigger is disabled. Only those log records needed to resume database processing if a system failure occurs are saved in this mode. Database backups can only be started using the BACKUP DB command. System Action: None. User Response: None. ANR2297I Command: Optionset optionset name, option option name, sequence number old sequence number, has been changed to new sequence number.
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. System Action: None. User Response: None. ANR2294I Log mode set to log mode.
Explanation: The requested option sequence number has been updated in response to an UPDATE CLIENTOPT command. System Action: None. User Response: None. ANR2298I Command: Optionset optionset name, option option name, sequence number old sequence number, is not updated.
Explanation: The mode for saving recovery log records has been set as indicated by the SET 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. System Action: None.
Explanation: The requested option sequence number is not updated in response to an UPDATE CLIENTOPT command. System Action: None. 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
210
IBM Tivoli Storage Manager: Messages
ANR2300E ANR2308W
changed has been set to the value indicated with the SET PASSEXP command. System Action: None. User Response: None. ANR2300E Could not open file spec the server help file. User Response: Contact the system administrator. 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. System Action: The server does not process the HELP 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 named help file could not be accessed. System Action: The requested help text is not displayed. User Response: Contact the system administrator. ANR2301E Errors were encountered while setting up the index to the help text.
Explanation: Either insufficient memory or a help file read failure has occurred during setup of the help index. System Action: The server does not display the requested help text. User Response: Contact the system administrator.
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. System Action: The server does not process the HELP command. User Response: Contact the system administrator. ANR2307E No help text could be found for this message: message ID.
ANR2302E
The argument operand is not valid for the HELP command.
Explanation: The argument supplied on the HELP command is not an integer or the name of a command. System Action: The server does not process the HELP command. User Response: Issue the HELP command with no operands and select from the numbered list displayed in response. ANR2303E There is no help section numbered section number.
Explanation: The 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. User Response: Contact the system administrator. ANR2308W Audit Volume marking damaged file as damaged on volume volume name: Node node name, Type file type, File space filespace name, fsId filespace id, File Name file name is number version of total versions versions.
Explanation: The numeric operand supplied on the HELP command is either less than 1 or greater than the highest-numbered entry in the help index. System Action: The server does not process the HELP command. User Response: Issue the HELP command with no operands and select from the numbered list (help index) displayed in response. ANR2304E I/O error reading help file name the file of help text.
Explanation: As the result of an AUDIT VOLUME command that specified FIX=YES for the volume shown, the file whose information is displayed is marked as damaged in the server. The file is marked as damaged because it can be recovered from a copy known to exist in a COPY storage pool. If this file belongs to an aggregate, the entire aggregate is marked damaged, and this message will be issued for every file in the aggregate. The version numbers for the file are numbered from most recent (1) to least recent (n, where n is the total number of versions. System Action: The file is marked as damaged in the server database. User Response: To recover the damaged file use the RESTORE STGPOOL or RESTORE VOLUME command.
Explanation: An error is detected when reading help text from the named file. System Action: The server ends display of the help text.
Chapter 3. Common and Platform Specfic Messages
211
ANR2309E ANR2315I
ANR2309E The server log mode is currently set to roll-forward. You may run out of log space when auditing the server in this mode. Specify LOGMODE=NORMAL to set the log mode to NORMAL for the audit operation, or LOGMODE=ROLLFORWARD to force the audit operation with the logmode set to roll-forward. ANR2312I Audit Volume (Repair) process started for volume volume name (process ID process ID).
Explanation: As the result of an AUDIT VOLUME command that specified FIX=YES for the volume shown, the process whose ID is displayed has begun auditing the volume. System Action: The volume is audited and inconsistent data is discarded. User Response: None. ANR2313I Audit Volume (Inspect Only) process started for volume volume name (process ID process ID).
Explanation: An AUDITDB operation was specified and the server log mode is set to roll-forward mode. When in roll-forward mode, the server may run out of log space during the AUDITDB operation, requiring an emergency extend of the recovery log to re-start the server. The recommended log mode for executing an AUDITDB operation is NORMAL. System Action: The AUDITDB operation fails User Response: To force the server log mode to NORMAL for the AUDITDB operation, specify LOGMODE=NORMAL on the AUDITDB command. Specify LOGMODE=ROLLFORWARD on the AUDITDB command to allow the audit to run with a roll-forward log mode setting. 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: As the result of an AUDIT VOLUME command that specified FIX=NO for the volume shown, the process whose ID is displayed has begun auditing the volume. System Action: The volume is audited and inconsistent data is displayed. User Response: None. 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: During the execution of an AUDIT VOLUME command, any data the volume named would be unavailable to users. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to audit the volume or 'N' to 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: 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. System Action: None. User Response: To recover files that have been marked as damaged on the volume, use the RESTORE STGPOOL or RESTORE volume command. ANR2315I Audit volume process ended for volume volume name; file count files inspected, file count damaged files found and marked as damaged.
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. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to audit the volume or 'N' to stop the process.
Explanation: The AUDIT VOLUME command 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
212
IBM Tivoli Storage Manager: Messages
ANR2316W ANR2323W
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). System Action: None. User Response: If you suspect that files were inaccessible because of hardware problems such as dirty tape heads, correct the hardware problem and reissue the AUDIT VOLUME FIX=NO command for this volume. To remove damaged file references, issue the AUDIT VOLUME command and specify FIX=YES. ANR2316W Audit Volume deleting damaged file on 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. ANR2319W Audit volume process terminated for volume volume name - error reading device.
Explanation: During processing of an AUDIT VOLUME command for the volume shown, an unrecoverable read error occurred on the volume. System Action: The AUDIT VOLUME command is ended. User Response: Attempt to correct the cause of the read error, and reissue the command. ANR2320W Audit volume process terminated for volume volume name - data transfer interrupted.
Explanation: As the result of an AUDIT VOLUME command that specified FIX=YES for the volume 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. User Response: None. ANR2317W Audit Volume found damaged file 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: During processing of an AUDIT VOLUME command for the volume shown, a data transfer operation has been interrupted and cannot be continued. System Action: The AUDIT VOLUME command is ended. User Response: If possible, determine and correct the cause of the interruption, and reissue the command. ANR2321W Audit volume process terminated for volume volume name - storage media inaccessible.
Explanation: During processing of an AUDIT VOLUME command for the volume shown, a required volume cannot be mounted. System Action: The AUDIT VOLUME command is ended. User Response: None. ANR2322W Audit volume process terminated for volume volume name - sufficient recovery log space is not available.
Explanation: As the result of an AUDIT VOLUME command that specified FIX=NO for the volume 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. System Action: None. User Response: None. ANR2318W Audit volume process terminated for volume volume name - process canceled.
Explanation: During processing of an AUDIT VOLUME command for the volume shown, the server does not have sufficient recovery log space to continue. System Action: The AUDIT VOLUME command is ended. User Response: If necessary, make more recovery log space available to the server. ANR2323W Audit volume process terminated for volume volume name - sufficient database space is not available.
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. User Response: None.
Explanation: During processing of an AUDIT VOLUME command for the volume shown, the server does not have sufficient database space to continue.
Chapter 3. Common and Platform Specfic Messages
213
ANR2324W ANR2335W
System Action: The AUDIT VOLUME command is ended. User Response: If necessary, make more database space available to the server. ANR2324W Audit volume process terminated for volume volume name - thread resource not available. ANR2332W Object object.ID deleted by another process during execution of an AUDIT VOLUME command for volume volume name.
Explanation: During processing of an AUDIT VOLUME command for the volume shown, the server cannot start a thread for the audit process. System Action: The AUDIT VOLUME command is ended. User Response: Reissue the AUDIT VOLUME command. If the error persists, it may indicate a shortage of server memory. ANR2325W Audit volume process terminated for volume volume name - sufficient memory is not available.
Explanation: During processing of an AUDIT 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 service representative. ANR2333W Missing or incorrect information detected by AUDIT VOLUME for volume volume name.
Explanation: During processing of an AUDIT VOLUME command for the volume shown, the server does not have enough memory available to complete the command. System Action: The AUDIT VOLUME command is ended. User Response: If necessary make more memory available to the server. ANR2326W Audit volume process terminated for volume volume name - lock conflict detected.
Explanation: An AUDIT VOLUME command detects missing or incorrect information for the specified volume. System Action: Audit processing continues. 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: During processing of an AUDIT VOLUME command for the volume shown, the server cannot obtain a required lock. System Action: The AUDIT VOLUME command is ended. User Response: Reissue the command. ANR2327W Audit volume process terminated for volume volume name - internal server error detected.
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. System Action: Audit processing continues. User Response: None. 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: During processing of an AUDIT VOLUME command for the volume shown, an internal server error occurs. System Action: The AUDIT VOLUME command is ended. User Response: Contact your service representative.
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.
214
IBM Tivoli Storage Manager: Messages
ANR2336W ANR2346E
System Action: None. 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 mount points available for removable media. ANR2342E Command: Storage pool description exceeds maximum characters characters.
Explanation: The command indicated contains a storage pool description that exceeds the maximum length allowed. System Action: The server does not process the command. User Response: Reissue the command with a valid storage pool description. ANR2343E Command: Invalid device class name device class name.
Explanation: During Audit Volume for the indicated volume, the server could not allocate sufficient mount points for the volume required. System Action: Audit Volume stops. User Response: If necessary, make more mount points available. ANR2339E Command: Object sets still exist for node node name.
Explanation: The command indicated contains an invalid device class name. System Action: The server does not process the command. User Response: Reissue the command with a valid device class name. ANR2344E Command: The option option is not valid for device class device class 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. System Action: The server does not process the 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 specifies an option shown that is not valid for a storage pool that belongs to the device class shown. System Action: The server does not process the command. User Response: Reissue the command with options appropriate to the device class. ANR2345E Command: Invalid volume name - volume name.
Explanation: The command indicated contains an invalid storage pool name. System Action: The server does not process the command. User Response: Reissue the command with a valid storage pool name. ANR2341E Command: Missing next storage pool name.
Explanation: The command indicated contains an invalid volume name. System Action: The server does not process the command. User Response: Reissue the command with a valid volume name. ANR2346E Command: Volume name volume name is not valid for device class device class name.
Explanation: The command indicated requires a storage pool name, but none has been entered. System Action: The server does not process the command. User Response: Reissue the command with a storage pool name.
Explanation: The command indicated specifies the name of a volume that cannot be used with the device class shown. System Action: The server does not process the command. User Response: Reissue the command with a valid volume name.
Chapter 3. Common and Platform Specfic Messages
215
ANR2347E ANR2356E
ANR2347E Command: Volume name volume name is ambiguous; resolves to multiple defined volume names. ANR2352E Command: Device class device class name may not be deleted.
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. System Action: The command is not executed. User Response: Reissue the command with a more specific volume name. ANR2348E Command: The option option is not valid for a volume assigned to a primary storage pool.
Explanation: A DELETE DEVCLASS command specifies the class name DISK, which is a system-defined device class and may not be deleted. System Action: The server does not process the command. User Response: None. ANR2353E Command: Device class device class name may not be updated.
Explanation: An UPDATE DEVCLASS command specifies the class name DISK, which is a system-defined device class and may not be changed. System Action: The server does not process the command. User Response: None. ANR2354E Command: Device class device class name is still referenced by one or more storage pools, or database backup or export volumes.
Explanation: The command indicated specifies an option that is not valid for a volume in a primary storage pool. System Action: The server does not process the command. User Response: Reissue the command with valid options for a volume in a primary storage pool. ANR2349E Command: The option option is not valid for a volume assigned to a copy storage pool.
Explanation: The command indicated specifies an option that is not valid for a volume in a copy storage pool. System Action: The server does not process the command. User Response: Reissue the command with valid options for a volume in a copy storage pool. ANR2350E Command: Device class device class name is already defined.
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 or export volumes. System Action: The server does not process the 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 references. ANR2355E Command: Required parameter is missing - missing parameter.
Explanation: The command indicated has attempted to define a device class that already exists. System Action: The server does not process the command. User Response: None. ANR2351E Command: Device class device class name is not defined.
Explanation: The specified server command has been entered without the required parameter. The required parameter is shown. System Action: The server ignores the command. User Response: Reissue the command and enter the proper syntax. ANR2356E Command: Incompatible parameters specified - first parameter, second parameter.
Explanation: The command indicated references a device class that does not exist. System Action: The server does not process the command. User Response: None.
Explanation: The specified server command has been entered with mutually exclusive parameters. The two parameters are listed. System Action: The server ignores the command.
216
IBM Tivoli Storage Manager: Messages
ANR2357E ANR2365I
User Response: Reissue the command and enter the proper syntax. ANR2357E Command: The DISK device class is not supported for copy storage pools. ANR2361E Command: A full database backup is required.
Explanation: A BACKUP DB command specified an incremental backup, but a full backup is required. System Action: The server does not process the 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: 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. System Action: The server does not process the command. User Response: Reissue the command specifying a sequential device class. ANR2358E Command: Device class device class name is still referenced in the volume history file.
Explanation: The DELETE DEVCLASS command has attempted to delete a device class that is associate with entries in the volume history file. These entries are for volumes that contain database backup or export data. System Action: The server does not process the command. User Response: Use the DELETE VOLHIST command to remove that entries before deleting the device class. ANR2359E Command: Volume name volume name must be specified with a DISK or FILE STGPOOL.
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. System Action: The server does not process the command. User Response: Reissue the command at a later time. ANR2363E Command: One of the following parameter must be supplied but is missing - missing parameter, missing parameter, missing parameter, missing parameter.
Explanation: The command indicated specifies the name of a volume that must be specified with a storage pool associated with a device class of type DISK or FILE. System Action: The server does not process the command. User Response: Reissue the command with a valid volume name and storage pool. ANR2360E Command: Device class device class name may not be used for database backup.
Explanation: The specified server command has been entered without one of the mutually exclusive required parameters. One of the parameters from the list must be specified. System Action: The server ignores the command. User Response: Reissue the command and enter the proper syntax. ANR2364E Command: Missing reclaim-storage pool name.
Explanation: The command specifies the DISK device class, which cannot be used for database backup, backup trigger, or restore operations. System Action: The server does not process the command. User Response: Reissue the command with a valid device class.
Explanation: The command indicated requires a storage pool name, but none has been entered. System Action: The server does not process the command. User Response: Reissue the command with a storage pool name. ANR2365I Backupset backup set name for node node name has been deleted.
Explanation: The backup set has been deleted. System Action: The server has deleted the backupset.
Chapter 3. Common and Platform Specfic Messages
217
ANR2366I ANR2374E
User Response: None. ANR2366I Backupset backup set name for node node name would have been deleted. ANR2370E Command: Database backup trigger is already defined.
Explanation: The database backup trigger cannot be defined because it is already defined. System Action: The server does not process the command. User Response: Use the UPDATE DBBACKUPTRIGGER command to modify the database backup trigger parameters. ANR2371E Command: Database backup trigger is not defined.
Explanation: The backup set would have been deleted as the result of a DELETE BACKUPSET command, but the PREVIEW=YES parameter was specified. System Action: None. User Response: If the backup set is to be deleted, reissue the command without specifying PREVIEW=YES. ANR2367I Retention period for backupset backup set name for node node name has been updated.
Explanation: The database backup trigger cannot be updated or deleted because it is not currently defined. System Action: The server does not process the command. User Response: None. ANR2372E Command: Database Space trigger is already defined.
Explanation: The backup sets retention period has been updated. System Action: The server has updated the backupsets retention period. User Response: None. ANR2368I Retention period for backupset backup set name for node node name would have been updated.
Explanation: The database space trigger cannot be defined because it is already defined. System Action: The server does not process the command. User Response: Use the UPDATE SPACETRIGGER command to modify the indicated space trigger parameters. ANR2373E Command: Database backup trigger is not defined.
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. System Action: None. User Response: If the backup set is to be updated, reissue the command without specifying PREVIEW=YES. ANR2369I Database backup volume and recovery plan file expiration starting under process process ID.
Explanation: The database space trigger cannot be updated or deleted because it is not currently defined. System Action: The server does not process the command. User Response: None. ANR2374E Command: Recovery Log Space trigger is already defined.
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. System Action: Server operation continues. The expiration process is cancellable. User Response: None.
Explanation: The recovery log space trigger cannot be defined because it is already defined. System Action: The server does not process the command. User Response: Use the UPDATE SPACETRIGGER command to modify the indicated space trigger parameters.
218
IBM Tivoli Storage Manager: Messages
ANR2375E ANR2384E
ANR2375E Command: Recovery Log trigger is not defined. ANR2380E Command: Storage pool storage pool name is not defined.
Explanation: The recovery log space trigger cannot be updated or deleted because it is not currently defined. System Action: The server does not process the command. User Response: None. ANR2376I Recovery Log Space trigger defined, but is disabled.
Explanation: The command indicated specifies the name of a nonexistent storage pool. System Action: The server does not process the command. User Response: Reissue the command with a valid storage pool name. ANR2381E Command: Storage pool storage pool name is already defined.
Explanation: A recovery log space trigger has been defined, but because the space expansion percentage is currently set to 0, the space trigger is disabled. System Action: None. User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command to set the space expansion percentage to a value greater than 0. ANR2377I Recovery Log Space trigger updated and enabled.
Explanation: A DEFINE STGPOOL command specifies the name of a storage pool that already exists. System Action: The server does not process the command. User Response: None. ANR2382E Command: Storage pool storage pool name still contains at least one volume.
Explanation: An UPDATE SPACETRIGGER command has successfully completed for the recovery log space trigger. The updated parameters specified on the command are used to automatically trigger space expansion for the database. System Action: None. User Response: None. ANR2378I Recovery Log Space trigger updated, but disabled.
Explanation: A DELETE STGPOOL command specifies a storage pool that has volumes assigned to it. System Action: The server does not process the command. User Response: Delete the volume belonging to the storage pool and reissue the command. ANR2383E Command: Storage pool storage pool name is currently in use by clients and/or data management operations.
Explanation: An UPDATE SPACETRIGGER command has successfully completed for the recovery log space trigger. However, the space expansion percentage is currently set to 0, which disables the space trigger. System Action: None. User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command with the SPACEexpansion parameter to set a value greater than zero. ANR2379I Recovery Log Space trigger deleted.
Explanation: The command indicated references a storage pool that is in use. System Action: The server does not process the command. User Response: Reissue the command at a later time. 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. System Action: The server does not process the command. User Response: Reissue the command with a different next pool value.
Explanation: A DELETE SPACETRIGGER command has successfully completed for the recovery log space trigger. Space expansions are no longer triggered automatically for the recovery log. System Action: None. User Response: None.
Chapter 3. Common and Platform Specfic Messages
219
ANR2385E ANR2392E
ANR2385E Command: Storage pool storage pool name is in use as the next or reclaim pool for one or more other storage pools. ANR2389E Command: The option option is not valid for a primary storage pool.
Explanation: A DELETE STGPOOL command specifies a pool that is the next pool or the reclaim pool for other storage pools. System Action: The server does not process the command. User Response: If necessary, update other storage pools so that they do not reference the pool to be deleted, and reissue the command. ANR2386E Command: High migration threshold must be set greater than or equal to the low migration threshold.
Explanation: The command indicated specifies an option that is not valid for a primary storage pool. System Action: The server does not process the command. User Response: Reissue the command with options appropriate for a primary storage pool. ANR2390E Command: The option option is not valid for a copy storage pool.
Explanation: The command indicated specifies an option that is not valid for a copy storage pool. System Action: The server does not process the command. User Response: Reissue the command with options appropriate for a copy storage pool. ANR2391E Command: Server could not write device configuration information to file name.
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). System Action: The server does not process the command. User Response: Reissue the command with a low migration threshold less than or equal to the high migration threshold. ANR2387E Command: Storage pool storage pool name is not a primary pool.
Explanation: The BACKUP DEVCONFIG command does not successfully complete because the server cannot write to the file name specified. System Action: The server does not process the command. User Response: Make sure that the server has proper authority to write to the file indicated and that sufficient space is available in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. ANR2392E Command: An internal error was encountered in writing device configuration information to file name.
Explanation: The command indicated specifies the name of a storage pool which is not a primary pool. The command syntax requires that a primary storage pool name be specified. System Action: The server does not process the command. User Response: Reissue the command with a valid primary storage pool name. ANR2388E Command: Storage pool storage pool name is not a copy pool.
Explanation: The BACKUP DEVCONFIG command does not successfully complete because the server cannot write to the file name specified. System Action: The server does not process the 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.
Explanation: The command indicated specifies the name of a storage pool which is not a copy pool. The command syntax requires that a copy storage pool name be specified. System Action: The server does not process the command. User Response: Reissue the command with a valid copy storage pool name.
220
IBM Tivoli Storage Manager: Messages
ANR2393I ANR2399E
ANR2393I Command: Server device configuration information was written to file name. 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. ANR2397E Command: An internal server error was encountered in writing device configuration information to one or more of the defined device configuration files.
Explanation: This message is displayed in response to 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 User Response: None. ANR2394I Command: Server device configuration information was written to all device configuration files.
Explanation: This message is displayed in response to the BACKUP DEVCONFIG command and indicates 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. User Response: None.
Explanation: The BACKUP DEVCONFIG command does not complete successfully because the server cannot write to one or more of the defined device configuration files. System Action: The server does not process the 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. Contact your service representative if you are unable to resolve the problem. ANR2398E Command: The device configuration file contains a statement with invalid syntax.
ANR2395I
Command: Device configuration files have NOT been defined for automatic recording - specify a file name for device configuration information.
Explanation: This message is displayed in response to the BACKUP DEVCONFIG command and indicates that device configuration information cannot be written because no files were specified in the options file. System Action: The device configuration information is not written. Server operation continues. User Response: Reissue the BACKUP DEVCONFIG command and specify the name of a file to which you would like to have device configuration information recorded. If desired, you may configure files that should be automatically updated with the DEVCONFIG option and restart the server. ANR2396E Command: An I/O error was encountered in writing device configuration information to one or more of the defined device configuration files.
Explanation: While processing the device configuration information, an invalid statement has been encountered. System Action: The server ends the operation being performed. User Response: Examine error messages on the server console that may have been displayed prior to this message and correct any problems if you have constructed the device configuration file manually. Make sure the statements are in the proper order. If you let the server construct the device configuration file automatically, restart the server, refresh the device configuration file by issuing the BACKUP DEVCONFIG command, and reissue the operation. If the problem persists, contact your service representative. ANR2399E Command: Storage pool storage pool name is not a sequential pool.
Explanation: The BACKUP DEVCONFIG command does not complete successfully because the server cannot write to one or more of the defined device configuration files. System Action: The server does not process the command. User Response: Examine error messages on the server console that may have been displayed prior to this
Explanation: The command indicated specifies the 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. System Action: The server does not process the command. User Response: Reissue the command with a valid sequential storage pool name.
Chapter 3. Common and Platform Specfic Messages
221
ANR2400E ANR2409E
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. System Action: The server does not process the command. User Response: Check the spelling of the volume name to ensure it is correct. If the volume does not exist, preallocate it with the appropriate mechanism for the operating system on which the server is running. ANR2405E Command: Volume volume name is currently in use by clients and/or data management operations.
Explanation: The command indicated specifies the 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. System Action: The server does not process the command. User Response: Specify a volume that is not in use, is not defined in a storage pool, and which has not been previously used for an export, a database dump, or database backup operation as recorded in the server volume history information. Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export, a database dump, or database backup operations. ANR2401E Command: Volume volume name is not defined in a storage pool.
Explanation: The command indicated specifies the name of a data storage volume that is currently in use. System Action: The server does not process the command. User Response: None. ANR2406E Command: Volume volume name still contains data.
Explanation: The indicated command tries to delete a data storage volume that contains data. System Action: The server does not process the command. User Response: None. ANR2407E Command: Maximum number of mirrored copies exceeded.
Explanation: The command indicated specifies the name of a storage pool volume that does not exist. System Action: The server does not process the command. User Response: None. ANR2402E Command: Volume volume name is already online.
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. System Action: The server does not process the command. User Response: None. ANR2408E Command: Capacity of volume volume name must be at least as large as capacity of volume volume name.
Explanation: A VARY ONLINE command specifies the name of a volume that is already online. System Action: The server does not process the command. User Response: None. ANR2403E Command: Volume volume name is not online.
Explanation: The command indicated specifies the name of a volume that is not online. System Action: The server does not process the command. User Response: None. ANR2404E Command: Volume volume name is not available.
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. System Action: The server does not process the command. User Response: Use a larger mirror volume. ANR2409E Command: Capacity of volume volume name must be at least 5 megabytes.
Explanation: The command indicated has attempted to access a volume that cannot be found.
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
222
IBM Tivoli Storage Manager: Messages
ANR2410E ANR2417E
volume. The minimum size for one of these volumes is 5 megabytes. System Action: The server does not process the command. User Response: Reissue the command and specify a volume that is at least 5 megabytes in size. ANR2410E Command: Unable to access volume volume name - access mode is set to unavailable. User Response: Reissue the command after the audit volume operation ends. ANR2414E Command: Deletion operation already in progress for volume volume name.
Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by a delete volume operation. System Action: The server does not process the command. User Response: Reissue the command after the delete volume operation ends. ANR2415E Command: Deletion operation already in progress for associated volume volume name.
Explanation: The command shown specifies the volume whose name is displayed, but the volume cannot be accessed because its status is unavailable. System Action: The server does not process the command. User Response: If necessary, reset the status of the volume and reissue the command. ANR2411E Command: Unable to access associated volume volume name - access mode is set to unavailable.
Explanation: The command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because it is in use by a delete volume operation. System Action: The server does not process the command. User Response: Reissue the command after the delete volume operation ends. ANR2416E Command: Move Data operation already in progress for volume volume name.
Explanation: The command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because its status is unavailable. System Action: The server does not process the command. User Response: If necessary, reset the status of the volume and reissue the command. ANR2412E Command: Audit operation already in progress for volume volume name.
Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by a move data operation. System Action: The server does not process the command. User Response: Reissue the command after the move data process ends. ANR2417E Command: Move Data operation already in progress for associated volume volume name.
Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by an audit volume operation. System Action: The server does not process the command. User Response: Reissue the command after the audit volume operation ends. ANR2413E Command: Audit operation already in progress for associated volume volume name.
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 a move data operation. System Action: The server does not process the command. User Response: Reissue the command after the move data operation ends.
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. System Action: The server does not process the command.
Chapter 3. Common and Platform Specfic Messages
223
ANR2418E ANR2426I
ANR2418E Command: Migration operation already in progress for volume volume name. ANR2422E Command: Volume volume name is not a defined disk volume.
Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by a migration operation. System Action: The server does not process the command. User Response: Reissue the command after the migration ends. ANR2419E Command: Migration operation already in progress for associated volume volume name.
Explanation: The command shown specifies a volume name that does not match any known disk volume. System Action: The server does not process the command. User Response: Reissue the command with the correct volume name. ANR2423E Command: Volume volume name is still online.
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 a migration operation. System Action: The server does not process the command. User Response: Reissue the command after the migration ends. ANR2420E Command: Space reclamation operation already in progress for volume volume name.
Explanation: An UPDATE VOLUME command specifies access=unavailable for a disk volume that is still online. System Action: The server does not process the command. User Response: Issue the VARY OFFLINE command, and reissue the UPDATE VOLUME command. ANR2424E Command: Unable to access volume volume name - access mode is set to destroyed.
Explanation: The command shown specifies the volume whose name is displayed, but the volume cannot be accessed because its status is destroyed. System Action: The server does not process the command. User Response: If necessary, reset the status of the volume and reissue the command. ANR2425E Command: Unable to access volume volume name - access mode is set to offsite.
Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by a reclamation operation. System Action: The server does not process the command. User Response: Reissue the command after the reclamation ends. ANR2421E Command: Space reclamation operation already in progress for associated volume volume name.
Explanation: The command shown specifies the volume whose name is displayed, but the volume cannot be accessed because its status is offsite. System Action: The server does not process the command. User Response: If necessary, reset the status of the volume and reissue the command. ANR2426I Backupset backup set name defined for node node name.
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 a reclamation operation. System Action: The server does not process the command. User Response: Reissue the command after the reclamation ends.
Explanation: The backup set has been defined for the indicated node. System Action: The server has defined the backupset. User Response: None.
224
IBM Tivoli Storage Manager: Messages
ANR2427E ANR2436E
ANR2427E Backupset backup set name for node node name was not deleted. Device class device class name was not found. ANR2432E Command: Maximum number of database volumes exceeded.
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 Backupset backup set name for node node name has not been deleted due to error error code.
Explanation: A DEFINE DBVOLUME command has attempted to add more database volumes than the server can manage. System Action: The server does not process the command. User Response: None. ANR2433E Command: A database define, delete, extend, reduce, or backup operation is already in progress.
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: The specified command has been entered while a command that is modifying or backing up the database is already active. System Action: The server does not process the command. User Response: Wait for other activity to end, and reissue the command. ANR2434E Command: Insufficient space on other database volumes to delete volume volume name.
Explanation: Do not allocate any volume that would cause the database to exceed 500GB. A subsequent DEFINE DBVOLUME command for that volume would fail. System Action: The server does not process the command. User Response: None. ANR2430E Command: Volume volume name is already defined as a database volume.
Explanation: A DELETE DBVOLUME command has been entered, but the data on the volume to be deleted cannot be copied to other volumes due to insufficient free space. System Action: The server does not process the command. User Response: Make more database space available, and reissue the command. ANR2435E Command: Unable to delete database volume volume name - mirrored copies not synchronized.
Explanation: A DEFINE DBVOLUME command specifies the name of a database volume that already exists. System Action: The server does not process the command. User Response: None. ANR2431E Command: Volume volume name is not a defined database volume.
Explanation: A DELETE DBVOLUME command has been entered, but mirrors of the volume to be deleted are not up to date. System Action: The server does not process the command. User Response: Try the command at a later time (after database volumes have been synchronized). ANR2436E Command: Insufficient space to extend database by requested amount.
Explanation: A DELETE DBVOLUME command specifies the name of a database volume that does not exist. System Action: The server does not process the command. User Response: None.
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. System Action: The server does not process the command.
Chapter 3. Common and Platform Specfic Messages
225
ANR2437E ANR2446E
User Response: Make more database space available, and reissue the command. ANR2437E Command: Output error encountered while attempting to extend database. User Response: None. ANR2442E Command: Volume volume name is not a defined recovery log volume.
Explanation: An EXTEND DB command has been entered, but an I/O error occurs during the command. System Action: The server does not process the command. User Response: Reissue the command. If the problem persists, identify and remove or repair the volume that caused the error. ANR2438E Command: Insufficient database space would be available following a reduction by the requested amount.
Explanation: A DELETE LOGVOLUME command specifies the name of a recovery log volume that does not exist. System Action: The server does not process the command. User Response: None. ANR2443E Command: Maximum number of recovery log volumes exceeded.
Explanation: A DEFINE LOGVOLUME command attempts to add more recovery log volumes than the server can manage. System Action: The server does not process the command. User Response: None. ANR2444E Command: A recovery log define, delete, extend, or reduce operation is already in progress.
Explanation: A REDUCE DB command has been entered, but the database does not have enough free space to reduce by the amount specified. System Action: The server does not process the command. User Response: None. ANR2439E Command: Unable to vary database volume volume name offline - mirrored copies not synchronized.
Explanation: The specified command has been entered while a command that is modifying the recovery log is already active. System Action: The server does not process the command. User Response: Wait for other activity to end, and reissue the command. ANR2445E Command: Insufficient space on other recovery log volumes to delete volume volume name.
Explanation: A VARY OFFLINE command has been entered, but mirrors of the volume to be varied are not up to date. System Action: The server does not process the 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.
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. System Action: The server does not process the command. User Response: None.
Explanation: A DELETE LOGVOLUME command has been entered, but the data on the volume to be deleted cannot be copied to other volumes due to insufficient free space. System Action: The server does not process the command. User Response: Make more recovery log space available, and reissue the command. ANR2446E Command: Unable to delete recovery log volume volume name - mirrored copies not synchronized.
ANR2441E
Command: Volume volume name is already defined as a recovery log volume.
Explanation: A DEFINE LOGVOLUME command specifies the name of a recovery log volume that already exists. System Action: The server does not process the command.
Explanation: A DELETE LOGVOLUME command has been entered, but mirrors of the volume to be deleted are not up to date. System Action: The server does not process the command.
226
IBM Tivoli Storage Manager: Messages
ANR2447E ANR2455E
User Response: Try the command at a later time (after recovery log volumes have been synchronized). ANR2447E Command: Insufficient space to extend recovery log by requested amount. System Action: The server does not process the command. User Response: None. ANR2452E Command: Maximum recovery log capacity exceeded.
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. System Action: The server does not process the command. User Response: Make more recovery log space available, and reissue the command. ANR2448E Command: Output error encountered while attempting to extend recovery log.
Explanation: Do not allocate any volume that would cause the recovery log to exceed 13GB. A subsequent DEFINE LOGVOLUME command for that volume would fail. System Action: The server does not process the command. User Response: None. ANR2453E Command: Unable to reduce recovery log - log mode must be set to NORMAL.
Explanation: An EXTEND LOG command has been entered, but an I/O error occurs during the command. System Action: The server does not process the command. User Response: Reissue the command. If the problem persists, identify and remove or repair the volume that caused the error. ANR2449E Command: Insufficient recovery log space would be available following a reduction by the requested amount.
Explanation: A REDUCE LOG command has been entered, but the recovery log 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. System Action: The server does not process the command. User Response: Set the log mode to NORMAL with the SET LOGMODE command, reissue the REDUCE LOG command, and set the log mode back to ROLLFORWARD with the SET LOGMODE command. If you change the log mode to NORMAL, you can only recover your database to the time of the last complete database backup. ANR2454E Command: Unable to reduce database LOGMODE must be set to NORMAL.
Explanation: A REDUCE LOG command has been entered, but the recovery log does not have enough free space to reduce by the amount specified. System Action: The server does not process the command. User Response: None. ANR2450E Command: Unable to vary recovery log volume volume name offline - mirrored copies not synchronized.
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. System Action: The server does not process the 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 Command: Unable to access associated volume volume name - access mode is set to destroyed.
Explanation: A DELETE LOGVOLUME command has been entered, but mirrors of the volume to be deleted are not up to date. System Action: The server does not process the command. User Response: Try the command at a later time (after recovery log volumes have been synchronized). ANR2451E Command: Unable to vary recovery log volume volume name offline - only copy.
Explanation: A VARY OFFLINE command has been entered, but the recovery log volume has no mirrors and contains the only copy of the data on that volume.
Explanation: The specified command would require access to the volume whose name is displayed (because
Chapter 3. Common and Platform Specfic Messages
227
ANR2456E ANR2462I
data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because its status is destroyed. System Action: The server does not process the command. User Response: If necessary, reset the status of the volume and reissue the command. ANR2456E Command: Unable to access associated volume volume name - access mode is set to offsite. progress to restore the contents of the indicated volume. System Action: The server does not process the 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 command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because its status is offsite. System Action: The server does not process the command. User Response: If necessary, reset the status of the volume and reissue the command. ANR2457E Command: Backup of primary storage pool primary pool name to copy storage pool copy pool name already in progress.
Explanation: The BACKUP VOLHISTORY command does not complete successfully because the server cannot write to the file name specified. System Action: The server does not process the command. User Response: Make sure that the server has proper authority to write to the file indicated and that sufficient space is available in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. ANR2461E Command: An internal error was encountered in writing sequential volume history information to file name.
Explanation: The command shown specifies a backup operation that is already in progress. System Action: The server does not process the 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 BACKUP VOLHISTORY command does not complete successfully because the server cannot write to the file name specified. System Action: The server does not process the 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. ANR2462I Command: Server sequential volume history information was written to file name.
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. System Action: The server does not process the 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: This message is displayed in response to 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. User Response: None.
Explanation: The indicated volume has an access mode of destroyed. Either a RESTORE STGPOOL command or a RESTORE VOLUME command is in
228
IBM Tivoli Storage Manager: Messages
ANR2463I ANR2469E
ANR2463I Command: Server sequential volume history information was written to all configured history files. ANR2466E Command: An internal server error was encountered in writing sequential volume history information to one or more of the defined volume history files.
Explanation: This message is displayed in response to 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. System Action: The server records sequential volume history information to the configured files. User Response: None. ANR2464I Command: Volume history files have NOT been defined for automatic history recording - specify a file name for recording history information.
Explanation: The BACKUP VOLHISTORY command does not complete successfully because the server cannot write to one or more of the defined volume history files. System Action: The server does not process the 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. 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: This message is displayed in response to the BACKUP VOLHISTORY. It indicates that sequential volume history information cannot automatically be written because no files were defined in the server options file for recording this information. System Action: The sequential volume history information is not written. Server operation continues. User Response: Reissue the BACKUP VOLHISTORY command and specify the name of a file for recording sequential volume history information. If desired, you may configure files that should be automatically updated with the VOLUMEHISTORY parameter and restart the server. ANR2465E Command: An I/O error was encountered in writing sequential volume history information to one or more of the defined volume history files.
Explanation: The DELETE VOLHISTORY command successfully deleted the number of entries specified. System Action: Server operation continues. User Response: None. ANR2468E Command: An internal server error was 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 BACKUP VOLHISTORY command does not complete successfully because the server cannot write to one or more of the defined volume history files. System Action: The server does not process the 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.
Explanation: The command failed because an invalid sequential volume history type was specified for the TYPE= parameter. System Action: The command fails, and server operation continues. 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.
Chapter 3. Common and Platform Specfic Messages
229
ANR2470I ANR2478E
ANR2470I Message output being re-directed to file file name. ANR2475E Command: File file name could not be opened.
Explanation: The message output is being redirected to the specified file instead of being displayed at the console. System Action: None. User Response: None. ANR2471E Message output re-direction to file file name failed - unable to open file.
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: An error occurs while trying to open the file. The message output will not be redirected to the specified file. System Action: None. User Response: Determine the cause of the file open failure and take corrective action. ANR2472E Command: Invalid volume specified: volume name.
Explanation: The license storage occupancy function is currently disabled. System Action: None. 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. ANR2477I License storage auditing is disabled, storage values may be outdated and should be ignored.
Explanation: The command failed because the sequential history volume specified is not a DB DUMP, DB BACKUP, or EXPORT volume. System Action: The command fails, and server operation continues. User Response: Reissue the command and specify a valid volume name. ANR2473I Command for volume volume name completed.
Explanation: The license storage occupancy function is currently disabled. System Action: None. 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 completed and the volume history file has been updated. System Action: The server records sequential volume history information. User Response: None. 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. System Action: The command fails. 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.
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. System Action: The server does not process the command. User Response: The command must be issued from a standard administrator session.
230
IBM Tivoli Storage Manager: Messages
ANR2479E ANR2488W
ANR2479E Command: Invalid SQL cursor name SQL cursor name. ANR2484E Command: Invalid SQL date-time display format - SQL date-time display format name.
Explanation: The command indicated contains an invalid SQL cursor name. System Action: The server does not process the command. User Response: Reissue the command with a valid SQL cursor name. ANR2480E Command: SQL cursor name SQL cursor name is already defined.
Explanation: The command indicated contains an invalid SQL date-time display format name. System Action: The server does not process the command. User Response: Reissue the command with a valid SQL date-time format name. ANR2485E Command: Invalid SQL display format SQL display format name.
Explanation: The command indicated specifies an SQL cursor name that has already been defined. System Action: The server does not process the command. User Response: Reissue the command and specify a different cursor name. ANR2481E Command: SQL cursor name SQL cursor name is not defined.
Explanation: The command indicated contains an invalid SQL display format name. System Action: The server does not process the command. User Response: Reissue the command with a valid SQL display format name. ANR2486E Command: Invalid SQL character arithmetic mode - SQL arithmetic mode.
Explanation: The command indicated specifies an SQL cursor name that has not been defined. System Action: The server does not process the command. User Response: Use the DEFINE CURSOR command to first define the cursor. ANR2482E Command: SQL cursor SQL cursor name is already open.
Explanation: The command indicated contains an invalid SQL arithmetic mode name. System Action: The server does not process the command. User Response: Reissue the command with a valid SQL arithmetic mode name. ANR2487E Command: An SQL expression is required.
Explanation: The command indicated failed because an SQL cursor is already open. System Action: The server does not process the command. User Response: Use the CLOSE CURSOR command to first close the current cursor. ANR2483E Command: No SQL cursor is currently open.
Explanation: The command indicated requires that an SQL expression be provided through the SQL keyword parameter. System Action: The server does not process the command. User Response: Reissue the command specifying an SQL expression. ANR2488W List file list file name could not be opened.
Explanation: The command indicated failed because no SQL cursor is currently open. System Action: The server does not process the command. User Response: Use the OPEN CURSOR command to first open a cursor.
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. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. For OUTFILE files, make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On OS/390 and z/OS, make
Chapter 3. Common and Platform Specfic Messages
231
ANR2489W ANR2505I
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. ANR2501I Schedule schedule name deleted from policy domain domain 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. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the 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.
Explanation: This message is displayed in response to the DELETE SCHEDULE command. The schedule named schedule name has been deleted from the policy domain named domain name in the server database. System Action: Server operation continues. User Response: None. ANR2502I Schedule schedule name updated in policy domain domain name.
Explanation: This message is displayed in response to the UPDATE SCHEDULE command. The schedule named schedule name has been updated in the policy domain named domain name in the server database. System Action: Server operation continues. User Response: None. ANR2503I Schedule schedule name in domain domain name copied to schedule new schedule name in domain new domain name.
Explanation: The command indicated failed because both the nodenames parameter and the servernames parameter were specified. System Action: None. User Response: Determine whether you want the action taken for one or more nodes or for one or more servers and reenter the command with only the correct parameter specified. ANR2491I Volume Creation Process starting for volume name, Process Id process ID.
Explanation: This message is displayed in response to 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. System Action: Server operation continues. User Response: None. ANR2504I Schedule schedule name deleted.
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. User Response: None. ANR2500I Schedule schedule name defined in policy domain domain name.
Explanation: This message is displayed in response to the DELETE SCHEDULE command. The schedule named schedule name has been deleted from the server database. System Action: Server operation continues. User Response: None. ANR2505I number of schedules schedules were defined for command.
Explanation: number of schedules were generated and nodes successfully associated for the command issued. System Action: Server operation continues. 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.
Explanation: This message is displayed in response to the DEFINE SCHEDULE command. The schedule named schedule name has been defined in the policy domain named domain name in the server database. System Action: Server operation continues. User Response: None.
232
IBM Tivoli Storage Manager: Messages
ANR2506I ANR2514E
ANR2506I Node node name associated with schedule schedule name in policy domain domain name processed. rc=return code. ANR2510I Node node name associated with schedule schedule name in policy domain domain name.
Explanation: This message is displayed in response to 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. System Action: Server operation continues. 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.
Explanation: This message is displayed in response to 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. System Action: Server operation continues. User Response: None. ANR2511I Node node name disassociated from schedule schedule name in policy domain domain name.
Explanation: This message is displayed in response to the DELETE ASSOCIATION command. Node node name is no longer associated with the schedule named schedule name in policy domain domain name. System Action: Server operation continues. User Response: None. ANR2512I Event records deleted: record count.
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. System Action: Server operation continues. User Response: This message is intended to report the completion state of a scheduled client action. This message indicates that the scheduled action completed successfully. ANR2508E Trace Tsmtrcfm failed: A tracefile name is required.
Explanation: This message is displayed in response to the DELETE EVENT command. A total of record count event records have been deleted from the database. System Action: Server operation continues. User Response: None. ANR2513I Schedule schedule name copied to schedule new schedule name.
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 Command: Invalid Virtual file space name - vfs name.
Explanation: This message is displayed in response to the COPY SCHEDULE command. The schedule named schedule name has been copied to the schedule named new schedule name. System Action: Server operation continues. User Response: None. ANR2514E Command: Virtual file space name vfs name conflicts with file space on the network attached storage (NAS) device.
Explanation: The specified server command has been entered with a virtual file space name that is longer than allowed. System Action: The server does not process the command. User Response: Reissue the command with a valid virtual file space name.
Explanation: The specified server command has been entered with a virtual file space that has the same name as a File space on the NAS device. System Action: The server does not process the 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.
Chapter 3. Common and Platform Specfic Messages
233
ANR2515I ANR2524I
ANR2515I Command: A virtual file space mapping named vfs name for node node name has been defined. User Response: Use QUERY VIRTUALFSMAPPING to verify that the virtual file space mapping is defined correctly. ANR2520I Scheduled sessions set to percent percent.
Explanation: In response to the DEFINE VIRTUALFSMAPPING command, a virtual file space mapping for the specified node has been defined in the server database. System Action: Server operation continues. User Response: None. ANR2516E Command: The specified file space, fs name, does not exist on the NAS device associated with the node node name.
Explanation: This message is displayed in response to the SET MAXSCHEDSESSIONS command. It indicates the percentage of total server sessions that can be used for the processing of scheduled work. System Action: Server operation continues. User Response: None. ANR2521I Event record retention period set to days days.
Explanation: The specified server command has been entered with a file space that does not exist on the associate NAS device. System Action: The server ignores the command. 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.
Explanation: This message is displayed in response to the SET EVENTRETENTION command. It indicates the number of days for which event records are retained in the database. System Action: Server operation continues. User Response: None. ANR2522I Randomization set to percent percent.
Explanation: The specified command has been issued with a virtual file space name that has already been defined for the indicated node. System Action: Server operation continues, but the command is not processed. User Response: Issue the command using a virtual file space name that has not already been defined for this node. ANR2518E Command: A virtual file space mapping already exists to the specified node, file space and path.
Explanation: This message is displayed in response to the SET RANDOMIZE command. It indicates the percentage of the startup window over which the start times for individual clients are distributed. System Action: Server operation continues. User Response: None. ANR2523I Schedule query period set to hours hour(s).
Explanation: The specified command has been issued with a node, file space and path for which there is already a virtual file space mapping defined. System Action: Server operation continues, but the command is not processed. User Response: Issue the command using a file space and path that does not already have a mapping defined. ANR2519E Command: The file space, fs name, does not exist on the NAS device associated with the node node name.
Explanation: This message is displayed in response to the SET QUERYSCHEDPERIOD command. It indicates the number of hours between attempts by the client to contact the server for scheduled commands. System Action: Server operation continues. User Response: None. ANR2524I Schedule query period reset to value determined by each client.
Explanation: This message is displayed in response to the SET QUERYSCHEDPERIOD command. System Action: Server operation continues. User Response: None.
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. System Action: The server ignores the command.
234
IBM Tivoli Storage Manager: Messages
ANR2525I ANR2535E
ANR2525I Maximum number of command retries set to retries. System Action: Server operation continues. User Response: None. ANR2531I Scheduling mode set to ANY.
Explanation: This message is displayed in response to 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. System Action: Server operation continues. User Response: None. ANR2526I Maximum number of command retries reset to value determined by each client.
Explanation: This message is displayed in response to the SET SCHEDMODES command. The server now allows clients to run in either the client-polling or the server-prompted scheduling mode. System Action: Server operation continues. User Response: None. ANR2532I Schedule schedule name updated.
Explanation: This message is displayed in response to the SET MAXCMDRETRIES command. System Action: Server operation continues. User Response: None. ANR2527I Retry period set to minutes minutes.
Explanation: This message is displayed in response to the UPDATE SCHEDULE command. The schedule named schedule name has been updated in the server database. System Action: Server operation continues. User Response: None. ANR2533I Client action schedule duration set to days days.
Explanation: This message is displayed in response to 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. System Action: Server operation continues. User Response: None. ANR2528I Retry period reset to value determined by each client.
Explanation: This message is displayed in response to 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. System Action: Server operation continues. User Response: None. ANR2534I Client action schedule schedule name was not executed by node name in domain name.
Explanation: This message is displayed in response to the SET RETRYPERIOD command. System Action: Server operation continues. User Response: None. ANR2529I Scheduling mode set to POLLING.
Explanation: Immediate client action schedule name was not executed by node node name, which is in domain domain name. The schedule is being deleted. System Action: Server operation continues. User Response: None. ANR2535E Command: The node node name cannot be removed or renamed because it has an associated data mover.
Explanation: This message is displayed in response to 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. System Action: Server operation continues. User Response: None. ANR2530I Scheduling mode set to PROMPTED.
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.
Explanation: This message is displayed in response to 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.
Chapter 3. Common and Platform Specfic Messages
235
ANR2536E ANR2544E
ANR2536E Command: The option option is not valid with the storage pools data format. 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 indicated includes an option that is not valid with the specified (or defaulted) data format for the storage pool. System Action: The server does not process the command. User Response: Reissue the command with options appropriate for the desired data format of the storage pool. ANR2537E Command: Device class device class name has a device type that is not allowed for this operation.
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. System Action: The server does not process the 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 device class in the indicated command has a device type that is not allowed for this operation. System Action: The server does not process the command. User Response: Choose a different device class and reissue the command. ANR2538E Command: Backup set cannot be generated for NAS node node name.
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. System Action: The server does not process the command. User Response: Issue the command again with a storage pool appropriate for the desired function. ANR2543E Command: The volume name is not compatible with the operations intended use.
Explanation: Backup sets cannot be generated for NAS nodes. System Action: The command fails. User Response: None. ANR2539E Command: Storage pool Storage Pool Name does not have a valid data format.
Explanation: The data format of the indicated storage pool is not valid for the requested operation. The storage pool must have NATIVE or NONBLOCK data format. The server is unable to perform the requested operation. System Action: The command fails. User Response: Choose a different storage pool with the appropriate data format and reissue the command. ANR2540E Command: The option device class is not valid with the storage pools data format.
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. System Action: The server does not process the command. User Response: Issue the command again with a 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.
Explanation: The command indicated specifies a device class that is not valid with the specified (or defaulted) data format for the storage pool. System Action: The server does not process the command. User Response: Reissue the command with a data
236
IBM Tivoli Storage Manager: Messages
ANR2545E ANR2552I
ANR2545E The version of the centera library, version, is not compatible with the server. ANR2549E Command: Invalid virtual file space name. A virtual file space mapping name must have a forward slash as the first character.
Explanation: The centera library must be at least version 2 to be able to be compatible with the server. System Action: The transaction fails. User Response: Contact your service representative. ANR2546E The centera device is not capable of performing the required operation, version.
Explanation: The specified server command has been entered with a virtual file space name that is does not have a forward slash as the first character. System Action: The server does not process the command. User Response: Reissue the command with a valid virtual file space name. ANR2550W command name: Administrative schedule schedule name does not have valid activation information.
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. User Response: Contact your service representative. ANR2547E A Centera device (devclass) reported error message,error during command Centera command.
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.
Explanation: The Centera device reported an error while performing the specified command. System Action: The operation fails. User Response: Verify that the IP addresses specified in the device class associated with the storage pool are correct. Contact your service representative if the problem persists. ANR2548I NAS command: Renaming file space filespace name for node node name to file space new filespace name.
Explanation: The NAS Backup process detected a name conflict between the Virtual file space filespace name and a file space on the NAS device associated with the node node name. The Virtual file space is renamed to the new filespace name. During a NAS backup process, if the object to be backed up is a Virtual file space, TSM will verify that this name does not also exist as a file space on the NAS device. If a name conflict exists, TSM will rename the existing 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.
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. The audit operation corrects this discrepancy by removing the invalid activation information. System Action: Server database audit operation 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. System Action: None. User Response: None.
Chapter 3. Common and Platform Specfic Messages
237
ANR2553I ANR2562I
ANR2553I Server now disabled for session type access. processing, the domain will not be propogated to managed servers that are not capable of using it. System Action: Server operation continues. User Response: Consider upgrading managed servers to at least TSM Version 5 Release 3. ANR2559W command: One or more managed servers that subscribe to administrative schedule schedule name are not capable of using an enhanced style schedule.
Explanation: The server has been made unavailable for use by the specified session types with the DISABLE command. System Action: None. User Response: None. ANR2556W The managed server server name is not capable of using enhanced style client schedule schedule name in domain domain name. The domain will not be propogated to this server.
Explanation: The managed server server name is subscribed to domain domain name that contains client schedule schedule name that uses enhanced style syntax. The managed server is not capable of using an enhanced style schedule. Only TSM servers that are at least Version 5 Release 3 are capable of using enhanced style schedules. System Action: Server operation continues. The 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 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 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. System Action: Server operation continues. 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. System Action: Server operation continues. User Response: None. ANR2561I Schedule prompter contacting node name (session session number) to start a scheduled operation.
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. System Action: Server operation continues. The 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 schedule prompter contacts the client scheduler for node node name because a scheduled operation should be started for that node. System Action: Server operation continues. User Response: None. ANR2562I Automatic event record deletion started.
Explanation: A process has been started to delete event records for which the retention period has elapsed. System Action: Server operation continues. User Response: None.
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
238
IBM Tivoli Storage Manager: Messages
ANR2563I ANR2572W
ANR2563I Removing event records dated prior to date time. The contact attempt would be skipped for a locked node. ANR2570W A scheduled session has been denied. The schedule manager is not active.
Explanation: Events that were scheduled to start prior to date time are automatically deleted unless their startup window has not yet elapsed. System Action: Server operation continues. User Response: None. ANR2564I Automatic event record deletion ended record count records deleted.
Explanation: The client scheduler attempts to connect with the server, but it is denied a session because the schedule manager is not active. System Action: Server operation continues, but central scheduling is not operational. User Response: Issue the QUERY OPTION command to determine if the option DISABLESCHEDS YES has been specified in the server options file. If so, scheduling can be enabled by updating the server options file with DISABLESCHEDS NO and restarting the server. If DISABLESCHEDS YES was not specfied in the server options file, determine the source of the error by examining the QUERY ACTLOG command to view the activity log and search for messages. After the error has been resolved, restart the server to restore central scheduler operations. If the error cannot be isolated and resolved, contact your service representative. ANR2571W Scheduled session from node node name (platform name) has been denied, scheduled sessions are not currently available.
Explanation: The event deletion process has ended. A total of record count event records have been deleted from the database. System Action: Server operation continues. User Response: None. 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. System Action: Server operation continues. User Response: None. 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. System Action: Server operation continues. 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 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. System Action: Server operation continues. User Response: Issue the QUERY OPTION command to determine if the option DISABLESCHEDS YES has been specified in the server options file. If so, scheduling can be enabled by updating the server options file with DISABLESCHEDS NO and restarting the server. If DISABLESCHEDS YES was not specfied in the server options file, change the total number of sessions by altering the MAXSESSIONS parameter in the server options file and then restarting the server. The percentage of sessions that are available for scheduled operations can be increased by using the SET MAXSCHEDSESSIONS command. ANR2572W Schedule prompter session to node node name has been denied, scheduled sessions are not currently available.
Explanation: The 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. System Action: Server operation continues. 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.
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
Chapter 3. Common and Platform Specfic Messages
239
ANR2573W ANR2579E
window for the scheduled event has elapsed. User Response: To change the total number of sessions, alter the MAXSESSIONS parameter in the server options file and then restart the server. The percentage of sessions that are available for scheduled operations can be increased by using the SET MAXSCHEDSESSIONS command. ANR2573W Sufficient memory is not available for the central scheduler - will retry in number of seconds seconds. 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. System Action: Server operation continues. The 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.
Explanation: The server suspends central scheduler processing because sufficient server memory is not available. System Action: Server operation continues; the scheduler operation will be retried after the specified delay. 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. ANR2574W Insufficient recovery log space available for the central scheduler - will retry in number of seconds seconds.
Explanation: This message is displayed in response to the DEFINE SCHEDULE command. The schedule named schedule name in the server database. System Action: Server operation continues. User Response: None. ANR2578W Schedule schedule name in domain domain name for node node name has missed its scheduled start up window.
Explanation: The server suspends central scheduler processing because sufficient recovery log space is not available. System Action: Server operation continues; the scheduler operation will be retried after the specified delay. 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 can extend the size of the log by using the EXTEND LOG command. ANR2575W Insufficient database space available for the central scheduler - will retry in number of seconds seconds.
Explanation: This message is displayed when the scheduled startup window for this schedule has passed and the schedule has not begun. System Action: Server operation continues. The scheduled operation is not processed by the server. User Response: Ensure that a scheduled session for node node name has been initiated from the client to the server. Refer to Administrators Guide and Administrators Reference for more information on setting up scheduling operations. ANR2579E Schedule schedule name in domain domain name for node node name failed (return code return code).
Explanation: The server suspends central scheduler processing because sufficient database space is not available. System Action: Server operation continues; the scheduler operation will be retried after the specified delay. 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 can extend the size of the log by using the EXTEND DB command.
Explanation: This message is displayed when a client reports failure in executing a scheduled action. The return code reported by the client is displayed. System Action: Server operation continues. User Response: Examine the nodes schedule log to determine the cause for the failure.
240
IBM Tivoli Storage Manager: Messages
ANR2580E ANR2605E
ANR2580E Schedule schedule name in domain domain name for node node name failed. ANR2601E Command: Schedule description exceeds maximum length characters.
Explanation: This message is displayed when the server finds that a scheduled start window has elapsed for a client schedule and the client is not currently running the schedule. System Action: Server operation continues. 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.
Explanation: The specified command has been issued with a description that exceeds the maximum length. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid description. ANR2602E Command: Invalid action - action.
Explanation: The specified command has been issued with an invalid action. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid action. ANR2603E Command: Options string exceeds maximum length characters.
Explanation: This message is displayed when the scheduled startup window for this schedule has passed and the schedule has not begun. System Action: Server operation continues. The scheduled operation is not processed by the server. User Response: Ensure that the duration and period specified in the schedule are long enough to allow the schedule to start. Refer to Administrators Guide and Administrators Reference for more information on setting up scheduling operations. ANR2582E Command: Specified device class cannot be used with storage pools with different reclamation types.
Explanation: The specified command has been issued with an options string that exceeds the maximum length. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid options string. ANR2604E Command: Objects string exceeds maximum length characters.
Explanation: Storage pools can be defined with RECLAMATIONTYPE=THRESHOLD or RECLAMATIONTYPE=SNAPLOCK. A device class can only be used with either RECLAMATIONTYPE=THRESHOLD or 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. System Action: The command fails. User Response: Reissue the command and specify 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. ANR2600E Command: Invalid schedule name schedule name.
Explanation: The specified command has been issued with an objects string that exceeds the maximum length. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid objects string. ANR2605E Command: Invalid priority - priority.
Explanation: The specified command has been issued with an invalid priority. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid priority.
Explanation: The specified command has been issued with an invalid schedule name. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid schedule name.
Chapter 3. Common and Platform Specfic Messages
241
ANR2606E ANR2616E
ANR2606E Command: Invalid start date - date. valid value for period units. ANR2612E Command: Invalid day of week - day of week.
Explanation: The specified command has been issued with an invalid start date. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid start date. ANR2607E Command: Invalid start time - time.
Explanation: The specified command has been issued with an invalid value for day of the week. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid value for day of the week. ANR2613E Command: Invalid expiration - date.
Explanation: The specified command has been issued with an invalid start time. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid start time. ANR2608E Command: Invalid duration - duration.
Explanation: The specified command has been issued with an invalid expiration date. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid expiration date. ANR2614E Command: Invalid combination of the following parameters: duration, duration units, period, period units.
Explanation: The specified command has been issued with an invalid duration. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid duration. ANR2609E Command: Invalid duration units duration units.
Explanation: The specified command has been issued with an invalid value for duration units. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid value for duration units. ANR2610E Command: Invalid period - period.
Explanation: The specified command has been issued 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. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid combination of parameters. ANR2615E Command: Expiration date date has elapsed.
Explanation: The specified command has been issued with an invalid period. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid period. ANR2611E Command: Invalid period units - period units.
Explanation: The specified command has been issued with an elapsed expiration date date. System Action: Server operation continues, but the command is not processed. 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.
Explanation: The specified command has been issued with an invalid value for period units. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a
Explanation: The specified command has been issued with a start date that is not earlier than the expiration date. System Action: Server operation continues, but the command is not processed.
242
IBM Tivoli Storage Manager: Messages
ANR2617E ANR2626E
User Response: Issue the command using a schedule start date that is earlier than the expiration date. ANR2617E Command: Schedule schedule name is not defined in policy domain domain name. User Response: Issue the command and specify different schedules. ANR2622E Command: No new node associations added.
Explanation: The specified command has been issued with a schedule name that has not been defined in the indicated policy domain. System Action: Server operation continues, but the command is not processed. User Response: Issue the command using a schedule that has already been defined for this domain. ANR2618E Command: Schedule schedule name is already defined in policy domain domain name.
Explanation: The specified command has been issued but no new node associations are defined. System Action: Server operation continues, but the command has no effect. User Response: Issue the command and specify different nodes. ANR2623E Command: No node associations deleted.
Explanation: The specified command has been issued but no node associations are deleted. System Action: Server operation continues, but the command has no effect. User Response: Issue the command and specify different nodes. ANR2624E Command: No matching nodes registered.
Explanation: The specified command has been issued with a schedule name that has already been defined for the indicated policy domain. System Action: Server operation continues, but the command is not processed. User Response: Issue the command using a schedule that has not already been defined for this domain. ANR2619E Command: Currently defined period period is invalid with updated period units.
Explanation: No matching nodes are found for the specified command. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify different nodes. ANR2625E Command: No matching nodes registered in policy domain domain name.
Explanation: The specified command has been issued with a value for period units that is not allowed with the existing period. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a new period. ANR2620E Command: Currently defined duration duration is invalid with updated duration units.
Explanation: The specified command has been issued, but no matching nodes are registered in the indicated policy domain. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify different nodes. ANR2626E Command: Invalid value for replace replace.
Explanation: The specified command has been issued with a value for duration units that is not allowed with the existing duration. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a new duration. ANR2621E Command: No matching schedules.
Explanation: The specified command has been issued with an invalid value for replace. System Action: Server operation continues, but the command is not processed. User Response: Issue the command using a valid value for replace.
Explanation: The specified command has been issued but no matching schedules have been found. System Action: Server operation continues, but the command is not processed.
Chapter 3. Common and Platform Specfic Messages
243
ANR2627E ANR2640E
ANR2627E Command: Invalid value for format format. ANR2633E Command: Invalid end date - date.
Explanation: The specified command has been issued with an invalid value for format. System Action: Server operation continues, but the command is not processed. User Response: Issue the command using a valid value for format. ANR2628E Command: Invalid date - date.
Explanation: The specified command has been issued with an invalid end date. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid end date. ANR2634E Command: Invalid end time - time.
Explanation: The specified command has been issued with an invalid date. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid date. ANR2629E Command: Invalid time - time.
Explanation: The specified command has been issued with an invalid end time. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid end time. ANR2635E Command: Invalid time range - Begin: begin End: end.
Explanation: The specified command has been issued with an invalid time. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid time. ANR2630E Command: Event deletion is already in process.
Explanation: The specified command has been issued 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). System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid time range. ANR2636E Command: Invalid value for exceptions only - exceptions only.
Explanation: The specified command has been issued while event deletion is already in progress. System Action: Server operation continues, but the command is not processed. User Response: Wait for event deletion to complete before issuing the command. ANR2631E Command: Invalid begin date - date.
Explanation: The specified command has been issued with an invalid value for exceptions only. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid value for exceptions only. ANR2640E Command: Invalid percentage of sessions for scheduled processing - value.
Explanation: The specified command has been issued with an invalid begin date. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid begin date. ANR2632E Command: Invalid begin time - date.
Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid value.
Explanation: The specified command has been issued with an invalid begin time. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid begin time.
244
IBM Tivoli Storage Manager: Messages
ANR2641E ANR2651E
ANR2641E Command: Invalid event record retention period - value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid value. ANR2647E Command: Invalid type - type.
Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid value. ANR2642E Command: Invalid percentage for randomization - value.
Explanation: The specified command has been issued with an invalid type. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid type. ANR2648E Command: Type string exceeds maximum length characters.
Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid value. ANR2643E Command: Invalid schedule query period - value.
Explanation: The specified command has been issued with a type string that exceeds the maximum length. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid type string. ANR2649E Command: Schedule schedule name is not defined.
Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid value. ANR2644E Command: Invalid maximum number of command retries - value.
Explanation: The specified command has been issued with a schedule name that has not been defined. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a schedule that has already been defined. ANR2650E Command: Schedule schedule name is already defined.
Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid value. ANR2645E Command: Invalid retry period - value.
Explanation: The specified command has been issued with a schedule name that has already been defined. System Action: Server operation continues, but the command is not processed. 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.
Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid value. ANR2646E Command: Invalid scheduling mode value.
Explanation: The specified command has been issued with an invalid value.
Explanation: The specified command has been issued 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.
Chapter 3. Common and Platform Specfic Messages
245
ANR2652E ANR2660E
System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid combination of parameters. ANR2652E Command: Invalid combination of one or more of the following parameters: active, cmd, type. After that, the schedule will be deleted from the database. System Action: Server operation continues, but the command is not processed. User Response: Reissue the command with a valid number of days. ANR2656E Command: Invalid schedule style schedStyle.
Explanation: The specified command has been issued 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. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid combination of parameters. ANR2653W Command: Node node name cannot be processed because it is not registered or does not belong to the specified domain.
Explanation: The specified command has been issued with an invalid schedule style. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid schedule style. ANR2657E Command: Invalid month month.
Explanation: The specified command has been issued with an invalid month. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid month. ANR2658E Command: Invalid day of month month.
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. 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: The specified command has been issued with an invalid day of month. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid day of month. ANR2659E Command: Invalid week of month month.
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. System Action: Server operation continues, but the command is not processed. User Response: Issue the command without the NODES parameter. ANR2655E Command: Invalid client action schedule duration - days.
Explanation: The specified command has been issued with an invalid week of month. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid week of month. ANR2660E Command: Invalid combination of enhanced schedule parameters or their values: parm1 and parm2.
Explanation: The specified command has been issued 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.
Explanation: The specified command has been issued 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.
246
IBM Tivoli Storage Manager: Messages
ANR2661E ANR2666W
System Action: Server operation continues, but the command is not processed. User Response: Issue the command and specify a valid combination of parameters. ANR2661E Command: Invalid combination of enhanced schedule parameters or their values, parm1 and parm2, found for schedule name. System Action: Server operation continues. User Response: None. ANR2664E Command: Invalid parameter parm for schedule style schedule style.
Explanation: A specified parameter is not valid for the schedule style. System Action: Server operation continues, but the command is not processed. User Response: Issue the command and with parameters valid for the schedule style. ANR2665W Command: Invalid month and day, month day, detected.
Explanation: The specified update command has been issued with either an invalid combination of parameters or their values, or a specified parameter or value is not compatible with an option that is not being updated for the existing schedule. WEEKOFMONTH and DAYOFWEEK must not be specified with DAYOFMONTH. WEEKEND or WEEKDAY must be specified with the FIRST or LAST week of month. System Action: Server operation continues, but the command is not processed. User Response: To see the options for the existing schedule, issue: QUERY SCHEDULE FORMAT=DETAILED for the client or administrative schedule. Determine if the error was caused by one of the following: v a conflict between parameters to the update command. v a conflict between a parameter specified with the update command and a value that already exists for the schedule. For the latter problem, also update the existing option that is causing the problem. Correct the update command and issue it again. ANR2662I (*) Query schedule format=standard displays an asterisk in the day of week column for enhanced schedules. The period column is blank. Issue query schedule format=detailed to display complete information about an enhanced schedule.
Explanation: The specified command has been issued 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. System Action: Server operation continues. 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: This message explains the standard display for an enhanced schedule. System Action: Server operation continues. User Response: Issue query schedule format=detailed to display information about an enhanced schedule. ANR2663I Command: resetting existing options options for schedule name to default values. .
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. System Action: Server operation continues. 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.
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.
Chapter 3. Common and Platform Specfic Messages
247
ANR2670E ANR2675E
ANR2670E Export command: Invalid value for SCHEDSTYLE parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import. ANR2673E Import command: Invalid value for SCHEDSTYLE parameter in exported data - schedule schedule name in domain domain name defined with default SCHEDSTYLE value.
Explanation: During processing of command export command, an invalid value is encountered for the SCHEDSTYLE parameter for schedule schedule name in domain domain name. System Action: Export processing continues, but the exported data contains an unknown SCHEDSTYLE value for this schedule. If this data is imported, the default or existing SCHEDSTYLE value is used. User Response: Update the SCHEDSTYLE value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the SCHEDSTYLE value after import processing has been performed. ANR2671E Export command: Invalid value for SCHEDSTYLE parameter detected while exporting administrative schedule schedule name - default or existing value is used during import.
Explanation: During processing of command import command, an invalid value is encountered for the SCHEDSTYLE parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues, by using the default SCHEDSTYLE value for this schedule. User Response: Verify that the correct SCHEDSTYLE value has been used for this schedule. Update this value, if necessary. ANR2674E Import command: Invalid value for SCHEDSTYLE parameter in exported data - existing SCHEDSTYLE value for schedule schedule name in domain domain name was not updated.
Explanation: During processing of command export command, an invalid value is encountered for the SCHEDSTYLE parameter for administrative schedule schedule name. System Action: Export processing continues, but the exported data contains an unknown SCHEDSTYLE value for this schedule. If this data is imported, the server uses the default or existing SCHEDSTYLE value. User Response: Update the SCHEDSTYLE value for this schedule and restart the export command. Alternatively, the export data with the unknown value can be used, and the SCHEDSTYLE value can be checked and updated after import processing has been performed. ANR2672E Import command: Invalid value for SCHEDSTYLE parameter in exported data for schedule schedule name in domain domain name.
Explanation: During processing of command import command, an invalid value is encountered for the SCHEDSTYLE parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues, by using the existing SCHEDSTYLE value for this schedule. User Response: Verify that the correct SCHEDSTYLE value has been used for this schedule. Update this value, if necessary. ANR2675E Import command: Invalid value for SCHEDSTYLE parameter in exported data for administrative schedule schedule name.
Explanation: During preview processing of command import command, an invalid value is encountered for the SCHEDSTYLE parameter for administrative schedule schedule name. System Action: Processing of the command continues. If a later command is issued that causes the data to be imported, the default or existing SCHEDSTYLE value is used. User Response: If the data is imported with a later command, verify that the correct SCHEDSTYLE value is used for this schedule.
Explanation: During preview processing of command import command, an invalid value is encountered for the SCHEDSTYLE parameter for schedule schedule name in policy domain domain name. System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing SCHEDSTYLE value is used. User Response: If the data is imported with a later command, verify that the correct SCHEDSTYLE value is used for this schedule.
248
IBM Tivoli Storage Manager: Messages
ANR2676E ANR2708E
ANR2676E Import command: Invalid value for SCHEDSTYLE parameter in exported data - administrative schedule schedule name defined with default SCHEDSTYLE value. 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. ANR2702E The schedule prompter could not be started: diagcode.
Explanation: During processing of command import command, an invalid value is encountered for the SCHEDSTYLE parameter for administrative schedule schedule name. System Action: Processing of the command continues, by using the default SCHEDSTYLE value for this schedule. User Response: Verify that the correct SCHEDSTYLE value has been used for this schedule. Update this value, if necessary. ANR2677E Import command: Invalid value for SCHEDSTYLE parameter in exported data - existing SCHEDSTYLE value for administrative schedule schedule name was not updated.
Explanation: The schedule prompter cannot be started during initialization because sufficient memory is not available. Diagnostic code diagcode is issued. System Action: Initialization 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. ANR2703E Schedule prompter aborted.
Explanation: The schedule prompter ends because of a processing error. System Action: Server operation continues, but prompted scheduling is not operational. User Response: To determine the source of the error, examine server messages issued prior to this message. Issue the QUERY ACTLOG command to view the activity log and search for messages. After the error has been resolved, restart the server to restore central scheduler prompting operations. If the error cannot be isolated and resolved, contact your service representative. ANR2707E Out of server log space in central scheduler.
Explanation: During processing of command import command, an invalid value is encountered for the SCHEDSTYLE parameter for administrative schedule schedule name. System Action: Processing of the command continues, by using the existing SCHEDSTYLE value for this schedule. User Response: Verify that the correct SCHEDSTYLE value has been used for this schedule. Update this value, if necessary. ANR2700E Schedule manager aborted.
Explanation: The schedule manager has ended because of an error condition and is not able to maintain entries for scheduled operations. System Action: Server operation continues, but the central scheduler is not operational. User Response: To determine the source of the error, 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 resolved, contact your service representative. ANR2701E The schedule manager could not be started: diagcode.
Explanation: The server ends a database update transaction for the central scheduler because sufficient log space is not available on the server. System Action: Server operation continues, but the database update fails. User Response: An authorized administrator can use 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. ANR2708E Out of server database space in central scheduler.
Explanation: The server ends a database update transaction for the central scheduler because sufficient database space is not available on the server. System Action: Server operation continues, but the database update fails. User Response: An authorized administrator can use the DEFINE DBVOLUME command to add volumes
Chapter 3. Common and Platform Specfic Messages
Explanation: The schedule manager cannot be started during initialization because sufficient memory is not available. Diagnostic code diagcode is issued. System Action: Initialization fails.
249
ANR2709E ANR2717E
for use by the database and can use the EXTEND DB command to extend the size of the database so that the new volumes are used. ANR2709E Schedule manager : Unable to start event record deletion. node node1. If the problem persists, contact your service representative to resolve the client program error. ANR2715E Client node node id unable to register valid address for server prompting: type address type (high address low address).
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. 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. ANR2712E Node node1 requested scheduling information for node node2 - session rejected.
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. System Action: Server operation continues, but the 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: 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. System Action: Server operation continues, but the 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 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 client scheduler for node node1 has attempted to execute a scheduled operation for another node, node2. System Action: Server operation continues, but the scheduled operation is not processed. User Response: Try restarting the client scheduler for node node1. If the problem persists, contact your service representative to resolve client program error. ANR2714E Node node1 trying to report scheduled operation results for node node2 session rejected.
Explanation: The client scheduler for node node1 has attempted to report the results of a scheduled operation using another node name, node2. System Action: Server operation continues, but the results that were sent from node node1 are not be stored in the servers database. User Response: Try restarting the client scheduler for
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
250
IBM Tivoli Storage Manager: Messages
ANR2718W ANR2757E
method is not currently available. The only valid address type is 1 (for TCP/IP). System Action: Server operation continues, but the 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 your service representative. ANR2718W Schedule manager disabled. 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. System Action: Server operation continues. The scheduled command is ended. User Response: None. ANR2754E DEFINE SCHEDULE or UPDATE SCHEDULE parameter CMD=command - Unknown command.
Explanation: The schedule manager has been disabled because the DISABLESCHEDS YES option was specified in the server options file. System Action: Server operation continues, but the 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 ).
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. ANR2755E DEFINE SCHEDULE or UPDATE SCHEDULE parameter CMD=command - not eligible for scheduling.
Explanation: This message is displayed when the server starts the execution of a scheduled command. The name of the schedule and the actual command scheduled is displayed. System Action: Server operation continues, the scheduled command is processed. User Response: None. ANR2751I Scheduled command schedule name completed successfully.
Explanation: The specified command is not eligible for scheduling. System Action: The DEFINE SCHEDULE or UPDATE SCHEDULE command is not processed. User Response: None. ANR2756I Scheduled command schedule name started successfully.
Explanation: This message is displayed when the server successfully completes processing of a scheduled command. System Action: Server operation continues. User Response: None. ANR2752E Scheduled command schedule name failed.
Explanation: This message is displayed when the server successfully starts processing of a background process for a scheduled command. System Action: Server operation continues. User Response: None. ANR2757E Command: The NODES parameter cannot be used when querying events for administrative schedules.
Explanation: This message is displayed when the server encounters a failure in processing a scheduled command. System Action: Server operation continues. The 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
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 administrative schedules. System Action: Server operation continues, but the command is not processed. User Response: Issue the command without the NODES parameter.
Chapter 3. Common and Platform Specfic Messages
251
ANR2758E ANR2766W
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. User Response: None. ANR2763E Command: The hexadecimal string entered for the path parameter is not valid; the string must contain an even number of characters.
Explanation: The .template file adds 9 more characters to the end of the filename. System Action: Server operation continues. User Response: Reduce the filename length to a working range for s390 system ANR2759I Command: The virtual file space definition vfs name for node node name has been deleted.
Explanation: The command indicated specifies a value that is not valid for the Hex Filespace parameter. System Action: The server does not process the command. User Response: Reissue the command with a valid entry for the Hex Filespace 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: In response to the DELETE VIRTUALFSMAPPING command, the virtual file space mapping vfs name for the node node name has been deleted in the server database. System Action: Server operation continues. User Response: None. ANR2760E Command: Unable to delete the virtual file space definition vfs name for node node name. A file space definition exists with the same 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. System Action: Server operation continues, the command fails. User Response: Reissue the command with a different target filespace name ANR2765E command: The node node name has an invalid node type for virtual file space definitions; the node type must be NAS.
Explanation: 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. System Action: The server does not process the command. User Response: To delete the virtual file space definition, first delete the filespace definition with the same name. ANR2761I Audit command: auditing inventory virtual file space mappings.
Explanation: A Define VirtualFSMapping command was entered with an invalid node type. System Action: The server does not process the command. User Response: You might want to run this command again, specifying a node of TYPE=NAS. ANR2766W Command: Virtual file space name vfs name conflicts with file space on the network attached storage (NAS) device.
Explanation: This message is displayed during a database audit and indicates that server information about virtual file space mappings is currently being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR2762I Command: A virtual file space mapping named vfs name for node node name has been updated.
Explanation: The specified server command has been entered with a virtual file space that has the same name as a file space on the NAS device. System Action: The server operation continues. 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.
Explanation: In response to the UPDATE VIRTUALFSMAPPING command, a virtual file space mapping for the specified node has been updated in the server database. System Action: Server operation continues.
252
IBM Tivoli Storage Manager: Messages
ANR2776I ANR2803I
ANR2776I Audit command: Inventory object (object.ID) is part of an incomplete group. The inventory entry will be deleted. User Response: Correct the error and reissue the command. ANR2797E The license value was skipped because of a bad date range.
Explanation: A database audit process found an inventory object that is part of an incomplete group. Because FIX=YES has been specified for the command, the inventory entry is deleted. System Action: Audit processing continues. User Response: None. ANR2777I Audit command: Inventory object (object.ID) is part of an incomplete group.
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: A database audit process found an inventory object that is part of an incomplete group. System Action: Audit processing continues. 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: The server refuses a server operation because the server is not licensed with the appropriate support. System Action: Server operation fails. User Response: Obtain and register the appropriate license. ANR2799W Server operation is in violation of server license terms - server is not licensed for License required.
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. System Action: Audit processing continues. User Response: None. ANR2779I Audit command: Storage entry for an inventory object (object.ID) cannot be found.
Explanation: The server warns about a server operation because the server is not licensed with the appropriate support. System Action: Server operation continues. User Response: Obtain and register the appropriate license. ANR2800E The license manager cannot be started: diagcode.
Explanation: A database audit process cannot find the storage entry for the specified inventory object. System Action: Audit processing continues. User Response: Run the audit command again with FIX=YES, so that the error can be corrected. ANR2780W Command: Updates for nodes previously processed during this command will be rolled back.
Explanation: The license manager cannot be started during initialization because sufficient memory is not available. Diagnostic code diagcode is issued. System Action: Initialization 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. ANR2803I License manager started.
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. System Action: Server operation continues.
Explanation: The license manager is started when the server is initialized. The license manager monitors license compliance. System Action: Server operation continues.
Chapter 3. Common and Platform Specfic Messages
253
ANR2804W ANR2813I
User Response: None. ANR2804W Insufficient memory is available for the license manager - will retry in number of seconds seconds. User Response: An authorized administrator can use 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. ANR2808E Out of server database space in license manager.
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. 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. ANR2805W Insufficient recovery log space available for the license manager - will retry in number of seconds seconds.
Explanation: The server ends a database update transaction for the license manager because sufficient database space is not available on the server. System Action: Server operation continues, but the database update fails. User Response: An authorized administrator can use the DEFINE DBVOLUME command to add volumes for use by the database and can use the EXTEND DB command to extend the size of the database so that the new volumes are used. ANR2811I Audit License completed - Server is in compliance with license terms.
Explanation: The server suspends license manager processing because sufficient recovery log space is not available. System Action: Server operation continues; the license manager operation will be retried after the specified delay. User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes using the DEFINE LOGVOLUME command, and can extend the size of the log using the EXTEND LOG command. ANR2806W Insufficient database space available for the license manager - will retry in number of seconds seconds.
Explanation: The results from the AUDIT LICENSES command indicate the server is in compliance with the terms of the current license. System Action: Server operation continues. User Response: None. ANR2812W License Audit completed - ATTENTION: Server is NOT in compliance with license terms.
Explanation: The results from the AUDIT LICENSES command indicate the server is not in compliance with the terms of the current license. System Action: Server operation continues, but the REGISTER NODE command or backup-archive requests, or both, will fail. User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance. ANR2813I Server is licensed for a capacity of capacity gigabytes and number of clients clients.
Explanation: The server suspends license manager processing because sufficient database space is not available. System Action: Server operation continues; the license manager operation will be retried after the specified delay. User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes using the 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.
Explanation: This message is issued during server startup. System Action: Server operation continues. User Response: None.
Explanation: The server ends a database update transaction for the license manager because sufficient recovery log space is not available on the server. System Action: Server operation continues, but the database update fails.
254
IBM Tivoli Storage Manager: Messages
ANR2814I ANR2823I
ANR2814I Audit command: License audit period changed to number of days days. ANR2819I Command: Licensed capacity changed to capacity GB with number of clients clients.
Explanation: This message is displayed in response to the SET LICENSEAUDITPERIOD command used to change the interval in days between automatic license audits. System Action: Server processing continues. User Response: None. ANR2815E Command: Invalid value specified for interval between license audits - value.
Explanation: The license information has been changed to the indicated values with the REGISTER LICENSE command. System Action: None. 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.
Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid value. ANR2816E Command: License audit or register operation already in progress.
Explanation: A background process has been started to audit the server for license compliance. 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. User Response: The administrator may query the status of the background process using the QUERY PROCESS command. ANR2821E Automatic license audit could not be started: diagcode.
Explanation: The server is currently performing a register license or license audit. System Action: The server does not process the 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.
Explanation: The license manager cannot start an automatic process to audit server licenses because sufficient memory is not available. Diagnostic code diagcode is issued. System Action: Server processing continues. 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. ANR2822I Cancel in progress
Explanation: A background process has been started 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. User Response: The administrator may query the status of the background process by using the QUERY PROCESS command, or cancel the process with the CANCEL PROCESS command. ANR2818I Command: Licensed capacity is capacity GB with number of clients clients.
Explanation: The license audit operation has been cancelled 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 AUDIT LICENSES operation. System Action: Server operation continues. User Response: None. ANR2823I Have audited number of nodes nodes
Explanation: This message displays the license information that existed before issuing the REGISTER LICENSE command. System Action: None. User Response: None.
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. System Action: Server operation continues.
Chapter 3. Common and Platform Specfic Messages
255
ANR2824I ANR2841W
User Response: None. ANR2824I License audit process process number canceled - number of nodes nodes audited. ANR2833I Command: Auditing license definitions.
Explanation: The server has started to audit database definitions that describe licensing information. System Action: Server database audit operation continues. User Response: None. ANR2834W License Audit completed - WARNING: Server is NOT in compliance with license terms.
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. System Action: The server process is ended and server operation continues. User Response: None. ANR2825I License audit process process number completed successfully - number of nodes nodes audited.
Explanation: The results from the AUDIT LICENSES command indicate that the server is not in compliance with the terms of the current license. System Action: Server operation continues, but the REGISTER NODE command fails. User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in 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.
Explanation: A background server process to audit server licenses has completed successfully after auditing the specified number of nodes. System Action: The server process is ended and server operation continues. User Response: None. ANR2826I License audit process process number terminated in error - number of nodes nodes audited.
Explanation: A background server process to audit 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. System Action: The server process is ended and server operation continues. User Response: None. ANR2832I Command: The License Manager has not yet completed initialization - please retry this command later.
Explanation: A background process has been started to audit the server for license compliance. System Action: The server checks registered nodes for the server and compares this against the value for which the server is licensed. User Response: The administrator may query the status of the background process using the QUERY PROCESS command, or cancel the process with the CANCEL PROCESS command. ANR2839I Automatic license audit started as process process ID.
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. System Action: Server operation continues; the command is not processed. User Response: Reissue the command after waiting 10 minutes. If this message is displayed after a number of retry attempts, contact your service representative.
Explanation: A background process has been started to audit the server for license compliance. System Action: The server checks registered nodes and compares them against the value for which the server is licensed. User Response: The administrator may query the status of the background process by using the QUERY PROCESS command. ANR2841W Server is NOT IN COMPLIANCE with license terms.
Explanation: This message is issued periodically when the server configuration does not comply with the terms for which it is licensed.
256
IBM Tivoli Storage Manager: Messages
ANR2852I ANR2904E
System Action: Server operation continues. User Response: Use the QUERY LICENSE command to display the current server configuration with respect to licensed terms to discover which factors of the configuration do not conform to your license. Contact your service representative to obtain more licenses, if required. ANR2852I Current license information: 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. User Response: None. ANR2901W The result of character string concatenation was truncated.
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. System Action: Server operation continues. User Response: None. ANR2853I New license information:
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. User Response: None. ANR2902E Insufficient memory was available to process the SQL statement.
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. System Action: Server operation continues. 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 Server is licensed to support Tivoli Space Manager clients.
Explanation: Sufficient memory was not available to complete the processing of an SQL query. System Action: The SQL query is terminated. User Response: None. ANR2903E An SQL parser stack overflow occurred while processing token token.
Explanation: This message is issued during server startup. System Action: Server operation continues. User Response: None. ANR2860I Server is licensed to support Tivoli Disaster Recovery Manager.
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. System Action: The SQL query is terminated. User Response: None. ANR2904E Unexpected SQL key word token token.
Explanation: This message is issued during server startup. System Action: Server operation continues. User Response: None.
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. User Response: None.
Chapter 3. Common and Platform Specfic Messages
257
ANR2905E ANR2915E
ANR2905E Unexpected SQL identifier token token. ANR2910E Invalid SQL token - token.
Explanation: A syntax error occurred because an SQL 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. System Action: The SQL query is terminated. User Response: None. ANR2906E Unexpected SQL literal token - token.
Explanation: An invalid SQL token was found. For example, the token formed by the character sequence ::! is not a valid SQL token. System Action: The SQL query is terminated. User Response: None. ANR2911E Invalid SQL numeric literal token token.
Explanation: A syntax error occurred because an SQL 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. System Action: The SQL query is terminated. User Response: None. ANR2907E Unexpected SQL operator token - token.
Explanation: An invalid SQL numeric literal token was found. For example, the floating point literal 1.456E is not valid. System Action: The SQL query is terminated. User Response: None. ANR2912E Invalid character string literal token token.
Explanation: A syntax error occurred because an SQL 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 =. System Action: The SQL query is terminated. User Response: None. ANR2908E Unexpected SQL punctuation 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. System Action: The SQL query is terminated. User Response: None. ANR2913E Invalid SQL identifier token - token.
Explanation: A syntax error occurred because an SQL 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. System Action: The SQL query is terminated. User Response: None. ANR2909E The SQL statement is incomplete; additional tokens are required.
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. System Action: The SQL query is terminated. User Response: None. ANR2914E SQL identifier token token is too long; name or component exceeds 18 characters.
Explanation: An SQL identifier token was found that exceeds the maximum length of 18 characters per component. System Action: The SQL query is terminated. User Response: None. ANR2915E The SQL token beginning with token is missing an ending delimiter.
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. System Action: The SQL query is terminated. User Response: None.
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. System Action: The SQL query is terminated. User Response: None.
258
IBM Tivoli Storage Manager: Messages
ANR2916E ANR2925E
ANR2916E The SQL data types data type and data type are incompatible for operator operator. ANR2921E The SQL data type of expression expression is data type; expecting a character string expression.
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 +. System Action: The SQL query is terminated. User Response: None. ANR2917E The SQL data type of expression expression is data type; expecting an integer expression.
Explanation: An SQL expression of character string type CHAR or VARCHAR is expected. System Action: The SQL query is terminated. User Response: None. ANR2922E The SQL data type of expression expression is data type; expecting a date, timestamp, character string date, character string timestamp, or interval expression.
Explanation: An SQL expression of data type SMALLINT, INTEGER, or DECIMAL with scale zero is expected. System Action: The SQL query is terminated. User Response: None. ANR2918E The SQL data type of expression expression is data type; expecting a Boolean expression.
Explanation: An SQL expression was expected of one of the types DATE, TIMESTAMP, CHAR, VARCHAR, or INTERVAL as the operand to the EXTRACT function. In the case of CHAR or VARCHAR, the expression must be a valid character string representation of a date or a timestamp. System Action: The SQL query is terminated. User Response: None. ANR2923E The SQL data type of expression expression is data type; expecting a time, timestamp, character string time, character string timestamp, or interval expression.
Explanation: An SQL expression of data type BOOLEAN is expected. System Action: The SQL query is terminated. User Response: None. ANR2919E The SQL data type of expression expression is data type; expecting a numeric expression.
Explanation: An SQL expression was expected of one 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. System Action: The SQL query is terminated. User Response: None. ANR2924E The SQL data type of expression expression is data type; expecting a date or character string date expression.
Explanation: An SQL expression of numeric data type SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL, FLOAT, or DOUBLE_PRECISION is expected. System Action: The SQL query is terminated. User Response: None. ANR2920E The SQL data type of expression expression is data type; expecting a 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. System Action: The SQL query is terminated. User Response: None.
Explanation: An SQL expression was expected of one of the types DATE, CHAR, or VARCHAR. In the case of CHAR or VARCHAR, the expression must be a valid character string representation of a date. System Action: The SQL query is terminated. User Response: None. ANR2925E The SQL data type of 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
Chapter 3. Common and Platform Specfic Messages
259
ANR2926E ANR2934E
CHAR or VARCHAR, the expression must be a valid character string representation of a time. System Action: The SQL query is terminated. User Response: None. ANR2926E The SQL data type of expression expression is data type; expecting a date, timestamp, character string date, or character string timestamp expression. User Response: None. 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). System Action: The SQL query is terminated. User Response: None. ANR2931E A subquery expression may not contain a reference to a column name that is contained in an outer query expression.
Explanation: An SQL expression was expected of one 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. System Action: The SQL query is terminated. User Response: None. ANR2927E The SQL data type of expression expression is data type; expecting an interval containing a single date-time field.
Explanation: A subquery contains a reference to a column name in an outer query expression. System Action: The SQL query is terminated. User Response: None. ANR2932E The maximum nesting depth for subquery expressions has been exceeded.
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. System Action: The SQL query is terminated. User Response: None. ANR2928E A number can not be converted to SQL data type INTERVAL if the interval contains multiple date-time fields.
Explanation: Too many nested subqueries were specified. System Action: The SQL query is terminated. User Response: None. ANR2933E The WHERE clause must not contain an aggregate function.
Explanation: The use of the aggregate functions COUNT, MAX, MIN, SUM, AVG, VARIANCE, or STDDEV in the WHERE clause is not allowed. System Action: The SQL query is terminated. User Response: None. 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: 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. System Action: The SQL query is terminated. User Response: None. ANR2929E The expression expression is not an integer constant.
Explanation: The result data type of a CASE expression can not be determined because all of the THEN expressions and the ELSE expression (if present) specifies the NULL key word. System Action: The SQL query is terminated. User Response: None.
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. System Action: The SQL query is terminated.
260
IBM Tivoli Storage Manager: Messages
ANR2935E ANR2944E
ANR2935E The date-time field field is not present in the expression expression (data type data type). ANR2940E The reference reference is an unknown SQL column name.
Explanation: The specified date-time field (YEAR, MONTH, DAY, HOUR, MINUTE, or SECOND) is not contained in the data type of the expression. System Action: The SQL query is terminated. User Response: None. ANR2936E The SQL aggregate function function can not be nested within another aggregate function.
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. System Action: The SQL query is terminated. User Response: None. ANR2941E The column reference column reference matches more than one SQL column name.
Explanation: One of the aggregate functions COUNT, MAX, MIN, SUM, AVG, VARIANCE, or STDDEV was found nested within another aggregate expression. System Action: The SQL query is terminated. User Response: None. ANR2937E An SQL subquery expression can not be nested within an aggregate function.
Explanation: The specified column reference is ambiguous because it matches the columns associated with multiple tables. System Action: The SQL query is terminated. User Response: None. ANR2942E The column reference column reference is not allowed in this context because it is part of an outer SQL query expression.
Explanation: An expression containing a subquery was found nested within one of the aggregate functions COUNT, MAX, MIN, SUM, AVG, VARIANCE, or STDDEV. System Action: The SQL query is terminated. User Response: None. ANR2938E The column column is not allowed in this context; it must either be named in the GROUP BY clause or be nested within an aggregate function.
Explanation: 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. System Action: The SQL query is terminated. User Response: None. ANR2943E The column reference column reference is a duplicate of another SQL column name in the same list.
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 COUNT, MAX, MIN, SUM, AVG, VARIANCE, or 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. System Action: The SQL query is terminated. User Response: None. ANR2939E The reference reference is an unknown SQL table name.
Explanation: A duplicate column reference was specified within the same GROUP BY or ORDER BY list of columns. System Action: The SQL query is terminated. User Response: None. ANR2944E The reference reference is an unknown SQL scalar function 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. System Action: The SQL query is terminated. User Response: None.
Explanation: The specified function reference is not the name of a valid scalar function. System Action: The SQL query is terminated. User Response: None.
Chapter 3. Common and Platform Specfic Messages
261
ANR2945E ANR2953E
ANR2945E Too few arguments are specified for SQL scalar function function. ANR2949E Arithmetic overflow occurred for SQL operator operator.
Explanation: Too few function arguments were specified. For example, the expression LEFT(x) is invalid because the LEFT function requires at least two arguments. System Action: The SQL query is terminated. User Response: None. ANR2946E Too many arguments are specified for SQL scalar function function.
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. System Action: The SQL query is terminated. User Response: None. 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: Too many function arguments were specified. For example, the expression UPPER(x,y) is invalid because the UPPER function requires exactly one argument. System Action: The SQL query is terminated. User Response: None. ANR2947E Division by zero was detected for operator operator.
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. System Action: The SQL query is terminated. User Response: None. ANR2951E The value value (data type data type) is not a valid argument 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. System Action: The SQL query is terminated. User Response: None. ANR2948E The value value can not be assigned or converted to SQL data type data type.
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. System Action: The SQL query is terminated. User Response: None. ANR2952E The value value (data type data type) is not a valid character string representation of an SQL date or a timestamp for operator operator.
Explanation: A value could not assigned or converted to a value in the specified SQL data type because either 1) the data type of the value can not be legally cast to the target data type (for example, data type TIME can not be converted to data type INTEGER); 2) the assignment of the value results in overflow in the target data type (for example, the decimal value 12345678.34 can not be assigned to data type DECIMAL(3,2) because the precision of the target type is exceeded); or 3) the syntax of a character string value is not appropriate for the target data type (for example, the string abc can not be converted to data type DATE). System Action: The SQL query is terminated. User Response: None.
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. System Action: The SQL query is terminated. User Response: None. ANR2953E 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
262
IBM Tivoli Storage Manager: Messages
ANR2954E ANR2961E
specified. For example, the string g pm is neither a valid time nor a timestamp. System Action: The SQL query is terminated. User Response: None. ANR2954E An SQL subquery used in a scalar expression must yield a table that contains at most one row. ANR2958E SQL temporary table storage has been exhausted.
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. System Action: The SQL query is terminated. 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: 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. System Action: The SQL query is terminated. 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 avolume. ANR2959E SQL temporary table row is too wide.
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. System Action: The SQL query is terminated. User Response: None. ANR2956E Unable to access SQL base table table.
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. System Action: The SQL query is terminated.
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. System Action: The SQL query is terminated. User Response: None. ANR2957E An error occurred inserting a row in an SQL temporary table. The server database size may need to be increased
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.
Explanation: A syntax error occurred because an SQL 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. System Action: The SQL query is terminated. User Response: None. ANR2961E Invalid SQL enumerated type name name.
Explanation: An error occurred when attempting to insert a row into a temporary table being used for an SQL query. This message is typically preceded by another error describing the condition. In many cases this error can be resolved by increasing the size of the server database. Free space in the database is used to store temporary tables created during the execution of an SQL SELECT query. System Action: The SQL query is terminated. User Response: None.
Explanation: A syntax error occurred because an SQL 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
Chapter 3. Common and Platform Specfic Messages
263
ANR2962E ANR2998W
server can be found in the SQL catalog table SYSCAT.ENUMTYPES. System Action: The SQL query is terminated. User Response: None. ANR2962E Unable to resolve SQL enumerated type for value value. 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: 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. System Action: The SQL query is terminated. User Response: None. ANR2963W This SQL query may produce a very large result table, or may require a significant amount of time to compute.
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: 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. System Action: The administrator is asked whether to 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 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. System Action: Server processing continues. 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 The server log is log full percentage percent full. The server will delay transactions by delay time milliseconds.
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. System Action: The SQL query is terminated. User Response: None.
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. System Action: Server processing continues. User Response: Monitor server activity and log usage. If possible, delay adding new work to the server load. ANR2998W The server log is log full percentage percent full. The server has cancelled the oldest transaction in the log.
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. System Action: The SQL query is terminated.
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. System Action: Server processing continues.
264
IBM Tivoli Storage Manager: Messages
ANR3000E ANR3010W
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. ANR3005E Command: The server name exceeds maximum length characters.
Explanation: The configuration manager name specified in the command is longer than the maximum length allowed. System Action: Server operation continues. The command is not processed. 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.
Explanation: The command can only be issued on a server that is a configuration manager. System Action: Server operation continues. The command is not processed. 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. System Action: Server operation continues. The command is not processed. User Response: Issue this command from a managed server. ANR3002E Command: Profile name exceeds maximum length characters.
Explanation: The specified command has been issued with an invalid refresh interval. System Action: Server operation continues. The command is not processed. User Response: Issue the command and specify a valid refresh interval value. ANR3007E Command: The option option must be specified.
Explanation: The profile name specified in the command is longer than the maximum length allowed. System Action: Server operation continues. The command is not processed. User Response: Select a profile name that does not exceed the maximum length. ANR3003E Command: Profile description exceeds maximum length characters.
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. System Action: Server operation continues. The command is not processed. User Response: Reissue the command with the 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: The profile description specified in the command is longer than the maximum length allowed. System Action: Server operation continues. The command is not processed. User Response: Select a description that does not exceed the maximum length. ANR3004E Command: The configuration manager name exceeds maximum length characters.
Explanation: A command has been entered that will delete an object from a configuration manager. Since this object is associated with one or more profiles on a configuration manager, configuration refresh processing will delete this object on subscribing managed servers. System Action: The system asks whether you wish to continue with the command. User Response: To process the command, enter 'Y' to continue or 'N' to stop the process.
Explanation: The configuration manager name specified in the command is longer than the maximum length allowed. System Action: Server operation continues. The command is not processed. User Response: Select a configuration manager name that does not exceed the maximum length.
Chapter 3. Common and Platform Specfic Messages
265
ANR3011E ANR3020E
ANR3011E command: Subscription for profile profile name was not deleted because one or more objects could not be discarded. ANR3015E command: One or more profiles still exist.
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. User Response: Examine previous messages to determine the action that must be taken before remaining objects can be discarded. Alternatively, you can delete the subscription without using the DISCARDOBJECTS=YES option. ANR3012I command: Configuration manager state set to state.
Explanation: A configuration manager state cannot be set to OFF is one or more profiles still exist. System Action: Server operation continues. The command is not processed. 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 manager state. System Action: The command succeeded. User Response: None. ANR3013W command: Configuration manager state already set to state.
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. System Action: The command succeeded. User Response: None. ANR3017I command: Profile profile name defined.
Explanation: The specified state is already in force on the server. System Action: Server operation continues. The command is not processed. 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. ANR3014E command: One or more subscriptions still exist.
Explanation: The command has successfully define a profile. System Action: The command succeeded. User Response: None. ANR3018E command: Profile profile name already exists.
Explanation: The profile specified already exists on the configuration manager. System Action: Server operation continues. The command is not processed. User Response: Decide on another profile name and reissue the command. ANR3019I command: Profile profile name updated.
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. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY SUBSCRIBERS command to determine which subscriptions still exist. The DELETE SUBSCRIBER command can be used to remove the record of these subscriptions. You may instead want to delete the actual subscription(s) on the managed server(s). When there are no more subscriptions recorded on the configuration manager, you must then delete all the profiles. Once the profiles have been deleted, you can reissue the command.
Explanation: The command has successfully updated a profile. System Action: The command succeeded. User Response: None. ANR3020E command: Profile profile name not found.
Explanation: The profile specified could not be found. System Action: Server operation continues. The command is not processed.
266
IBM Tivoli Storage Manager: Messages
ANR3021I ANR3030I
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 command: Profile profile name copied to profile profile name. ANR3026I command: Profile profile name deleted.
Explanation: The command has successfully deleted the profile from the configuration manager. System Action: The command succeeded. User Response: None. ANR3027E command: One or more subscriptions still exist 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. System Action: The command succeeded. User Response: None. ANR3022E command: The profile lock timeout interval value must be between minimum value and maximum value.
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. System Action: Server operation continues. The command is not processed. 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 specified command has been issued with an invalid lock timeout interval. System Action: Server operation continues. The command is not processed. User Response: Issue the command and specify a valid lock timeout interval value. ANR3023I command: Profile profile name locked.
Explanation: The command has successfully locked the profile. No configuration information can be propogated to the subscribers of the profile until it is unlocked. System Action: The command succeeded. User Response: None. ANR3024W command: Profile profile already locked with timeout interval greater than interval.
Explanation: The specifed command cannot be performed on a locked profile. System Action: Server operation continues. The command is not processed. User Response: Unlock the profile using the UNLOCK PROFILE command and then reissue the command. ANR3029E command: Profile name not specified.
Explanation: An attempt was made to lock the specified profile. The profile is already locked with a timeout interval greater than the value specifed. System Action: The profile remains locked with the original timeout interval. User Response: If you want to lower the timeout interval, unlock the profile and then lock the profile again specifying the lower value. ANR3025I command: Profile profile name unlocked.
Explanation: A profile name must be specifed on this command using the PROFILE= parameter. System Action: Server operation continues. The command is not processed. User Response: Reissue the command and specify a profile name. ANR3030I command: Subscription defined for profile profile name.
Explanation: The command has successfully unlocked the profile. Configuration information can now be propogated to the subscribers of the profile. System Action: The command succeeded. User Response: None.
Explanation: The command has successfully defined a subscription to the specified profile. A refresh of the configuration information has been initiated. System Action: The command succeeded.
Chapter 3. Common and Platform Specfic Messages
267
ANR3031W ANR3039E
User Response: None. ANR3031W command: Subscription for profile profile name already exists. subscription will reappear when it performs its next configuration refresh. System Action: The command succeeded. User Response: None. ANR3036E command: Subscriber subscriber name not found.
Explanation: A subscription already exists for the specified profile. System Action: Server operation continues. The command is not processed. User Response: Check to make sure you specified the correction profile name, and reissue the command if needed. ANR3032E command: Server name not specified.
Explanation: The specified subscriber name was not found in the configuration managers records as being a valid subscriber of any profiles. System Action: Server operation continues. The command is not processed. 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 profile profile name.
Explanation: A server name must be specifed on this command using the SERVER= parameter. This identifies the configuration manager. System Action: Server operation continues. The command is not processed. User Response: Reissue the command and specify a server name. ANR3033E command: Server server is not the managed servers configuration manager.
Explanation: The command has successfully deleted a subscription for the specified profile. A refresh of the configuration information has been initiated. System Action: The command succeeded. User Response: None. ANR3038E command: Subscription for profile profile name not found.
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. System Action: Server operation continues. The command is not processed. User Response: Reissue the command and leave off the server parameter. It will default to use the current configuration manager. A QUERY SUBSCRIPTION will display the configuration manager currently in use. ANR3034E command: Server server cannot be used as this servers configuration manager.
Explanation: A subscription was not found for the specified profile. System Action: Server operation continues. The command is not processed. User Response: Check to see that the profile name was specified correctly. Issue the QUERY SUBSCRIPTION command to check to see which profiles have subscriptions. Reissue the command with the correct profile name. ANR3039E command: No matching administrators found in configuration.
Explanation: A server name was specified on the command which cannot be used as a configuration manager. System Action: Server operation continues. The command is not processed. User Response: Find out the currect name for the configuration manager and then reissue the command. ANR3035I command: Subscriber subscriber name deleted.
Explanation: No administrator definitions were found on the configuration manager that match the admin(s) specified on the DEFINE PROFASSOCIATION command. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY ADMIN command to check which administrators that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.
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
268
IBM Tivoli Storage Manager: Messages
ANR3040I ANR3047E
ANR3040I command: All administrators associated with profile profilename. ANR3044I command: All domains associated with profile profilename.
Explanation: The command has successfully associated all the administrators with the specified profile. All administrator definitions will be automatically propogated to managed servers which subscribe to the profile. If an administrator is added to the configuration manager in the future, its definition will also be automatically propogated to the managed servers. System Action: The command succeeded. User Response: None.
Explanation: The command has successfully associated all the domains with the specified profile. All domain definitions will be automatically propogated to managed servers which subscribe to the profile. If a domain is added to the configuration manager in the future, its definition will also be automatically propogated to the managed servers. System Action: The command succeeded. User Response: None. ANR3045I command: Domain domain associated with profile profilename.
ANR3041I
command: Administrator admin associated with profile profilename.
Explanation: The command has successfully associated the administrator with the specified profile. The administrator definition will be automatically propogated to managed servers which subscribe to the profile. System Action: The command succeeded. User Response: None. ANR3042W command: No additional administrators associated with profile profilename.
Explanation: The command has successfully associated the domain with the specified profile. The domain definition will be automatically propogated to managed servers which subscribe to the profile. System Action: The command succeeded. User Response: None. ANR3046W command: No additional domains associated with profile profilename.
Explanation: No additional administrator were associated with the profile. The administrator(s) specified are already associated with the profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY ADMIN command to check which administrators are defined on the server and then reissue to DEFINE PROFASSOCIATION command. The QUERY PROFASSOCIATION FORMAT=DETAILED can be used to see which administrators are already associated with the profile. ANR3043E command: No matching domains found in configuration.
Explanation: No additional domains were associated with the profile. The domain(s) specified are already associated with the profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY DOMAIN command to check which domains are defined on the server and then reissue to DEFINE PROFASSOCIATION command. The QUERY PROFASSOCIATION FORMAT=DETAILED can be used to see which domains are already associated with the profile. ANR3047E command: No matching admin schedules found in configuration.
Explanation: No domain definitions were found on the configuration manager that match the domain(s) specified on the DEFINE PROFASSOCIATION command. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY DOMAIN command to check which domains that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.
Explanation: No admin schedule definitions were found on the configuration manager that match the admin schedule(s) specified on the DEFINE PROFASSOCIATION command. System Action: Server operation continues. The command is not processed. 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.
Chapter 3. Common and Platform Specfic Messages
269
ANR3048I ANR3055E
ANR3048I command: All admin schedules associated with profile profilename. ANR3052I command: All scripts associated with profile profilename.
Explanation: The command has successfully associated all the admin schedules with the specified profile. All admin schedule definitions will be automatically propogated to managed servers which 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. System Action: The command succeeded. User Response: None.
Explanation: The command has successfully 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. System Action: The command succeeded. User Response: None. ANR3053I command: Script script associated with profile profilename.
ANR3049I
command: Admin Schedule admin schedule associated with profile profilename.
Explanation: The command has successfully associated the admin schedule with the specified profile. The admin schedule definition will be automatically propogated to managed servers which subscribe to the profile. System Action: The command succeeded. User Response: None. ANR3050W command: No additional admin scheduless associated with profile profilename.
Explanation: The command has successfully associated the script with the specified profile. The script definition will be automatically propogated to managed servers which subscribe to the profile. System Action: The command succeeded. User Response: None. ANR3054W command: No additional scripts associated with profile profilename.
Explanation: No additional scripts were associated with the profile. The script(s) specified are already associated with the profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY SCRIPT command to 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 found in configuration.
Explanation: No additional admin schedules were associated with the profile. The admin schedule(s) specified are already associated with the profile. System Action: Server operation continues. The command is not processed. 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 associated with the profile. ANR3051E command: No matching scripts found in configuration.
Explanation: No client option set definitions were found on the configuration manager that match the client option set(s) specified on the DEFINE PROFASSOCIATION command. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY CLOPTSET command to check which client option sets that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.
Explanation: No script definitions were found on the configuration manager that match the script(s) specified on the DEFINE PROFASSOCIATION command. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY SCRIPT command to check which scripts that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.
270
IBM Tivoli Storage Manager: Messages
ANR3056I ANR3063E
ANR3056I command: All client option sets associated with profile profilename. ANR3060I command: All servers associated with profile profilename.
Explanation: The command has successfully associated all the client option sets with the specified profile. All client option set definitions will be automatically propogated to managed servers which 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. System Action: The command succeeded. User Response: None.
Explanation: The command has successfully 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. System Action: The command succeeded. User Response: None. ANR3061I command: Server server associated with profile profilename.
ANR3057I
command: Client option set client option set associated with profile profilename.
Explanation: The command has successfully associated the client option set with the specified profile. The client option set definition will be automatically propogated to managed servers which subscribe to the profile. System Action: The command succeeded. User Response: None. ANR3058W command: No additional client option sets associated with profile profilename.
Explanation: The command has successfully associated the server with the specified profile. The server definition will be automatically propogated to managed servers which subscribe to the profile. System Action: The command succeeded. User Response: None. ANR3062W command: No additional servers associated with profile profilename.
Explanation: No additional client option sets were associated with the profile. The client option set(s) specified are already associated with the profile. System Action: Server operation continues. The command is not processed. 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 PROFASSOCIATION FORMAT=DETAILED can be used to see which client option sets are already associated with the profile. ANR3059E command: No matching servers found in configuration.
Explanation: No additional servers were associated with the profile. The server(s) specified are already associated with the profile. System Action: Server operation continues. The command is not processed. 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 found in configuration.
Explanation: No server definitions were found on the configuration manager that match the server(s) specified on the DEFINE PROFASSOCIATION command. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY SERVER command to check which servers that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.
Explanation: No server group definitions were found on the configuration manager that match the server group(s) specified on the DEFINE PROFASSOCIATION command. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY SERVERGROUP command to check which server groups that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.
Chapter 3. Common and Platform Specfic Messages
271
ANR3064I ANR3072I
ANR3064I command: All server groups associated with profile profilename. ANR3068I command: All administrator associations deleted from profile profilename.
Explanation: The command has successfully associated all the server groups with the specified profile. All server group definitions will be automatically propogated to managed servers which 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. System Action: The command succeeded. User Response: None. ANR3065I command: Server group server group associated with profile profilename.
Explanation: The command has successfully deleted all administrators associations from the specified profile. This will automatically delete these administrators from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None. ANR3069I command: Administrator association admin deleted from profile profilename.
Explanation: The command has successfully associated the server group with the specified profile. The server group definition will be automatically propogated to managed servers which subscribe to the profile. System Action: The command succeeded. User Response: None. ANR3066W command: No additional server groups associated with profile profilename.
Explanation: The command has successfully deleted an administrator association from the specified profile. This will automatically delete this administrator from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None. ANR3070E command: No matching domains associated with profile profile.
Explanation: No matching domain definitions are associated with the specified specified profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY PROFASSOCIATION command to check which domains are associated with the profile and then reissue to DELETE PROFASSOCIATION command. ANR3071I command: All domain associations deleted from profile profilename.
Explanation: No additional server groups were associated with the profile. The server group(s) specified are already associated with the profile. System Action: Server operation continues. The command is not processed. 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 PROFASSOCIATION FORMAT=DETAILED can be used to see which server groups are already associated with the profile. ANR3067E command: No matching administrators associated with profile profile.
Explanation: The command has successfully deleted all domains associations from the specified profile. This will automatically delete these domains from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None. ANR3072I command: Domain association domain deleted from profile profilename.
Explanation: No matching administrator definitions are associated with the specified specified profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY PROFASSOCIATION command to check which administrators are associated with the profile and then reissue to DELETE PROFASSOCIATION command.
Explanation: The command has successfully deleted a domain association from the specified profile. This will automatically delete this domain from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None.
272
IBM Tivoli Storage Manager: Messages
ANR3073E ANR3082E
ANR3073E command: No matching admin schedules associated with profile profile. User Response: None. ANR3078I command: Script association script deleted from profile profilename.
Explanation: No matching admin schedule definitions are associated with the specified specified profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY PROFASSOCIATION command to check which admin schedules are associated with the profile and then reissue to DELETE PROFASSOCIATION command. ANR3074I command: All admin schedule associations deleted from profile profilename.
Explanation: The command has successfully deleted a script association from the specified profile. This will automatically delete this script from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None. ANR3079E command: No matching client option sets associated with profile profile.
Explanation: The command has successfully deleted 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. System Action: The command succeeded. User Response: None. ANR3075I command: Admin schedule association admin schedule deleted from profile profilename.
Explanation: No matching clent option set definitions are associated with the specified specified profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY PROFASSOCIATION command to check which client option sets are associated with the profile and then reissue to DELETE PROFASSOCIATION command. ANR3080I command: All client option set associations deleted from profile profilename.
Explanation: The command has successfully deleted an admin schedule association from the specified profile. This will automatically delete this admin schedule from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None. ANR3076E command: No matching scripts associated with profile profile.
Explanation: The command has successfully deleted 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. System Action: The command succeeded. User Response: None. ANR3081I command: Client option set association client option set deleted from profile profilename.
Explanation: No matching script definitions are associated with the specified specified profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY PROFASSOCIATION command to check which scripts are associated with the profile and then reissue to DELETE PROFASSOCIATION command. ANR3077I command: All script associations deleted from profile profilename.
Explanation: The command has successfully deleted a client option set association from the specified profile. This will automatically delete this client option set from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None. ANR3082E command: No matching servers associated with profile profile.
Explanation: The command has successfully deleted all scripts associations from the specified profile. This will automatically delete these scripts from the managed servers that are subscribed to this profile. System Action: The command succeeded.
Explanation: No matching server definitions are associated with the specified specified profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY PROFASSOCIATION
Chapter 3. Common and Platform Specfic Messages
273
ANR3083I ANR3091E
command to check which servers are associated with the profile and then reissue to DELETE PROFASSOCIATION command. ANR3083I command: All server associations deleted from profile profilename. ANR3088W This command will cause the deletion of objects on any managed server subscribed to profile profile name.
Explanation: The command has successfully deleted all servers associations from the specified profile. This will automatically delete these servers from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None. ANR3084I command: Server association server deleted from profile profilename.
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. System Action: The system asks whether you wish to continue with the command. 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 command has successfully deleted a server association from the specified profile. This will automatically delete this server definition from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None. ANR3085E command: No matching server groups associated with profile profile.
Explanation: The specified command failed while attempting to communicate with the indicated server. System Action: Server operation continues. The command is not processed. 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 configuration manager.
Explanation: No matching server group definitions are associated with the specified specified profile. System Action: Server operation continues. The command is not processed. User Response: Use the QUERY PROFASSOCIATION command to check which server groups are associated with the profile and then reissue to DELETE PROFASSOCIATION command. ANR3086I command: All server group associations deleted from profile profilename.
Explanation: The specified command failed because it tried to contact the specified server, and discovered that the server is not a configuration manager. System Action: Server operation continues. The command is not processed. User Response: Reissue the command and specify a correct configuration manager name. ANR3091E command: Profile list not specified.
Explanation: The command has successfully deleted all server groups associations from the specified profile. This will automatically delete these server groups from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None. ANR3087I command: Server group association server group deleted from profile profilename.
Explanation: The specified command failed because you did not specify a profile list on the command. System Action: Server operation continues. The command is not processed. User Response: Reissue the command specifying a profile list.
Explanation: The command has successfully deleted a server group association from the specified profile. This will automatically delete this server group from the managed servers that are subscribed to this profile. System Action: The command succeeded. User Response: None.
274
IBM Tivoli Storage Manager: Messages
ANR3092I ANR3156E
ANR3092I command: Subscriber notification processing has begun. ANR3152I Configuration refresh started with configuration manager server name.
Explanation: A NOTIFY SUBSCRIBER process has begun. The managed server(s) are being contacted, asking them to immediately perform a configuration refresh. System Action: Server operation continues. The command succeeded. User Response: None. ANR3093I command: No matching profiles or subscriptions were found.
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. User Response: None. ANR3153I Configuration refresh ended successfully with configuration manager server name.
Explanation: No subscriptions were found for the profiles specified. Either the profiles do not exist, or there are no subscriptions to the profiles. System Action: Server operation continues. The command is not processed. 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: 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. User Response: None. ANR3154E Communication error on notify to managed server server name. Will retry in minutes minutes.
Explanation: While receiving configuration information from the specified configuration manager, processing failed because of a communications error. System Action: Server operation continues. The configuration refresh process was stopped and will be automatically retried. User Response: Perhaps the configuration manager is not active. If the problem continues, contact the administrator for the configuration manager, or contact a network administrator. The refresh will automatically retry several times and then give up until the configuration refresh interval is reached again. ANR3151E Configuration refresh failed with configuration manager server name.
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 receiving configuration information from the specified configuration manager, processing failed. System Action: Server operation continues. The 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.
Explanation: While sending configuration information to the specified managed server, processing failed. System Action: Server operation continues. The configuration refresh process ended. User Response: Examine the activity log of both the
Chapter 3. Common and Platform Specfic Messages
275
ANR3157I ANR3163E
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. ANR3160E Unable to receive confirmation of refresh from managed server server name.
Explanation: While sending configuration information to the specified managed server, a communication error occurred when trying to receive confirmation from the managed server that information was processed successfully. System Action: Server operation continues. Configuration refresh processing ended. User Response: Determine if communication can be established with the managed server by using the server PING command. Use the NOTIFY SUBSCRIBERS command to force the configuration refresh to retry. ANR3161E Premature end of configuration refresh for managed server 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. User Response: None. 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. System Action: Server processing continues. User Response: None. ANR3159E Managed server server name has newer version for profile profile name.
Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of on error. System Action: Server operation continues. Configuration refresh processing ended. User Response: Examine the activity log on the managed server for any error messages that might explain why the refresh failed. Use the NOTIFY SUBSCRIBERS command on the configuration manager to force the configuration refresh to retry. ANR3162E Managed server server name aborted configuration refresh processing due to a low memory condition.
Explanation: While sending configuration information 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.
Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of a low memory condition on the managed server. System Action: Server operation continues. Configuration refresh processing ended. User Response: Make more memory available to the managed server. ANR3163E Managed server server name aborted configuration refresh processing due to an internal error.
Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of an internal error on the managed server. System Action: Server operation continues. Configuration refresh processing ended. User Response: Examine the activity log of the managed server for messages that explain the cause of the internal error.
276
IBM Tivoli Storage Manager: Messages
ANR3164E ANR3171E
ANR3164E Managed server server name aborted configuration refresh processing due to a lock conflict. ANR3168E Configuration manager server name aborted configuration refresh processing due to an internal error.
Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of a lock conflict on the managed server. System Action: Server operation continues. Configuration refresh processing ended. User Response: Use the NOTIFY SUBSCRIBERS command to retry the configuration refresh. If this problem persists, contact your service representative. ANR3165E Managed server server name aborted configuration refresh processing due to a protocol error.
Explanation: While receiving configuration information from the specified configuration manager, processing ended prematurely because of an internal error on the configuration manager. System Action: Server operation continues. Configuration refresh processing ended. User Response: Examine the activity log of the configuration manager for messages that explain the cause of the internal error. ANR3169E Configuration manager server name aborted configuration refresh processing due to a lock conflict.
Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of a protocol error detected on the managed server. System Action: Server operation continues. Configuration refresh processing ended. User Response: Use the NOTIFY SUBSCRIBERS command to retry the configuration refresh. If this problem persists, contact your service representative. ANR3166E Unable to receive configuration refresh information from server server name.
Explanation: While receiving configuration information from the specified managed server, processing ended prematurely because of a lock conflict on the configuration manager. System Action: Server operation continues. Configuration refresh processing ended. User Response: Retry the configuration refresh by issuing the SET CONFIGREFRESH command (using the current refresh interval value). If this problem persists, contact your service representative. ANR3170E Configuration manager server name aborted configuration refresh processing due to a protocol error.
Explanation: While receiving configuration information from the specified configuration manager, processing ended prematurely because of a communications error. System Action: Server operation continues. Configuration refresh processing ended. 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.
Explanation: While receiving configuration information from the specified configuration manager, processing ended prematurely because of a protocol error detected on the configuration manager. System Action: Server operation continues. Configuration refresh processing ended. User Response: Retry the configuration refresh by issuing the SET CONFIGREFRESH command (using the current refresh interval value). If this problem persists, contact your service representative. ANR3171E Configuration refresh with configuration manager server name had to skip processing for one or more objects.
Explanation: While receiving configuration information from the specified configuration manager, processing ended prematurely because of a low memory condition on the configuration manager. System Action: Server operation continues. Configuration refresh processing ended. User Response: Notify the administrator of the configuration manager.
Explanation: While receiving configuration information from the specified configuration manager, it became necessary to skip the creation or deletion of one or more objects. System Action: Server operation continues. Configuration refresh processing ended. User Response: Examine the managed servers
Chapter 3. Common and Platform Specfic Messages
277
ANR3172W ANR3200E
activity log for earlier messages that identfy the object, and take the actions identified in those messages. Configuration refresh processing will not complete successfully until the problem is clear up. ANR3172W Subscription exists for deleted profile profile name. System Action: Server operation continues. The 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 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. System Action: Server operation continues. 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.
Explanation: While receiving configuration refresh information from the specified managed server, it was detected that a subscribed-to profile is locked. System Action: Server operation continues. Refresh processings skips over this profile. User Response: Normally, the profile will later be unlocked automatically, or by an administrator. If you think that it should not be locked, have ask the configuration manager admin to unlock it using the UNLOCK PROFILE command. ANR3176W Profile profile name is locked and could not be refreshed for managed server server name.
Explanation: While sending configuration refresh information to the specified managed server, it was detected that a subscribed-to profile is locked. System Action: Server operation continues. Refresh 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 profile profile name.
Explanation: While receiving configuration 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. 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. ANR3174E Communication error with managed server server name.
Explanation: While receiving configuration refresh information from the configuration manager, an object was received that is not supported on this managed server. System Action: Server operation continues. Refresh 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.
Explanation: While receiving or sending information to the specified managed server, a communcations error was experienced.
Explanation: The specified command cannot be executed because it would alter the contents of the
278
IBM Tivoli Storage Manager: Messages
ANR3201E ANR3208E
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. System Action: The command fails and server operation continues. User Response: None. ANR3201E command: Domain domain name is a managed object and cannot be deleted. ANR3205E command: Management class class name in domain domain name, policy set set name is a managed object and cannot be deleted.
Explanation: The indicated management class is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated. ANR3206E command: Management class class name in domain domain name, policy set set name is a managed object and cannot be updated.
Explanation: The indicated domain is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated. ANR3202E command: Domain domain name is a managed object and cannot be updated.
Explanation: The indicated management class is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated. ANR3207E command: Backup copy group group name in domain domain name, policy set set name, management class class name is a managed object and cannot be deleted.
Explanation: The indicated domain is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated. 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 object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated. ANR3204E command: Policy set set name in domain domain name is a managed object and cannot be updated.
Explanation: The indicated backup copy group is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated. ANR3208E command: Archive copy group group name in domain domain name, policy set set name, management class class name is a managed object and cannot be deleted.
Explanation: The indicated policy set is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.
Explanation: The indicated archive copy group is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.
Chapter 3. Common and Platform Specfic Messages
279
ANR3209E ANR3216W
ANR3209E command: Backup copy group group name in domain domain name, policy set set name, management class class name is a managed object and cannot be updated. ANR3213E command: Administrative schedule schedule name is a managed object and cannot be deleted.
Explanation: The indicated backup copy group is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated. ANR3210E command: Archive copy group group name in domain domain name, policy set set name, management class class name is a managed object and cannot be updated.
Explanation: The indicated administrative schedule is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this object, you can delete the subscription to the configuration profiles with 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 archive copy group is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated. ANR3211E command: Client schedule schedule name in domain domain name is a managed object and cannot be deleted.
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. System Action: The command fails and server operation continues. User Response: To update this object, you can delete the subscription to the configuration profiles with which the object is associated. ANR3215W Managed domain domain name contains at least one node and cannot be discarded.
Explanation: The indicated client schedule is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated. ANR3212E command: Client schedule schedule name in domain domain name is a managed object and cannot be updated.
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.
Explanation: The indicated client schedule is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.
Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with 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.
280
IBM Tivoli Storage Manager: Messages
ANR3217E ANR3224E
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. ANR3221E command: Administrator administrator name is a managed object - authority cannot be revoked.
Explanation: The indicated administrator is a managed object. Authority of this administrator cannot be revoked on the managed server. System Action: The command fails and server operation continues. User Response: To revoke authority of this administrator, you can delete the subscription to the configuration profiles with which the object is associated. ANR3222W Managed administrator administrator name is the only system administrator and cannot be discarded.
Explanation: The indicated administrator is a managed object and cannot be removed on the managed server. System Action: The command fails and server operation continues. User Response: To remove this administrator, you can delete the subscription to the configuration profiles with which the object is associated. ANR3218E command: Administrator administrator name is a managed object and cannot be updated.
Explanation: The indicated administrator is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this administrator, you can delete the subscription to the configuration profiles with which the object is associated. ANR3219E command: Administrator administrator name is a managed object and cannot be renamed.
Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with 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 Managed administrator administrator name is currently accessing the server and cannot be discarded.
Explanation: The indicated administrator is a managed object and cannot be renamed on the managed server. System Action: The command fails and server operation continues. User Response: To rename this administrator, you can delete the subscription to the configuration profiles with which the object is associated. ANR3220E command: Administrator administrator name is a managed object - authority cannot be granted.
Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with DISCARDOBJECTS=YES. The indicated administrator cannot be discarded on the managed server because it has an active session with the server. System Action: Administrator administrator name is not deleted. User Response: Quit or cancel all sessions for this administrator before discarding the administrator definition. ANR3224E command: Command script command script name is a managed object and cannot be deleted.
Explanation: The indicated administrator is a managed object. Authority cannot be granted to this administrator on the managed server. System Action: The command fails and server operation continues. User Response: To grant authority to this administrator, you can delete the subscription to the configuration profiles with which the object is associated.
Explanation: The indicated command script is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this script, you can delete the subscription to the configuration profiles with which the object is associated.
Chapter 3. Common and Platform Specfic Messages
281
ANR3225E ANR3234E
ANR3225E command: Command script command script name is a managed object and cannot be updated. System Action: The command fails and server operation continues. User Response: None. ANR3230E command: Server group group name is a managed object and cannot be deleted.
Explanation: The indicated command script is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this script, you can delete the subscription to the configuration profiles with which the object is associated. ANR3226E command: Command script command script name is a managed object and cannot be renamed.
Explanation: The indicated server group is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this server group, you can delete the subscription to the configuration profiles with which the object is associated. ANR3231E command: Server group group name is a managed object and cannot be updated.
Explanation: The indicated command script is a managed object and cannot be renamed on the managed server. System Action: The command fails and server operation continues. User Response: To rename this script, you can delete the subscription to the configuration profiles with which the object is associated. ANR3227E command: Option set optionset name is a managed object and cannot be deleted.
Explanation: The indicated server group is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this server group, you can delete the subscription to the configuration profiles with which the object is associated. ANR3232E command: Server group group name is a managed object and cannot be renamed.
Explanation: The indicated option set is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues. User Response: To delete this option set, you can delete the subscription to the configuration profiles with which the object is associated. ANR3228E command: Option set optionset name is a managed object and cannot be updated.
Explanation: The indicated server group is a managed object and cannot be renamed on the managed server. System Action: The command fails and server operation continues. User Response: To rename this server group, you can delete the subscription to the configuration profiles with which the object is associated. ANR3233E command: Command cannot be executed - server group group name is a managed object.
Explanation: The indicated option set is a managed object and cannot be updated on the managed server. System Action: The command fails and server operation continues. User Response: To update this option set, you can delete the subscription to the configuration profiles with which the object is associated. ANR3229E command: Command cannot be executed - option set optionset name is a managed object.
Explanation: The specified command cannot be executed because it would alter the membership of the indicated managed server group. System Action: The command fails and server operation continues. User Response: None. ANR3234E command: Server server name is a managed object and cannot be deleted.
Explanation: The specified command cannot be executed because it would alter the contents of the indicated managed option set.
Explanation: The indicated server is a managed object and cannot be deleted on the managed server. System Action: The command fails and server operation continues.
282
IBM Tivoli Storage Manager: Messages
ANR3235E ANR3350W
User Response: To delete this object, you can delete the subscription to the configuration profiles with which the object is associated. ANR3235E command: Server server name is a managed object - one or more specified attributes cannot be updated. ANR3238E command: This object cannot be renamed because it is associated with one or more configuration profiles.
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. System Action: The command fails and server operation continues. 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 configuration profiles with which the object is associated, so that the server is no longer a managed object. ANR3236W Server server name is currently in use and cannot be discarded.
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. System Action: The command fails and server operation continues. 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. System Action: The command fails. 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 configuration manager.
Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with 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 and cannot be discarded.
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 which domain domain name is associated.
Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with 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. User Response: Before server name can be deleted, the DELETE EVENTSERVER command must be used to remove the event server reference to server name.
Chapter 3. Common and Platform Specfic Messages
283
ANR3351W ANR3357I
ANR3351W Managed domain domain name contains at least one node and cannot be deleted during configuration refresh processing. System Action: Refresh processing continues, but this administrative schedule is not replaced. The system will attempt to replace the local administrative schedule during later configuration refresh operations. User Response: If you want this administrative schedule to be replaced with the schedule definition from the configuration manager, deactivate the local schedule using the Update Schedule command. After the administrative schedule definition has successfully been propagated from the configuration manager, you can activate the new schedule. Alternatively, if you want to prevent further attempts to replace the local schedule definition during configuration refresh processing, delete the subscription to the profiles with which the schedule name is associated. ANR3355W Managed administrative schedule schedule name is active 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. System Action: Refresh processing continues, but this 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.
Explanation: 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 configuration manager. System Action: None. User Response: None. ANR3353I Managed domain domain name deleted during configuration refresh processing.
Explanation: During configuration refresh processing, the enterprise configuration facility attempted to 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. System Action: Refresh processing continues, but this 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 processing, delete the subscription to the profiles with which the schedule name is associated. ANR3356I Locally defined administrative schedule schedule name replaced during configuration refresh processing.
Explanation: During configuration refresh processing, 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. System Action: None. User Response: None. ANR3354W Locally defined administrative schedule schedule name is active and cannot be replaced with a definition from the configuration manager.
Explanation: During configuration refresh processing, a local administrative schedule definition was replaced with a definition from the configuration manager. System Action: None. User Response: None. ANR3357I Managed administrative schedule schedule name deleted during configuration refresh processing.
Explanation: During configuration refresh processing 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.
Explanation: During configuration refresh processing, the indicated managed administrative schedule was
284
IBM Tivoli Storage Manager: Messages
ANR3358W ANR3363W
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. System Action: None. User Response: None. ANR3358W Locally defined administrator administrator name is the only system administrator and cannot be replaced with a definition from the configuration manager. ANR3360W Managed system administrator administrator name is the only system administrator - authority cannot be revoked during configuration refresh processing.
Explanation: 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 configuration refresh processing.
Explanation: During configuration refresh processing 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. System Action: Refresh processing continues, but this 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 processing, delete the subscription to the profiles with which administrator administrator name is associated. ANR3359W Managed system administrator administrator name is the only system administrator and cannot be deleted during configuration refresh processing.
Explanation: During configuration refresh processing, a local administrator definition was replaced with a definition from the configuration manager. System Action: None. User Response: None. ANR3362I Managed administrator administrator name deleted during configuration refresh processing.
Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated administrator because it has been deleted from the configuration manager or because the profile association no longer exists. The administrator could not be deleted on the managed server because it is the only system administrator. System Action: Refresh processing continues, but this 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.
Explanation: During configuration refresh processing, the indicated managed administrator was removed from the managed server. This occurred either because the administrator has been deleted from the configuration manager or because the profile association no longer exists. System Action: None. User Response: None. ANR3363W Managed administrator administrator name is currently accessing the server and cannot be deleted during configuration refresh processing.
Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated administrator because it has been deleted from the configuration manager or because the profile association no longer exists. The administrator could not be deleted on the managed server because it currently has an active session with the server.
Chapter 3. Common and Platform Specfic Messages
285
ANR3364W ANR3371W
System Action: Refresh processing continues, but this 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. ANR3367I Locally defined option set option set name replaced during configuration refresh processing.
Explanation: During configuration refresh processing, a local option set definition was replaced with a definition from the configuration manager. System Action: None. User Response: None. ANR3368I Managed option set option set name deleted during configuration refresh processing.
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. User Response: 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. ANR3365I Locally defined command script command script name replaced during configuration refresh processing.
Explanation: During configuration refresh 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 manager or because the profile association no longer exists. System Action: None. User Response: None. ANR3369I Locally defined server group group name replaced during configuration refresh processing.
Explanation: During configuration refresh processing, a local server group definition was replaced with a definition from the configuration manager. System Action: None. User Response: None. ANR3370I Managed server group group name deleted during configuration refresh processing.
Explanation: During configuration refresh processing, a local command script definition was replaced with a definition from the configuration manager. System Action: None. User Response: None. ANR3366I Managed command script command script name deleted during configuration refresh processing.
Explanation: 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 manager or because the profile association no longer exists. System Action: None. User Response: None. ANR3371W Server group group name cannot be defined during configuration refresh processing because a server already exists with this name.
Explanation: 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 manager or because the profile association no longer exists. System Action: None. User Response: None.
Explanation: During configuration refresh processing, 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
286
IBM Tivoli Storage Manager: Messages
ANR3372I ANR3377W
definition with the same name already exists on the managed server. System Action: Refresh processing continues, but this 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 replaced during configuration refresh processing. 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: Refresh processing continues, but this server definition is not deleted. The system will attempt to delete the server during later configuration refresh operations. 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. ANR3376W Server server name is the event server and cannot be deleted during configuration refresh processing.
Explanation: During configuration refresh processing, a local server definition was replaced with a definition from the configuration manager. System Action: None. User Response: None. ANR3373I Server server name deleted during configuration refresh processing.
Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated server definition because it has been deleted from the configuration manager or because the profile association no longer exists. The indicated server could not be deleted on the managed server because it is the event server for the managed server. System Action: Refresh processing continues, but this server definition is not deleted. The system will attempt to delete the server during later configuration refresh operations. User Response: Before server name can be deleted, the 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.
Explanation: During configuration refresh processing, the definition for managed object server name was removed from the managed server. This occurred either because server name has been deleted from the configuration manager or because the profile association no longer exists. System Action: None. User Response: None. ANR3374I Server group group name replaced with server server name during configuration refresh processing.
Explanation: During configuration refresh processing, a server group definition was replaced with a server definition from the configuration manager. The server has the same name as the deleted server group. System Action: None. User Response: None. ANR3375W Server server name is currently in use cannot be deleted during configuration refresh processing.
Explanation: During configuration refresh processing, the enterprise configuration facility attempted to 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. System Action: Refresh processing continues, but this 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.
Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated server definition because it has been deleted from the configuration manager or because the profile association no longer exists. The indicated server could not be deleted on the managed
Chapter 3. Common and Platform Specfic Messages
287
ANR3470I ANR3478E
ANR3470I Command: Auditing enterprise configuration definitions. ANR3474I Audit command: Enterprise configuration global attribute(s) are incorrect attributes will be corrected using available database information or default values.
Explanation: The server has started to audit database definitions used by the enterprise configuration facility. System Action: Server database audit operation continues. User Response: None. ANR3471E Audit command: Enterprise configuration global attributes are missing.
Explanation: A database audit process finds that global attributes used by the enterprise configuration 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. System Action: Audit processing continues. 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. ANR3475E Audit command: Extraneous profile information found.
Explanation: A database audit process finds that the global attributes used by the enterprise configuration facility are missing. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES specified so that the enterprise configuration global attributes can be recreated. ANR3472I Audit command: Enterprise configuration global attributes are missing - attributes will be recreated using available database information or default values.
Explanation: A database audit process finds extraneous configuration profile information. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the information is deleted. ANR3476E Audit command: Extraneous profile information found - information will be deleted.
Explanation: A database audit process finds that the global attributes used by the enterprise configuration 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. System Action: Audit processing continues. 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 Audit command: Enterprise configuration global attribute(s) are incorrect.
Explanation: A database audit process finds extraneous configuration profile information. Because FIX=YES has been specified for the audit command, the extraneous information will be deleted. System Action: Audit processing continues. User Response: None. ANR3477E Audit command: Profile information is inconsistent.
Explanation: A database audit process finds that global attributes used by the enterprise configuration facility are incorrect. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES specified so that the enterprise configuration global attributes can be corrected.
Explanation: A database audit process detects inconsistent configuration profile information. This information can be corrected. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the information can be corrected. ANR3478E Audit command: Profile information is inconsistent - it will be corrected.
Explanation: A database audit process detects inconsistent configuration profile information. Because FIX=YES has been specified for the audit command, the information will be corrected.
288
IBM Tivoli Storage Manager: Messages
ANR3479E ANR3502W
System Action: Audit processing continues. User Response: None. ANR3479E Audit command: Profile association information is missing. ANR3484E Audit command: Profile subscription information is inconsistent - it will be corrected.
Explanation: A database audit process detects missing profile association information. This information can be recreated. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the information can be recreated. ANR3480E Audit command: Profile association information is missing - it will be recreated.
Explanation: A database audit process detects inconsistent profile subscription information. Because FIX=YES has been specified for the audit command, the information will be corrected. System Action: Audit processing continues. User Response: None. ANR3485E Audit command: Profile subscriptions were found to more than one configuration manager.
Explanation: A database audit process detects missing profile association information. Because FIX=YES has been specified for the audit command, the information will be recreated. System Action: Audit processing continues. User Response: None. ANR3481E Audit command: Extraneous profile association information found.
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. System Action: Audit processing continues. 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 being generated.
Explanation: A database audit process finds extraneous profile association information. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the information is deleted. ANR3482E Audit command: Extraneous profile association information found information will be deleted.
Explanation: The named object set is being created for the specified node. System Action: The server generates a backup set. User Response: None. ANR3501I Backup set for node name as set name completed successfully - processed files files.
Explanation: A database audit process finds extraneous profile association information. Because FIX=YES has been specified for the audit command, the extraneous information will be deleted. System Action: Audit processing continues. User Response: None. ANR3483E Audit command: Subscription information is inconsistent.
Explanation: The named object set was successfully created for the specified node. The number of files processed is specified. System Action: None. User Response: None. ANR3502W Backup set for node name as set name completed with file processing errors processed files files with error files files skipped.
Explanation: A database audit process detects inconsistent profile subscription information. This information can be corrected. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the information can be corrected.
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. System Action: None. User Response: Evaluate other server messages for an
Chapter 3. Common and Platform Specfic Messages
289
ANR3503E ANR3511E
indication of why the files where skipped. Files can be skipped because of failures locking those files, having no files to process, or for other more serious problems. First, retry the command and see if it completes without any skipped files. If you are unable to generate the backup set without skipping files, please contact your local service representative for assistance. ANR3503E Generation of backup set for node name as set name failed. ANR3507I Cancel in progress
Explanation: This message is displayed in response to 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 operation continues. User Response: None. ANR3508W Generation of backup set for node name as set name failed - no filespaces to process.
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. System Action: Server operation continues. 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.
Explanation: The named object for the specified node was not created. No filespaces were available to process. System Action: Server operation continues. 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 Command: Error encountered in accessing data storage - device class device class name is not defined.
Explanation: During command command processing, an error occurred because the specified device class is not defined. System Action: The command command is ended and server operation continues. User Response: Make sure the specified device class is defined. ANR3510E Command: Error encountered in accessing data storage - disk volume specified.
Explanation: The named object for the specified node 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. System Action: Server operation continues. 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 Backup set for node name as set name used volume volume name.
Explanation: During command command processing, an error occurred because a specified volume is a disk volume rather than a tape volume. System Action: The command command is ended and server operation continues. User Response: Make sure that all volumes specified for the command command are tape volumes. ANR3511E Command: Error encountered in accessing data storage - invalid volume name specified.
Explanation: The named object for the specified node used the specified volume. System Action: Server operation continues. User Response: None.
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. System Action: The command command operation is ended and server operation continues.
290
IBM Tivoli Storage Manager: Messages
ANR3512E ANR3519E
User Response: Issue the command with a valid volume name. ANR3512E Command: Error encountered in accessing data storage - insufficient number of mount points available for removable media. defined in a storage pool, and that has not been previously used for an export, database dump, or database backup operation as recorded in the server volume history information. Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export, database dump, or database backup operations. ANR3516E Command: Out of space on sequential media, scratch media could not be mounted.
Explanation: During command command processing, the server cannot allocate sufficient mount points. System Action: The command command operation is ended and server operation continues. User Response: If necessary, make more mount points available. ANR3513E Command: Output error encountered in accessing data storage.
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. System Action: The command command operation ends and server operation continues. User Response: Query the activity log to find messages preceding this one to determine the cause of the error. After the problem is corrected, the command can be retried. ANR3514E Command: Data transfer was interrupted in accessing data storage.
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. ANR3517E Command: Error encountered in accessing 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. System Action: The command command operation is ended and server operation continues. User Response: Issue the command again and make sure the necessary volumes are accessible. ANR3518I Command: Processing canceled before completion.
Explanation: The database transaction associated with command command operation failed because data transfer to or from data storage was interrupted by an external event. System Action: The command command operation is ended and server operation continues. User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Reissue the command command after the problem is resolved. ANR3515E Command: Error encountered in accessing data storage - volume already in use.
Explanation: The background process to service the command command has been canceled with the CANCEL PROCESS command. System Action: Processing for the command command ends. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message. User Response: None. ANR3519E Command: Insufficient memory available in accessing data storage.
Explanation: During command command processing, a 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. System Action: The command command operation is ended and server operation continues. User Response: Specify a volume that is not in use or
Explanation: The server encounters a memory shortage in accessing data storage during command command operation.
Chapter 3. Common and Platform Specfic Messages
291
ANR3520E ANR3526E
System Action: The command command operation ends and server operation continues. 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. ANR3520E Command: Internal error encountered in accessing data storage. The object for which the I/O was issued is reported in a later message. System Action: Backup set processing skips this file, and continues operation. User Response: Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down with the HALT command to correct the hardware problem. ANR3524W Backup set command: Transaction failed data transfer interrupted.
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. ANR3521W BackupSet command: Data storage retrieve or restore failed - data integrity error detected.
Explanation: The database transaction associated with 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 server operation continues. User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the backup set operation again after problem is resolved. ANR3525W Backup set command: Transaction failed storage media inaccessible.
Explanation: The server ends an backup set operation because an internal database integrity error has been encountered on the server. System Action: The server ends the backup set operation and continues operation. User Response: Contact your service representative. ANR3522W Command: Retrieve or restore failed - file was deleted from data storage during retrieval.
Explanation: The server ends a transaction for an backup set 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 backup set operation and server operation continues. User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage. ANR3526E Backup set command: Error encountered in accessing data storage - volume cannot be used.
Explanation: The server ends a file retrieval operation for the specified command because the file has been deleted from data storage by another process before retrieval is complete. System Action: The server ends the command and continues operation. 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 command after these processes have been completed or canceled. ANR3523W Backup set command: Retrieve failed error on input storage device.
Explanation: During backup set processing, a volume has been mounted but cannot be used. System Action: The backup set operation is ended and server operation continues. User Response: Query the activity log for messages preceding this one that give additional information. Make sure a usable volume is specified and mounted.
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.
292
IBM Tivoli Storage Manager: Messages
ANR3527E ANR3534E
ANR3527E Backup set command operation terminated - it is acting on an empty volume or volume content is not as expected. ANR3530E Audit command: A missing, incorrect, or, invalid collocation group has been detected.
Explanation: The volume content it is acting on not as expected or it is an empty volume System Action: The command operation is ended. User Response: Issue the command again and make sure the expected content is in the volumes or the volume is not empty. ANR3528E Backup set command: Media not accessible in accessing data storage.
Explanation: A database audit process found a missing, incorrect, or invalid collocation group. System Action: Audit processing continues. 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: 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. System Action: The server ends the backup set operation and server operation continues. User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage. ANR3529W Generate backupset 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: A database audit process found a missing, incorrect, or invalid collocation group. Because FIX=YES has been specified for the audit command, the error will be corrected. System Action: Audit processing continues. User Response: None. ANR3532E Audit command: Missing or incorrect 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. System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES so that the error can be corrected. ANR3533E Audit command: Missing or incorrect collocation group id detected for collocation group name - it will be corrected.
Explanation: During generate backupset 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 integrity error was detected for some other file within the aggregate. System Action: The damaged file is not added to the backupset. 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 the file is reset to the undamaged state and it is important that the file be included in the backupset, rerun the generate backupset command. If, however, the audit does not clear the damaged state of the file and 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. If it is still important that the file be included in the backupset, rerun the generate backupset command.
Explanation: A database audit process detects missing or incorrect information for a collocation group. Because FIX=YES has been specified for the audit command, the error will be corrected. System Action: Audit processing continues. User Response: None. ANR3534E 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. System Action: Audit processing continues. User Response: Issue the audit command again, and specify FIX=YES so that the error can be corrected.
Chapter 3. Common and Platform Specfic Messages
293
ANR3535E ANR3601W
ANR3535E Audit command: Missing or incorrect collocation group name has been detected for collocation group id collocation group id - it will be corrected. ANR3541E Error error code occurred opening object set set node:set name for session session number, node.
Explanation: A database audit process detects missing or incorrect information for a collocation group. Because FIX=YES has been specified for the audit command, the error will be corrected. System Action: Audit processing continues. User Response: None. ANR3536E Audit command: Inconsistent information detected in collocation group (Aggregate.ID).
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 Error error code occurred reading object set set node:set name for session session number, node.
Explanation: An error occurred while reading the indicated object set. System Action: An error is returned to the client. User Response: Correct the problem reported by previous messages, if possible. ANR3543E Error error code occurred while sending entries from object set set node:set name for session session number, node.
Explanation: A database audit process finds inconsistent information for a collocation group. This problem cannot be corrected by the audit process. System Action: Audit processing continues. User Response: Contact your service representative. ANR3537E Audit command: A missing or incorrect collocation group member has been detected for collocation group ID collocation group ID.
Explanation: An error occurred while sending entries for the indicated object set. System Action: An error is returned to the client. User Response: Correct the problem reported by other prior or subsequent messages related to this session, and try the operation again. ANR3550E Definition of backup set set name for node name failed because it has an unknown format.
Explanation: A database audit process detects a missing or incorrect member for a collocation group. System Action: Audit processing continues. User Response: Issue the audit command again, and specify FIX=YES so that the error can be corrected. ANR3538E Audit command: A missing or incorrect 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. Because FIX=YES has been specified for the audit command, the error will be corrected. System Action: Audit processing continues. User Response: None. ANR3540E Object set set node:set name was not found for session session number, node.
Explanation: The named object for the specified node 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. System Action: Server operation continues. 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 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. User Response: None.
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.
294
IBM Tivoli Storage Manager: Messages
ANR3602E ANR3608E
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. 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 was attempting to communicate with the database server but was unable to do so. System Action: The storage agent operation fails. User Response: Check the configuration of the storage agent and server to ensure that communication parameters are correct. Ensure that the database server is running and is accepting messages. ANR3603E Storage AgentStorage Agent name was unable to load policy information due to a protocol error.
Explanation: 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. User Response: Check the configuration of the storage agent and server to ensure that communication parameters are correct. If this problem persists, contact your service representative. ANR3607E The storage agent was communicating with the client on a restore request with verb verb name and received return code return code.
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 service representative. ANR3604E This command is not supported in the current operating environment.
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. System Action: Database server and storage agent continue. The restore request fails, but may be retried by the client. User Response: Check the configuration of the storage agent and client to ensure that communication parameters are correct. If this problem persists, contact your service representative. ANR3608E The storage agent was communicating with the database server on a restore request. An unexpected request (id verb ) was received from the database server.
Explanation: A command was issued that is valid under most circumstances, but not in the current server environment. System Action: Server operation continues. 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. User Response: Check the configuration of the storage agent and server to ensure that communication parameters are correct.
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. System Action: Database server and storage agent continue. The restore request may fail, but may be retried by the client. User Response: If this problem persists, contact your service representative.
Chapter 3. Common and Platform Specfic Messages
295
ANR3609E ANR4003I
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. ANR3999E Failure validating database load: expected numRecs records and numBV bit vectors - loaded actNumRecs records and actNumBV bit vectors.
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. System Action: Database server and storage agent 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, contact your service representative. ANR3610I Domain Identifier domain identifier was not found.
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 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 sesulting 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 server was cleaning up cached policy information after a restore request. A domain with the indicated identifier was not found in an internal list. System Action: Database server and storage agent 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, contact your service representative. ANR3611E Storage Agent unable to contact server.
Explanation: The database dump process has started. System Action: The server dumps the contents of the database to a file or removable media. User Response: None. ANR4001I Dump command: Database dump process completed.
Explanation: The database dump process has ended. System Action: The server completes processing. User Response: None. ANR4002I Dump command: Database dump process terminated due to error (error indicator).
Explanation: The storage agent was attempting to 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.
Explanation: The database dump process has ended prematurely due to an error. System Action: The server ends dump processing. User Response: Examine previously issued messages to determine if an error can be corrected, such as an output error. If you cannot resolve the error, contact your service representative. ANR4003I Load command: Database load process started.
Explanation: The database load process has started. System Action: The server loads the contents of the database from a file or removable media.
296
IBM Tivoli Storage Manager: Messages
ANR4004I ANR4012W
User Response: None. ANR4004I Load command: Database load process completed. ANR4009E Load command: Database object object name cannot be deleted because it is in use by another process.
Explanation: The database load process has ended. System Action: The server completes processing. User Response: None. ANR4005E Load command: Database load process terminated due to error (error indicator).
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, contact your service representative. ANR4010E Dump/load command: Database dump/load processing failed - insufficient memory.
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 your service representative. ANR4006I Command: Volume volume number written by process is volume name.
Explanation: The database dump/load process fails due to insufficient memory. System Action: Database processing ends. User Response: Allocate additional storage to the server. There are two ways to do this: v Increase the size of the servers virtual machine (for VM), or region size (for MVS). For AIX, ensure that there is sufficient paging space. You may also use SMIT to determine if the number of applications is causing a memory shortage. For OS/2, ensure that there is sufficient space for the OS/2 SWAPPER.DAT file. Check your CONFIG.SYS for the SWAPPATH statement to determine where your SWAPPER.DAT file is located and then determine how much space is left on the drive. v Decrease the amount of space allocated to the servers database or log buffer pool. To do this, update the value of the BUFPOOLSIZE or LOGPOOLSIZE parameters in the server options file and restart the server. Note that each page causes an additional 4K page to be allocated for the specified buffer pool. Reducing the pool sizes requires more I/O to service the same amount of data; some performance degradation may result. ANR4011W Dump command: Database page page number is invalid - it will be skipped.
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. User Response: None. ANR4007E 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. User Response: Examine previously issued messages 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 specified page is invalid, and it will not be used during dump processing. System Action: Processing continues. User Response: None. ANR4012W Dump command: Database page page number is damaged.
Explanation: The database load process attempts to delete a database object, but the object does not exist. System Action: Database processing continues. User Response: None.
Explanation: The specified database page is damaged; it will not be dumped. System Action: Processing continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
297
ANR4013I ANR4021E
ANR4013I Dump command: Dumped number of entries database entries (cumulative). ANR4017E Load command: Invalid record type record type read from database dump data.
Explanation: This message indicates the number of database entries that have been dumped so far during database dump processing. System Action: Server processing continues. User Response: None. ANR4014E Load command: The specified input volume does not contain a server database dump.
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 error cannot be isolated and resolved, contact your service representative. ANR4018E Load command: Load processing failed insufficient recovery log space.
Explanation: The specified volume does not contain a dump created from the database dump command. System Action: Processing ends. User Response: None. ANR4015E Load command: Invalid record format (format code) detected.
Explanation: The load process fails due to insufficient recovery log space. System Action: Database load processing ends. User Response: Reinstall the server and specify a larger recovery log and reissue the database load command. ANR4019E Load command: Load processing failed insufficient database space.
Explanation: During processing of command load command, an invalid record type is detected when reading the dumped information from the dump media. System Action: Processing of the command ends. User Response: Examine the server messages issued prior to this message to determine the source of the 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 resolved, contact your service representative. ANR4016E Load command: Invalid header sequence number detected in database dump. Expected expected sequence number; Actual actual sequence number.
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. User Response: Examine the messages issued prior to 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 problem persists, contact your service representative. ANR4021E Dump/load command: Error (error code) occurred during an open operation.
Explanation: During processing of command load command, an invalid sequence number is detected when reading the dumped information from the dump media. System Action: Processing of the command ends. User Response: Examine previously issued server messages to determine the source of the error. If the error cannot be isolated and resolved, contact your service representative.
Explanation: An error occurs while attempting an open operation on the dump media for a database dump/load operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the operation failed; correct the problem and restart the process.
298
IBM Tivoli Storage Manager: Messages
ANR4022E ANR4032I
ANR4022E Dump command: Error (error code) occurred during a write operation. ANR4028I Dump command: Process process number, Database dump terminated due to an error (error code).
Explanation: The server database dump process encounters an error while writing to the dump media. System Action: Server processing continues, the dump processing ends. User Response: Refer to the other displayed messages to determine why the operation failed; correct the problem and restart the process. ANR4023E Load command: Error (error code) occurred during a read operation.
Explanation: The online database dump process has ended prematurely due to an error. System Action: The server ends dump processing. User Response: Examine the messages issued prior to this message to see if an error can be corrected, such as output error. If you cannot resolve the error, contact your service representative. ANR4029I Dump command: Database checkpoint started.
Explanation: The server database load process encounters an error reading from the dump media. System Action: The database load operation ends. User Response: Refer to the other displayed messages to determine why the operation failed; correct the problem and restart the process. ANR4025I 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.
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 processing continues. User Response: None. ANR4030I Dump command: Database checkpoint completed.
Explanation: The database dump process has flushed all updated pages from the database buffer pool to stable storage. System Action: Database load processing continues. User Response: None. ANR4031I Dump/load command: Copied number of pages database pages.
Explanation: This message is displayed in response to 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: This message is displayed at the end of a server database dump or load command to indicate the number of database pages copied. System Action: Database dump or load processing ends. User Response: None. ANR4032I Dump/load command: Copied number of records database records.
Explanation: The online server database dump process started as process process number has completed. System Action: Database dump processing ends. User Response: None. ANR4027I Dump command: Process process number, database dump was canceled.
Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of database records copied. System Action: Database dump or load processing ends. User Response: None.
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. User Response: None.
Chapter 3. Common and Platform Specfic Messages
299
ANR4033I ANR4042I
ANR4033I Dump/load command: Copied number of bit vectors bit vectors. ANR4038I Load command: Loading database information dumped on dump date at dump time.
Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of database bit vectors copied. System Action: Database dump or load processing ends. User Response: None. ANR4034I Dump/load command: Encountered number of bad database pages bad database pages.
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. System Action: Database load processing continues. User Response: None. ANR4039I Load command: Loaded number of entries database entries (cumulative).
Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of invalid database pages that have been encountered. System Action: Database dump or load processing ends. User Response: None.
Explanation: This message indicates the number of database entries that have been loaded so far during database load processing. System Action: Database load processing continues. User Response: None. ANR4040I Audit command: Auditing client node and administrator definitions.
ANR4035I
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. System Action: Database dump or load processing ends. User Response: None. ANR4036I Dump/load command: Copied number of database entries database entries.
Explanation: This message is displayed during a database audit and indicates that the client node and administrator definitions are being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4041I Audit command: Node node name is assigned to Domain domain name, but not verified by server database policy entries.
Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of database entries that have been copied. System Action: Database dump or load processing ends. User Response: None. ANR4037I Dump/load command: number of bytes copied.
Explanation: A database audit process finds a node assigned to a policy domain that is not recorded properly in policy database entries. System Action: Audit processing continues. 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.
Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of bytes that have been copied. System Action: Database dump or load processing ends. User Response: None.
Explanation: A database audit process finds a node 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
300
IBM Tivoli Storage Manager: Messages
ANR4043I ANR4050I
will attempt to correct the policy domain assignment for the node. System Action: Audit processing continues. User Response: When the audit command completes, you may want to check the domain assignment for this node, and reassign the node to a different policy domain, if desired. ANR4043I Audit command: Node node name assignment failed - will attempt to assign the node to domain domain name. sets the nodes compression value to the default value. System Action: Audit processing continues. 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 Audit command: Invalid archive delete value encountered for node node name.
Explanation: A database audit process finds a node 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. System Action: Audit processing continues. User Response: When the audit command completes, you may want to check the domain assignment for this node, and reassign the node to a different policy domain, if desired. ANR4044I 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.
Explanation: A database audit process encounters an invalid archive delete permission value for the node indicated. System Action: Audit processing continues. 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 problem. ANR4048I Audit command: Invalid archive delete value encountered for node node name the default value will be set.
Explanation: A database audit process encounters an 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. System Action: Audit processing continues. 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 value encountered for node node name.
Explanation: A database audit process cannot find an appropriate policy domain for assigning the specified node. System Action: Audit processing continues. User Response: When the audit command completes, use the UPDATE NODE command to assign the specified node to an appropriate policy domain. ANR4045I Audit command: Invalid compression value encountered for node node name.
Explanation: A database audit process encounters an invalid backup delete permission value for the node indicated. System Action: Audit processing continues. 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 problem. ANR4050I Audit command: Invalid backup delete value encountered for node node name the default value will be set.
Explanation: A database audit process encounters an invalid node compression value for the node indicated. System Action: Audit processing continues. 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 problem. ANR4046I Audit command: Invalid compression value encountered for node node name the default value will be set.
Explanation: A database audit process encounters an invalid node compression value for the node indicated. Because FIX=YES has been specified, the audit function
Explanation: A database audit process encounters an invalid backup delete permission value for the node indicated. Because FIX=YES has been specified, the audit function sets the nodes backup delete permission value to the default value.
Chapter 3. Common and Platform Specfic Messages
301
ANR4051I ANR4058I
System Action: Audit processing continues. User Response: If you want the backup delete value for the specified node to be set to a value other than the default, use the UPDATE NODE command to change the value after the audit command has completed. ANR4051I Audit command: Invalid lock state encountered for node node name. ANR4055I Audit command: Invalid lock state encountered for administrator administrator name.
Explanation: A database audit process encounters an invalid lock state value for the administrator indicated. System Action: Audit processing continues. 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 problem. ANR4056I Audit command: Invalid lock state encountered for administrator administrator name the administrator will be unlocked.
Explanation: A database audit process encounters an invalid lock state value for the node indicated. System Action: Audit processing continues. 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 problem. ANR4052I Audit command: Invalid lock state encountered for node node name the node will be unlocked.
Explanation: A database audit process encounters an invalid lock state value for the administrator indicated. Because FIX=YES has been specified, the audit function sets the administrators lock state to unlocked. System Action: Audit processing continues. 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.
Explanation: A database audit process encounters an invalid lock state value for the node indicated. Because FIX=YES has been specified, the audit function sets the nodes lock state to unlocked. System Action: Audit processing continues. 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.
Explanation: A database audit process finds that the global attributes used for server administrative activities are missing. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES specified so that the administrative global attributes can be recreated. ANR4058I Audit command: Administrative global attributes are missing - default values will be used to recreate the attributes.
Explanation: A database audit process encounters an invalid Node conversion state value for the node indicated. System Action: Audit processing continues. 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 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.
Explanation: A database audit process finds that the global attributes used for server administrative 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. System Action: Audit processing continues. User Response: When the audit completes, you can use the QUERY STATUS command to examine the values set for the administrative global attributes, and use the appropriate SET command to change the attributes, if desired.
Explanation: A database audit process encounters an invalid conversion state value for the node indicated. Because FIX=YES has been specified, the audit function resets the conversion state. System Action: Audit processing continues. User Response: None.
302
IBM Tivoli Storage Manager: Messages
ANR4059E ANR4066I
ANR4059E Audit command: Administrative ID assignments are incorrect. ANR4063E Audit command: Client node node number not found in the server database.
Explanation: A database audit process finds that the global attributes used for server administrative activities are incorrect. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES specified so that the administrative global attributes can be corrected. ANR4060I Audit command: Administrative ID assignments are incorrect - value(s) will be corrected.
Explanation: A database audit process finds a client node reference that is not defined correctly in the server database. System Action: Audit processing continues. 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 Audit command: Client node node number created as node node name assigned to policy domain domain name in the server database.
Explanation: A database audit process finds that the 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. System Action: Audit processing continues. User Response: None. ANR4061E Audit command: Administrative global attribute(s) are incorrect.
Explanation: A database audit process finds a client 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. System Action: Audit processing continues. 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 that the global attributes used for server administrative activities are incorrect. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES specified so that the administrative global attributes can be corrected. ANR4062I Audit command: Administrative global attribute(s) are incorrect - default values will be set.
Explanation: A database audit process finds that the global attributes used for server administrative 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. System Action: Audit processing continues. User Response: When the audit completes, you can use the QUERY STATUS command to examine the values set for the administrative global attributes, and use the appropriate SET command to change the attributes, if desired.
Explanation: A database audit process finds an administrator reference that is not defined correctly in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4066I Audit command: Administrator administrator number not found in the server database - reference will be removed.
Explanation: A database audit process finds an administrator reference that is not defined correctly in the server database. The invalid reference will be removed from the database. System Action: Audit processing continues. User Response: After the audit command completes,
Chapter 3. Common and Platform Specfic Messages
303
ANR4067E ANR4075I
review your administrator definitions with the QUERY ADMIN command. You can then use the REGISTER ADMIN and UPDATE ADMIN commands to change any definitions desired. ANR4067E Audit command: Domain domain name referenced by an administrator authority does not exist. 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.
Explanation: A database audit process encounters an invalid sign-on attempts value that is not valid for the node or administrator indicated. System Action: Audit processing continues. 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 problem. ANR4072I Audit command: Invalid file aggregation information encountered for node node name.
Explanation: A database audit process finds a policy administrator reference to a policy domain that does not exist. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. 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. System Action: Audit processing continues. 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 name referenced by an administrator authority does not exist.
Explanation: A database audit process encounters invalid information used for controlling aggregation of files for the node indicated. System Action: Audit processing continues. 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 problem. ANR4073I Audit command: Invalid file aggregation information encountered for node node name - information will be corrected.
Explanation: A database audit process encounters invalid information used for controlling aggregation of files for the node specified. Because FIX=YES has been specified, the audit function corrects the information. System Action: Audit processing continues. User Response: None. ANR4074I Dump/load command: Encountered number of entries bad database entries.
Explanation: A database audit process finds a storage administrator reference to a storage pool that does not exist. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4070I Audit command: Storage pool storage pool name referenced by an administrator authority does not exist - the authority will be removed.
Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of invalid database entries that have been encountered. System Action: Database dump or load processing ends. User Response: None. ANR4075I Audit command: Auditing policy definitions.
Explanation: A database audit process finds a policy administrator reference to a storage pool that does not exist. Because FIX=YES has been specified, the authority will be removed. System Action: Audit processing continues. User Response: After the audit command completes, review your administrator definitions with the QUERY ADMIN command. You can then use the REGISTER
Explanation: This message is displayed during a database audit and indicates that the server policy information (domain, policy set, management classes,
304
IBM Tivoli Storage Manager: Messages
ANR4076E ANR4084E
and copy groups) are being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4076E Audit command: Invalid client node count detected for policy domain domain name. ANR4080E Audit command: Invalid grace period backup retention value encountered for policy domain domain name.
Explanation: A database audit process finds an incorrect grace period retention value for the specified policy domain. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4081I Audit command: Invalid grace period backup retention value encountered for policy domain domain name - default value will be set.
Explanation: A database audit process finds that the count of nodes recorded for the specified policy domain do not match the actual number of nodes assigned to the domain. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4077I Audit command: Invalid client node count detected for policy domain domain name count will be corrected.
Explanation: A database audit process finds an incorrect grace period retention value for the specified policy domain. Because FIX=YES has been specified for the audit command, the default value will be set. System Action: Audit processing continues. User Response: None. ANR4082E Audit command: Invalid grace period archive retention value encountered for policy domain domain name.
Explanation: A database audit process finds that the 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. System Action: Audit processing continues. User Response: None. ANR4078E Audit command: Invalid activation indicators encountered for policy domain domain name.
Explanation: A database audit process finds an incorrect grace period retention value for the specified policy domain. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4083I Audit command: Invalid grace period archive retention value encountered for policy domain domain name - default value will be set.
Explanation: A database audit process finds incorrect policy set activation entries for the specified policy domain. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4079I Audit command: Invalid activation indicators encountered for policy domain domain name - entry will be corrected.
Explanation: A database audit process finds an incorrect grace period retention value for the specified policy domain. Because FIX=YES has been specified for the audit command, the default value will be set. System Action: Audit processing continues. User Response: None. ANR4084E Audit command: Invalid administrator update information encountered for policy domain domain name.
Explanation: A database audit process finds incorrect policy set activation entries for the specified policy domain. Because FIX=YES has been specified for the audit command, the entry will be corrected. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process finds incorrect last updated information for the specified policy domain. System Action: Audit processing continues. User Response: Reissue the audit command and
Chapter 3. Common and Platform Specfic Messages
305
ANR4085I ANR4093E
specify FIX=YES so that the error can be corrected. ANR4085I Audit command: Invalid administrator update information encountered for policy domain domain name - information will be corrected. not exist. Because FIX=YES has been specified for the audit command, the reference will be removed from the policy set. System Action: Audit processing continues. User Response: When the audit command completes, 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. 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 incorrect last updated information for the specified policy domain. Because FIX=YES has been specified for the command, the information is corrected. System Action: Audit processing continues. User Response: None. ANR4086E Audit command: Invalid node node number found assigned to domain domain name.
Explanation: A database audit process finds a node number assigned to a policy domain that does not reference a valid client node definition. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4087I Audit command: Invalid node node number found assigned to domain domain name reference will be deleted.
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. System Action: Audit processing continues. User Response: When the audit command completes, you must activate a new policy set for the domain with a valid default management class. ANR4091E Audit command: Invalid administrator update information encountered for policy set set name in policy domain domain name.
Explanation: A database audit process finds a node number assigned to a policy domain that does not reference a valid client node definition. Because FIX=YES has been specified for the audit command, the reference will be deleted. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process finds incorrect last updated information for the specified policy set. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4092I Audit command: Invalid administrator update information encountered for policy set set name in policy domain domain name - information will be corrected.
ANR4088E
Audit command: Default management class management class name specified for policy set policy set name in domain domain name does not exist.
Explanation: A database audit process finds a policy set with a default management class specified that does not exist. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. 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.
Explanation: A database audit process finds incorrect last updated information for the specified policy set. Because FIX=YES has been specified for the command, the information is corrected. System Action: Audit processing continues. User Response: None. ANR4093E Audit command: A management class identifier is not defined for management class management class name in policy set set name, domain domain name.
Explanation: A database audit process finds a policy set with a default management class specified that does
Explanation: A database audit process finds incorrect information for the specified management class.
306
IBM Tivoli Storage Manager: Messages
ANR4094E ANR4101I
System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4094E Audit command: A management class identifier is not defined for management class management class name in policy set set name, domain domain name - an identifier will be generated for this management class. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4098I Audit command: Invalid administrator update information encountered for management class management class name in policy set set name in policy domain domain name - information will be corrected.
Explanation: A database audit process finds incorrect information for the specified management class. The audit process generates an identifier, because FIX=YES has been specified for the audit command. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process finds incorrect last updated information for the specified management class. Because FIX=YES has been specified for the command, the information is corrected. System Action: Audit processing continues. User Response: None. ANR4099E Audit command: Copy group copy group name in management class management class name, policy set set name, domain domain name has an invalid name or type.
ANR4095E
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).
Explanation: A database audit process finds incorrect information for the specified management class. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4096E 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) - the correct identifier will be stored.
Explanation: A database audit process encounters a copy group that has an invalid name or copy group type. System Action: Audit processing continues. User Response: If FIX=YES has not been specified for 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.
Explanation: A database audit process encounters a copy group that has an invalid name or copy group type. The process attempts to reinsert the definition as a backup copy group. System Action: Audit processing continues. User Response: None. ANR4101I Audit command: A backup copy group already exists - the invalid copy group will be deleted.
Explanation: A database audit process finds incorrect information for the specified management class. The audit process corrects the identifier, because FIX=YES has been specified for the audit command. System Action: Audit processing continues. User Response: None. ANR4097E Audit command: Invalid administrator update information encountered for management class management class name in policy set set name in policy domain domain name.
Explanation: A database audit process encounters a copy group that has an invalid name or copy group 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. System Action: Audit processing continues. User Response: After the audit command completes, you may examine the server copy groups using the QUERY COPYGROUP command, and correct them
Chapter 3. Common and Platform Specfic Messages
Explanation: A database audit process finds incorrect last updated information for the specified management class. System Action: Audit processing continues.
307
ANR4102I ANR4109I
with the DEFINE COPYGROUP and UPDATE COPYGROUP commands if desired. ANR4102I Audit command: Attempting to reinsert the copy group as an ARCHIVE copy group. User Response: None. ANR4106E Audit command: An invalid copy group identifier (actual identifier) was encountered for a copy group in management class management class name, policy set set name, domain domain name (expected expected identifier).
Explanation: A database audit process encounters a copy group that has an invalid name or copy group type. The process attempts to reinsert the definition as an archive copy group. System Action: Audit processing continues. User Response: None. ANR4103I Audit command: An archive copy group already exists - the invalid copy group will be deleted.
Explanation: A database audit process finds incorrect information for the specified copy group. System Action: Audit processing continues. User Response: For programming support, contact your service representative. ANR4107E Audit command: An invalid copy group identifier (actual identifier) was encountered for copy group name copy group name (expected expected identifier).
Explanation: A database audit process encounters a copy group that has an invalid name or copy group 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. System Action: Audit processing continues. User Response: After the audit command completes, 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 Audit command: An invalid management class identifier (actual identifier) was encountered for a copy group in management class management class name, policy set set name, domain domain name (expected expected identifier).
Explanation: A database audit process finds incorrect information for the specified copy group name. System Action: Audit processing continues. User Response: For programming support, contact your service representative. 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.
Explanation: A database audit process encounters invalid backup copy group attributes for the specified copy group. System Action: Audit processing continues. User Response: If FIX=YES has not been specified for the audit command, reissue the command specifying FIX=YES so that the inconsistency can be corrected. ANR4109I 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 - the copy group will be corrected using default attributes.
Explanation: A database audit process finds incorrect information for the specified copy group. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4105E Audit command: An invalid management class identifier (actual identifier) was encountered for a copy group in management class management class name, policy set set name, domain domain name (expected expected identifier) - the correct identifier will be stored.
Explanation: A database audit process finds incorrect information for the specified copy group. The audit process corrects the identifier, since FIX=YES has been specified for the audit command. System Action: Audit processing continues.
Explanation: A database audit process encounters 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. System Action: Audit processing continues. User Response: After the audit command completes, examine the copy group by using the QUERY
308
IBM Tivoli Storage Manager: Messages
ANR4110E ANR4116I
COPYGROUP command, and correct attributes with the UPDATE COPYGROUP command, if desired. ANR4110E Audit command: Invalid archive copy group attributes encountered for copy group copy group name in management class management class name, policy set set name, domain domain name. ANR4113E Audit command: Invalid administrator update information encountered for copy group copy group name in management class management class name, policy set set name, policy domain domain name.
Explanation: A database audit process finds incorrect last updated information for the specified copy group. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4114I Audit command: Invalid administrator update information encountered for copy group copy group name in management class management class name, policy set set name, policy domain domain name - information will be corrected.
Explanation: A database audit process encounters invalid archive copy group attributes for the specified copy group. System Action: Audit processing continues. User Response: If FIX=YES has not been specified for the audit command, reissue the command and specify FIX=YES so that the inconsistency can be corrected. ANR4111I Audit command: Invalid archive copy group attributes encountered for copy group copy group name in management class management class name, policy set set name, domain domain name - the copy group will be corrected using default attributes.
Explanation: A database audit process finds incorrect last updated information for the specified copy group. Because FIX=YES has been specified for the command, the information is corrected. System Action: Audit processing continues. User Response: None. ANR4115E Audit command: Policy domain domain name is referenced, but not formally defined.
Explanation: A database audit process encounters 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. System Action: Audit processing continues. User Response: After the audit command completes, examine the copy group by using the QUERY COPYGROUP command, and correct the attributes with the UPDATE COPYGROUP command, if desired. ANR4112W Audit command: Storage pool storage pool name, specified as a destination for copy group copy group name in management class management class name, policy set set name, domain domain name, does not exists.
Explanation: A database audit process finds a reference to the specified policy domain, but the domain is not formally defined in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4116I Audit command: Policy domain domain name is referenced, but not formally defined - a policy domain with default attributes will be defined with this name.
Explanation: A database audit process encounters a 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. System Action: Audit processing continues. User Response: After the audit command completes, 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.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. User Response: After the audit command has 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.
Chapter 3. Common and Platform Specfic Messages
309
ANR4117E ANR4125I
ANR4117E Audit command: Policy set set name in domain domain name is referenced, but not formally defined. 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).
Explanation: A database audit process finds a reference to the specified policy set, but the set is not formally defined in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. 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.
Explanation: A database audit process finds a reference count for the specified management class that did not match the actual number of instances for this class. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4123I Audit command: The instance count for management class class name does not agree with the actual management class data (number of instances instances) - the number will be corrected.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. 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.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. User Response: None. ANR4124E Audit command: The instance count for copy group copy group name does not agree with the actual copy group data (number of instances instances).
Explanation: A database audit process finds a reference to the specified management class, but the class is not formally defined in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4120I Audit command: Management class class name in policy set set name, domain domain name is referenced, but not formally defined - the management class will be created.
Explanation: A database audit process finds a reference count for the specified copy group that does not match the actual number of instances for this copy group. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4125I Audit command: The instance count for copy group copy group name does not agree with the actual copy group data (number of instances instances) - the number will be corrected.
Explanation: A database audit process finds a reference to the specified management class, but the class is not formally defined in the server database. Because FIX=YES has been specified for the audit command, the audit process defines a management class in the server with this name. System Action: Audit processing continues. User Response: After the audit command has completed, you can view the attributes for this management class by using the QUERY MGMTCLASS
Explanation: A database audit process finds a 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. System Action: Audit processing continues. User Response: None.
310
IBM Tivoli Storage Manager: Messages
ANR4126E ANR4133I
ANR4126E Audit command: Policy global attributes cannot be found. ANR4131W Audit Volume found incorrect object information for volume volume name: Node node name, Type file type, File space filespace name, fsId filespace id, File name file name.
Explanation: A database audit process is not able to locate the global attributes for policy information in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4127I Audit command: Policy global attributes cannot be found - attributes will recreated.
Explanation: As the result of an AUDIT VOLUME command that specified FIX=NO for the volume shown, object information for the specified file is found to be in error. System Action: None. User Response: None. ANR4132I Audit volume process ended for volume volume name; file count files inspected, file count damaged files deleted, file count damaged files marked as damaged, file count objects updated.
Explanation: A database audit process is not able to locate the global attributes for policy information in the server database. Because FIX=YES has been specified for the audit command, the attributes will be regenerated. System Action: Audit processing continues. User Response: None. ANR4128E Audit command: Policy global high-water marks do not match the identifiers in use.
Explanation: A database audit process finds the attributes used to track policy identifiers are incorrect. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4129E Audit command: Policy global high-water marks do not match the identifiers in use - they will be corrected.
Explanation: The AUDIT VOLUME command specifying FIX=YES for the volume shown has ended. The number of files audited, the number of inconsistent files deleted or marked as damaged, and the number of updated objects 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. System Action: None. User Response: To recover files that have been marked as damaged on the volume, use the RESTORE STGPOOL or RESTORE volume command. ANR4133I Audit volume process ended for volume volume name; file count files inspected, file count damaged files found and marked as damaged, file count objects need updating.
Explanation: A database audit process finds the attributes used to track policy identifiers are incorrect. Because FIX=YES has been specified for the audit command, the attributes will be corrected. System Action: Audit processing continues. User Response: None. ANR4130W Audit Volume updating object information for volume volume name: Node node name, Type file type, File space filespace name, fsId filespace id , File Name file name.
Explanation: As the result of an AUDIT VOLUME command that specified FIX=YES for the volume shown, object information for the specified file will be updated. System Action: The object information is updated. User Response: None.
Explanation: The AUDIT VOLUME command specifying FIX=NO for the volume shown has ended. The number of files audited, the number of inconsistent files found, and the number of files with incorrect object information 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). System Action: None. User Response: If you suspect that files were inaccessible because of hardware problems such as
Chapter 3. Common and Platform Specfic Messages
311
ANR4135I ANR4144I
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. ANR4135I Audit command: Auditing central scheduler definitions. ANR4140I Audit command: Database audit process started.
Explanation: This message is displayed during a database audit and indicates that the audit process has started. System Action: Audit processing continues. User Response: None. ANR4141I Audit command: Database audit process completed.
Explanation: This message is displayed during a database audit and indicates that the server scheduling information is examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4136I Audit command: Auditing server inventory.
Explanation: This message is displayed during a database audit and indicates that the database audit has successfully completed. System Action: Audit processing ends. User Response: None. ANR4142I Audit command: Database audit process terminated in error.
Explanation: This message is displayed during a database audit and indicates that server information about client file spaces is currently being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4137I Audit command: Auditing inventory file spaces.
Explanation: This message is displayed during a database audit and indicates that the audit process ended prematurely due to an internal server database error. System Action: Audit processing ends. User Response: Examine the messages issued prior to this one to see if the error can be corrected. If the situation cannot be resolved, contact your service representative. ANR4143E Audit command: Central scheduler global attributes cannot be found.
Explanation: This message is displayed during a database audit and indicates that server information about client file spaces is currently being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4138I Audit command: Auditing inventory backup objects.
Explanation: A database audit process cannot locate the global attributes for scheduling information in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4144I Audit command: Central scheduler global attributes cannot be found - attributes will be recreated.
Explanation: This message is displayed during a database audit and indicates that server information about client backup objects is currently being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4139I Audit command: Auditing inventory archive objects.
Explanation: This message is displayed during a database audit and indicates that server information about client archive objects is currently being examined by the database audit process. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process cannot locate the global attributes for scheduler information in the server database. Because FIX=YES has been specified for the audit command, the attributes will be regenerated. System Action: Audit processing continues. User Response: None.
312
IBM Tivoli Storage Manager: Messages
ANR4145E ANR4152I
ANR4145E Audit command: One or more central scheduler attributes are incorrect. ANR4149E Audit command: One or more attributes for schedule schedule name in policy domain domain name are incorrect.
Explanation: A database audit process finds that the global attributes used for server scheduling activities are incorrect. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected. ANR4146I Audit command: One or more central scheduler global attribute(s) are incorrect - default values will be set.
Explanation: A database audit process finds one or more invalid attributes for the specified schedule. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected. 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 that the 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. System Action: Audit processing continues. User Response: When the audit completes, you can use the QUERY STATUS command to examine the values set for the administrative global attributes, and use the appropriate SET command to change the attributes, if desired. ANR4147E Audit command: Policy domain domain name referenced by schedule schedule name does not exist.
Explanation: A database audit process finds one or more invalid attributes for the specified schedule. Because FIX=YES has been specified for the audit command the invalid attributes will be set to default values. System Action: Audit processing continues. User Response: When the audit completes, you can 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.
Explanation: A database audit process finds a schedule that references a policy domain that is not defined in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected. ANR4148I Audit command: Policy domain domain name referenced by schedule schedule name does not exist - the schedule will be deleted.
Explanation: A database audit process finds a schedule reference from a client node for a schedule that is not defined in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected. ANR4152I Audit command: Schedule schedule name in policy domain domain name not found, but is referenced by a client node - the schedule association will be deleted.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process finds a schedule reference from a client node for a schedule that is not defined in the server database. Because FIX=YES has been specified for the audit command, the schedule association will be deleted from the server database. System Action: Audit processing continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
313
ANR4153E ANR4162I
ANR4153E Audit command: Schedule schedule name in policy domain domain name references a client node that does not exist. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4158I Audit command: Scheduling callback address is registered for a client node that does not exist - callback information will be deleted.
Explanation: A database audit process finds a schedule that references a client node that is not defined in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected. ANR4154I Audit command: Schedule schedule name in policy domain domain name references a client node that does not exist - the node reference will be deleted.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. User Response: None. ANR4159I Audit command: An inventory authorization rule specifies an invalid node (node ID) or file space (filespace ID) - the rule will be deleted.
Explanation: A database audit process finds a schedule that references a client node 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. System Action: Audit processing continues. User Response: None. ANR4155E Audit command: Invalid administrator update information encountered for a schedule assignment.
Explanation: A database audit process finds that 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. System Action: Audit processing continues. User Response: None. ANR4160I Audit command: An inventory authorization rule specifies an invalid node (node ID) or file space (filespace ID).
Explanation: A database audit process finds incorrect last updated information for a schedule-node assignment. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4156I Audit command: Invalid administrator update information encountered for a schedule assignment - information will be corrected.
Explanation: A database audit process finds that either a node ID or file space ID is invalid for an authorization rule. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4161I Audit command: Inventory global attributes could not be found - they will be created.
Explanation: A database audit process finds incorrect last updated information for a schedule-node assignment. Because FIX=YES has been specified for the command, the information is corrected. System Action: Audit processing continues. User Response: None. ANR4157E Audit command: Scheduling callback address is registered for a client node that does not exist.
Explanation: A database audit process cannot find the inventory global attributes. Because FIX=YES has been specified for the command, the information is corrected by the creation of the global attributes. System Action: Audit processing continues. User Response: None. ANR4162I Audit command: Inventory global attributes could not be found.
Explanation: A database audit process finds a server-prompted-scheduling callback address for a node that does not exist. System Action: Audit processing continues.
Explanation: A database audit process cannot find the inventory global attributes. System Action: Audit processing continues.
314
IBM Tivoli Storage Manager: Messages
ANR4163I ANR4171I
User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4163I Audit command: Invalid object ID high-water mark encountered for inventory global attributes - the value will be corrected. ANR4167I Audit command: The file space high-water mark for node node ID is incorrect - the value will be corrected.
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 command, the information is corrected. System Action: Audit processing continues. User Response: None. ANR4168I Audit command: The file space high-water mark for node node ID is incorrect.
Explanation: A database audit process finds that the 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. System Action: Audit processing continues. User Response: None. ANR4164I Audit command: Invalid object ID high-water mark encountered for inventory global attributes.
Explanation: A database audit process finds that a file space high-water mark is incorrect for the specified node ID. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4169I Audit command: The file space high-water mark for node node ID is incorrect - the value will be corrected.
Explanation: A database audit process finds that the object ID high-water mark for the inventory global attributes is invalid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4165I Audit command: An inventory node assignment entry was not found for node node ID - an entry will be created.
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. System Action: Audit processing continues. User Response: None. ANR4170I Audit command: The authorization rule high-water mark for node node ID is incorrect.
Explanation: A database audit process cannot find the 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. System Action: Audit processing continues. User Response: None. ANR4166I Audit command: An inventory node assignment entry was not found for node node ID.
Explanation: A database audit process finds that an authorization rule high-water mark is incorrect for the specified node ID. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4171I Audit command: Primary backup entry for an expiring object (object.ID) cannot be found - the expiring object entry will be deleted.
Explanation: A database audit process cannot find the node assignment entry corresponding to the specified node. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
Explanation: A database audit process cannot find the primary backup entry for the specified expiring object. Because FIX=YES has been specified for the command, the information is corrected by deleting the expiring object entry. System Action: Audit processing continues.
Chapter 3. Common and Platform Specfic Messages
315
ANR4172I ANR4181I
User Response: None. ANR4172I Audit command: Primary backup entry for an expiring object (object.ID) cannot be found. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4177I Audit command: Primary backup entry for an object (object.ID) cannot be found entry will be deleted.
Explanation: A database audit process cannot find the primary backup entry for the specified expiring object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4173I Audit command: Primary archive entry for an expiring object (object.ID) cannot be found - the expiring object entry will be deleted.
Explanation: A database audit process cannot find the specified primary backup object. Because FIX=YES has been specified for the command, the entry is deleted. System Action: Audit processing continues. User Response: None. ANR4178I Audit command: Primary backup entry for an object (object.ID) cannot be found.
Explanation: A database audit process cannot find the primary archive entry for the specified expiring object. Because FIX=YES has been specified for the command, the information is corrected by deleting the expiring object entry. System Action: Audit processing continues. User Response: None. ANR4174I Audit command: Primary archive entry for an expiring object (object.ID) cannot be found.
Explanation: A database audit process cannot find the specified primary backup object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4179I Audit command: Primary archive entry for an object (object.ID) cannot be found entry will be deleted.
Explanation: A database audit process cannot find the specified primary archive object. Because FIX=YES has been specified for the command, the entry is deleted. System Action: Audit processing continues. User Response: None. ANR4180I Audit command: Primary archive entry for an object (object.ID) cannot be found.
Explanation: A database audit process cannot find the primary archive entry for the specified expiring object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4175I Audit command: Invalid copy type encountered for an expiring objects entry (object.ID) - the expiring object entry will be deleted.
Explanation: A database audit process cannot find the specified primary archive object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4181I Audit command: Invalid copy type encountered for object object.ID - object found as a backup object - correcting the invalid copy type
Explanation: A database audit process finds that the copy type for the specified expiring object is invalid. Because FIX=YES has been specified for the command, the information is corrected by deleting the expiring object entry. The entry will be recreated later if it is necessary. System Action: Audit processing continues. User Response: None. ANR4176I Audit command: Invalid copy type encountered for an expiring objects entry (object.ID).
Explanation: A database audit process encounters an invalid copy type for the specified object ID but finds a corresponding backup object for the entry. Because FIX=YES has been specified for the command, the invalid copy type is corrected. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process finds that the copy type for the specified expiring object is invalid. System Action: Audit processing continues.
316
IBM Tivoli Storage Manager: Messages
ANR4182I ANR4191I
ANR4182I Audit command: Invalid copy type encountered for object object.ID - object found as an archive object - correcting the invalid copy type User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4187I Audit command: Inventory object fields for object object.ID do not match the primary backup entry - the object will be updated.
Explanation: A database audit process encounters an invalid copy type for the specified object ID but finds a corresponding archive object for the entry. Because FIX=YES has been specified for the command, the invalid copy type is corrected. System Action: Audit processing continues. User Response: None. ANR4183I Audit command: Invalid copy type encountered for object object.ID primary archive entry created for object using default values.
Explanation: A database audit process determines that the object fields for the specified object ID do not match the fields for the corresponding primary backup object. Because FIX=YES has specified for the command, the incorrect object fields will be corrected. System Action: Audit processing continues. User Response: None. ANR4188I Audit command: Inventory object fields for object object.ID do not match the primary backup entry.
Explanation: A database audit process encounters an 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. System Action: Audit processing continues. User Response: None. ANR4184I Audit command: Invalid copy type encountered for object object.ID.
Explanation: A database audit process determines that the object fields for the specified object ID do not match the fields for the corresponding primary backup object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4189I Audit command: Expiring entry for inactive backup object object.ID not found - the entry will be created.
Explanation: A database audit process encounters an invalid copy type for the specified object ID and is unable to find corresponding primary backup or primary archive objects. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4185I Audit command: Object entry for backup object object.ID not found - entry will be created.
Explanation: A database audit process cannot find an expiring entry for the specified inactive backup entry. Because FIX=YES has been specified for the command, an expiring entry will be created. System Action: Audit processing continues. User Response: None. ANR4190I Audit command: Expiring entry for inactive backup object object.ID not found.
Explanation: A database audit process cannot find an object entry for the specified backup object. Because FIX=YES has been specified for the command, an object entry is created using default values. System Action: Audit processing continues. User Response: None. ANR4186I Audit command: Object entry for backup object object.ID not found.
Explanation: A database audit process cannot find an expiring entry for the specified inactive backup entry. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4191I Audit command: Object entry for archive object object.ID not found - entry will be created.
Explanation: A database audit process cannot find an object entry for the specified backup object. System Action: Audit processing continues.
Explanation: A database audit process cannot find an object entry for the specified archive object. Because FIX=YES has been specified for the command, the
Chapter 3. Common and Platform Specfic Messages
317
ANR4192I ANR4201I
information is corrected by creating an object entry. System Action: Audit processing continues. User Response: None. ANR4192I Audit command: Object entry for archive object object.ID not found. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. 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. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4198I Audit command: File space entry filespace ID not found for node node name - an entry will be created.
Explanation: A database audit process cannot find an object entry for the specified archive object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4193I Audit command: Inventory object fields for object object.ID do not match the primary archive entry - the object will be updated.
Explanation: A database audit process determines that the object fields for the specified object ID do not match the fields for the corresponding primary archive object. Because FIX=YES has been specified for the command, the incorrect object fields will be corrected. System Action: Audit processing continues. User Response: None. ANR4194I Audit command: Inventory object fields for object object.ID do not match the primary archive entry.
Explanation: A database audit process cannot find a file space entry for the specified node. Because FIX=YES has been specified for the command, a file space entry has been created. System Action: Audit processing continues. User Response: None. ANR4199I Audit command: File space entry filespace ID not found for node node name unable to create an entry.
Explanation: A database audit process determines that the object fields for the specified object ID do not match the fields for the corresponding primary archive object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4195I Audit command: Expiring entry for archive object object.ID not found - the entry will be created.
Explanation: A database audit process cannot find a file space entry for the specified node. Because FIX=YES has been specified for the command, the audit process has attempted to create a file space entry but is not successful. System Action: Audit processing continues. User Response: Contact your system administrator. 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.
Explanation: A database audit process cannot find an expiring entry for the specified archive object. Because FIX=YES has been specified for the command, an expiring entry will be created. System Action: Audit processing continues. User Response: None. ANR4196I Audit command: Expiring entry for archive object object.ID not found.
Explanation: A database audit process determines that the specified expiring object entry does not match the corresponding object entry for the specified object ID. Because FIX=YES has been specified for the command, the expiring object entry is deleted. System Action: Audit processing continues. User Response: None. ANR4201I Audit command: Expiring entry node ID and file space filespace ID does not match the object entry for object ID object.ID.
Explanation: A database audit process cannot find an expiring entry for the specified archive object. System Action: Audit processing continues.
Explanation: A database audit process determines that the specified expiring object entry does not match the corresponding object entry for the specified object ID. System Action: Audit processing continues.
318
IBM Tivoli Storage Manager: Messages
ANR4202I ANR4211I
User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4202I Audit command: The base date for expiration processing of entry object.ID is not valid - the entry will be deleted. ANR4207I Audit command: Object entry for expiring object object.ID not found.
Explanation: A database audit process cannot find an object entry corresponding to the specified expiring object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4208I Audit command: An inventory node assignment entry is not valid for node node ID - the entry will be deleted.
Explanation: A database audit process determines that the specified expiring object has a date that is not valid. Because FIX=YES has been specified for the command, the expiring object entry is deleted. System Action: Audit processing continues. User Response: None. ANR4203I Audit command: The base date for expiration processing of object object.ID is not valid.
Explanation: A database audit process finds that a 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. System Action: Audit processing continues. User Response: None. ANR4209I Audit command: An inventory node assignment entry was not found for node node ID.
Explanation: A database audit process determines that the specified expiring object has a date value that is not valid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4204I Audit command: One or more date values for a backup entry object.ID is not valid.
Explanation: A database audit process finds that a node assignment entry for the specified node ID is not valid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4210I Audit command: Auditing physical volume repository definitions.
Explanation: A database audit process determines that one or more of the date values is improperly formatted or contains incorrect information for the specified backup object. System Action: Audit processing continues. User Response: Contact your system administrator. ANR4205I Audit command: The insertion date value for archive entry object.ID is not valid.
Explanation: A database audit process determines that the insertion date for the specified archive object is improperly formatted or contains incorrect information. System Action: Audit processing continues. User Response: Contact your system administrator. ANR4206I Audit command: Object entry for expiring object object.ID not found - expiring object entry will be deleted.
Explanation: This message is displayed during a database audit and indicates that the physical volume repository definitions are being examined by the database audit process. System Action: Audit processing continues. User Response: None. 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. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
Explanation: A database audit process cannot find an object entry corresponding to the specified expiring object. Because FIX=YES has been specified for the command, the expiring object entry for the specified object ID is deleted. System Action: Audit processing continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
319
ANR4212I ANR4220I
ANR4212I 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. the command, the invalid library inventory entry is deleted. System Action: Audit processing continues. User Response: None. ANR4217I Audit command: The volume status for library library name and volume volume name in the physical volume repository is invalid.
Explanation: A database audit process finds that a drive entry is missing a corresponding library entry. Because FIX=YES has been specified for the command, the invalid drive entry is deleted. System Action: Audit processing continues. User Response: None. ANR4213I Audit command: A device type for library library name and drive drive name in the physical volume repository is invalid.
Explanation: A database audit process finds that the 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. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4218I Audit command: The volume status for library library name and volume volume name in the physical volume repository is invalid - the volume status will be changed to private.
Explanation: A database audit process finds that a device type for the specified library and drive is invalid. System Action: Audit processing continues. User Response: Contact the system administrator so that appropriate action may be taken. ANR4214I Audit command: A drive model for library library name and drive drive name in the physical volume repository is invalid.
Explanation: A database audit process finds that the drive model for the specified library and drive is invalid. System Action: Audit processing continues. User Response: Contact the system administrator so that appropriate action may be taken. ANR4215I Audit command: An object entry for library library name and volume volume name in the physical volume repository is invalid.
Explanation: A database audit process finds that the 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. Because FIX=YES has been specified for the command, the incorrect volume status is set to private. System Action: Audit processing continues. User Response: None. ANR4219I Audit command: A library type specified for library library name in the physical volume repository is invalid.
Explanation: A database audit process finds that a library inventory entry is missing a corresponding library entry. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4216I Audit command: An object entry for library library name and volume volume name in the physical volume repository is invalid - the entry will be deleted.
Explanation: A database audit process finds that the library type for the specified library is invalid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. 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.
Explanation: A database audit process finds that a library inventory entry is missing a corresponding library entry. Because FIX=YES has been specified for
Explanation: A database audit process finds that the library type for the specified library is invalid. Because FIX=YES has been specified for the command, the
320
IBM Tivoli Storage Manager: Messages
ANR4221I ANR4229E
information is corrected by changing the library type to the default type. System Action: Audit processing continues. User Response: None. ANR4221I 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. ANR4225I Audit command: table entry for archive object (object.ID), node (node identifier), description (description), filespace (filespace identifier) not found - the entry will be created. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
Explanation: A database audit process cannot find a converted table table entry for the specified archive object. Because FIX=YES has been specified for the command, an entry will be created. System Action: Audit processing continues. User Response: None. ANR4226I Audit command: table entry for archive object (object.ID), node (node identifier), description (description), filespace (filespace identifier) not found.
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. System Action: Audit processing continues. User Response: None. ANR4222I 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).
Explanation: A database audit process cannot find a converted table table entry for the specified archive object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4227E Audit command: Inconsistent information detected for file aggregate (Aggregate.ID).
Explanation: A database audit process has found an error with the specified archive description. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4223I Audit command: An error (error code) was found with converted archive object for node (node identifier), description (description identifier), object (object.ID), filespace (filespace identifier) - entry will be deleted.
Explanation: A database audit process finds inconsistent information for a file aggregate. This problem cannot be corrected by the audit process, but the file data is not deleted. System Action: Audit processing continues. User Response: Contact your service representative. ANR4228E Audit command: Missing or incorrect information detected for file aggregate (Aggregate.ID).
Explanation: A database audit process has found an error with the specified converted archive object. Because FIX=YES has been specified for the command, the entry is deleted. System Action: Audit processing continues. User Response: None. ANR4224I Audit command: An error (error code) was found with converted archive object for node (node identifier), description (description identifier), object (object.ID), filespace (filespace identifier).
Explanation: A database audit process detects missing or incorrect information for a file aggregate. This information can be corrected. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4229E Audit command: Missing or incorrect information detected for file aggregate (Aggregate.ID) - It will be corrected.
Explanation: A database audit process has found an error with the specified converted archive object. System Action: Audit processing continues.
Explanation: A database audit process detects missing or incorrect information for a file aggregate. Because
Chapter 3. Common and Platform Specfic Messages
321
ANR4230I ANR4238E
FIX=YES has been specified for the audit command, the error will be corrected. System Action: Audit processing continues. User Response: None. ANR4230I Audit command: Auditing data storage definitions. command, the pool ID information will be created or corrected for this storage pool. System Action: Audit processing continues. User Response: None. ANR4235E Audit command: Device class ID referenced by storage pool storage pool name is not defined - data in this pool may not be available.
Explanation: This message is displayed during a database audit and indicates that the data storage definitions are being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4231E Audit command: Invalid device class strategy strategy for device class device class name.
Explanation: A database audit process finds a storage pool which references a device class ID which is not defined. System Action: Audit processing continues. User Response: Contact your service representative. ANR4236E Audit command: An invalid access strategy was encountered for storage pool storage pool name.
Explanation: A database audit process finds a device class with an invalid access strategy. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the access strategy can be corrected. ANR4232E Audit command: Invalid device class strategy strategy for device class device class name - information will be corrected.
Explanation: A database audit process encounters an invalid device access strategy for the specified storage pool. System Action: Audit processing continues. User Response: Reissue the audit command with 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.
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. System Action: Audit processing continues. User Response: None. ANR4233E Audit command: Pool ID information is missing or incorrect for storage pool storage pool name.
Explanation: A database audit process encounters an 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. System Action: Audit processing continues. User Response: After the audit command completes, examine the storage pool using the QUERY STGPOOL command, and verify that the correct information is displayed for this storage pool. ANR4238E Audit command: Storage pool storage pool name specifies an undefined pool ID for its next storage pool.
Explanation: A database audit process finds a storage pool whose pool ID information is missing or incorrect. System Action: Audit processing continues. User Response: Reissue the audit command with 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.
Explanation: The specified storage pool references an invalid pool ID as its next storage pool. System Action: Audit processing continues. User Response: Use the UPDATE STGPOOL command to update the next pool. Alternatively, if the audit command is reissued with FIX=YES, the reference to the next pool will be deleted.
Explanation: A database audit process finds a storage pool whose pool ID information is missing or incorrect. Because FIX=YES has been specified for the audit
322
IBM Tivoli Storage Manager: Messages
ANR4239E ANR4246E
ANR4239E Audit command: Storage pool storage pool name specifies an undefined pool ID for its next storage pool - reference will be deleted. ANR4243E Audit command: Invalid administrator update information encountered for storage pool storage pool name information will be corrected.
Explanation: The specified storage pool references an invalid pool ID as its next storage pool. Because FIX=YES has been specified for the command, the reference is deleted. The specified storage pool will not have a next pool. System Action: Audit processing continues. User Response: After the audit command completes, 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.
Explanation: A database audit process finds incorrect information pertaining to the last update for the specified storage pool. Because FIX=YES has been specified for the command, the information is corrected. System Action: Audit processing continues. User Response: None. 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 encounters an invalid attribute for the specified storage pool. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the attribute can be corrected. ANR4241E Audit command: An invalid attribute was encountered for storage pool storage pool name - the attribute will be assigned its default value.
Explanation: A database audit process finds a data storage volume which references a storage pool ID that is not defined. System Action: Audit processing continues. 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. ANR4245E Audit command: An invalid access strategy was encountered for volume volume name.
Explanation: A database audit process encounters an invalid attribute for the specified storage pool. Because FIX=YES has been specified for the command, the storage pool will be corrected using the default value for the attribute. System Action: Audit processing continues. User Response: After the audit command completes, examine the storage pool using the QUERY STGPOOL command, and correct attributes with the UPDATE STGPOOL command, if desired. ANR4242E Audit command: Invalid administrator update information encountered for storage pool storage pool name.
Explanation: A database audit process encounters an invalid device access strategy for the specified volume. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the strategy can be corrected. ANR4246E Audit command: An invalid access strategy was encountered for volume volume name - the strategy will be corrected.
Explanation: A database audit process finds incorrect information pertaining to the last update for the specified storage pool. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
Explanation: A database audit process encounters an invalid device access strategy for the specified volume. Because FIX=YES has been specified for the command, the access strategy will be corrected for this volume. System Action: Audit processing continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
323
ANR4247E ANR4254E
ANR4247E Audit command: Missing information for volume volume name cannot be created. Delete the volume after optionally moving any files from the volume. System Action: Audit processing continues. User Response: Reissue the audit command with 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.
Explanation: A database audit process encounters missing database information for the specified volume. Since FIX=YES has been specified for the audit command, an attempt is made to create the missing information where possible. However, some of the information cannot be created, and the volume must be deleted. System Action: The access mode for the volume is set to UNAVAILABLE to prevent further attempts to write to this volume. Audit processing continues. User Response: After audit processing completes, an administrator should take the following actions to eliminate the volume v (Optional) Use the UPDATE VOLUME command to set the access mode for the volume to READWRITE. It may then be possible to use the MOVE DATA command to move files from the volume so that these files can be accessed by the server. v (Required) Use the DELETE VOLUME command to delete the volume from the database. ANR4248E Audit command: Missing or incorrect information for storage volume volume name.
Explanation: A database audit process finds a 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 extraneous information will be deleted. System Action: Audit processing continues. User Response: None. ANR4252E Audit command: Data storage global attributes cannot be found.
Explanation: A database audit process is not able to locate the global attributes for data storage in the server database. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4253E Audit command: Data storage global attributes cannot be found - attributes will be recreated.
Explanation: A database audit process finds a data storage volume for which information is missing or incorrect. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the information can be created or corrected. ANR4249E Audit command: Missing or incorrect information for storage volume volume name - information will be created or corrected.
Explanation: A database audit process is not able to locate the global attributes for data storage in the server database. Because FIX=YES has been specified for the audit command, the attributes will be regenerated. System Action: Audit processing continues. User Response: None. ANR4254E Audit command: Data storage high-water marks do not match the identifiers in use.
Explanation: A database audit process finds a data storage volume for which information is missing or incorrect. Since FIX=YES has been specified for the audit command, the information will be created or corrected. System Action: Audit processing continues. User Response: None. ANR4250E Audit command: Extraneous reference found.
Explanation: A database audit process finds that the information used to track data storage identifiers is incorrect. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
Explanation: A database audit process finds a reference to a nonexistent entity such as a storage pool or volume.
324
IBM Tivoli Storage Manager: Messages
ANR4255E ANR4264I
ANR4255E Audit command: Data storage high-water marks do not match the identifiers in use - they will be corrected. ANR4260E Audit command: Invalid data encountered for a file in data storage - the error will be corrected.
Explanation: A database audit process finds that the information used to track data storage identifiers is incorrect. Because FIX=YES has been specified for the audit command, the error will be corrected. System Action: Audit processing continues. User Response: None. ANR4256I Audit command: Auditing data storage definitions for disk volumes.
Explanation: A database audit process finds invalid data for a file in data storage. Because FIX=YES has been specified for the audit command, the error will be corrected. System Action: Audit processing continues. User Response: None. ANR4261E Audit command: Invalid access information was encountered for volume volume name.
Explanation: This message is displayed during a database audit and indicates that the database information relating to data storage disk volumes is being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4257E Audit command: A correctable data-integrity error was detected on volume volume name.
Explanation: A database audit process encounters invalid access information for the specified volume. System Action: Audit processing continues. 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. ANR4262E Audit command: Invalid access information was encountered for volume volume name - the information will be corrected.
Explanation: A database audit process finds a data-integrity error for a file stored on the specified volume. This error is correctable. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4258E Audit command: A data-integrity error was detected on volume volume name the error will be corrected.
Explanation: A database audit process encounters invalid access information for the specified volume. Because FIX=YES has been specified for the command, the information will be corrected by setting the default value. System Action: Audit processing continues. User Response: After audit processing has completed, use the UPDATE VOLUME command to set the access information for this volume, if desired. ANR4263I Audit command: Auditing data storage definitions for sequential volumes.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. User Response: None. ANR4259E Audit command: Invalid data encountered for a file in data storage - data can be corrected.
Explanation: This message is displayed during a database audit and indicates that the database information relating to data storage sequential volumes is being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4264I Audit command: Auditing file information.
Explanation: A database audit process finds invalid data for a file in data storage. The error should be correctable. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
Explanation: This message is displayed during a database audit and indicates that information on stored files is being examined by the database audit process. System Action: Audit processing continues.
Chapter 3. Common and Platform Specfic Messages
325
ANR4265I ANR4274E
User Response: None. ANR4265I Audit command: Auditing disk file information. ANR4270E Audit command: Extraneous file data reference found - information will be deleted.
Explanation: This message is displayed during a database audit and indicates that information on files stored on disk media is being examined by the database audit process. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process finds a reference to a file that no longer exists. Because FIX=YES has been specified for the audit command, the information will be deleted. System Action: Audit processing continues. User Response: None. ANR4271E Audit command: Missing or incorrect occupancy information detected.
ANR4266I
Audit command: Auditing sequential file information.
Explanation: This message is displayed during a database audit and indicates that information on files stored on sequential media is being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4267E Audit command: A storage pool containing file data cannot be located file data may not be accessible.
Explanation: A database audit process detects missing or incorrect occupancy information for a data storage pool or a data storage volume. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the information can be created or corrected. ANR4272E Audit command: Missing or incorrect occupancy information detected information will be created or corrected.
Explanation: This message is displayed during a 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. System Action: Audit processing continues. User Response: Contact your service representative. ANR4268E Audit command: A storage volume containing file data cannot be located file data may not be accessible.
Explanation: A database audit process detects missing or incorrect occupancy information for a data storage pool or a data storage volume. Because FIX=YES has been specified for the audit command, the information will be created or corrected. System Action: Audit processing continues. User Response: None. ANR4273E Audit command: A data-integrity error was detected on volume volume name Issue the AUDIT VOLUME command to correct the error.
Explanation: This message is displayed during a database audit and indicates that the storage volume containing a files data cannot be located or is not defined. This problem cannot be corrected by the audit process, and the file data is deleted. System Action: Audit processing continues. User Response: Contact your service representative. ANR4269E Audit command: Extraneous file data reference found.
Explanation: A database audit process finds a data-integrity error for a file stored on the specified volume. System Action: Audit processing continues. 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.
Explanation: A database audit process finds a reference to a file that no longer exists. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the information can be deleted.
Explanation: A database audit process finds a data-integrity error for a stored file. This error can be corrected. System Action: Audit processing continues. User Response: Reissue the audit command and
326
IBM Tivoli Storage Manager: Messages
ANR4275E ANR4282I
specify FIX=YES so that the error can be corrected. ANR4275E Audit command: A data-integrity error was detected - it will be corrected. specify FIX=YES so that the error can be corrected. ANR4280I Audit command: Administrator administrator number assigned to more than just system authority class - the other class entries will be deleted.
Explanation: A database audit process finds a data-integrity error for a stored file. Because FIX=YES has been specified for the audit command, the error will be corrected. System Action: Audit processing continues. User Response: None. ANR4276E Audit command: Invalid file storage information detected - file data is not accessible.
Explanation: A database audit process finds that an 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. System Action: Audit processing continues. User Response: None. ANR4281E Audit command: Administrator administrator number assigned as an unrestricted policy administrator is also assigned as a restricted administrator for domain domain name.
Explanation: A database audit process finds invalid file storage information for a stored file, and it cannot be corrected. System Action: Audit processing continues. User Response: Issue the AUDIT VOLUME command on all your volumes to correct the data-integrity error. ANR4277E Audit command: Invalid file storage information detected.
Explanation: A database audit process finds invalid file storage information for a stored file. This information can be corrected. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4278E Audit command: Invalid file storage information detected - It will be corrected.
Explanation: A database audit process finds the 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. The administrators authority needs to be corrected. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4282I Audit command: Administrator administrator number assigned as an unrestricted policy administrator is also assigned as administrator for domain domain name - restricted class entry will be deleted.
Explanation: A database audit process finds invalid file storage information for a stored file. Because FIX=YES has been specified for the audit command, the error will be corrected. System Action: Audit processing continues. User Response: None. ANR4279E Audit command: Administrator administrator number assigned to more than just system authority class.
Explanation: A database audit process finds that an 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. System Action: Audit processing continues. User Response: Reissue the audit command and
Explanation: A database audit process finds the 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. System Action: Audit processing continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
327
ANR4283E ANR4291I
ANR4283E Audit command: Administrator administrator number assigned as an unrestricted storage administrator is also assigned as a restricted administrator for storage pool storage pool name. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4287E Audit command: Storage allocation error detected for volume volume name - It will be corrected.
Explanation: A database audit process finds the specified administrator is assigned as an unrestricted 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. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4284I Audit command: Administrator administrator number assigned as an unrestricted storage administrator is also assigned as a restricted administrator for storage pool storage pool name - restricted class entry will be deleted.
Explanation: A database audit process finds incorrect block allocation information for the specified storage volume; the error will be corrected. System Action: Audit processing continues. User Response: None. 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. System Action: Audit processing continues. User Response: Contact your service representative. ANR4289E Audit command: Multiple files allocated the same disk storage block on volume volume name.
Explanation: A database audit process finds the specified administrator is assigned as an unrestricted 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. System Action: Audit processing continues. User Response: None. ANR4285E Audit command: A data-integrity error was detected on a storage volume for object (Object.ID).
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. System Action: Audit processing continues. User Response: Contact your service representative. ANR4290I Audit command: License global attributes could not be found - they will be created.
Explanation: A database audit process found a 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. System Action: Audit processing continues. User Response: None. ANR4286E Audit command: A correctable storage allocation error detected for volume volume name.
Explanation: A database audit process cannot find the license global attributes. Because FIX=YES has been specified for the command, the information is corrected by the creation of the global attributes. System Action: Audit processing continues. User Response: None. ANR4291I Audit command: License global attributes could not be found.
Explanation: A database audit process cannot find the license global attributes. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
Explanation: A database audit process finds incorrect block allocation information for the specified storage volume; the error can be corrected. System Action: Audit processing continues.
328
IBM Tivoli Storage Manager: Messages
ANR4292I ANR4301I
ANR4292I Audit command: Invalid table active column encountered for license global attribute - the value will be corrected. ANR4297I Audit command: An invalid license node assignment entry was found for node node ID.
Explanation: A database audit process finds that the active column license global attribute is invalid. Because FIX=YES has been specified for the command, the active column is reset to a proper value. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process finds that the license node assignment entry is invalid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4298I Expiration thread already processing unable to begin another expiration process.
ANR4293I
Audit command: Invalid table active column encountered for license global attributes.
Explanation: A database audit process finds that the active column license global attribute is invalid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4294I Audit command: A license node assignment entry was not found for node node ID - an entry will be created.
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. System Action: Current expiration process continues. User Response: Use the QUERY PROCESS command to determine the status of the current expiration process. ANR4299I Audit command: Invalid audit interval encountered for license global attribute the value will be set to the default.
Explanation: A database audit process cannot find the node assignment entry corresponding to the specified node. Since FIX=YES has been specified for the command, the required license entry will be created using default values. System Action: Audit processing continues. User Response: None. ANR4295I Audit command: A license node assignment entry was not found for node node ID.
Explanation: A database audit process finds that the 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. System Action: Audit processing continues. User Response: None. ANR4300I Audit command: Invalid audit interval encountered for license global attributes.
Explanation: A database audit process cannot find the node assignment entry corresponding to the specified node. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4296I Audit command: An invalid license node assignment entry was found for node node ID - the entry will be deleted.
Explanation: A database audit process finds that the audit interval license global attribute is invalid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4301I Audit command: Invalid last audit date encountered for license global attribute the value will be set to 0.
Explanation: A database audit process finds that the license node assignment entry is invalid. Because FIX=YES has been specified for the command, the node entry is deleted. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process finds that the last audit date license global attribute is invalid. Because FIX=YES has been specified for the command, the last audit date is set to 0. The next execution of AUDIT LICENSES will set a new last audit date. System Action: Audit processing continues.
Chapter 3. Common and Platform Specfic Messages
329
ANR4302I ANR4311I
User Response: None. ANR4302I Audit command: Invalid last audit date encountered for license global attribute. ANR4307I Audit command: Auditing inventory external space-managed objects.
Explanation: A database audit process finds that the last audit date license global attribute is invalid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4303E Audit command: Inventory references for object(Object.ID) deleted.
Explanation: This message is displayed during a database audit and indicates that server information about external space-managed client objects is currently being examined by the database audit process. System Action: Audit processing continues. User Response: None. 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.
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: Audit processing continues. User Response: None. ANR4304E Audit command: object name missing entry for cluster cluster ID - cluster entries deleted.
Explanation: A database audit process finds that an 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. System Action: Audit processing continues. User Response: None. ANR4309I Audit command: External space-managed entry for node node ID and file space filespace ID is missing a corresponding space-managed object entry.
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. System Action: Audit processing continues. User Response: None. ANR4305E Audit command: object name missing entry for cluster cluster ID.
Explanation: A database audit process finds that an external space-managed entry is missing a corresponding space-managed entry. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4310I Audit command: Auditing inventory space-managed objects.
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. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4306I AUDITDB: Processed number of entries database entries (cumulative).
Explanation: This message is displayed during a database audit and indicates that server information about space-managed client objects is currently being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4311I Audit command: Object entry for space-managed object object.ID not found - entry will be created.
Explanation: This message indicates the number of database entries that have been processed during database audit processing. System Action: Database audit processing continues. User Response: None.
Explanation: A database audit process cannot find an object entry for the specified space-managed object. Because FIX=YES has been specified for the command, an object entry is created by using default values. System Action: Audit processing continues.
330
IBM Tivoli Storage Manager: Messages
ANR4312I ANR4320I
User Response: None. ANR4312I Audit command: Object entry for space-managed object object.ID not found. ANR4316I Audit command: Space-managed object (object ID) for node node ID and file space filespace ID is missing the corresponding external space managed entry.
Explanation: A database audit process cannot find an object entry for the specified backup object. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. 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 determines that the space-managed object entry is missing a corresponding external space-managed entry. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4317I Audit command: External 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. System Action: Audit processing continues. User Response: None. ANR4314I Audit command: Space-managed object (object ID) for node node ID and file space filespace ID has one or more incorrect fields.
Explanation: A database audit process determined 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. System Action: Audit processing continues. User Response: None. ANR4318I Audit command: External space-managed object (object ID) for node node ID and file space filespace ID has one or more incorrect fields.
Explanation: A database audit process determined that one or more field values for the specified space-managed object is not valid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4315I Audit command: Space-managed object (object ID) for node node ID and file space filespace ID is missing the corresponding external space managed entry - the entry will be created.
Explanation: A database audit process determined that one or more field values for the specified external space-managed object is not valid. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4319I Audit command: Space-managed object not found for object object.ID - object entry will be deleted.
Explanation: A database audit process determines that the space-managed object entry is missing a corresponding external space managed entry. Because FIX=YES was specified, the missing entry will be created. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process cannot find a space-managed object entry for the specified object. Because FIX=YES was specified the object entry will be deleted. System Action: Audit processing continues. User Response: None. ANR4320I Audit command: Space-managed object not found for object object.ID.
Explanation: A database audit process cannot find a space-managed object entry for the specified object. System Action: Audit processing continues.
Chapter 3. Common and Platform Specfic Messages
331
ANR4321I ANR4328W
User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4321I Audit command: Invalid copy type encountered for object object.ID - object found as an space-managed object correcting the invalid copy type ANR4325E Audit command: Management class class name in policy set set name, domain domain name does not have a valid AUTOMIGNONUSE value defined - the default value will be set.
Explanation: A database audit process encounters an invalid copy type for the specified object ID, but finds a corresponding space-managed object for the entry. Because FIX=YES has been specified for the command, the invalid copy type is corrected. System Action: Audit processing continues. User Response: None. ANR4322E Audit command: Management class class name in policy set set name, domain domain name does not have a valid space management technique defined.
Explanation: A database audit process finds a management class that does not have a valid value specified. Because FIX=YES was specified for the AUDITDB operation, the default AUTOMIGNONUSE value will be set for the management class specified. System Action: Audit processing continues. User Response: Refer to the DEFINE MGMTCLASS command in the Administrators Reference for valid values. ANR4326E Audit command: Management class class name in policy set set name, domain domain name does not have a valid MIGREQUIRESBKUP value specified.
Explanation: A database audit process finds a management class that does not have a valid value specified. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4323E Audit command: Management class class name in policy set set name, domain domain name does not have a valid space management technique defined - the default value will be set.
Explanation: A database audit process finds a management class that does not have a valid value specified. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4327E Audit command: Management class class name in policy set set name, domain domain name does not have a valid MIGREQUIRESBKUP value defined the default value will be set.
Explanation: A database audit process finds a management class that does not have a valid value specified. Because FIX=YES was specified for the AUDITDB operation, the default space management technique value will be set for the management class specified. System Action: Audit processing continues. User Response: Refer to the DEFINE MGMTCLASS command in the Administrators Reference for valid values. ANR4324E Audit command: Management class class name in policy set set name, domain domain name does not have a valid AUTOMIGNONUSE value specified.
Explanation: A database audit process finds a management class that does not have a valid value specified. Because FIX=YES was specified for the AUDITDB operation, the default MIGREQUIRESBKUP value will be set for the management class specified. System Action: Audit processing continues. User Response: Refer to the DEFINE MGMTCLASS command in the Administrators Reference for valid values. ANR4328W Audit command: Storage pool storage pool name, specified as a space management destination for management class management class name, policy set set name, domain domain name, does not exist.
Explanation: A database audit process finds a management class that does not have a valid value specified. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
Explanation: A database audit process encounters a 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.
332
IBM Tivoli Storage Manager: Messages
ANR4329I ANR4336W
System Action: Audit processing continues. User Response: After the audit command completes, use the DEFINE STGPOOL command to define the missing storage pool or the UPDATE MGMTCLASS command to update the management class to refer to an existing storage pool. ANR4329I Audit command: Inactive reference found for active backup entry (Object.ID) - the inactive reference will be deleted. 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 operation completes.
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. System Action: Audit processing continues. User Response: None. ANR4330I Audit command: Inactive reference found for active backup entry (Object.ID).
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. System Action: The administrator is asked whether to 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: A database audit process found that an active backup entry for the specified object has a corresponding inactive backup entry. System Action: Audit processing continues. User Response: None. ANR4331E command process terminated, no matching device classes.
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. System Action: The volumes are reconciled and invalid volumes are displayed. User Response: None. ANR4335I command (Inspect Only) process started, process ID process ID.
Explanation: The server did not find any device class names matching the specifications entered in the RECONCILE VOLUMES command. System Action: Server operation continues. User Response: Use the QUERY DEVCLASS command to determine which device classes are defined on the server and reissue the RECONCILE VOLUMES command. 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 operation completes.
Explanation: As the result of a RECONCILE VOLUMES command that specified FIX=NO, the process whose ID is displayed has begun reconciling the volumes associated with the given device class. System Action: The volumes are reconciled and inconsistent volumes are displayed. User Response: None. ANR4336W command process ended, process ID process ID.
Explanation: The RECONCILE VOLUMES command for the specified device class has ended. System Action: None. User Response: For complete details on the results of the RECONCILE VOLUMES command, examine the previous messages.
Explanation: During the execution of a RECONCILE VOLUMES command, any data a volume named would be unavailable to users. System Action: The administrator is asked whether to continue. User Response: Enter 'Y' to reconcile the volumes or 'N' to stop the process.
Chapter 3. Common and Platform Specfic Messages
333
ANR4337W ANR4346I
ANR4337W command process terminated - process canceled. ANR4342W command process terminated - lock conflict detected.
Explanation: During processing of a RECONCILE VOLUMES command, the process performing the reconcile was canceled. System Action: The RECONCILE VOLUMES command is ended. User Response: None. ANR4338W command process terminated - sufficient recovery log space is not available.
Explanation: During processing of a RECONCILE VOLUMES command, the source server cannot obtain a required lock. System Action: The RECONCILE VOLUMES command is ended. User Response: Reissue the RECONCILE VOLUMES command. ANR4343W command process terminated - internal server error detected.
Explanation: During processing of a RECONCILE VOLUMES command, the source server does not have sufficient recovery log space to continue. System Action: The RECONCILE VOLUMES command is ended. User Response: If necessary, make more recovery log space available to the source server. ANR4339W command process terminated - sufficient database space is not available.
Explanation: During processing of a RECONCILE VOLUMES command, an internal server error occurs on the source server. System Action: The RECONCILE VOLUMES command is ended. User Response: Contact your service representative. ANR4344I command started for device class device class (process ID process ID).
Explanation: During processing of a RECONCILE VOLUMES command, the source server does not have sufficient database space to continue. System Action: The RECONCILE VOLUMES command is ended. User Response: If necessary, make more database space available to the source server. ANR4340W command process terminated - thread resource not available.
Explanation: The RECONCILE VOLUMES process whose ID is displayed has started reconciling volumes associated with the given device class. System Action: The volumes are reconciled and inconsistent volumes are displayed. User Response: None. 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.
Explanation: During processing of a RECONCILE VOLUMES command, the source server cannot start a thread for the reconcile process. System Action: The RECONCILE VOLUMES command is ended. User Response: Reissue the RECONCILE VOLUMES command. If the error persists, it may indicate a shortage of source server memory. ANR4341W command process terminated - sufficient memory is not available.
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 or deleted are displayed. System Action: None. User Response: For complete details on the results of 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: During processing of a RECONCILE VOLUMES command, the source server does not have enough memory available to complete the command. System Action: The RECONCILE VOLUMES command is ended. User Response: If necessary make more memory available to the source server.
Explanation: The RECONCILE VOLUMES process whose ID is displayed has finished reconciling volumes associated with the given device class. The number of
334
IBM Tivoli Storage Manager: Messages
ANR4352I ANR4357W
volumes reconciled and the number of invalid volumes found are displayed. System Action: None. User Response: For complete details on the results of 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 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 Explanation: This message is displayed in response to a QUERY PROCESS command, and indicates that a reconciliation process is attempting to obtain volume information from the shown server. System Action: The reconciliation process continues. User Response: None. ANR4353I Cancel in progress command: Volume volume name not valid, target server missing corresponding entry for source server.
Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on the source server and it has no matching volume on the target server. System Action: The reconciliation process continues. User Response: The database on either the source or target server has been regressed by either an RESTORE DATABASE operation or some system facility external 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 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 command: Volume volume name not valid, target server volume refers to device class device class that does not exist on the source server.
Explanation: This message is displayed in response to a QUERY PROCESS command, and indicates that a reconciliation process has been canceled. The process will end shortly. System Action: The reconciliation process terminates and server operation continues. User Response: None. ANR4354W command: Source server not authorized to reconcile target server server name.
Explanation: During processing of a RECONCILE VOLUMES command, the source server was not permitted to reconcile volume on the shown target server. System Action: The reconciliation process continues. User Response: If the source server should have 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.
Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on the target server and it is associated with the device class shown. The source server has NO corresponding device class. System Action: The reconciliation process continues. User Response: The database on either the source or target server has been regressed by either an RESTORE DATABASE operation or some system facility external to the server. Investigate the action that caused one or both of the databases to be regressed to their current condition. If a newer database image exist for that server, consider restoring the server to that point in 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
Chapter 3. Common and Platform Specfic Messages
Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was reported by the target server and it has no matching volume on the source server. System Action: The reconciliation process continues.
335
ANR4358W ANR4361W
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 command: Volume volume name not valid, the attributes of the volume on target server do not match the attributes on the source server. 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. ANR4360W command: Volume volume name not valid, the type of the volume on target server does not match the type on the source server.
Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on both the source and target server, but the attributes describing the volume does not match. System Action: The reconciliation process continues. 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 image exist for that server, consider restoring the server to that point in time. If the condition of the database on each server is acceptable, additional actions will have to be taken because RECONCILE VOLUMES FIX=YES is unable to correct this situation. 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. ANR4359W command: Volume volume name not valid, the size of the volume on target server does not match the size on the source server.
Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on 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. System Action: The reconciliation process continues. User Response: The database on either the source or target server has been regressed by either an RESTORE DATABASE operation or some system facility external 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 image exists for that server, consider restoring the server to that point in time. If the condition of the database on each server is acceptable, additional actions will have to be taken because RECONCILE VOLUMES FIX=YES is unable to correct this situation. These actions may have to be performed on one or both servers. Use the QUERY 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 command: Volume volume name not valid, the target server has reported damage to all or part of the volume.
Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on both the source and target server, but the size of the volume does not match. System Action: The reconciliation process continues. User Response: The database on either the source or target server has been regressed by either an RESTORE DATABASE operation or some system facility external 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 image exist for that server, consider restoring the server to that point in time. If the condition of the database on each server is
Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on both the source and target server, but the target server has reported damage to all or part of the volume. System Action: The reconciliation process continues.
336
IBM Tivoli Storage Manager: Messages
ANR4362W ANR4368I
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. ANR4365W command: Prefix for volume volume name does not match the device class prefix.
Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on 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. System Action: The reconciliation process continues. 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.
Explanation: As the result of a RECONCILE VOLUMES command that specified FIX=YES, the volume shown whose information is displayed is deleted from the target server. System Action: The volume is deleted. User Response: None. ANR4363W command: Volume volume name access changed to access mode.
Explanation: As the result of a RECONCILE 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. User Response: None. ANR4367E Audit command: A storage volume containing file data cannot be located file data may not be accessible.
Explanation: As the result of a RECONCILE VOLUMES command that specified FIX=YES, the access mode of the source volume has been changed to the value shown. System Action: The volumes access mode is changed. 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. ANR4364W command: Unable to connect to target server server name.
Explanation: This message is displayed during a database audit and indicates that the storage volume containing a files data cannot be located or is not defined. System Action: Audit processing continues. User Response: Reissue the audit command with 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 Audit command: Attributes for group group.ID and member member.ID are not correct - the attributes are corrected.
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.
Explanation: A database audit process determines that 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. System Action: Audit processing continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
337
ANR4369I ANR4375E
ANR4369I Audit command: Attributes for group group.ID and member member.ID are not correct. password on the target server. Retry the failing operation. ANR4373E Session rejected by target server server name, reason: rejection reason.
Explanation: A database audit process determines that attributes for the specified group ID and member ID do not match attributes for the corresponding primary backup object. System Action: Audit processing continues. 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 open a session with the shown target server. The session was rejected for the indicated reason. System Action: The operation fails. User Response: Check both the source server and the target server for any additional messages that might 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. ANR4374E Session failure, source server detected an internal error.
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. System Action: The operation fails. 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 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. System Action: The operation fails. User Response: Issue the RECONCILE VOLUMES command to determine the problem. If possible, correct the problem and retry the failing operation. ANR4372E The password on the source server does not match the password on target server server name.
Explanation: The source server ends the session because an internal logic error is detected. System Action: The source server ends the session and continues operation. 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. ANR4375E Session failure, source server has insufficient memory.
Explanation: The source server has attempted to 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. System Action: The operation fails. 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
Explanation: The source server ends the session because sufficient memory (virtual memory) is not available.
338
IBM Tivoli Storage Manager: Messages
ANR4376E ANR4383E
System Action: The source server ends the session and continues operation. 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. ANR4376E Session failure, target server server name is locked on the source server. 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.
Explanation: The source server ends the session because shown target server is locked from source server access. System Action: The source server ends the session and continues operation. User Response: Before the source server is permitted to access the target server, a properly authorized administrator must unlock the target server. ANR4377E Session failure, target server server name is not defined on the source server.
Explanation: The source server has attempted to update its server validation key on the target server. An error occurred that prevented the source server from updating the target server. System Action: The operation fails. 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. ANR4381E The source server was unable to register with target server server name.
Explanation: The source server ends the session because shown target server is not defined on the source server. System Action: The source server ends the session and continues operation. User Response: Before the source server is permitted to access the target server, the target server must be properly defined. ANR4378E For device class device class, the retry of a session with target server server name has timed out.
Explanation: The source server has attempted to register with the shown target server. An error occurred that prevented the source server from registering with the target server. System Action: The operation fails. 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.
Explanation: The source server has attempted to 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: Determine it the target server is having a problem or considering increasing the RETRYPERIOD value. ANR4379E The source server was unable to update the password on target server server name.
Explanation: The source server ends the session because the shown target server has provided policy information which is incomplete. The missing policy object is shown. System Action: The source server ends the session and continues operation. 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 Session failure, target server server name has aborted current transaction; reason: abort reason.
Explanation: The source server has attempted to update the target password. An error occurred that prevented the source server from updating the target server. System Action: The operation fails. 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
Explanation: The source server ends the session because the shown target server has aborted the current
Chapter 3. Common and Platform Specfic Messages
339
ANR4384E ANR4391I
transaction for the given reason. System Action: The source server ends the session and continues operation. User Response: Check both the source server and the target server for any additional messages that might further describe the reason the transaction was aborted. Retry the failing operation. ANR4384E Node node name is not allowed to establish a session as a target server. System Action: Server operation continues. 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.
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. System Action: The operation fails. 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 Session retry in progress with target server server name.
Explanation: The CANCEL EXPIRATION command was issued but there were no expiration processes currently running. System Action: Server operation continues. User Response: None. ANR4389I Expiration process cancelled.
Explanation: The CANCEL EXPIRATION command was issued and successfully cancelled the current process. System Action: Server operation continues. User Response: None. ANR4390E CANCEL EXPIRATION failed - unable to cancel expiration process.
Explanation: The source server is attempting to re-establish a session with the shown target server. Session retry processing occurs when the source server has lost the connection with a target server and a RETRYPERIOD value is specified, System Action: The source server attempts to contact the target server. User Response: Determine if the target server is having a problem and considering canceling the operation on the source server or correcting the problem with the target server. ANR4386I Session retry was successful for target server server name.
Explanation: The CANCEL EXPIRATION command was issued but encountered an error. Due to this error, the command was unable to cancel the process. System Action: Server operation continues. 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. ANR4391I 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: The source server has re-establish a session with the shown target server. System Action: Source server processing continues. User Response: None. ANR4387E Session session number for node node name (client platform) refused - node name not registered as TYPE=CLIENT.
Explanation: Expiration processing is currently evaluating information for the node, filespace, domain name, and management class specified for the file type indicated. System Action: Server operation continues. User Response: None.
Explanation: The server refuses a request to start a 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.
340
IBM Tivoli Storage Manager: Messages
ANR4395I ANR4405I
ANR4395I Audit command: Invalid node type encountered for node node name. System Action: Server operation continues. User Response: None. ANR4402I Database Dump command: Database update activity resumed
Explanation: A database audit process encounters an invalid node type for the node indicated, and FIX=YES was not specified. System Action: Audit processing continues. 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: Database update activities that were suspended by the database dump process are restarted. System Action: Server operation continues. User Response: None. ANR4403I Database Load command: Database dump image is consistent - a database audit (AUDITDB) will NOT be required if this load completes successfully.
Explanation: A database audit process encounters an invalid node type for the node indicated. Because FIX=YES has been specified, the audit function sets the nodes type to the default value. System Action: Audit processing continues. 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 after the audit command has completed. ANR4397E Audit command: An invalid data format was encountered for storage pool storage pool name.
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. System Action: Server database load processing continues. User Response: None ANR4404I Database Load command: Loaded a consistent dump image - a database audit (AUDITDB) is NOT required.
Explanation: A database audit process encounters an invalid data format for the specified storage pool. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the attribute can be corrected. ANR4398E Audit command: An invalid data format was encountered for storage pool storage pool name - the data format will be assigned its default value.
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. System Action: Server database load processing completes. User Response: None. ANR4405I Database Load command: Loaded an inconsistent dump image - a database audit (AUDITDB) IS REQUIRED with FIX=YES.
Explanation: A database audit process encounters an 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: 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.
Explanation: Expiration processing is currently evaluating information for backup sets for the node specified.
Chapter 3. Common and Platform Specfic Messages
341
ANR4406I ANR4415I
ANR4406I Audit command: Client option Client option name sequence number option sequence number is not a member of an optionset. The option will be deleted. User Response: If possible, correct the condition that stopped the expansion. If the problem persists, contact your service representative. ANR4411I Triggered space expansion retry delay ended; checking space trigger criteria.
Explanation: A database audit process found that the specified client option does not have a corresponding optionset. The option is deleted. System Action: Audit processing continues. User Response: None. ANR4407I Audit command: Client option Client option name sequence number option sequence number is not a member of an optionset.
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. User Response: None. ANR4412I Data Base and Recovery Log Space expansion triggered.
Explanation: A database audit process found that the specified client option does not have a corresponding optionset. The option is deleted. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4408I Audit command: Client option Client option name sequence number option sequence number in optionset optionset name is not a valid option. The option will be deleted.
Explanation: A triggered space expansion had started. System Action: Space expansion begins. User Response: None. ANR4413I Recovery Log Space expansion Is Needed, megabytes needed Megabytes needed.
Explanation: A database audit process found that the specified client option is not a valid option. The option is deleted. System Action: Audit processing continues. User Response: None. ANR4409I Audit command: Client option Client option name sequence number option sequence number in optionset option set is not a valid option.
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. User Response: None. ANR4414I Data Base Space expansion Is Needed, megabytes needed Megabytes needed.
Explanation: A database audit process found that the specified client option is not a valid option. System Action: Audit processing continues. User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected. ANR4410I Triggered space expansion will be retried in number of seconds seconds.
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. User Response: None. ANR4415I Data Base and Recovery Log Space Expansion Completed.
Explanation: Because of a problem encountered 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. System Action: The system waits for the specified period and then retries to expand the database and/or recovery log.
Explanation: A triggered space expansion had completed. System Action: Normal operations resume. User Response: None.
342
IBM Tivoli Storage Manager: Messages
ANR4416W ANR4421W
ANR4416W Unable to Determine Maximum Number of Data Base Volume Copies, rc=return code. ANR4419W Unable to Determine Maximum Number of Recovery Log 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. System Action: Server operation continues. No 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.
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. System Action: Server operation continues. No 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.
Explanation: The Data Base Space Trigger was in the processing of expanding the data base by creating new database volumes. In doing so, database copy volumes are created for mirroring. The indicated database copy 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. 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. ANR4418W Unable to Define Data Base Copy Volume Data Base Copy Volume for volume Data Base Volume.
Explanation: The Recovery Log Space Trigger was in the processing of expanding the recovery log by 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. 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. ANR4421W Unable to Define Recovery Log Copy Volume Recovery Log Copy Volume for volume Recovery Log Volume.
Explanation: The Data Base Space Trigger was in the processing of expanding the data base by creating new database volumes. In doing so, database copy volumes are created for mirroring. The indicated database copy volume was created for the primary database volume named, but could be registered with the server. System Action: Server operation continues. A database copy volumes is not registered for the indicated primary volume. The database copy volume still exists on the system. User Response: Use the Query DBVOL command to determine if your database volume configuration is satisfactory. You may use the DEFINE DBCOPY command to retry the definition of the database volume copy, if necessary.
Explanation: The Recovery Log Space Trigger was in the processing of expanding the recovery log by 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. System Action: Server operation continues. A recovery log copy volume is not registered for the indicated primary volume. The recovery log copy volume still exists on the system. 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 retry the definition of the recovery log volume copy, if necessary.
Chapter 3. Common and Platform Specfic Messages
343
ANR4422I ANR4428W
ANR4422I AUDITDB: Insufficient database space to optimze audit processing. ANR4426W Recovery Log can no longer be Expanded by the Space Trigger.
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: 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. System Action: Server operation continues, but the recovery log is not automatically expanded. No additional recovery log expansion will occur as a result of the recovery log space trigger. User Response: None. You may review the space trigger settings and use the UPDATE SPACETRIGGER LOG command to adjust space trigger values. You may also backup the data base and/or setup a database backup trigger to cause the database to be backed up more often. Backing up the database will decrease the 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.
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. System Action: Server operation continues. No additional database space expansion will occur as a result of the database space trigger. User Response: None. You may review the space trigger settings and use the UPDATE SPACETRIGGER DB command to adjust space trigger values. ANR4425W Recovery Log has reached Maximum Size in Space Trigger.
Explanation: The Recovery Log Space Trigger was in the processing of expanding the recovery log by 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). System Action: Server operation continues. User Response: Use the QUERY LOGVOL command to determine if your volume configuration is satisfactory. You may use the DEFINE LOGCOPY command to define additional copy volumes, if necessary. You may use the DELETE LOGCOPY command to delete unnecessary copy volumes. ANR4428W One or more Data Base Volumes differs in number of copy volumes.
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. System Action: Server operation continues. No additional recovery log expansion will occur as a result of the recovery log space trigger. User Response: None. You may review the space trigger settings and use the UPDATE SPACETRIGGER LOG command to adjust space trigger values.
Explanation: The Data Base Space Trigger was in the processing of expanding the data base by creating new 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). System Action: Server operation continues. User Response: Use the Query DBVOL command to determine if your volume configuration is satisfactory.
344
IBM Tivoli Storage Manager: Messages
ANR4429W ANR4435I
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. 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. System Action: Server operation continues, but the 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. User Response: None. You may review the space trigger settings and use the UPDATE SPACETRIGGER 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 Recovery Log Space Trigger was in the processing of expanding the recovery log by creating new recovery log volumes. The indicated recovery log volume was created, but could not be registered with the server. System Action: Server operation continues. A recovery 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 determine if your recovery log volume configuration is satisfactory. You may use the DEFINE LOGCOPY command to retry the definition of the recovery log volume copy, if necessary. There will be an additional message in the activity log prior to this message indicating the reason for the failure. ANR4430W Unable to Define Data Base Volume Data Base Volume.
Explanation: The Data Base Space Trigger was in the processing of expanding the data base by creating new database volumes. The indicated database volume was created, but could not be registered with the server. System Action: Server operation continues. A database volume is not registered with the server. The database volume still exists on the system. User Response: Use the Query DBVOL command to determine if your database volume configuration is satisfactory. You may use the DEFINE DBVOLUME command for the database volume named, to retry the definition of the database volume copy, if necessary. There will be an additional message in the activity log prior to this message indicating the reason for the failure. ANR4431I Recovery Log 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. User Response: None. ANR4434E Audit command: Password expiration found for unknown client node node name.
Explanation: A database audit process finds a password expiration period for a client node, but the client node is not defined correctly in the server database. System Action: Audit processing continues. 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. ANR4435I Audit command: Password expiration period deleted for unknown client node node name.
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.
Explanation: A database audit process finds a 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. System Action: Audit processing continues.
Chapter 3. Common and Platform Specfic Messages
345
ANR4436E ANR4443I
User Response: None. ANR4436E Audit command: Invalid password expiration password expiration period for client node node name. User Response: None. ANR4440E Audit command: Invalid password expiration password expiration period for administrator administrator name.
Explanation: A database audit process finds an invalid password expiration period for a client node. System Action: Audit processing continues. 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. ANR4437I Audit command: Invalid password expiration period password expiration period deleted for client node node name.
Explanation: A database audit process finds an invalid password expiration period for an administrator. System Action: Audit processing continues. 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. ANR4441I Audit command: Invalid password expiration period password expiration period deleted for administrator administrator name.
Explanation: A database audit process finds an invalid password expiration period for a client node. Because FIX=YES has been specified for the audit command, the audit function deletes the password expiration period, causing the default, global password expiration period to take effect for the client node. System Action: Audit processing continues. User Response: After the AUDIT command completes, use the QUERY NODE command to examine the node that was updated. Use the UPDATE NODE command to set the correct password expiration period for the node. ANR4438E Audit command: Password expiration found for unknown administrator administrator name.
Explanation: A database audit process finds an invalid password expiration period for an administrator. Because FIX=YES has been specified for the audit command, the audit function deletes the password expiration period, causing the default, global password expiration period to take effect for the administrator. System Action: Audit processing continues. User Response: After the AUDIT command completes, 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. ANR4442E Audit command: Extended attribute extended attribute type is not a valid attribute type.
Explanation: A database audit process finds a password expiration period for an administrator, but the administrator is not defined correctly in the server database. System Action: Audit processing continues. 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. ANR4439I Audit command: Password expiration period deleted for unknown administrator administrator name.
Explanation: A database audit process finds an extended attribute type that is not supported. System Action: Audit processing continues. 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. ANR4443I Audit command: Invalid extended attribute extended attribute type has been deleted.
Explanation: A database audit process finds a 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 password expiration period. System Action: Audit processing continues.
Explanation: A database audit process finds an extended attribute type that is not supported. Because FIX=YES has been specified for the audit command, the audit function deletes extended attribute. System Action: Audit processing continues. User Response: None.
346
IBM Tivoli Storage Manager: Messages
ANR4444W ANR4453E
ANR4444W Command: Input volume volume name cannot be processed. ANR4449E Audit command: An invalid data mover attribute was encountered for data mover 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: A database audit process encountered an invalid data mover attribute for the specified data mover. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the attribute can be corrected. ANR4450E Audit command: An invalid data mover attribute was encountered for data mover data mover name - the data mover entry will be removed.
Explanation: Determines if context reporting will be generated when an ANR9999D error occures. This is turned on or off with the SET CONTEXTmessaging command. System Action: None. User Response: None. ANR4446I Audit command: Auditing address definitions.
Explanation: A database audit process encounters an invalid data mover attribute for the specified data mover. System Action: Because FIX=YES has been specified 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. ANR4451E Audit command: An invalid disk attribute was encountered for disk name.
Explanation: This message is displayed during a database audit and indicates that the name address definitions are being examined by the database audit process. System Action: Audit processing continues. User Response: None. ANR4447E Audit command: An invalid data mover type was encountered for data mover name.
Explanation: A database audit process encountered an invalid disk attribute for the specified disk. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the attribute can be corrected. ANR4452E Audit command: An invalid disk attribute was encountered for disk name - the disk entry will be removed.
Explanation: A database audit process encounters an invalid data mover type for the specified data mover. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the attribute can be corrected. ANR4448E Audit command: An invalid data mover type was encountered for data mover datamover name - the data mover entry will be removed.
Explanation: A database audit process encounters an invalid disk attribute for the specified disk. Because FIX=YES has been specified for the command, the disk entry will be removed. System Action: Audit processing continues. 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
Explanation: A database audit process encounters an invalid data mover type for the specified data mover. System Action: Because FIX=YES has been specified 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.
Explanation: A database audit process encountered an invalid source attribute in a path definiton with the specified source name and destination name. System Action: Audit processing continues.
Chapter 3. Common and Platform Specfic Messages
347
ANR4454E ANR4461E
User Response: Reissue the audit command with FIX=YES so that the attribute can be corrected. ANR4454E Audit command: An invalid source attribute was encountered for source name and destination destination name the path entry will be removed. function specifying FIX=YES so that the error can be corrected. ANR4458I Audit command: KEEPMP setting deleted for unknown client node node name.
Explanation: A database audit process encounters an 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 entry will be removed. System Action: Audit processing continues. 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 after the audit command has completed. ANR4455E Audit command: An invalid destination attribute was encountered for source name and destination destination name
Explanation: A database audit process found a KEEPMP setting 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 has deleted the KEEPMP setting. System Action: Audit processing continues. User Response: None. ANR4459E Audit command: Invalid KEEPMP setting KEEPMP setting for client node node name.
Explanation: A database audit process found an invalid KEEPMP setting for a client node. System Action: Audit processing continues. 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. ANR4460I Audit command: Invalid KEEPMP setting KEEPMP setting deleted for client node node name.
Explanation: A database audit process encountered an invalid destination attribute in a path definiton with the specified source name and destination name. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES so that the attribute can be corrected. ANR4456E Audit command: An invalid destination attribute was encountered for source name and destination destination name the path entry will be removed.
Explanation: A database audit process encounters an invalid destination attribute in a path definition with the specified source name and destination name. Because FIX=YES has been specified for the command, the path entry will be removed. System Action: Audit processing continues. 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 after the audit command has completed. ANR4457E Audit command: KEEPMP found for unknown client node node name.
Explanation: A database audit process found an invalid KEEPMP setting for a client node. Because FIX=YES has been specified for the audit command, the audit function has deleted the KEEPMP setting, causing the default, KEEPMP setting to take effect for the client node. System Action: Audit processing continues. User Response: After the AUDIT command completes, use the QUERY NODE command to examine the node that was updated. Use the UPDATE NODE command to set the correct KEEPMP setting for the node. ANR4461E Audit command: TCP name, address and GUID found for unknown client node node name.
Explanation: A database audit process found a KEEPMP setting for a client node, but the client node is not defined correctly in the server database. System Action: Audit processing continues. User Response: If the audit command has not been issued with FIX=YES specified, reissue the audit
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. System Action: Audit processing continues. 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.
348
IBM Tivoli Storage Manager: Messages
ANR4462I ANR4471E
ANR4462I Audit command: TCP name, address and GUID deleted for unknown client node node name. ANR4466I Audit command: An incorrect transaction group was found for node node name. This information will be corrected.
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. Because FIX=YES has been specified for the audit command, the audit function deletes the TCP name, address and GUID. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process encounters 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. System Action: Audit processing continues. User Response: None. ANR4467E Audit command: Data Path Type Path was found for unknown client node node name.
ANR4463E
Audit command: Invalid TCP name, address or GUID length invalid length for client node node name.
Explanation: A database audit process found an invalid TCP name, address or globally unique identifer length for a client node. System Action: Audit processing continues. 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. ANR4464I Audit command: Invalid TCP name, address or GUID length invalid length deleted for client node node name.
Explanation: A database audit process found a Data Path setting for a client node, but the client node is not defined correctly in the server database. System Action: Audit processing continues. 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. ANR4468I Audit command: The Data Path Type Path setting was deleted for unknown client node node name.
Explanation: A database audit process found an 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. System Action: Audit processing continues. User Response: After the AUDIT command completes, use the QUERY NODE command to examine the node that was updated. The values should be blank. ANR4465I Audit command: An incorrect transaction group size was found for 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 FIX=YES has been specified for the audit command, the audit function has deleted the KEEPMP setting. System Action: Audit processing continues. User Response: None. ANR4471E Audit command: Invalid TCP address ( server-prompted scheduling ) or length invalid length for client node node name.
Explanation: A database audit process found an invalid TCP address or length for a client nodes server-prompted scheduling.. System Action: Audit processing continues. 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.
Explanation: A database audit process encounters invalid information used for controlling the transaction group size for the node indicated. System Action: Audit processing continues. 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.
Chapter 3. Common and Platform Specfic Messages
349
ANR4472I ANR4478I
ANR4472I Audit command: Invalid TCP name or length for server-prompted scheduling.invalid length deleted for client node node name. 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. ANR4476I Audit command: Node missing from session initiation value for server-prompted scheduling. Attribute deleted for client node node name.
Explanation: A database audit process found an invalid TCP name or length for a client nodes server-prompted scheduling attributes. Because FIX=YES has been specified for the audit command, the audit function sets the TCP information to blank. The values must be reset with the UPDATE NODE command. System Action: Audit processing continues. User Response: After the AUDIT command completes, use the QUERY NODE command to examine the node 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 client node addressing information for a client nodes server-prompted scheduling but the node definition was missing. Because FIX=YES has been specified for the audit command, the audit function deletes the value. The information must be redefined with the REGISTER or UPDATE NODE commands. System Action: Audit processing continues. User Response: After the AUDIT command completes, use the QUERY NODE command to examine the node that was updated. ANR4477E Audit command: An invalid data path type path setting was found 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. System Action: Audit processing continues. 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. ANR4474I Audit command: Node missing from session initiation value for server-prompted scheduling. Attribute deleted for client node node name.
Explanation: A database audit process found an incorrect data path setting for a client node. System Action: Audit processing continues. 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. ANR4478I Audit command: An incorrect data path type path setting was deleted for client node node name.
Explanation: A database audit process found a value for a client nodes server-prompted session iniiating attributes, but the node definition was mising. Because FIX=YES has been specified for the audit command, the audit function sets the value to the default. The attribute must be redefined with the REGISTER or UPDATE NODE commands. System Action: Audit processing continues. User Response: After the AUDIT command completes, use the QUERY NODE command to examine the node that was updated. ANR4475E Audit command: Node missing from client address attribute for client node node name.
Explanation: A database audit process found an invalid data path setting for a client node. Because FIX=YES has been specified for the audit command, the audit function has deleted the Data Path setting, causing the default Data Path setting to take effect for the client node. System Action: Audit processing continues. User Response: After the AUDIT command completes, use the QUERY NODE command to examine the node that was updated. Use the UPDATE NODE command to set the correct data path setting for the node.
Explanation: A database audit process found client node addressing information for a client nodes server-prompted scheduling but the node definition was missing. System Action: Audit processing continues.
350
IBM Tivoli Storage Manager: Messages
ANR4479I ANR4488I
ANR4479I Extraneous or incorrect entry found for a backup group member. ANR4484I Node node name issued command: Delete Access copy type file space namehigh-level addresslow-level address authorized node name ,authorized owner name.
Explanation: An extraneous or incorrect entry was found for a member of a backup group. System Action: Audit processing continues. User Response: Issue the AUDITDB command again, using the FIX=YES parameter. ANR4480I Extraneous or incorrect entry fixed for a backup group member.
Explanation: The DELETE ACCESS command completed. System Action: Processing continues. User Response: None. ANR4485I A storage pool space trigger has been defined and enabled for storage pool storage pool name.
Explanation: An extraneous or incorrect entry was 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. System Action: Audit processing continues. 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
Explanation: A storage pool space trigger has been defined with a DEFINE SPACETRIGGER command for the specified storage pool. System Action: None. User Response: None. ANR4486I A default storage pool space trigger has been defined and enabled.
Explanation: An extraneous or incorrect entry was found for a proxy association. System Action: Audit processing continues. User Response: Issue the AUDITDB command again, using the FIX=YES parameter. ANR4482I Command: Extraneous or incorrect entry found for a proxy association. Target: node_id_1 Agent: node_id_2
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. System Action: None. User Response: None. ANR4487I The storage pool space trigger is defined for storage pool storage pool name, but is disabled.
Explanation: An extraneous or incorrect entry was found for a proxy association. The entry will be removed. System Action: Audit processing continues. 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: 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. System Action: None. User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command to set the space expansion percentage to a value greater than 0. ANR4488I The default storage pool space trigger is defined, but it is disabled.
Explanation: The SET ACCESS command completed. System Action: Processing continues. User Response: None.
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. System Action: None. User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command to set the space
Chapter 3. Common and Platform Specfic Messages
351
ANR4489I ANR4496E
expansion percentage to a value greater than 0. ANR4489I The storage pool space trigger has been deleted for storage pool storage pool name. ANR4493I The storage pool space trigger is updated, but disabled for storage pool storage pool name.
Explanation: A DELETE SPACETRIGGER command 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. System Action: None. User Response: None. ANR4490I The default storage pool space trigger has been deleted.
Explanation: An UPDATE SPACETRIGGER command 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. System Action: None. User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command with the SPACEexpansion parameter to set a value greater than zero. ANR4494I The default storage pool space trigger is updated, but disabled.
Explanation: A DELETE SPACETRIGGER command 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. System Action: None. User Response: None. ANR4491I The storage pool space trigger is updated and enabled for storage pool storage pool name.
Explanation: An UPDATE SPACETRIGGER command has successfully completed for the default storage pool space trigger. However, the space expansion percentage is currently set to 0, which disables the space trigger. System Action: None. User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command with the SPACEexpansion parameter to set a value greater than zero. ANR4495E Command: Storage pool space trigger is not defined.
Explanation: An UPDATE SPACETRIGGER command 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. System Action: None. User Response: None. ANR4492I The default storage pool space trigger is updated and enabled.
Explanation: The storage pool space trigger cannot be updated or deleted because it is not currently defined. 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. System Action: The server does not process the command. User Response: None. ANR4496E Command: Storage pool space trigger is already defined.
Explanation: An UPDATE SPACETRIGGER command has successfully completed for the default storage pool space trigger. The updated parameters specified on the command are used to automatically trigger space expansion for storage pools without a specific storage pool space trigger and which are associated with a devtype=FILE or devtype=DISK device class. System Action: None. User Response: None.
Explanation: The storage pool space trigger cannot be 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. System Action: The server does not process the command. User Response: Use the UPDATE SPACETRIGGER command to modify the indicated space trigger parameters.
352
IBM Tivoli Storage Manager: Messages
ANR4497E ANR4511E
ANR4497E Command: EXPansionprefix not valid for storage pool space trigger with storage pool Storage Pool. ANR4502W No files have been defined for automatically storing sequential volume history information.
Explanation: The storage pool space trigger cannot be defined with an EXPansionprefix parameter because the specified storage pool is not associated with a DISK-type device class. Sequential access storage pools use their associated directories for creating space when a space trigger is activated. System Action: The server does not process the command. User Response: Use the UPDATE SPACETRIGGER 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 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. System Action: Server operation continues. User Response: To have the server automatically record sequential volume history information to assist in server recovery, use the VOLUMEHISTORY option in the server options file to specify where history information should be written. If you update the options file, restart the server. ANR4503W Current date current date is earlier than the date when the server was started start date.
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. System Action: The server does not process the 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. ANR4500I Writing sequential volume history information to defined files.
Explanation: The server has detected that the current system date is an earlier date than the system date when the server was started. System Action: Processing continues. User Response: On the machine on which the server is running, verify that the system date is correct. ANR4510E Server could not write sequential volume history information to volume history 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. The files updated are those specified with the VOLUMEHISTORY option in the server options file. System Action: Server operation continues. User Response: None. ANR4501I Sequential volume history information successfully written to file name.
Explanation: While attempting to write sequential volume history information to defined history files, the server could not write to the file name specified. System Action: The server does not write volume history information to the file specified User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. After the problem has been corrected, use the BACKUP VOLHISTORY command to write sequential volume history information to the file. ANR4511E Volume history file volume history file name could not be opened.
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. System Action: Server operation continues. User Response: None.
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
Chapter 3. Common and Platform Specfic Messages
353
ANR4512E ANR4518E
history information to or read volume history information from the file specified User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. ANR4512E A database transaction failure was encountered in processing sequential volume history information. ANR4515E Sufficient recovery log space is not available for the server while processing sequential volume history information.
Explanation: While attempting to process sequential volume history information, the server finds that sufficient recovery log space is not available for updates. System Action: The operation fails. Usage for a sequential volume was not properly recorded for later reference. User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes by using the 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 process sequential volume history information, the server encountered a database transaction error. System Action: The operation fails. Usage for a sequential volume was not properly recorded for later reference. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. If this does not resolve the problem, contact your support representative. ANR4513E A database lock conflict was encountered in processing sequential volume history information.
Explanation: While attempting to read sequential volume history information from defined history files, the server finds that it cannot open any of the files defined in the server options file. System Action: The server does not read volume history information. If the current server task requires this information, the task ends. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to 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: While attempting to process sequential volume history information, the server encountered a database locking conflict. System Action: The operation fails. This usually means that usage for a sequential volume was not properly recorded for later reference User Response: Examine error messages that may have been displayed prior to this message and correct any 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 sequential volume history information.
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 Volume history file file name line line number does not have the proper format - read operation fails.
Explanation: While attempting to process sequential volume history information, the server found that sufficient database space was not available for updates. System Action: The operation fails. Usage for a sequential volume was not properly recorded for later reference. 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.
Explanation: The server is attempting to read from a volume history file and encounters a record that does not have the proper format.
354
IBM Tivoli Storage Manager: Messages
ANR4519W ANR4526E
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. ANR4519W Volume History File does not reflect latest Storage Agent Updates 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. System Action: Space expansion begins. User Response: None. ANR4524I Volume volume name defined in Storage Pool storage pool name as a result of storage pool triggered space exapnsion.
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. ANR4520I Storage Pool storage pool name is being skipped during a space allocation. A request for request amount megabytes was made but only available amount megabytes were available.
Explanation: A 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. System Action: Processing continues. User Response: None. ANR4525E Failure to define volume volume name in Storage Pool storage pool name. Return codereturn code.
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 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 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. System Action: Processing continues. 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. User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see Appendix B. Allocating Additional Server Memory.
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
Chapter 3. Common and Platform Specfic Messages
355
ANR4527W ANR4540E
ANR4527W Storage Pool Space trigger for storage pool name is disabled after volume definition failures expansion failures. Insufficient space for pool expansion. 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 failed to complete a storage pool expansion for the indicated storage pool. The number of failures in pool expansion is also displayed. System Action: Server processing continues but the storage pool is not expanded. The storage pool space trigger for the indicated storage pool is disabled. User Response: Allocate additional storage space to the server. For storage pools of device type FILE, additional directories may be added to the list of directories that the associated device class uses for storage. If this action is taken, the corresponding storage agent directories should be added via the UPDATE PATH command. The storage pool space trigger may be re-enabled with the UPDATE SPACETRIGGER STG STPOOL=xx command, where xx is the storage pool for which expansion has failed ( no space trigger parameters need be updated ). ANR4528W Storage Pool Space Expansion for storage pool name is disabled due to previous expansion failures. After addressing space requirements, an UPDATE SPACETRIGGER STG command must be issued to allow automatic stgpool expansion.
Explanation: The server 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 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 Audit command: Invalid device class device class id found in DevClass.Dirs table.
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 ). System Action: Server processing continues but the 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 ).
Explanation: A database audit process finds a non-existent device class or a device class with an invalid access strategy for a record in the Devclasses.Dirs table. System Action: Audit processing continues. 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
356
IBM Tivoli Storage Manager: Messages
ANR4541E ANR4549I
removed, review directories associated with Device classes and Paths with the following commands: QUERY DEVCLASS F=D QUERY PATH F=D ANR4541E Audit command: Invalid directory for device class device class id in DevClass.Dirs table. 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 ANR4544E Audit command: Invalid library for device class device class id in the DevClass.Dirs table.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. 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 ANR4542E Audit command: Invalid server for device class device class id in DevClass.Dirs table. The server name in the table is server name.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. User Response: If the FIX=YES parameter was specified, the database 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 ANR4545E Audit command: Invalid drive for device class device class id in the DevClass.Dirs table.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. 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 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.
Explanation: A database audit process finds a 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. System Action: Audit processing continues. User Response: If the FIX=YES parameter was specified, the database 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 ANR4549I Database dump command: A database dump is already in progress.
Explanation: A database audit process finds a 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. System Action: Audit processing continues.
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. System Action: Server operation continues. The requested database dump is not started.
Chapter 3. Common and Platform Specfic Messages
357
ANR4550I ANR4560I
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. 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. System Action: None. User Response: None. ANR4555I Database backup process process ID canceled.
Explanation: A full database backup process has completed. The output volumes used in this backup may be used during a database restore operation. System Action: None. User Response: None. ANR4551I Incremental database backup (process process ID) complete, number of database pages pages copied.
Explanation: The database backup process was canceled by an administrator with the CANCEL PROCESS command. System Action: The database backup process is ended. User Response: None. 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: An incremental database backup process has completed. The output volumes used in this backup may be used in conjunction with any preceding volumes in the backup series during a database restore operation. System Action: None. User Response: None. ANR4552I Full database backup triggered; started as process process ID.
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. System Action: The database backup process starts and server operation continues. User Response: The administrator may query the status of the database backup process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command. ANR4553I Incremental database backup triggered; started as process process ID.
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.
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. System Action: The database backup process starts and server operation continues. User Response: The administrator may query the status of the database backup process by using the
Explanation: Because of a problem encountered during a triggered database backup, the current backup stops but will be retried after the time period shown. System Action: The system waits for the specified period and then retries a database backup. User Response: If possible, correct the condition that stopped the database backup. If the problem persists, contact your service representative.
358
IBM Tivoli Storage Manager: Messages
ANR4561I ANR4572E
ANR4561I Triggered database backup retry delay ended; checking database backup trigger criteria. for the retry period to expire and then tries the database backup again. 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: Because a triggered database backup had been stopped due to a problem, the system waited before retrying. The retry wait period has ended, and the system can now retry the database backup. System Action: Database backup begins. User Response: None. ANR4562I Database backup criteria is no longer met; triggered database backup canceled.
Explanation: During database backup or restore processing, an error occurred because the specified device class is not defined. System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. A database restore is terminated. User Response: For database backup, make sure the specified device class is defined. For database restore processing, make sure the device class has a definition in a device configuration file that is pointed to in the server options file. ANR4571E Database backup/restore terminated insufficient number of mount points available for removable media.
Explanation: Because a triggered database backup had been stopped due to a problem, the system waited before retrying. The retry wait period has ended, and the system determined that the criteria for triggering a database backup was no longer met. System Action: The system waits until the database backup trigger criteria is met before triggering another database backup. User Response: None. 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. User Response: None. ANR4564I Unable to trigger database backup sufficient memory is not available.
Explanation: During database backup or restore, the server cannot allocate sufficient mount points for the volumes required. 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 ended. User Response: For database backup, make more mount points available if necessary. For database restore processing, make sure the device class has sufficient mount points defined in the device configuration information file that is pointed to in the server options file. ANR4572E Database restore terminated - excessive read errors encountered.
Explanation: A database backup was triggered, but there is not enough server memory available. System Action: The backup stops and the server waits for the retry period to expire and then tries the database backup again. User Response: If necessary, make more memory available to the server. ANR4565E Unable to trigger database backup thread resource not available.
Explanation: During database restore, read errors occur that prevent the restore from continuing. System Action: Database restore processing stops. User Response: Use a different device for the restore operation. If the problem persists, contact your service representative.
Explanation: A database backup was triggered, but the server cannot start a thread for the backup process. System Action: The backup stops and the server waits
Chapter 3. Common and Platform Specfic Messages
359
ANR4573E ANR4578E
ANR4573E Database backup terminated - excessive write errors encountered. 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. 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. User Response: For database backup, make more server database space available, if necessary. For database restore, make sure that the size of the online database is at least the same capacity as the database being restored. ANR4577E Database backup terminated - volume already in use.
Explanation: During database backup, write errors occur that prevent the backup from continuing. 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. User Response: If possible, determine and correct the cause of the write errors. If the problem cannot be corrected, contact your service representative. ANR4574E Database backup/restore terminated data transfer interrupted.
Explanation: During a database backup or restore operation, a data transfer operation has been interrupted and cannot be continued. 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 ended. User Response: If possible, determine and correct the cause of the interruption. If the problem cannot be corrected, contact your service representative. ANR4575E Database backup/restore terminated sufficient recovery log space is not available.
Explanation: During a database backup operation, a volume cannot be used because it is already defined in a storage pool, or has been previously used by an export, a database dump, or a database backup operation (as recorded in the volume history) or is in use by another process. 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. 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, a database dump, or a database backup operation as recorded in the server 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.
Explanation: During a database backup or restore operation, the server runs out of recovery log space. 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 more server recovery log space available, if necessary. For database restore, contact your service representative. ANR4576E Database backup/restore terminated sufficient database space is not available.
Explanation: During a database backup or restore operation, a required volume cannot be mounted, because the mount request was canceled. 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: 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,
Explanation: During a database backup or restore operation, the server runs out of database space. System Action: If the database backup was started with the BACKUP DB command, the database backup
360
IBM Tivoli Storage Manager: Messages
ANR4579E ANR4590I
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. 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, contact your service representative. ANR4583E Database backup terminated - output media full and scratch media could not be mounted.
Explanation: During a database backup or restore operation, the server cannot start a thread for the backup process. 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: 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 shortage of server memory. ANR4580E Database backup/restore terminated insufficient memory available.
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 server operation continues. User Response: Reissue the command and specify additional volume names on the command, or specify SCRATCH=YES. ANR4584E Database restore terminated incomplete input volume list.
Explanation: During a database backup or restore operation, there was not enough server memory available. 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: If necessary, make more memory available to the server. ANR4581W Database backup/restore terminated internal server error detected.
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.
Explanation: During a database backup or restore operation, the server encounters an internal error. 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: Contact your service representative. ANR4582E Database restore terminated - volume cannot be used.
Explanation: During a database restore operation, a volume has been mounted but cannot be used.
Explanation: During a DSMSERV DISPLAY DBBACKUPVOL command, the server displays the necessary information about a backup volume. System Action: Processing continues for all volumes in the given volume list.
Chapter 3. Common and Platform Specfic Messages
361
ANR4600I ANR4620I
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. ANR4611E Unable to restore database and roll forward updates - log mode was not previously set to ROLLFORWARD.
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. System Action: None. User Response: None. ANR4601E Incomplete volume list found for TODATE date time - retrying.
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. System Action: The server does not process the command. User Response: Reissue the command and specify a point in time (TODATE/TOTIME) for restore. ANR4612E Unable to restore database and roll forward updates.
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. 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: 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: 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. System Action: The server does not process the command. User Response: Reissue the command and specify a point in time (TODATE/TOTIME) for restore. ANR4619I Snapshot database backup series snapshot database backup series using device class device class.
Explanation: No volumes were found in the volume history files that meet the date and time parameters specified. System Action: The server does not process the command. User Response: Reissue the command with a valid date and time. ANR4610E Database volume DB volume name not found in current configuration.
Explanation: The device class used for the snapshot database backup is shown. System Action: None. User Response: None. ANR4620I Database backup series Backup series operation backup operation device class device class.
Explanation: The command specified the name of a nonexistent database volume. System Action: The server does not process the command. User Response: Reissue the command with a valid database volume name.
Explanation: The device class used for the backup is shown. System Action: None. User Response: None.
362
IBM Tivoli Storage Manager: Messages
ANR4621I ANR4636I
ANR4621I Database backup device class device class. 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 ANR4622I Volume volume sequence number in backup operation: volume name. Point-in-time database restore (no commit) complete.
Explanation: The device class for the backup is shown. System Action: None. User Response: None.
Explanation: The volume sequence and name for a full or an incremental database backup are shown. System Action: None. User Response: None. ANR4623I Stream stream number in backup operation volume volume sequence number in backup stream: Volume name.
Explanation: A point-in-time database restore with a specified list of volumes is complete. The database is not yet usable. System Action: None. 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 Starting point-in-time database restore to date date time.
Explanation: The stream number, volume sequence and name for a full or an incremental database backup are shown. System Action: None. User Response: None. ANR4630I Starting point-in-time database restore (commit).
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 the point in time of this backup. System Action: None. User Response: None. ANR4635I Point-in-time database restore complete, restore date date time.
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. System Action: None. User Response: If you inadvertently specified COMMIT=YES, restart the restore process from the beginning, starting with restoring the full backup (backup operation 0). ANR4631I Point-in-time database restore (commit) complete, restore date date time.
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. System Action: None. User Response: None. ANR4636I Starting roll-forward database restore.
Explanation: A point-in-time database restore with a specified list of volumes is complete. The date shown is the date to which the database has been restored. System Action: None. User Response: None. ANR4632I Starting point-in-time database restore (no commit).
Explanation: A roll-forward database restore has begun. When this restore is complete, the database will be returned to its most recent state. System Action: None. User Response: None.
Explanation: A point-in-time database restore with a specified list of volumes has started. When this restore is complete, the database will not yet be usable. System Action: None.
Chapter 3. Common and Platform Specfic Messages
363
ANR4637I ANR4646I
ANR4637I Roll-forward database restore complete. System Action: None. User Response: None. ANR4643I Processed number of log records log records.
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. System Action: None. User Response: None. ANR4638I Restore of backup series backup series number operation backup operation in series in progress.
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. System Action: None. User Response: None. ANR4644I A full backup will be required for the next database backup operation.
Explanation: During a DSMSERV RESTORE DB, the server displays the backup series and operation currently being restored. System Action: None. User Response: None. ANR4639I Restored number of pages restored of number of pages to restore from current backup operation database pages.
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. System Action: None. 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 The restore date reflects the most recent backup available up to the specified TODATE.
Explanation: Periodically, during a DSMSERV RESTORE DB, the server displays the number of pages restored from the current backup being restored. System Action: None. User Response: None. ANR4640I 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. System Action: None. User Response: None. ANR4641I Sequential media log redo pass in progress.
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. System Action: None. 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 number of megabytes megabytes.
Explanation: During a DSMSERV RESTORE DB, the process of committing incomplete database updates has begun. System Action: None. User Response: None. ANR4642I Sequential media log undo pass in progress.
Explanation: During a point-in-time restore of a database, the size of the database being restored is displayed. The available capacity of the online database volumes must be at least this size. System Action: None. User Response: None.
Explanation: During a DSMSERV RESTORE DB, the process of rolling back incomplete transactions has begun.
364
IBM Tivoli Storage Manager: Messages
ANR4647I ANR4661E
ANR4647I Database available capacity is number of megabytes megabytes. ANR4651E Restore of backup series current series operation current operation is not in sequence; backup is part of another log epoch.
Explanation: During a point-in-time restore of a 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 number of megabytes megabytes.
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. System Action: The database restore is terminated. 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. ANR4657E SNMP: Failed to connect to server at address address, port port.
Explanation: During a point-in-time restore of a 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. System Action: The assigned capacity of the online database is extended to the size required for restore. User Response: None. ANR4649I Reducing database assigned capacity to number of megabytes megabytes.
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: During a point-in-time restore of a 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: None. 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: 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 operation continues. User Response: Contact your service representative. ANR4660I Connected to SNMP subagent at SNMP subagent address on port port number.
Explanation: During a DSMSERV RESTORE DB, a backup volume was mounted that is not in the correct sequence. System Action: The database restore is terminated. 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.
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. User Response: None. 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.
Chapter 3. Common and Platform Specfic Messages
365
ANR4662W ANR4667W
System Action: The server discontinues SNMP processing and server operation continues. User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see the appendix Allocating Additional Server Memory. ANR4662W Failure sending message to SNMP subagent. ANR4664W Failure in registering with SNMP subagent.
Explanation: The server experienced a problem while attempting to register with the SNMP subagent. This may be due to problems with communication or the SNMP subagent being unavailable. System Action: Heartbeat messaging will be disabled until the server is re-started. User Response: Ensure that the subagent is running and that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use. ANR4665W Failure retrying registration with SNMP subagent.
Explanation: The server experienced an error return code from TCP/IP while sending to the SNMP subagent. This message is also issued when the SNMP subagent has an error sending a verb to the server when acting as an SNMP client. This may be a normal event if either side of the connection is abruptly ended, as in the case of terminating the subagent program. The error is reflected in another message for TCP/IP which further describes the error. System Action: The session is ended. Server operation continues. If a message is being forwarded to an SNMP managing node, the message is not sent. If a heartbeat message was being sent to the subagent, this heartbeat message is lost and the server attempts to re-start its session with the SNMP subagent. User Response: If the session is ended as a result of intentionally stopping either the subagent, no response is required. Otherwise, ensure that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use. ANR4663W Failure receiving message from SNMP subagent.
Explanation: The server experienced a problem while 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. 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. ANR4666W Failure sending heartbeat message to SNMP subagent.
Explanation: The server experienced an error return code from TCP/IP while receiving data from the SNMP subagent. This may be a normal event if either side of the connection is abruptly ended, as in the case of terminating the subagent program. The error is reflected in another message for TCP/IP which further describes the error. System Action: The session is ended. Server operation 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. 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.
Explanation: The server experienced a problem while attempting to send a heartbeat message to the SNMP subagent. This may be due to problems with communication or the SNMP subagent being unavailable. System Action: The server will attempt to contact the SNMP subagent again and re-synchronize. 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. ANR4667W Failure retrying heartbeat message to SNMP subagent.
Explanation: The server experienced a problem while attempting to send a heartbeat message to the SNMP subagent. This may be due to problems with communication or the SNMP subagent being 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.
366
IBM Tivoli Storage Manager: Messages
ANR4668I ANR4676E
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. Re-start the server if the heartbeat function is required. ANR4668I Connection successfully re-established with SNMP subagent. 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 experienced a problem while attempting to send a heartbeat message to the SNMP subagent. System Action: The server was able to successfully resynchronize with the SNMP subagent. User Response: None. ANR4669W Heartbeat message was not accepted by SNMP subagent.
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. User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see the appendix Allocating Additional Server Memory. ANR4673E Insufficient memory for subagent initialization (the portion of initialization where the allocation of memory failed).
Explanation: The server experienced a problem while attempting to send a heartbeat message to the SNMP 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. 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. ANR4670W Failure in opening session with SNMP subagent.
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. System Action: Initialization of the subagent fails. User Response: Contact your service representative. ANR4675E Server/subagent protocol violation invalid (where the protocol breakdown occurred).
Explanation: The server experienced a problem while attempting to open a session with the SNMP subagent. System Action: Processing continues. Heartbeat and message forwarding function will not be available. 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. If heartbeat and message forwarding functions are required, re-start the server. ANR4671W SNMP subagent did not accept registration of this server.
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. User Response: Contact your service representative. ANR4676E Unable to register another server.
Explanation: The server experienced a problem while 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
Explanation: The SNMP subagent received a request to register a new server and was unable to allocate the memory necessary to register the new server. System Action: The subagent will not register the new server. User Response: Contact your service representative.
Chapter 3. Common and Platform Specfic Messages
367
ANR4677I ANR4686E
ANR4677I Session established with server name: The name of the registered server.. ANR4682W A SNMP agent connection error occurred. Attempting to re-establish connection.
Explanation: The SNMP subagent completed the registration of the identified server. System Action: The subagent will wait for additional requests from the server. User Response: None. ANR4678I Session closed with server name: The name of the deregistered server..
Explanation: An error has occurred in the communication between the subagent and the SNMP agent. System Action: The subagent will attempt to reconnect. User Response: Make sure that the SNMP daemon is up, running and correctly configured. ANR4683E Unable to open trace file file name.
Explanation: The SNMP subagent completed the deregistration of the identified server. System Action: None. User Response: None. ANR4679W Messages are no longer being forwarded to the SNMP subagent.
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..
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 DPI subagent (The subagent name.): Connected or reconnected, ready to receive requests.
Explanation: An error occurred while attempting to process a trap request from a server. data. System Action: The subagent processing continues. User Response: Make sure that the SNMP daemon is up, running and correctly configured. ANR4685E Insufficient memory for subagent initialization.
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 additional memory to the subagent. ANR4686E Insufficient memory for subagent trace initialization.
Explanation: The subagent has successfully connected or reconnected to the SNMP agent. System Action: The subagent is ready to receive requests from servers. User Response: None. ANR4681W Connect to SNMP agent failed, will keep trying.
Explanation: The SNMP subagent trace could not initialize due to the inability to obtain the required memory. System Action: Initialization of the subagent fails. User Response: Allocate additional memory to the subagent.
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.
368
IBM Tivoli Storage Manager: Messages
ANR4687E ANR4695E
ANR4687E Server/subagent protocol violation expecting registration request. Received request: The value of the request that was received. ANR4692I DPI subagent (The subagent name.): reconnected, ready to receive requests.
Explanation: The subagent has successfully reconnected to the SNMP agent. System Action: The subagent is ready to receive request from servers. User Response: None. ANR4693I Interface Driver information will be loaded in quiet mode: Only warning and error messages will be displayed.
Explanation: The SNMP subagent was expecting a registration request. It actually received something other than a registration request. System Action: The subagent will stop processing requests from the server sending the invalid requests. User Response: Contact your service representative. 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. System Action: The subagent will stop processing requests from the server sending the invalid requests. User Response: Ensure the server and subagent are at the same maintenance level. If they are, contact your service representative. ANR4689E Invalid request type received (The value of the request that was received.).
Explanation: The server is loading information needed for the Administrative WEB Interface. To minimize message traffic, only error and warning messages will be displayed. System Action: When the command completes, WEB administrative information will be loaded into the server. User Response: None. ANR4694E SNMP Subagent Port Confirmation Has Failed.
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. User Response: Contact your service representative. ANR4690E Unexpected request type (The value of the request that was received.) in trap data header.
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 subagent received an invalid trap request from a server. System Action: The subagent will stop processing requests from the server sending the invalid requests. User Response: Contact your service representative. ANR4691I DPI subagent (The subagent name.): connected, ready to receive requests.
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 operation continues. 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.
Explanation: The subagent has successfully connected to the SNMP agent. System Action: The subagent is ready to receive request from servers. User Response: None.
Chapter 3. Common and Platform Specfic Messages
369
ANR4697E ANR4704I
ANR4697E SNMP: Failed to authenticate to server at address address, port port. ANR4701I The server move size threshold has been set to new threshold. Move operations that start after this point will use the new value.
Explanation: The SNMP client was attempting to run a session with the server at the indicated address and port number in response to an SNMP Get Request, which causes a Server Script to be run. The subagent connected to the indicated server, but failed in authentication. System Action: The SNMP subagent ends this attempt to run the script and continues operation. User Response: Ensure that the indicated server has an an administrative id of SNMPADMIN and that this adminstrative id has sufficient authority to run the script and commands it contains. ANR4698E SNMP: Communications Failure in Sending verb type verb (command).
Explanation: A SETOPT commmand was used to set 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. System Action: The server uses this new setting for move operations that are started after this message is issued. User Response: Contact your service representative. 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.
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. User Response: Contact your service representative. ANR4699E SNMP: Receive Buffer overflow.
Explanation: A SETOPT commmand was used to set the value for the maxmimum number of files that can be sent from the client in a single database transaction. System Action: The server uses this new setting for client sessions that are started after this message is issued. User Response: Contact your service representative. ANR4703E Invalid key ring filename Key Ring Filename
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. User Response: Contact your service representative. 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: The key ring filename specified did not contain the .kyr extention. System Action: None. 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: 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. User Response: Contact your service representative.
Explanation: The key ring filename have been set to the new value specified in the DEFINE KEYRING command. System Action: None. User Response: Restart the server to use the new key ring information.
370
IBM Tivoli Storage Manager: Messages
ANR4705I ANR4713E
ANR4705I The server IDL definitions have not been installed. These definitions will need to be installed for the Web Administrator interface to work. 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: 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. System Action: None. User Response: If you would like to use the server web administrator interface you will need to: 1. 2. 3. 4. Halt the server. Issue the command DSMSERV RUNFILE dsmserv.idl. For AS/400 command see next step. For AS/400, issue the command STRSVRADSM SVRMODE(*PRPWEB). Restart the server. Unable to open file Filename to satisfy web session Session ID.
Explanation: A volume mount is awaiting operator intervention on the specified library manager server. System Action: The volume mount operation waits for operator intervention. User Response: Refer to the server consol and/ir activity log on the named library manaer server to determine the action that needs to be performed to complete the mount operation. ANR4710W Library manager Server Name could not be contacted to control library Library Name.
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. System Action: None. User Response: Verify that permission for the file are set correctly and file exists. ANR4707E Import/Loaddb command operation terminated - incomplete input volume list.
Explanation: The 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.
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. User Response: Issue the command again and make sure the necessary volumes are included in the volume list. ANR4708I Native SSL support has been disabled, please use the web proxy.
Explanation: The command failed because an invalid volume history type was specified for the TYPE= parameter. System Action: The command fails, and server operation continues. 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: 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. System Action: None.
Explanation: The command indicated specifies a value that is not valid for the Hex Filespace parameter. System Action: The server does not process the command. User Response: Reissue the command with a valid entry for the Hex Filespace parameter.
Chapter 3. Common and Platform Specfic Messages
371
ANR4714I ANR4724E
ANR4714I Command filename for filespace filespace name of node node name started as process process ID. User Response: To obtain status on the file deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR4718I DELETE FILE file name canceled for filespace filespace name of node node name : number of objects objects deleted.
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. System Action: The server starts a background process 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.
Explanation: A background server process that has 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. System Action: The server process is ended and server operation continues. User Response: No action is required. An authorized administrator can issue the DELETE FILE command to delete the remaining files desired. ANR4719I DELETE FILE file name complete for filespace filespace name of node node name : number of objects objects deleted.
Explanation: A background server process has started (on the server) to delete files from the given filespace for the given node. System Action: The background process deletes backup and archive objects that match the given file name while server operation continues. User Response: To obtain status on the file deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR4716I DELETE FILE file name (backup data) for filespace filespace name of node node name started.
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. System Action: The server process is ended and server operation continues. User Response: None. ANR4723E Session rejected for down level storage agent storage agent name.
Explanation: A background server process has started (on the server) to delete files from the given filespace for the given node. System Action: The background process deletes backup objects that match the given file name while server operation continues. User Response: To obtain status on the file deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR4717I DELETE FILE file name (archive data) for filespace filespace name of node node name started.
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. User Response: None. ANR4724E During the backup of node node (Node id) filespace filespace name (filespace id) a deletion activity occurred.
Explanation: A background server process has started (on the server) to delete files from the given filespace for the given node. System Action: The background process deletes archive objects that match the given file name while server operation continues.
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
372
IBM Tivoli Storage Manager: Messages
ANR4725E ANR4731E
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. v An unsupported model of the filer server was detected 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. 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.
Explanation: An internal error occurred in an attempt to obtain a lock during processing. System Action: The activity that generated this error fails. User Response: Retry the process. If the process fails contact your service representative. ANR4726I The support module has been loaded.
Explanation: The module indicated has been successfully loaded. Operations involving this module may be performed by the server. System Action: Functions which depend on this module may now be performed on the server. User Response: None. ANR4727E Server Server name is incompatible with this server. Please update the server to the same level as this storage agent.
Explanation: The TSM server was trying to connect to a file server with an unsupported level of the operating system. The server can establish NDMP connection only to a file server with supported level of the operating system. Please check the following site for supported levels of file server operating systems: http://www.tivoli.com/storage System Action: The TSM server backup/restore of the file server fails. User Response: Upgrade the file server to a supported level of the operating system. ANR4730E Command: The number of copy storage pool names specified with the COPYSTGPOOLS parameter exceeds the maximum number allowed.
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. User Response: None. 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 number of copy storage pool names that can be specified with the COPYSTGPOOLS parameter is limited to three. Earlier versions allowed up to ten copy storage pools in the list. System Action: The command fails. User Response: Reissue the command specifying three or fewer copy storage pool names. ANR4731E Command: Copy storage pool storage pool name is not defined.
Explanation: The server attempted to connect to a file server. The connection failed because of one of the following possible reasons: v One of the parameters specified during datamover definition was incorrect: TCP/IP address of the file server, user id, password, TCP/IP port v File server does not support requested NDMP version v File server is not accessible v NDMP server limits the number of opened NDMP sessions
Explanation: A DEFINE STGPOOL or UPDATE STGPOOL command contained a copy storage pool that is not defined. System Action: None. User Response: Verify that the copy storage pool name stated in the error message is correct. Correct the problem by using a copy storage pool that already exists or define the copy storage pool. Retry the command.
Chapter 3. Common and Platform Specfic Messages
373
ANR4732E ANR4739E
ANR4732E Command: The storage pool storage pool name is not a copy storage pool. ANR4736E Set serverfree is not allowed when server-free is not available.
Explanation: A DEFINE STGPOOL or UPDATE STGPOOL command contained a copy storage pool name that is not a copy storage pool. System Action: None. User Response: Remove the storage pool name from the list and retry the command. ANR4733E Command: The copy storage pool contains a copy storage pool name that introduces a cycle into the storage pool chain.
Explanation: Server-free processing did not initialize. Changing the status is not allowed. System Action: Server processing continues. User Response: Server-free status may be changed when the status is ON or OFF. ANR4737E Transaction failed for session session number for node node name (client platform) - the copy continue attribute for storage pool storage pool name prevented further retries.
Explanation: A DEFINE STGPOOL or UPDATE STGPOOL command contained a copy storage pool that eventually points to the pool being processed. System Action: None. User Response: Remove the storage pool name from the copy storage pool list and retry the command. ANR4734W Copy storage pool Copy Storage Pool Name was removed from the copy storage pool list because of a failure for session Session Id.
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. System Action: None. 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 Command: Storage pool storage pool name is in use in the copy storage pool parameter for one or more other storage pools.
Explanation: The named copy 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. System Action: None. 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 copy 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 Server-free processing is not available. Initialization failed.
Explanation: A DELETE STGPOOL command specifies a pool that is listed as one of the copy storage pool for other storage pools COPYSTGPOOLS parameter. System Action: The server does not process the command. User Response: If necessary, update other storage pools so that they do not reference the pool to be deleted, and reissue the command. ANR4739E Either the high-level address (hladdress), low-level address (lladdress), or both were entered in error.
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.
Explanation: The high-level or low-level addresses supplied are incorrect. System Action: The server does not process the 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
374
IBM Tivoli Storage Manager: Messages
ANR4740W ANR4745E
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. 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: 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 administrator adminName. This administrator has defined or updated schedules. Renaming this administrator will cause these schedules to fail.
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. User Response: 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 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 device class. The mount limit specified for the device class does not provide a sufficient number of mount points to support the simultaneous write operation. System Action: None. User Response: Make more mount points available. ANR4744W The server cannot acquire a sufficient number of mount points.
Explanation: A RENAME ADMINISTRATOR command has been entered for an administrator that owns administrative schedules. If you confirm that you want to proceed with this command, the schedules owned by this administrator will fail when executed in the future. System Action: The system asks whether you wish to continue with the command. 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 ADMIN_SCHEDULES table to determine which schedules were last updated by the administrator. Use the UPDATE SCHEDULE command to update those schedules contolled by an administrator that has authority to execute them, or use the DELETE SCHEDULE command to remove the schedules.
Explanation: During simultaneous write processing, the server cannot acquire a sufficient number of mount points to satisfy the request. System Action: None. 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
Chapter 3. Common and Platform Specfic Messages
375
ANR4746E ANR4756I
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. User Response: None. ANR4746E Session rejected for up level storage agent storage agent name. ANR4753E REPAIR STGVOL process process number ended, processed volumes processed of total volumes total volumes with repaired volumes repaired and failed volumes failures.
Explanation: The REPAIR STGVOL process has ended. It processed volumes processed out of total volumes total volumes to be processed. The repaired volumes indicates the number of volumes that needed database repairs and were repaired. The failed volumes are volumes that either failed during evaluation or during database repair if it was needed. System Action: None. User Response: If there were failed volumes, review the activity log for more information about the failure. ANR4754I REPAIR STGVOL process process number ended, processed volumes processed of total volumes total volumes with repaired volumes repaired.
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. User Response: None. ANR4747W The web administrative interface is no longer supported. Begin using the Integrated Solutions Console instead.
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. System Action: None. User Response: None. ANR4755W REPAIR STGVOL process process number ended, processed volumes processed of total volumes total volumes with repaired volumes repaired.
Explanation: The web administrative interface is no longer supported. It has been replaced by an administrative interface based on the Integrated Solutions Console. 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. ANR4752I REPAIR STGVOL process process number started for number of volumes volumes.
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. System Action: None. 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 process has been started as the reported process number. This will evaluate and if needed repair the indicated number of volumes. System Action: None. User Response: This process may be monitored using the QUERY PROCESS command. If this process needs to be cancelled, issue the CANCEL PROCESS command.
Explanation: The REPAIR STGVOL selected volume name volume to process. This volume will be evaluated for database reference errors and if any are
376
IBM Tivoli Storage Manager: Messages
ANR4757I ANR4799E
encountered, they will be corrected. System Action: None. User Response: None. ANR4757I REPAIR STGVOL finished evaluating volume volume name, no repair was needed. ANR4761E REPAIR STGVOL reset processing history failed.
Explanation: The REPAIR STGVOL command was issued with RESET=YES. This resets the processing history. However, the reset of the processing history failed. System Action: None. 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. ANR4797E Drive driveName is missing path information. Please check that all related paths are defined properly.
Explanation: The REPAIR STGVOL finished evaluating volume name volume. No repair actions were taken for the database because there were no errors detected. System Action: None. User Response: None. 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. System Action: None. User Response: None. ANR4759E REPAIR STGVOL failed to process volume name.
Explanation: A drive does not have sufficient path information for the operation to complete. This is typically due to a path not being defined. System Action: The server fails the storage operation. User Response: Verify that all applicable paths are defined for the drive. Also verify that the information contained in the paths is correct. ANR4798E Server-free operation type operation had a target failure. Please refer to accompanying messages and Message Reference Manual for further information.
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. System Action: None. 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 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 The server-free operation type from device source name through data mover data mover name to device target name failed after issue.
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. System Action: None. User Response: An administrator may want to periodically reset the processing history and re-evaluate all volume in the server as a means of validating the server database.
Explanation: The server-free operation failed after issuing the SCSI command. This might be because the
Chapter 3. Common and Platform Specfic Messages
377
ANR4800E ANR4807W
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 source name through data mover data mover name to device target name encountered an I/O error. The following information was returned from sense device name: KEY=Key value ASC=Asc value ASCQ=Ascq value SENSE=Sense info System Action: None. User Response: None. 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. System Action: None. User Response: None. 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. System Action: None. User Response: None. ANR4805I Administrator administrator name already uses 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. 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. ANR4801E The server-free operation from device source name through data mover data mover name to device target name encountered an error. This sense information is typically generated by configuration issues, please verify the device definitions.
Explanation: The administrators password expiration period is currently set to the common password expiration period. System Action: None. User Response: None. ANR4806W The password expiration period for node name cannot be reset to the common password expiration period.
Explanation: The nodes password expiration period could not be reset to the common password expiration period at this time. System Action: None. 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.
Explanation: The server-free process did not complete due to the target being unreachable. System Action: The server will fail the transfer. User Response: For the devices involved in this operation, please verify that the device and path defintions are correct. If this message has been issued after the definitions have been verified, please verify that the hardware is operating correctly and that the data mover can see both target devices. ANR4802I Password expiration period for node node name has been reset.
Explanation: The administrators password expiration period could not be reset to the common password expiration period at this time. System Action: None. User Response: Attempt to reset the nodes password expiration period at a later time.
Explanation: The nodes password expiration period has been reset to the common password expiration period.
378
IBM Tivoli Storage Manager: Messages
ANR4808W ANR4827E
ANR4808W The password expiration period for all administrators and nodes has been reset to the common password expiration period. Additional Server Memory. ANR4824E The loading or reading of a table of contents for node node name, file space file space name failed because of a lock conflict.
Explanation: All administrators not managed by a profile and nodes on this server have had their password expiration period reset to the common password expiration period. System Action: None. User Response: None. ANR4820E Command The creation date and creation time are both required to be specified.
Explanation: The server ends a table of contents (TOC) loading or reading for the specified node and file space because the requested resource is already in use by another process. System Action: The TOC loading or reading is ended and server operation continues. 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.
Explanation: The server-free process did not complete due to the target being unreachable. System Action: The server will fail the command. User Response: Reissue the command, specifying both creation date and creation time, or neither of them. ANR4821E Command: The creation date - date. is not valid
Explanation: The server ends a table of contents (TOC) loading for the requested TOCs. The requested TOCs have to be for the same file space in the same node name. System Action: The TOC loading or reading is ended and server operation continues. User Response: Try the TOC loading specifying the TOCs in the same node for the same filespace. ANR4826E The object for the table of contents is not found in the server for node node name, file space file space name.
Explanation: The specified command has been issued with an invalid creation date. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid creation date. ANR4822E Command: The creation time date is not valid.
Explanation: The specified command has been issued with an invalid creation time. System Action: Server operation continues, but the command is not processed. User Response: Issue the command with a valid creation time. ANR4823E The loading or reading of a table of contents for node node name, file space file space name failed because sufficient memory is not available.
Explanation: The server ends a table of contents (TOC) loading or reading for the object in the specified node and file space, because the server cannot find the object for the TOC. System Action: The TOC loading or reading is ended 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.
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. System Action: The TOC loading or reading is ended and server operation continues. User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see Appendix. Allocating
Explanation: The server ends a table of contents (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 TOC loading is ended and server operation continues.
Chapter 3. Common and Platform Specfic Messages
379
ANR4828E ANR4834E
User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see Appendix. Allocating Additional Server Memory. ANR4828E The loading or reading of a table of contents for node node name, file space file space name failed because an internal server error was detected. ANR4831E 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. System Action: The TOC loading or reading is ended and server operation continues. User Response: Try the operation again at a later time. ANR4832E The loading or reading of a table of contents for node node name, file space file space name failed. The required volume was not mounted.
Explanation: The server ends a table of contents (TOC) loading or reading for the specified node and file space because an internal logic error is detected. System Action: The TOC loading or reading is ended and server operation continues. 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. ANR4829E The loading or reading of a table of contents for node node name, file space file space name failed. The transaction is stopped.
Explanation: During the table of contents (TOC) loading or reading operation, a required volume cannot be mounted. The mount request may have been canceled. System Action: The TOC loading or reading is ended and server operation continues. User Response: Try the TOC loading or reading again and make sure the necessary volumes are accessible. ANR4833W The loading or reading of a table of contents for node node name, file space file space name failed. The file was deleted from server storage.
Explanation: An error was detected during transaction commit. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The table of contents (TOC) loading or reading is ended and server operation continues. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR4830E The loading or reading of a table of contents for node node name, file space file space name failed. Insufficient mount points are available to satisfy the request.
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. System Action: The TOC loading or reading is ended and server operation continues. User Response: Contact your administrator to find out if DELETE FILESPACE, DELETE VOLUME, or inventory expiration processes are running; these processes can delete files in server storage during TOC loading or reading. ANR4834E The loading or reading of a table of contents for node node name, file space file space name failed. The data transfer is interrupted.
Explanation: The server was unable to allocate sufficient mount points to read the table of contents (TOC). System Action: The TOC loading or reading is ended and server operation continues. User Response: If necessary, make more mount points available.
Explanation: The server ends a table of contents (TOC) loading or reading for the specified node and 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 operation continues. User Response: Examine the messages issued prior to
380
IBM Tivoli Storage Manager: Messages
ANR4835E ANR4842E
this message to determine why the data transfer was interrupted. Attempt the operation again if the problem can be resolved. ANR4835E The reading of a table of contents for node node name, file space file space name failed. A data integrity error was detected. ANR4839E The loading for the table of contents for node node name, file space file space name failed. See previous messages.
Explanation: The loading for the table of contents (TOC) in the specified node and file space has failed. System Action: The TOC loading is ended and the server operation continues. User Response: Examine the messages issued prior to this message to determine the source of the problem. ANR4840I The loading for the table of contents for node node name, file space file space name was cancelled.
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. System Action: The TOC reading is ended and server operation continues. User Response: Examine the messages issued prior to this message and contact your service representative. ANR4836E The reading of a table of contents for node node name, file space file space name failed. There was an error in reading from a device.
Explanation: The loading for the table of contents (TOC) in the specified node and file space has been cancelled by the user. System Action: The TOC loading is ended and the server operation continues. User Response: None. ANR4841E The loading for the table of contents for node node name, file space file space name failed. An invalid object type detected.
Explanation: The server ends a table of contents (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. System Action: The TOC reading is ended and server operation continues. User Response: Examine the messages issued prior to this message that specify the device that is failing. The server may need to be shut down with a HALT command to correct the hardware problem. ANR4837I The loading for the table of contents for node node name, file space file space name started.
Explanation: The loading for the table of contents (TOC) in the specified node and file space failed because the object type given is different than the one in the server database. System Action: The TOC loading is ended and the server operation continues. User Response: Re-try the Table of Contents loading, specifying a valid object type. ANR4842E The loading of a table of contents for node node name failed. The file space name was not found.
Explanation: The loading for the table of contents (TOC) in the specified node and file space has been started. System Action: The server operation continues. User Response: None. ANR4838I The loading for the table of contents for node node name, file space file space name was successful: total entries loaded number of entries.
Explanation: The server ends a table of contents (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 operation continues. 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.
Explanation: The loading for the table of contents (TOC) in the specified node and file space has been successfully finished. System Action: The server operation continues. User Response: None.
Chapter 3. Common and Platform Specfic Messages
381
ANR4843I ANR4872E
ANR4843I Command: Displayed number of objects objects, number of errors errors were encountered. 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: QUERY TOC has completed. The number of objects displayed and the error count are displayed. System Action: The QUERY TOC command ends and server operation continues. 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 contents for node node name, file space file space name contains no entries.
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. System Action: The server operation continues. 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. ANR4870W Audit command: Storage pool storage pool name, specified as a Table of Contents (TOC) destination for copy group copy group name in management class management class name, policy set set name, domain domain name, does not exist.
Explanation: The specified table of contents (TOC) exists, but it is empty. No entries are displayed. System Action: Server operation continues. User Response: None. ANR4860W The correct value of ARCHRETENTION for domain domain name will not be sent to the managed servers. Please upgrade the managed servers to be at least the same level as that of the configuration manager.
Explanation: A database audit process finds a storage 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. System Action: Audit processing continues. User Response: After the audit command completes, 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. ANR4871I Collocation group collocation group name defined.
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. System Action: The server operation continues. 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.
Explanation: A DEFINE COLLOCGROUP command has created the collocation group indicated. System Action: None. User Response: None. ANR4872E Command: Invalid collocation group name - collocation group name.
Explanation: Server processing for the command command fails because the collocation group name collocation group name specified does not contain valid characters or contains too many characters.
382
IBM Tivoli Storage Manager: Messages
ANR4873E ANR4881E
System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Issue the command again and specify a collocation group name that conforms to the name requirements. For information on the character and length specifications for valid collocation group names, refer to the Administrators Reference. ANR4873E Command: Collocation group description exceeds maximum length of length limit characters. incorrectly, issue the command again with the correct node name. ANR4877E Command: Collocation group collocation group name is not defined.
Explanation: Server processing for the command command fails because the collocation group name collocation group name specified does not refer to a defined collocation group in the server database. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Issue the command again, specifying a collocation group name that is defined in the server database. For a list of the names of defined collocation groups in the server database, issue the QUERY COLLOCGROUP command. ANR4878I Command: number of nodes members defined in the collocation group collocation group name.
Explanation: Server processing for the command command fails because the collocation group description specified is longer than the length limit number of characters allowed. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Issue the command again and specify a shorter collocation group description. ANR4874I Collocation group collocation group name updated.
Explanation: A DEFINE COLLOCMEMBER command has created the specified number of members in the indicated collocation group. System Action: None. User Response: None. ANR4879I Command: number of nodes members deleted from collocation group collocation group name.
Explanation: In response to the UPDATE COLLOCGROUP command, the collocation group collocation group name has been updated in the server database. System Action: Server operation continues. User Response: None. ANR4875I Collocation group collocation group name deleted.
Explanation: A DELETE COLLOCMEMBER command has deleted the specified number of members from the indicated collocation group. System Action: None. User Response: None. ANR4880I Node node name disassociated from collocation group collocation group name.
Explanation: In response to the DELETE COLLOCGROUP command, the collocation group collocation group name has been deleted from the server database. System Action: Server operation continues. User Response: None. ANR4876W Command: Node node name cannot be processed because it is not registered.
Explanation: This message is displayed in response to the DELETE COLLOCMEMBER command. Node node name is no longer associated with the collocation group name collocation group name. System Action: Server operation continues. User Response: None. ANR4881E Command: Collocation group collocation group name is already defined.
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. System Action: The indicated node is not processed, but other nodes can be processed if specified by this command. User Response: If the node name was entered
Explanation: Server processing for the command command fails because the collocation group name collocation group name specified refers to a collocation
Chapter 3. Common and Platform Specfic Messages
383
ANR4882E ANR4889E
group that is already defined in the server database. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: Issue the command again, specifying a collocation group name that is not defined in the server database. For a list of the names of defined collocation groups in the server database, issue the QUERY COLLOCGROUP command. ANR4882E Command: Collocation group collocation group name still contains at least one node. ANR4885E Command: Either node name or collocation group name must be specified.
Explanation: The indicated command failed because 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 server operation continues. User Response: Issue the command again, by specifying either the node name or the collocation group name. ANR4886E Audit command: A missing or incorrect collocation group id has been detected for node node id.
Explanation: Server processing for the delete command command fails because the collocation group collocation group name specified refers to a collocation group that still contains at least one node. A collocation group cannot be deleted if one or more client nodes are still assigned to the collocation group. System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database. User Response: To remove remaining nodes from the 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 database audit process detects missing or incorrect collocation group identifier for the specified node member. System Action: Audit processing continues. User Response: Issue the audit command again, and specify FIX=YES so that the error can be corrected. ANR4887E Audit command: A missing or incorrect collocation group id has been detected for node node id - it will be corrected.
Explanation: A database audit process detects missing 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. System Action: Audit processing continues. User Response: None. ANR4888E Audit command: Collocation group global high-water mark does not match the identifier in use.
Explanation: This message is displayed in response to the DEFINE COLLOCMEMBER command. Node node name is associated with the collocation group name collocation group name. System Action: Server operation continues. User Response: None. ANR4884W Node node name already associated to collocation group collocation group name.
Explanation: A database audit process finds the attribute used to track collocation group identifiers are incorrect. System Action: Audit processing continues. User Response: Issue the audit command again, and specify FIX=YES so that the error can be corrected. ANR4889E Audit command: Collocation group global high-water mark does not match the identifiers in use; it will be corrected.
Explanation: This message is displayed in response to 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. System Action: Server operation continues. User Response: If the node name was entered incorrectly, issue the command again with the correct node name.
Explanation: A database audit process finds the attributes used to track collocation group identifiers are incorrect. Because FIX=YES has been specified for the audit command, the attributes will be corrected. System Action: Audit processing continues.
384
IBM Tivoli Storage Manager: Messages
ANR4920E ANR4928E
User Response: None. ANR4920E Command: Administrator administrator name is not authorized to issue this command for storage pool pool name. ANR4924E Command: Migration is not needed for the storage pool pool name.
Explanation: The specified administrator has entered the indicated command, but this administrator does not have the proper authority necessary to run the 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. System Action: The server does not process the command. 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. ANR4921E Command: Primary storage pool pool name does not have a target pool.
Explanation: Either the high migration threshold (percentage) is set to 100 to prevent migration for the specified storage pool or the number of volumes containing data has not reached the high migration threshold. System Action: The server does not process the command. User Response: Re-issue the command when migration is needed for the pool. ANR4925W Migration process process ID terminated for storage pool storage pool name duration exceeded.
Explanation: During migration for the indicated storage pool, a process performing the migration has been terminated because the migration duration has exceeded. System Action: The migration process is terminated. User Response: None. ANR4926W Migration terminated for volume volume name - duration exceeded.
Explanation: The specified primary storage pool does not have a target storage pool for the specified operation. System Action: The server does not process the 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: During migration for the indicated volume, the duration for the migration has been exceeded. System Action: The volume migration is terminated. User Response: None. ANR4927W Reclamation terminated for volume volume name - duration exceeded.
Explanation: The migration operation is already running for the specified storage pool. System Action: The server does not process the command. User Response: Re-issue the command when migration is not running. ANR4923E Command: Reclamation is currently running for the storage pool pool name.
Explanation: During reclamation for the indicated volume, the duration for the reclamation has been exceeded. System Action: The volume reclamation is terminated. User Response: None. ANR4928E Command: Reclamation is not allowed for the storage pool pool name.
Explanation: The reclamation operation is already running for the specified storage pool. System Action: The server does not process the command. User Response: Re-issue the command when reclamation is not running.
Explanation: The high reclamation threshold (percentage) is set to 100 to prevent reclamation for the specified storage pool. System Action: The server does not process the command. User Response: Re-issue the command when migration is needed for the pool.
Chapter 3. Common and Platform Specfic Messages
385
ANR4929E ANR4937E
ANR4929E Command: The storage pool pool name is not a sequential-access pool. ANR4933I Space reclamation ended for offsite volume volume name.
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. System Action: The server does not process the 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: Space reclamation for the named offsite volume is complete. System Action: None. User Response: None. 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. System Action: None. User Response: None. 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: 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. System Action: Data is moved from this storage pool to the same pool or to the reclaim storage pool. User Response: None. 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: Migration processing for the specified storage pool has ended with the results shown. System Action: None. User Response: Examine previous messages to 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: 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. System Action: Data is moved from this storage pool to the same pool or to the reclaim storage pool. User Response: None. ANR4932I Reclamation process process ID ended for storage pool storage pool name.
Explanation: Reclamation processing for the specified storage pool has ended with the results shown. System Action: None. User Response: Examine previous messages to determine whether all reclamation processes ended successfully. ANR4937E Command: Reclamation will not run delete filespace is currently running.
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. System Action: None. User Response: None.
Explanation: A delete filespace operation is running. To Avoid the resource contention, reclamation will not run when delete filespace is running. System Action: The server does not process the command. User Response: Re-issue the command when delete filespace is not running.
386
IBM Tivoli Storage Manager: Messages
ANR4938E ANR4946W
ANR4938E Command: Administrator administrator name is not authorized to issue this command for target storage pool pool name. ANR4944E Command: Volumes cannot be defined in RECLAMATIONTYPE=SNAPLOCK storage pools.
Explanation: The specified administrator has entered the indicated command, but this administrator does not have the proper authority necessary to run the command for the indicated pool. The indicated pool is the pool that to which files are migrated or reclaimed. System Action: The server does not process the command. 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. ANR4939E Command: The option option is not valid for a DISK storage pool.
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. System Action: The operation fails. 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: The command indicated specifies an option that is not valid for a DISK storage pool. System Action: The server does not process the command. User Response: Reissue the command with options appropriate for a DISK storage pool. ANR4940E Reclamation is ended for storage pool storage pool name. There is an insufficient number of mount points available for removable media.
Explanation: While attempting to define a volume on volume name the server detected that the volume size exceeds the maximum allowed. System Action: The operation fails. 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: During reclamation for the indicated storage pool the server could not allocate sufficient mount points in the storage pool. System Action: Reclamation stops. User Response: If necessary, make more mount points available. ANR4943E Command: Volumes cannot be deleted from RECLAMATIONTYPE=SNAPLOCK storage pools.
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. System Action: The operation continues. 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).
Explanation: Deleting volumes from RECLAMATIONTYPE=SNAPLOCK storage pools is not allowed. Rather, deletion of empty volumes occurs automatically during reclamation processing. System Action: The operation fails. User Response: Allow deletion of empty volumes to be done automatically during reclamation processing.
Chapter 3. Common and Platform Specfic Messages
387
ANR4947E ANR4953E
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. history messages. The NDMP node ID reported in the message is the node ID referenced in the current NDMP file history message. System Action: The TOC creation fails. User Response: Verify that the NDMP server is properly sending file history information. Otherwise, contact your service representative. ANR4951E The writing of a table of contents for node node name, file space file space name failed. The object is excluded from storage pool pool name and all successor pools because of its size.
Explanation: While creating a table of contents (TOC), the server attempted to translate the Unicode path name in the file history message from UCS-2 to UTF-8. The translation failed. 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 Storage Manager is running. Try the operation again. ANR4948E The list file named list file name contains more than max entry count entries.
Explanation: While reading a list file, the server detects that the number of entries exceeds the maximum allowed. System Action: The operation fails. User Response: Consider breaking up the operation into multiple commands, each handling a subset of the required entries. ANR4949E The server is unable to write to table table name because there is not enough temporary space in the database. Table of contents operation for node node name, file space file space name fails.
Explanation: The server ends a table of contents (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. System Action: The TOC creation is ended and server operation continues. 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 The writing of a table of contents for node node name, file space file space name failed. No space is available in storage pool pool name and all successor pools.
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: The server ends a table of contents (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. System Action: The TOC creation is ended and server operation continues. 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. ANR4953E The writing of a table of contents for node node name, file space file space name failed. The server encountered an error when writing to the storage device.
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
Explanation: The server ends a table of contents (TOC) creation for the specified node because an I/O error has been encountered by the server in writing to a device.
388
IBM Tivoli Storage Manager: Messages
ANR4954E ANR4960E
System Action: The TOC creation is ended and server operation continues. User Response: Query the activity log to find messages preceding this one that specify the failing device. Storage pool volumes can be varied offline (by using the VARY command), or the server may need to be halted to correct the hardware problem. After the problem is corrected, try the operation again. ANR4954E The writing of a table of contents for node node name, file space file space name failed. The data transfer was interrupted. command to extend the size of the log so that the new volumes are used. ANR4957E The writing of a table of contents for node node name, file space file space name failed. The server does not have sufficient database space.
Explanation: The server ends a table of contents (TOC) creation for the specified node because sufficient database space is not available on the server. System Action: The TOC creation is ended and server operation continues. User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database. Also,an administrator can issue the EXTEND DB command to extend the size of the database so that the new volumes are used. ANR4958E The writing of a table of contents for node node name, file space file space name failed. The server is unable to start a new thread.
Explanation: The server ends a table of contents (TOC) creation for the specified node because data transfer to or from data storage was interrupted by an external event. System Action: The TOC creation is ended and server operation continues. User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the operation again if the problem can be resolved. ANR4955E The writing of a table of contents for node node name, file space file space name failed. The storage media is not available.
Explanation: The server ends a table of contents (TOC) creation for the specified node because sufficient memory is not available for starting additional processes on the server. System Action: The TOC creation is ended and server operation continues. User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online, or see Appendix. Allocating Additional Server Memory. ANR4959E The writing of a table of contents for node node name, file space file space name failed. The server does not have sufficient memory.
Explanation: The server ends a table of contents (TOC) creation for the specified node because storage volumes are not available in the storage pools in which the TOC is to be stored. System Action: The TOC creation is ended and server operation continues. User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for TOC storage. ANR4956E The writing of a table of contents for node node name, file space file space name failed. The server does not have sufficient recovery log space.
Explanation: The server ends a table of contents (TOC) creation for the specified node because sufficient memory is not available on the server. System Action: The TOC creation is ended and server operation continues. User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online, or see Appendix. Allocating Additional Server Memory. ANR4960E The writing of a table of contents for node node name, file space file space name failed. The server detected an internal error.
Explanation: The server ends a table of contents (TOC) creation for the specified node because sufficient log space is not available on the server. System Action: The TOC creation is ended and server operation continues. User Response: An authorized administrator can issue the DEFINE LOGVOLUME command to add volumes for use by the log, and can issue the EXTEND LOG
Explanation: The server ends a table of contents (TOC) creation for the specified node because an
Chapter 3. Common and Platform Specfic Messages
389
ANR4961E ANR4967W
internal logic error is detected. System Action: The TOC creation is ended and server operation continues. 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. ANR4961E The writing of a table of contents for node node name, file space file space name failed. The server could not commit the transaction. ANR4964I Space reclamation deleted number of volumes WORM FILE volumes for storage pool storage pool name.
Explanation: During reclamation for the indicated 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. User Response: None. ANR4965E operation is ended for storage pool storage pool name. Sufficient database space is not available.
Explanation: An error was detected during transaction commit. This message should be preceded by other messages that give additional information about the failed transaction. System Action: The table of contents (TOC) creation is ended and server operation continues. User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative. ANR4962E The writing of a table of contents for node node name, file space file space name failed. The server does not have sufficient mount points available to satisfy the request.
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. User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes using the DEFINE DBVOLUME command and can extend the size of the database using the EXTEND DB command. ANR4966E operation is ended for storage pool storage pool name; sufficient recovery log space is not available.
Explanation: The server was unable to allocate sufficient mount points to write the table of contents (TOC). System Action: The TOC creation is ended and server operation continues. User Response: If necessary, make more mount points available. ANR4963E The writing of a table of contents for node node name, file space file space name failed. See previous messages.
Explanation: Insufficient server recovery log space has been encountered during the indicated operation for the indicated storage pool. System Action: Either the Migration or Reclamation stops, or the operation specified in the message stops. User Response: To increase the amount of recovery log space available to the server, an authorized 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: The server ends a table of contents (TOC) creation for the specified node because a previous error has occurred. System Action: The TOC creation is ended and server operation continues. 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.
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.
390
IBM Tivoli Storage Manager: Messages
ANR4968W ANR4983I
ANR4968W Reclamation failed on WORM FILE volume volume name. ANR4971E Audit command: Missing or incorrect reclamation retention date for WORM FILE volume volume name. The reclamation retention date will be created or corrected.
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.
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. System Action: Audit processing continues. User Response: None. 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. User Response: None. ANR4981E Interface Driver audit completed Inconsistencies were found.
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. System Action: The server operation continues without converting the command output from the servers code page to UTF-8. 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. ANR4970E Audit command: Missing or incorrect reclamation retention date for WORM FILE volume volume name; run AUDIT VOLUME FIX=YES for correction.
Explanation: The server found errors during the audit of the definitions for Web interface. System Action: The Web Interface is not correctly installed. The Web Admin will not work correctly, but the server may be run without any problems. User Response: Ensure you are using the correct IDL file for the server level you are running. Examine error messages that may have been displayed before and/or after this message and correct any problems, if possible. If the cause of this can not be determined or resolved, contact your support representative. ANR4982I Interface Driver audit completed definitions are consistent.
Explanation: The server successfully completed the installation of the definitions for the Web interface. System Action: The Web Interface is now installed. The server may be run without any problems. User Response: None. ANR4983I Auditing Interface Driver Groups.
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. System Action: Audit processing continues. User Response: Issue the AUDIT VOLUME command with FIX=YES, so that the reclamation retention date can be created or corrected.
Explanation: The server is auditing the driver groups. System Action: The server will audit the driver groups and proceed to the next step. User Response: None.
Chapter 3. Common and Platform Specfic Messages
391
ANR4984E ANR5000E (S/390)
ANR4984E Error description User Response: None. ANR4990I Auditing Interface Driver Operation Parameters.
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 operation parameters. System Action: The server will audit the driver operation parameters and proceed to the next step. User Response: None. ANR4991I Auditing Interface Driver Tasks.
Explanation: The server is auditing the driver tasks. System Action: The server will audit the driver tasks and proceed to the next step. User Response: None. ANR4992I Auditing Interface Driver Task 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. User Response: None. ANR4986I Auditing Interface Driver Classes.
Explanation: The server is auditing the driver task members. System Action: The server will audit the driver task members and proceed to the next step. User Response: None. ANR4993E The client platform platform name is currently not supported by the TSM Storage Agent.
Explanation: The server is auditing the driver classes. System Action: The server will audit the driver classes and proceed to the next step. User Response: None. ANR4987E Audit processing failed: sufficient memory is not available for processing.
Explanation: At this point in time the storage agent does not accept the incomming client platform. System Action: None. User Response: None. ANR4994E Query whether the volume volume name is in the library library name failed.
Explanation: At RUNFILE time, the server is unable to process the IDL data due to insufficient memory. System Action: Server runfile stops. User Response: Restart the server runfile process with more memory available. ANR4988I Auditing Interface Driver Complex Class containers.
Explanation: The server is auditing the driver class containers. System Action: The server will audit the driver class containers and proceed to the next step. User Response: None. ANR4989I Auditing Interface Driver Operations.
Explanation: An attempt to query if the indicated volume is in the specified library failed. It could be the library is offline or the library manager is down in a library sharing environment. System Action: The requested operation failed. 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. ANR5000E (S/390) Unable to load tape deletion exit. Explanation: The tape deletion exit module specified in the options file cannot be loaded. System Action: Server operation continues. User Response: Ensure that the tape deletion exit
Explanation: The server is auditing the driver operations. System Action: The server will audit the driver operations and proceed to the next step.
392
IBM Tivoli Storage Manager: Messages
ANR5010E (S/390) ANR5019E (S/390)
module is in the system linklist or in the JOBLIB/STEPLIB for the server. ANR5010E (S/390) Unable to initialize disk driver internal error code from IUCV. Explanation: The servers disk driver cannot be initialized because the error code has been received from the IUCV DECLARE BUFFER function. System Action: Server initialization fails. User Response: For a description of the reported error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system. ANR5011E (S/390) Unable to open disk vaddr invalid virtual device address. Explanation: A disk cannot be opened for processing because the specified virtual address is beyond the supported range. Virtual addresses must be specified in the range 0001 to FFFF. System Action: Server operation continues. User Response: Specify a valid virtual address. ANR5012E (S/390) Unable to open disk vaddr - error code received from FILEDEF. Explanation: A disk cannot be opened for processing because the error code has been received from the FILEDEF command. The server enters one FILEDEF command per open disk so that the CMS DISKID function may be used. System Action: Server operation continues. User Response: For a description of the FILEDEF error code, refer to the CMS Command Reference publication for your operating system. ANR5013E (S/390) Unable to open disk vaddr virtual disk not attached. Explanation: A disk cannot be opened because the virtual disk is not attached to the servers virtual machine. System Action: Server operation continues. User Response: Ensure that the VM DASD volume containing the disk is online, and that the disk is properly linked to the servers virtual machine. ANR5014E (S/390) Unable to open disk vaddr - error code received from DISKID. Explanation: A disk cannot be opened for processing because the error code has been received from the DISKID function. System Action: Server operation continues. User Response: For a description of the DISKID error code, refer to the CMS Command Reference publication for your operating system. ANR5015E (S/390) Unable to open disk vaddr internal error code connecting to Block I/O System Service. Explanation: A disk cannot be opened for processing because the IUCV CONNECT error code is received when attempting to connect to the CP DASD Block I/O System Service. System Action: Server operation continues. User Response: For a description of the IUCV CONNECT error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system. ANR5016E (S/390) Unable to open disk vaddr - device type not supported. Explanation: A disk cannot be opened for processing because its device type is not supported. System Action: Server operation continues. User Response: Use only the disk devices supported by the CP DASD Block I/O System Service. ANR5017E (S/390) Unable to open disk vaddr - block size not supported. Explanation: A disk cannot be opened for processing because its formatted block size is not supported. System Action: Server operation continues. User Response: Use only the disks formatted with block sizes supported by the CP DASD Block I/O System Service. ANR5018E (S/390) Unable to open disk vaddr - IUCV path already exists to device. Explanation: A disk cannot be opened because a path already exists for this device to the CP DASD Block I/O System Service. System Action: Server operation continues. User Response: Contact your service representative. ANR5019E (S/390) Unable to open disk vaddr internal error code from Block I/O System Service. Explanation: A disk cannot be opened for processing because the connection to the CP DASD Block I/O System Service has been severed with error code. System Action: Server operation continues. User Response: For a description of the severed error
Chapter 3. Common and Platform Specfic Messages
393
ANR5020E (S/390) ANR5028E (S/390)
code, refer to the documentation for the CP DASD Block I/O System Service in the CP Programming Services publication for your specific operating system. ANR5020E (S/390) Unable to open disk vaddr - device is read-only. Explanation: A disk cannot be opened for processing because it is accessible only as a read-only device. All server disks must be accessible in read/write mode. System Action: Server operation continues. User Response: Ensure that the disk is properly linked in read/write mode. ANR5021E (S/390) 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. System Action: Server operation continues. 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 (S/390) 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. System Action: Server operation continues. User Response: Reformat or replace the disk. ANR5023E (S/390) 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. System Action: Server operation continues. User Response: Reformat or replace the disk. ANR5024E (S/390) Unable to perform I/O to disk vaddr - format error detected. Explanation: The server encounters a format error on the specified disk. System Action: Server operation continues. User Response: Reformat the disk by using the DSMDISK exec. ANR5027E (S/390) Open of DDNAME ddname failed, insufficient memory. Explanation: The server is unable to open ddname ddname due to a lack of storage. System Action: Server operation continues. User Response: Increase the region for the server or lower the MAXSESSIONS parameter in the server options file. There are three ways to do this: 1. On VM, increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. 2. On MVS, increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server. 3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated. 4. Decrease the amount of space allocated to the servers database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4KB of memory to be allocated. Note that the server must be shut down (with the HALT command) before changes can be made to the server options file. ANR5028E (S/390) Open of data set dsn failed; zero pages in data set. Explanation: The VSAM linear data set dsn has no space. This message appears when: ANR5026E (S/390) Open of data set dsn failed, return code rc, reason code reason. Explanation: Data set dsn cannot be opened. System Action: Server operation continues. User Response: Verify that dsn is a VSAM linear data set. If dsn is a valid VSAM linear data set, contact your service representative. ANR5025E (S/390) Disk vaddr has been reset and is no longer available. Explanation: A disk is reset during operation because a CP RESET or DETACH command has been entered from the servers console. System Action: The disk is marked off-line. User Response: Ensure that the disk is properly reattached to the servers virtual machine.
394
IBM Tivoli Storage Manager: Messages
ANR5030E (S/390) ANR5039E (S/390)
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 System Action: Server operation continues. User Response: Run the dsmfmt utility, or reallocate the VSAM linear data set as appropriate. ANR5030E (S/390) Dynamic allocation of data set dsn failed, return code rc, error code error-code, info code info-code. Explanation: The dynamic allocation of data set dsn fails. The return code rc, error code error-code and information code info-code, are in decimal and can be found in the Dynamic Allocation section of MVS/ESA Programming: Authorized Assembler Services Guide. System Action: Server operation continues. User Response: Ensure that the data set dsn is available for allocation by the server. ANR5032E (S/390) Unable to free DDNAME dsn, return code rc, error code error-code, info code info-code. Explanation: The dynamic deallocation of data set dsn fails. The return code rc, error code error-code and information code info-code are in decimal and can be found in the Dynamic Allocation section of MVS/ESA Programming: Authorized Assembler Services Guide. System Action: Server operation continues. User Response: Contact your service representative. ANR5033E (S/390) Close of ddname dsn failed, return code rc, reason code reason. Explanation: Data set dsn cannot be closed. System Action: Server operation continues. User Response: Verify that dsn is a VSAM linear data set. If dsn is a valid VSAM linear data set, contact your service representative. ANR5034E (S/390) Unable to allocate processor for ddname dsn. Explanation: The number of simultaneous tapes supported by the server has been exceeded. System Action: Server operation continues. User Response: Contact your service representative for a fix that allows additional tapes. ANR5038E (S/390) Volume volume cannot be processed this level of the operating system. Explanation: The volume was created on a level of the operating system that had BSAM Large Block support, and cannot be processed on this level of the operating system. System Action: Server operation continues. User Response: Mark storage volume pool volumes unavailable until the operating system is upgraded to 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. ANR5039E (S/390) Unable to open disk vaddr - IUCV MAXCONN value exceeded. Explanation: The disk at virtual address vaddr cannot be opened due to a lack of IUCV connections. System Action: Server operation continues. User Response: Increase the IUCV MAXCONN value
Chapter 3. Common and Platform Specfic Messages
ANR5035E (S/390) Dynamic allocation of tape unit unit failed, return code rc, error code error-code, info code info-code. Explanation: The dynamic allocation of a tape unit unit fails. The return code rc, error code error-code, and information code info-code are in decimal and can be found in the Dynamic Allocation section of MVS/ESA Programming: Authorized Assembler Services Guide. System Action: Server operation continues. User Response: Examine the MVS messages preceding this message. They should explain the cause of the allocation problem; otherwise, contact your service representative. ANR5036E (S/390) Open of tape unit unit (ddname ddname) failed, return code rc. Explanation: Open of ddname ddname fails. System Action: Server operation continues. User Response: Examine the MVS messages preceding this message. The ANR1401W message and the volume name will explain the problem. If necessary, contact your service representative. ANR5037E (S/390) Unable to acquire processor, dsn. Explanation: The number of simultaneous tapes supported by the server has been exceeded. System Action: Server operation continues. User Response: Contact your service representative for a fix that allows additional tapes.
395
ANR5040E (S/390) ANR5049E (S/390)
in the server CP directory entry and restart the server. ANR5040E (S/390) Data set name dsn contains qualifier qual that is longer than 8 characters. Explanation: Data set dsn qualifier qual is too long. Data set qualifiers must be 1 to 8 characters long. System Action: Server operation continues. User Response: Specify data set name qualifiers with a maximum of 8 characters. ANR5041E (S/390) Data set name dsn contains a null qualifier. Explanation: Data set dsn contains null qualifier (either 2 consecutive periods or an ending period without a subsequent qualifier). Data set qualifiers must be 1 to 8 characters long. System Action: Server operation continues. User Response: Specify valid data set name qualifiers. ANR5042E (S/390) Data set name dsn contains qualifier qual that does not begin, with an alpha character. Explanation: Data set dsn qualifier qual does not begin with an alpha character. Data set qualifiers must start with an alpha character. System Action: Server operation continues. User Response: Specify data set name qualifiers that begin with an alpha character. ANR5043E (S/390) Data set name dsn contains qualifier qual that contains a character that is not alphanumeric. Explanation: Data set dsn qualifier qual contains a character that is not alphanumeric. Data set qualifiers must contain only alphanumeric characters. System Action: Server operation continues. User Response: Specify data set name qualifiers that contain only alphanumeric characters. ANR5044E (S/390) Cannot format data set dsn. Data set is not empty. Explanation: The server will not format dsn because it is not empty. System Action: Server operation continues. User Response: Verify that dsn is the correct data set youd like to format. The server formats empty data sets only. ANR5045E (S/390) Failed to open dataset dsn. Error detected with the VSAM high-used (VSAM high-used value) or high-allocated (VSAM high-allocated value) values. Explanation: The server did not open dataset dsn. 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 not brought on-line. Server operation continues. User Response: Issue listcat entry(dsn) all to check the high-used and high-allocated values. If you moved the dataset, verify that a logical move was performed. Correct any user errors. Otherwise, contact your service representative. ANR5046I (S/390) Dynamic allocation of tape unit unit was cancelled by the operator. Explanation: The dynamic allocation of a tape unit unit was cancelled by the operator. System Action: Server operation continues, tape mount fails. User Response: None. ANR5048E (S/390) 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 (S/390) Tape data set allocation of data set organization changed from hex server value to hex 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). 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 data set organization. Check for any system exits that may change the data set organization (for example, IEFDB401). Ensure that the
396
IBM Tivoli Storage Manager: Messages
ANR5050E (S/390) ANR5064E (S/390)
server can use its original value for the data set organization. See MVS/DFP V3R3 Macro Instructions for Data Sets for valid values. ANR5050E (S/390) Tape data set allocation of record format changed from hex server value to hex current value. 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). 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 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 (S/390) 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. 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 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. ANR5060E (S/390) Unable to open VTAM ACB Name name, rc code. Explanation: The server cannot be identified to VTAM with the ACB name specified. System Action: Server operation continues. Support for the 3270 and SNALU6.2 COMMmethods is disabled. The server periodically tries to open the ACB and when successful, the 3270 and SNALU6.2 COMMmethods are enabled. User Response: For a description of the reported error code, refer to VTAM Programming. If the ACB has been temporarily varied off, no action is required. The server periodically tries to open the ACB. If the ACB is not defined and the COMMmethods 3270 or SNALU6.2 are not supported for any clients, shut down the server with the HALT command and set the LUNAME statement in the server options file to *NONE*. If COMMmethods 3270 or SNALU6.2 are supported, contact your VTAM (network) administrator to ensure that the ACB name has been properly defined in a member of SYS1.VTAMLST. ANR5061E (S/390) Unable to issue SETLOGON for VTAM ACB Name name, rc code, reas reason, rpl: rtncd return code fdb2 feedback. Explanation: The server detects an error while informing VTAM that it is ready to accept a session. System Action: Server operation continues. Support for the 3270 and SNALU6.2 COMMmethods is disabled. The server periodically tries to reissue the SETLOGON instruction. User Response: For a description of the reported error code, refer to VTAM Programming. ANR5062E (S/390) Unable to allocate number of bytes bytes for VTAM control blocks. Explanation: The server is unable to access the storage it needs to support the COMMmethods 3270 and SNALU6.2. System Action: The COMMmethods 3270 and SNALU6.2 are disabled. If the storage for the global control block cannot be accessed, these COMMmethods remain disabled until the server is shut down with the HALT command and restarted. Otherwise, the server periodically tries to access the needed storage and when successful, the 3270 and SNALU6.2 COMMmethods are enabled. Server operation continues. User Response: If the support for the COMMmethods 3270 and SNALU6.2 is needed immediately, shut down the server (with the HALT command), resolve the storage problem, and restart the server. If the COMMmethods 3270 and SNALU6.2 are not used, shut down the server, set the LUNAME to *NONE*, and restart the server. ANR5063E (S/390) Unable to allocate session number for LU LU ID. Explanation: The server is unable to assign a session number to the incoming session. System Action: Server operation continues. The server rejects the incoming session. User Response: If the MAXSESSIONS statement in the server options file has been set correctly, the end-user (client) must wait until there is a free session before retrying to connect with the server. If the MAXSESSIONS statement is in error, shut down the server, correct the MAXSESSIONS statement, restart the server, and have the client retry connecting with the server. ANR5064E (S/390) Unable to allocate number of bytes bytes for VTAM session with LU LU ID. Explanation: The server is unable to access the storage needed to support the incoming 3270 dial-in session.
Chapter 3. Common and Platform Specfic Messages
397
ANR5065E (S/390) ANR5071W (S/390)
System Action: Server operation continues. The incoming session is rejected. User Response: Allocate additional storage to the server virtual machine. There are four ways to do this: 1. On VM, increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. 2. On MVS, increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server. 3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated. 4. Decrease the amount of space allocated to the servers database buffer pool. To do this, edit the server options 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) to allow changes made to the server options file to take place. ANR5065E (S/390) Unable to open session with LU LU ID CID conversation ID, rc code reason reason, rpl: rtncd return code fdb2 feedback. Explanation: The server encounters an error while accepting an incoming session by way of a VTAM OPNDST instruction. The session is rejected. System Action: Server operation continues. User Response: For a description of error code, refer to VTAM Programming. ANR5066E (S/390) Unable to close session with LU LU ID CID conversation ID, rc code reason reason, rpl: rtncd return code fdb2 feedback. Explanation: The server encounters an error while ending a session. System Action: Server operation continues. User Response: For a description of the error code, refer to VTAM Programming. ANR5067E (S/390) Unable to close VTAM ACB Name name, rc code. Explanation: The server detects an error while closing the ACB for the specified name. System Action: The server proceeds with HALT command processing. User Response: For a description of the reported error code, refer to VTAM Programming. ANR5068E (S/390) Unable to receive on session with LU LU ID CID conversation ID, rc code reason reason, rpl: rtncd return code fdb2 feedback sense sense code. Explanation: The server encounters an error while receiving data on the session. System Action: Server operation continues, and the session is ended. User Response: For a description of the reported error code, refer to VTAM Programming. ANR5069E (S/390) Unable to send on session with LU LU ID CID conversation ID, rc code reason reason, rpl: rtncd return code fdb2 feedback sense sense code. Explanation: The server encounters an error while sending data on the session. System Action: Server operation continues, and the session is ended. User Response: For a description of the reported error code, refer to VTAM Programming. ANR5070I (S/390) 3270 Dial-in driver terminated as requested. Explanation: The servers 3270 dial-in communications driver is ending as requested. System Action: Server operation continues with support for the 3270 COMMmethod disabled. User Response: None. ANR5071W (S/390) Application resource name was defined to VTAM with APPC=NO. Explanation: The specified VTAM application has been defined with APPC=NO. This definition, may be normal for your installation if SNALU6.2 is not used by the clients. If this is true, then this message can be ignored. System Action: Server operation continues. Support for the SNALU6.2 is disabled. User Response: If clients are using SNALU6.2, define the VTAM application with APPC=YES. For the server to recognize the new definition, you must stop the server by using the HALT command and restart the server.
398
IBM Tivoli Storage Manager: Messages
ANR5080I (S/390) ANR5087I (S/390)
ANR5080I (S/390) IUCV driver ready for connection with clients. Explanation: The servers IUCV communications driver is ready to receive connection requests from clients. System Action: Server operation continues. The IUCV is enabled. User Response: None. ANR5081E (S/390) Unable to initialize IUCV driver code code. Explanation: The servers IUCV communications driver cannot initialize itself because it received the error code code when entering the IUCV DECLARE BUFFER function. System Action: Server initialization fails. User Response: For a description of the reported error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system, and the TCP/IP for MVS Programmers Reference for your version of TCP/IP. ANR5082W (S/390) IUCV connection terminated insufficient memory. Explanation: An IUCV connection request is refused by the servers IUCV communications driver because sufficient memory is not available to construct a session. System Action: Server operation continues. User Response: Allocate additional storage to the server virtual machine. There are four ways to do this: 1. On VM, increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. 2. On MVS, increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server. 3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated. 4. Decrease the amount of space allocated to the servers database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4KB of memory to be allocated. Note that the server must be shut down (with the HALT command) before changes can be made to the server options file. ANR5083E (S/390) IUCV connection terminated error code accepting connect request. Explanation: The servers IUCV communications driver is unable to accept a new connection from a client because error code has been received from the IUCV ACCEPT function. System Action: Server operation continues. User Response: For a description of the IUCV ACCEPT error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system, and the TCP/IP for MVS Programmers Reference for your version of TCP/IP. ANR5084W (S/390) IUCV connection terminated server HALT in progress. Explanation: The servers IUCV communications driver refuses a request for a client connection because the HALT command has been entered. System Action: The server rejects the session and proceeds with HALT command processing. User Response: None. ANR5085I (S/390) IUCV driver unable to start. Server terminating. Explanation: The server is unable to start the thread to monitor the status of the IUCV communications driver. System Action: The server shuts down. User Response: If sufficient storage is available when this error occurs, contact your service representative. On MVS, ensure the region size parameter on the JCL is at least 128MB. Otherwise if on VM, ensure that the server virtual machine is at least 128MB in size. ANR5086I (S/390) IUCV driver terminated. Explanation: The IUCV communications driver has shut down. System Action: Server operation continues. Support for the IUCV COMMmethod is disabled. The server periodically tries to restart the IUCV communications driver. User Response: None. ANR5087I (S/390) IUCV driver starting. Explanation: The server is reporting that it is in the process of starting the IUCV communications driver. System Action: The server attempts to initiate a process that will monitor the status of the IUCV communications driver. User Response: None.
Chapter 3. Common and Platform Specfic Messages
399
ANR5088E (S/390) ANR5094W (S/390)
ANR5088E (S/390) Unable to establish a wrap connection - return code code. Explanation: The server is unable to establish an IUCV connection with itself. System Action: Server operation continues. Support for the IUCV COMMmethod is disabled. The server will periodically retry the connect. User Response: For a description of this IUCV CONNECT error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system, and the TCP/IP for MVS Programmers Reference for your version of TCP/IP. ANR5089I (S/390) IUCV driver terminated as requested. Explanation: The servers IUCV communications driver is ending as requested. System Action: Server operation continues with support for the ADMIUCV COMMmethod disabled. User Response: None. ANR5090I (S/390) TCP/IP driver ready for connection with clients on port port number. Explanation: The servers TCP/IP communications driver is ready to receive connection requests from clients. System Action: Server operation continues. Support for the TCP/IP COMMmethod is enabled. User Response: None. ANR5091E (S/390) Unable to initialize TCP/IP driver - insufficient memory. Explanation: The servers TCP/IP communications driver is unable to initialize itself due to insufficient memory (virtual storage). System Action: Server initialization fails. User Response: Allocate additional storage to the server virtual machine. There are four ways to do this: 1. On VM, increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. 2. On MVS, increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server. 3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated. 4. Decrease the amount of space allocated to the servers database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4KB of memory to be allocated. Note that the server must be shut down (with the HALT command) before changes can be made to the server options file. ANR5092E (S/390) Unable to initialize TCP/IP driver - error creating acceptor socket. Explanation: The servers TCP/IP communications driver is unable to create its critical listening socket, and so TCP/IP communications cannot be initialized. System Action: Server initialization continues. TCP/IP communications initialization will be retried. User Response: Check that TCP/IP is running, and that TCPName in the options file matches the TCP/IP subsystem name you intend to use. ANR5093E (S/390) Unable to establish TCP connection - accept error. Explanation: The servers TCP/IP communications driver detects an internal error while attempting to accept a new client connection. System Action: Server operation continues. User Response: Report the error to your service representative. ANR5094W (S/390) Unable to establish TCP connection - insufficient memory. Explanation: A TCP/IP connection request has been refused by the servers TCP/IP communications driver because sufficient memory is not available to construct a session. System Action: Server operation continues. User Response: Allocate additional storage to the server virtual machine. There are three ways to do this: 1. On VM, increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. 2. On MVS, increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server. 3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
400
IBM Tivoli Storage Manager: Messages
ANR5095W (S/390) ANR5102W (S/390)
4. Decrease the amount of space allocated to the servers database buffer pool. To do this, edit the server options 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 server options file. ANR5095W (S/390) Unable to establish TCP connection - server HALT in progress. Explanation: The servers TCP/IP communications driver refuses a request for a client connection because the HALT command has been entered. System Action: The server rejects the session and proceeds with HALT command processing. User Response: None. ANR5096W (S/390) Unable to initialize OE BPX TCP/IP driver - TCP/IP is down level. Explanation: Although the OS/390 is at V2R5 or above the level of TCP/IP is below V3R4 level, and so OE BPX TCP/IP communications cannot be initialized. System Action: Server initialization continues. TCP/IP communications is initialized, instead of OE BPX TCP/IP. User Response: Make sure the TCP/IP V3R4 or above is installed and running in the system if OE BPX TCP/IP communication is to be used. ANR5097I (S/390) TCP/IP driver terminated as requested. Explanation: The servers TCP/IP communications driver is ending as requested. System Action: Server operation continues with support for the TCP/IP COMMmethod disabled. User Response: None. ANR5098I (S/390) TCP/IP driver starting. Explanation: The server is in the process of starting the TCP/IP communications driver. System Action: The server tries to initiate a thread that will monitor the status of the TCP/IP communications driver. User Response: None. ANR5099E (S/390) Unable to initialize TCP/IP driver - error using Port socket number (rc = code). Explanation: The servers TCP/IP communications driver detects an internal error while attempting to use the specified TCP/IP port number. System Action: The server stops listening for TCP/IP sessions. Server operation continues without support for the TCP/IP communications method. The server tries to restart the communications method periodically. User Response: Report the error to your service representative. ANR5100E (S/390) Unable to initialize TCP/IP driver -error listening on Portsocket number (rc = code). Explanation: The servers TCP/IP communications driver detects an internal error while attempting to listen for a connection on the TCP/IP port. System Action: The server ends the TCP/IP acceptor process. Server operation continues without support for the TCP/IP COMMmethod. The server periodically tries to restart the acceptor process. User Response: Report the error to your service representative. ANR5101W (S/390) TCP/IP communications driver terminating. Explanation: The servers TCP/IP communications driver has shut down. System Action: Server operation continues without support for the TCP/IP COMMmethod option. The server periodically tries to restart the TCP/IP communications driver if the server is not in the process of shutting down. User Response: If the server is not in the process of shutting down, this message may indicate that the TCP/IP server is not available or that a server internal error has occurred. Review the console log to determine if an internal error has occurred. If an internal error has occurred, contact your service representative. If the TCP/IP server is unavailable, correct the problem and the server will automatically reinitiate the TCP/IP communications driver. ANR5102W (S/390) Error received for connection connection number (socket socket number). TCP/IP driver will stop, then re-start. Explanation: The servers TCP/IP communications driver received an error for the specified connection. System Action: The server stops the TCP/IP communications driver, and restarts the communications driver.
Chapter 3. Common and Platform Specfic Messages
401
ANR5103I (S/390) ANR5109E (S/390)
User Response: This process may take up to 5 minutes. If the condition persists, report the problem to your service representative. ANR5103I (S/390) CLIO/S (IBM)TCP/IP driver ready for service on port clio port number. Explanation: The servers CLIO/S TCP/IP communications driver is ready to handle connection requests to and from AIX clients using COMMmethod CLIO through an IBM TCP/IP host network. System Action: Server operation continues. Support for the TCPName and CLIOPort server options is enabled. User Response: None. ANR5104E (S/390) Unable to initialize CLIO/S (IBM)TCP/IP driver - error creating listening socket. Explanation: The servers CLIO/S communication driver is unable to create its critical listening socket; therefore, CLIO/S (IBM)TCP/IP communication cannot be initialized. System Action: Server initialization continues. CLIO/S (IBM)TCP/IP communication initialization will be retried every minute. This message will be suppressed after being issued for the third time; however, attempts to initialize CLIO/S communications will continue every minute until message ANR5103I is issued indicating CLIO/S driver is ready for service. User Response: Check that TCP/IP is running, and that TCPName, in the options file, matches the name of the target TCP/IP address space. ANR5105I (S/390) Interlink TCPaccess driver is ready for service on port interlink port number. Explanation: The servers Interlink TCPaccess communications driver is ready to receive connection requests from clients connected through Interlink TCPaccess. System Action: Server operation continues. Support for the ICSSname and ICSPort server options is enabled. User Response: None. ANR5106E (S/390) Unable to initialize Interlink TCPaccess driver - error opening listen endpoint. Explanation: The servers Interlink TCPaccess driver is unable to create its critical listen endpoint; Interlink TCPaccess communication cannot be initialized. System Action: Server initialization continues. Interlink TCPaccess communications will be retried every minute and this message will suppressed after being issued three times. User Response: Check that TCPaccess is running and that ICSSname, in the options file, matches the TCPaccess subsystem name you intend to use. The ICSSname option should match the SSN parameter of the PROC statement in the TCPaccess startup procedure. Refer to Interlink TCPaccess publications for details. ANR5107E (S/390) Unable to initialize CLIO/S (IBM)TCP/IP driver - error binding acceptor socket socket number (rc = code). Explanation: The servers TCP/IP communications driver detects an error while attempting to bind the acceptor socket. System Action: The server ends the TCP/IP acceptor process. Server operation continues without support for the TCP/IP COMMmethod. The server tries to restart the acceptor process periodically. User Response: Check that TCP/IP is running and that TCPName, in the options file, matches the name of the target TCP/IP address space. ANR5108E (S/390) The CLIO/S functions have not been linked into this module. Explanation: The server cannot find the CLIO/S functions required to support CLIO (IBM)TCP/IP communications. System Action: The connection to the server fails. User Response: The cause of this error is the omission of the required post-SMP/E link-edit step to merge CLIO functions from SYS1.SFCFLIB(FCFIADSM). Before retrying the operation, ensure that your installation has performed the required post install link-edit step. Find the ADSM SAMPLIB and use member ANRCLIOK for an example of the required post-SMP/E link edit to load ANRSERV with CLIO/S communication code. ANR5109E (S/390) The CLIO/S communication driver cannot be started. Explanation: The server is unable to start the CLIO/S communication driver because either TCPPort and CLIOPort server options are the same value or TCPName is coded with *NONE*. System Action: The CLIO/S communication option will not be available and server initialization continues. User Response: Check the server options file to ensure CLIOPort and TCPPort values are different. If the CLIOPort and TCPPort options are specified correctly, check the TCPName option to ensure *NONE* is not coded for this option. Specify a unique CLIOPort value and ensure a valid TCPName parameter is coded to allow the (IBM)TCP/IP CLIO/S communication driver
402
IBM Tivoli Storage Manager: Messages
ANR5110I (S/390) ANR5116I (S/390)
to start. CLIOPort has no default value; however, TCPPort and TCPName default to 1500 and TCPIP respectively. This message can be eliminated if CLIO/S communication is not required by removing the CLIOPort option from the server option file and recycling the server. ANR5110I (S/390) 3270 Dial-in driver ready for connection with clients. Explanation: The servers 3270 dial-in communications driver is ready to receive connection requests from clients. System Action: Server operation continues. Support for the 3270 COMMmethod is enabled. User Response: None. ANR5111E (S/390) Unable to initialize 3270 dial-in driver - error defining GRAF devices. Explanation: The servers 3270 dial-in communications driver is unable to define one or more CP GRAF devices, and is therefore unable to initialize itself. System Action: Server initialization fails. User Response: Contact your service representative. ANR5112W (S/390) Unable to define additional GRAF devices for dial-in. Explanation: The servers 3270 dial-in communications driver is unable to define additional CP GRAF devices, and may not be able to accept subsequent connections from clients. System Action: Server operation continues. User Response: Contact your service representative. ANR5113W (S/390) 3270 dial-in session terminated insufficient memory. Explanation: A 3270 dial-in connection request has been refused by the servers 3270 communications driver because sufficient memory is not available to construct a session. System Action: Server operation continues. User Response: Allocate additional storage to the server virtual machine. There are three ways to do this: 1. On VM, increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. 2. On MVS, increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server. 3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the
Chapter 3. Common and Platform Specfic Messages
MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated. 4. Decrease the amount of space allocated to the servers database buffer pool. To do this, edit the server options 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 server options file. ANR5114W (S/390) 3270 dial-in session terminated device does not support structured fields. Explanation: The servers 3270 communications driver has refused a client connection request because the 3270 device initiating the connection does not support structured fields. System Action: Server operation continues. User Response: Retry the 3270 connection from a device that properly supports structured fields. ANR5115W (S/390) 3270 dial-in session terminated emulator not supported. Explanation: The servers 3270 dial-in communications driver has refused a connection request from a client, because the clients 3270 emulator does not or is not configured for the level of 3270 extended data stream support that the server requires. System Action: Server operation continues. User Response: Retry the 3270 connection by using a supported emulator program, such as the OS/2 Communications Manager, or the IBM Personal Communications/3270 program. ANR5116I (S/390) 3270 Dial-in driver unable to start. Server terminating. Explanation: The server is unable to start the thread that monitors the status of the 3270 dial-in communications driver. System Action: The server shuts down. User Response: If sufficient storage is available when this error occurs, contact your service representative. Otherwise for VM, ensure that the storage for the server virtual machine is at least 128MB. For MVS, ensure the region size parameter on the JCL is at least 128MB.
403
ANR5117I (S/390) ANR5127W (S/390)
ANR5117I (S/390) 3270 Dial-in driver terminated. Explanation: The 3270 dial-in communications driver has shut down. System Action: Server operation continues. Support for the 3270 COMMmethod is disabled. The server periodically tries to restart the 3270 dial-in communications driver. User Response: None. ANR5118I (S/390) 3270 Dial-in driver starting. Explanation: The server is reporting that it is in the process of starting the 3270 dial-in communications driver. System Action: The server tries to initiate a process that will monitor the status of the 3270 dial-in communications driver. User Response: None. ANR5120I (S/390) APPC driver unable to start. Server terminating. Explanation: The server is unable to start the thread that monitors the status of the APPC communications driver. System Action: The server shuts down. User Response: If sufficient storage is available when this error occurs, contact your service representative. Otherwise for VM, ensure that storage for the server virtual machine is at least 128MB. For MVS, ensure the region size parameter on the JCL is at least 128MB. ANR5121I (S/390) APPC driver ready for connections with clients on resource resource name. Explanation: The servers APPC communications driver is reporting that it is ready to receive connection requests from clients. System Action: Server operation continues. Support for the SNALU6.2 COMMmethod is enabled. User Response: None. ANR5122I (S/390) APPC driver terminated. Explanation: The APPC communications driver has shut down. System Action: Server operation continues. Support for the SNALU6.2 COMMmethod is disabled. The server periodically tries to restart the APPC communications driver. User Response: None. ANR5124E (S/390) APPC driver unable to declare as resource resource name, rc code, reason reason. Explanation: The server cannot connect to the *IDENT (the Identify System Service) to identify itself as the resource manager for the resource specified. System Action: Server operation continues. Support for the SNALU6.2 COMMmethod is disabled. The server periodically tries to restart the APPC communications driver. User Response: Ensure that the following IUCV statement is present in the CP directory entry for the server: IUCV *IDENT appc-resource GLOBAL REVOKE. ANR5125E (S/390) APPC connection terminated error code accepting connect request. Explanation: The servers APPC communications driver is unable to accept a new connection from a client, because error code has been received from the IUCV ACCEPT function. System Action: Server operation continues. User Response: For a description of the IUCV ACCEPT error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system. ANR5126W (S/390) APPC connection terminated server HALT in progress. Explanation: The servers APPC communications driver refuses a request for a client connection because the HALT command has been entered. System Action: The server rejects the session and proceeds with HALT command processing. User Response: None. ANR5127W (S/390) APPC connection terminated insufficient memory. Explanation: An IUCV connection request is refused by the servers APPC communications driver because sufficient memory is not available to construct a session. System Action: Server operation continues. ANR5123I (S/390) APPC driver starting. Explanation: The server is reporting that it is in the process of starting the APPC communications driver. System Action: The server tries to initiate a thread that will monitor the status of the APPC communications driver. User Response: None.
404
IBM Tivoli Storage Manager: Messages
ANR5128E (S/390) ANR5132W (S/390)
User Response: Allocate additional storage to the server virtual machine. There are three ways to do this: 1. On VM, increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. 2. On MVS, increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server. 3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated. 4. Decrease the amount of space allocated to the servers database buffer pool. To do this, edit the server options 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 server options file. ANR5128E (S/390) Unable to allocate session number for LU LU ID. Explanation: The server is unable to assign a session number to the incoming session. System Action: Server operation continues. The server rejects the incoming session. User Response: If the MAXSESSIONS statement in the server options file has been set correctly, the end-user (client) must wait until there is a free session before retrying to connect with the server. If the MAXSESSIONS statement is in error, shut down the server, correct the MAXSESSIONS statement, restart the server, and have the client retry to connect with the server. ANR5129W (S/390) VTAM APPC (LU62) conversation terminated - server HALT in progress. Explanation: The servers APPC communications driver rejects a conversation because the HALT command has been entered. System Action: The server rejects the conversation and proceeds with HALT command processing. User Response: None. ANR5130W (S/390) VTAM APPC (LU62) conversation (conversation ID) with LU LU ID terminated - insufficient memory. Explanation: An APPC conversation has been terminated by the servers APPC communications
Chapter 3. Common and Platform Specfic Messages
driver because sufficient memory is not available to support this conversation. System Action: Server operation continues. The conversation is deallocated. User Response: Allocate additional storage to the server virtual machine. There are three ways to do this: 1. Increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server. 2. Reduce the maximum number of client sessions permitted. To do this, edit the server options 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 server options 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 server options file. ANR5131I (S/390) APPC driver terminated as requested. Explanation: The servers APPC communications driver is reporting that it is terminating as requested. System Action: Server operation continues with support for the SNALU6.2 COMMmethod disabled. User Response: None. ANR5132W (S/390) VTAM APPC (LU62) support is not available with current session. Explanation: The servers VTAM APPC (LU6.2) communications driver is not available. Clients that use the SNALU6.2 communications method cannot establish a session with the server. Refer to ANR5071W, which was displayed prior to this message, for additional information. If the SNALU6.2 communication method is not used, ignore this message and message ANR5071W. System Action: Server operation continues without support for the SNALU6.2 COMMmethod. User Response: Verify that the server application is defined correctly to VTAM. APPC=YES must be specified with the VTAM APPL macro when defining the server application when SNALU6.2 support is used.
405
ANR5133W (S/390) ANR5204I (S/390)
ANR5133W (S/390) VTAM APPC (LU62) connect request rejected. Explanation: A clients VTAM APPC (LU6.2) connect request was rejected because the LU6.2 communications driver is not available. This process may be the result of the server application not being defined correctly to VTAM. The application must be defined with APPC=YES with the APPL macro to enable SNALU6.2 support on the server. System Action: VTAM message IST663I and other related messages are displayed; server operation continues. User Response: Verify that the server application is defined correctly to VTAM. APPC=YES must be specified with the VTAM APPL macro when defining the server application. ANR5140I (S/390) HTTP (IBM) communications is listening for clients on port port number. Explanation: The servers HTTP (IBM) TCP/IP communications driver is ready to receive connection requests from Web clients. System Action: Server operation continues. Support for Web Client HTTP communication is enabled. User Response: None. ANR5142I (S/390) TCP/IP Administrative driver ready for connection with clients on port port number. Explanation: The servers TCP/IP communications driver for administrators is ready to receive connection requests from administrative clients and other systems. System Action: Server operation continues. User Response: None. ANR5143I (S/390) TCP Access Administrative driver ready for connection with clients on port port number. Explanation: The servers TCP Access communications driver for administrators is ready to receive connection requests from administrative clients and other systems. System Action: Server operation continues. User Response: None. ANR5148I (S/390) HTTP (TCPaccess) driver is listening for clients on port port number. Explanation: The servers HTTP (TCPaccess) TCP/IP communications driver is ready to receive connection requests from Web clients. System Action: Server operation continues. Support for Web Client HTTP over TCPaccess is enabled. User Response: None. ANR5200S (S/390) Unable to connect to the *MSG System Service, rc = code. Explanation: The server receives return code code from the IUCV CONNECT function when connecting to the *MSG System Service. System Action: The server shuts down. User Response: Determine the cause of the error code, correct the problem, and restart the server. For a description of the reported error code, refer to the IUCV documentation in the CP Programming Services publication, or the publication for your operating system that contains documentation for the IUCV CONNECT function. ANR5201S (S/390) Error code from *MSG System Service path path ID. Explanation: An error occurs on the IUCV path to the *MSG System Service. System Action: The server shuts down. User Response: Determine the cause of the error code, correct the problem, and restart the server. For a description of the reported error code, refer to the IUCV documentation in the CP Programming Services publication, or the publication for your operating system that contains IUCV documentation. ANR5202E (S/390) Unable to communicate with any Notify user ID. Explanation: The server is unable to send a message to any user ID specified on the NOTIFY option in the DSMSERV OPT file. System Action: Server operation continues. User Response: Have someone with an authorized NOTIFY user ID log on to the system. ANR5203E (S/390) Unable to communicate with any Mount Operator. Explanation: The server is unable to send a message to any user ID specified on the MOUNTOP option in the DSMSERV OPT file. System Action: Server operation continues. User Response: Have someone with an authorized MOUNTOP user ID log on to the system. ANR5204I (S/390) Autolog-response Explanation: The result of the XAUTOLOG command for the mount exit virtual machine is Autolog-response. System Action: Server operation continues.
406
IBM Tivoli Storage Manager: Messages
ANR5205I (S/390) ANR5215I (S/390)
User Response: None. ANR5205I (S/390) From userid: msg. Explanation: The message msg has been received from a nonauthorized user ID userid. System Action: Server operation continues. User Response: If the user ID userid is a server mount operator, ensure that the user ID is in the MOUNTOP list in the server options file. ANR5208I (S/390) Dismounting volume volser (updated). 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. System Action: Server operation continues. User Response: None. ANR5209I (S/390) 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. System Action: Server operation continues. User Response: None. ANR5210I (S/390) Request number: Mount devclass volume ID at vaddr mode within number of minutes minutes. Explanation: The server has requested a volume be mounted. System Action: The running task waits until the mount is satisfied or canceled. User Response: Use the DSMOP command to satisfy or cancel the mount request. ANR5211I (S/390) Request number: Mount devclass volume ID at vaddr mode (format) within number of minutes minutes. Explanation: The server has requested a volume with a specific format be mounted. System Action: The running task waits until the mount is satisfied or canceled. User Response: Use the DSMOP command to satisfy or cancel the mount request. ANR5212I (S/390) Request number: Mount devclass volume ID at vaddr mode via Exit Machine machine name. Explanation: The server has requested a volume be mounted. System Action: The running task waits until the mount is satisfied or canceled. User Response: Use the DSMOP command to satisfy or cancel the mount request. ANR5213I (S/390) Request number: Mount devclass volume ID at vaddr mode (format) via Exit Machine machine name. Explanation: The server has requested a volume with a specific format be mounted. System Action: The running task waits until the mount is satisfied or canceled. User Response: Use the DSMOP command to satisfy or cancel the mount request. ANR5214I (S/390) Request number: Mount devclass volume ID at vaddr mode waiting for available Exit Machine. Explanation: The server has requested a volume be mounted. System Action: The running task waits until the mount is satisfied or canceled. User Response: Use the DSMOP command to satisfy or cancel the mount request. ANR5215I (S/390) Request number: Mount devclass volume ID at vaddr mode (format) waiting for available Exit Machine. Explanation: The server has requested a volume be mounted. System Action: The running task waits until the mount is satisfied or canceled. User Response: Use the DSMOP command to satisfy or cancel the mount request.
Chapter 3. Common and Platform Specfic Messages
407
ANR5216I (S/390) ANR5227E (S/390)
ANR5216I (S/390) 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. System Action: Server operation continues. User Response: Locate the specified volume and be prepared to make it available to the server. ANR5217I (S/390) 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. System Action: Server operation continues. User Response: None. ANR5218I (S/390) Detaching tape device vaddr - not requested by server. Explanation: The virtual address vaddr is detached because it has not been requested by the server. System Action: Server operation continues. User Response: Check the virtual address requested by the server for tape mounts. Reissue the CP ATTACH command and specify the correct virtual address. ANR5220I (S/390) Deleting type volser from Storage Pool pool. Explanation: The volume volser of device type type has been removed from storage pool pool. System Action: Server operation continues. User Response: The server no longer uses the volume specified. You can return the volume to the scratch pool. ANR5221I (S/390) Request: Delete type volser via Exit Machine userid. Explanation: The deletion of volume volser of device type type is scheduled for Mount Exit Virtual Machine userid as request number request. System Action: Server operation continues. User Response: None. ANR5222I (S/390) Request: Delete type volser waiting for available Exit Machine. Explanation: The deletion of volume volser of device type type is waiting for an available Mount Exit Virtual Machine userid as request number request. System Action: Server operation continues. User Response: None. ANR5223E (S/390) Deletion Exit for volser (storage pool pool) failed - unknown Rc=rc. Explanation: The deletion of volume volser in storage pool pool fails. System Action: Server operation continues. User Response: Contact service representative. ANR5224E (S/390) Deletion Exit for volser (storage pool pool) failed - ExitRc=rc, Rc=abend-indicated. Explanation: The deletion of volume volser in storage pool pool fails. System Action: Server operation continues. 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 exit has abended, the indicator abend-indicated is nonzero. ANR5225E (S/390) Deletion Exit for volser (storage pool pool) failed - unable to get device class information. Explanation: The deletion of volume volser in storage pool pool has failed due to an internal server error. System Action: Server operation continues. User Response: Contact your service representative. ANR5226E (S/390) Deletion Exit for volser (storage pool pool) failed - unable to start background thread. Explanation: The deletion of volume volser in storage pool pool has failed due to an internal server error. System Action: Server operation continues. User Response: Contact your service representative. ANR5227E (S/390) Deletion Exit for volser (storage pool pool) failed - insufficient memory. Explanation: The deletion of volume volser in storage pool pool fails due to lack of available storage. System Action: Server operation continues.
408
IBM Tivoli Storage Manager: Messages
ANR5228I (S/390) ANR5234E (S/390)
User Response: Increase the region or virtual machine size for the server or reduce the MAXSESSIONS value in the server options file. ANR5228I (S/390) Deleting type volser from volume history (previous use volume). Explanation: The volume volser in device type type has been deleted from the volume history. It was previously used for previous use. System Action: Server operation continues. User Response: The server no longer tracks the volume specified. You can return the volume to the scratch pool. ANR5229W (S/390) 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. System Action: Server operation continues. 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. ANR5230I (S/390) Request number: Starting Exit Machine mountvm to mount devclass volume ID. Explanation: The server has autologged a mount exit virtual machine to handle a mount request. System Action: The server autologs a mount exit virtual machine. User Response: None. ANR5231I (S/390) Request number: Starting Exit Machine mountvm to delete devclass volume ID. Explanation: The server autologs a mount exit virtual machine to handle a mount delete request. System Action: The server autologs a mount exit virtual machine. User Response: None. ANR5232W (S/390) [XAUTOLOG] mountvm failed with return code code. Explanation: An error occurs during XAUTOLOG of a mount exit virtual machine. System Action: The server retries the command. If the command continues to fail, the mount exit machine is marked off-line, and another mount exit machine is used. User Response: If the mount exit machine is placed in the off-line status, determine the cause, correct the problem, and use the DSMOP or administrator READY EXIT command to restore the mount exit machine to the ready status. ANR5233E (S/390) Exit Machine mountvm taken offline - nn command attempts failed. Explanation: The number of XAUTOLOG attempts has exceeded an internal threshold. The mount exit virtual machine is no longer used. System Action: The server marks the mount exit virtual machine off-line. User Response: To make the mount exit machine available, determine the cause of the autolog failure. Correct the problem and use the DSMOP or administrator READY EXIT command to restore the mount exit machine to the ready status. ANR5234E (S/390) All Exit Machines are Offline. Explanation: All the defined mount exit virtual machines have been placed in the off-line status by the server. System Action: Any mount requests by the server are queued. User Response: Determine the cause of the autolog failures of all the mount exit virtual machines, correct any problems and use the DSMOP or administrator READY EXIT command to make the mount exit machines available.
Chapter 3. Common and Platform Specfic Messages
409
ANR5240E (S/390) ANR5258E (S/390)
ANR5240E (S/390) Request number: Mount for volume ID has timed out. Explanation: The mount request has not been satisfied in the requested time. System Action: The server cancels the mount request. User Response: None. ANR5241E (S/390) Exit Machine mountvm not logged on, mount for volume ID cancelled. Explanation: A mount exit virtual machine has logged off without satisfying the servers mount request. System Action: The server cancels the mount request. User Response: None. ANR5250E (S/390) Command: User user ID not authorized. Explanation: An unauthorized user has attempted to enter a DSMOP command. System Action: The server does not process the command. User Response: If the user should be authorized, add that user ID on the REPLYOP option in the DSMSERV OPT file. ANR5251E (S/390) Command: Invalid request number - request number. Explanation: A DSMOP command has been entered with an incorrect request number. System Action: The server does not process the command. User Response: Enter the command with the correct request number. ANR5252E (S/390) Command: No match found for this request number. Explanation: The request number specified by the DSMOP command is not in the list of outstanding mount requests. System Action: The server does not process the command. User Response: Enter the command with the correct request number. ANR5253E (S/390) Request: Invalid device address raddr. Explanation: The response to server request number request has specified an invalid real device address raddr. System Action: Server operation continues. User Response: Respond to the request again, by specifying a valid real device address. ANR5254E (S/390) Command: CP command command name failed. Explanation: A DSMOP CANCEL REQUEST or a DSMOP REPLY command fails. System Action: The server tries to enter the CP command command and receives a nonzero return code. User Response: If you have entered a DSMOP CANCEL REQUEST, force the mount exit virtual machine to cancel the mount request with the FORCE option. To use the DSMOP CANCEL REQUEST command when running the mount exit, the server must have FORCE privilege. If you have entered a DSMOP REPLY command, attach the device to the server with the ATTACH option. To use the DSMOP REPLY command, the server must have ATTACH privilege. ANR5255E (S/390) Command: No matching Exit Machines were found Offline. Explanation: A READY EXIT command has been issued and all Mount Exit Virtual Machines are ready. System Action: Server operation continues. User Response: None. ANR5256E (S/390) Command: Invalid match pattern specified for Exit Machine name. Explanation: A DSMOP READY command has been entered specifying a user ID that is not a defined mount exit virtual machine. System Action: The server does not process the command. User Response: Enter the command and specify the correct mount exit virtual machine name. ANR5257I (S/390) Command: No requests outstanding. Explanation: A DSMOP QUERY MOUNTS command has been entered when no mount requests are outstanding. System Action: Server operation continues. User Response: None. ANR5258E (S/390) Command: Command not valid when Exit is active. Explanation: A DSMOP REPLY command has been entered by a reply operator when the mount exit is active.
410
IBM Tivoli Storage Manager: Messages
ANR5259E (S/390) ANR5268I (S/390)
System Action: The server does not process the command. User Response: The DSMOP REPLY command is invalid when the mount exit is used. When using mount exit machines, all mount requests are issued from the mount exit machines using your installations procedures. ANR5259E (S/390) Command: Command not valid when Exit is not active. Explanation: A DSMOP READY command or a DSMOP QUERY EXITS command has been entered when the mount exit is not being used. System Action: The server does not process the command. User Response: None. ANR5260E (S/390) Command: Volume volume not found. Explanation: A DISMOUNT VOLUME command was issued, but the volume to be dismounted cannot be found. System Action: Server operation continues. User Response: Ensure that the correct volume name is entered. ANR5261E (S/390) Command: Volume volume is not Idle. Explanation: A DISMOUNT VOLUME command has been issued, but the volume is in use and cannot be dismounted. System Action: Server operation continues. User Response: If it is necessary to dismount the volume, cancel the session or process that is using the volume, and reissue the command. ANR5262E (S/390) Command: Device raddr not found. Explanation: A DISMOUNT DEVICE command has been issued, but the device to be dismounted cannot be found. System Action: Server operation continues. User Response: Ensure that the correct device has been specified. ANR5263E (S/390) Command: Device raddr is not Idle. Explanation: A DISMOUNT DEVICE command has been issued, but the device is in use and cannot be dismounted. System Action: Server operation continues. User Response: If it is necessary to dismount the device, cancel the session or process that is using the volume, and reissue the command. ANR5264I (S/390) Command not executed - password has expired. Explanation: An administrative command has been issued, but the administrators password has expired. System Action: Server operation continues. User Response: Update your password by starting an administrative client session. Alternatively, the server system administrator may use the UPDATE ADMIN command to update an administrators password. ANR5265I (S/390) Command not executed administrator name is locked. Explanation: An administrative command has been issued, but the administrators user ID is locked from accessing the server. System Action: Server operation continues. User Response: The server system administrator can issue the UNLOCK ADMIN command to restore access to a server administrative user ID. ANR5266I (S/390) Command not executed insufficient memory. Explanation: An administrative command has been issued, but there is insufficient memory to execute the command. System Action: Server operation continues. User Response: Increase the region or virtual machine size for the server or lower the MAXSESSIONS parameter in the server options file and restart the server. ANR5267I (S/390) Command not executed - internal error detected. Explanation: An administrative command has been issued, but there is a detected internal processing error that prevents the command from executing. System Action: Server operation continues. User Response: Look for preceding message concerning access to administrative user ID information within the server and contact your service representative. ANR5268I (S/390) Command not executed insufficient recovery log space. Explanation: An administrative command has been issued, but there is insufficient recovery log space to complete the database transaction.
Chapter 3. Common and Platform Specfic Messages
411
ANR5269I (S/390) ANR5289I (S/390)
System Action: Server operation continues. User Response: To increase the amount of log space available to the server, an authorized admininstrator can add log volumes using the DEFINE LOGVOLUME command, and extend the size of the log using the EXTEND LOG command. ANR5269I (S/390) Command not executed insufficient database space. Explanation: An administrative command has been issued, but there is insufficient database space to complete the database transaction. System Action: Server operation continues. User Response: To increase the amount of database space available to the server, an authorized admininstrator can add database volumes using the DEFINE DBVOLUME command, and extend the size of the database using the EXTEND DB command. ANR5270I (S/390) SMFWTM macro return code 40 (buffer shortage). Explanation: SMFWTM completed with return code 40. System Action: The server continues to operate. User Response: Increase SMF buffer limit or disable server accounting. ANR5280I (S/390) Command accepted. Explanation: A DSMOP REPLY command is accepted. System Action: The server processes the DSMOP REPLY command. User Response: None. ANR5287I (S/390) Exit Machine mountvm: Busy. ANR5281I (S/390) Request request number for volume ID canceled by user ID. Explanation: A mount request is successfully canceled. System Action: The system cancels the mount request. User Response: None. ANR5288I (S/390) Exit Machine mountvm: Offline. ANR5282I (S/390) Request request number for volume ID cancelled (PERM) by user ID. Explanation: A mount request is successfully canceled with the PERM option. System Action: The system cancels the mount request and marks the volume as unavailable. User Response: None. Explanation: The status of a mount exit virtual machine is off-line. System Action: Server operation continues. User Response: None. ANR5289I (S/390) 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. Explanation: The status of a mount exit virtual machine is busy. System Action: Server operation continues. User Response: None. ANR5283I (S/390) Exit Machine mountvm status set to Ready. Explanation: A DSMOP READY command has been entered. System Action: The server changes the status of the mount exit virtual machine to ready. User Response: None. ANR5284I (S/390) Requests outstanding: Explanation: The list of currently outstanding mount requests follows. System Action: The server lists all outstanding mount requests or the one specified on the DSMOP QUERY command. User Response: None. ANR5285I (S/390) Exit Machine Status: Explanation: The list of mount exit virtual machine status follows. System Action: The server lists the status of all mount exit virtual machines or the status of the one specified on the DSMOP QUERY command. User Response: None. ANR5286I (S/390) Exit Machine mountvm: Ready. Explanation: The status of a mount exit virtual machine is ready. System Action: Server operation continues. User Response: None.
412
IBM Tivoli Storage Manager: Messages
ANR5290I (S/390) ANR5302I (S/390)
System Action: Server operation continues. User Response: None. ANR5290I (S/390) Volume volume (class class) mounted mode on raddr, status: In Use. Explanation: Volume volume, which is of device class class and is mounted at address raddr in mode mode, is in use by the server. System Action: Server operation continues. User Response: None. ANR5291I (S/390) Volume volume (class class) mounted mode on raddr, status: Dismounting. Explanation: Volume volume, which is in device class class and is mounted at address raddr in mode mode, is in the process of dismounting. System Action: Server operation continues. User Response: None. ANR5292I (S/390) number volume(s) found. ANR5297I (S/390) Volume volume (class class) mounted mode, status: In Retry. Explanation: Volume volume, which is in device class 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. System Action: Server operation continues. User Response: None. ANR5300I (S/390) Verifying volume label volume ID on device real address. Explanation: The server is verifying the volume label of a mounted read/write volume again prior to dismounting the volume. System Action: The server performs the reverification of the volume label as an integrity check of the volume. User Response: None. ANR5301I (S/390) Request number: Verifying volume label volume ID on device device. Explanation: The server is verifying the volume label of a mounted volume during the mount process. System Action: The server ensures that the volume mounted is acceptable. User Response: None. ANR5302I (S/390) Request number: Assigning volume volume ID to SCRTCH. Explanation: The server has assigned the mounted volume to be used as the requested scratch volume. System Action: The server dynamically adds the volume label of the mounted volume to the storage pool. User Response: None. ANR5296I (S/390) Volume volume (class class) mounted mode, status: Dismounting. Explanation: Volume volume, which is in device class class in mode mode, is in the process of dismounting. System Action: Server operation continues. User Response: None. User Response: None.
Explanation: A QUERY MOUNT command has been issued; number volumes are mounted. System Action: Server operation continues. User Response: None. ANR5293I (S/390) Cancelling mount for volume volume. Explanation: A CANCEL MOUNT command has been issued for volume volume. The CANCEL command is being processed. System Action: Server operation continues. User Response: Query the activity log to verify that the mount request has been cancelled. ANR5294I (S/390) Volume volume (class class) mounted mode, status: Idle. Explanation: Volume volume, which is in device class class in mode mode, is eligible for dismounting or reuse. System Action: Server operation continues. User Response: None. ANR5295I (S/390) Volume volume (class class) mounted mode, status: In Use. Explanation: Volume volume, which is in device class class in mode mode, is in use by the server. System Action: Server operation continues.
Chapter 3. Common and Platform Specfic Messages
413
ANR5303I (S/390) ANR5311E (S/390)
ANR5303I (S/390) Request number: Assigning volume volume ID to EXPORT. Explanation: The server has assigned the mounted volume to be used as the requested export volume. System Action: The server uses the volume for the EXPORT operation. User Response: None. ANR5304I (S/390) Request number: Assigning volume volume ID to IMPORT. Explanation: The server has assigned the mounted volume to be used as the requested import volume. System Action: The server uses the volume for the IMPORT operation. User Response: None. ANR5305E (S/390) Request number: Device real address is not a supported devclass device. Explanation: A device is attached to the server to satisfy a mount request, but it is the wrong 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. ANR5306E (S/390) Request number: Device real address not capable. Explanation: The server requested a volume with a specific density or format. The device used to satisfy the mount cannot write using the requested density or format. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Mount the volume on a device capable of the requested density or format. ANR5307E (S/390) Request number: Volume on real address is write protected. Explanation: The mounted volume is not enabled for writing. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Enable the volume for writing and reply to the mount again. ANR5308E (S/390) Request number: Volume on real address is not write protected. Explanation: The mounted volume is not write protected. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Disable the volume for writing and reply to the mount again. ANR5309E (S/390) Request number: Volume on real address has no VOL1 label. Explanation: The mounted volume does not have a standard label. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Make sure you are mounting the correct volume. All volumes must have a standard VOL1 label. ANR5310E (S/390) Volume on real address has no VOL1 label - volume integrity compromised. Explanation: During volume unmount label reverification, the server finds no VOL1 label. System Action: The server marks the volume as unavailable. User Response: The volume cannot be used because the VOL1 label has been overwritten. All active data on the volume cannot be recovered. Delete the volume from the storage pool with the DELETE VOLUME command by using the DISCARD=YES option. To use this volume again, the volume must be initialized with a VOL1 label. The volume may then be redefined in the storage pool. ANR5311E (S/390) Request number: Volume label on raddr (volume ID found) does not match volume ID expected. Explanation: During mount processing, the volume ID read on the mounted volume does not match the specifically requested partially full volume. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Make sure you are mounting the correct volume.
414
IBM Tivoli Storage Manager: Messages
ANR5312E (S/390) ANR5322I (S/390)
ANR5312E (S/390) Volume label on raddr (volume ID found) does not match volume ID expected - volume integrity compromised. Explanation: During volume unmount label reverification, the server finds a different VOL1 label. System Action: The server marks the volume as unavailable. User Response: The volume cannot be used because the VOL1 label has been overwritten by a different VOL1 label. All active data on the volume cannot be recovered. Delete the volume from the repository with the DELETE VOLUME command by using the NORECLAIM option. To use this volume again, the volume must be initialized with a VOL1 label. The volume may then be redefined in the repository. ANR5313I (S/390) Request number: Mount for volume ID complete on device real address. Explanation: A volume mount has successfully completed. System Action: The task waiting for a volume mount resumes. User Response: None. ANR5314E (S/390) Request number: Permanent I/O error on device real address. Explanation: A permanent I/O error occurred when the device was opened. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Mount the volume on a different device. ANR5315E (S/390) Read Data Check on device real address. Explanation: A data check occurred during a read operation. System Action: The server redrives the I/O by using Diagnose X'20' or Diagnose X'A8'. User Response: None. ANR5316E (S/390) Write Data Check on device real address. Explanation: A data check occurred during a write operation. System Action: The server redrives the I/O by using Diagnose X'20' or Diagnose X'A8'. User Response: None. ANR5317I (S/390) Make device real address ready. Explanation: The device is in a not ready condition. System Action: The server sends an intervention required message to the mount operator user IDs listed in the DSMSERV OPT file. User Response: Make the device ready. ANR5318I (S/390) Intervention cleared on device real address. Explanation: The device requiring operator intervention is now ready. System Action: The task waiting for the device continues. User Response: None. ANR5319I (S/390) Intervention required on device real address. Explanation: The device requires operator intervention. System Action: The task waits until the device is made ready. User Response: Make the device ready. ANR5320I (S/390) 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. System Action: The server dismounts the volume, detaches the device, and reissues the original request. User Response: Mount a volume not already in use by the server. ANR5321I (S/390) 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. User Response: None. ANR5322I (S/390) Permanent error on volume volume ID on device real address. Explanation: During processing of a tape volume, a permanent I/O error occurred. System Action: The server places the volume in an I/O error state. If the volume was being used for writing, it is marked read-only.
Chapter 3. Common and Platform Specfic Messages
415
ANR5323I (S/390) ANR5331S (S/390)
User Response: None. ANR5323I (S/390) Assigning volume volume ID to SCRTCH. Explanation: The server has assigned the mounted volume to be used as the requested scratch volume. System Action: The server dynamically adds the volume label of the mounted volume to the storage pool. User Response: None. ANR5324I (S/390) Assigning volume volume ID to EXPORT. Explanation: The server has assigned the mounted volume to be used as the requested export volume. System Action: The server uses the volume for the EXPORT operation. User Response: None. ANR5325I (S/390) Assigning volume volume ID to IMPORT. Explanation: The server has assigned the mounted volume to be used as the requested import volume. System Action: The server uses the volume for the IMPORT operation. User Response: None. ANR5326E (S/390) Volume label on raddr (volume ID found) does not match volume ID expected. Explanation: During mount processing, the volume ID read on the mounted volume does not match the specifically requested partially full volume. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Make sure you are mounting the correct volume. ANR5327I (S/390) Request number: Assigning volume volume ID to DUMPDB. Explanation: The server has assigned the mounted volume to be used as the requested DUMPDB volume. System Action: The server uses the volume for the DUMPDB operation. User Response: None. ANR5328I (S/390) Request number: Assigning volume volume ID to LOADDB. Explanation: The server assigns the mounted volume for use as the requested LOADDB volume. System Action: The server uses the volume for the LOADDB operation. User Response: None. ANR5329I (S/390) Assigning volume volume ID to DUMPDB. Explanation: The server assigns the mounted volume for use as the requested DUMPDB volume. System Action: The server uses the volume for the DUMPDB operation. User Response: None. ANR5330I (S/390) Assigning volume volume ID to LOADDB. Explanation: The server assigns the mounted volume for use as the requested LOADDB volume. System Action: The server uses the volume for the LOADDB operation. User Response: None. ANR5331S (S/390) 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.
416
IBM Tivoli Storage Manager: Messages
ANR5332I (S/390) ANR5350E (S/390)
ANR5332I (S/390) Request number: Assigning volume volume ID to DBBKUP. Explanation: The server assigns the mounted volume for use as the requested DBBKUP volume. System Action: The server uses the volume for the DBBKUP operation. User Response: None. ANR5333I (S/390) Assigning volume volume ID to DBBKUP. Explanation: The server assigns the mounted volume for use as the requested DBBKUP volume. System Action: The server uses the volume for the DBBKUP operation. User Response: None. ANR5334W (S/390) 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 the specified 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. ANR5335E (S/390) 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. System Action: The server dismounts the 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. ANR5336E (S/390) Volume volume ID must be read-only on 3590 device. 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. System Action: The server cancels the current operation. User Response: Update the volume access to READONLY or insure that a device of the type used to create the volume is used to satisfy the mount. ANR5337I (S/390) Assigning volume volume ID to backup set. Explanation: The server has assigned the mounted volume to be used as the requested backup set volume. System Action: The server uses the volume for the backup set operation. User Response: None. ANR5338E (S/390) DEVCLASS device class mounted Device real address, device not capable. Explanation: The server requested a volume with a specific format. The device used to satisfy the mount cannot write using the requested format. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Check the devclass UNIT parameter, and insure the device requested matched the format type defined. ANR5350E (S/390) Error locating block block number on device real address. Explanation: A Locate Block 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
Chapter 3. Common and Platform Specfic Messages
417
ANR5351E (S/390) ANR5358E (S/390)
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. ANR5351E (S/390) 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 (S/390) 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 integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option. ANR5353E (S/390) Load Display failed on device real address. Explanation: A Load Display CCW failed. System Action: Server operation continues. No text is loaded into the display window. User Response: None. ANR5354E (S/390) 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. ANR5357E (S/390) Manual Rewind/Rewind-Unload on device real address. Explanation: The Rewind Unload switch or the Rewind switch on the drive has been pressed. System Action: The server verifies the volume label and attempts to reposition the tape and continue operation. If the volume label verification fails, the server marks the volume in the unavailable state. If the reposition fails, the server marks the volume in the I/O error state. User Response: If the server succeeds in its recovery, no action is required. If recovery is unsuccessful, you can reset the error status of the volume with the UPDATE VOLUME command. Volume integrity may have been compromised. Issue the DELETE VOLUME command with the DISCARD=NO option to try to recover any data. ANR5358E (S/390) Request number: I/O Error at beginning of tape on real address. Explanation: An I/O error has occurred attempting to mount a tape volume; the beginning of the volume cannot be detected. 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. ANR5355E (S/390) Reload cartridge on device real address. Explanation: The cartridge is not inserted correctly, or the tape is not processed correctly. System Action: The task waits until the drive is made ready. An intervention required message is sent to the mount operator user IDs. User Response: Make the drive ready. ANR5356E (S/390) Unload cartridge on device real address. Explanation: The drive cannot maintain tape tension and control tape movement during an unload operation. System Action: The task waits until the drive is made ready. An intervention required message is sent to the mount operator user IDs. User Response: Make the drive ready.
418
IBM Tivoli Storage Manager: Messages
ANR5359E (S/390) ANR5365E (S/390)
ANR5359E (S/390) Request number: Cartridge Length Error on device real address. Explanation: A tape cartridge has been mounted that is too short for processing on the drive. 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. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option. ANR5360E (S/390) Request number: Cartridge Length Incompatible on device real address. Explanation: A tape cartridge has been mounted on a drive and the tape is too long to be processed on the drive or has been initialized to the wrong length. 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. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option. ANR5361E (S/390) Request number: Cartridge Format Incompatible on device real address. Explanation: A tape cartridge has been mounted on a drive, but the tape format cannot be processed on the drive. 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. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option. ANR5362E (S/390) Request number: Cartridge Length Violation on device real address. Explanation: A tape cartridge has been mounted on a drive but the tape is too long to be processed on the drive. 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. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option. ANR5363E (S/390) Request number: Cartridge Compaction Incompatible on device real address. Explanation: A tape cartridge has been mounted on a drive but the tape compression algorithm ID is not compatible with the drive. 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. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option. ANR5364E (S/390) Record sequence error on device real address. Explanation: During processing of a tape volume, the record tape number read does not match that expected by the drive. System Action: The server marks the volume in an I/O error condition. 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. ANR5365E (S/390) Volume fenced on device real address. Explanation: During processing of a tape volume, errors have occurred that caused the tape drive to lose the ability to process the volume. System Action: The server marks the volume in an I/O error condition. User Response: Unload and reload the tape to reset the drive. Reset the error condition with the UPDATE VOLUME command. This failure may be due to a hardware problem. If the problem persists, use the DELETE VOLUME command with the DISCARD=NO option to remove the volume from the storage pool.
Chapter 3. Common and Platform Specfic Messages
419
ANR5366E (S/390) ANR5371E (S/390)
ANR5366E (S/390) Request number: Volume volume ID data set name label dsn in HDR1 label cannot be overwritten with Export data set name export dsn. Explanation: During mount processing of an EXPORT tape volume, the server encountered a nonblank data set name in the HDR1 label. Normally, the server writes the export dsn in this field. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Most tape volume initialization programs only write VOL1 label. If your tape volume initialization program also writes a HDR1 label, the data set name in the HDR1 label must be blank. Be sure that the volume in question is the proper tape volume, and reinitialize it with only a VOL1 label, or with a blank data set name in the HDR1 label. ANR5367I (S/390) Request number: Volume volume ID data set name label dsn in HDR1 label will be overwritten with Export data set name export dsn. Explanation: During mount processing of an EXPORT tape volume, the server encountered a nonblank data set name in the HDR1 label. This data set name will be overwritten with export dsn. System Action: The server continues with mount processing. User Response: None. ANR5368E (S/390) Request number: Volume volume ID data set name label dsn in HDR1 label cannot be overwritten with DUMPDB data set name dumpdb dsn. Explanation: During mount processing of an DUMPDB tape volume, the server encountered a nonblank data set name in the HDR1 label. Normally, the server would write the dumpdb dsn in this field. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Most tape volume initialization programs only write a VOL1 label. If your tape volume initialization program also writes a HDR1 label, the data set name in the HDR1 label must be blank. Be sure the volume in question is the correct tape volume, and reinitialize it with only a VOL1 label, or with a blank data set name in the HDR1 label. ANR5369I (S/390) Request number: Volume volume ID data set name label dsn in HDR1 label will be overwritten with DUMPDB data set name dumpdb dsn. Explanation: During mount processing of an DUMPDB tape volume, the server encountered a nonblank data set name in the HDR1 label. This data set name will be overwritten with dumpdb dsn. System Action: The server continues with mount processing. User Response: None. ANR5370E (S/390) Invalid block header on device real address. Explanation: During a read operation, the block header of the block read does not contain data recognized by the server. System Action: The server may place 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, 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. ANR5371E (S/390) Request number: Volume volume ID data set name label dsn in HDR1 label cannot be overwritten with DBBKUP data set name dbbkup dsn. Explanation: During mount processing of a DBBKUP tape volume, the server encountered a nonblank data set name in the HDR1 label. Normally, the server writes the dbbkup dsn in this field. System Action: The server dismounts the volume, detaches the device, and requests the original volume again. User Response: Most tape volume initialization programs only write VOL1 label. If your tape volume initialization program also writes a HDR1 label, the data set name in the HDR1 label must be blank. Be
420
IBM Tivoli Storage Manager: Messages
ANR5372I (S/390) ANR5411I (S/390)
sure that the volume in question is the proper tape volume, and reinitialize it with only a VOL1 label, or with a blank data set name in the HDR1 label. ANR5372I (S/390) Request number: Volume volume ID data set name label dsn in HDR1 label will be overwritten with DBBKUP data set name dbbkup dsn. Explanation: During mount processing of a DBBKUP tape volume, the server encountered a nonblank data set name in the HDR1 label. This data set name will be overwritten with dbbkup dsn. System Action: The server continues with mount processing. User Response: None. ANR5373I (S/390) 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. 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 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. User Response: None. ANR5404I (S/390) SERVER volume volume name mounted. Explanation: The server has mounted the given volume. System Action: Read or write operations, or both, will commence for the volume. User Response: None. ANR5405I (S/390) End-of-volume reached for SERVER volume volume name. Explanation: The server has detected an end-of-volume condition for the given volume. System Action: The volume is marked full. If more data must be stored, the server accesses another volume. User Response: None. ANR5410I (S/390) FILE volume volume name mounted. Explanation: The server has opened the given file to simulate a tape volume. System Action: Read or write operations, or both, will commence for the volume. User Response: None. ANR5411I (S/390) End-of-volume reached for FILE volume volume name. Explanation: The server has detected an end-of-volume condition for the given volume. System Action: The volume is marked full. If more data must be stored, the server accesses another volume. User Response: None. ANR5374I (S/390) Tape volume volume ID on real address real address has had an unsolicited interrupt, and may have been dismounted. Explanation: An unsolicited interrupt is received for the drive where the volume is mounted. The drive is not ready or its state cannot be determined, so the tape may have been dismounted. System Action: If the server can recover without possibility of data loss, it will reverify the label and continue operations. If the label is not verified or data loss is possible with continued use, the next operation will fail and the tape will be dismounted. User Response: Check the tape drive.
Chapter 3. Common and Platform Specfic Messages
421
ANR5412I (S/390) ANR5418E (S/390)
ANR5412I (S/390) 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 (S/390) 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. System Action: Server operation continues. 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 (S/390) 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. Error codes greater than eight are MVS ABEND codes, documented in MVS/ESA System Codes, GC28-1486. System Action: Server operation continues. 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. ANR5415W (S/390) SFS CSL call CSL name failed with return code rc, reason code rs. optional (file or directory being processed) Explanation: A call to an SFS CSL routine failed. System Action: See following server messages. User Response: Check the return and reason codes in the System Messages and Codes manual, Callable Services Library (CSL) Reason Codes section, for information on the problem and on the action needed to correct it. ANR5416E (S/390) Minidisk device class cannot be used with SFS file file name. Explanation: A device class of DEVTYPE=FILE is defined with FILEMODE= where the file mode letter is associated with an SFS directory. Device classes defined with DEVTYPE=FILE and FILEMODE= parameters can only be associated with an accessed minidisk (CMS file mode letter A-Z). System Action: File is not used. User Response: When using a minidisk, define the DEVTYPE=FILE device class with the FILEMODE= parameter. When using an SFS directory, use the DIRECTORY= parameter. ANR5417E (S/390) File file name already exists, it cannot be created. Explanation: The server attempted to create a new file using file name but received indication that the file already exists. The server will create a new file after it determines that the file named file name is not in its database. The server will append to an existing file with the name file name only if it exists in its database. The server will not overwrite an existing file. System Action: File is not used. User Response: The file named file name must either be renamed or erased. ANR5418E (S/390) File file name cannot be used. Explanation: The server found that the file file name exists in its database, but either was accessed as read-only or the file did not exist on the minidisk identified by the file mode letter or the file did not exist in the SFS directory. System Action: File is not used. User Response: Make sure the minidisk is accessed with the file mode letter specified for the device class defined with DEVTYPE=FILE FILEMODE=?. If the file is in an SFS directory, make sure the SFS directory still exists and the server user ID has been granted read/write authority to the directory and to the file named command. If the volume status is read/write and
422
IBM Tivoli Storage Manager: Messages
ANR5419E (S/390) ANR5455E (S/390)
the volume is not full, write access is required. If the file does not exist, the server cannot use the volume. Storage volumes should be deleted using the DELETE VOLUME command with DISCARDDATA=YES. Volumes for IMPORT, LOAD or RESTORE DB cannot be used. ANR5419E (S/390) Filemode or directory filemode or directory name cannot be used. Explanation: The server determined that a minidisk with the file mode letter filemode or that the SFS directory directory name were not available for use. System Action: Server operation continues but file is not used. User Response: Ensure that a minidisk is accessed with the file mode letter filemode or that an SFS directory directory directory exists and that the server user ID has been granted read/write authority to the directory and all files in that directory. ANR5420W (S/390) 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. ANR5450E (S/390) Error opening filespec. Explanation: An error occurred while attempting an open operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the open operation failed. Correct the problem and restart the process. ANR5451E (S/390) An error (error code) occurred during a write operation. Explanation: An error occurred while attempting a write operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the write operation failed. Correct the problem and restart the process. ANR5452E (S/390) An error (error code) occurred during a read operation. Explanation: An error occurred while attempting a read operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the read operation failed. Correct the problem and restart the process. ANR5453E (S/390) 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 (S/390) Device type volume volume name cannot be overwritten by DUMPDB operation. Explanation: The specified volume already exists or contains data. The server does not allow new dump 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 dump operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the dump operation. ANR5455E (S/390) Device type volume volume name cannot be overwritten by BACKUP DB operation. Explanation: The specified volume already exists or contains data. The server does not allow new backup 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 backup operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the backup operation.
Chapter 3. Common and Platform Specfic Messages
423
ANR5456E (S/390) ANR5505E (S/390)
ANR5456E (S/390) Device type volume volume name cannot be overwritten by backup set operation. Explanation: The specified volume already exists or contains data. The server does not allow new backup set 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 backup set operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the backup set operation. ANR5499E (S/390) Command: Required parameter was not specified parameter. Explanation: The command command has been issued, but without a required parameter. If two parameters are listed, the command requires at least one of the parameters. System Action: Server operation continues. User Response: Reissue the command and specify the missing parameter and any additional parameters that are required for the command. The HELP DEFINE or HELP UPDATE commands may be used to obtain syntax assistance. ANR5500E (S/390) Command: Device type not specified. Explanation: The command command has been issued, but without the DEVTYPE keyword. System Action: Server operation continues. 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 (S/390) Command: attribute is invalid for device type. Explanation: The command command has been issued with an incompatible combination of device type and attribute. System Action: Server operation continues. User Response: Reissue the command, and specify a compatible set of attributes. The HELP DEFINE or HELP UPDATE commands may be used to obtain syntax assistance. ANR5502E (S/390) Command: LENGTH is invalid with 3480 and 3480XF formats. Explanation: The command command has been issued with an incompatible combination of device type, FORMAT, and LENGTH. A length specification is invalid with 3480 and 3480XF formats. System Action: Server operation continues. User Response: Reissue the command, and specify a 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. ANR5503E (S/390) Command: Invalid parameter for update - parameter. Explanation: The command command has been issued. However, the parameter is not an attribute that must be updated. System Action: Server operation continues. User Response: Reissue the command, and specify a compatible set of attributes. The HELP UPDATE command may be used to obtain syntax assistance. ANR5504E (S/390) Command: new attribute conflicts with existing old attribute. Explanation: The command command has been issued. However, new attribute conflicts with old attribute in updating the device class. System Action: Server operation continues. User Response: Reissue the command, and specify a 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. ANR5505E (S/390) Command: MOUNTLIMIT is less than current number of mounted volumes. Explanation: The command command has been issued that specifies a MOUNTLIMIT smaller than the existing number of volumes that are already allocated. System Action: Server operation continues. 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.
424
IBM Tivoli Storage Manager: Messages
ANR5506E (S/390) ANR5517E (S/390)
ANR5506E (S/390) Command: Conflicting parameters parm1 and parm2. Explanation: The command command has been issued that specifies conflicting parameters parm1 and parm2. Conflicting parameters include specifying FORMAT and LENGTH with DENSITY, and RETENTION with EXPIRATION. System Action: Server operation continues. User Response: Reissue the command, and specify a compatible set of parameters. The HELP DEFINE or HELP UPDATE commands may be used to obtain syntax assistance. ANR5507E (S/390) Command: Device type devtype not supported on this platform. Explanation: An unsupported device type has been specified for command. In MVS, for example, the REEL device type is not supported. System Action: Server operation continues. User Response: Specify a valid device type for the platform. The HELP DEFINE command may be used to obtain syntax assistance. ANR5508E (S/390) Device class device class not defined in device configuration file. Explanation: The issued command requires that the specified device class be defined in the device configuration file. The definition was not found. System Action: The command is not processed. User Response: Reissue the command, and specify a valid device class. You may also want to refresh your device configuration file by issuing the BACKUP DEVCONFIG command. ANR5509E (S/390) 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. System Action: The command is not processed. User Response: Reissue the command, and specify a parameter less than or equal to the allowed maximum. ANR5510E (S/390) Data set name dsn is not valid. Explanation: Data set name dsn is not valid. System Action: Server operation continues. User Response: Reissue the server command, and specify a valid data set name. ANR5517E (S/390) Command: Library library name is already defined. Explanation: The designated library cannot be defined because it already exists. System Action: The command is not processed. User Response: If you want to define an additional
Chapter 3. Common and Platform Specfic Messages
ANR5511E (S/390) Unit name unit is not valid. Explanation: Unit name unit is not valid. System Action: Server operation continues. User Response: Reissue the server command, and specify a valid unit name. ANR5512E (S/390) Volume serial volser is not valid. Explanation: Volume serial volser is not valid. System Action: Server operation continues. User Response: Reissue the server command, and specify a valid volume serial. ANR5513E (S/390) Expiration date expdt is not valid. Explanation: Expiration data expdt is not valid. System Action: Server operation continues. User Response: Reissue the server command, and specify a valid expiration date. ANR5514E (S/390) Retention period retpd is not valid. Explanation: Retention period retpd is not valid. System Action: Server operation continues. User Response: Reissue the server command, and specify a valid retention period. ANR5515I (S/390) Library library name defined. Explanation: The designated library has been successfully defined. System Action: The library is defined and recorded in the database. User Response: None. ANR5516E (S/390) 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. System Action: The command is not processed. User Response: Reissue the command using a valid library name.
425
ANR5518E (S/390) ANR5959E (S/390)
library, reissue the command with a different library name. ANR5518E (S/390) Command: Incorrect value for parameter parameter. Explanation: An incorrect value has been provided for the specified parameter. System Action: The command is not processed. User Response: Reissue the command, and specify a valid parameter value. ANR5519I (S/390) 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 library, reissue the command with a different library name. ANR5520I (S/390) Library library name deleted. Explanation: The designated library has been successfully deleted. System Action: The library is deleted and removed from the database. User Response: None. ANR5953W (S/390) 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. System Action: Server operation continues. No 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 (S/390) 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. System Action: Server operation continues. No accounting record is generated. User Response: Allocate additional storage to the server virtual machine. There are three ways to do this: 1. Increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. 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. ANR5956E (S/390) C library not available, unable to continue. Explanation: The C/370 or LE/370 library is not available. System Action: Server operation ends. User Response: Make the C/370 or LE/370 library available to the server. ANR5957W (S/390) C library is at level level. Explanation: The C run-time library is at a lower level (level) than expected. System Action: Server attempts to continue operation. User Response: Ensure that the proper level of the C/370 or LE/370 library is installed and available to the server. ANR5958E (S/390) SVM is at level level, the server requires at least required-level, unable to continue. Explanation: The SVM run-time library is at level level, but the server requires at least level required-level. System Action: Server operation ends. User Response: Check the required PTFs for the server. Ensure that the proper level of SVM is installed. ANR5959E (S/390) Server not running APF authorized. The server and all JOBLIB/STEPLIB libraries (C library and other libraries) must be authorized. Explanation: The server is not running with MVS authorization.
426
IBM Tivoli Storage Manager: Messages
ANR5960E (S/390) ANR5980E (S/390)
System Action: Server operation ends. User Response: Ensure that all library data sets required by the server are authorized. ANR5960E (S/390) Unable to initialize kernel virtual machine requires ECMODE capability. Explanation: The CP directory entry for the server does not contain an OPTION ECMODE statement. System Action: Server operation ends. User Response: Add an OPTION ECMODE statement to the CP directory entry for the server. ANR5961E (S/390) Insufficient memory for server initialization. Explanation: The server program cannot allocate enough memory (virtual storage) to fully initialize itself. System Action: Server initialization fails. The server is not started. User Response: Allocate additional storage to the server virtual machine or reduce the storage required by the server. There are three ways to do this: 1. Increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. For MVS, increase the region size; 40M is the recommended minimum size for the server but larger servers require more. 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. ANR5962I (S/390) DSMSERV generated at time on date. Explanation: The server module has been generated at the indicated date and time. System Action: Server operation continues. User Response: None. ANR5963I (S/390) Server termination complete. Explanation: The server has completed shut down. System Action: Server operation ends. User Response: None. ANR5964E (S/390) Server unable to mark itself non-swappable. Return code rc from SYSEVENT TRANSWAP. Explanation: The server cannot issue a SYSEVENT TRANSWAP macro. System Action: Server operation ends. User Response: Contact your service representative. ANR5965I (S/390) Console command: command Explanation: A server command command has been received from an MVS operator console. System Action: Server operation continues. User Response: None. ANR5967W (S/390) Accounting record not produced, return code rc. Explanation: There was a problem generating the accounting record. System Action: Server operation continues. User Response: Contact your service representative. ANR5980E (S/390) Unable to initialize PDM driver insufficient memory. Explanation: The servers PDM communications driver is unable to initialize itself due to insufficient memory (virtual storage). System Action: Server initialization fails. User Response: Allocate additional storage to the server virtual machine. There are three ways to do this: 1. Increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server. 2. Reduce the maximum number of client sessions permitted. To do this, edit the server options 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 server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4KB of memory to be allocated.
Chapter 3. Common and Platform Specfic Messages
427
ANR5981I (S/390) ANR6203I
Note that the server must be shut down (with the HALT command) before changes can be made to the server options file. ANR5981I (S/390) InfoSpeed/PDM communication enabled on port port number. Explanation: The servers PDM communications driver is ready to receive connection requests from clients. System Action: Server operation continues. User Response: None. ANR5982E (S/390) InfoSpeed accept error rc = rc on port port number. Explanation: The servers InfoSpeed communications driver has received an error from the ACCEPT function. System Action: Server operation continues and InfoSpeed communications will be retried. User Response: None. ANR6201I ANR5983I (S/390) Unable to use SCRATCH volumes for LAN-free storage operation. Explanation: The z/OS server prohibits SCRATCH volume selection for LAN-free activity. For a volume selection to satisfy a LAN-Free request, it must be written to by the Tivoli Storage Manager z/OS version 5.2 server at least once. After this occurs, the volume becomes eligible for LAN-Free operations. System Action: Session ends. User Response: It is necessary to define volumes destined for LAN-Free storage requests. Allowing the z/OS server to allocate a SCRATCH volume when populating a LAN-Free storage pool will render the volume ineligible for LAN-Free selection. The administrator should maintain a storage pool of empty or filling volumes in order to satisfy LAN-Free requests. ANR5984E (S/390) 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. System Action: The command is not processed. User Response: Delete all paths to this library, and reissue the command. Command name: Level compression audit level compression audit starting as background process process ID. ANR6200I Command name: Level compression audit level compression audit started as process process ID. ANR5985E (S/390) Command: Library library name is not defined. Explanation: The designated library has not been defined. System Action: The command is not processed. User Response: Reissue the command using a different library name, or define the library before retrying the command.
Explanation: A compression audit at the specified level has been started as a background server process with the process identifier reported. System Action: Server operation continues. The background audit attempts to identify client files that may be affected by the client compression problem. User Response: None.
Explanation: A compression audit at the specified level was started as a background server process having the process identifier reported. System Action: Server operation continues. The background audit attempts to identify client files that may be affected by the client compression problem. User Response: None. ANR6202I Command name: Verifying candidates from last audit.
Explanation: A compression audit has started to verify the client file candidates that were identified in a previous compression audit execution. The verification process eliminates compression candidates that are now found to be expired by policy on the server. System Action: The audit operation continues. User Response: None. 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, subject to the qualifications that were specified for the command. System Action: The audit operation continues.
428
IBM Tivoli Storage Manager: Messages
ANR6204I ANR6210I
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. message is issued whenever a candidate file is detected during a compression audit that was started with the VERBOSE=YES parameter specified. System Action: The audit operation continues. User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation. 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 ended and is reporting the total number of suspect client files that have been found. System Action: The audit operation completes. User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. 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 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 Command name: Process process ID, level audit level audit completed successfully number of candidate files candidate files were found in number of files examined files examined.
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. System Action: The audit operation continues. User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation. ANR6206I Command name: Process process ID, starting base level 1 compression audit.
Explanation: A compression audit operation completed successfully. The number of candidate files that were found are displayed. System Action: The audit operation ends. User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. ANR6210I Command name: Process process ID, level audit level audit completed successfully number of candidate files candidate files were found.
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 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. ANR6207I Command name: Process process ID, level 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 operation completed successfully. The number of candidate files that have been found are displayed. System Action: The audit operation ends. User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command.
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
Chapter 3. Common and Platform Specfic Messages
429
ANR6211I ANR6221I
ANR6211I Command name: Process process ID, level audit level analysis detected candidate file object name in file space client filespace name for node client node name. ANR6214I Command name: Process process ID, 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.
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. System Action: The audit operation continues. User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation. ANR6212I Command name: Process process ID, level 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 operation completed successfully. The number of candidate files that were promoted as candidates at this level of audit, eliminated as candidates at this level of audit, and found to be expired are reported. System Action: The audit operation ends. User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. 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: 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 VERBOSE=YES parameter specified. System Action: The audit operation continues. User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation. 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: 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. System Action: Server operation continues. User Response: None. ANR6221I Force backup operation started as process process ID.
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. System Action: The audit operation ends. User Response: The compression audit can be restarted with the AUDIT COMPRESSION command. The compression candidate list can be displayed with the QUERY COMPRESSION command.
Explanation: A force backup operation was started as a background server process with the indicated identifier. System Action: Server operation continues. User Response: None.
430
IBM Tivoli Storage Manager: Messages
ANR6222I ANR6300E
ANR6222I Command name: Process process ID was cancelled - number of files files were processed prior to cancellation. operation. The QUERY PROCESS command may be used to query the status of the operation. ANR6227I cleanup process name operation starting as process process ID.
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: 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. System Action: Server operation continues. User Response: The CANCEL PROCESS command can be used to cancel the compression cleanup operation. The QUERY PROCESS command may be used to query the status of the operation. ANR6228W Cleanup process name: Process process ID has been cancelled - cleanup processing is incomplete.
Explanation: The indicated process has completed processing. All database references have been deleted for the indicated number of files. System Action: The process ends. User Response: None. ANR6224I Force backup process process ID has completed - number of files files were marked for forced backup.
Explanation: A compression cleanup operation has been cancelled prior to successful completion. System Action: Server operation continues. User Response: The CLEANUP COMPRESSION command can be used to restart the cleanup operation. ANR6229I Cleanup process name: Process process ID completed successfully.
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. System Action: The process ends. User Response: None. ANR6225I File identifier removed as a suspect for compression errors.
Explanation: A compression cleanup operation has successfully completed. System Action: The cleanup process ends. User Response: None. ANR6300E Command name: Insufficient server memory available for the operation.
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: Server operation continues. User Response: None. ANR6226I Command name: Started as background process process ID.
Explanation: A compression testing routine cannot continue because sufficient memory is not available on the server. System Action: The operation fails. 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.
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. System Action: Server operation continues. User Response: The CANCEL PROCESS command can be used to cancel the compression cleanup
Chapter 3. Common and Platform Specfic Messages
431
ANR6301E ANR6601E
ANR6301E Command name: Invalid LEVEL specified. This command only supports a value of 1 or 2 for the LEVEL parameter. ANR6304E Command name: Command cannot be processed until compression audit is performed.
Explanation: An invalid LEVEL= parameter has been specified for the command. System Action: The command fails. User Response: Reissue the command specifying a 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: The indicated command cannot be processed until a compression audit is performed using the AUDIT COMPRESSION command. System Action: The command fails. 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: A compression audit operation failed before completion. The number of candidate files that were found prior to the failure are displayed. System Action: The audit operation ends. 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: 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. System Action: Server operation continues. User Response: Use the QUERY COMPRESSION command to obtain the correct identifier for the file to be removed. ANR6306E Cleanup process name: Process process ID failed due to server error - cleanup processing is incomplete.
Explanation: A compression cleanup operation has 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 service representative. ANR6600E Command: Invalid machine name machine name.
Explanation: A compression audit operation failed 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 audit failure are reported. System Action: The audit operation ends. 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.
Explanation: The machine name specified in the command is invalid. System Action: The server does not process the command. User Response: Issue the command again and specify 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. System Action: The server does not process the command.
432
IBM Tivoli Storage Manager: Messages
ANR6602E ANR6611E
User Response: Issue the command again and specify a valid description. ANR6602E Command: Recovery instructions file name exceeds maximum length characters. ANR6607E Command: Machine machine name is already defined.
Explanation: The machine specified in the command is already defined to the server. System Action: The server does not process the command. User Response: Issue the command again and specify another machine. ANR6608E Command: A machine containing a server is already defined.
Explanation: The recovery instructions file name specified in the command exceeds the maximum length of allowable characters. System Action: The server does not process the command. User Response: Issue the command again and specify a valid recovery instructions file name. ANR6603E Command: Characteristics file name exceeds maximum length characters.
Explanation: The characteristics file name specified in the command exceeds the maximum length of allowable characters. System Action: The server does not process the command. User Response: Issue the command again and specify a valid characteristics file name. ANR6604E Command: Invalid building identifier building.
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. System Action: The server does not process the 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. System Action: None. User Response: None. ANR6610E Command: Invalid recovery media name recovery media name.
Explanation: The building identifier specified in the command is invalid. System Action: The server does not process the command. User Response: Issue the command again and specify a valid building identifier. ANR6605E Command: Invalid floor identifier - floor.
Explanation: The recovery media name specified in the command is invalid. System Action: The server does not process the command. User Response: Issue the command again and specify a valid recovery media name. ANR6611E Command: Location information exceeds maximum length characters.
Explanation: The floor identifier specified in the command is invalid. System Action: The server does not process the command. User Response: Issue the command again and specify a valid floor identifier. ANR6606E Command: Invalid room identifier - room.
Explanation: The location specified in the command exceeds the maximum length of allowable characters. System Action: The server does not process the command. User Response: Issue the command again and specify a valid location.
Explanation: The room identifier specified in the command is invalid. System Action: The server does not process the command. User Response: Issue the command again and specify a valid room identifier.
Chapter 3. Common and Platform Specfic Messages
433
ANR6612I ANR6622E
ANR6612I Machine machine name updated. User Response: Issue the command again and specify a valid registered node. ANR6618E Command: No matching node registered.
Explanation: An UPDATE MACHINE command has updated one or more attributes of a machine. System Action: None. User Response: None. ANR6613I Machine machine name deleted.
Explanation: The node specified in the command does not match any node registered to the server. System Action: The server does not process the command. User Response: Issue the command again and specify a valid node. ANR6619I Node node name associated with machine machine name.
Explanation: A DELETE MACHINE command has deleted the requested machine from the server. System Action: None. User Response: None. ANR6614E Command: Machine machine name is not defined.
Explanation: The machine specified in the command is not defined to the server. System Action: The server does not process the command. User Response: Issue the command again and specify a valid machine. ANR6615E Command: Failed to open input file - file 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. System Action: None. User Response: None. ANR6620E Command: Machine and node association is already defined.
Explanation: The machine and node association specified in the command is already defined to the server. System Action: The server operation continues, but the command has no effect. User Response: Issue the command again and specify a valid node. ANR6621I Node node name disassociated from machine machine name.
Explanation: The input file specified in the command cannot be opened by the server. System Action: The server does not process the command. User Response: Issue the command again and specify 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. System Action: The server does not process the command. User Response: Issue the command again and specify a valid sequence number. ANR6617W Command: Node node name cannot be processed because it is not registered.
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. System Action: None. User Response: None. ANR6622E Command: Recovery media recovery media name is not defined.
Explanation: The recovery media specified in the command is not defined to the server. System Action: The server does not process the command. User Response: Issue the command again and specify a valid recovery media.
Explanation: The node indicated in the message cannot be processed because it is not registered. System Action: The indicated node is not processed, but another node can be processed if specified by this command.
434
IBM Tivoli Storage Manager: Messages
ANR6623W ANR6632I
ANR6623W Command: Machine machine name cannot be processed because it is not defined. ANR6628E Command: Volume list exceeds maximum length characters.
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. User Response: Issue the command again and specify a valid machine. ANR6624E Command: No matching machine defined.
Explanation: The volume list specified in the command exceeds the maximum length of allowable characters. System Action: The server does not process the command. User Response: Issue the command again and specify a valid volume list. ANR6629E Command: Product name exceeds maximum length characters.
Explanation: The machine specified in the command does not match any machine defined to the server. System Action: The server does not process the command. User Response: Issue the command again and specify a valid machine. ANR6625I Machine machine name associated with recovery media recovery media name.
Explanation: The product name specified in the command exceeds the maximum length of allowable characters. System Action: The server does not process the command. User Response: Issue the command again and specify a valid product name. ANR6630E Command: Product information exceeds maximum length characters.
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. System Action: None. User Response: None. ANR6626E Command: Recovery media/machine association is already defined.
Explanation: The product information specified in the command exceeds the maximum length of allowable characters. System Action: The server does not process the command. User Response: Issue the command again and specify 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. System Action: The server operation continues, but the command has no effect. User Response: Issue the command again and specify a valid machine. ANR6627I Machine machine name disassociated from recovery media recovery media name.
Explanation: Boot recovery media cannot be defined to the server without specifying a volume list. System Action: The server does not process the command. User Response: Issue the command again and specify the volume list for the boot recovery media. ANR6632I Recovery media recovery media name defined.
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. System Action: None. User Response: None.
Explanation: A DEFINE RECOVERYMEDIA command has defined the recovery media to the server. System Action: None. User Response: None.
Chapter 3. Common and Platform Specfic Messages
435
ANR6633I ANR6641E
ANR6633I Recovery media recovery media name updated. ANR6638E Command: The characteristics for machine machine name are already defined.
Explanation: An UPDATE RECOVERYMEDIA command has updated one or more attributes of the recovery media. System Action: None. User Response: None. ANR6634I Recovery media recovery media name deleted.
Explanation: The characteristics for the machine specified in the command are already defined to the server. System Action: The server does not process the command. User Response: If the specified machine is defined to the server, issue an UPDATE MACHINE command to update the existing characteristics. If the machine is not defined to the server, run AUDIT DRM FIX to delete the characteristics. ANR6639E Command: The recovery instructions for machine machine name are already defined.
Explanation: A DELETE RECOVERYMEDIA command has deleted the requested recovery media from the server. System Action: None. User Response: None. ANR6635E Command: Recovery media recovery media name is already defined.
Explanation: The recovery instructions for the machine specified in the command are already defined to the server. System Action: The server does not process the 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. ANR6640E Command: Cannot delete volume list for boot recovery media.
Explanation: The recovery media specified in the command is already defined to the server. System Action: The server does not process the command. User Response: Issue the command again and specify a different recovery media. ANR6636E Command: The characteristics specified for machine machine name exceeds maximum length characters.
Explanation: The characteristics specified in the command exceeds the maximum length of allowable characters. System Action: The server does not process the command. User Response: Issue the command again and specify valid characteristics. ANR6637E Command: The recovery instructions specified for machine machine name exceeds maximum length 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. System Action: The server does not process the command. User Response: To delete the volume list, issue an UPDATE RECOVERYMEDIA command and specify a recovery media type of OTHER and VOLUMES=. To change the recovery media type to BOOT, issue an UPDATE RECOVERYMEDIA command and specify the volume list containing the boot recovery media and TYPE=BOOT. ANR6641E Command: No association found for machine and node pair specified.
Explanation: The recovery instructions specified in the command exceeds the maximum length of allowable characters. System Action: The server does not process the command. User Response: Issue the command again and specify valid recovery instructions.
Explanation: No association found for the machine and node pair specified in the command. System Action: Server operation continues, but the command has no effect. User Response: Issue the command again and specify a valid machine and node pair.
436
IBM Tivoli Storage Manager: Messages
ANR6642E ANR6651I
ANR6642E Command: No association found for recovery media and machine pair specified. ANR6647E Audit command: DRM global attributes are missing.
Explanation: No association found for the recovery media and machine pair specified in the command. System Action: Server operation continues, but the command has no effect. User Response: Issue the command again and specify a valid recovery media and machine pair. ANR6643E Command: Invalid parameter value parameter value.
Explanation: A database audit process finds that the global attributes used for server DRM activities are missing. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to recreate the DRM global attributes. ANR6648I Audit command: DRM global attributes are missing - default values will be used to recreate the attributes.
Explanation: The parameter issued in the command is invalid. System Action: The server does not process the command. User Response: Issue the command again and specify a valid parameter. ANR6644E Command: A character string must be specified.
Explanation: A database audit process finds that the 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. System Action: Audit processing continues. User Response: None. ANR6649E Audit command: DRM machine ID assignments are incorrect.
Explanation: The INSERT command is invalid. A character string must be specified. System Action: The server does not process the command. User Response: Issue the command again and specify a valid character string. ANR6645W Node node name has already been associated with machine machine name.
Explanation: A database audit process finds that the global attributes machine ID used for server DRM activities are incorrect. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES specified so that the DRM global attributes can be corrected. ANR6650I Audit command: DRM machine ID Assignments are incorrect - values will be corrected.
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. System Action: The indicated node is not processed, but another node can be processed if specified by the command. User Response: Issue the command again and specify a valid node name. ANR6646I Audit command: Auditing disaster recovery manager definitions.
Explanation: A database audit process finds that the global attributes machine ID used for server DRM activities are incorrect. Since FIX=YES has been specified on the AUDIT command, the attribute value will be corrected in the server database. System Action: Audit processing continues. User Response: None ANR6651I Audit command: Invalid priority value encountered for machine machine name.
Explanation: This message is displayed during a database audit and indicates that the disaster recovery manager definitions are being examined by the database audit process. System Action: Audit processing continues. User Response: None.
Explanation: A database audit process encounters an invalid priority value for the machine indicated. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the priority. Or, issue an UPDATE MACHINE command and specify a new priority value.
Chapter 3. Common and Platform Specfic Messages
437
ANR6652I ANR6660I
ANR6652I Audit command: Invalid priority value encountered for machine machine name the default value will be set. FIX=YES has been specified, the audit function removes the machine floor value. System Action: Audit processing continues. User Response: To set the floor value to another value, issue an UPDATE MACHINE command after the audit command has completed. ANR6657I Audit command: Invalid room value encountered for machine machine name.
Explanation: A database audit process encounters an invalid machine priority value for the machine indicated. Because FIX=YES has been specified, the audit function sets the machine priority value to the default value. System Action: Audit processing continues. User Response: To override the default value, issue an UPDATE MACHINE command to change the value after the audit command has completed. ANR6653I Audit command: Invalid building value encountered for machine machine name.
Explanation: A database audit process encounters an invalid room value for the machine indicated. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the room value. Or, issue an UPDATE MACHINE command and specify a new room value. ANR6658I Audit command: Invalid room value encountered for machine machine name the room value will be removed.
Explanation: A database audit process encounters an invalid building value for the machine indicated. System Action: Audit processing continues. User Response: Issue the command again and specify 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.
Explanation: A database audit process encounters an invalid room value for the machine indicated. Because FIX=YES has been specified, the audit function removes the machine room value. System Action: Audit processing continues. User Response: To set the room value for the specified machine to another value, use the UPDATE MACHINE command after the audit command has completed. ANR6659I Audit command: Invalid server value encountered for machine machine name.
Explanation: A database audit process encounters an invalid building value for the machine indicated. Because FIX=YES has been specified, the audit function removes the machine building value. System Action: Audit processing continues. User Response: To set the building value to another value, issue an UPDATE MACHINE command after the audit command has completed. ANR6655I Audit command: Invalid floor value encountered for machine machine name.
Explanation: A database audit process encounters an invalid server value for the machine indicated. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the server value. Or, issue an UPDATE MACHINE command and specify a new server value. ANR6660I Audit command: Invalid server value encountered for machine machine name the default value will be set.
Explanation: A database audit process encounters an invalid floor value for the machine indicated. System Action: Audit processing continues. User Response: Issue the command again and specify 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.
Explanation: A database audit process encounters an invalid server value for the machine indicated. Because FIX=YES has been specified, the audit function sets the machine server value to the default value. System Action: Audit processing continues. User Response: To override the default value, issue an UPDATE MACHINE command to change the value after the audit command has completed.
Explanation: A database audit process encounters an invalid floor value for the machine indicated. Because
438
IBM Tivoli Storage Manager: Messages
ANR6661I ANR6668E
ANR6661I Audit command: Multiple machines are indicated as servers. Only one machine should have the server indicator set to YES. ANR6665I Audit command: Invalid access value encountered for recovery media recovery media name - the default value will be set.
Explanation: A database audit process encounters more than one machine with the server indicator set to YES. System Action: Audit processing continues. 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.
Explanation: A database audit process encounters an invalid access value for the recovery media indicated. Because FIX=YES has been specified, the audit function sets the recovery media access value to the default value. System Action: Audit processing continues. User Response: To override the default value, issue an 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.
Explanation: A database audit process finds a characteristics reference from a machine for characteristics that are not in the server database. System Action: Audit processing continues. User Response: Issue an UPDATE MACHINE command to load the characteristics into the database after the audit command has completed. ANR6663I Audit command: Recovery instructions for machine machine name not found.
Explanation: A database audit process encounters an invalid type value for the recovery media indicated. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the type value. Or, issue an UPDATE RECOVERYMEDIA command and specify a new type value. ANR6667I Audit command: Invalid type value encountered for recovery media recovery media name - the default value will be set.
Explanation: A database audit process finds a recovery instructions reference from a machine for recovery instructions that are not in the server database. System Action: Audit processing continues. User Response: Issue an UPDATE MACHINE command to load the recovery instructions into the database after the audit command has completed. ANR6664I Audit command: Invalid access value encountered for recovery media recovery media name.
Explanation: A database audit process encounters an invalid type value for the recovery media indicated. Because FIX=YES has been specified, the audit function sets the recovery media type value to the default value. System Action: Audit processing continues. User Response: To override the default value, issue an UPDATE RECOVERYMEDIA command to change the value after the audit command has completed. ANR6668E Audit command: Machine is not found for internal machine ID machine ID, which is referenced by recovery media.
Explanation: A database audit process encounters an invalid access value for the recovery media indicated. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the access value. Or, issue an UPDATE RECOVERYMEDIA command and specify a new access value.
Explanation: A database audit process finds recovery media that references a machine that is not defined in the server database. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct recovery media attributes.
Chapter 3. Common and Platform Specfic Messages
439
ANR6669I ANR6677I
ANR6669I Audit command: Machine is not found for internal machine ID machine ID, which is referenced by recovery media - the machine reference will be deleted. ANR6673I Audit command: Client node not found for internal node ID node ID, which is referenced by a machine - the client node reference will be deleted.
Explanation: A database audit process finds recovery 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. System Action: Audit processing continues. User Response: None. 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 a client node 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. System Action: Audit processing continues. User Response: None. ANR6674E Audit command: Machine not found for internal machine ID machine ID, which is referenced by a client node.
Explanation: A database audit process finds a machine that references recovery media that is not defined in the server database. System Action: Audit processing continues. User Response: Issue the command again and specify 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 reference will be deleted.
Explanation: A database audit process finds a client node that references a machine that is not defined in the server database. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the machine attributes. ANR6675I Audit command: Machine not found for internal machine ID machine ID, which is referenced by a client node - the machine reference will be deleted.
Explanation: A database audit process finds m machine that references recovery media that is not defined in the server database. Because FIX=YES has been specified for the audit command, the reference will be deleted from the server database. System Action: Audit processing continues. User Response: None. ANR6672E Audit command: Client node not found for internal node ID node ID, which is referenced by a machine.
Explanation: A database audit process finds a client node 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. System Action: Audit processing continues. User Response: None. ANR6676E Audit command: Machine not found for internal machine ID machine ID, which is referenced by characteristics.
Explanation: A database audit process finds a machine that references a client node that is not defined in the server database. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the machine attributes.
Explanation: A database audit process finds characteristics that reference a machine that is not defined in the server database. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the machine attributes. ANR6677I Audit command: Machine not found for internal machine ID machine ID, which is referenced by characteristics - the machine reference will be deleted.
Explanation: A database audit process finds characteristics that reference a machine that is not defined in the server database. Because FIX=YES has
440
IBM Tivoli Storage Manager: Messages
ANR6678E ANR6686E
been specified for the audit command, the reference will be removed from the server database. System Action: Audit processing continues. User Response: None. ANR6678E Audit command: Machine not found for internal machine ID machine ID, which is referenced by recovery instructions. 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. User Response: None. ANR6683I Command: Volume volume name was moved from from state state to to state.
Explanation: A database audit process finds recovery instructions that reference a machine that is not defined in the server database. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the machine attributes. ANR6679I Audit command: Machine not found for internal machine ID machine ID, which is referenced by recovery instructions the machine reference will be deleted.
Explanation: Volume volume name is successfully moved from state1 to state2 by the indicated command. System Action: The indicated volume is moved to the destination state. User Response: None. ANR6684I Command: Volume volume name was deleted.
Explanation: A database audit process finds recovery instructions that reference a machine that is not defined in the server database. Because FIX=YES has been specified for the audit command, the reference will be removed from the server database. System Action: Audit processing continues. User Response: None. ANR6680E Audit command: Missing or invalid internal database attribute encountered for machine machine name.
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 Command: Volume volume name not defined.
Explanation: A database audit process finds an invalid attribute for the specified machine. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the machine attributes. ANR6681I Audit command: Missing or invalid internal database attribute encountered for machine machine name - the attribute will be corrected.
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. User Response: Reissue the command specifying a valid volume name. ANR6686E Command: Volume volume name in use.
Explanation: A database audit process finds an invalid attribute for the specified machine. Because FIX=YES has been specified for the audit command the invalid attribute will be corrected. System Action: Audit processing continues. User Response: None.
Explanation: The MOVE DRMEDIA * WHERESTATE=MOUNTABLE command displays the message. Volume volume name is used for another operation. System Action: The command is not processed if the volume is explicitly specified on the command. If a
Chapter 3. Common and Platform Specfic Messages
441
ANR6687E ANR6697I
volume pattern is specified on the command, the indicated volume is not processed, but the other volumes are processed. User Response: Wait until the conflicting volume activity has completed, and then reissue the command. If the volume is currently mounted, but idle, dismount the volume by using a DISMOUNT VOLUME command and then retry this operation. ANR6687E Command: Executable command string exceeds maximum length characters. 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. System Action: The server does not process the command. User Response: Reissue the command specifying COURIER or COURIERRETRIEVE as the state for a volume that has access mode of OFFSITE. ANR6695E Command: Device class device class name not defined for volume volume name.
Explanation: The length of the executable command string specified with the CMD parameter exceeds the maximum length of allowable characters (255). System Action: The server stops processing the command. User Response: Issue the command again and specify 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 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. User Response: Reissue the command after the indicated device class is defined to the server. ANR6696I command: operation for volume volume name in library library name starting.
Explanation: The indicated operation has failed because the entry/exit port of the specified library is full. System Action: The command fails. 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. ANR6691E Command: No match is found for this move.
Explanation: The indicated operation is being started for the volume shown in the given library. 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. ANR6697I command: operation for volume volume name in library library name completed successfully.
Explanation: The indicated command was issued, but no matching volumes are defined to the server or the volume specified is not managed by the command. System Action: The command is not processed.
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).
442
IBM Tivoli Storage Manager: Messages
ANR6698E ANR6707W
User Response: None. ANR6698E command: operation for volume volume name in library library name failed. ANR6703E Command: Invalid recovery plan prefix prefix.
Explanation: The indicated command has been entered with an invalid recovery plan prefix. System Action: The server does not process the command. User Response: Reissue the command with a valid recovery plan prefix. ANR6704E Command: Invalid plan instructions prefix - prefix.
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. System Action: The volume is not processed. User Response: Check for additional message and eliminate the condition that caused the failure, then retry the command. ANR6699I Cancel in progress.
Explanation: The indicated command has been entered with an invalid plan instructions prefix. System Action: The server does not process the command. User Response: Reissue the command with a valid plan instructions prefix. ANR6705E Command: Invalid character for volume postfix - postfix character.
Explanation: The MOVE DRMEDIA command 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 a MOVE DRMEDIA command. System Action: Server operation continues. User Response: None. ANR6700I Command command completed successfully.
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. System Action: The server does not process the command. User Response: Reissue the command with a valid character. ANR6706E Command: Invalid vault name - vault name.
Explanation: The indicated command completed successfully. System Action: None. User Response: None. ANR6701E Command: Invalid courier name - courier name.
Explanation: The indicated command has been entered with an invalid courier name. System Action: The server does not process the command. User Response: Reissue the command with a valid courier name. ANR6702E Command: Invalid expiration days value - days value.
Explanation: The indicated command has been entered with an invalid vault name. System Action: The server does not process the command. User Response: Reissue the command with a valid vault name. ANR6707W Command: The state, access and location attributes of the copy storage pool volume volume name were not updated.
Explanation: The indicated command has been entered that specifies an invalid expiration days value. System Action: The server does not process the command. User Response: Reissue the command with a valid expiration days value.
Explanation: The MOVE DRMEDIA command could not update the state, access and location of volume volume name because it was in use by another server 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. User Response: Wait until the conflicting volume
Chapter 3. Common and Platform Specfic Messages
443
ANR6711E ANR6719E
activity has completed, and then reissue the MOVE DRMEDIA command. ANR6711E Audit command: An invalid database backup series expiration days encountered. ANR6715E Audit command: An invalid file process value encountered.
Explanation: A database audit process encounters an invalid file process value. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the file process value. Or, issue a SET DRMFILEPROCESS command and specify a new file process value. ANR6716I Audit command: An invalid file process value encountered - the default value will be set.
Explanation: A database audit process encounters an invalid value for database backup series expiration days. System Action: Audit processing continues. User Response: Issue the command again and specify 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.
Explanation: A database audit process encounters an invalid file process value. Because FIX=YES has been specified, the audit function sets the file process value to the default value. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMFILEPROCESS command to change the value after the audit command has completed. ANR6717E Audit command: Extraneous DRM global attribute encountered.
Explanation: A database audit process encounters an 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. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMDBBACKUPEXPIREDAYS command to change the value after the audit command has completed. ANR6713E Audit command: An invalid check label value encountered.
Explanation: A database audit process finds a nonexistent DRM global attribute. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to delete the extraneous attribute. ANR6718I Audit command: Extraneous DRM global attribute encountered - the attribute will be deleted.
Explanation: A database audit process encounters an invalid check label value. System Action: Audit processing continues. User Response: Issue the command again and specify 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.
Explanation: A database audit process finds a nonexistent DRM global attribute. Since FIX=YES has been specified, the extraneous attribute will be deleted. System Action: Audit processing continues. User Response: None. ANR6719E Audit command: DRM machine ID assignments not found.
Explanation: A database audit process encounters an invalid check label value. Because FIX=YES has been specified, the audit function sets the check label value to the default value. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMCHECKLABEL command to change the value after the audit command has completed.
Explanation: A database audit process finds no entries in server database for DRM internal machine ID assignments. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the error.
444
IBM Tivoli Storage Manager: Messages
ANR6720I ANR6728I
ANR6720I Audit command: DRM machine ID assignments not found - entry will be created. User Response: To override the default value, issue a SET DRMPLANFILEPREFIX command to change the value after the audit command has completed. ANR6725E Audit command: Prefix for DRM recovery plan instructions not found.
Explanation: A database audit process finds no entries 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. System Action: Audit processing continues. User Response: None. ANR6721E Audit command: DRM recovery media ID assignments not found.
Explanation: A database audit process finds no entries in server database for DRM recovery plan instructions prefix definitions. System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6726I Audit command: Prefix for DRM recovery plan instructions not found - entry will be created.
Explanation: A database audit process finds no entries in server database for DRM internal recovery media ID assignments. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the error. ANR6722I Audit command: DRM recovery media ID assignments not found - entry will be created.
Explanation: A database audit process finds no entries 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. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMPLANINSTRPREFIX command to change the value after the audit command has completed. ANR6727E Audit command: Postfix for DRM replacement volumes names not found.
Explanation: A database audit process finds no entries 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. System Action: Audit processing continues. User Response: None. ANR6723E Audit command: Prefix for DRM recovery plan not found.
Explanation: A database audit process finds no entries in server database for DRM postfix definitions for replacement volumes names. System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6728I Audit command: Postfix for DRM replacement volumes names not found entry will be created.
Explanation: A database audit process finds no entries in server database for DRM recovery plan prefix definitions. System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6724I Audit command: Prefix for DRM recovery plan not found - entry will be created.
Explanation: A database audit process finds no entries 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. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMPLANVPOSTFIX command to change the value after the audit command has completed.
Explanation: A database audit process finds no entries 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. System Action: Audit processing continues.
Chapter 3. Common and Platform Specfic Messages
445
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. 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. ANR6734E Command: Volume volume name not processed: library library name not defined.
Explanation: A database audit process finds no entries in server database for primary storage pools to be restored by DRM. System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6730I Audit command: Primary storage pools to be restored by DRM not found - entry will be created.
Explanation: A database audit process finds no entries in server database for primary storage pools to be restored by DRM. Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the primary storage pools to be restored by DRM. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMPRIMSTGPOOL command to change the value after the audit command has completed. ANR6731E Audit command: Copy storage pools to be managed by DRM not found.
Explanation: The indicated volume is not processed since the designated library has not been defined or has been deleted. System Action: The volume is not processed. User Response: Reissue the command using a different library name, or define the library before retrying the command. ANR6735E Audit command: Courier information for ORM not found.
Explanation: A database audit process finds no entries in server database for courier name definitions used by DRM Offsite Recovery Media (ORM). System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6736I Audit command: Courier information for ORM not found - entry will be created.
Explanation: A database audit process finds no entries in server database for copy storage pools to be managed by DRM. System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6732I Audit command: Copy storage pools to be managed by DRM not found - entry will be created.
Explanation: A database audit process finds no entries 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 function creates an entry using the default value in the server database for the courier name definitions. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMCOURIERNAME command to change the value after the audit command has completed. ANR6737E Audit command: Vault name for ORM not found.
Explanation: A database audit process finds no entries in server database for copy storage pools to be managed by DRM. Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the copy storage pools to be managed by DRM. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMCOPYSTGPOOL command to change the value after the audit command has completed. ANR6733E Command: Cannot complete initialization for process name process.
Explanation: A database audit process finds no entries in server database for vault name definitions used by DRM Offsite Recovery Media (ORM). System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error.
Explanation: The indicated process fails during process initialization.
446
IBM Tivoli Storage Manager: Messages
ANR6738I ANR6746I
ANR6738I Audit command: Vault name for ORM not found - entry will be created. ANR6742I Audit command: Check label indicator for ORM not found - entry will be created.
Explanation: A database audit process finds no entries in server database for vault name definitions used by DRM Offsite Recovery Media (ORM). 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 vault name definitions. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMVAULTNAME command to change the value after the audit command has completed. ANR6739E Audit command: Database backup series expiration days for ORM not found.
Explanation: A database audit process finds no entries in server database for check label definitions used by DRM Offsite Recovery Media (ORM ). 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 check label definitions. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMCHECKLABEL command to change the value after the audit command has completed. ANR6743E Audit command: File process indicator for ORM not found.
Explanation: A database audit process finds no entries in server database for database backup series expiration days definitions used by DRM Offsite Recovery Media (ORM). System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6740I Audit command: Database backup series expiration days for ORM not found entry will be created.
Explanation: A database audit process finds no entries in server database for file process definitions used by DRM Offsite Recovery Media (ORM). System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6744I Audit command: File process indicator for ORM not found - entry will be created.
Explanation: A database audit process finds no entries 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 audit command, the audit function creates an entry using the default value in the server database for the database backup series expiration days definitions. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMDBBACKUPEXPIREDAYS command to change the value after the audit command has completed. ANR6741E Audit command: Check label indicator for ORM not found.
Explanation: A database audit process finds no entries in server database for file process definitions used by DRM Offsite Recovery Media (ORM). Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the file process definitions. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMFILEPROCESS command to change the value after the audit command has completed. ANR6745E Audit command: DRM recovery media ID assignments are incorrect.
Explanation: A database audit process finds that the global attributes recovery media id used for server DRM activities are incorrect. System Action: Audit processing continues. User Response: Reissue the audit command with FIX=YES specified so that the DRM global attributes can be corrected. ANR6746I Audit command: DRM recovery media ID assignments are incorrect - values will be corrected.
Explanation: A database audit process finds no entries in server database for check label definitions used by DRM Offsite Recovery Media (ORM). System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error.
Explanation: A database audit process finds that the global attributes recovery media ID used for server DRM activities are incorrect. Since FIX=YES has been
Chapter 3. Common and Platform Specfic Messages
447
ANR6747I ANR6754I
specified on the AUDIT command, the attribute value will be corrected in the server database. System Action: Audit processing continues. User Response: None. ANR6747I Number of volumes processed: number ANR6751E 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. System Action: Server operation continues. 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 Disaster recovery manager operation Command being processed is in violation of server license terms - server is not licensed for disaster recovery manager support.
Explanation: The MOVE DRMEDIA command has processed the number of volumes displayed. This message may be displayed in response to a QUERY PROCESS command for a MOVE DRMEDIA command. System Action: Server operation continues. User Response: None. 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 displayed in response to a QUERY PROCESS command for a MOVE DRMEDIA command. System Action: Server operation continues. User Response: None. ANR6749I Command: process process ID terminated before completion - process canceled.
Explanation: The server warns about a disaster recovery manager operation because the server is not licensed to support disaster recovery manager. System Action: Server operation continues. 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.
Explanation: The indicated background process performing the command shown has been canceled. System Action: If other processes are executing, these processes continue. User Response: None. ANR6750E Disaster recovery manager operation command being processed is denied - server is not in compliance with license terms.
Explanation: The server encountered an internal error in determining whether the server is in compliance with license terms. System Action: Server operation continues. 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.
Explanation: The server refuses a disaster recovery manager operation because the current server configuration is not in compliance with the license terms. System Action: Server operation continues. Disaster recovery operations cannot be performed until the server is licensed for the Tivoli Disaster Recovery Manager product. User Response: Issue a QUERY LICENSE command to determine which license terms are not in compliance.
Explanation: A DELETE MACHINE command has deleted the requested characteristics from the server. System Action: None. User Response: None.
448
IBM Tivoli Storage Manager: Messages
ANR6755I ANR6761E
ANR6755I Machine machine name recovery instructions deleted. System Action: Server operation continues. User Response: None. ANR6760E Command: Executable command line exceeds maximum length characters for volume volume name.
Explanation: A DELETE MACHINE command has deleted the requested recovery instructions from the server. System Action: None. User Response: None. ANR6756E Machine machine name characteristics not defined to the server.
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). System Action: The server stops processing the command. User Response: Issue the command again and specify 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: A DELETE MACHINE command cannot delete the requested characteristics from the server. The characteristics for the specified machine are not defined to the server. System Action: The server operation continues, but the command has no effect. User Response: Issue the command again and specify 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. System Action: The server operation continues, but the command has no effect. User Response: Issue the command again and specify 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. System Action: The server does not process the command. User Response: Issue the command again and specify one valid character string. ANR6759E Disaster recovery manager operation command being processed is denied disaster recovery manager support is not available for server platform platform.
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. System Action: The server does not process the command. User Response: Reissue the command specifying a specific volume name or by specifying the WHERESTATE parameter along with the TOSTATE parameter.
Explanation: The server refuses a disaster recovery manager operation because disaster recovery manager support is not available for the indicated server platform.
Chapter 3. Common and Platform Specfic Messages
449
ANR6762E ANR6771E
ANR6762E Command: The specified destination state tostate is invalid for volume volume name in current state state. ANR6767E Command: Invalid command file name command file name.
Explanation: The indicated command specifies a destination state that is invalid for the volume name shown in the indicated current state. System Action: The server does not process the volume. User Response: Issue the command again and specify a valid destination state for the volume name shown. ANR6763I Command: The specified command has been written to file file name.
Explanation: The indicated command has been entered with an invalid command file name. System Action: The server does not process the command. User Response: Reissue the command with a valid command file name. ANR6768E command: Prefix exceeds maximum characters characters.
Explanation: The command string specified with the CMD parameter on the command shown is written to the indicated file for each volume successfully processed. System Action: None. User Response: Execute the commands written to the file. ANR6764E command: Command file name 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. System Action: The server does not process the command. User Response: Reissue the command specifying a valid prefix. ANR6769E Audit command: Not mountable name information for ORM not found.
Explanation: The file name specified for containing the executable commands generated by DRM exceeds the maximum valid length shown. System Action: The server does not process the command. User Response: Reissue the command specifying a valid file name. ANR6765E Command: Invalid not mountable location name - not mountable name.
Explanation: A database audit process finds no entries in server database for not mountable location name definitions used by DRM Offsite Recovery Media (ORM). System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6770I Audit command: Not mountable name information for ORM not found - entry will be created.
Explanation: The indicated command has been entered with an invalid not mountable location name. System Action: The server does not process the command. User Response: Reissue the command with a valid not mountable location name. ANR6766E Command: No command string is specified for FORMAT=CMD.
Explanation: A database audit process finds no entries in server database for not mountable location name definitions used by DRM Offsite Recovery Media (ORM). 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 courier name definitions. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMNOTMOUNTABLENAME command to change the value after the audit command has completed. ANR6771E Audit command: Command file name information for ORM not found.
Explanation: The indicated command has been entered with a FORMAT=CMD to write a command string to a file, but no command string is specified. System Action: The server does not process the command. User Response: Reissue the command specifying a command string to be written to a file.
Explanation: A database audit process finds no entries in server database for command file name definitions used by DRM Offsite Recovery Media (ORM).
450
IBM Tivoli Storage Manager: Messages
ANR6772I ANR6778E
System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6772I Audit command: Command file name information for ORM not found - entry will be created. ANR6775E Command: Error writing to file file name for volume volume name.
Explanation: An error occurred while writing to the file name shown for the indicated volume. System Action: The server stops processing the command. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated. 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
Explanation: A database audit process finds no entries in server database for command file name definitions used by DRM Offsite Recovery Media (ORM). 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 command file name definitions. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMCMDFILENAME command to change the value after the audit command has completed. ANR6773E Command: Unable to open file command file name for output.
Explanation: An error occurred while opening the 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. System Action: The server does not process the indicated command. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated. In AIX, make sure that the file name specified in the command or in the SET command is a full path file name, not a directory path name. In MVS, make sure that the file name specified in the command or in the SET command is a valid MVS file name. Reissue the command after determining the cause of the error. ANR6774E Command: Invalid volume transition states - from specified WHERESTATE state to specified TOSTATE state.
Explanation: The indicated command failed but the file created could not be deleted. System Action: None. User Response: Delete the file shown. ANR6777E Command: Command file file name already in use.
Explanation: The command indicated references a 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). System Action: The server does not process the command. User Response: Reissue the command at a later time or reissue the command specifying a different command file name. ANR6778E Command: Volume volume name not processed: device type device type not supported.
Explanation: The TOSTATE specified is an invalid destination state for the WHERESTATE specified. System Action: The server does not process the command. User Response: Issue the command again and specify a valid destination state.
Explanation: The indicated volume is not processed because the device type shown is not supported by the function.
Chapter 3. Common and Platform Specfic Messages
451
ANR6779E ANR6901I
System Action: The indicated volume is not processed. User Response: None. ANR6779E Disaster recovery manager operation command being processed is denied disaster recovery manager support is not available for server platform. audit command, the audit function creates an entry using the default value in the server database for the recovery plan file expiration days definitions. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMRPFEXPIREDAYS command to change the value after the audit command has completed. ANR6784I Number of volumes processed: number volumes processed. Volumes sent to library library name for checkout: number volumes sent.
Explanation: The server refuses a disaster recovery manager operation because disaster recovery manager support is not available for the server platform. System Action: Server operation continues. User Response: None. ANR6780E Audit command: An invalid recovery plan file expiration days encountered.
Explanation: A database audit process encounters an invalid value for recovery plan file expiration days. System Action: Audit processing continues. User Response: Issue the command again and specify FIX=YES to correct the expiration days. Or, issue an SET DRMRPFEXPIREDAYS command and specify a new expiration days value. ANR6781I Audit command: An invalid recovery plan file expiration days encountered - the default value will be set.
Explanation: The MOVE DRMEDIA command has 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. System Action: Server operation continues. User Response: None. ANR6785W Warning: The ADSM V3 Disaster Recovery Manager Disk Image Dump function is not supported in the Tivoli Disaster Recovery Manager. The ADSM V3 DRM Disk Image Restore function has been stabilized with no new maintenance or hardware support planned.
Explanation: A database audit process encounters an invalid value for recovery plan file expiration days. Because FIX=YES has been specified, the audit function sets the expiration days value to the default value. System Action: Audit processing continues. User Response: To override the default value, issue a SET DRMRPFEXPIREDAYS command to change the value after the audit command has completed. ANR6782E Audit command: Recovery plan file expiration days not found.
Explanation: None. System Action: DRM Disk Image Dump and Restore function continues. User Response: None. ANR6900I Command: The recovery plan file file name was created.
Explanation: The recovery plan file was created. System Action: None. User Response: None. ANR6901I Number of plan stanzas processed: number.
Explanation: A database audit process finds no entries in server database for recovery plan file expiration days definitions. System Action: Audit processing continues. User Response: Issue the audit command again and specify FIX=YES to correct the error. ANR6783I Audit command: Recovery plan file expiration days not found - entry will be created.
Explanation: The PREPARE command has processed the number of stanzas displayed. This message may be displayed in response to a QUERY PROCESS command for a PREPARE command. System Action: Server operation continues. User Response: None.
Explanation: A database audit process finds no entries in server database for recovery plan file expiration days definitions. Because FIX=YES has been specified for the
452
IBM Tivoli Storage Manager: Messages
ANR6902I ANR6920W
ANR6902I Number of plan stanzas processed: number. Currently processing stanza: recovery plan stanza name. ANR6913W Command: No volumes with backup data exist in copy storage pool storage pool 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. System Action: Server operation continues. User Response: None. ANR6903I Cancel in progress.
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. ANR6915W Command: Storage pool storage pool name storage pool type is not defined to the server.
Explanation: The PREPARE command 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 a PREPARE command. System Action: Server operation continues. User Response: None. ANR6904I Sending recovery plan file to target 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. System Action: Stanzas in the recovery plan do not include recovery information for the storage pool. User Response: Correct the storage pool specification or define the storage pool to the server. ANR6916W Command: No copy storage pools are defined.
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. System Action: Server operation continues. User Response: None. ANR6905I Command: Recovery plan file RPF volume name was created. Specified device class device class name.
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: The recovery plan file was created on the target server. System Action: Server operation continues. User Response: None. ANR6912W Command: The database was not backed up.
Explanation: A source file for recovery instructions was not found. System Action: The recovery plan will not contain recovery instructions. User Response: To get recovery instructions in the recovery plan, ensure the corresponding instructions source file exists. If it does, check authorizations to the file. ANR6920W 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: No backups have been made of the server data base. System Action: Stanzas in the recovery plan do not include database recovery information. User Response: Backup the server data base by issuing the BACKUP DB command.
Explanation: Appending the replacement volume name postfix (as defined with SET DRMPLANVPOSTFIX) to the original volume name
Chapter 3. Common and Platform Specfic Messages
453
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 the Administrators Reference for your particular 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 Reference for your particular platform. ANR6925W Command: No machine characteristics defined for machine machine name.
Explanation: The Prepare command cannot open the specified server options file. System Action: VOLHISTORY and DEVCONFIG options are added to the recovery plan file stanza DSMSERV.OPT.FILE. User Response: None. ANR6922W Command: No machine information was defined for the machine that contains server server name.
Explanation: No characteristics have been defined to the server for the specified machine. System Action: The recovery plan file does not contain the machine characteristics 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 Reference for your particular platform. 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.
Explanation: The machine information has not been saved in the server data base. System Action: The recovery plan file does not contain the machine and recovery media information stanzas. User Response: If you want to include the machine information in the recovery plan file, issue the DEFINE MACHINE command to save the machine information in the server data base and reissue the PREPARE command. ANR6923W Command: No recovery media defined for machine machine name.
Explanation: Appending the replacement volume name postfix (as defined with SET DRMPLANVPOSTFIX) to the original volume name has created a name that is not valid for the server device type shown. System Action: Replacement volume name is used in the recovery plan stanza. User Response: Devise a naming convention that allows the use of the replacement volume name postfix or at restore time manually update the generated recovery plan with a legal replacement name. For additional information and related commands, refer to the Administrators Reference for your particular platform. ANR6927W Command: Primary storage pool storage pool name, storage pool data format, is not managed by DRM.
Explanation: No recovery media has been defined to the server for the specified machine. System Action: The recovery plan file does not contain the machine recovery media stanza. User Response: If you want to include the machine recovery media information in the recovery plan file, issue the DEFINE RECOVERYMEDIA command. Reissue the PREPARE command after the appropriate commands have been issued to define the recovery media. For additional information and related commands, refer to the Administrators Reference for your particular platform.
Explanation: A SET DRMPRIMSTGPOOL or the PREPARE command specified a primary storage pool that is used for backing up NAS file servers, using
454
IBM Tivoli Storage Manager: Messages
ANR6928W ANR6942E
NDMP. DRM does not manage a storage pool with this data format. System Action: Stanzas in the recovery plan do not include recovery information for the storage pool. User Response: Correct the storage pool specification. ANR6938I ANR6928W Command: No eligible primary storage pools match the specified storage pool name storage pool name . No information found for stanza stanza name. System Action: The server does not process the command. User Response: Reissue the command with the parameter from the web.
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: Invalid recovery plan file stanza name - stanza 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. System Action: Stanzas in the recovery plan do not include recovery information for the storage pools. User Response: Correct the storage pool specification or define eligible storage pools to the server. ANR6929W Command: No eligible primary storage pools are defined to the server.
Explanation: The specified recovery plan file stanza name is invalid. System Action: The server does not process the command. User Response: Issue the command again and specify a valid recovery plan file stanza name. ANR6940E command command not allowed from server console.
Explanation: The server has no eligible primary storage pools defined. System Action: Recovery plan file will not contain primary storage pool information. User Response: Define eligible primary storage pools to the server. ANR6930W Command: Primary storage pool storage pool name, whose device class uses the CENTERA device type, is not managed by DRM.
Explanation: The indicated command is not allowed to be issued from the server console. System Action: The command is not executed. User Response: Reissue the command from an administrator using an Administrative Client. ANR6941E Query recovery plan file content is waiting for mount point in device class device class name.
Explanation: Query recovery plan file content has begun to wait for a mount point that can be used for a volume in the device class shown. System Action: The function waits for the mount point. User Response: Respond to any mount requests. ANR6942E Query recovery plan file content is waiting for access to input volume volume name.
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: Stanzas in the recovery plan do not include recovery information for the storage pool. User Response: Correct the storage pool specification. ANR6937E command: parameter name parameter not allowed from the command line.
Explanation: Query recovery plan file content has begun to wait for availability of the input volume shown. System Action: The function waits for the volume to become available. User Response: None.
Explanation: The parameter shown is not allowed from the command line interface.
Chapter 3. Common and Platform Specfic Messages
455
ANR6943E ANR6951E
ANR6943E Query recovery plan file content is waiting for mount of input volume volume name. System Action: The retrieve operation ends, and the server operation continues. User Response: Contact your service representative. ANR6948E Command: Cannot find the recovery plan file for Recovery plan file name.
Explanation: Query recovery plan file content has begun to wait for the mount of the input volume shown. System Action: The function waits for mount. User Response: Respond to any mount requests. ANR6944E Command: Invalid recovery plan file name - recovery plan file name.
Explanation: The server cannot find the specified recovery plan file. System Action: The server does not process the command. User Response: Issue the command again and specify 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: No matching device class defined.
Explanation: The recovery plan file name specified in the command is invalid. System Action: The server does not process the command. User Response: Issue the command again and specify a valid recovery plan file name. ANR6945E Command: Cannot find filespace filespace name for recovery plan file recovery plan file name.
Explanation: The device class specified in the command does not match any device class defined to the server. System Action: The server does not process the command. User Response: Issue the command again and specify a valid device class. ANR6950E Command: The recovery plan file was not created.
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 server operation continues. 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: Due to a processing error, a recovery plan file was not created. System Action: Recovery plan file not created. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Reissue the command, after determining the cause of the error. ANR6951E Command: Recovery plan file file name was not created.
Explanation: The server ends an retrieve operation because an I/O error has been encountered by the server in reading from a device. System Action: The retrieve operation ends, and the server operation continues. User Response: Query the activity log to find messages preceding this one that specify the device that is failing. The server may need to be shut down with the HALT command to correct the hardware problem. ANR6947E Command: Data storage retrieve failed for recovery plan file name - data integrity error detected.
Explanation: Due to a processing error, a recovery plan file was not created. System Action: Recovery plan file not created. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. Reissue the command, after determining the cause of the error.
Explanation: The server ends the retrieve operation because an internal database integrity error has been encountered on the server.
456
IBM Tivoli Storage Manager: Messages
ANR6952E ANR6966E
ANR6952E Command: File name file name already exists. ANR6962E Command: Query database failed.
Explanation: File already exits. System Action: None. User Response: Determine why file already exists. If possible, delete it. Reissue the command, after determining the cause of the error. ANR6953E Command: File write error.
Explanation: A server database query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created. User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6963E Command: Query log failed.
Explanation: An error occurred while writing to the recovery plan file. System Action: The recovery plan file was not created. User Response: Examine error messages that may have been displayed prior to this message and correct any 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.
Explanation: A server database query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created. User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6964E Command: Query storage pool failed.
Explanation: An error occurred while opening the recovery plan file for output. System Action: The recovery plan file was not created. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated. Reissue the command after determining the cause of the error. ANR6959E Command: Plan instructions prefix instructions prefix is not valid.
Explanation: An server database query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created. User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6965E Command: Query volume failed.
Explanation: The prefix specified for recovery instructions is not valid. System Action: The recovery plan file was not created. User Response: Reissue the command specifying a valid prefix. ANR6960E Command: Recovery plan prefix plan prefix is not valid.
Explanation: An server database query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created. User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6966E Command: Query database volume failed.
Explanation: The prefix specified for the recovery plan file is too long. System Action: The recovery plan file was not created. User Response: Reissue the command specifying a valid prefix.
Explanation: A server database query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created.
Chapter 3. Common and Platform Specfic Messages
457
ANR6967E ANR6975E
User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6967E Command: Query log volume failed. ANR6971E Command: Could not delete plan file plan file name.
Explanation: Prepare command failed but the plan file created could not be deleted. System Action: None. User Response: Delete the plan file. ANR6972E Command: Query machine failed.
Explanation: A server database query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created. User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6968E Command: Query volume history failed.
Explanation: A server machine query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created. User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6973E Command: Query recovery media failed.
Explanation: An server database query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created. User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6969E Command: Query device class failed.
Explanation: A server recovery media query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created. User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6974E Command: Unable to open file file name.
Explanation: An server database query error occurred. This message always accompanies another error message and provides more detail about that error. System Action: The recovery plan file was not created. User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative. ANR6970E Command: A recovery plan file is already being created.
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. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Reissue the command after determining the cause of the error. ANR6975E Command: Unable to read file file name.
Explanation: The server command processor will not start a background process to execute another PREPARE command. System Action: The command process ends and server operation continues. User Response: Reissue the command after the first PREPARE command has completed.
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. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Reissue the command after
458
IBM Tivoli Storage Manager: Messages
ANR6976E ANR6986E
determining the cause of the error. ANR6976E Command: The recovery plan file was not stored on another server and the local copy file name cannot be deleted. ANR6980E Command: Prefix prefix exceeds maximum characters characters.
Explanation: Due to a processing error, a recovery plan file was not stored on target server and the local copy of the plan file cannot be deleted. System Action: PREPARE processing ends. User Response: Examine error messages that may have been displayed prior to this message and correct any 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 plan or instructions prefix that is too long. The maximum valid length is shown in the message. System Action: The server does not process the command. User Response: Reissue the command specifying a shorter prefix. ANR6984E Command: Out of space on sequential media, scratch media could not be mounted. Specified device class device class name; maximum capacity: number of bytes bytes.
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. System Action: The server does not process the command. User Response: Reissue the command specifying a valid device class name. ANR6978E Command: Invalid device class device class name.
Explanation: During command PREPARE processing, the process encounters an out-of-space condition writing to the sequential media. Command PREPARE ends when there is no more space on the sequential media for storing data. System Action: Command PREPARE processing ends. Server processing continues. 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: Error encountered in accessing data storage - volume already in use.
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. System Action: The server does not process the command. User Response: Reissue the command with a valid device class. ANR6979E Command: Recovery plan file was not created. Specified device class device class name.
Explanation: During command command processing, a volume cannot be used because it is already defined in a storage pool, or has been previously used by an export, database dump, database backup, or DRM prepare operation or is in use by another process. System Action: The command command operation is ended and server operation continues. User Response: Re-issue the PREPARE command. ANR6986E Command: The DELETELATEST parameter is only valid for volume history types RPFILE or RPFSNAPSHOT.
Explanation: A recovery plan file cannot be not created using the specified device class. System Action: Recovery plan file not created. User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Reissue the command, after determining the cause of the error.
Explanation: The command failed because an invalid volume history type was specified for the TYPE= parameter. System Action: The command fails, and server operation continues. User Response: Re-issue the command and specify a valid type value.
Chapter 3. Common and Platform Specfic Messages
459
ANR7800I ANR7803E
ANR7800I DSMSERV generated at time on date. User Response: None. ANR7801I (Linux) Subsystem process ID is process identifier. Explanation: The server process has the indicated process identifier. System Action: Server operation continues. ANR7800I (HP-UX) DSMSERV generated at time on date. Explanation: The server module was generated at the indicated date and time. System Action: Server operation continues. User Response: None. ANR7800I (Linux) DSMSERV generated at time on date. Explanation: The server module was generated at the indicated date and time. System Action: Server operation continues. User Response: None. ANR7800I (Solaris) DSMSERV generated at time on date. Explanation: The server module was generated at the indicated date and time. System Action: Server operation continues. User Response: None. ANR7800I (Windows) DSMSERV generated at time on date. Explanation: The server module was generated at the indicated date and time. System Action: Server operation continues. User Response: None. ANR7801I Subsystem (master) PID is process identifier. User Response: None. ANR7801I (Solaris) Subsystem process ID is process identifier. Explanation: The server process has the indicated process identifier. System Action: Server operation continues. User Response: None. ANR7802E Shared memory segments for a server running in the current directory already exist. The -F parameter can be used to overwrite.
Explanation: The server module was generated at the indicated date and time. System Action: Server operation continues. User Response: None.
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. ANR7803E Attempt to overwrite a shared memory segment, as directed with the -F parameter, FAILED.
Explanation: The server kernel extension process has the indicated process identifier. System Action: Server operation continues. User Response: None. ANR7801I (HP-UX) Subsystem (master) process ID is process identifier. Explanation: The servers master HP-UX process has the indicated process identifier. System Action: Server operation continues.
Explanation: The server has been started with the -F parameter and unsuccessfully attempted to overwrite existing shared memory segments. This error occurs when the user that starts the server with -F parameter is not the owner of the shared memory segments and lacks the required authority. System Action: Server terminates. User Response: Resolve the authorization problem and restart the server.
460
IBM Tivoli Storage Manager: Messages
ANR7804I ANR7805E (Solaris)
ANR7804I An server is already running from this directory. server ONLY if there are no other dsmserv processes running ANR7805E (Linux) Volume volume name is in use by another server. Explanation: The server has attempted to open a disk volume but has discovered that the volume is in use by another server. System Action: The open operation fails for the volume. User Response: To prevent concurrent RAW volume access by more than one server, files are created in the /tmp directory to 'lock' these volumes. The names of these temporary files are /tmp/adsm.disk.dev.<volumename> where <volumename> is the name of the RAW volume defined in the /dev directory. Please note that the name for 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. Explanation: The server has attempted to open a disk volume but has discovered that the volume is in use by another server. System Action: The open operation fails for the volume. User Response: To prevent concurrent RAW volume access by more than one server, files are created in the /tmp directory to 'lock' these volumes. The names of these temporary files are /tmp/adsm.disk.dev.<volumename> where <volumename> is the name of the RAW volume defined in the /dev directory. Please note that the name for 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
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. System Action: Server terminates. 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' AIX command can be used to display processes that are currently running. ANR7804I (HP-UX) 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. System Action: Server terminates. 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' command can be used to display processes that are currently running. ANR7805E Volume volume name is in use by another server.
Explanation: The server has attempted to open a disk volume but has discovered that the volume is in use by another server. System Action: The open operation fails for the volume. User Response: To prevent concurrent RAW volume access by more than one server, files are created in the /tmp directory to 'lock' these volumes. The names of these temporary files are /tmp/adsm.disk.dev.<volumename> where <volumename> is the name of the RAW volume defined in the /dev directory. Please note that the name for the logical volume as defined in SMIT is represented in the /dev directory with a leading 'r' character (for example, a raw volume defined in SMIT as dsmstg1 will be represented in the /dev directory as the file /dev/rdsmstg1). You may use the AIX 'ps -e' command to determine if other dsmserv processes are running. You may remove the temporary lock files and attempt to re-start the
Chapter 3. Common and Platform Specfic Messages
461
ANR7806W ANR7807W (HP-UX)
since the server locks the linked volume, not the link name itself. You may use the Solaris 'ps -ef | grep dsmserv' command to determine if other dsmserv processes are running. You may remove the temporary lock files for RAW volumes and attempt to re-start the server ONLY if there are no other dsmserv processes are running. ANR7806W Unable to open file file. 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 (Windows) 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. The file may be already opened by the server or another program. ANR7807W Unable to get information for 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 (HP-UX) Unable to open file file. Explanation: The server was unable to open the indicated file. System Action: The operation that was to use the indicated file fails. A subsequent unnumbered message had details from the system. User Response: Determine the reason for being unable to open the file and re-attempt the operation. Common reasons for being unable to open the file include providing the wrong name, having insufficient authorization to open the file and not being the files owner. ANR7806W (Linux) 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 (Solaris) 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
Explanation: The server was unable to get information about the indicated file. System Action: The operation that was to use the indicated file fails. A subsequent, unnumbered message has details from the system. User Response: Determine the reason for being unable 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 authorization to open the file and not being the files owner. ANR7807W (HP-UX) Unable to get information for file file. Explanation: The server was unable to get information about the indicated file. System Action: The operation that was to use the indicated file fails. A subsequent, unnumbered message has details from the system. User Response: Determine the reason for being unable 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 authorization to open the file and not being the files owner.
462
IBM Tivoli Storage Manager: Messages
ANR7807W (Linux) ANR7811E (HP-UX)
ANR7807W (Linux) Unable to get information for file file. Explanation: The server was unable to get information about the indicated file. System Action: The operation that was to use the indicated file fails. A subsequent, unnumbered message has details from the system. User Response: Determine the reason for being unable 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 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. Explanation: The server was unable to get information about the indicated file. System Action: The operation that was to use the indicated file fails. A subsequent, unnumbered message has details from the system. User Response: Determine the reason for being unable 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 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. 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 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. Explanation: Unable to start console input thread. System Action: Server operation stops. User Response: See other issued messages. ANR7810E (Solaris) Error creating console input thread. Explanation: Unable to start console input thread. System Action: Server operation stops. User Response: See other issued messages. ANR7811E (HP-UX) Insufficient memory for console initialization. Explanation: The server is unable to allocate enough memory for console initialization. System Action: Server operation stops. User Response: Ensure that there is sufficient paging space for HP-UX. It may be necessary to reduce the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.
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. ANR7809I Using scheduling policy policy.
Explanation: All threads in the server will use the specified scheduling policy. System Action: Operations continue User Response: None
Chapter 3. Common and Platform Specfic Messages
463
ANR7811E (Linux) ANR7813W (Solaris)
ANR7811E (Linux) Insufficient memory for console initialization. Explanation: The server is unable to allocate enough memory for console initialization. System Action: Server operation stops. 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. ANR7811E (Solaris) Insufficient memory for console initialization. Explanation: The server is unable to allocate enough memory for console initialization. System Action: Server operation stops. User Response: Ensure that there is sufficient paging space for Sun Solaris. It may be necessary to reduce the maximum number of client sessions by changing the MAXSESSIONS option in the server options file. ANR7812E (HP-UX) 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. User Response: Ensure that there is sufficient paging space for HP-UX. It may be necessary to reduce the maximum number of client sessions by changing the MAXSESSIONS option in the server options file. ANR7812E (Linux) 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. 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. 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. User Response: Ensure that there is sufficient paging space for Sun Solaris. It may be necessary to reduce the maximum number of client sessions by changing the MAXSESSIONS option in the server options file. 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. System Action: Server processing continues. 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. 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 swap space is available for Solaris. The amount of swap available can be obtained by executing 'swap -l'. If the number of free blocks is low, you can add swap files while the system is running by executing 'mkfile' and then 'swap -a'. See the Solaris man pages on 'mkfile' and 'swap' for more details. If the server has been started from a non-root user ID, ensure that the process limit per user is sufficient to accomodate the server. You can tune the 'maxusers=##' parameter in the /etc/system file to increase the number of number of users that can be on the system at one time. This will also force the kernel to allocate more memory/swap for user-processes. A system reboot with the 'reconfigure' option is required for the new user settings to take effect. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file. ANR7813W (Solaris) Unable to create a new child thread. 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 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
464
IBM Tivoli Storage Manager: Messages
ANR7814I (HP-UX) ANR7821I (Linux)
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) The size of the file ( ) is not a multiple of the disk block size (). The server rounds to nearest smaller block multiple (). Explanation: The server, while attempting to define a volume, had to round off the size to the nearest smaller number, which is a multiple of the disk block size (). System Action: Server operation continues. User Response: None. ANR7820E Insufficient memory to buffer console input; the following input line was discarded: discarded console input. User Response: Note the associated messages and call your service representative. ANR7820S (Solaris) 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 call your service representative. ANR7820W (Windows) Insufficient Space Available for file file name. Explanation: The server was attempting to create a file with the indicated name. There was insufficient space for the file on the disk. System Action: Server processing continues. The file creation request fails. User Response: Specify a file name on a drive with sufficient space or change the space request to a value consistent with the drive. ANR7821E Error reading from standard input.
Explanation: An error occurs during an attempt to allocate a buffer large enough to read console input. System Action: The console input is discarded. User Response: Ensure that sufficient paging space is 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 number of client sessions by changing the MAXSESSIONS option in the server options file. 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 contact your service representative. ANR7820S (Linux) 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.
Explanation: An error occurs during an attempt to read from standard input. System Action: The console input thread is terminated. User Response: Correct the standard input problem and restart the server. ANR7821I (HP-UX) Server thread thread ID terminated in response to external signal. Explanation: The thread has ended due to an external signal. System Action: The server completes termination processing. User Response: None. ANR7821I (Linux) Thread thread ID terminated in response to external signal. Explanation: The thread has ended due to an external signal. System Action: The server completes termination processing. User Response: None.
Chapter 3. Common and Platform Specfic Messages
465
ANR7821I (Solaris) ANR7824E
ANR7821I (Solaris) Server thread thread ID terminated in response to external signal. Explanation: The thread has ended due to an external signal. System Action: The server completes termination processing. User Response: None. ANR7821W (Windows) Unable to create directory when creating volume file name. Explanation: The server was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed. System Action: Server processing continues. The file creation request fails. User Response: Specify a file name in an existing directory or change the name request to specify a different directory name. ANR7822E Error creating console input thread. User Response: None. ANR7822W (Windows) File Already exists when creating volume file name. Explanation: The server was attempting to create a file with the indicated name. The file already exists. System Action: Server processing continues. The file creation request fails. User Response: Specify a new file name. The server will not use an existing file name when creating a file. ANR7823E Insufficient memory for console initialization.
Explanation: Unable to allocate enough memory for console initialization. System Action: Server operation stops. User Response: Ensure that sufficient paging space is 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 number of client sessions by changing the MAXSESSIONS option in the server options file. ANR7823S (Linux) Internal error internal error detected. Explanation: An internal error is detected during server initialization or operation. System Action: Server operation stops. User Response: Contact your service representative. ANR7823W (Windows) Unable to create file file name. Explanation: The server was attempting to create a file with the indicated name. The system reported an error in creating the file. System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. ANR7824E Error loading Async I/O support module.
Explanation: Unable to start console input thread. System Action: Server operation stops. User Response: See other issued messages. ANR7822I (HP-UX) Server thread thread ID terminated in response to server shutdown. Explanation: The thread has ended due to a server shutdown. System Action: The server completes termination processing. User Response: None. ANR7822I (Linux) Thread thread ID terminated in response to server shutdown. Explanation: The thread has ended due to a server shutdown. System Action: The server completes termination processing. User Response: None. ANR7822I (Solaris) Server thread thread ID terminated in response to server shutdown. Explanation: The thread has ended due to a server shutdown. System Action: The server completes termination processing.
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. System Action: Server operation continues, but 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.
466
IBM Tivoli Storage Manager: Messages
ANR7824S (HP-UX) ANR7830E (Solaris)
ANR7824S (HP-UX) Server operation terminated. Explanation: An error occurs that causes server operation to stop. System Action: Server operation stops. User Response: Contact your service representative. ANR7824S (Linux) Server operation terminated. Explanation: An error occurs that causes server operation to stop. System Action: Server operation stops. User Response: Contact your service representative. ANR7824S (Solaris) Server operation terminated. Explanation: An error occurs that causes server operation to stop. System Action: Server operation stops. User Response: Contact your service representative. ANR7824W (Windows) Unable to write volume file name. Explanation: The server was attempting to create a file with the indicated name. The server was able to partially write to the file before running out of space. System Action: The server continues processing. The 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 (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 ANR7825W (Windows) Unable to create volume file name. Return code= return code. Explanation: The server was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is an internal code from the server. System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. The return code may also be provided to your service representative for interpretation. ANR7826W (Windows) Creation of Volume file name failed. Process was cancelled. Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command. System Action: The server continues processing. The file creation request fails. User Response: The DEFINE command may be re-entered. 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. 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. 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. 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.
Chapter 3. Common and Platform Specfic Messages
467
ANR7831E (Linux) ANR7833E (Solaris)
ANR7831E (Linux) raw partition name has an existing filesystem. Explanation: The RAW partition specified has an existing Solaris file system on it. Writing to this Partition may/and most likely will destroy this filesystem. System Action: Warn the user that an existing filesystem for the raw partition specified may be destroyed if written to. User Response: Determine if user still wants the valid filesystem data. If not, user needs to destroy the filesystem by either formatting the partition, create a program to destroy the filesystem header information so that the server will not be able to detect the filesystem header information, or rearrange the starting and ending blocks of a partition by using the Solaris format() command. The user can read the format() function in the Sun manuals for further details on filesystems. ANR7831E (Solaris) raw partition name has an existing filesystem. Explanation: The RAW partition specified has an 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. 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. Explanation: The RAW partition specified has an 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. ANR7833S The process 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: None. 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. User Response: Have the user specify the actual file, where the file is not a symbolic link. Using ls -l, one can see if the file is a symbolic link. ANR7833E (Solaris) symbolic links has too many symbolic links - the server only supports a maximum of 10. Explanation: The file specified has too many symbolic links. The server will follow at most 10 links before ending this symbolic link name resolution. System Action: Disallow access to this file User Response: Have the user specify the actual file, where the file is not a symbolic link. Using ls -l, one can see if the file is a symbolic link.
Explanation: The process has ended with the indicated exit code. This error is due to the problem caused and indicated by a preceding message. System Action: The server completes termination processing. User Response: None. ANR7832E (Linux) raw partition name corresponds to a protected filesystem, such as / or /usr. Explanation: The RAW partition specified has an 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.
468
IBM Tivoli Storage Manager: Messages
ANR7834I ANR7837S
ANR7834I The thread thread ID terminated in response to external signal. 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. System Action: Disallow access to this raw partition. 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. System Action: Disallow access to this raw partition. User Response: Have the system administrator change the starting cylinder of this partition to a number greater than 0. ANR7834E (Solaris) Specified raw partition name raw partition cannot contain the 0th disk cylinder. Explanation: The raw partition specified has the 0th disk cylinder. The server should not be allowed to write into the 0th cylinder. It allowed, the disk label would be corrupted. System Action: Disallow access to this raw partition User Response: Have the system administrator change the starting cylinder of this partition to a number greater than 0. ANR7834I (Windows) The server thread thread ID (tid Windows NT thread ID) terminated in response to external signal. Explanation: The thread has terminated due to an external signal. System Action: The server completes termination processing. User Response: None. ANR7835I The server thread thread ID terminated in response to server shutdown. User Response: Have the system administrator change 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 system that is at Solaris 2.6 or above, the limit is 1TB. System Action: Disallow access to this raw partition User Response: Have the system administrator change 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. System Action: The server completes termination processing. User Response: None. ANR7836S Server initialization terminated.
Explanation: The thread has ended due to an external signal. System Action: The server completes termination processing. User Response: None.
Explanation: An error occurs that causes server initialization to end. System Action: Server operation stops. User Response: Contact your service representative. ANR7837S Internal error internal error detected.
Explanation: The thread has ended due to a server shutdown. System Action: The server completes termination processing. User Response: None.
Explanation: An internal error is detected during server initialization or operation. System Action: Server operation stops. User Response: Contact your service representative.
Chapter 3. Common and Platform Specfic Messages
469
ANR7837S (Windows) ANR7843W (Windows)
The user needs to extend the log file with dsmserv extend log logname size when he gets ANR7837S, LOGSEG871 errors. ANR7837S (Windows) Internal error The internal error that was detected. detected. Explanation: An internal error was detected during server initialization or operation. System Action: Server operation will halt. User Response: Contact your service representative. The user needs to extend the log file with dsmserv extend log logname size when he gets ANR7837S, LOGSEG871 errors. ANR7838S Server operation terminated. ANR7843W (HP-UX) 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 routines used to obtain this information returned a failing return code 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. Explanation: The server checks the amount of real memory in the system to optimize use of storage in the database buffer pool. The server uses Object Data Manager (ODM) to determine how much real memory is installed on the system. The routine s used to call ODM failed or were unable to return the real memory size. System Action: Server operation continues. The server allows the data base buffer pool size to grow withoug taking into account real memory. User Response: The server may need to run as a root user to obtain this information. ANR7843W (Solaris) 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 routines used to obtain this information returned a failing return code 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 (Windows) 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 routines used to obtain this information returned a failing return code 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
Explanation: An error occurs that causes server operation to stop. System Action: Server operation stops. User Response: Contact your service representative. ANR7841S Insufficient kernel memory available.
Explanation: An error occurs due to insufficient kernel memory. System Action: Server operation stops. User Response: Contact your service representative. ANR7842S Monitor kernel extension not initialized.
Explanation: The monitor kernel extension is not initialized. System Action: Server operation stops. User Response: Contact your service representative. 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.
470
IBM Tivoli Storage Manager: Messages
ANR7849I ANR7860W (Linux)
user to obtain this information. ANR7849I Server operation terminated - kernel extension has been reset. 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. System Action: Server operation continues. User Response: None. 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. System Action: Server operation continues. User Response: None. ANR7860W ANR7851S Error resetting handler for signal signal number (signal name). Insufficient Space Available for file file name.
Explanation: The kernel extension has been reinitialized by the server in response to a previous condition for which a message has been issued. System Action: Server operation stops. User Response: None. ANR7850I The process process ID has terminated on signal signal number (signal name).
Explanation: The specified process has ended due to the specified signal. System Action: Server operation stops. User Response: Contact your service representative.
Explanation: An error occurs resetting the specified signal handler. System Action: Server operation stops. User Response: Contact your service representative. ANR7852I (Windows) The current process affinity mask is: 0xThe process affinity mask.. Explanation: The server is running on the processors indicated by the mask. System Action: Server operation continues. User Response: None. 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. System Action: Server operation continues. User Response: None. 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. System Action: Server operation continues. User Response: None.
Explanation: The server was attempting to create a file with the indicated name. There was insufficient space for the file in the filesystem. System Action: The server continues processing. The file creation request fails. User Response: Specify a file name in a filesystem with sufficient space or change the space request to a value consistent with the filesystem. ANR7860W (HP-UX) Insufficient Space Available for file file name. Explanation: The server was attempting to create a file with the indicated name. There was insufficient space for the file in the filesystem. System Action: The server continues processing. The file creation request fails. User Response: Specify a file name in a filesystem with sufficient space or change the space request to a value consistent with the filesystem. ANR7860W (Linux) Insufficient Space Available for file file name. Explanation: The server was attempting to create a file with the indicated name. There was insufficient space for the file in the filesystem. System Action: The server continues processing. The file creation request fails. User Response: Specify a file name in a filesystem with sufficient space or change the space request to a value consistent with the filesystem.
Chapter 3. Common and Platform Specfic Messages
471
ANR7860W (Solaris) ANR7863W
ANR7860W (Solaris) Insufficient Space Available for file file name. Explanation: The server was attempting to create a file with the indicated name. There was insufficient space for the file in the filesystem. System Action: The server continues processing. The file creation request fails. User Response: Specify a file name in a filesystem with sufficient space or change the space request to a value consistent with the filesystem. ANR7861W Unable to create directory when creating volume file name. User Response: Specify a file name in an existing directory or or change the name request to specify a different directory name. ANR7862W File Already exists when creating volume file name.
Explanation: The server was attempting to create a file with the indicated name. The file already exists. System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. The server will not use an existing file name when creating a file. ANR7862W (HP-UX) File Already exists when creating volume file name. Explanation: The server was attempting to create a file with the indicated name. The file already exists. System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. The server will not use an existing file name when creating a file. ANR7862W (Linux) File Already exists when creating volume file name. Explanation: The server was attempting to create a file with the indicated name. The file already exists. System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. The server will not use an existing file name when creating a file. ANR7862W (Solaris) File Already exists when creating volume file name. Explanation: The server was attempting to create a file with the indicated name. The file already exists. System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. The server will not use an existing file name when creating a file. ANR7863W Unable to create file file name.
Explanation: The server was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed. System Action: The server continues processing. The file creation request fails. User Response: Specify a file name in an existing directory or or change the name request to specify a different directory name. ANR7861W (HP-UX) Unable to create directory when creating volume file name. Explanation: The server was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed. System Action: The server continues processing. The file creation request fails. User Response: Specify a file name in an existing directory or or change the name request to specify a different directory name. ANR7861W (Linux) Unable to create directory when creating volume file name. Explanation: The server was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed. System Action: The server continues processing. The file creation request fails. User Response: Specify a file name in an existing directory or or change the name request to specify a different directory name. ANR7861W (Solaris) Unable to create directory when creating volume file name. Explanation: The server was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed. System Action: The server continues processing. The file creation request fails.
Explanation: The server was attempting to create a file 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.
472
IBM Tivoli Storage Manager: Messages
ANR7863W (HP-UX) ANR7865W (Linux)
ANR7863W (HP-UX) Unable to create file file name. Explanation: The server was attempting to create a file 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. ANR7863W (Linux) Unable to create file file name. Explanation: The server was attempting to create a file 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. ANR7863W (Solaris) Unable to create file file name. Explanation: The server was attempting to create a file 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. ANR7864W Unable to write volume file name. ANR7864W (Linux) Unable to write volume file name. Explanation: The server was attempting to create a file with the indicated name. The server was able to partially write to the file before running out of space. System Action: The server continues processing. The file creation request fails. The file is still present on the system. User Response: Specify a new file name where there is sufficient space. ANR7864W (Solaris) Unable to write volume file name. Explanation: The server was attempting to create a file with the indicated name. The server was able to partially write to the file before running out of space. System Action: The server continues processing. The file creation request fails. The file is still present on the system. User Response: Specify a new file name where there is sufficient space. ANR7865W Unable to create volume file name. Return code=return code.
Explanation: The server was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is an the server internal code. System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. The return code may also be provided to your service representative for interpretation. ANR7865W (HP-UX) Unable to create volume file name. Return code=return code. Explanation: The server was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is a server internal code. System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. The return code may also be provided to your service representative for interpretation. ANR7865W (Linux) Unable to create volume file name. Return code=return code. Explanation: The server was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is an internal code from the server.
Chapter 3. Common and Platform Specfic Messages
Explanation: The server was attempting to create a file with the indicated name. The server was able to partially write to the file before running out of space. System Action: The server continues processing. The file creation request fails. The file is still present on the system. User Response: Specify a new file name where there is sufficient space. ANR7864W (HP-UX) Unable to write volume file name. Explanation: The server was attempting to create a file with the indicated name. The server was able to partially write to the file before running out of space. System Action: The server continues processing. The file creation request fails. The file is still present on the system. User Response: Specify a new file name where there is sufficient space.
473
ANR7865W (Solaris) ANR8190I
System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. The return code may also be provided to your service representative for interpretation. ANR7865W (Solaris) Unable to create volume file name. Return code=return code. Explanation: The server was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is a server internal code. System Action: The server continues processing. The file creation request fails. User Response: Specify a new file name. The return code may also be provided to your service representative for interpretation. ANR7866W Creation of Volume file name failed. Process was cancelled. ANR7866W (Solaris) Creation of Volume file name failed. Process was cancelled. Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command. System Action: The server continues processing. The file creation request fails. User Response: The DEFINE command may be re-entered. 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 real memory is installed on the system. The routine used to initialize an ODM query failed. ODM returned an error message as indicated. System Action: Server operation continues. The server makes assumptions concerning information it could not obtain. User Response: The server may need to run as a root user to obtain this information. ANR7871W Unable to complete odm query. Error message from odm is odm message.
Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command. System Action: The server continues processing. The file creation request fails. User Response: The DEFINE command may be re-entered. ANR7866W (HP-UX) Creation of Volume file name failed. Process was cancelled. Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command. System Action: The server continues processing. The file creation request fails. User Response: The DEFINE command may be re-entered. ANR7866W (Linux) Creation of Volume file name failed. Process was cancelled. Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command. System Action: The server continues processing. The file creation request fails. User Response: The DEFINE command may be re-entered.
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. System Action: Server operation continues. The server makes assumptions concerning information it could not obtain. User Response: The server may need to run as a root user to obtain this information. ANR8190I 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. System Action: Server operation continues. User Response: None.
474
IBM Tivoli Storage Manager: Messages
ANR8190I (HP-UX) ANR8191W (Solaris)
ANR8190I (HP-UX) 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. System Action: Server operation continues. User Response: None. 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. System Action: Server operation continues. User Response: None. ANR8190I (Solaris) 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. System Action: Server operation continues. User Response: None. ANR8191W HTTP driver unable to initialize due to error in using port port, reason code reason code. ANR8191W (HP-UX) 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. System Action: Server operation continues, but the 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 sever, wait one minute, and then restart the server. If that does not work, it may be necessary to restart HP-UX. ANR8191W (Linux) 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. System Action: Server operation continues, but the 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 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 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. ANR8191W (Solaris) HTTP driver unable to initialize due to error in BINDing to 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. System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTP protocol.
Chapter 3. Common and Platform Specfic Messages
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. System Action: Server operation continues, but the 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.
475
ANR8192I (HP-UX) ANR8193W (Solaris)
User Response: Ensure that no other application is using the port number specified in the server options 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 connection with clients on port port number. Explanation: The server is now able to accept sessions with clients that use the HTTPS protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8192I (Linux) HTTPS driver ready for connection with clients on port port number. Explanation: The server is now able to accept sessions with clients that use the HTTPS protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8192I (Solaris) HTTPS driver ready for connection with clients on port port number. Explanation: The server is now able to accept sessions with clients that use the HTTPS protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8193W (HP-UX) HTTPS driver unable to initialize due to error in using Port port, reason code reason code. 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. System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol. User Response: Ensure that no other application is using the port number specified in the server options file with the HTTPSPORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTPS communications. 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 HP-UX. ANR8193W (Linux) HTTPS driver unable to initialize due to error in using port port, reason code reason code. 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. System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol. User Response: Ensure that no other application is using the port number specified in the server options file with the HTTPSPORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTPS communications. 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 Solaris ANR8193W (Solaris) HTTPS driver unable to initialize due to error in BINDing to Port port, reason code reason code. 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. System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol. User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTPS communications. 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
476
IBM Tivoli Storage Manager: Messages
ANR8194W (HP-UX) ANR8201E (Linux)
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. Explanation: While initializing HTTPS communications, the server has failed initialize of the secure data certificate information. System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol. 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. ANR8200I TCP/IP driver ready for connection with clients on port port number. User Response: None. ANR8200I (Windows) TCP/IP driver ready for connection with clients on port port number. Explanation: The server can now accept sessions with clients using the TCP/IP protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8201W Unable to initialize TCP/IP driver insufficient memory.
Explanation: Because the operating system rejects a memory allocation request, the server cannot start communications through TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. User Response: Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file. 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. System Action: Server operation continues, but 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. Explanation: The server is unable to initialize the TCP/IP driver due to a socket creation error. System Action: Server operation continues, but 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.
Explanation: The server is now able to accept sessions with clients that use the TCP/IP protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8200I (HP-UX) TCP/IP driver ready for connection with clients on port port number. Explanation: The server is now able to accept sessions with clients using the TCP/IP protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8200I (Linux) TCP/IP driver ready for connection with clients on port port number. Explanation: The server is now able to accept sessions with clients using the TCP/IP protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8200I (Solaris) TCP/IP driver ready for connection with clients on port port number. Explanation: The server is now able to accept sessions with clients using the TCP/IP protocol on the indicated port number. System Action: Server operation continues.
Chapter 3. Common and Platform Specfic Messages
477
ANR8201E (Solaris) ANR8202W (Windows)
ANR8201E (Solaris) 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. System Action: Server operation continues, but 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. 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. System Action: Server operation continues, but the server cannot accept sessions from clients using the 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. 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. 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. Explanation: The server is unable to initialize the TCP/IP driver due to a socket binding error. System Action: Server operation continues, but 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. 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. Make sure TCPPORT and HTTPORT and TCPADMINPORT do not specify or default to the same values. ANR8202E (Solaris) Unable to initialize TCP/IP driver - socket bind operation for port TCP port number failed; error error code. Explanation: The server is unable to initialize the TCP/IP driver due to a socket binding error. System Action: Server operation continues, but 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. 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. ANR8202W (Windows) Unable to initialize TCP/IP driver - error creating acceptor socket. 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. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. 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 started,
Explanation: Because TCP/IP rejects a request for a socket on which to listen, the server cannot start communications through TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. 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 started, use the HALT command from a server prompt to stop the server and restart it. ANR8202E (HP-UX) Unable to initialize TCP/IP driver - socket bind operation for port TCP port number failed; error error code. Explanation: The server is unable to initialize the TCP/IP driver due to a socket binding error. System Action: Server operation continues, but TCP/IP support is inoperative. User Response: Ensure that TCP/IP is operational on your system by using the ping command with your
478
IBM Tivoli Storage Manager: Messages
ANR8203W ANR8204E (Linux)
issue the HALT command to stop the server, and then restart the server. ANR8203W Unable to establish TCP connection accept error. your system, you must activate it; then halt and restart the server. ANR8203W (Windows) Unable to establish TCP connection - accept error. Explanation: The server cannot accept a client session due to failure in TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. 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 started, issue the HALT command to stop the server, and then restart the server. ANR8204W Unable to establish TCP connection insufficient memory.
Explanation: The server cannot accept a client session due to a failure in TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. 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 started, use the HALT command from a server prompt to terminate the server and restart it. ANR8203E (HP-UX) Unable to initialize TCP/IP driver - listen operation failed; error error code. Explanation: The server is unable to initialize the TCP/IP driver due to a socket listen error. System Action: Server operation continues, but 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. ANR8203E (Linux) Unable to initialize TCP/IP driver - listen operation failed; error error code. Explanation: The server is unable to initialize the TCP/IP driver due to a socket listen error. System Action: Server operation continues, but 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. ANR8203E (Solaris) Unable to initialize TCP/IP driver - listen operation failed; error error code. Explanation: The server is unable to initialize the TCP/IP driver due to a socket listen error. System Action: Server operation continues, but 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
Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues, but the session request for this session fails. User Response: Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8204E (HP-UX) Unable to initialize TCP/IP driver - thread creation failed. Explanation: The server is unable to initialize the TCP/IP driver due to an error creating a server thread. System Action: Server operation continues, but TCP/IP support is inoperative. User Response: This error often results from a lack of memory. Ensure that your system has sufficient paging space to support the current activities. ANR8204E (Linux) Unable to initialize TCP/IP driver - thread creation failed. Explanation: The server is unable to initialize the TCP/IP driver due to an error creating a server thread. System Action: Server operation continues, but TCP/IP support is inoperative. User Response: This error often results from a lack of memory. Ensure that your system has sufficient paging space to support the current activities.
Chapter 3. Common and Platform Specfic Messages
479
ANR8204E (Solaris) ANR8206E (HP-UX)
ANR8204E (Solaris) Unable to initialize TCP/IP driver - thread creation failed. Explanation: The server is unable to initialize the TCP/IP driver due to an error creating a server thread. System Action: Server operation continues, but TCP/IP support is inoperative. User Response: This error often results from a lack of memory. Ensure that your system has sufficient paging space to support the current activities. ANR8204W (Windows) Unable to establish TCP connection - insufficient memory. Explanation: The server is unable to accept a client session due to a memory allocation request failure. System Action: Server operation continues, but the session request for this session fails. 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. 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. System Action: Server operation continues, but 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. ANR8205E (Solaris) Terminating TCP/IP driver socket accept operation failed; error error code. Explanation: The server is unable to initialize the TCP/IP driver due to a socket accept error. System Action: Server operation continues, but 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. ANR8205W (Windows) Unable to establish TCP connection - server HALT in progress. Explanation: The server is unable to accept a client session due to server HALT processing that is in progress. System Action: Server operation continues, but the session request for this session fails. User Response: None. ANR8206W Socket socket (session session number) closed abruptly.
Explanation: The server cannot accept a client session due to server HALT processing that is in progress. System Action: Server operation continues, but the session request for this session fails. User Response: None. ANR8205E (HP-UX) Terminating TCP/IP driver accept operation failed; error error code. Explanation: The server is unable to initialize the TCP/IP driver due to a socket accept error. System Action: Server operation continues, but 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. ANR8205E (Linux) Terminating TCP/IP driver socket accept operation failed; error error code. Explanation: The server is unable to initialize the TCP/IP driver due to a socket accept error.
Explanation: The server detects that the indicated session on the specified TCP/IP socket is closed outside of the server. System Action: Server operation continues, but the session is ended. User Response: None. 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. System Action: Server operation continues. 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.
480
IBM Tivoli Storage Manager: Messages
ANR8206E (Linux) ANR8208W
ANR8206E (Linux) 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. System Action: Server operation continues. 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 (Solaris) 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. System Action: Server operation continues. 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. ANR8206I (Windows) TCP/IP administrative driver ready for connection with clients on port port number. Explanation: The server can now accept sessions with administrative clients using the TCP/IP protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8207W TCP/IP driver unable to initialize due to socket initialization error. ANR8207E (HP-UX) Unable to establish TCP/IP session with IP host address due to memory shortage. Explanation: The server is unable to establish a session because of a memory shortage condition. System Action: Server operation continues. User Response: Ensure that your system has sufficient paging space to support the current level of system activities. ANR8207E (Linux) Unable to establish TCP/IP session with IP host address due to memory shortage. Explanation: The server is unable to establish a session because of a memory shortage condition. System Action: Server operation continues. User Response: Ensure that your system has sufficient paging space to support the current level of system activities. ANR8207E (Solaris) Unable to establish TCP/IP session with IP host address due to memory shortage. Explanation: The server is unable to establish a session because of a memory shortage condition. System Action: Server operation continues. User Response: Ensure that your system has sufficient paging space to support the current level of system activities. ANR8207W (Windows) TCP/IP driver unable to initialize due to socket initialization error. Explanation: While initializing TCP/IP communications, the server has failed to set up an interface with TCP/IP for Windows. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. User Response: Ensure that TCP/IP is properly installed on your system. Ensure that TCP/IP has been started on your system. Issue the TCP/IP ping command to your own address to verify that TCP/IP is both installed and active. ANR8208W TCP/IP driver unable to initialize due to error in using port port, reason code reason code.
Explanation: While initializing TCP/IP communications, the server fails to set up an interface with TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. User Response: Ensure that TCP/IP has been started and is active on your system. You may issue the TCP/IP ping command to your own address to verify that TCP/IP is both started and active.
Explanation: While initializing TCP/IP communications, the server fails to connect to a master socket on which to listen for clients. The reason code is
Chapter 3. Common and Platform Specfic Messages
481
ANR8208E (HP-UX) ANR8209E (HP-UX)
the return code from the TCP/IP bind API. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. User Response: Ensure that no other application is using the port number specified in the server options 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 specified for both TCP/IP and HTTP communications. If the server was brought down and client sessions were active, it may be necessary to terminate the client sessions on the client systems before the port can be freed. ANR8208E (HP-UX) Unable to establish TCP/IP session with IP host address - socket creation failed; error error code. Explanation: The server is unable to establish a session because of a socket creation error. System Action: Server operation continues. 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. ANR8208E (Linux) Unable to establish TCP/IP session with IP host address - socket creation failed; error error code. Explanation: The server is unable to establish a session because of a socket creation error. System Action: Server operation continues. 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. ANR8208E (Solaris) Unable to establish TCP/IP session with IP host address - socket creation failed; error error code. Explanation: The server is unable to establish a session because of a socket creation error. System Action: Server operation continues. 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. ANR8208W (Windows) TCP/IP driver unable to initialize due to error in using Port port, reason code reason code. Explanation: While initializing TCP/IP communications, the server has failed to connect to a master socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. User Response: Ensure that no other application is using the port number specified in the server options file with the TCPPORT option. 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. 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. ANR8209W TCP/IP driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code.
Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API. System Action: Server operation continues, but the 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. ANR8209E (HP-UX) Unable to establish TCP/IP session with IP host address - connection refused. Explanation: The server is unable to establish a session because the remote system refused the connection request. System Action: Server operation continues. 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.
482
IBM Tivoli Storage Manager: Messages
ANR8209E (Linux) ANR8210E (Solaris)
ANR8209E (Linux) Unable to establish TCP/IP session with IP host address - connection refused. Explanation: The server is unable to establish a session because the remote system refused the connection request. System Action: Server operation continues. 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. ANR8209E (Solaris) Unable to establish TCP/IP session with IP host address - connection refused. Explanation: The server is unable to establish a session because the remote system refused the connection request. System Action: Server operation continues. 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. ANR8209W (Windows) TCP/IP driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code. Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the TCP/IP protocol. User Response: Ensure that TCP/IP is running 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. User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start. ANR8210E (HP-UX) Unable to establish TCP/IP session with IP host address - connection request timed out. Explanation: The server is unable to establish a session because the remote system did not respond to the connection request. System Action: Server operation continues. User Response: Ensure the following: v The specified remote system is operational and is properly configured to run TCP/IP. v The client options file specifies the correct TCPServeraddress and TCPPort of the server you are attempting to contact. v Necessary gateways and routers are functioning properly. ANR8210E (Linux) Unable to establish TCP/IP session with IP host address - connection request timed out. Explanation: The server is unable to establish a session because the remote system did not respond to the connection request. System Action: Server operation continues. User Response: Ensure the following: v The specified remote system is operational and is properly configured to run TCP/IP. v The client options file specifies the correct TCPServeraddress and TCPPort of the server you are attempting to contact. v Necessary gateways and routers are functioning properly. ANR8210E (Solaris) Unable to establish TCP/IP session with IP host address - connection request timed out. Explanation: The server is unable to establish a session because the remote system did not respond to the connection request. System Action: Server operation continues. User Response: Ensure the following: v The specified remote system is operational and is properly configured to run TCP/IP. v The client options file specifies the correct TCPServeraddress and TCPPort of the server you are attempting to contact.
Explanation: While attempting to accept a session request from a client using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the TCP/IP protocol.
Chapter 3. Common and Platform Specfic Messages
483
ANR8210W (Windows) ANR8212E (HP-UX)
v Necessary gateways and routers are functioning properly. ANR8210W (Windows) 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 error. The reason code is the return code from the TCP/IP accept API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the TCP/IP protocol. User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start. ANR8211W TCP/IP driver is terminating due to error in creating a new thread. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Also, ensure that necessary gateways and routers are functioning properly. ANR8211E (Solaris) Unable to establish TCP/IP session with IP host address system/network unreachable. Explanation: The server is unable to establish a session because the remote system or network is unreachable. System Action: Server operation continues. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Also, ensure that necessary gateways and routers are functioning properly. ANR8211W (Windows) TCP/IP driver is terminating due to error in creating a new thread. Explanation: The server cannot initialize due its inability to create a new thread of execution. System Action: Server operation continues, but TCP/IP communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8212W Unable to resolve address for node name.
Explanation: The server cannot initialize due to the inability to create a new thread of execution. System Action: Server operation continues, but TCP/IP communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8211E (HP-UX) Unable to establish TCP/IP session with IP host address system/network unreachable. Explanation: The server is unable to establish a session because the remote system or network is unreachable. System Action: Server operation continues. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Also, ensure that necessary gateways and routers are functioning properly. ANR8211E (Linux) Unable to establish TCP/IP session with IP host address system/network unreachable. Explanation: The server is unable to establish a session because the remote system or network is unreachable. System Action: Server operation continues.
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. ANR8212E (HP-UX) Unable to establish TCP/IP session with IP host address - connect failed; error error code. Explanation: The server is unable to establish a session because of a connection error. System Action: Server operation continues. User Response: Ensure that the specified remote
484
IBM Tivoli Storage Manager: Messages
ANR8212E (Linux) ANR8214E
system is operational and is properly configured to run TCP/IP. ANR8212E (Linux) Unable to establish TCP/IP session with IP host address - connect failed; error error code. Explanation: The server is unable to establish a session because of a connection error. System Action: Server operation continues. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. ANR8212E (Solaris) Unable to establish TCP/IP session with IP host address - connect failed; error error code. Explanation: The server is unable to establish a session because of a connection error. System Action: Server operation continues. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. ANR8212W (Windows) Unable to resolve address for node name. Explanation: The server attempts to obtain a TCP/IP address for the indicated node name. The attempt is 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. ANR8213W Session open with node name timed out. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. ANR8213E (Linux) Session Session identifier aborted due to send error; error error code. Explanation: The session between the server and the specified client system experienced a fatal error sending data. System Action: The session with the remote system is ended. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. ANR8213E (Solaris) Session Session identifier aborted due to send error; error error code. Explanation: The session between the server and the specified client system experienced a fatal error sending data. System Action: The session with the remote system is ended. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. ANR8213W (Windows) Session open with node name timed out. Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful. System Action: The attempt to communicate with the indicated node fails. 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. ANR8214E Session open with IP host address failed due to connection refusal.
Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful. System Action: The attempt to communicate with the indicated node fails. 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. 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.
Explanation: The server is unable to establish a session because the remote system refused the connection request. System Action: Server operation continues. 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.
Chapter 3. Common and Platform Specfic Messages
485
ANR8214E (HP-UX) ANR8215W (Windows)
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. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite. ANR8214E (Linux) Session terminated when no data was read on socket socket number. Explanation: The server is unable to read data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite. ANR8214E (Solaris) Session terminated when no data was read on socket socket number. Explanation: The server is unable to read data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite. ANR8214E (Windows) Session open with IP host address failed due to connection refusal. Explanation: The server is unable to establish a session because the remote system refused the connection request. System Action: Server operation continues. 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. ANR8215W Session open with IP host address failed as unreachable.
Explanation: The server is unable to establish a session because the remote system is unreachable. System Action: Server operation continues. User Response: Ensure that the IP host address is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose. ANR8215E (HP-UX) Session Session identifier aborted due to receive error; error error code. Explanation: The session between the server and the specified client system experienced a disruptive error receiving data. System Action: The session with the remote system is ended. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. ANR8215E (Linux) Session Session identifier aborted due to receive error; error error code. Explanation: The session between the server and the specified client system experienced a fatal error receiving data. System Action: The session with the remote system is ended. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. ANR8215E (Solaris) Session Session identifier aborted due to receive error; error error code. Explanation: The session between the server and the specified client system experienced a fatal error receiving data. System Action: The session with the remote system is ended. User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. ANR8215W (Windows) Session open with IP host address failed as unreachable. Explanation: The server is unable to establish a session because the remote system is unreachable. System Action: Server operation continues.
486
IBM Tivoli Storage Manager: Messages
ANR8216W ANR8217W (Linux)
User Response: Ensure that the IP host address is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose. ANR8216W Error sending data on socket socket number. Reason return code. ANR8216W (Windows) Error sending data on socket socket number. Reason return code. Explanation: The server experiences an error return code from TCP/IP while sending data over the indicated socket. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of 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. ANR8217W Error receiving data on socket socket number. Reason return code.
Explanation: The server experiences an error return code from TCP/IP while sending data over the indicated socket. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of 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. ANR8216E (HP-UX) Unable to establish TCP/IP session with IP host address due to thread creation error. Explanation: The server is unable to establish a session because of an error creating a thread. System Action: Server operation continues. User Response: Ensure that your system has sufficient paging space to support the current level of system activities. ANR8216E (Linux) Unable to establish TCP/IP session with IP host address due to thread creation error. Explanation: The server is unable to establish a session because of an error creating a thread. System Action: Server operation continues. User Response: Ensure that your system has sufficient paging space to support the current level of system activities. ANR8216E (Solaris) Unable to establish TCP/IP session with IP host address due to thread creation error. Explanation: The server is unable to establish a session because of an error creating a thread. System Action: Server operation continues. User Response: Ensure that your system has sufficient paging space to support the current level of system activities.
Explanation: The server experiences an error return code from TCP/IP while receiving data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of 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. ANR8217W (HP-UX) TCP/IP driver is unable to set the window size to TCPWindowsize for client client. The default value will be used. Explanation: The server cannot set the window size for the indicated client to the requested size shown. The server uses the default window size for the indicated session. There may be a lack of memory for TCP/IP buffers. System Action: Server operation continues and the 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 driver - insufficient memory. Explanation: Because the operating system rejects a memory allocation request, the server cannot start communications through TCP/IP. System Action: Server operation continues, but the
Chapter 3. Common and Platform Specfic Messages
487
ANR8217W (Solaris) ANR8218W (Windows)
server cannot accept sessions from clients using the TCP/IP protocol. User Response: Ensure that sufficient paging space is 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 maximum number of client sessions by changing the MAXSESSIONS option in the server options file. ANR8217W (Solaris) Unable to initialize TCP/IP driver - insufficient memory. Explanation: Because the operating system rejects a memory allocation request, the server cannot start communications through TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. User Response: Ensure that sufficient paging space is 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 maximum number of client sessions by changing the MAXSESSIONS option in the server options file. ANR8217W (Windows) Error receiving data on socket socket number. Reason return code. Explanation: The server experiences an error return code from TCP/IP while receiving data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of 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. ANR8218W Session terminated when no data was read on socket socket number. ANR8218W (HP-UX) TCP/IP driver is unable to use the TCP/IP NODELAY option for client client. Explanation: The server cannot set TCP/IP NODELAY for the indicated client. The session proceeds with TCP/IP Delay processing in effect. This causes TCP/IP to buffer data prior to sending it to clients. System Action: Server operation continues and the session continues with the delay processing on. User Response: Further details for use in contacting your service representative can be obtained by issuing the following trace commands from an administrative session or from the server console (proper administrative authority is required): TRACE ENABLE TCPINFO TRACE BEGIN tcptrace.out. After a session starts and displays message ANR8218W, issue the following commands: TRACE FLUSH TRACE END. This will create trace data in file tcptrace.out and will terminate the trace. This file should be supplied to your server representative on request. ANR8218W (Linux) Unable to resolve address for node name. 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. ANR8218W (Solaris) Unable to resolve address for node name. Explanation: The server attempts to obtain a TCP/IP address for the indicated node name. The attempt is 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. 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. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no
Explanation: The server is unable to read data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of 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.
488
IBM Tivoli Storage Manager: Messages
ANR8219W ANR8220W (HP-UX)
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. 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. ANR8219W (Solaris) Unable to establish TCP connection - insufficient memory. Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues, but the session request for this session fails. User Response: Ensure that sufficient paging space is 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 the server options file. ANR8219W (Windows) TCP/IP driver is unable to accept a new session due to error in creating a new thread. Explanation: The server cannot accept a client session due to the inability to create a new thread. System Action: Server operation continues, the session request fails. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8220W 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 accept a client session with the client at the indicated address due to an inability to create a new thread. System Action: Server operation continues, the session request fails. User Response: The most likely cause is lack of memory. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8219W (HP-UX) Unable to initialize TCP/IP driver - insufficient memory. Explanation: Because the operating system rejects a memory allocation request, the server cannot start communications through TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol. User Response: Ensure that sufficient paging space is available for HP-UX. You may also use SMIT to determine if the number of applications is causing a memory shortage. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file. ANR8219W (Linux) Unable to establish TCP connection - insufficient memory. Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues, but the session request for this session fails. User Response: Ensure that sufficient paging space is 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 the server options file.
Explanation: The server cannot set the window size for the indicated client to the requested size shown. The server uses the default window size for the indicated session. There may be a lack of memory for TCP/IP buffers. 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. ANR8220W (HP-UX) Unable to establish TCP connection - insufficient memory. Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues, but the session request for this session fails.
Chapter 3. Common and Platform Specfic Messages
489
ANR8220W (Linux) ANR8221W (Linux)
User Response: Ensure that sufficient paging space is available for HP-UX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8220W (Linux) TCP/IP driver is unable to set the window size to TCPWindowsize for client client. The default value will be used. Explanation: The server cannot set the window size for the indicated client to the requested size shown. The server uses the default window size for the indicated session. There may be a lack of memory for TCP/IP buffers. System Action: Server operation continues and the 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. ANR8220W (Solaris) TCP/IP driver is unable to set the window size to TCPWindowsize for client client. The default value will be used. Explanation: The server cannot set the window size for the indicated client to the requested size shown. The server uses the default window size for the indicated session. There may be a lack of memory for TCP/IP buffers. System Action: Server operation continues and the 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. ANR8220W (Windows) TCP/IP driver is unable to contact node name due to an output socket initialization error. Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful due to the inability to initialize a local socket. System Action: The attempt to communicate with the indicated node fails. User Response: Ensure that TCP/IP is operating properly on this node and that it can communicate remotely. Use the TCP/IP ping command for this purpose. ANR8221W TCP/IP driver is unable to use the TCP/IP NODELAY option for client client.
Explanation: The server cannot set TCP/IP NODELAY for the indicated client. The session proceeds with TCP/IP Delay processing in effect. This causes TCP/IP to buffer data prior to sending it to clients. System Action: Server operation continues and the session continues with the delay processing on. User Response: Further details for use in contacting your service representative can be obtained by issuing the following trace commands from an administrative session or from the server console (proper administrative authority is required): TRACE ENABLE TCPINFO TRACE BEGIN. After a session starts and displays message ANR8221W, issue the commands TRACE FLUSH TRACE END. This will create trace data in file tcptrace.out and will terminate the trace. This file should be supplied to your service representative on request. ANR8221I (HP-UX) TCP/IP administrative driver ready for connection with clients on port port number. Explanation: The server can now accept sessions with administrative clients using the TCP/IP protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8221W (Linux) TCP/IP driver is unable to use the TCP/IP NODELAY option for client client. Explanation: The server cannot set TCP/IP NODELAY for the indicated client. The session proceeds with TCP/IP delay processing in effect. This causes TCP/IP to buffer data prior to sending it to clients. System Action: Server operation continues and the 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 administrative authority is required): TRACE ENABLE TCPINFO TRACE BEGIN tcptrace.out. After a session starts and displays message ANR8221W, 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 service representative on request.
490
IBM Tivoli Storage Manager: Messages
ANR8221W (Solaris) ANR8222W (Windows)
ANR8221W (Solaris) TCP/IP driver is unable to use the TCP/IP NODELAY option for client client. Explanation: The server cannot set TCP/IP NODELAY for the indicated client. The session proceeds with TCP/IP Delay processing in effect. This causes TCP/IP to buffer data prior to sending it to clients. System Action: Server operation continues and the session continues with the delay processing on. User Response: Further details for use in contacting your service representative can be obtained by issuing the following trace commands from an administrative session or from the server console (proper administrative authority is required): TRACE ENABLE TCPINFO TRACE BEGIN tcptrace.out After a session starts and displays message ANR8221W, 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 service representative on request. ANR8221W (Windows) TCP/IP driver is unable to set the window size to TCPWindowsize for session session, client client. The default value will be used. Explanation: The server cannot set the window size for the indicated session/client to the requested size shown. The server will use the default window size for the indicated session. System Action: Server operation continues and the session continues with the default window size. User Response: The most likely cause is lack of memory for TCP/IP buffers. You may retry with a smaller TCP window size in the options file. You can issue the QUERY OPTION command to display the current setting of the TCP window size. ANR8222W TCP/IP driver is unable to set the window size to TCPWindowsize for the server master socket. The default value will be used. ANR8222W (HP-UX) The TCP/IP administrative driver was unable to initialize due to error using Port port, reason code reason code. Explanation: While initializing TCP/IP communications for administrative sessions, the server failed to connect to a master socket to listen for clients. The reason code is the return code from the TCP/IP bind API. System Action: Server operation continues, but the 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. User Response: Ensure that no other application is using the port number specified in the server options file with the TCPADMINPORT 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 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 end the client sessions on the client systems before the port can be freed. ANR8222W (Linux) Unable to establish TCP connection - server HALT in progress. Explanation: The server cannot accept a client session due to server HALT processing that is in progress. System Action: Server operation continues, but the session request for this session fails. User Response: None. ANR8222W (Solaris) Unable to establish TCP connection - server HALT in progress. Explanation: The server cannot accept a client session due to server HALT processing that is in progress. System Action: Server operation continues, but the session request for this session fails. User Response: None. ANR8222W (Windows) TCP/IP driver is unable to use the TCP/IP NODELAY option for client client. Explanation: The server cannot set TCP/IP NODELAY for the indicated client. The session proceeds with TCP/IP Delay processing in effect. This causes TCP/IP to buffer data prior to sending it to clients. System Action: Server operation continues and the session continues with the delay processing on. User Response: Further details for use in contacting your service representative can be obtained by issuing
Chapter 3. Common and Platform Specfic Messages
Explanation: The server cannot set the window size 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.
491
ANR8223W ANR8224W
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 ANR8222W, 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 service representative on request. ANR8223W Unable to connect to remote system RemoteSystem due to unexpected return code ReturnCode You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. 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. Explanation: The server cannot accept a client session with the client at the indicated address due to an inability to create a new thread. System Action: Server operation continues, the session request fails. User Response: The most likely cause is lack of memory. Ensure that sufficient paging space is available for Solaris. You may also use ps -ef to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. 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. System Action: The attempt to communicate with the indicated node fails. Server operation continues. 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.
Explanation: The server was unable to connect to a remote system due to an unexpected return code from the connect Application Programming Interface. Common return code are handled with specific messages. This return code was unexpected. System Action: Server operation continues but the connection to the remote system fails. User Response: TCP/IP return code are listed in file /usr/include/sys/errno.h and may provide a pointer to the underlying problem. /usr/include/sys/errno.h is part of fileset bos.adt.include. ANR8223W (HP-UX) The TCP/IP driver is unable to accept a new session with the client at address TCP/IP address, due to an error in creating a new thread. Explanation: The server cannot accept a client session with the client at the indicated address due to an inability to create a new thread. System Action: Server operation continues, but the 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 server can accept with the MAXSESSIONS option in the server options file. 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. Explanation: The server cannot accept a client session with the client at the indicated address due to an inability to create a new thread. System Action: Server operation continues, the session request fails. User Response: The most likely cause is lack of memory. Ensure that sufficient paging space is available for Solaris. You may also use ps -ef to determine if the number of applications is causing a memory shortage.
Explanation: While initializing TCP/IP communications for administrative sessions, the server has failed to connect to a master socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API. System Action: Server operation continues, but the server cannot accept administrative sessions from clients using the TCP/IP protocol. This also includes server to server sessions, storage agent to server sessions, and library client to server sesssions. User Response: Ensure that no other application is using the port number specified in the server options file with the TCPADMINPORT, TCPPORT, or HTTPPORT 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.
492
IBM Tivoli Storage Manager: Messages
ANR8224W (Linux) ANR8225I (Solaris)
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 the client sessions on the client systems before the port can be freed. ANR8224W (Linux) TCP/IP driver is unable to set the window size to TCPWindowsize for the server master socket. The default value will be used. Explanation: The server cannot set the window size 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. ANR8224W (Solaris) TCP/IP driver is unable to set the window size to TCPWindowsize for the server master socket. The default value will be used. Explanation: The server cannot set the window size 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. ANR8224W (Windows) TCP/IP Administrative driver was unable to initialize due to error in using Port port, reason code reason code. Explanation: While initializing TCP/IP communications for administrative sessions, the server has failed to connect to a master socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API. System Action: Server operation continues, but the server cannot accept administrative sessions from clients using the TCP/IP protocol. This also includes server to server sessions, storage agent to server sessions, and library client to server sessions. User Response: Ensure that no other application is using the port number specified in the server options file with the TCPADMINPORT option. If HTTP is also in use for client sessions, ensure that the same port
Chapter 3. Common and Platform Specfic Messages
number is not specified for both TCP/IP and HTTP 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 connection with clients on port port number.
Explanation: The server can now accept sessions with administrative clients using the TCP/IP protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8225W (Linux) TCP/IP Administrative driver was unable to initialize due to error in using port port, reason code reason code. Explanation: While initializing TCP/IP communications for administrative sessions, the server has failed to connect to a master socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API. System Action: Server operation continues, but the server cannot accept administrative sessions from clients using the TCP/IP protocol. This also includes server to server sessions, storage agent to server sessions, and library client to server sesssions. User Response: Ensure that no other application is using the port number specified in the server options file with the TCPADMINPORT, TCPPORT, or HTTPPORT 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 may be necessary to terminate the client sessions on the client systems before the port can be freed. ANR8225I (Solaris) TCP/IP administrative driver ready for connection with clients on port port number. Explanation: The server can now accept sessions with administrative clients using the TCP/IP protocol on the indicated port number. System Action: Server operation continues. User Response: None.
493
ANR8226E ANR8229W (Windows)
ANR8226E Error errno detecting version of HBA-API library. 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 Fileset devices.common.IBM.fc.hba-api is not at the required level.
Explanation: The server attempted to determine the level of the devices.common.IBM.fc.hba-api fileset and encountered an error. System Action: Server operation continues, but without accurate SAN device mapping. User Response: None. ANR8226I (Linux) TCP/IP administrative driver ready for connection with clients on port port number. Explanation: The server can now accept sessions with administrative clients using the TCP/IP protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8226W (Solaris) TCP/IP Administrative driver was unable to initialize due to error in 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. System Action: Server operation continues, but the server cannot accept administrative sessions from clients using the TCP/IP protocol. This also includes server to server sessions, storage agent to server sessions, and library client to server sesssions. System Action: Server operation continues, but the 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-server sesssions. User Response: Ensure that no other application is using the port number specified in the server options 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 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. System Action: Server operation continues, but the
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. System Action: Server operation continues, but without accurate SAN device mapping. User Response: None. 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. System Action: Server operation continues, but the sessions will not be accepted on the specified adapter. Other network adapters remain unaffected. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. ANR8228W (Windows) NETBIOS connection terminated - server HALT in progress. Explanation: The server cannot accept a client session due to server HALT processing that is in progress. System Action: Server operation continues, but the session request for this session fails. User Response: None. 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.
494
IBM Tivoli Storage Manager: Messages
ANR8230W (Windows) ANR8235W (Windows)
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 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. ANR8230W (Windows) Insufficient memory to start NETBIOS session on adapter network adapter number. Explanation: The server cannot accept a client session due to a memory allocation request failure on the specified adapter. System Action: Server operation continues, but the session request fails. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can 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. Explanation: The server cannot initialize due to the inability to create a new thread of execution. System Action: Server operation continues, but NETBIOS communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file. ANR8232W (Windows) Unable to create thread to listen for NETBIOS sessions on adapter network adapter number. Explanation: The server cannot initialize due to the inability to create a new thread of execution to monitor the indicated network adapter. System Action: Server operation continues, but NETBIOS communications is inoperative on the indicated adapter. Other adapters remain unaffected. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file. ANR8233W (Windows) Unable to create thread to 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 session request fails. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file. 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. System Action: Server operation continues, but the maximum number of NETBIOS sessions is limited to the number of sessions that are acquired.
Chapter 3. Common and Platform Specfic Messages
495
ANR8236W (Windows) ANR8264W (Windows)
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. 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. ANR8261W (Windows) Named Pipes connection terminated - insufficient memory. Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues. Named Pipes communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8262W (Windows) Named Pipes driver is terminating due to error in creating a new thread. Explanation: The server cannot initialize due to the inability to create a new thread of execution. System Action: Server operation continues, but Named Pipes communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8263W (Windows) Error sending data on Named Pipes, session session number.WriteFile Return code is return code. Explanation: The server experiences an error return 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. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8264W (Windows) Error reading data on Named Pipes, session session number. ReadFile return code is return code. Explanation: The server experiences an error return code from the ReadFile Windows API while reading
ANR8260I (Windows) Named Pipes driver ready for connection with clients. Explanation: The server is now able to accept sessions with clients using the Named Pipes protocol. System Action: Server operation continues. User Response: None.
496
IBM Tivoli Storage Manager: Messages
ANR8265W (Windows) ANR8274W (Windows)
data from Named Pipes in the indicated session. This may be a normal event if either side of the connection is ended abruptly. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8265W (Windows) Error open Named Pipes Named Pipes name, CreateNamedPipe return code return code. Explanation: The server experiences an error return 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. System Action: The session is ended. Server operation 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. Explanation: The server experiences an error return 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. System Action: The session is ended. Server operation continues. Named Pipes communications is inoperative. 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. Explanation: The server experiences an error return 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. System Action: The session is ended. Server operation continues. Named Pipes communications is inoperative. 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. Explanation: The server experiences an error return 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 specified in the server options file. System Action: The session is ended. Server operation continues. Named Pipes communications is inoperative. User Response: To use Windows unified logon specify the name of a valid Windows account or group name. Restart the server to reenable Named Pipes communications. ANR8269W (Windows) Error opening Named Pipe Named Pipes name, reason: System message. Explanation: The server experiences an error return 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. System Action: The session is ended. Server operation continues. Named Pipes communications is inoperative. User Response: Consider the reason text and take appropriate action. Stop and restart the server to reenable Named Pipes communications. ANR8273I (Windows) Shared memory driver ready for connection with clients on port port number. Explanation: The server is now able to accept sessions with clients using the shared memory protocol on the indicated port. System Action: Server operation continues. User Response: None. ANR8274W (Windows) Shared memory communications driver is terminating due to error in creating a new thread. Explanation: The server cannot initialize due to the inability to create a new thread of execution. System Action: Server operation continues, but shared memory communications is inoperative.
Chapter 3. Common and Platform Specfic Messages
497
ANR8275W (Windows) ANR8282I (Solaris)
User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. ANR8275W (Windows) Shared memory connection terminated - insufficient memory. Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues. Shared memory communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8276W (Windows) Shared memory connection terminated - unable to initialize. Key channel key, Reason: reason code. Explanation: The server cannot accept a client session due being unable to initialize shared memory. System Action: Server operation continues. Shared memory communications are inoperative. User Response: Try a different shared memory session. ANR8277E (Windows) Shared memory unable to initialize - Port: shm port number, Reason: reason code. Explanation: The server cannot accept a client session 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. System Action: Server operation continues. Shared memory communications are inoperative. User Response: Try a different shared memory session. ANR8280I (Windows) HTTP driver ready for connection with clients on port port number. Explanation: The server can now accept sessions with clients using the HTTP protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8281W (Windows) HTTP driver unable to initialize due to error in BINDing to 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. System Action: Server operation continues, but the 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 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. If that does not work, it may be necessary to restart Windows. ANR8282I (HP-UX) SNMP driver ready for connection with subagent on port port number. Explanation: The server can now accept sessions with SNMP subagents on the indicated port number. System Action: Server operation continues. User Response: None. ANR8282I (Linux) SNMP driver ready for connection with subagent on port port number. Explanation: The server can now accept sessions with SNMP subagents on the indicated port number. System Action: Server operation continues. User Response: None. ANR8282I (Solaris) SNMP driver ready for connection with subagent on port port number. Explanation: The server can now accept sessions with SNMP subagents on the indicated port number. System Action: Server operation continues. User Response: None.
498
IBM Tivoli Storage Manager: Messages
ANR8282I (Windows) ANR8284E (HP-UX)
ANR8282I (Windows) HTTPS driver ready for connection with clients on port port number. Explanation: The server can now accept sessions with clients using the HTTPS protocol on the indicated port number. System Action: Server operation continues. User Response: None. ANR8283W (HP-UX) SNMP driver unable to initialize due to error in using Port port, reason code reason code. Explanation: While initializing TCP/IP communications, the server has failed to connect to a master TCP/IP socket on which to listen to SNMP subagents. The reason code is the return code from the TCP/IP bind API. System Action: Server operation continues, but the server cannot accept sessions from SNMP subagents to run macro commands. User Response: Ensure that no other application is using the port number specified in the server options 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 communications. This may be done by issuing the TCP/IP netstat command. ANR8283W (Linux) SNMP driver unable to initialize due to error in BINDing to Port port, reason code reason code. Explanation: While initializing TCP/IP communications, the server has failed to connect to a master TCP/IP socket on which to listen to SNMP subagents. The reason code is the return code from the TCP/IP bind API. System Action: Server operation continues, but the server cannot accept sessions from SNMP subagents to run macro commands. User Response: Ensure that no other application is using the port number specified in the server options file with the 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 communications. ANR8283W (Solaris) SNMP driver unable to initialize due to error in BINDing to Port port, reason code reason code. Explanation: While initializing TCP/IP communications, the server has failed to connect to a master TCP/IP socket on which to listen to SNMP subagents. The reason code is the return code from the TCP/IP bind API. System Action: Server operation continues, but the server cannot accept sessions from SNMP subagents to run macro commands. User Response: Ensure that no other application is using the port number specified in the server options file with the 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 communications. ANR8283W (Windows) HTTPS driver unable to initialize due to error in BINDing to Port port, reason code reason code. 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. System Action: Server operation continues, but the 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 PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTPS communications. 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. 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. System Action: Server operation continues without Shared Memory Communications. User Response: Examine previous error messages for the cause of the failure. ANR8284E (HP-UX) The Shared Memory Communications Protocol could not initialize. Explanation: The server was unable to initialize the Shared Memory Communications Protocol due to an error. System Action: Server operation continues without Shared Memory Communications.
Chapter 3. Common and Platform Specfic Messages
499
ANR8284E (Linux) ANR8286W (HP-UX)
User Response: Examine previous error messages for the cause of the failure. ANR8284E (Linux) The Shared Memory Communications Protocol could not initialize. Explanation: The server was unable to initialize the Shared Memory Communications Protocol due to an error. System Action: Server operation continues without Shared Memory Communications. User Response: Examine previous error messages for the cause of the failure. ANR8284E (Solaris) The Shared Memory Communications Protocol could not initialize. Explanation: The server was unable to initialize the Shared Memory Communications Protocol due to an error. System Action: Server operation continues without Shared Memory Communications. User Response: Examine previous error messages for the cause of the failure. ANR8284W (Windows) HTTPS driver unable to initialize due to error in secure data initialization, reason code reason code. Explanation: While initializing HTTPS communications, the server has failed to initialize the secure data certificate information. System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol. 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 connection with clients on port port ANR8285I (HP-UX) Shared Memory driver ready for connection with clients on port port Explanation: The server is now able to accept sessions with clients using the Shared Memory protocol. System Action: Server operation continues. User Response: None. ANR8285I (Linux) Shared Memory driver ready for connection with clients on port port Explanation: The server is now able to accept sessions with clients using the Shared Memory protocol. System Action: Server operation continues. User Response: None. ANR8285I (Solaris) Shared Memory driver ready for connection with clients on port port Explanation: The server is now able to accept sessions with clients using the Shared Memory protocol. System Action: Server operation continues. User Response: None. ANR8285I (Windows) SNMP driver ready for connection with subagent on port port number. Explanation: The server can now accept sessions with SNMP subagents on the indicated port number. System Action: Server operation continues. User Response: None. ANR8286W Unable to initialize Shared Memory driver - insufficient memory.
Explanation: Because the operating system rejected a memory allocation request, the server cannot start communications through the Shared Memory protocol. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. User Response: Ensure that there is sufficient paging 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 maximum number of client sessions by changing the MAXSESSIONS option in the server options file. ANR8286W (HP-UX) Unable to initialize Shared Memory driver - insufficient memory. Explanation: Because the operating system rejected a memory allocation request, the server cannot start communications through the Shared Memory protocol.
Explanation: The server is now able to accept sessions with clients using the Shared Memory protocol. System Action: Server operation continues. User Response: None.
500
IBM Tivoli Storage Manager: Messages
ANR8286W (Linux) ANR8287W (Solaris)
System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. User Response: Ensure that there is sufficient paging space for HP-UX. You may also use SAM to determine if the number of applications is causing a memory shortage. 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 (Linux) Unable to initialize Shared Memory driver - insufficient memory. Explanation: Because the operating system rejected a memory allocation request, the server cannot start communications through the Shared Memory protocol. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. 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 Memory driver - insufficient memory. Explanation: Because the operating system rejected a memory allocation request, the server cannot start communications through the Shared Memory protocol. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. 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 (Windows) SNMP driver unable to initialize due to error in BINDing to Port port, reason code reason code. Explanation: While initializing TCP/IP communications, the server has failed to connect to a master TCP/IP socket on which to listen to SNMP subagents. The reason code is the return code from the TCP/IP bind API. System Action: Server operation continues, but the server cannot accept sessions from SNMP subagents to run macro commands. User Response: Ensure that no other application is using the port number specified in the server options file with the 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 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 Unable to initialize Shared Memory driver - error creating acceptor socket. Reason code reason code.
Explanation: Because TCP/IP rejected a request for a socket on which to listen, the server cannot start communications through Shared Memory. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. User Response: If TCP/IP is not started, use the HALT command from any server prompt to stop the server, and restart it. ANR8287W (HP-UX) Unable to initialize Shared Memory driver - error creating acceptor socket. Reason code reason code. Explanation: Because TCP/IP rejected a request for a socket on which to listen, the server cannot start communications through Shared Memory. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. User Response: If TCP/IP is not started, use the HALT command from any server prompt to stop the server, and restart it. ANR8287W (Linux) Unable to initialize Shared Memory driver - error creating acceptor socket. Reason code reason code. Explanation: Because TCP/IP rejected a request for a socket on which to listen, the server cannot start communications through Shared Memory. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. User Response: If TCP/IP is not started, use the HALT command from any prompt to stop the server, and restart it. ANR8287W (Solaris) Unable to initialize Shared Memory driver - error creating acceptor socket. Reason code reason code. Explanation: Because TCP/IP rejected a request for a socket on which to listen, the server cannot start communications through Shared Memory. System Action: Server operation continues, but the
Chapter 3. Common and Platform Specfic Messages
501
ANR8288W ANR8289W (Linux)
server cannot accept sessions from clients using the Shared Memory protocol. User Response: If TCP/IP is not started, use the HALT command from any server prompt to stop the server, and restart it. ANR8288W Unable to establish Shared Memory connection - insufficient memory. System Action: Server operation continues, but the session request for this session fails. User Response: Ensure that there is sufficient swap space for Solaris. 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. ANR8289W Shared Memory driver is terminating due to error in creating a new thread.
Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues, but the session request for this session fails. User Response: Ensure that there is sufficient paging 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 maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8288W (HP-UX) Unable to establish Shared Memory connection - insufficient memory. Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues, but the session request for this session fails. User Response: Ensure that there is sufficient paging space for HP-UX. You may also use SAM to determine if the number of applications is causing a memory shortage. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8288W (Linux) Unable to establish Shared Memory connection - insufficient memory. Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues, but the session request for this session fails. User Response: Ensure that there is sufficient swap space for Solaris. 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. ANR8288W (Solaris) Unable to establish Shared Memory connection - insufficient memory. Explanation: The server cannot accept a client session due to a memory allocation request failure.
Explanation: The server cannot initialize due to the inability to create a new thread of execution. System Action: Server operation continues, but Shared Memory communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient paging 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 maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8289W (HP-UX) Shared Memory driver is terminating due to error in creating a new thread. Explanation: The server cannot initialize due to the inability to create a new thread of execution. System Action: Server operation continues, but Shared Memory communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient paging space for HP-UX. You may also use SAM to determine if the number of applications is causing a memory shortage. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8289W (Linux) Shared Memory driver is terminating due to error in creating a new thread. Explanation: The server cannot initialize due to the inability to create a new thread of execution. System Action: Server operation continues, but Shared Memory communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient swap space for Solaris. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.
502
IBM Tivoli Storage Manager: Messages
ANR8289W (Solaris) ANR8291W (Linux)
ANR8289W (Solaris) Shared Memory driver is terminating due to error in creating a new thread. Explanation: The server cannot initialize due to the inability to create a new thread of execution. System Action: Server operation continues, but Shared Memory communications is inoperative. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient swap space for Solaris. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8290W Error sending data through Shared Memory. Reason return code. ANR8290W (Solaris) Error sending data through Shared Memory. Reason return code. Explanation: The server experienced an error return code while sending data through shared memory. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8290I (Windows) IPX/SPX driver ready for connection with clients on socket IPX socket number. Explanation: The server is now able to accept sessions with clients using the IPX/SPX protocol on the indicated socket number. System Action: Server operation continues. User Response: None. ANR8291W Error receiving data through Shared Memory. Reason return code.
Explanation: The server experienced an error return code while sending data through shared memory. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8290W (HP-UX) Error sending data through Shared Memory. Reason return code. Explanation: The server experienced an error return code while sending data through shared memory. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8290W (Linux) Error sending data through Shared Memory. Reason return code. Explanation: The server experienced an error return code while sending data through shared memory. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.
Explanation: The server experienced an error return code while receiving data through the Shared Memory protocol. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8291W (HP-UX) Error receiving data through Shared Memory. Reason return code. Explanation: The server experienced an error return code while receiving data through the Shared Memory protocol. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8291W (Linux) Error receiving data through Shared Memory. Reason return code. Explanation: The server experienced an error return code while receiving data through the Shared Memory protocol. This may be a normal event if either side of the connection is abruptly ended.
Chapter 3. Common and Platform Specfic Messages
503
ANR8291W (Solaris) ANR8293W
System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8291W (Solaris) Error receiving data through Shared Memory. Reason return code. Explanation: The server experienced an error return code while receiving data through the Shared Memory protocol. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. 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. System Action: Server operation continues, but 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 Session terminated when no data was read through Shared Memory. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8292W (Linux) Session terminated when no data was read through Shared Memory. Explanation: The server is unable to read data from Shared Memory. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8292W (Solaris) Session terminated when no data was read through Shared Memory. Explanation: The server is unable to read data from Shared Memory. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8292W (Windows) IPX/SPX connection terminated - insufficient memory. Explanation: The server cannot accept a client session due to a memory allocation request failure. System Action: Server operation continues. User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file. ANR8293W Shared Memory driver unable to initialize due to socket initialization error.
Explanation: The server is unable to read data from Shared Memory. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues. User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. ANR8292W (HP-UX) Session terminated when no data was read through Shared Memory. Explanation: The server is unable to read data from Shared Memory. This may be a normal event if either side of the connection is abruptly ended.
Explanation: While initializing Shared Memory communications, the server failed to set up an interface with TCP/IP. System Action: Server operation continues, but the
504
IBM Tivoli Storage Manager: Messages
ANR8293W (HP-UX) ANR8294W (Linux)
server cannot accept sessions from clients using the Shared Memory protocol. User Response: Ensure that TCP/IP has been started and is active on your system. You may issue the TCP/IP ping command to your own address to verify that TCP/IP is both started and active. ANR8293W (HP-UX) Shared Memory driver unable to initialize due to socket initialization error. Explanation: While initializing Shared Memory communications, the server failed to set up an interface with TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. User Response: Ensure that TCP/IP has been started and is active on your system. You may issue the TCP/IP ping command to your own address to verify that TCP/IP is both started and active. ANR8293W (Linux) Shared Memory driver unable to initialize due to socket initialization error. Explanation: While initializing Shared Memory communications, the server failed to set up an interface with TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. User Response: Ensure that TCP/IP has been started and is active on your system. You may issue the TCP/IP ping command to your own address to verify that TCP/IP is both started and active. ANR8293W (Solaris) Shared Memory driver unable to initialize due to socket initialization error. Explanation: While initializing Shared Memory communications, the server failed to set up an interface with TCP/IP. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. User Response: Ensure that TCP/IP has been started and is active on your system. You may issue the TCP/IP ping command to your own address to verify that TCP/IP is both started and active. ANR8293W (Windows) IPX/SPX driver unable to initialize due to error in LISTENing on the master socket, return code = return code. Explanation: While attempting to listen for session requests from clients using IPX/SPX, the server encountered an error. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the IPX/SPX protocol. 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. ANR8294W Shared Memory session unable to initialize.
Explanation: While initializing a Shared Memory communications session, an error occurred during initial setup. System Action: Server operation continues, but the session is terminated. User Response: Contact your service representative for assistance in resolving the error. ANR8294W (HP-UX) Shared Memory session unable to initialize. Explanation: While initializing a Shared Memory communications session, an error occurred during initial setup. System Action: Server operation continues, but the session is terminated. User Response: Contact your service representative for assistance in resolving the error. ANR8294W (Linux) Shared Memory session unable to initialize. Explanation: While initializing a Shared Memory communications session, an error occurred during initial setup. System Action: Server operation continues, but the session is terminated. User Response: Contact your service representative for assistance in resolving the error.
Chapter 3. Common and Platform Specfic Messages
505
ANR8294W (Solaris) ANR8295W (Windows)
ANR8294W (Solaris) Shared Memory session unable to initialize. Explanation: While initializing a Shared Memory communications session, an error occurred during initial setup. System Action: Server operation continues, but the 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. Explanation: The server cannot accept a client session due to a failure in accepting the connection from IPX/SPX. System Action: Server operation continues, but this session request fails. 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 Shared Memory driver unable to initialize due to error in BINDing to Port port, reason code reason code. server cannot accept sessions from clients using the Shared Memory protocol. 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 command. If the server was brought down and client sessions were active, it may be necessary to terminate the client sessions on the client systems before the port can be freed. ANR8295W (Linux) Shared Memory driver unable to initialize due to error in BINDing to Port port, reason code reason code. Explanation: While initializing Shared Memory communications, the server 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. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. 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 command. If the server was brought down and client sessions were active, it may be necessary to terminate the client sessions on the client systems before the port can be freed. ANR8295W (Solaris) Shared Memory driver unable to initialize due to error in BINDing to Port port, reason code reason code. Explanation: While initializing Shared Memory communications, the server 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. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. 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 command. If the server was brought down and client sessions were active, it may be necessary to terminate the client sessions on the client systems before the port can be freed. ANR8295W (Windows) Error sending data on session session number. Reason return code. Explanation: The server experiences an error return code from IPX/SPX while sending data on the indicated session. This may be a normal event if either side of the connection is abruptly ended. System Action: The session is ended. Server operation continues.
Explanation: While initializing Shared Memory communications, the server 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. System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol. 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 command. If the server was brought down and client sessions were active, it may be necessary to terminate the client sessions on the client systems before the port can be freed. ANR8295W (HP-UX) Shared Memory driver unable to initialize due to error in using Port port, reason code reason code. Explanation: While initializing Shared Memory communications, the server 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. System Action: Server operation continues, but the
506
IBM Tivoli Storage Manager: Messages
ANR8296W ANR8297W (Linux)
User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that IPX/SPX is still active. ANR8296W Shared Memory driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code. ANR8296W (Solaris) Shared Memory driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code. Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory 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. ANR8297W Shared Memory driver is terminating due to error in accepting a new session, 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. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory 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. ANR8296W (HP-UX) Shared Memory driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code. Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory 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. ANR8296W (Linux) Shared Memory driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code. Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory 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.
Explanation: While attempting to accept a session request from a client using the Shared Memory protocol, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol. User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start. ANR8297W (HP-UX) Shared Memory 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 the Shared Memory protocol, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol. User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start. ANR8297W (Linux) Shared Memory 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 the Shared Memory
Chapter 3. Common and Platform Specfic Messages
507
ANR8297W (Solaris) ANR8304E
protocol, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol. User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start. ANR8297W (Solaris) Shared Memory 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 the Shared Memory protocol, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API. System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol. User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start. 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 D in the Messages manual for recommended action. User Response: Ensure that the DEVICE parameter associated with the library was identified correctly in 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. If the problem persists, contact your service representative and provide the internal code values from this message. 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 D in the Messages manual for recommended action.
Explanation: An I/O error has occurred while operating on the designated drive. System Action: The operation fails. User Response: Ensure that the DEVICE parameter associated with the drive was identified correctly in the DEFINE PATH command, and that the device is currently powered on and ready. The drive or library reference manual provided with the device usually contain tables that explain the values of the KEY, ASC, and ASCQ fields. If the problem persists, contact your service representative and provide the internal code values and sense data from this message. 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 designated drive. System Action: The operation fails. User Response: Ensure that the DEVICE parameter associated with the drive was identified correctly in the DEFINE PATH command, and that the device is currently powered on and ready. If the problem persists, contact your service representative and provide the internal code values from this message. ANR8304E Time out error on drive drive name in library library name.
Explanation: An I/O error has occurred while operating on the designated library device. System Action: The operation fails. User Response: Ensure that the DEVICE parameter associated with the library was identified correctly in 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 drive or library reference manual provided with the device usually contain tables that explain the values of the KEY, ASC, and ASCQ fields. If the problem persists, contact your service representative and provide the internal code values and sense data from this message. ANR8301E I/O error on library library name (OP=internal code, SENSE=internal code).
Explanation: A time out condition occurred while waiting for the given drive to become ready so that automated library operations could be performed. System Action: The operation fails. User Response: Ensure that the DEVICE parameter associated with the drive was identified correctly in the DEFINE PATH command, and that the device is currently powered on and ready.
Explanation: An I/O error has occurred while operating on the designated library device. System Action: The operation fails.
508
IBM Tivoli Storage Manager: Messages
ANR8305E ANR8311E
ANR8305E Library library name is not ready or not operational. ANR8308I Request number: device type volume volume name is required for use in library library name; CHECKIN LIBVOLUME required within time limit minutes.
Explanation: The specified automated library device is either not ready or not in an operational state. 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 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. System Action: The server waits until it detects that the volume has been checked into the library, or the time limit expires. User Response: Obtain the required volume, and insert it into the library by issuing a CHECKIN LIBVOLUME command. Use the SWAP=YES option of the CHECKIN LIBVOLUME command if the library is currently full; this process allows the server to select an appropriate volume to be swapped out in order to make room for the required volume. ANR8309E Mount attempt failed - library library name is not defined.
Explanation: A CHECKIN LIBVOLUME or a LABEL LIBVOLUME command is in progress, and the specified volume is needed. The server expects the volume to be inserted into the slot with the specified element number of the given library within the time limit specified in the message. For the slot and element number diagram of your library, refer to the documentation provided with the current ptf level or refer to the 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: An attempt has been made to mount a volume, but the attempt fails because the specified library is not defined. System Action: The operation fails. 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 and retry the operation. ANR8310E An I/O error occurred while accessing library library name.
Explanation: An I/O error occurs while accessing the designated library. System Action: The operation fails. User Response: Ensure that the DEVICE parameter associated with the library is identified correctly in the DEFINE PATH command, and that the library is currently powered on and ready. If the library has an access door, make sure it is closed. After checking and correcting these potential problems, retry the operation. ANR8311E An I/O error occurred while accessing drive drive name for low-level operation operation, errno = drive errno.
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. System Action: The server waits until a REPLY 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.
Explanation: An I/O error occurs while performing the operation on the specified drive. System Action: The operation fails. User Response: Ensure that the DEVICE parameter 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
Chapter 3. Common and Platform Specfic Messages
509
ANR8312E ANR8319I
correcting these potential problems, retry the operation. ANR8312E Volume volume name could not be located in library library name. ANR8316E Selecting swap volume to be checked out of library library name.
Explanation: The designated volume cannot be found at its expected location in the given library. System Action: The operation fails. 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 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: A mount request is made for the given volume in the specified library, but the volume is not currently checked into the library. System Action: The mount operation fails. If the volume is being mounted for storage pool I/O (as opposed to import/export I/O), its ACCESS attribute is changed to UNAVAILABLE to prevent further mount requests. User Response: Issue a CHECKIN LIBVOLUME command to return the volume into the library, and update the volumes ACCESS attribute to READONLY or READWRITE using the UPDATE VOLUME command. Retry the mount request. ANR8314E Library library name is full.
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. System Action: None. User Response: Physically eject the volume from the drive. ANR8318I Request number: Mount side side of device type volume volume name mount mode in drive drive name of library library name within time limit< minutes.
Explanation: A library operation fails because all of the librarys storage locations are occupied. System Action: The operation fails. 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: 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 Request number: Insert device type volume volume name mount mode into library library name within time limit minute(s).
Explanation: Drives of the type identified in the command are not supported in the given type of library. System Action: The command is not processed. User Response: Determine whether the drive and library combination is supported by the installed level of the server. If so, contact your service representative.
Explanation: A CHECKIN LIBVOLUME command is in progress, and the specified volume is needed. The server expects the volume to be inserted into the library with the convenience I/O station mechanism. System Action: The server waits until the volume is in the library, or until the time limit expires. User Response: Insert the specified volume into the library. If the volume has already been inserted into the library, no user action is necessary.
510
IBM Tivoli Storage Manager: Messages
ANR8320I ANR8326I
ANR8320I Request number: Insert device type volume 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. ANR8323I Request number: Insert device type 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 or a LABEL LIBVOLUME command is in progress, and the 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. System Action: The server waits until a REPLY command is issued, or until the time limit expires. 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 Request number: Remove device type volume volume name from drive drive name of library library name; issue REPLY along with the request ID when ready.
Explanation: A CHECKIN LIBVOLUME or a LABEL LIBVOLUME cmmand is in progress, and the specified volume is needed. Mount the volume in the entry/exit port of the given library within the time limit specified in the message. System Action: The server waits until a REPLY command is issued, or until the time limit expires. 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. System Action: None. User Response: If the volume is stored offline, retrieve it so that it is readily accessible when the server requests that it be mounted. ANR8325I Dismounting volume volume name mount retention period minute mount retention expired.
Explanation: A CHECKOUT LIBVOLUME or a LABEL LIBVOLUME command has completed. You can remove the specified volume from the designated drive and store it outside the library. System Action: The server waits until a REPLY command is issued. User Response: Remove the volume from the drive and store it in a safe place. Issue a REPLY command, along with the request ID, to tell the server that the volume has been removed. The volume can be returned to the library with the CHECKIN LIBVOLUME command. ANR8322I Request number: Remove device type volume volume name from entry/exit port of library library name; issue REPLY along with the request ID when ready.
Explanation: The specified volume is dismounted because the given mount retention period has expired. System Action: The volume is dismounted. User Response: None. ANR8326I Request number: Mount device type volume volume name mount mode in drive drive name of library library name within time limit minutes.
Explanation: A CHECKOUT LIBVOLUME command has completed. You can remove the specified volume from the entry/exit port of the given library and store it elsewhere. System Action: The server waits until a REPLY 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.
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.
Chapter 3. Common and Platform Specfic Messages
511
ANR8327E ANR8336I
ANR8327E Command: Cannot cancel request request number. ANR8332I Device type volume volume name is mounted mount mode, status: IDLE.
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 Request number: device type volume volume name mounted in drive drive name.
Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is 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. System Action: None. User Response: None. ANR8333I Device type volume volume name is mounted mount mode, status: IN USE.
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: None. ANR8329I Device type volume volume name is 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 for I/O operations. The volume is currently in use, meaning that read or write operations, or both are being performed. System Action: None. User Response: None. ANR8334I Number of matches matches found.
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. System Action: None. User Response: None. ANR8330I Device type volume volume name is mounted mount mode in drive drive name, status: IN USE.
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. System Action: None. User Response: None. ANR8335I Request number: Verifying label of device type volume volume name in drive drive name.
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 in use, meaning that read or write operations, or both, are being performed. System Action: None. User Response: None. ANR8331I Device type volume volume name is mounted mount mode in drive drive name, status: DISMOUNTING.
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. User Response: None. ANR8336I Verifying label of device type volume volume name in drive drive name.
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 being dismounted by the server. System Action: None. User Response: None.
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. User Response: None.
512
IBM Tivoli Storage Manager: Messages
ANR8337I ANR8346I
ANR8337I Device type volume volume name mounted in drive drive name. User Response: None. ANR8342I Request request number for volume volume name canceled by administrator 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. User Response: None. ANR8338E Device type volume volume name cannot be overwritten by EXPORT operation.
Explanation: A mount request is canceled by the given administrator. System Action: The system cancels the mount request. User Response: None. ANR8343I Request request number for volume volume name canceled (PERMANENT) by administrator name.
Explanation: The specified volume already exists or contains data, so that the server cannot allow new export data to be written to it. System Action: The server detects that the given volume already contains some data that would be overwritten by the requested export operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the export operation. ANR8339E Device type volume intended volume name in drive drive name was replaced with volume incorrect volume name.
Explanation: A mount request is successfully canceled with the PERMANENT option. System Action: The system cancels the mount request and marks the volume as unavailable. User Response: None. ANR8344E Command: Invalid request number request number.
Explanation: A command has been entered with an incorrect request number. System Action: The server does not process the command. User Response: Issue the command with the correct request number. ANR8345E Command: No match found for this request number.
Explanation: The server detects that a previously mounted and verified volume (the desired volume) has been replaced with a different volume (the incorrect volume). No further read or write operations, or both, can occur on the given drive, because data corruption may occur. System Action: The server dismounts the volume from the drive. User Response: Mount the correct volume again if it is in a manual library and retry the operation. ANR8340I Device type volume volume name mounted.
Explanation: The request number specified by the command is not in the list of outstanding mount requests. System Action: The server does not process the command. User Response: Issue the command with the correct request number. ANR8346I Command: No requests are outstanding.
Explanation: The server has mounted the given volume. System Action: Read or write operations, or both, will commence for the volume. User Response: None. ANR8341I End-of-volume reached for device type volume volume name.
Explanation: A QUERY REQUEST or CANCEL REQUEST command has been entered although no mount requests are outstanding. System Action: Server operation continues. User Response: None.
Explanation: The server has detected an end-of-volume condition for the given volume. System Action: The volume is marked full. If more data must be stored, the server will access another volume for it.
Chapter 3. Common and Platform Specfic Messages
513
ANR8347E ANR8355E
ANR8347E Command: Volume volume not found. ANR8352I Requests outstanding:
Explanation: A DISMOUNT VOLUME command is issued, but the volume to be dismounted cannot be found. System Action: Server operation continues. User Response: Ensure that the correct volume name is entered. ANR8348E Command: Volume volume is not Idle.
Explanation: This message provides a list of currently outstanding mount requests. System Action: The server lists all outstanding mount requests or the one specified on the QUERY REQUEST command. User Response: None. ANR8353E Request number: I/O error reading label of volume in drive drive name.
Explanation: A DISMOUNT VOLUME command has been issued, but the volume is still in use and cannot be dismounted. System Action: Server operation continues. User Response: If it is necessary to dismount the volume, cancel the session or process that is using the volume, and reissue the command. ANR8349E Command: Device device not found.
Explanation: The server detects an error while reading the volume label from the volume in the specified drive. System Action: The volume is ejected, and the server continues to wait for the requested volume to be mounted. User Response: Ensure the following: 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. 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, retry the operation. ANR8354E Request number: Incorrect volume (volume name) mounted in drive drive name.
Explanation: A DISMOUNT DEVICE command has been issued, but the device to be dismounted cannot be found. System Action: Server operation continues. User Response: Ensure that the correct device has been specified. ANR8350E Command: Device device is not Idle.
Explanation: A DISMOUNT DEVICE command has been issued, but the device is still in use and cannot be dismounted. System Action: Server operation continues. User Response: If it is necessary to dismount the device, cancel the session or process that is using the device, and reissue the command. ANR8351E Request number: Mount request for volume volume name has timed out.
Explanation: The 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 volume name in drive drive name.
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.
Explanation: The server detects an error while reading/verifying the volume label for the volume in the specified drive. System Action: The volume is dismounted by the server. User Response: Ensure the following: 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
514
IBM Tivoli Storage Manager: Messages
ANR8356E ANR8364E
library, the library itself may need to be audited by using the AUDIT LIBRARY command. v The DEVICE parameter associated with the drive is identified correctly in the DEFINE PATH command, and the drive is currently powered on and ready. After checking and correcting these potential problems, retry the operation. ANR8356E Incorrect volume mounted volume name was mounted instead of volume expected volume name in library library name. 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 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. ANR8357I Error reading label of volume from slot-element element address in drive drive name of library library name.
Explanation: The specified volume has been deleted by the server. It can be returned to a scratch pool by the mount operator if desired. System Action: The volume is removed from the servers inventory. User Response: None. ANR8361E Command: Device type not specified.
Explanation: The specified command requires that the DEVTYPE parameter be supplied. System Action: The command is not processed. User Response: Reissue the command, and specify a valid DEVTYPE parameter. ANR8362E Command: The parameter parameter is invalid for device type device type.
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. User Response: Remove the volume from the library and ensure that it is properly labeled. After doing so, the volume can be checked into the library. ANR8358E Audit operation is required for library library name.
Explanation: The specified parameter is not valid for a device class with the given device type. System Action: The command is not processed. User Response: Reissue the command with a correct parameter. ANR8363E Command: The parameter parameter is required for device type device type.
Explanation: The server encounters a problem managing the given library, and determines that an AUDIT LIBRARY operation should be performed. System Action: The server may continue to access the library, but some volumes may not be accessible until an AUDIT LIBRARY command is issued against the library. 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 specified command requires that the given parameter be supplied when the indicated device type is used. System Action: The command is not processed. User Response: Reissue the command, providing the required parameter value. ANR8364E Command: Cannot reduce MOUNTLIMIT below number of volumes currently mounted.
Explanation: The server encounters a media fault while accessing the given volume using the specified drive.
Explanation: The MOUNTLIMIT value cannot be reduced below the number of currently mounted volumes.
Chapter 3. Common and Platform Specfic Messages
515
ANR8365E ANR8373I
System Action: The command is not processed. 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. LIBRARY parameter of the device class that references it. ANR8370I Device type volume volume name is mounted mount mode, status: RETRY.
Explanation: The specified parameter cannot be changed from the value that was provided with the associated DEFINE command. System Action: The command is not processed. 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 Command: Invalid value for parameter parameter.
Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is 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. System Action: None. User Response: None. ANR8371I I/O is being bypassed for volume volume name.
Explanation: An invalid value has been provided for the specified parameter. System Action: The command is not processed. User Response: Reissue the command, and specify a valid parameter value. ANR8367E Command: Multiple parameter values are not allowed.
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. System Action: None. User Response: None. ANR8372I Request number: Remove device type volume volume name from drive drive name of library library name.
Explanation: The designated parameter is specified more than once in the command; this is not allowed. System Action: The command is not processed. 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.
Explanation: A LABEL LIBVOLUME command has completed. You can remove the specified volume from the designated drive and store it outside the library. System Action: None. User Response: Remove the volume from the drive and store it in a safe place. ANR8373I 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 the request ID when ready.
Explanation: The user inserted the wrong side of the requested volume into the indicated drive. System Action: The volume is ejected, and the server continues to wait for the requested side of the volume to be mounted. User Response: Insert the correct side of the requested volume into the designated drive. ANR8369E 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
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. System Action: The server waits until a REPLY command is issued, or until the time limit expires. User Response: Insert the volumes into the librarys entry/exit port; and issue a REPLY command, along
516
IBM Tivoli Storage Manager: Messages
ANR8374E ANR8382W
with the request ID, to tell the server that the volumes have been inserted. ANR8374E Unable to unmount mountpoint mountpoint name. retrying the dismount of the given volume because of a failure during the previous dismount. System Action: None. User Response: None. ANR8379I Mount point in device class Device class name is waiting for the volume mount to complete, status: WAITING FOR VOLUME.
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 removablefile 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 Device type volume volume name cannot be overwritten by BACKUPSET operation.
Explanation: In response to a QUERY MOUNT command, the server indicates that there is a mount point in the given device class waiting for the volume mount to complete. System Action: None. User Response: None. ANR8380I Device type volume volume name is mounted mount mode in drive drive name, status: RETRY DISMOUNT FAILURE.
Explanation: The specified volume already exists or contains data, so that the server cannot allow new backup set data to be written to it. System Action: The server detects that the given volume already contains some data that would be overwritten by the requested backup set operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the backup set operation. ANR8376I Mount point reserved in device class Device class name, status: RESERVED.
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. System Action: None. User Response: None. ANR8381E Device type volume volume name could not be mounted in drive drive name.
Explanation: In response to a QUERY MOUNT command, the server indicates that there is a mount point reserved for future I/O operations in the given device class. System Action: None. User Response: None. ANR8377I Device type volume volume name is mounted mount mode, status: DISMOUNTING.
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. System Action: The requested operation fails. User Response: Examine previous messages for additional information regarding the specified volume and the operation. ANR8382W Library library name is now full.
Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is currently being dismounted. System Action: None. User Response: None. ANR8378I Device type volume volume name is mounted mount mode, status: RETRY DISMOUNT FAILURE.
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.
Explanation: In response to a QUERY MOUNT command, the server indicates that it is currently
Chapter 3. Common and Platform Specfic Messages
517
ANR8383E ANR8388E
ANR8383E Device class device class name directory directory name is not a SnapLock directory. ANR8386W Slot element number of library library name is inaccessible.
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 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 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 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.
Explanation: A CHECKOUT LIBVOLUME command 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.
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 continues to wait for the requested volume to be 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: When processing the named device class, 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. System Action: The operation fails. 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.
Explanation: The entry/exit ports of the library do not contain a volume that can be processed. System Action: The command fails. 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.
518
IBM Tivoli Storage Manager: Messages
ANR8389E ANR8405E
ANR8389E Device class device class name has storage pools using it with inconsistent RECLAMATIONTYPE parameters, or invalid directories specified in it. ANR8400I Library library name defined.
Explanation: The designated library has been successfully defined. System Action: The library is defined and recorded in the database. User Response: None. ANR8401E Command: Invalid library name library name.
Explanation: When processing the named device class, it was discovered that it was not configured properly. A device class can be referenced by storage pools of type RECLAMATIONTYPE=THRESHOLD or 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 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=THRESHOLD or 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.
Explanation: The designated library name is invalid; either it contains too many characters, or some of the characters are invalid. System Action: The command is not processed. User Response: Reissue the command using a valid library name. ANR8402E Command: Library library name is already defined.
Explanation: The designated library cannot be defined because it already exists. System Action: The command is not processed. User Response: If you want to define an additional library, reissue the command with a different library name. ANR8403E Command: Operation not allowed for library type libraries.
Explanation: The requested operation is not allowed for libraries of the given type. System Action: The command is not processed. User Response: None. 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. User Response: None. ANR8405E Command: Invalid drive name drive name.
Explanation: The designated drive name is invalid; either it contains too many characters, or some of the characters are invalid. System Action: The command is not processed. User Response: Reissue the command using a valid drive name.
Chapter 3. Common and Platform Specfic Messages
519
ANR8406E ANR8417E
ANR8406E Command: Drive drive name is already defined in library library name. ANR8412I Drive drive name deleted from library library name.
Explanation: The designated drive cannot be defined because it has already been defined for the specified library. System Action: The command is not processed. User Response: If you want to define an additional drive, reissue the command with a different drive name. ANR8407E Command: The MODEL parameter is required for this command.
Explanation: The designated drive has been deleted successfully from the specified library. System Action: The drive is deleted. User Response: None. ANR8413E Command: Drive drive name is currently in use.
Explanation: The designated drive cannot be deleted or updated because it is currently in use. System Action: The command is not processed. User Response: Wait until the drive is no longer in use, and reissue the command. ANR8414E Command: Drive drive name is not defined in library library name.
Explanation: The MODEL parameter has not been provided; it is required. System Action: The command is not processed. User Response: Reissue the command using the MODEL parameter. ANR8408E Command: The DEVICE parameter is required for this command.
Explanation: The designated drive has not been defined in the given library. System Action: The command is not processed. User Response: Reissue the command using a different drive name. If appropriate, define the drive before retrying the command. ANR8415E Command: The parameter parameter is required for this command.
Explanation: The DEVICE parameter has not been provided; it is required. System Action: The command is not processed. User Response: Reissue the command using the DEVICE parameter. ANR8409E Command: Library library name is not defined.
Explanation: The specified parameter must be provided when processing the given command. System Action: The command is not processed. User Response: Reissue the command, providing the required parameter value. ANR8416E Command: The parameter parameter is invalid for library type library type.
Explanation: The designated library has not been defined. System Action: The command is not processed. User Response: Reissue the command using a different library name, or define the library before retrying the command. ANR8410I Library library name deleted.
Explanation: The designated library has been deleted successfully. System Action: The library is deleted. User Response: None. ANR8411E Command: One or more drives are still defined in library library name.
Explanation: The specified parameter is not valid for libraries of the given type. The scratchcategory must be at lest 2 less than the privatecategory for 349x libraries. System Action: The command is not processed. User Response: Reissue the command, using only the proper parameters. If using the scratchcategory make sure it is at least 2 less than the privatecategory. ANR8417E Command: The parameter parameter is invalid for drives in library type libraries.
Explanation: The designated library cannot be deleted because there are still drives defined within it. System Action: The command is not processed. User Response: Delete all drives from the library, and reissue the command.
Explanation: The specified parameter is not allowed when defining or updating drives in a library of the given type. System Action: The command is not processed.
520
IBM Tivoli Storage Manager: Messages
ANR8418E ANR8426E
User Response: Reissue the command, using only the proper parameters. ANR8418E Command: An I/O error occurred while accessing library library name. given library. 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 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.
Explanation: An I/O error occurs while accessing the designated library. System Action: The operation fails. User Response: Ensure that the DEVICE parameter associated with the library is identified correctly in the DEFINE PATH command, and that the library is currently powered on and ready. If the library has an access door, make sure it is closed. After checking and correcting these potential problems, retry the operation. ANR8419E Command: The drive or element conflicts with an existing drive in library library name.
Explanation: A background server process that has been working to check in one or more volumes for the given library is canceled by the CANCEL PROCESS command. System Action: The server process is ended and server operation continues. User Response: None. ANR8424I Checking in volume volume name 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. System Action: The command is not processed. User Response: Specify a valid ELEMENT parameter that is not used by any other drive in the library. ANR8420E Command: An I/O error occurred while accessing drive drive name.
Explanation: 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. System Action: The background process operation continues. 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 library library name.
Explanation: An I/O error occurs while accessing the specified drive. System Action: The operation fails. User Response: Ensure that the DEVICE parameter 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: In response to a QUERY PROCESS command, this message displays the status for a CHECKIN LIBVOLUME process on the server. Volumes are being checked into the given library automatically using a search for previously-unknown volumes. System Action: The background process operation continues. User Response: None. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR8426E CHECKIN LIBVOLUME for volume volume name in library library name failed.
Explanation: The server cannot start a background process to carry out the designated command. System Action: The operation fails. User Response: Check for and correct memory shortages or other server resource constraints, and reissue the command. ANR8422I Command: Operation for library library name started as process process ID.
Explanation: A volume check-in process has been started to handle the insertion of a volume into the
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.
Chapter 3. Common and Platform Specfic Messages
521
ANR8427I ANR8435I
User Response: Make sure the library and drive devices associated with this command are powered on and ready, and then reissue the command. ANR8427I CHECKIN LIBVOLUME for volume volume name in library library name completed successfully. User Response: None. ANR8432E Command: Volume volume name is already present in library library name.
Explanation: The specified volume cannot be checked into the given library because it is already present. System Action: The command is not processed. 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 Command: Volume volume name is not present 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. User Response: None. ANR8428E Command: The STATUS parameter is required for this command.
Explanation: The specified volume cannot be checked out of the given library because it is not present. System Action: The command is not processed. 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: The STATUS parameter must be provided with the given command. System Action: The command is not processed. User Response: Reissue the command, and provide a valid STATUS parameter value. ANR8429E Command: No drives are currently defined in library library name.
Explanation: The command cannot be issued until at least one drive has been defined in the given library. System Action: The command is not processed. 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 Volume volume name has been checked into library library name.
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. System Action: The server starts a background process to perform the operation in response to the CHECKOUT 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. ANR8435I CHECKOUT LIBVOLUME for volume volume name in library library name has been canceled.
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. User Response: None. ANR8431I CHECKIN LIBVOLUME process completed for library library name; volume count volume(s) found.
Explanation: A background server process that has been working to check out the volume from the given library is canceled by the CANCEL PROCESS command. System Action: The server process is ended and server operation continues. User Response: None.
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.
522
IBM Tivoli Storage Manager: Messages
ANR8436I ANR8445I
ANR8436I Checking out volume volume name from library library name. ANR8441E Initialization failed for SCSI library library name.
Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKOUT LIBVOLUME process on the server. System Action: The background process operation continues. User Response: None. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR8437E CHECKOUT LIBVOLUME for volume volume name in library library name failed.
Explanation: The initialization process for the given library has failed, and will not be retried until the next time the server needs to access the library. System Action: The library is made temporarily unavailable. User Response: Make sure the library is powered on and attached. ANR8442E Command: Volume volume name in library library name is currently in use.
Explanation: The background process for a CHECKOUT LIBVOLUME command has failed. System Action: The background process ends, but the volume has not been checked out of the library. User Response: Make sure the library and drive devices associated with this command are powered on and ready, then retry the command. ANR8438I CHECKOUT LIBVOLUME for volume volume name in library library name completed successfully.
Explanation: The command cannot be processed because the specified volume is already being used for another operation. System Action: The command is not processed. User Response: Wait until the conflicting volume activity has completed, and then reissue the command. If the volume is currently mounted, but idle, you can dismount it with the DISMOUNT VOLUME command and then retry this operation. ANR8443E Command: Volume volume name in library library name cannot be assigned a status of SCRATCH.
Explanation: The background process for a CHECKOUT LIBVOLUME command has completed successfully. System Action: The volume is either deleted from the librarys inventory (if its status is something other than DATA) or marked not present (if its status is DATA). User Response: None. ANR8439I SCSI library library name is ready for operations.
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. System Action: The command is not processed. 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 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. User Response: None. ANR8440E Initialization failed for SCSI library library name; will retry in delay time minute(s).
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. System Action: The command is not processed. User Response: Wait until the library initialization completes or the library becomes ready. ANR8445I Volume volume name in library library name updated.
Explanation: The initialization process for the given 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.
Explanation: The specified library volume has been updated successfully.
Chapter 3. Common and Platform Specfic Messages
523
ANR8446I ANR8453E
System Action: The library volume inventory is updated. User Response: None. ANR8449E ANR8446I Manual intervention required for library library name. Scratch volume volume name rejected volume name is already in use. a new name in the process, or delete the existing volume that caused the name conflict.
Explanation: The specified library requires manual intervention. System Action: Current library activity will be delayed until the required intervention occurs. User Response: If the library has an access door, make sure it is in the closed position. If it has a cartridge carousel, make sure the carousel is installed. The server automatically detects when the appropriate action has been taken; it will then continue its operations. ANR8447E No drives are currently available in library library name.
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 rename the rejected volume or delete the existing volume that caused the name conflict. ANR8450E Command: Library library name is currently in use.
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 library cannot be deleted or updated because it is currently in use for an I/O operation. System Action: The command is not processed. 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.
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. User Response: None. ANR8452E Initialization failed for 349X library library name; will retry in delay time minute(s).
Explanation: The initialization process for the given library has failed. It is 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. ANR8453E Initialization failed for 349X library library name.
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
Explanation: The initialization process for the given library has failed and will not be retried until the next time the server needs to access the library. System Action: The library is made temporarily unavailable.
524
IBM Tivoli Storage Manager: Messages
ANR8454E ANR8462I
User Response: None. ANR8454E Mismatch detected between external label (volume name from external label) and media label (volume name from media label) in 349X library library name. the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command. ANR8458I AUDIT LIBRARY process for library library name has been canceled.
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. User Response: Remove the volume from the library and ensure that it is properly labeled. ANR8455E Volume volume name could not be located during audit of library library name. Volume has been removed from the library inventory.
Explanation: A background server process that has been working to audit the given library is canceled by the CANCEL PROCESS command. System Action: The server process is ended and server operation continues. User Response: None. ANR8459I Auditing volume inventory for library library name.
Explanation: In response to a QUERY PROCESS command, this message displays the status for an AUDIT LIBRARY process on the server. System Action: Server operation continues. User Response: None. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR8460E AUDIT LIBRARY process for library library name failed.
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: The background process for an AUDIT LIBRARY command has failed. System Action: The background process ends. User Response: Make sure the library and drive devices associated with this command are powered on and ready, then reissue the command. ANR8461I AUDIT LIBRARY process for library library name completed successfully.
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 Command: Operation for library library name started as process process ID.
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. User Response: None. ANR8462I End-of-side reached for device type volume volume name.
Explanation: A library audit process has been started for the given library. 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 AUDIT LIBRARY command entered by an administrator. User Response: To obtain status on the process, issue
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. User Response: None.
Chapter 3. Common and Platform Specfic Messages
525
ANR8463E ANR8471E
ANR8463E Device type volume volume name is write protected. ANR8467I Drive drive name in library library name updated.
Explanation: The server has detected a write-protect condition for the given volume. System Action: The server will dismount the volume and continue processing with another volume. User Response: Adjust the write-protect switch on the volume so that writing is allowed. If the volume is an optical volume and the write-protect switch is already set to allow writing, use the MOVE DATA command to move the data off of the volume. Rewritable volumes may be reformatted and reused after the data is moved to another volume. ANR8464E command: Invalid update request for library library name.
Explanation: An UPDATE DRIVE request has been successfully processed for the given drive. System Action: The server updates its information about the drive. User Response: None. ANR8468I device type volume volume name dismounted from drive drive name in library library name.
Explanation: The specified volume has been dismounted from the given drive. System Action: None. 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 library name failed.
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. System Action: The server does not process the command. User Response: If a different type of library device has been installed, the old library definition must be deleted with a DELETE LIBRARY command, and a new library must be defined. The UPDATE LIBRARY command cannot be used in this case. ANR8465I Library library name updated.
Explanation: An attempt to dismount the designated volume failed due to an I/O error. System Action: None. 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: An UPDATE LIBRARY request has been successfully processed for the given library. System Action: The server updates its information about the library. User Response: None. ANR8466E command: Invalid update request for drive drive name in library library name.
Explanation: The specified drive could not be initialized at this time. System Action: The initialization of the specified library continues. User Response: Examine previous messages for 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: 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. System Action: The server does not process the 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.
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
526
IBM Tivoli Storage Manager: Messages
ANR8472I ANR8478W
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 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. User Response: Delete all paths to this library, and reissue the command. ANR8475I Dismount of volume volume name failed. It may still be in the drive.
Explanation: The specified volume could not be dismounted. TSM encountered an error trying to dismount the volume. If the volume is a storage pool volume, TSM already attempted to make it unavailable. Review the output of the QUERY VOLUME F=D command for storage pool volumes. Review the output of the QUERY VOLHISTORY command for non-storage pool volumes. System Action: None. User Response: Review message ANR8469E in the activity log. Check if the volume is still loaded in the drive. If the volume is not in the drive, determine where the volume is located in the library. ANR8476E Operation is not supported for the libtype of library library name.
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. User Response: Remove the volume from the library and ensure that it is properly labeled. After doing so, the volume can be checked into the library. ANR8473I Volume volume name was found in storage element slot element address in library library name. It may still be in the drive.
Explanation: The operation failed because the libtype of the library is not supported for the operation. System Action: The operation fails. 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 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. System Action: None. User Response: Verify all other cleaner cartridges are in the correct storage slots. Issue the QUERY LIBVOLUME command to obtain the storage slots of all the cartridges currently checked into TSM. Remove the cartridge in the storage slot identified in the ANR8911W message. Remove the specified volume from the drive. Issue an AUDIT LIBRARY command against the library. ANR8474E Command: One or more paths are still defined to library library name.
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. System Action: The operation fails. 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 invetory does not match the database inventory. System Action: The operation fails. User Response: Run audit library against the specified library.
Explanation: The designated library cannot be deleted because there are still paths defined to it. System Action: The command is not processed.
Chapter 3. Common and Platform Specfic Messages
527
ANR8479W ANR8500E
ANR8479W Unable to audit slot-element slot-element of library library name. was not found or the statements in the file are in the wrong order. System Action: The command is not processed. User Response: Reissue the command, and specify a 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.
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. ANR8493I device type volume volume name mounted in drive drive name in library library name.
Explanation: The specified command requires that the 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. System Action: The command is not processed. User Response: Refresh your device configuration information file by issuing the BACKUP DEVCONFIG command. Make sure a library is defined for the device class. Reissue the command. ANR8498E Drive not defined for library library in device configuration information file.
Explanation: The specified volume has been mounted in the specified drive. System Action: None. User Response: For automated libraries, this message is purely informational. ANR8494E Command: An option specified is not valid for library type libraries.
Explanation: The specified command requires that the 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. System Action: The command is not processed. User Response: Refresh your device configuration information file by issuing the BACKUP DEVCONFIG command. Make sure a drive is defined for the library associated with the device class. Reissue the command. ANR8499I Command accepted.
Explanation: A requested option is not valid for libraries of the given type for the specified command. System Action: The command is not processed. User Response: None. ANR8495E Device type volume volume name cannot be written by BACKUP DB operation.
Explanation: The specified volume already exists or contains data, so that the server cannot allow new BACKUP DB data to be written to it. Or there is no space available on the destination filespace to write this backup to. System Action: The server detects that the given volume already contains some data that would be overwritten by the requested BACKUP DB command, or that there is not enough space available. User Response: If the specified volume does not contain any valuable data, delete it and retry the BACKUP DB command. ANR8496E Device class device class not defined in device configuration information file.
Explanation: The command is accepted and processed by the server. System Action: The server processes the command. User Response: None. ANR8500E No paths are defined for library library name in device configuration information file.
Explanation: The specified command requires that a path be defined in the device configuration information file for a drive in the specified library. This definition was not found, or the statements in the file are in the wrong order. System Action: The command is not processed. User Response: Refresh your device configuration information file by issuing the BACKUP DEVCONFIG command. Make sure a path is defined for the library
Explanation: The command that has been issued requires that the specified device class be defined in the device configuration information file. This definition
528
IBM Tivoli Storage Manager: Messages
ANR8501E ANR8550E (Solaris)
associated with the device class. Reissue the command. ANR8501E System return code return code received opening volume server volume name with file name file name SnapLock Filer documentation to resolve the issue; then, retry the command. ANR8550E Error opening filespec.
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. ANR8502E Errno errno received checking WORM directory directory name on Filer.
Explanation: An error occurs while attempting an open operation. System Action: Server processing continues. User Response: v Refer to the other displayed messages to determine why the open operation has failed. Correct the problem and restart the process. v If you have entered a file name ensure that the file name is correct and that it exists. ANR8550E (HP-UX) Error opening file name. Explanation: An error occurs while the server attempts a file open operation. System Action: Server processing continues. User Response: v Refer to the other displayed messages to determine why the open operation has failed. Correct the problem and restart the process. v If you have entered a file name ensure that the file name is correct and that it exists. ANR8550E (Linux) Error opening file name. Explanation: An error occurs while the server attempts a file open operation. System Action: Server processing continues. User Response: v Refer to the other displayed messages to determine why the open operation has failed. Correct the problem and restart the process. v If you have entered a file name ensure that the file name is correct and that it exists. ANR8550E (Solaris) Error opening file name. Explanation: An error occurs while the server attempts a file open operation. System Action: Server processing continues. User Response: v Refer to the other displayed messages to determine why the open operation has failed. Correct the problem and restart the process. v If you have entered a file name ensure that the file name is correct and that it exists.
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
Chapter 3. Common and Platform Specfic Messages
529
ANR8550E (Windows) ANR8552E (Solaris)
ANR8550E (Windows) Error opening filespec. Explanation: The server detects an error while attempting an open operation. System Action: Server processing continues. User Response: v Refer to the other displayed messages to determine why the open operation has failed. Correct the problem and restart the process. v If you have entered a file name ensure that the file name is correct and that it exists. ANR8551E An error (error code) occurred during a write operation. ANR8551E (Windows) An error (error code) occurred during a write operation. Explanation: The server detects an error while attempting a write operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the write operation has failed. Correct the problem and restart the process. ANR8552E An error (error code) occurred during a read operation.
Explanation: An error occurs while attempting a read operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the read operation failed; correct the problem and restart the process. ANR8552E (HP-UX) An error (error code) occurred during a read operation. Explanation: An error occurs while the server attempts a read operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the read operation failed. Correct the problem and restart the process. ANR8552E (Linux) An error (error code) occurred during a read operation. Explanation: An error occurs while the server attempts a read operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the read operation failed; correct the problem and restart the process. ANR8552E (Solaris) An error (error code) occurred during a read operation. Explanation: An error occurs while the server attempts a read operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the read operation failed. Correct the problem and restart the process.
Explanation: An error occurs while attempting a write operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the write operation failed; correct the problem and restart the process. ANR8551E (HP-UX) An error (error code) occurred during a write operation. Explanation: An error occurs while the server attempts a write operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the write operation failed. Correct the problem and restart the process. ANR8551E (Linux) An error (error code) occurred during a write operation. Explanation: An error occurs while the server attempts a write operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the write operation failed; correct the problem and restart the process. ANR8551E (Solaris) An error (error code) occurred during a write operation. Explanation: An error occurs while the server attempts a write operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the write operation failed. Correct the problem and restart the process.
530
IBM Tivoli Storage Manager: Messages
ANR8552E (Windows) ANR8554W (HP-UX)
ANR8552E (Windows) An error (error code) occurred during a read operation. Explanation: The server detects an error while attempting a read operation. System Action: Server processing continues. User Response: Refer to the other displayed messages to determine why the read operation has failed. Correct the problem and restart the process. ANR8553E Device type volume volume name cannot be overwritten by DUMPDB operation. ANR8553E (Solaris) Device type volume volume name cannot be overwritten by DUMPDB operation. Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it. System Action: The server has detected that the given volume already contains data that would be overwritten by the requested DUMPDB operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the DUMPDB operation, or specify a different volume name. ANR8553E (Windows) Device type volume volume name cannot be overwritten by DUMPDB operation. Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it. System Action: The server detects that the given volume already contains some data that would be overwritten by the requested DUMPDB operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the DUMPDB operation. ANR8554W Dump/load command: Device class device class name not defined. Devtype of FILE is assumed.
Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it. System Action: The server has detected that the given volume already contains some data that would be overwritten by the requested DUMPDB operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the DUMPDB operation. ANR8553E (HP-UX) Device type volume volume name cannot be overwritten by DUMPDB operation. Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it. System Action: The server has detected that the given volume already contains data that would be overwritten by the requested DUMPDB operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the DUMPDB operation, or specify a different volume name. ANR8553E (Linux) Device type volume volume name cannot be overwritten by DUMPDB operation. Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it. System Action: The server has detected that the given volume already contains data that would be overwritten by the requested DUMPDB operation. User Response: If the specified volume does not contain any valuable data, delete it and retry the DUMPDB operation, or specify a different volume name.
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. User Response: Refer to the other displayed messages to determine why the device class is not defined. Correct the problem and restart the command if you do not wish to write to or read from a file. ANR8554W (HP-UX) Dump/load command: Device class device class name not defined. Devtype of FILE is assumed. Explanation: The specified device class name is not defined with the DUMPLOADDB DEVCLASS option, to the server in the server options file or the server is not able to define the specified device class. System Action: Processing continues. The dump/load process assumes the device class is devtype=FILE and writes to or reads from a file.
Chapter 3. Common and Platform Specfic Messages
531
ANR8554W (Linux) ANR8556E (HP-UX)
User Response: Refer to the other displayed messages 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 (Linux) 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. User Response: Refer to the other displayed messages 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. 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. User Response: Refer to the other displayed messages 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. ANR8555E Error error code (error string) occurred during a read operation from disk disk name. ANR8555E (Linux) An error (error code, error string) occurred during a read operation from disk disk name. Explanation: An error occured while attempting a read from disk. System Action: Server processing continues. User Response: Correct the problem and restart the process. ANR8555E (Solaris) An error (error code, error string) occurred during a read operation from disk disk name. Explanation: An error occured while attempting a read from disk. System Action: Server processing continues. User Response: Correct the problem and restart the process. ANR8555E (Windows) An error (error code) occurred during a read operation from disk disk name. Explanation: An error occured while attempting a read from disk. System Action: Server processing continues. User Response: Correct the problem and restart the process. ANR8556E Error error code (error string) occurred during a write operation to disk disk name.
Explanation: An error occured while attempting a write to disk. System Action: Server processing continues. User Response: Correct the problem and restart the process. ANR8556E (HP-UX) An error (error code, error string) occurred during a write operation to disk disk name. Explanation: An error occured while attempting a write to disk. System Action: Server processing continues. User Response: Correct the problem and restart the process.
Explanation: An error occured while attempting a read from disk. System Action: Server processing continues. User Response: Correct the problem and start the process again. ANR8555E (HP-UX) An error (error code, error string) occurred during a read operation from disk disk name. Explanation: An error occured while attempting a read from disk. System Action: Server processing continues. User Response: Correct the problem and restart the process.
532
IBM Tivoli Storage Manager: Messages
ANR8556E (Linux) ANR8571E (HP-UX)
ANR8556E (Linux) An error (error code, error string) occurred during a write operation to disk disk name. Explanation: An error occured while attempting a write to disk. System Action: Server processing continues. User Response: Correct the problem and restart the process. ANR8556E (Solaris) An error (error code, error string) occurred during a write operation to disk disk name. Explanation: An error occured while attempting a write to disk. System Action: Server processing continues. User Response: Correct the problem and restart the process. ANR8556E (Windows) An error (error code) occurred during a write operation to disk disk name. Explanation: An error occured while attempting a write to disk. System Action: Server processing continues. User Response: Correct the problem and restart the process. ANR8557W Retrying failed I/O operation for disk disk name, errno errno. ANR8570E (HP-UX) HTTPS Initialization failed. No keyring file or keyring password were specified. Explanation: The HTTPS required keyring file and keyring password are not found. System Action: The HTTPS COMMMethod is not initialized. User Response: Ensure server has access to the keyring file and password. Restart the server. ANR8570E (Linux) HTTPS Initialization failed. No keyring file or keyring password were specified. Explanation: HTTPS required keyring file and keyring password are not found. System Action: The HTTPS COMMMethod is not initialized. User Response: Ensure server has access to keyring file and password. Re-start the server. ANR8570E (Solaris) HTTPS Initialization failed. No keyring file or keyring password were specified. Explanation: HTTPS required keyring file and keyring password are not found. System Action: The HTTPS COMMMethod is not initialized. User Response: Ensure server has access to keyring file and password. Re-start the server. ANR8570E (Windows) HTTPS Initialization failed. No keyring file or keyring password were specified. Explanation: HTTPS required keyring file and keyring password are not found. System Action: The HTTPS COMMMethod is not initialized. User Response: Ensure server has access to keyring file and password. Re-start the server. ANR8571E (HP-UX) HTTPS Initialization failed. The keyring file format is invalid. Explanation: HTTPS required keyring file has an invalid format. System Action: The HTTPS COMMMethod is not initialized. User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.
Explanation: An error occured while attempting an I/O operation on a disk volume. The request will be retried. System Action: The failed I/O operation is attempted again. User Response: Correct the problem being reported to avoid more errors in the future, or contact AIX support for assistance. ANR8558E 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. System Action: Server processing continues. User Response: Correct the problem and start the process again.
Chapter 3. Common and Platform Specfic Messages
533
ANR8571E (Linux) ANR8573E (Solaris)
ANR8571E (Linux) HTTPS Initialization failed. The keyring file format is invalid. Explanation: HTTPS required keyring file has an invalid format. System Action: The HTTPS COMMMethod is not initialized. User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server. ANR8571E (Solaris) HTTPS Initialization failed. The keyring file format is invalid. Explanation: HTTPS required keyring file has an invalid format. System Action: The HTTPS COMMMethod is not initialized. User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server. ANR8571E (Windows) HTTPS Initialization failed. The keyring file format is invalid. Explanation: HTTPS required keyring file has an invalid format. System Action: The HTTPS COMMMethod is not initialized. User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server. ANR8572E (HP-UX) HTTPS Initialization failed. The keyring file password is invalid. Explanation: An invalid password was specified for the HTTPS keyring file. System Action: The HTTPS COMMMethod is not initialized. User Response: Obtain the correct password for the keyring file. Then re-start the server. ANR8572E (Linux) HTTPS Initialization failed. The keyring file password is invalid. Explanation: An invalid password was specified for the HTTPS keyring file. System Action: The HTTPS COMMMethod is not initialized. User Response: Obtain the correct password for the keyring file. Then re-start the server. ANR8572E (Solaris) HTTPS Initialization failed. The keyring file password is invalid. Explanation: An invalid password was specified for the HTTPS keyring file. System Action: The HTTPS COMMMethod is not initialized. User Response: Obtain the correct password for the keyring file. Then re-start the server. ANR8572E (Windows) HTTPS Initialization failed. The keyring file password is invalid. Explanation: An invalid password was specified for the HTTPS keyring file. System Action: The HTTPS COMMMethod is not initialized. User Response: Obtain the correct password for the keyring file. Then re-start the server. 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. System Action: The HTTPS COMMMethod is not initialized. User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server. ANR8573E (Linux) HTTPS Initialization failed. I/O error occurred reading the keyring file. Explanation: An unknown I/O error occurred reading the keyring file. System Action: The HTTPS COMMMethod is not initialized. User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server. ANR8573E (Solaris) HTTPS Initialization failed. I/O error occurred reading the keyring file. Explanation: An unknown I/O error occurred reading the keyring file. System Action: The HTTPS COMMMethod is not initialized. User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.
534
IBM Tivoli Storage Manager: Messages
ANR8573E (Windows) ANR8576E (HP-UX)
ANR8573E (Windows) HTTPS Initialization failed. I/O error occurred reading the keyring file. Explanation: An unknown I/O error occurred reading the keyring file. System Action: The HTTPS COMMMethod is not initialized. User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server. 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: The HTTPS COMMMethod is not initialized. User Response: Ensure the keyring file is present and has read access allowed. Then re-start the server. ANR8574E (Linux) 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: The HTTPS COMMMethod is not initialized. User Response: Ensure the keyring file is present and has read access allowed. Then re-start the server. ANR8574E (Solaris) 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: The HTTPS COMMMethod is not initialized. User Response: Ensure the keyring file is present and has read access allowed. Then re-start the server. ANR8574E (Windows) 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: The HTTPS COMMMethod is not initialized. User Response: Ensure the keyring file is present and has read access allowed. Then re-start the server. ANR8575E (HP-UX) HTTPS Initialization failed. The specified certificate within the keyring file has expired. Explanation: The default or specified certificate within the keyring file has expired. System Action: The HTTPS COMMMethod is not initialized. User Response: The certificate must be renewed and re-instated into the keyring file. Then re-start the server. ANR8575E (Linux) HTTPS Initialization failed. The specified certificate within the keyring file has expired. Explanation: The default or specified certificate within the keyring file has expired. System Action: The HTTPS COMMMethod is not initialized. User Response: The certificate must be renewed and re-instated into the keyring file. Then re-start the server. ANR8575E (Solaris) HTTPS Initialization failed. The specified certificate within the keyring file has expired. Explanation: The default or specified certificate within the keyring file has expired. System Action: The HTTPS COMMMethod is not initialized. User Response: The certificate must be renewed and re-instated into the keyring file. Then re-start the server. ANR8575E (Windows) HTTPS Initialization failed. The specified certificate within the keyring file has expired. Explanation: The default or specified certificate within the keyring file has expired. System Action: The HTTPS COMMMethod is not initialized. User Response: The certificate must be renewed and re-instated into the keyring file. Then re-start the server. ANR8576E (HP-UX) HTTPS Initialization failed. The specified cert within the keyring file has as an invalid distinguished name. Explanation: The distinguished name for the specified cert is invalid. System Action: The HTTPS COMMMethod is not initialized. User Response: Ensure the correct keyring has been specified and that the keyring contains the correct distinguished name. Then re-start the server.
Chapter 3. Common and Platform Specfic Messages
535
ANR8576E (Linux) ANR8676E (S/390)
ANR8576E (Linux) HTTPS Initialization failed. The specified cert within the keyring file has as an invalid distinguished name. Explanation: The distinguished name for the specified cert is invalid. access. System Action: The HTTPS COMMMethod is not initialized. User Response: Ensure the correct keyring has been specified and that the keyring contains the correct distinguished name. Then re-start the server. ANR8576E (Solaris) HTTPS Initialization failed. The specified cert within the keyring file has as an invalid distinguished name. Explanation: The distinguished name for the specified cert is invalid. System Action: The HTTPS COMMMethod is not initialized. User Response: Ensure the correct keyring has been specified and that the keyring contains the correct distinguished name. Then re-start the server. ANR8576E (Windows) HTTPS Initialization failed. The specified cert within the keyring file has as an invalid distinguished name. Explanation: The distinguished name for the specified cert is invalid. System Action: The HTTPS COMMMethod is not initialized. User Response: Ensure the correct keyring has been specified and that the keyring contains the correct distinguished name. Then re-start the server. ANR8675E File name with environment variable DSMSERV_DIR: File already exists for File or Filetext Exit. ANR8675E (Linux) File name with environment variable DSMSERV_DIR: File already exists for File/FileText Exit, overwrite option not set to YES. Explanation: The specified file already exists and the overwrite option was not set to Yes. System Action: Server continues running. User Response: Specify another file or set the overwrite option to YES in the server options file. ANR8675E (S/390) File name: File already exists for File Exit. Explanation: The specified file already exists and the file-exit option was set to PRESERVE. System Action: Server continues running. User Response: Specify a non-existent file. ANR8675E (Solaris) File name with environment variable DSMSERV_DIR: File already exists for File/FileText Exit, overwrite option not set to YES. Explanation: The specified file already exists and the overwrite option was not set to Yes. System Action: Server continues running. 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. Explanation: The specified file already exists and the File/FileText exit option was set to PRESERVE. System Action: Server continues running. User Response: Specify a non-existent file. ANR8676E (S/390) User specified module: Cannot load into server, system errno = Error number generated by MVS. Explanation: The server was unable to load the module specified. The module is not a properly C-compiled/linked dynamic module or an ASSEMBLER/PLI compiled module. System Action: Server continues running. User Response: Use the server supplied sample user-exit files as a starting point.
Explanation: The specified file already exists and the file-exit option was set to PRESERVE. System Action: Server continues running. User Response: Specify a non-existent file. ANR8675E (HP-UX) 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. System Action: Server continues running. User Response: Specify a non-existent file.
536
IBM Tivoli Storage Manager: Messages
ANR8677E ANR8678E
ANR8677E User specified module, with environment variable DSMSERV_DIR: Cannot load into server, system errno = Error number generated by AIX. System Action: Server initialization stops or server continues running if already up. The module is unloaded. User Response: Check the user-exit module compilation type. Make sure it matches with what is specified in the options file. Only C, Assembler, and PLI compiled modules are supported. ANR8677E (Solaris) User specified module, with environment variable DSMSERV_DIR: Cannot load into server, system errno = Error number generated by Solaris. Explanation: The server was unable to load the module specified. The module is not a properly C-compiled and linked dynamic module. System Action: Server continues running. ANR8677E (HP-UX) User specified module, with environment variable DSMSERV_DIR: Cannot load into server, system errno = Error number generated by HP-UX. Explanation: The server was unable to load the module specified. The module is not a properly C-compiled and linked dynamic module. System Action: Server initialization stops or server continues running if already up. User Response: Use the server supplied sample makefile and export files to compile-link the user-exit module. Make sure the export.ref file contains the server-defined function name, and the module actually contains the server-defined function name, with one void parameter declared. ANR8677E (Linux) User specified module, with environment variable DSMSERV_DIR: Cannot load into server, system errno = Error number generated by Solaris. Explanation: The server was unable to load the module specified. The module is not a properly C-compiled and linked dynamic module. System Action: Server continues running. User Response: Use the supplied sample makefile, c , and h files to generate the user-exit module. Make sure the module contains product-defined function name adsmV3UserExit, and the module actually contains the product-defined function name, with one void * parameter declared, and returns void. ANR8677E (S/390) The user-exit module loaded does not match with type specified in options file. Explanation: The server was able to load a module, but the type of the module did not match the type specified in the server options file
Chapter 3. Common and Platform Specfic Messages
Explanation: The server was unable to load the module specified. The module is not a properly C-compiled and linked dynamic module. System Action: Server initialization stops or server continues running if already up. User Response: Use the server supplied sample makefile and export files to compile-link the user-exit module. Make sure the export.ref file contains the server-defined function name, and the module actually contains the server-defined function name, with one void parameter declared.
User Response: Use the server supplied sample 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. Explanation: The server was unable to load the module specified. The module is not a properly C-compiled and linked dynamic module. System Action: Server continues running. User Response: Use the server supplied sample makefile compile-link the user-exit module. ANR8678E Cannot bind User specified module, with environment variable DSMSERV_DIR into server, system errno = Error number generated by AIX.
Explanation: The server was unable to bind with the module specified. System Action: Server initialization stops or server continues running if already up. User Response: Use the server supplied sample makefile and export files to compile-link the user-exit module. Make sure the export.ref file contains the server-defined function name, and the module actually contains the server-defined function name, with 1 void parameter declared. The module may contain a global variable name that conflicts with the servers.
537
ANR8678E (HP-UX) ANR8679W (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. System Action: Server initialization stops or server continues running if already up. User Response: Use the server supplied sample makefile and export files to compile-link the user-exit module. Make sure the export.ref file contains the server-defined function name, and the module actually contains the server-defined function name, with one void parameter declared. 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. Explanation: The server was unable to bind with the module specified. The server could not find a function named adsmV3UserExit in the module. System Action: Server continues running. 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 generated by Solaris. Explanation: The server was unable to bind with the module specified. The server could not find a function named adsmV3UserExit in the module. System Action: Server continues running. User Response: Use the server 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 (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. System Action: Server continues running. ANR8679W (Solaris) Unable to unload user exit module: system errno = Error number generated by Solaris. Explanation: The server was not able to unload the user-exit module. System Action: Server continues running. User Response: The server should be stopped at the earliest possible time before the user exit is to be reactivated. User Response: Use the server supplied sample makefile to compile-link the user-exit module. Make sure there is a function name in the DLL as specified in the server options file. Make sure the function only accepts one argument, a void pointer. ANR8679W There is already an user-exit loaded.
Explanation: There was a previous successful load of an user-exit module, thus server cannot load another one. System Action: Server initilization stops or server continues running if already up. User Response: To load a new user-exit module, halt the server and then restart the server with the new user-exit module. ANR8679W (HP-UX) There is already an user-exit loaded. Explanation: There was a previous successful load of an user-exit module, thus server cannot load another one. System Action: Server initialization stops or server continues running if already up. User Response: To load a new user-exit module, the server must be halted and then restart the server with the new user-exit module. ANR8679W (Linux) Unable to unload user exit module: system errno = Error number generated by Solaris. Explanation: The server was not able to unload the user-exit module. System Action: Server continues running. User Response: The server should be stopped at the earliest possible time before the user exit is to be reactivated.
538
IBM Tivoli Storage Manager: Messages
ANR8679W (Windows) ANR8681I (Solaris)
ANR8679W (Windows) There is already an user-exit loaded. Explanation: There was a previous successful load of an user-exit module, thus server cannot load another one. System Action: Server continues running. User Response: To load a new user-exit module, halt the server and then restart the server with the new user-exit module. ANR8680W There is already a file used for the file or filetext exit. ANR8680W (Windows) 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. System Action: Server continues running. 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.
Explanation: There was a previous file open for the file or filetext exit. The server cannot open another one. System Action: Server initialization stops or server continues running if already up. 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 (HP-UX) There is already a file used for the file or filetext exit. Explanation: There was a previous file open for the file or filetext exit. The server cannot open another one. System Action: Server initialization stops or server continues running if already up. User Response: To start a new file for the file or filetext exit, halt the server, then restart the server with a new file name. ANR8680W (Linux) 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. System Action: Server initialization stops or server continues running if already up. 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. Explanation: There was a previous file open for the file or filetext exit. The server cannot open another one. System Action: Server initialization stops or server continues running if already up. User Response: To start a new file for the file or the filetext exit, halt the server, then restart the server with a new file name.
Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port. System Action: The server sends events to the Tivoli event server using this connection. User Response: None. ANR8681I (HP-UX) Connected to Tivoli event server at node name on port port. Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port. System Action: The server sends events to the Tivoli event server using this connection. User Response: None. ANR8681I (Linux) Connected to Tivoli event server at node name on port port. Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port. System Action: The server sends events to the Tivoli event server using this connection. User Response: None. ANR8681I (S/390) Connected to Tivoli event server at node name on port port. Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port. System Action: The server sends events to the Tivoli event server using this connection. User Response: None. ANR8681I (Solaris) 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.
Chapter 3. Common and Platform Specfic Messages
539
ANR8681I (Windows) ANR8683E
System Action: The server sends events to the Tivoli event server using this connection. User Response: None. ANR8681I (Windows) Connected to Tivoli event server at node name on port port. Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port. System Action: The server sends events to the Tivoli event server using this connection. User Response: None. ANR8682E Unable to determine port of Tivoli event server on node name. ANR8682E (S/390) 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 specified in the server options file. ANR8682E (Solaris) 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 specified in the server options file. ANR8682E (Windows) 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 specified in the server options file. ANR8683E Unable to connect to the Tivoli event server at node name on port port.
Explanation: The server was unable to determine the TCP/IP port on which the Tivoli event server on node 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 specified in the server options file. ANR8682E (HP-UX) 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 specified in the server options file. ANR8682E (Linux) 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 specified in the server options file.
Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port. 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 the value specified for TECPORT in the server options file is correct.
540
IBM Tivoli Storage Manager: Messages
ANR8683E (HP-UX) ANR8684E (HP-UX)
ANR8683E (HP-UX) Unable to connect to the Tivoli event server at node name on port port. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port. 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 the value specified for TECPORT in the server options file is correct. ANR8683E (Linux) Unable to connect to the Tivoli event server at node name on port port. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port. 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 the value specified for TECPORT in the server options file is correct. ANR8683E (S/390) Unable to connect to the Tivoli event server at node name on port port. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port. 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 the value specified for TECPORT in the server options file is correct. ANR8683E (Solaris) Unable to connect to the Tivoli event server at node name on port port. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port. 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
Chapter 3. Common and Platform Specfic Messages
TCP/IP Portmapper, then ensure that the value specified for TECPORT in the server options file is correct. ANR8683E (Windows) Unable to connect to the Tivoli event server at node name on port port. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port. 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 the value specified for TECPORT in the server options file is correct. ANR8684E Unable to connect to the Tivoli event server because TCP/IP is not available.
Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available. System Action: Event logging to the Tivoli event server is disabled. User Response: v Ensure that COMMMETHOD TCPIP is specified in the server options file. v If COMMMETHOD TCPIP was specified, use the BEGIN EVENTLOGGING TIVOLI command to manually start event logging to the Tivoli event server once server initialization has completed. ANR8684E (HP-UX) Unable to connect to the Tivoli event server because TCP/IP is not available. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available. System Action: Event logging to the Tivoli event 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 BEGIN EVENTLOGGING TIVOLI command to manually start event logging to the Tivoli event server once server initialization has completed.
541
ANR8684E (Linux) ANR8740W
ANR8684E (Linux) Unable to connect to the Tivoli event server because TCP/IP is not available. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available. System Action: Event logging to the Tivoli event 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 BEGIN EVENTLOGGING TIVOLI command to manually start event logging to the Tivoli event server once server initialization has completed. ANR8684E (S/390) Unable to connect to the Tivoli event server because TCP/IP is not available. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available. System Action: Event logging to the Tivoli event server is disabled. User Response: v Ensure that a valid value for TCPNAME is specified in the server options file. v If TCPNAME has the correct value, use the BEGIN EVENTLOGGING TIVOLI command to manually start event logging to the Tivoli event server once the server initialization has completed. ANR8684E (Solaris) Unable to connect to the Tivoli event server because TCP/IP is not available. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available. System Action: Event logging to the Tivoli event 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 BEGIN EVENTLOGGING TIVOLI command to manually start event logging to the Tivoli event server once server initialization has completed. ANR8684E (Windows) Unable to connect to the Tivoli event server because TCP/IP is not available. Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available. System Action: Event logging to the Tivoli event 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 BEGIN EVENTLOGGING TIVOLI command to manually start event logging to the Tivoli event server once server initialization has completed. 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. System Action: Server operation continues. User Response: None. ANR8686I Core dump successfully generated
Explanation: The server has successfully generated the requested core dump. System Action: Server operation continues. User Response: None. 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. System Action: Server operation continues. User Response: None. 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.
542
IBM Tivoli Storage Manager: Messages
ANR8741E ANR8749E
ANR8741E CHECKIN LIBVOLUME not permitted with current license terms. 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 Device type device type is not supported in this release.
Explanation: The CHECKIN LIBVOLUME operation is not permitted because the current license terms do not allow it. System Action: The command fails. 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. ANR8742E This server is not licensed to support the device type device type. Device Support Module module number is required.
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. ANR8747I Checking in volume volume name in library library name- CANCEL PENDING.
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. System Action: The operation fails. User Response: Contact your service representative to update the server license terms so that support for the required device type is enabled. ANR8743E This server is not licensed to support library device name. Device Support Module module number is required.
Explanation: In response to a QUERY PROCESS command, this message displays the status for a 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. User Response: None. ANR8748I Checking in volumes in search mode in library library name- CANCEL PENDING.
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. System Action: The operation fails. User Response: Contact your service representative to update the server license terms so that support for the given library device is enabled. ANR8744E Command: Current license terms do not permit this operation.
Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKIN LIBVOLUME process on the server. Volumes were being checked into the given library in search mode, but the process was canceled by an administrator. System Action: The background process operation is being terminated. User Response: None. ANR8749E Library order sequence check on library library name.
Explanation: The specified command failed because the current license terms do not permit it. System Action: The operation fails. User Response: Contact your service representative to update the server license terms so that the requested operation can be processed. ANR8745E Support for the 3590 device type is disabled for 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. v Mount is already pending. v Demount is already pending. v Demount was requested but no volume is mounted.
Chapter 3. Common and Platform Specfic Messages
Explanation: The requested operation fails because support for the 3590 device type is not currently enabled for the specified library. System Action: The operation fails.
543
ANR8750E ANR8760I
System Action: The operation fails. 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. ANR8753W This server is not licensed to support library library name. Library Sharing is required.
Explanation: This message is issued when a DEFINE LIBRARY command or library initialization for a library that requires library sharing and library sharing 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. User Response: Contact your service representative to update the server license terms so that support for the required device type is enabled. ANR8754E Command: There is already a request to delete library libary 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). System Action: The operation fails. User Response: Ensure the DEVTYPE parameter on the CHECKIN command matches the device type of the drive. Retry the operation. ANR8751W This server is not licensed to support the device type device type. Managed Library license is required.
Explanation: The designated library cannot be deleted or updated because there is a request to delete the library already. System Action: The command is not processed. User Response: None. ANR8755E Command: There is already a request to update library library name.
Explanation: This message is issued when a DEFINE DRIVE command or a volume mount operation uses a device class that is not licensed on the server. System Action: The operation fails if this is a try-and-buy server. For purchased servers, this message is to warn you that you are not in compliance with registered license terms. User Response: Contact your service representative to update the server license terms so that support for the required device type is enabled. ANR8752W This server is not licensed to support library device type. Managed Library license is required.
Explanation: The designated library cannot be deleted because there is a request to update the library already. System Action: The command is not processed. User Response: None. ANR8756E For 3995 optical libraries, must specify CHECKLABEL=YES.
Explanation: Optical libraries require the CHECKLABEL parameter to be set to YES System Action: The command fails. User Response: Reissue the command and specify the CHECKLABEL=YES option. ANR8760I Cancel in progress.
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. User Response: Contact your service representative to update the server license terms so that support for the required device type is enabled.
Explanation: The MOVE MEDIA command 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 a MOVE MEDIA command. System Action: Server operation continues. User Response: None.
544
IBM Tivoli Storage Manager: Messages
ANR8761I ANR8768E
ANR8761I Number of volumes processed: number 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 name in library library name completed successfully; Place the ejected volume in location location name.
Explanation: The MOVE MEDIA command has processed the number of volumes displayed. This message may be displayed in response to a QUERY PROCESS command for a MOVE MEDIA command. System Action: Server operation continues. User Response: None. ANR8762I Number of volumes processed: number. Ejecting volume volume name from library library name.
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. System Action: Server operation continues. User Response: None. ANR8763E Command: Volume volume name not processed: library library name not defined.
Explanation: The CHECKOUT LIBVOLUME operation has completed successfully for the indicated volume in the given library. Place the ejected volume in the indicated location. System Action: The volume is either deleted from the library inventory (if its status is something other than DATA) or marked not present (if its status is DATA). 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. ANR8767I Number of volumes processed: number volumes processed. Volumes sent to library library name for checkout: number volumes sent.
Explanation: The indicated volume is not processed since the designated library has not been defined or has been deleted. System Action: The volume is not processed. User Response: Reissue the command using a different library name, or define the library before retrying the command. ANR8764E Command: Volume volume name not processed: the operation is not allowed for library type library type.
Explanation: The indicated volume is not processed since the requested operation is not allowed for libraries of the given type. System Action: The volume is not processed. User Response: None. ANR8765I Request number: device type volume volume name in location location name is required for use in library library name; CHECKIN LIBVOLUME required within time limit minutes.
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 message may be displayed in response to a QUERY PROCESS command for a MOVE MEDIA command. System Action: Server operation continues. User Response: None. ANR8768E File file name on volume drive name could not be found.
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
Explanation: The server was unable to find the specified file name on the indicated volume. For removablefile 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. System Action: The volume is rejected. User Response: Ensure that the proper volume has been placed into the drive. If you are creating a
Chapter 3. Common and Platform Specfic Messages
545
ANR8769E ANR8775I
removablefile 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. ANR8773E Incompatible options CHECKLABEL=NO and SEARCH=YES for SCSI libraries.
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: 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. System Action: The command fails. 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: 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. ANR8771E Volume volume name in library library name is deleted. External Library is not synchronized with the server. Audit required.
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 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 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: 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. User Response: Contact your service representative to 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.
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. User Response: None.
546
IBM Tivoli Storage Manager: Messages
ANR8776W ANR8781E
ANR8776W Volume volume name in drive drive name contains lost VCR data; performance may be degraded. 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 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 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. ANR8780E Volume in drive drive name has no label.
Explanation: The VCR data on the volume is lost or corrupted, resulting in degraded tape positioning. The mount fails because the tape drive was configured to fail mounts that indicate this condition. System Action: The client command fails and the transaction is rolled back. User Response: Until the VCR data can be restored, 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 volume in the indicated drive does not have a label. The server requires that all media be uniquely labelled. System Action: The volume is rejected and the server prompts for a new volume. User Response: Use the appropriate labelling 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 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.)
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 labelled 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 labelling requirements. If ????? is shown for the label, it indicates that server was unable to read the label. System Action: The volume is rejected.
Chapter 3. Common and Platform Specfic Messages
547
ANR8782E ANR8788W
User Response: Use the appropriate labelling 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. This label must still conform to server requirements. ANR8782E Volume volume name could not be accessed by library library name. accommodate volume growth. ANR8786I Request number: Remove device type 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: The designated volume is in the inventory of the Library Manager, but the physical location is either inaccessible or unknown. System Action: The operation fails. The access mode of the volume is changed to UNAVAILABLE. User Response: Ensure that the cartridge is physically in the library, and reinventory the library. If the volume location is resolved, restore the access mode of the volume to its previous value using the UPDATE VOLUME command. ANR8783E Label on volume in drive drive name could not be read.
Explanation: 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. System Action: The server waits until a REPLY command is issued. User Response: Remove the volume from the library 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 library library name.
Explanation: The server was unable to read the label on the indicated drive. System Action: The volume is rejected. User Response: Use the appropriate labelling 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. This label must still conform to server requirements. ANR8784E File file name on volume drive name could not be created.
Explanation: A command is issued with the CHECKLABEL=BARCODE option. The library is unable to detect that the cartridges have valid barcode labels. The barcode reader is disabled or it is unable to read the labels. System Action: Unless the command is checking in cleaning cartridges, the process continues by loading the cartridges into the 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. ANR8788W Unable to read the barcode of cartridge in slot-id Element number of slot in library library name; loading in drive to read label.
Explanation: The 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. System Action: The volume is rejected. 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. System Action: The operation fails. User Response: The file system must be expanded to
Explanation: The library barcode reader is unable to read the label of a tape cartridge. The cartridge is found in the slot with the given element number. System Action: The cartridge is loaded into a drive and its label will be read from the tape. User Response: Cancel the process if you do not want to load any cartridges into the librarys drives. Examine the cartridge to ensure it has a barcode label and that it
548
IBM Tivoli Storage Manager: Messages
ANR8789W ANR8797W
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. to prevent deadlock from occurring between two recovering transactions. One of these criteria has failed. System Action: No DDR is performed and the transaction fails. User Response: Restart the transaction. ANR8794E Retry of operation name operation failed for device type volume volume name.
Explanation: Due to a drive or media fault, the server is moving the volume to a new drive. System Action: Read or write operations resume on the volume once it is remounted. User Response: None. ANR8790I device type volume volume name re-mounted in drive drive 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: 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. User Response: None. ANR8791E Unable to move device type volume volume name to another drive.
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. User Response: None. ANR8796W Drive drive name of library library name is not online; UPDATE DRIVE required.
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. User Response: See previous error messages to determine the cause of the DDR failure, and correct the problem. If the problem is an unreadable label, any data on the volume may be lost. ANR8792E Unrecoverable drive failures on drive drive name; drive is now taken offline.
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.
Explanation: The drive has been determined to be faulty because of recurrent failures. System Action: The drive is now marked offline. User Response: Service the drive for failures. Delete and redefine the drive to bring it back online. ANR8793E Dynamic drive recovery failed for device type volume volume name because not enough drives are available.
Explanation: The server is unable to use the mentioned drive. 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 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.
Chapter 3. Common and Platform Specfic Messages
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
549
ANR8798W ANR8806E
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. User Response: None. ANR8802E LABEL LIBVOLUME process process Id for library library name failed.
Explanation: The Label process terminated with a failure. System Action: The process ends. User Response: See previous error messages to 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.
Explanation: The drive being made offline is currently mounted with an open tape volume. If the transaction using the volume requires subsequent tape mounts and is unable to acquire a drive, the transaction will fail. System Action: If this tape volume is one of a sequence of volumes that are required to process a transaction, a drive must be available for each mount. This may be any drive in the library, but if all other library drives are currently busy and are still busy at the time the new tape must be mounted, the transaction will fail. User Response: If possible, make the drive online until the transaction using it ends. If there is an idle volume on the drive, dismount the volume first. ANR8799I Command: Operation for library library name started as process process ID.
Explanation: A background server process that has 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. System Action: The server process is ended and server operation continues. User Response: None. ANR8804I Labelling volume volume name in library library name.
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. System Action: The server starts a background process to perform the operation in response to the LABEL 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. ANR8800I LABEL LIBVOLUME for volume volume name in library library name completed successfully.
Explanation: In response to a QUERY PROCESS command, this message displays the status for a LABEL process on the server. System Action: The background process continues. User Response: None. The process may be cancelled by an authorized administrator using the CANCEL PROCESS command. ANR8805I Labelling volumes in library library name; volume count volumes(s) labelled.
Explanation: The background process to LABEL a volume has succeeded. System Action: The volumes label has been rewritten. User Response: None. ANR8801I LABEL LIBVOLUME process process Id for library library name completed; count of labelled volumes volume(s) labelled, count of checked in volumes volume(s) checked-in.
Explanation: In response to a QUERY PROCESS command, this message displays the status of a LABEL process with the SEARCH option. System Action: The background process continues. User Response: None. The process may be cancelled by an authorized administrator using the CANCEL PROCESS command. ANR8806E Could not write volume label volume name on the tape in library library name.
Explanation: A search-mode process to LABEL volumes has succeeded. System Action: The volumes have been labelled.
Explanation: The Label process could not write the label on the tape specified. System Action: For a LABEL operation with SEARCH=YES, the background process continues to the
550
IBM Tivoli Storage Manager: Messages
ANR8807W ANR8814I
next volume. For an individual volume, the process ends. The volume is not labelled and is not 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. ANR8807W Could not write label volume name on the volume in drive drive name of library library name because volume is already labelled existing volume name. ANR8810I Volume volume name has been labeled in library library name.
Explanation: The Label process with the search option has found and labeled a volume. System Action: The process ends. User Response: None. ANR8811E Command: The LABELSOURCE parameter is required when using SEARCH with this command.
Explanation: The check in or label process could not write the label on the tape specified because the volume is already labelled. System Action: The check in process will not overwrite volumes that are already labelled, and the label process will only overwrite volumes when OVERWRITE=YES is specified. The volume is not labelled 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. User Response: Reissue the command with the correct parameters. ANR8808E Could not write label label name on the volume in drive drive name of library library name because that volume is already labeled with volume name which is still defined in a storage pool or volume history.
Explanation: The LABELSOURCE parameter must be provided with the given command. System Action: The command is not processed. User Response: Reissue the command, and provide a valid LABELSOURCE parameter value. 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. System Action: The command is not processed. User Response: Reissue the command, and provide a valid SEARCH parameter value. ANR8813W Unable to read the barcode of cartridge in slot element Element number of slot in library library name.
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. System Action: The server process is ended and server operation continues. User Response: It is usually not necessary to re-label volumes. If the volume must be relabeled, that volume must first be removed from the storage pool or volume history file where it is defined. ANR8809I Request number: Please provide the label name for the volume in slot element slot element number of library library name by issuing REPLY n LABEL=xxx within time limit minutes, where n is the request ID and xxx is the desired label name.
Explanation: The library barcode reader is unable to read the label of a tape cartridge. The cartridge is found in the slot with the given element number. System Action: When LABELSOURCE=BARCODE is specified on the LABEL LIBVOLUME command, volumes without a barcode cannot be labelled. 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: A LABEL LIBVOLUME command is in progress, and the name of the next volume is needed. System Action: The server waits until a REPLY command is issued. User Response: Issue a REPLY command, along with the request ID, and the volume name for the next cartridge.
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.
Chapter 3. Common and Platform Specfic Messages
551
ANR8815I ANR8821E
System Action: The server continues normal operation. User Response: Remove the specified volume from the library. ANR8815I Remove volume Volume name from port element Port element number of library Library name. ANR8818E I/O Error on library library name; request for op. operation/function to the 3494 Library Manager has timed out.
Explanation: A command for the operation was issued to the Library Manager and a response was not received within the maximum timeout period. System Action: The operation and the transaction fails. User Response: Verify that communications with the library is operational, that it is online and ready for commands. Increase the time-out limit of the Library Manager Control Point device driver. If the problem persists, provide your service representative with the 3494 Library Manager transaction logs. ANR8819E Unable to read the barcode label(s) in 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. ANR8816E command: Volume Volume name in library Library name cannot be labelled because it is currently defined in a storage pool or in the volume history file.
Explanation: During command command processing, a 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 volme 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 is has previously used by an export, database dump, or database backup operation (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 Name length for volume Volume name invalid; max is Maximum name length.
Explanation: A LABEL command was issued with the LABELSOURCE=BARCODE option. The library was unable to detect that the cartridges had valid barcode 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 barcode reader. Not all vendors labels are readable by all libraries. Check that the barcode reader is configured and functioning properly. User Response: None. 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. User Response: None. ANR8821E Barcode of element slot element address, hardware barcode string, exceeds maximum length characters in 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.
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.
552
IBM Tivoli Storage Manager: Messages
ANR8822E ANR8830E
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. 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: 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: A CHECKIN LIBVOLUME SEARCH=BULK command was issued on a library that has no Entry/Exit ports. System Action: None. User Response: None. ANR8827E No Entry/Exit port is available on library library name.
Explanation: A CHECKOUT LIBVOL command was issued on a library where all its Entry/Exit Ports were found to be full or inaccessible. System Action: None. User Response: Empty all the entry/exit ports on the library, close the entry/exit port door, make sure the ports are accessible, and try the command again. ANR8828E Slot element number of library library name is inaccessible.
Explanation: The library device returned a count of zero for either the drives orthe 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. System Action: The operation fails. User Response: Configure the drives to the operating system, and reinitialize the library. ANR8824E I/O Error on library library name; request request id for operation operation/function to the 3494 Library Manager been lost.
Explanation: The slot in the library could not be physically accessed at this time. System Action: None. User Response: Verify that the Entry/Exit door is closed and the device has not logged any device errors before trying the command again. ANR8829I Remove volume volume name from slot element number of library library name at your convenience.
Explanation: A command for the operation was issued to the Library Manager and a response was not received within the maximum timeout period. System Action: The operation and the transaction fails. User Response: Verify that communications with the library is operational, that it is online and ready for commands. If the problem persists, provide your service representative with the 3494 Library Manager transaction logs and the request id from the failed operation. ANR8825E Volume range is not a valid volume range.
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. System Action: None. 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 specified string is not a valid volume range. System Action: The program prompts for a new 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 begining and
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.
Chapter 3. Common and Platform Specfic Messages
553
ANR8831W ANR8837E
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. 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 neccessary, 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: 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. System Action: None. 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 ore resolved, contact your support representative. Return the tape to scratch or dispose of it. ANR8832E CHECKIN LIBVOLUME for volumes in search mode in library library name failed.
Explanation: The server external library manager sent a RELEASE request to the external agent for the named volume, but the external agent was unable comply with the request. The server, however, marked the volume scratched in its inventory; consequently, the server inventory and the external agent inventory are not consistent. This message is issued to inform the customer that the external agent inventory must be made consistent with the server inventory using the facilities of the external agent. System Action: The server has returned the volume to scratch status. User Response: Consult the documentation for the external agent and take the appropriate action to make the agent inventory consistent with the server inventory. ANR8836E Function RSM_function failed in server_function processing, return return code, call call number.
Explanation: The background process for a CHECKIN LIBVOLUME command has failed. System Action: The background process ends, but volumes have 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. ANR8833E Command: Volume volume name in library library name is currently being checked in or checked out.
Explanation: The command cannot be processed because the specified volume is being checked in or checked out of the library. System Action: The command is not processed. 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: The library function that uses the API to the Windows NT Removable Storage Manager failed with a return code from the API. The call number represents the exact API call issued in the program. System Action: The function fails. User Response: Use the RSM documentation to determine the source of the problem. ANR8837E RSM Library Library Name not supported on this Windows platform.
Explanation: The libtype=RSM was used on a Windows platform that does not support RSM. System Action: The function fails. User Response: Use another library type to define the library.
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.
554
IBM Tivoli Storage Manager: Messages
ANR8838E ANR8844E
ANR8838E I/O error on drive drive name: excessive unit attentions received from device. User Response: Remove the volume from the 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: 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. System Action: The operation fails. 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 neccessary to manually unload the volume and mark the drive offline with the UPDATE DRIVE command. ANR8839W Drive drive name of library library name is accessible.
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. ANR8843E Initialization failed for library type library library name - the library will be inaccessible.
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. System Action: The drive is left offline and is not used for tape operations. User Response: Issue the UPDATE DRIVE command to bring the drive back online. ANR8840E Unable to open device device name with error error number.
Explanation: The initialization process for the given 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 library was inaccessible, thus causing a open request to fail. This will inturn cause the pending request to fail. System Action: A drive is marked inaccessible and the server starts polling the drive to determine if the library and drive are inaccessable. In most case, the libary 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. ANR8841I Remove volume from slot element number of library library name at your convenience.
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.
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. System Action: None.
Chapter 3. Common and Platform Specfic Messages
555
ANR8845E ANR8851E
ANR8845E Loadable module module name is required for remote operation. 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 Drive drive name of library library name is inaccessible; server has begun polling drive.
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 initializion 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 initializion 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 contact your service representative. ANR8846E Volume volume name is assigned to a category that does not belong to library library name.
Explanation: The server is unable to use the mentioned drive. 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 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. ANR8849E Command: There is already a request to delete drive drive name.
Explanation: The attempted operation on the volume cannot proceed because it is assigned to a category other than the insert, private, or scratch category used by the library. System Action: The attempted operation is terminated. 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. 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
Explanation: The designated drive cannot be deleted or updated because there is a request to delete the drive already. System Action: The command is not processed. User Response: None. ANR8850I ACSLS 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. User Response: None. ANR8851E Initialization failed for ACSLS library library name; will retry in delay time minute(s).
Explanation: The initialization process for the given library has failed. It is retried automatically after the
556
IBM Tivoli Storage Manager: Messages
ANR8852E ANR8860W
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. ANR8852E Initialization failed for ACSLS library library name. 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. 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. ANR8857I ACS access control set to user_id - user id, status=acs status.
Explanation: The initialization process for the given library has failed and will not be retried until the next time the server needs to access the library. System Action: The library is made temporarily unavailable. User Response: None. 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. System Action: The command fails. User Response: Reissue the CHECKIN LIBVOL command and specify CHECKLABEL=YES. ANR8854E ACSAPI(command name) invocation failed, status=acs status.
Explanation: The ACSLS ACCESSID structure for command and volume access control is set the user_id as indicated. System Action: None. User Response: Ensure the indicated user_id is the same as specified in the environment variable ACSAPI_USER_ID. ANR8858W Unable to lock drive drive id,drive id,drive id,drive id, status=acs status.
Explanation: The ACSLS library api invocation for the given command failed. 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 function acs_lock_drive failed for the specified drive. System Action: Depends on the server function and command, library drive may be unavailable. or may be temporary unavailable in a shared library environment. User Response: Contact your ACS System Administrator and perform ACSLS library problem determination if the problem persists. ANR8859W Unable to lock volume volume id, status=acs status.
Explanation: The ACSLS library api responded with an unsuccessful status as indicated. System Action: Depends on the server function and command, library may be unavailable. 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.
Explanation: The ACSLS library function acs_lock_volume failed for the specified volume. System Action: Depends on the server function and command, library volume is unavailable. User Response: Contact your ACS System Administrator and perform ACSLS library problem determination if the problem persist. ANR8860W Volume volume id is already locked by user id.
Explanation: The specified volume is already locked by other user or has a different lock id. System Action: Depends on the function, the volume maybe bypassed or the process maybe terminated.
Chapter 3. Common and Platform Specfic Messages
557
ANR8861I ANR8870E
User Response: This may not be an error in a shared configuration. However, if the existing volume lock is not needed. contact your ACSLS system administrator to clear the lock the volume. ANR8861I Wait and monitor the ACSSA console message to remove volume volume id from CAP. User Response: Determine the volume status from the ACSSA and re-issue the command if necessary. ANR8866E Incompatible option REMOVE=BULK for ACSLS libraries.
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. System Action: None. User Response: Monitor the ACSSA console and wait. ANR8862I Unable to access ACS volume volume id.
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. System Action: The command fails. User Response: Reissue the CHECKOUT LIBVOL command and specify REMOVE=YES or NO. ANR8867I Processing volume volume id for the command command.
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. System Action: Depends on the server function and command, library volume is unavailable. User Response: Contact your ACS System Administrator and perform ACSLS library problem determination if the problem persist.. ANR8863I Unlocking library library name volumes from the ACSLS server.
Explanation: The specified volume is being processed for the specified command. System Action: The command process continues. User Response: None. 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 System Action: The operation continues. User Response: Determine the volume status from the message and do something as needed ANR8869E Command: There is already a request to update drive drive name.
Explanation: The volumes of the specified library are being unlocked from the ACSLS server. System Action: The operation continues. The process may take a while depends on the number of volumes in the library. User Response: None. ANR8864I ACSLS library library name is being re-initialized.
Explanation: The designated drive cannot be deleted because there is a request to update the drive already. System Action: The command is not processed. User Response: None. ANR8870E The path to the library library name is unavailable.
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. User Response: None. ANR8865W Volume volume name bypassed for command, status=acs_status.
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.
Explanation: The specified volume is bypassed. The volume is not in a valid status for the specified function. System Action: The operation continues.
558
IBM Tivoli Storage Manager: Messages
ANR8871I ANR8877E
ANR8871I The device name device name specified has been changed to device name. ANR8875E 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 specified device name on the DEFINE PATH or UPDATE PATH command has been changed to recommended device name. System Action: The command process continues. User Response: None. ANR8872E No path is available for drive drive name - could not unload volume volume name from drive.
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, and retry the operation. ANR8876E The media in element element number of library library name is a cleaner.
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. User Response: Ensure that a path is defined to the drive. If there is a path defined to the drive, make sure that the path is online and that the source of the path is also online. Run the AUDIT LIBRARY command after the problem is corrected. ANR8873E The path from source source name to destination drive name is taken offline.
Explanation: 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 labelled 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, and retry the operation. ANR8877E Volume volume name is incompatible type with device class devclass name in library library name.
Explanation: There is problem using the indicated path. The path is now marked offline. System Action: The path is inaccessible. User Response: Determine the reason the path is inaccessible, such as hardware problem. Render any needed corrections. Then, the path may be made online by issuing the UPDATE PATH command with the ONLINE=YES option. ANR8874E The type of device used by the media in element element number of library library name cannot be determined by the hardware. Volume is not processed.
Explanation: 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. System Action: The operation fails. 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 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-labelled if the barcode name changes.
Chapter 3. Common and Platform Specfic Messages
559
ANR8878E ANR8904I
ANR8878E Failed to close the remote library library name(device name). ANR8901E Command: Incompatible options STATUS=CLEANER and CHECKLABEL=YES.
Explanation: An attempt to close a remote Library device attached to a NAS File Server failed. System Action: The operation fails. User Response: Examine previous messages for additional information regarding the specified library. ANR8879E Failed to close the SCSI session for the remote library library name(device name).
Explanation: Cleaner cartridges do not have internal labels that can be checked by loading them into the drive. System Action: The command fails. User Response: Reissue the CHECKIN LIBVOL 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). ANR8902W Unable to read the barcode of cleaner cartridge in slot-id Element number of slot in library library name; cleaner not checked in.
Explanation: An attempt to close a SCSI session for a remote Library device attached to a NAS File Server failed. System Action: The operation fails. User Response: Examine previous messages for additional information regarding the specified library. ANR8880W Device type of drive Drive name in library Library name was determined to be GENERIC_TAPE.
Explanation: The library barcode reader is unable to 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 barcode reader. Not all vendors labels are readable by all libraries. Check that the barcode reader is configured and is functioning properly. The cleaner cartridge can be checked in without use of the barcode label by issuing the CHECKIN LIBVOL command. ANR8903E Command: Missing CLEANINGS parameter for cleaner cartridge checkin.
Explanation: The device type of a drive is determined when the path for that drive is defined. If the wrong device file was used in the device parameter of DEFINE PATH the device type of the drive will often be GENERIC_TAPE. If you are using the TSM device driver or the IBMTape device driver, then you should not have a device type of GENERIC_TAPE. You should only have a device type of GENERIC_TAPE if you are using the native OS device driver. System Action: None. User Response: Verify that GENERIC_TAPE is the desired device type for this drive. While the device type GENERIC_TAPE is valid, it is often a mistake, and thus, should be verified that it is the intended device type. If GENERIC_TAPE is not the intended device type, all paths for this drive and the drive itself will have to be deleted and redefined. ANR8881W Insufficient space for new volume in directory directory for device class device class name.
Explanation: When checking in a cleaner cartridge, the CLEANINGS parameter is required. System Action: The command fails. User Response: Reissue the CHECKIN LIBVOL command and specify a value for the CLEANINGS parameter which is used to determine the number of times a cleaner can be mounted to clean a drive. ANR8904I Command: Cleaning operation for drive drive name in library library name started as process process ID.
Explanation: The server found that the indicated directory had insufficient space in which to create a new volume. System Action: Other directories available to the device class are used, if any. If no directories with space are available, the operation fails. This message is issued periodically as requests are made for space in this directory. User Response: The file system must be expanded to accommodate volume growth.
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.
560
IBM Tivoli Storage Manager: Messages
ANR8905I ANR8912E
User Response: To obtain status on the process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command. ANR8905I CLEAN DRIVE process for drive drive name in library library name is been canceled. ANR8909I Cleaning drive drive name in library library name- CANCEL PENDING.
Explanation: In response to a QUERY PROCESS command, this message displays the status for a CLEAN DRIVE process on the server. System Action: The background process operation is terminated. User Response: None. ANR8910I No cleaner, or no cleaner with cleanings left, found in library library name.
Explanation: A background server process is has been working to clean the specified drive and is canceled by the CANCEL PROCESS command. System Action: The cleaning process is ended. User Response: None. ANR8906I Cleaning drive drive name 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. System Action: The drive is available for normal 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: In response to a QUERY PROCESS command, this message displays the status for a CLEAN DRIVE process on the server. The given volume is being checked in to the designated library. System Action: The background process operation continues. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. User Response: None. The process may be canceled by an authorized administrator using the CANCEL PROCESS command. ANR8907E CLEAN DRIVE for drive drive name in library library name failed.
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. System Action: The drive is available for normal 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 cleaner volume status. If necessary a cleaner cartridge should be checked in to replace it. ANR8912E Unable to verify the label of volume from slot-element element-address in drive drive name in library library name.
Explanation: The background process for a CLEAN DRIVE fails. System Action: The background process ends, but the drive is not cleaned. User Response: Make sure the library and drive devices associated with this command are powered on and ready. Reissue the command. 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. User Response: None.
Explanation: The volume from the slot that is identified by the element address is loaded into a drive. The drive cannot be opened following the load. The label cannot be read to process the volume. System Action: The volume is stored, and processing continues with the next available slot. User Response: Check the system error logs for errors reported by the drive that are related to this volume. Make sure that the cartridge is not a cleaner cartridge that would have been loaded by mistake. If the
Chapter 3. Common and Platform Specfic Messages
561
ANR8913I ANR8921E
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. ANR8913I Drive drive name in library library name is currently busy; Cleaning is scheduled. User Response: None. ANR8917I Drive mapping for drive Drive name in library library name on storage agent storage agent name updated.
Explanation: An UPDATE DRIVEMAPPING request has been successfully processed for the given drive. System Action: The server updates its information about the drive mapping. User Response: None. ANR8918I Drive mapping for drive Drive name in library library name on storage agent storage agent name deleted.
Explanation: A background process to clean the drive is unable to acquire the drive because the drive is busy. System Action: The background process operation completes. The drive is scheduled to be cleaned when it is unloaded. User Response: None. ANR8914I Drive drive name in library library name needs to be cleaned.
Explanation: The drive mapping for the specified storage agent, library, and drive has been deleted successfully. System Action: The drive mapping is deleted. User Response: None. ANR8919I Initialization and recovery has started for shared library library name.
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. User Response: None. ANR8915I Cleaning cartridge cleaner name in library library name is near end of life; has cleanings left uses left.
Explanation: The shared library has started to initialize or recover to resynchronize the library manager and library client. System Action: None. User Response: This process should resynchronize all of the drives that are currently being used by this library client. This process might also start after a communication error or if the library client has not been able to verify drive status with the library manager. ANR8920I Initialization and recovery has ended for shared library library name.
Explanation: A cleaner cartridge is found and used, but its number of uses it has left is nearly exhausted. System Action: The cleaning operation continues. User Response: As the cleaner is used, monitor the number of cleanings that remain with the QUERY LIBVOL command. Remove the cleaner when all cleanings are exhausted. A new cleaner may be checked in so that the library is not left without a useful cleaner when the old cleaner is exhausted. ANR8916I Drivemapping for drive Drive name in library library name on storage agent storage agent name defined.
Explanation: Initialization or recovery has ended the library manager and library client should be synchronized. System Action: None. 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: A drive mapping has been successfully defined for the specified drive. System Action: The drivemapping is defined and recorded in the database.
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
562
IBM Tivoli Storage Manager: Messages
ANR8922I ANR8929E
defined or when the server is first initialized. System Action: None. 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. 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: 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. System Action: None. User Response: Define a device class for the library using the DEFINE DEVCLASS command. ANR8923I Dismount failed because drive drive name in library library name is not currently owned by drive owner 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. System Action: None. 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 library client attempted to dismount a drive that was not currently owned by the library client. System Action: None. User Response: None. ANR8925W Drive drive name in library library name has not been confirmed for use by server server name for over elapsed time seconds. Drive will be reclaimed for use by others.
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. System Action: None. User Response: Issue the UPDATE LIBRARY libname SHARED=YES command to make the library shared. ANR8929E Library library name specified for shared file device class device class name was not defined as a FILE library.
Explanation: The library server was unable to contact the library client for the given interval to verify that the library client is still using the drive. At this point the error recovery logic of the library manager will reclaim the drive (including dismounting the clients volume if possible) and allow other to use the drive. System Action: None. 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: 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.
Explanation: The library client was unable to confirm the usage of the drive to the with the library manager. System Action: None.
Chapter 3. Common and Platform Specfic Messages
563
ANR8930W ANR8934W
ANR8930W 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. 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: 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. User Response: Use the QUERY DRIVE command to 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: 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. System Action: The server continues operation. 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.
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. System Action: The server continues operation. User Response: Use the QUERY DRIVE command to 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.
Explanation: A FILE volume was being inserted into the library inventory. The file was not found in the directory associated with the device class that references the library. However, an entry for the indicated file name is already in the library inventory. System Action: The server continues operation. 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
564
IBM Tivoli Storage Manager: Messages
ANR8935E ANR8941W
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. 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 in library server or storage agent name does not contain the directory attribute.
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. System Action: The drive will not be accessible by the library during tape operations. User Response: The drive may be made accessible by issuing the UPDATE DRIVE command with the 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. System Action: The drive will not be accessible by the server for tape operations. User Response: The drive may be made accessible by issuing the UPDATE DRIVE command with the DEVICE= option. ANR8938E Initialization failed for Shared library library name; will retry within delay time minute(s).
Explanation: A library client or storage agent requested a mount of a drive that is contained in a file library but the path definition does not contian the directory attribute. System Action: The request will fail. User Response: Ensure that DIRECTORY attribute of the above path definition contains the correct value for the given server or storage agent. ANR8941W The volume from slot-element element-address in drive drive name in library library name is blank.
Explanation: The initialization process for the given library has failed. It will be retried automatically in the specified time. System Action: The initialization will be retried later. User Response: Ensure that the library manager server is running, and the library is initialized.
Explanation: The volume in the slot is not labelled 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.
Chapter 3. Common and Platform Specfic Messages
565
ANR8942E ANR8949E
ANR8942E Could not move volume volume name from slot-element element-address to slot-element element-address. ANR8945W Scratch volume mount failed volume name.
Explanation: Scratch volume mount failed. System Action: Scratch volume mount operation failed. User Response: None. ANR8946W There were more labels in the vollist than volumes available to label.
Explanation: Could Not move volume from slot to slot. System Action: Move volume operation failed. User Response: None. 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 D in the Messages manual for recommended action.
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. User Response: None. ANR8947W There were less labels in the vollist than volumes available.
Explanation: A hardware or media error has occurred while operating on the designated library device. System Action: The operation fails. User Response: Ensure that the DEVICE parameter associated with the library was identified correctly in 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 drive or library reference manual provided with the device usually contain tables that explain the values of the KEY, ASC, and ASCQ fields. If the problem persists, contact your hardware support and/or service representative and provide the internal code values and sense data from this message. 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 D in the Messages manual for recommended action.
Explanation: Label Libvolume command still finishes without error, but volumes are left unlabeled. System Action: Additional volumes were left unlabeled. User Response: None. ANR8948S Device device, volume volume name has issued the following Critical TapeAlert: alertmessage
Explanation: The specified deviced 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: A hardware or media error has occurred while operating on the designated drive. System Action: The operation fails. User Response: Ensure that the DEVICE parameter associated with the drive was identified correctly in the DEFINE PATH command, and that the device is currently powered on and ready. The drive or library reference manual provided with the device usually contain tables that explain the values of the KEY, ASC, and ASCQ fields. If the problem persists, contact your hardware support and/or service representative and provide the internal code values and sense data from this message.
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
566
IBM Tivoli Storage Manager: Messages
ANR8950W ANR8957E
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. User Response: Proper response may be indicated in the text of the TapeAlert. The context of the TapeAlert may need to be determined from other activity log messages in order to follow its recommendations. ANR8950W Device device, volume volume has issued the following Warning TapeAlert: alertmessage 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. User Response: None. ANR8955I Drive drive name in library library name with serial number serial number is updated with the newly discovered serial number serial number .
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. 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. ANR8951I Device device, volume volume has issued the following Information TapeAlert: alertmessage
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: User Response: None. ANR8956E Serial number defined for library library name does not match the discovered serial number.
Explanation: The specified deviced while loaded with the named volume has issued a TapeAlert information message. This message is a feature of the hardware and is from the device, not the TSM server. It is surfaced at the termination of the current operation but is independent of the operation. System Action: The operation may or may not fail, depending on other error indications such as check conditions from the device. The TapeAlert message does not by itself indicate failure. See other messages related to the device or volume in the activity log. 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. ANR8952E Library serial number does not match that defined for library name .
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: Autodectect is OFF and the serial number reported by the library did not match the serial number in the library definiton.
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
Explanation: An invalid value has been provided for the specified parameter. System Action: The command is not processed. User Response: Reissue the command, and specify a valid parameter value.
Chapter 3. Common and Platform Specfic Messages
567
ANR8958E ANR8968E
ANR8958E Command: Autodectect is OFF and the serial number reported by the drive did not match the serial number in the drive definiton. ANR8964W Unable to update the path in the database path source name and drive drive name .
Explanation: An invalid value has been provided for the specified parameter. System Action: The command is not processed. User Response: Reissue the command, and specify a valid parameter value. ANR8959W Path to the library or the device does not exist.
Explanation: The system is not able to update the path information in the database. System Action: . User Response: None. ANR8965W The server is unable to automatically determine the serial number for the device.
Explanation: A path to the library or the device does not exist yet. System Action: This may not be an error. User Response: None. ANR8960I Command: The display of Tape Alerts from SCSI devices is status.
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. System Action: Server operation continues. User Response: Verify that the device name in the path definition is correct. ANR8966E Cannot get device number for the drive drive name.
Explanation: Whether the status of Tape Alerts from SCSI devices will be display. System Action: The command is processed. User Response: None. ANR8961E Serial number defined for library library name and drive drive name is blank and does not match the discovered drive serial number serial number.
Explanation: 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 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 or an invalid device name was specified for the drive. Render any needed corrections to the drive. The drive will be brought online automatically when the polling process detects that is has become accessible. ANR8967E Command: The drive serial conflicts with an existing drive in library library name.
Explanation: A device has been swapped and we are not able to get the new path. System Action: . User Response: None. ANR8962E Serial number defined for library library 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: . User Response: None. ANR8963E Unable to find path to match the serial number defined for drive drive name in library library name .
Explanation: The serial number already exists in the drives in the given library. System Action: The command is not processed. User Response: Specify a valid serial parameter for this drive. ANR8968E Unable to create path for device device.
Explanation: A device has been swapped and we are not able to get the new path. System Action: . User Response: None.
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.
568
IBM Tivoli Storage Manager: Messages
ANR8969E ANR8975I
User Response: The device parameter is probably not valid. This could be temperary, 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 ownerOwner name. ANR8972E command: Unable to find the element number for drive drive name in library library name.
Explanation: Because the drive serial number does not match any drive serial number in the serial/element number map reported by the library, the element number cannot be determined. System Action: The command is not processed. 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 Reset has failed to break the reservation set by another system for device device name with path path name.
Explanation: A command was issued updating ownership of a volume. The owner of this particular volume can not be changed. System Action: The command is not processed. User Response: None. ANR8970E Unable to open special file specialfile for tracing parameter device driver; errno = errno.
Explanation: The attempt to reset the device reservation set by another system has failed. System Action: . User Response: The device my have to be rebooted to reset the reservation. If not, this device will not be accessible. 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: 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: 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: 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.
Explanation: A new path has been found for the device and the path information has been updated. System Action: . User Response: The path change may be caused by system reboot or cable swap or device addition or removal.
Chapter 3. Common and Platform Specfic Messages
569
ANR8976W ANR9581W (HP-UX)
ANR8976W Command: commandUpdate creates a mismatch in the number of directories defined for device class device class name and the number of directories in one or more PATH definitions. User Response: Determine why file does not exist; create if necessary. ANR9579W (Solaris) 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. 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. Explanation: Appending the replacement volume name postfix to the original volume name has created a name that may not be a valid raw partition name. System Action: Replacement volume name is used in the recovery plan stanza. 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. Explanation: Appending the replacement volume name postfix to the original volume name has created a name that may not be a valid raw partition name. System Action: Replacement volume name is used in the recovery plan stanza. 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
Explanation: The specified command causes a mismatch in the number of directories for a device class and the number of directories in or more PATH definitions which reference the specified device class. LANFree operations can fail if a storage agent requires access to a directory for which there is no corresponding directory entry in its PATH definition. System Action: The server processes the command. User Response: Make sure that the directory definitions are consistent between the device class definition and storage agent PATH definitions. Storage Agent PATH definitions should have the same number of directories as the corresponding device class and should appear in the same order. Directory specifications for a device class can be reviewed by issued the QUERY DEVCLASS classname Format=Detailed command. Directory specifications for PATH definitions can be reviewed by issued the QUERY PATH servername drivename SRCT=SERVER DESTTYPE=DRIVE Format=Detailed command. 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. System Action: PREPARE uses the following default file names in the plan file: v For the server executable the default is /opt/IBMadsm-s/bin/dsmserv. v For the volume formatting program the default is /opt/IBMadsm-s/bin/dsmfmt.
570
IBM Tivoli Storage Manager: Messages
ANR9581W (Linux) ANR9583E (Linux)
volume is DISK or the device class device type is FILE. System Action: The entry for the volume is not included in the recovery plan stanza. User Response: Determine why file does not exist; create if necessary. ANR9581W (Linux) command: Volume file name not found while building stanza recovery plan stanza name. Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE. System Action: The entry for the volume is not included in the recovery plan stanza. User Response: Determine why file does not exist; create if necessary. ANR9581W (Solaris) Command: Volume file name not found while building stanza recovery plan stanza name. Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE. System Action: The entry for the volume is not included in the recovery plan stanza. User Response: Determine why file does not exist; create if necessary. ANR9582E (HP-UX) Command: Generated file name too long. Length of directory or prefix prefix plus name exceeds maximum characters characters. Explanation: The file name generated is too long. The maximum valid length is shown in the message. System Action: The recovery plan file was not created. User Response: Reissue the command specifying a 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 prefix plus name exceeds maximum characters characters. Explanation: The file name generated is too long. The maximum valid length is shown in the message. System Action: The recovery plan file was not created.
Chapter 3. Common and Platform Specfic Messages
User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE ANR9582E (Solaris) Command: Generated file name too long. Length of directory or prefix prefix plus name exceeds maximum characters characters. Explanation: The file name generated is too long. The maximum valid length is shown in the message. System Action: The recovery plan file was not created. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE ANR9583E (HP-UX) Command: Cannot generate fully qualified file name for name. Explanation: A failure occurred expanding the specified file name. System Action: Recovery plan file not created. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE ANR9583E (Linux) command: Cannot generate fully qualified file name for name. Explanation: A failure occurred expanding the specified file name. System Action: Recovery plan file not created. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE
571
ANR9583E (Solaris) ANR9600E
ANR9583E (Solaris) Command: Cannot generate fully qualified file name for name. Explanation: A failure occurred expanding the specified file name. System Action: Recovery plan file not created. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE ANR9584E (HP-UX) command: Cannot generate server options file name. Explanation: A failure occurred generating the server options file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9584E (Linux) command: Cannot generate server options file name. Explanation: A failure occurred generating the server options file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9584E (Solaris) Command: Cannot generate server options file name. Explanation: A failure occurred generating the server options file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9585E (HP-UX) Command: Cannot generate a volume history file name. Explanation: A failure occurred generating the volume history file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9585E (Linux) command: Cannot generate a volume history file name. Explanation: A failure occurred generating the volume history file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9585E (Solaris) Command: Cannot generate a volume history file name. Explanation: A failure occurred generating the volume history file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9586E (HP-UX) Command: Cannot generate a device configuration file name. Explanation: A failure occurred generating the device configuration file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9586E (Linux) command: Cannot generate a device configuration file name. Explanation: A failure occurred generating the device configuration file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9586E (Solaris) Command: Cannot generate a device configuration file name. Explanation: A failure occurred generating the device configuration file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9600E Invalid information passed to NETLS license interface.
Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients. System Action: Server operation continues. New licensing information is not used by the server.
572
IBM Tivoli Storage Manager: Messages
ANR9600E (Solaris) ANR9605E
User Response: Contact your service representative for assistance in resolving the error. ANR9600E (Solaris) Failed to allocate memory for shared memory communications. Error: error text. Explanation: An error has occurred when attempting to get memory for the shared communications option. System Action: Shared memory communications will not be activated. User Response: The maximum shared memory is, most likely, too small. To increase on SUN, update /etc/system with set shmsys:shminfo_shmmax=268435456 (a recommended size). ANR9601E The NETLS license interface was not initialized properly. ANR9602E (Solaris) Error errno while attaching memory segment for shared memory communications. Explanation: An error occurred while attempting to attach a shared memory segment for a shared communications session. System Action: The shared memory communications session does not initialize. User Response: Check the SUN documentation for the shmat subroutine and determine what the errno indicates, and take the appropriate action to correct the error. 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. System Action: Server operation continues. New licensing information is not used by the server. User Response: If the server is not running with root authority, make sure that directory authorities in the /usr/lib/netls/conf path are set so that the user ID under which the server is running can create, read, and write to the /usr/lib/netls/conf/nodelock file. If the server is running with root authority, contact your service representative for assistance in resolving this problem. ANR9604E The NETLS license interface encountered an internal error.
Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients. System Action: Server operation continues. New licensing information is not used by the server. User Response: Contact your service representative for assistance in resolving the error. 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. System Action: Shared memory communications will not be activated. User Response: If the error given is ENOSPC, the maximum number of system message queue have likely been exceeded. update /etc/system with set shmsys:msginfo_msgmni=100. Any other error suggests an internal problem and shoud be reported. ANR9602E Invalid JOB information passed to the NETLS Interface.
Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients. System Action: Server operation continues. New licensing information is not used by the server. User Response: Contact your service representative for assistance in resolving the error. ANR9605E An invalid vendor ID was passed to NETLS.
Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients. System Action: Server operation continues. New licensing information is not used by the server. User Response: Contact your service representative for assistance in resolving the error.
Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients. System Action: Server operation continues. New licensing information is not used by the server. User Response: Contact your service representative for assistance in resolving the error.
Chapter 3. Common and Platform Specfic Messages
573
ANR9606E ANR9612E
ANR9606E NETLS failed to find socket families to contact a server. 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. ANR9610E (Linux) Unable to create directory: directory. Explanation: The REGISTER LICENSE command is unable to either create or verify the specified directory structure. System Action: None. ANR9607E No NETLS Servers found. Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients. System Action: Server operation continues. New licensing information is not used by the server. User Response: Contact your service representative for assistance in resolving the error. ANR9608E A NETLS Security Breach was encountered. User Response: If the server is not running with root authority, make sure that directory authorities in the 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. ANR9610E (Solaris) Unable to create directory: directory. Explanation: The REGISTER LICENSE command is unable to either create or verify the specified directory structure. System Action: None. User Response: If the server is not running with root authority, make sure that directory authorities in the 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.
Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients. System Action: Server operation continues. New licensing information is not used by the server. User Response: Contact your service representative for assistance in resolving the error.
Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients. System Action: Server operation continues. New licensing information is not used by the server. User Response: Contact your service representative for assistance in resolving the error. ANR9609E Incorrect license entered: Password entered = password Annotation entered = annotation.
Explanation: The REGISTER LICENSE command is unable to either create or open the nodelock file. System Action: None. 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. ANR9612E Error writing to NODELOCK file.
Explanation: The license information entered for a REGISTER LICENSE command is not correct. System Action: None. 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. System Action: None. 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
Explanation: The REGISTER LICENSE command fails writing to the nodelock file. System Action: None. User Response: If the server is not running with root
574
IBM Tivoli Storage Manager: Messages
ANR9613W ANR9614E (Solaris)
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. ANR9613W Error loading modname for Licensing function: error string. ANR9613W (Solaris) 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: 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.
Explanation: The server cannot load file module modname to initialize licensing functions due to error error string. System Action: Server operation continues. Default licensing values are in effect for running the server. User Response: The dsmreg.lic module is accessed as part of the load process for licensing. It should be in the same directory as the dsmserv executable or it must be in a directory that is pointed to by the DSMSERV_DIR environment variable. The dsmreg.lic module is only installed when you purchase the product. ANR9613W (HP-UX) Error loading modname for 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 (Linux) Error loading modname for Licensing function. Explanation: The server cannot load file module modname to initialize licensing functions. System Action: Server operation continues. Default licensing values are in effect for running the server. 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.
Explanation: The REGISTER LICENSE command is unable to create or open the server license file. System Action: None. 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 representative for assistance. ANR9614E (Linux) Unable to open license file: file. Explanation: The REGISTER LICENSE command is unable to either create or open the server license file. System Action: None. 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 representative for assistance. ANR9614E (Solaris) Unable to open license file: file. Explanation: The REGISTER LICENSE command is unable to either create or open the server license file. System Action: None. 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 representative for assistance.
Chapter 3. Common and Platform Specfic Messages
575
ANR9615E ANR9617W (Linux)
ANR9615E Error writing to adsmserv.licenses file. ANR9616W (Linux) Invalid license record record value found in license file - it will be ignored. Explanation: The license manager found an invalid record in the server license file (adsmserv.licenses). The record is ignored. System Action: The invalid record is ignored. User Response: Erase the adsmserv.licenses file and reregister your licenses. Refer to the licenses provided to you to ensure that only valid licenses are specified with the REGISTER LICENSE command. ANR9616W (Solaris) Invalid license record record value found in license file - it will be ignored. Explanation: The license manager found an invalid record in the server license file (adsmserv.licenses). The record is ignored. System Action: The invalid record is ignored. User Response: Erase the adsmserv.licenses file and reregister your licenses. 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 REGISTER LICENSE command fails writing to the server license file. System Action: None. 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. 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 representative for assistance. ANR9615E (Linux) Error writing to adsmserv.licenses file. Explanation: The REGISTER LICENSE command fails writing to the server license file. System Action: None. 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. Explanation: The REGISTER LICENSE command fails writing to the server license file. System Action: None. 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.
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 service representative. ANR9617W (Linux) 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 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.
Explanation: The license manager found an invalid record in the server license file (adsmserv.licenses). The record is ignored. System Action: The invalid record is ignored. User Response: Erase the adsmserv.licenses file and reregister your licenses.
576
IBM Tivoli Storage Manager: Messages
ANR9617W (Solaris) ANR9623I
ANR9617W (Solaris) 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 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. terms are not changed by the REGISTER LICENSE command. User Response: The license authorization file is required for formal licensing for the server. The file is delivered when the server is purchased, but is not available in the product service stream or with demonstration copies of the server. If you have purchased the server, please contact your service representation for assistance in resolving this problem. ANR9622I An EVALUATION LICENSE for support of Tivoli Space Management will expire on expiration date.
Explanation: The REGISTER LICENSE command fails because the license authorization module cannot be found. System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command. User Response: The license authorization file is required for formal licensing for the AIX/6000 server. The file is delivered when the product is purchased, but it is not available in the product service stream or with demonstration copies of the server. If you have purchased the server, contact your service representative for assistance in resolving this problem. ANR9618E (Linux) License registration is not supported on this server. Explanation: The REGISTER LICENSE command failed because the license authorization module could not be found. System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command. User Response: The license authorization file is required for formal licensing for the server. The file is delivered when the product is purchased, but is not available in the product service stream or with demonstration copies of the server. If you have purchased the server, please contact your service representation for assistance in resolving this problem. ANR9618E (Solaris) License registration is not supported on this server. Explanation: The REGISTER LICENSE command failed because the license authorization module could not be found. System Action: Server operation continues; licensing
Explanation: The AIX/6000 server is distributed with an evaluation license for Tivoli Space Management support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms. System Action: The Tivoli Space Management license allows clients to utilize the server for storing files migrated during space management. The server checks this license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Space Management after the expiration date shown. ANR9623I An EVALUATION LICENSE for support of Tivoli Disaster Recovery Manager will expire on expiration date.
Explanation: The AIX/6000 server is distributed with an evaluation license for Tivoli Disaster Recovery Manager support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms. System Action: The Tivoli Disaster Recovery Manager license allows customers to store information in the server regarding machines and recovery media, allows management of offsite recovery media, collects and stores information in the server for server recovery and allows data base and storage pool backups to a device class of type server. The server checks this license when machines or recovery media are defined to the server, when PREPARE or MOVE DRMMEDIA are invoked and when a data base backup or storage pool backup to a device class of type server are performed to ensure that the server is licensed to perform this function. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation
Chapter 3. Common and Platform Specfic Messages
577
ANR9624E ANR9624I (Windows)
period has elapsed. Without formal licenses, the server 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. this license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Space Management after the expiration date shown. ANR9624I (Solaris) An EVALUATION LICENSE for support of Tivoli Space Management will expire on expiration date. Explanation: The server is distributed with an evaluation license for Tivoli Space Management support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms. System Action: The Tivoli Space Management license allows clients to utilize the server for storing files migrated during space management. The server checks this license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Space Management after the expiration date shown. ANR9624I (Windows) An EVALUATION LICENSE for support of Tivoli Space Management will expire on expiration date. Explanation: The server is distributed with an evaluation license for Tivoli Space Management support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms. System Action: The Tivoli Space Management license allows clients to utilize the server for storing files migrated during space management. The server checks this license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Space Management after the expiration date shown.
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 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 will expire on expiration date. Explanation: The server is distributed with an evaluation license for Tivoli Space Management support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms. System Action: The Tivoli Space Management license allows clients to utilize the server for storing files migrated during space management. The server checks this license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Space Management after the expiration date shown. ANR9624I (Linux) An EVALUATION LICENSE for support of Tivoli Space Management will expire on expiration date. Explanation: The server is distributed with an evaluation license for Tivoli Space Management support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms. System Action: The Tivoli Space Management license allows clients to utilize the server for storing files migrated during space management. The server checks
578
IBM Tivoli Storage Manager: Messages
ANR9625E ANR9625I (Windows)
ANR9625E Could not open file file name. 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. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Disaster Recovery Manager after the expiration date shown. ANR9625I (Solaris) An EVALUATION LICENSE for support of Tivoli Disaster Recovery Manager will expire on expiration date. Explanation: The 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 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. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Disaster Recovery Manager after the expiration date shown. ANR9625I (Windows) An EVALUATION LICENSE for support of Tivoli Disaster Recovery Manager will expire on expiration date. Explanation: The 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 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
Chapter 3. Common and Platform Specfic Messages
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 service representative. ANR9625I (HP-UX) An EVALUATION LICENSE for support of Tivoli Disaster Recovery Manager will expire on expiration date. Explanation: The 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 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. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Disaster Recovery Manager after the expiration date shown. ANR9625I (Linux) An EVALUATION LICENSE for support of Tivoli Disaster Recovery Manager will expire on expiration date. Explanation: The 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 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
579
ANR9626E ANR9632I (Windows)
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. User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Disaster Recovery Manager after the expiration date shown. ANR9626E Invalid license certificate file: file name. installed correctly. If the installation was successful, re-boot your system and re-start the server. If this message continues to be issued, contact your service representative. ANR9629E (Windows) 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 service representative. ANR9630E (Windows) 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. 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 service representative. ANR9631E (Windows) 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 DSMSER-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. 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.
Explanation: The specified file does not contain valid license certificate information. System Action: The license registration command ignores the contents of the file. 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 service representative. 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. ANR9628E (Windows) 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 server installation. Check to make sure that the product was
580
IBM Tivoli Storage Manager: Messages
ANR9634E ANR9635E (HP-UX)
System Action: Server licensing asumes Try and Buy mode with licenses for 180 days. User Response: The named DLL library(ies) are required for the server to support feature licensing. If you are running an evaluation copy of the server, this message should not cause concern and is normal. If the libraries are installed and this message continues to be issued, contact a support representative for assistance. ANR9634E command name: No license certificate files were found with the file name specification specification. 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 service representative. ANR9634E (Solaris) 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. 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 service representative. ANR9634E (Windows) 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. 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 service representative. ANR9635E (HP-UX) 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. 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 service representative.
Explanation: The server did not find any license certificate file(s) with the file name specification entered. 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. 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, contact your service representative. ANR9634E (HP-UX) 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. 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 service representative. ANR9634E (Linux) 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.
Chapter 3. Common and Platform Specfic Messages
581
ANR9635E (Linux) ANR9637E (HP-UX)
ANR9635E (Linux) 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. 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 service representative. ANR9635E (Solaris) 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. 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 service representative. ANR9635E (Windows) 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. 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 service representative. ANR9636E (HP-UX) 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 service representative. ANR9636E (Linux) 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 service representative. ANR9636E (Solaris) 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 service representative. ANR9636E (Windows) 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 service representative. ANR9637E (HP-UX) 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
582
IBM Tivoli Storage Manager: Messages
ANR9637E (Linux) ANR9638W (Solaris)
corrections have been made, contact your service representative. ANR9637E (Linux) 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. ANR9637E (Solaris) 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. ANR9637E (Windows) 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 DSMSER-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. ANR9638W (HP-UX) License registration is not supported on this server. Explanation: The REGISTER LICENSE command fails because the license authorization module cannot be found. System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command. User Response: The license authorization file is 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 demonstration copies of the server. If you have purchased the server, contact your service representative for assistance in resolving this problem. ANR9638W (Linux) License registration is not supported on this server. Explanation: The REGISTER LICENSE command fails because the license authorization module cannot be found. System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command. User Response: The license authorization file is required for formal licensing for the 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. ANR9638W (Solaris) License registration is not supported on this server. Explanation: The REGISTER LICENSE command fails because the license authorization module cannot be found. System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command. User Response: The license authorization file is 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 demonstration copies of the server. If you have purchased the server, contact your service representative for assistance in resolving this problem.
Chapter 3. Common and Platform Specfic Messages
583
ANR9638W (Windows) ANR9641W (HP-UX)
ANR9638W (Windows) License registration is not supported on this server. Explanation: The REGISTER LICENSE command fails because the license authorization module cannot be found. System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command. User Response: The license authorization file is required for formal licensing for the Windows server. The file is delivered when the product is purchased, but it is not available in the product service stream or with demonstration copies of the server. If you have purchased the server, contact your service representative for assistance in resolving this problem. ANR9639W (HP-UX) Unable to load shared library shared library. Explanation: The server module is unable to load the indicated shared library. System Action: Server operation continues, but the 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. ANR9639W (Linux) Unable to load Shared License File shared library. Explanation: The server was unable to loaded the shared library. System Action: Server operation continues, but 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. System Action: Server operation continues, but 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. Explanation: The server module is unable to load the address of a routine in the indicated shared library. System Action: Server operation continues, but the function that requires the shared library will be inoperative. User Response: Ensure that the shared library is accessible. If the problem persists, contact your service representative. ANR9640E (Linux) Unable to load procedure address from shared library shared library license module. Explanation: The server module is unable to load the address of a routine in the indicated shared library for license loading. System Action: Server operation continues, but the function that requires the shared library will be inoperative. User Response: Ensure that the shared library is accessible. If the problem persists, contact your Customer Service Representative. ANR9640E (Solaris) Unable to load procedure address from shared library shared library license module. Explanation: The server module is unable to load the address of a routine in the indicated shared library for license loading. System Action: Server operation continues, but the function that requires the shared library will be inoperative. User Response: Ensure that the shared library is 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. System Action: Server operation continues. 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
584
IBM Tivoli Storage Manager: Messages
ANR9641W (Linux) ANR9654E (Solaris)
appear after re-registering the proper licenses. If this message persists, contact your service representative. ANR9641W (Linux) One or more EVALUATION LICENSES will expire on expiration date. System Action: Server operation continues. 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 persists, contact your service representative. ANR9641W (Solaris) One or more EVALUATION LICENSES will expire on expiration date. System Action: Server operation continues. 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 persists, contact your service representative. 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. Server operation continues. 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. Server operation continues. 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 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 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. ANR9653E (Solaris) 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 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. ANR9654E (HP-UX) 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 service representative. ANR9654E (Solaris) 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,
Chapter 3. Common and Platform Specfic Messages
585
ANR9655E (HP-UX) ANR9676E (HP-UX)
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 service representative. ANR9655E (HP-UX) 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. 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 service representative. ANR9655E (Solaris) 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. 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 service representative. ANR9656E (HP-UX) 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. ANR9656E (Solaris) 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. ANR9676E Error errno attaching memory segment for shared memory communications.
Explanation: An error occurred while attempting to attach a shared memory segment for a shared communications session. System Action: The shared memory communications session does not initialize. User Response: Check the AIX documentation for the shmat subroutine and determine what the error number indicates. On AIX, if the error number is EMFILE, make sure the EXTSHM environment variable is set to ON before starting the server. This allows the server to support more than 3 concurrent shared memory sessions. ANR9676E (HP-UX) Error errno attaching memory segment for shared memory communications. Explanation: An error occurred while attempting to attach a shared memory segment for a shared communications session. System Action: The shared memory communications session does not initialize. User Response: Check the AIX documentation for the shmat subroutine and determine what the error number indicates. On AIX, if the error number is EMFILE, make sure the EXTSHM environment variable is set to ON before starting the server. This allows the server to support more than 3 concurrent shared memory sessions.
586
IBM Tivoli Storage Manager: Messages
ANR9676E (Linux) ANR9679W (Windows)
ANR9676E (Linux) Error errno attaching memory segment for shared memory communications. Explanation: An error occurred while attempting to attach a shared memory segment for a shared communications session. System Action: The shared memory communications session does not initialize. User Response: Check the AIX documentation for the shmat subroutine and determine what the error number indicates. On AIX, if the error number is EMFILE, make sure the EXTSHM environment variable is set to ON before starting the server. This allows the server to support more than 3 concurrent shared memory sessions. ANR9677E Failed to allocate memory for shared memory communications. Error: error text. ANR9678E (HP-UX) 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. System Action: Shared memory communications will not be activated. User Response: None. ANR9678E (Linux) 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. System Action: Shared memory communications will not be activated. User Response: None. 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. User Response: None. ANR9679W Command: Unable to locate file file name.
Explanation: An error has occurred when attempting to get memory for the shared communications option. System Action: Shared memory communications will not be activated. ANR9677E (HP-UX) Failed to allocate memory for shared memory communications. Error: error text. Explanation: An error has occurred when attempting to get memory for the shared communications option. System Action: Shared memory communications will not be activated. User Response: None. ANR9677E (Linux) Failed to allocate memory for shared memory communications. Error: error text. Explanation: An error has occurred when attempting to get memory for the shared communications option. System Action: Shared memory communications will not be activated. User Response: None. ANR9678E Failed to allocate message queue for the shared memory communications Error: error text.
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 /usr/tivoli/tsm/server/bin/dsmserv. v For the volume formatting program the default is /usr/tivoli/tsm/server/bin/dsmfmt. User Response: Determine why file does not exist; create if necessary. ANR9679W (Windows) Command: Unable to locate file file name. Explanation: The specified file cannot be found. System Action: PREPARE uses the following default file names in the plan file: v For the server executable the default is c:\progra~1\tivoli\tsm\server\dsmserv.
Chapter 3. Common and Platform Specfic Messages
Explanation: An error has occurred when attempting to get memory for the shared communications option. System Action: Shared memory communications will not be activated.
587
ANR9680W ANR9681W (Windows)
User Response: Determine why file does not exist; create if necessary. ANR9680W Command: Could not obtain AIX logical volume information for volume name while building stanza recovery plan stanza name. ANR9680W (Windows) Unable to locate path for component in registry. Explanation: The path to the component could not be found in the registry. System Action: PREPARE uses the following default path names in the plan file: v For the components installation directory the default is c:\progra~1\tivoli\tsm\server\ v For the administrative command line client the default is c:\progra~1\tivoli\tsm\baclient\ v For the disk formatting utility the default is c:\progra~1\tivoli\tsm\utils\ User Response: Determine why path does not exist; install components if necessary. ANR9681W ANR9680W (HP-UX) Command: Could not obtain logical volume information for volume name while building stanza recovery plan stanza name. Explanation: This volume is defined to the server but PREPARE can not obtain logical volume information for it. System Action: The entry for the volume is not included in the recovery plan stanza. User Response: This message should be preceded by another error message which contains an error code. ANR9680W (S/390) 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 (Solaris) Command: Could not obtain logical volume information for volume name while building stanza recovery plan stanza name. Explanation: This volume is defined to the server but PREPARE can not obtain logical volume information for it. System Action: The entry for the volume is not included in the recovery plan stanza. User Response: This message should be preceded by another error message which contains an error code. Command: Volume file name not found while building stanza recovery plan stanza name.
Explanation: This volume is defined to the server but PREPARE can not obtain AIX logical volume information for it from the AIX Object Data Manager (ODM). System Action: The entry for the volume is not included in the recovery plan stanza. User Response: This message should be preceded by another error message which contains the ODM error code.
Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE. System Action: The entry for the volume is not included in the recovery plan stanza. User Response: Determine why the file does not exist; create it if necessary. ANR9681W (S/390) Command: Volume file name not found while building stanza recovery plan stanza name. Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE. System Action: The entry for the volume is not included in the recovery plan stanza. User Response: Determine why file does not exist; create if necessary. ANR9681W (Windows) Command: Volume file name not found while building stanza recovery plan stanza name. Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE. System Action: The entry for the volume is not included in the recovery plan stanza. User Response: Determine why file does not exist; create if necessary.
588
IBM Tivoli Storage Manager: Messages
ANR9682E ANR9684E (S/390)
ANR9682E Command: Generated file name too long. Length of directory or prefix 'prefix' plus 'name' exceeds maximum characters characters. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE ANR9683W (S/390) Command: Cannot generate fully qualified file name for name. Prepare will substitute file name default name. Explanation: The fully qualified name for the volume 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 (Windows) Command: Cannot generate fully qualified file name for name. Explanation: A failure occurred expanding the specified file name. System Action: Recovery plan file not created. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE ANR9684E Command: Cannot generate server options file name.
Explanation: The file name generated is too long. The maximum valid length is shown in the message. System Action: The recovery plan file was not created. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE ANR9682E (S/390) Command: Generated file name too long. Length of directory or prefix prefix plus name exceeds maximum characters characters. Explanation: The file name generated is too long. The maximum valid length is shown in the message. System Action: The recovery plan file was not created. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE ANR9682E (Windows) Command: Generated file name too long. Length of directory or prefix prefix plus name exceeds maximum characters characters. Explanation: The file name generated is too long. The maximum valid length is shown in the message. System Action: The recovery plan file was not created. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX v SET DRMINSTRPREFIX v PREPARE ANR9683E Command: Cannot generate fully qualified file name for 'name'.
Explanation: A failure occurred generating the server options file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9684E (S/390) Command: Cannot generate fully qualified file name for name. Explanation: A failure occurred creating the specified file name. System Action: Recovery plan file not created. User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix: v SET DRMPLANPREFIX
Chapter 3. Common and Platform Specfic Messages
Explanation: A failure occurred expanding the specified file name. System Action: Recovery plan file not created.
589
ANR9684E (Windows) ANR9712E
v SET DRMINSTRPREFIX v PREPARE ANR9684E (Windows) Command: Cannot generate server options file name. Explanation: A failure occurred generating the server options file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9685E Command: Cannot generate a volume history file name. ANR9686E (Windows) Command: Cannot generate a device configuration file name. Explanation: A failure occurred generating the device configuration file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9690W (S/390) Command: Cannot obtain help file name. Explanation: Help file name cannot be obtained. HLPAMENG will not be included in the START.SERVER stanza of the plan file. System Action: Processing continues. User Response: None. ANR9691W (S/390) 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. System Action: Processing continues. User Response: None. ANR9710E Insufficient memory to continue operations.
Explanation: A failure occurred generating the volume history file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9685E (S/390) 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. System Action: The recovery plan file was not created. User Response: Catalog the options file. ANR9685E (Windows) Command: Cannot generate a volume history file name. Explanation: A failure occurred generating the volume history file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information. ANR9686E Command: Cannot generate a device configuration file name.
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 Unrecognized argument argument.
Explanation: The specified argument is not recognized as one that is supported by the label utility program. System Action: The program is halted. User Response: Retry the label utility program with the correct argument syntax. ANR9712E Argument has invalid value argument.
Explanation: A failure occurred generating the device configuration file name. System Action: Recovery plan file not created. User Response: See accompanying messages for more information.
Explanation: The value specified for the given argument is not valid. System Action: The program is halted. User Response: Retry the label utility program with the correct argument syntax.
590
IBM Tivoli Storage Manager: Messages
ANR9713E ANR9723I
ANR9713E Only one library can be specified. ANR9719E Too many drives were specified.
Explanation: Only one library can be specified in the argument list for the label utility program. System Action: The program is halted. User Response: Retry the label utility program with the correct argument syntax. ANR9714E No drives were specified.
Explanation: The number of drives specified on the command line exceeds the limits of the program. System Action: The program is halted. User Response: Retry the operation, specifying only up to the maximum number of supported drives. The program can be invoked with the -help argument to determine this maximum value. ANR9720I Volume volume name was labeled successfully using drive drive name.
Explanation: At least one drive must be specified for use by the label utility (DSMLABEL) program. System Action: The program is halted. User Response: Retry the label utility program with the correct argument syntax. ANR9715E Error starting label activity for drive drive name.
Explanation: The volume is successfully labeled. System Action: The program continues operation. User Response: None. ANR9721E Volume name is not a valid volume name.
Explanation: The label utility is unable to start its activity for the given drive. System Action: The program is halted. User Response: Increase the number of allowed threads or processes in the system, then retry the operation. ANR9716E Device library name is not accessible, or is not recognized as a supported library type.
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. ANR9722I 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 device specified for the library cannot be accessed or is not recognized as a supported device. System Action: The program is halted. User Response: Retry the operation, specifying a valid supported library. ANR9717E Element address element address is not valid for drive drive name.
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:
Explanation: The specified element address does not represent a valid drive location in the associated library. System Action: The program is halted. User Response: Retry the operation, specifying a valid 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. System Action: The program is halted. User Response: Retry the operation, specifying a valid supported drive.
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.
Chapter 3. Common and Platform Specfic Messages
591
ANR9724I ANR9732I
User Response: Mount side A of a new volume, then type a volume name for it and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name. ANR9724I Flip the volume in drive drive name to side B, then press ENTER. System Action: All further activity on the given drive is suspended. User Response: Ensure that the drive is in proper operating condition before resuming its use. ANR9729E 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. System Action: The program waits for the ENTER key to be pressed. User Response: Flip the volume in the drive, and press ENTER. ANR9725E The volume in drive drive name is already labeled (volume name).
Explanation: An I/O error occurs while attempting to format the media for the specified volume in the given drive. System Action: The volume is not labeled. 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. System Action: The volume is not labeled. User Response: If an overwrite of the existing label with a new label is desired, restart the DSMLABEL utility program by using the -overwrite argument. ANR9726E I/O error writing label for volume volume name in drive drive name.
Explanation: The specified library device requires manual intervention before it can be accessed for normal operations. System Action: The operation will be retried periodically until either the required action is performed or a timeout occurs. User Response: If the library has an access door, make sure it is in the closed position. If it has a cartridge carousel, make sure the carousel is installed. ANR9731I 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:
Explanation: An I/O error occurs while attempting to write the label for the specified volume in the given drive. System Action: The volume is not labeled. User Response: Ensure that the volume is not write protected, the drive is powered on and ready, and the device parameter has the correct value. ANR9727E Media fault detected on volume volume name in drive drive name.
Explanation: The program prompts for a new volume to be mounted in the entry/exit port of the given library so that a label can be written to it. System Action: The program waits for the volume name to be entered. User Response: Insert a new volume into the entry/exit port, then type a volume name for it and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name. ANR9732I Insert a new volume in the entry/exit port of library library device name with side A facing up, then enter the name (1-maximum length characters) to be used for its label; or just press ENTER to quit this program:
Explanation: A media fault condition is detected for the specified volume in the given drive. System Action: The volume is not labeled. 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. ANR9728E Error ejecting volume from drive drive name.
Explanation: An error occurs while ejecting the volume from the given drive.
Explanation: The program prompts for a new volume to be mounted in the entry/exit port of the given library so that a label can be written to it.
592
IBM Tivoli Storage Manager: Messages
ANR9733I ANR9740E
System Action: The program waits for the volume name to be entered. User Response: Insert a new volume into the entry/exit port, then type a volume name for it and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name. ANR9733I Insert a new volume in drive drive name of library library device name, then enter the name (1-maximum length characters) to be used for its label; or just press ENTER to quit this program: ANR9736E An I/O error occurred while accessing library device library device name.
Explanation: An attempted I/O operation for the given library failed. System Action: If the error is noncritical, operation continues; otherwise, the program is halted. User Response: Ensure that the library device is 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: 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, 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. 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:
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.
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 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:
Explanation: All activity associated with the volume in the entry/exit port 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 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. User Response: None. ANR9740E 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. System Action: The program waits for the volume name to be entered. User Response: Type the name for the next volume to be labeled and then press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.
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. System Action: The volume is not labeled. User Response: If you are sure the volume contains
Chapter 3. Common and Platform Specfic Messages
593
ANR9741E ANR9749I
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. ANR9741E Drives drive name and drive name cannot use the same element address. User Response: Retry the program, specifying at most one trace argument. ANR9746E Unable to open trace file file name.
Explanation: An error occurs while opening the specified file for writing trace data. System Action: The program is halted. User Response: Retry the program, specifying a valid file name for the trace file. ANR9747I Unable to write to trace file.
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: 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 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:
Explanation: The element address value for the specified drive is omitted, or an illegal value has been provided. System Action: The program is stopped. User Response: Restart the program, providing a valid element address. Appropriate values can be determined with the worksheets in Administrators Guide. ANR9743I Attempting to label volume volume name using drive drive name...
Explanation: The specified volume is in the process of being labeled in the given drive. System Action: Labeling activity continues. User Response: None. ANR9744E Volume volume name is not present in library library name.
Explanation: The program prompts for a new volume 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. System Action: The program waits for the volume 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 (1-maximum length characters) to be used for its label; or just press ENTER to quit this program:
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 retry the operation. ANR9745E Only one trace argument is allowed.
Explanation: More than one trace argument has been encountered, but only one is allowed. System Action: The program is halted.
Explanation: The program prompts for a new volume 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.
594
IBM Tivoli Storage Manager: Messages
ANR9750I ANR9758W
System Action: The program waits for the volume name to be entered. User Response: Insert side A of a new volume, close the library access door, type a volume name for it, and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name. ANR9750I Remove the volume from slot with element number slot element address in library library device name, then press ENTER. 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: All activity associated with the volume 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. System Action: The program waits until the ENTER key is pressed. User Response: Remove the volume from the specified slot, close the library access door, and press ENTER. ANR9751E The volume in drive drive name is not compatible with the drive.
Explanation: The hardware did not return any valid barcode data for any cartridge. System Action: The program terminates without attempting to label any cartridges. User Response: Make sure the hardware supports barcodes, or that barcode labels have been affixed to the cartridges. ANR9756I No volumes were found.
Explanation: The volume cannot be used in the drive. It is most likely an outdated media type that the drive cannot write. System Action: The volume is not labeled. 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.
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 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. System Action: The program is halted. User Response: Retry the operation, specifying a valid drive id for the drive. ANR9758W Error mounting volume volume name.
Explanation: The specified drive cannot be accessed. System Action: The program is halted. 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.
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.
Chapter 3. Common and Platform Specfic Messages
595
ANR9759E ANR9778E
ANR9759E unsuccessful ACSAPI response, status=acs status. ANR9774W Volume volume name should be freed of data as soon as possible.
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 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: 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. System Action: None. User Response: Monitor the ACSSA console and wait. ANR9771E Volume volume name has an incorrect barcode label describing the volumes WORM type.
Explanation: An I/O error has occurred while writing on the specified volume. System Action: The operation fails. 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: 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 mislabelled. 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. ANR9773E Hardware configuration error in library library name: number of drives drives, number of storage slots storage slots.
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. System Action: The operation continues. User Response: None. ANR9778E Unable to establish a communication session with the primary library manager.
Explanation: The library device retuned 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. System Action: The operation fails. User Response: Configure the drives to the operating system, and reinitialize the library.
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. System Action: None. User Response: Verify the primary library manager is up and operational. Once the server is verified to be operational, retry the operation.
596
IBM Tivoli Storage Manager: Messages
ANR9779E ANR9788E
ANR9779E Unable to acquire a drive for volume volume name from the library manager. ANR9783E Primary Library Manager does not contain a valid value.
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 System Action: None. 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: The primary library manager server has not be defined to this server. System Action: None. User Response: Define the server to this server using the DEFINE SERVER command. 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. System Action: None. User Response: Define the server to this server using the DEFINE SERVER command. 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. System Action: None. User Response: Verify drive name with the library manager. ANR9786E A communication error has occurred. Operation ending.
Explanation: A communication error occurred while dismount the volume. System Action: None. User Response: Verify the library manager is up and operational. Verify that the library manager and library client can communicate using command routing. ANR9781E Volser volume name was not found to be mounted on the library manager.
Explanation: A communication error occurred. System Action: None. User Response: Verify the library manager is up and operational. Verify that the library manager and library client can communicate using command routing. ANR9787E The owner name specified is not defined to this server.
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. System Action: None. User Response: Verify that the volume has been dismounted. ANR9782E Primary Library Manager primary library manager name is NOT defined as a server.
Explanation: A command was issued specifying ownership of a volume. The name of the owner given was not defined to this server. System Action: None. User Response: Define the server to this server using the DEFINE SERVER command. ANR9788E Command: Library library name is not defined - the primary library manager not defined.
Explanation: The primary library manager server has not be defined to this server. System Action: None. User Response: Define the server to this server using the DEFINE SERVER command.
Explanation: The designated library is not defined because the primary library manager is not defined as a server to this server. System Action: The command is not processed.
Chapter 3. Common and Platform Specfic Messages
597
ANR9789E ANR9797E
User Response: Define the server to this server using the DEFINE SERVER command. ANR9789E Command: Library library name is not defined - the secondary library manager not defined. System Action: The background process operation is being terminated. User Response: None. ANR9794E Unable to load the RSM dynamic link library dynamic link library.
Explanation: The designated library is not defined because the secondary library manager is not defined as a server to this server. System Action: The command is not processed. User Response: Define the server to this server using the DEFINE SERVER command. ANR9790W Request to mount volume Volume Name for library client Library Client Name failed.
Explanation: The server module is unable to load the indicated dynamic link library. System Action: Server operation continues, but the 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: A library client requested a volume to be mount by the library manager, which in turn failed. System Action: None. 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: The designated storage agent name is invalid; either it contains too many characters, or some of the characters are invalid. System Action: The command is not processed. User Response: Reissue the command using a valid 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: In a shared library, the volume ownership has been changed from current owner to new owner. System Action: None. User Response: None. ANR9792E Library Library Name on library manager Library Manager Name is currently not being shared.
Explanation: The designated drive mapping cannot be defined because it has already been defined for the specified drive, library, and storage agent. System Action: The command is not processed. User Response: If you want to define an additional 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: A define library command attempted to define a shared library that was not being shared by the library manager. System Action: None. 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.
Explanation: The designated drive map has not been defined for the given drive in the given library on the given storage agent. System Action: The command is not processed. User Response: Reissue the command using a different drive name. If appropriate, define the drive before retrying the command.
Explanation: In response to a QUERY PROCESS command, this message displays the status for a process on the server. The command was started, but the process was canceled by an administrator.
598
IBM Tivoli Storage Manager: Messages
ANR9798E ANR9900W (Linux)
ANR9798E Command: One or more paths are still defined for drive drive name in library library name. 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. System Action: Processing continues. User Response: None. 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. System Action: Processing continues. User Response: None. ANR9900W Attention -- Accounting records could not be written to the file: filespec.
Explanation: The designated drive cannot be deleted because there are still paths defined for it. System Action: The command is not processed. User Response: Delete all paths for the drive, and reissue the command. 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. System Action: None. User Response: Verify the library on the library manager is being shared. If the library is not being 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 server detects an error while trying to open the accounting file. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9900W (HP-UX) Attention -- Accounting records could not be written to the file: file name. Explanation: The server detects an error while trying to open the accounting file. System Action: Server processing continues, but no accounting records are written. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9900W (Linux) Attention -- Accounting records could not be written to the file: file name. Explanation: The server detects an error while trying to open the accounting file. System Action: Server processing continues, but no accounting records are written. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.
Explanation: The command attempted to perform an operation that is not allowed unless the library is allowed to be shared. System Action: None. User Response: Verify the library on the library manager is being shared. If the library is not being 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. System Action: Processing continues. User Response: None. 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
Chapter 3. Common and Platform Specfic Messages
599
ANR9900W (Solaris) ANR9902W (Linux)
ANR9900W (Solaris) Attention -- Accounting records could not be written to the file: file name. Explanation: The server detects an error while trying to open the accounting file. System Action: Server processing continues, but no accounting records are written. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9900W (Windows) Attention -- Accounting records could not be written to the file: filespec. Explanation: The server detects an error while trying to open the accounting file. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9901W Attention -- Accounting records could not be written to the file: filespec. ANR9901W (Solaris) Attention -- Accounting records could not be written to the file: file name. Explanation: The server detects an error while trying to write an accounting record. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9901W (Windows) Attention -- Accounting records could not be written to the file: filespec. Explanation: The server detects an error while trying to write an accounting record. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9902W Attention -- Accounting records could not be written to the file: filespec.
Explanation: The server detects an error while trying to write an accounting record. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9901W (HP-UX) Attention -- Accounting records could not be written to the file: file name. Explanation: The server detects an error while trying to write an accounting record. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9901W (Linux) Attention -- Accounting records could not be written to the file: file name. Explanation: The server detects an error while trying to write an accounting record. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.
Explanation: The server detects an error while trying to close the accounting file. System Action: Server processing continues. User Response: Ensure that sufficient disk space is available and that the accounting file is not marked as read-only. ANR9902W (HP-UX) Attention -- Accounting records could not be written to the file: file name. Explanation: The server detects an error while trying to close the accounting file. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9902W (Linux) Attention -- Accounting records could not be written to the file: file name. Explanation: The server detects an error while trying to close the accounting file. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.
600
IBM Tivoli Storage Manager: Messages
ANR9902W (Solaris) ANR9952E (Windows)
ANR9902W (Solaris) Attention -- Accounting records could not be written to the file: file name. Explanation: The server detects an error while trying to close the accounting file. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only. ANR9902W (Windows) Attention -- Accounting records could not be written to the file: filespec. Explanation: The server detects an error while trying to close the accounting file. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as 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. System Action: Server processing continues. User Response: Consider increasing the maximum thread count on the system. 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. System Action: Server processing continues. User Response: Try the operation again later. ANR9950W (S/390) Attention -- License option could not be written to the file: filespec. Explanation: The server detects an error while trying to write to the options file. System Action: Server processing continues. User Response: Ensure that sufficient disk space is 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. Explanation: The server detects an error while trying to write to the options file. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the options file is not marked as read-only. ANR9951W (S/390) Attention -- License option could not be written to the file: filespec. Explanation: The server detects an error while trying to write to the options file. System Action: Server processing continues. User Response: Ensure that sufficient disk space is 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. Explanation: The server detects an error while trying to close the options file. System Action: Server processing continues. User Response: Ensure that there is sufficient disk space and that the options file is not marked as read-only. ANR9952E (S/390) Command: Incorrect value specified for licensed storage capacity - value. Explanation: The specified command has been issued with an incorrect value. System Action: Server operation continues, but the command is not processed. User Response: Reissue the command using a valid value. ANR9952E (Windows) Command: Invalid value specified for licensed storage capacity value. Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command using a valid value.
Chapter 3. Common and Platform Specfic Messages
601
ANR9953E (S/390) ANR9959W (Windows)
ANR9953E (S/390) Command: Invalid value specified for number of licensed clients - value. Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Reissue the command using a valid value. ANR9953E (Windows) Command: Invalid value specified for number of licensed clients - value. Explanation: The specified command has been issued with an invalid value. System Action: Server operation continues, but the command is not processed. User Response: Issue the command using a valid value. ANR9954S (S/390) The server is not licensed for use on this system. Explanation: DFSMS/MVS Feature server is not defined as licensed for this system to use in SYS1.PARMLIB member IGDDFPKG. System Action: The server operation ends. User Response: If you are licensed to use the server, update the IGDDFPKG member in SYS1.PARMLIB to set the correct value that enables the server. Either start task DFSMSPKG or reIPL. ANR9955W (Windows) Unable to load dynamic link library dynamic link library. Explanation: The server module is unable to load the indicated dynamic link library. System Action: Server operation continues, but the function that requires the dynamic link library will be 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. Explanation: The server module is unable to load the address of a routine in the indicated dynamic link library. System Action: Server operation continues, but the function that requires the dynamic link library will be 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 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 i usually the case when you have been using evaluation licenses prior to purchasing the server for Windows. System Action: Server operation continues. 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 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 persists, contact your service representative. ANR9958W (Windows) Node entry node name was removed from this servers definition in Active Directory. Explanation: In response to a REMOVE NODE command, the requested backup-archive node has been removed from this servers definition in Active Directory. System Action: None. User Response: None. ANR9959W (Windows) Node entry node name was not removed from this servers definition in Active Directory. Explanation: In response to a REMOVE NODE command, the requested backup-archive node has not been removed from this servers definition in Active Directory. System Action: None. 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.
602
IBM Tivoli Storage Manager: Messages
ANR9960W (Windows) ANR9969E (Windows)
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. System Action: None. User Response: None. 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. System Action: None. User Response: To register a node entry in the Active Directory, the option adregister has to be set to yes in the server options file. A domain controller must also be available. The Active Directory Configuration wizard can be used to manually update the server definition. ANR9962W (Windows) Node entry node name was renamed in this servers definition in Active Directory. Explanation: In response to a RENAME NODE command, the requested backup-archive node has been renamed to the new name shown. System Action: None. User Response: None. ANR9963W (Windows) Node entry node name was not renamed in this servers definition in Active Directory. Explanation: In response to a RENAME NODE command, the requested backup-archive node has not been renamed. System Action: None. 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. System Action: Server operation continues. 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. ANR9968I (Windows) Success accessing Active Directory. Explanation: Active Directory Server could be contacted. System Action: User Response: None. ANR9966I (Windows) NodeName node name. Explanation: The NodeName is registered in Active Directory. System Action: Server operation continues. User Response: None. ANR9967I (Windows) Server server name was defined in Active Directory. Explanation: The server is registered in Active Directory. System Action: None. User Response: None. 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 System Action: Server operation continues. 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.
Chapter 3. Common and Platform Specfic Messages
603
ANR9999D
ANR9999D (component)(code):(text)
Explanation: This message carries diagnostic text relating to a server process or algorithm. This information is intended for reporting processing exceptions and other non-standard situations that occur on the ADSM server. The (component), (code), and (text) will vary depending upon the cause of the message and the server process or algorithm that issues the message. System Action: Server processing may or may not continue depending upon the cause of this message. Use the SET CONTEXTMESSAGING command and set the message context reporting to ON to receive additional information when the server issues this message. See the Administrators Reference. User Response: 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 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.
604
IBM Tivoli Storage Manager: Messages
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 Error processing filespace-name: file 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. System Action: Processing stopped. User Response: Report the program error to your service representative. 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 Error processing filespace 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. System Action: File skipped. User Response: None. ANE4006E Error processing filespace namepath-namefile-name: directory path not found Explanation: You specified an incorrect directory path. System Action: Processing stopped. User Response: Correct the syntax specified on the call and retry the operation. ANE4007E Error processing filespace namepath-namefile-name: access to the object is denied Explanation: Access to the specified file or directory is denied. You tried to read from or write to a file and you do not have access permission for either the file or the directory. System Action: Processing stopped. User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location. ANE4008E Error processing filespace namepath-namefile-name: file is temporarily unavailable Explanation: File is temporarily unavailable. System Action: File skipped. User Response: Check and see if file is locked by other process. If not, retry the command. ANE4009E Error processing filespace namepath-namefile-name: disk full condition Explanation: No more files can be restored or retrieved because the destination disk is full. System Action: Processing stopped. User Response: Free up disk space, or restore or retrieve the file to another disk.
Copyright IBM Corp. 1993, 2004
605
ANE4010E
Error processing filespace namepath-namefile-name: stale NFS handle Explanation: An NFS file system becomes stale. System Action: File system skipped. User Response: Check the NFS mounted filesystem. ANE4011E Error processing filespace namepath-namefile-name: no file handles available Explanation: All file handles for your system are currently in use. No more are available. System Action: Processing stopped. 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 Error processing filespace 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. User Response: None. ANE4013E Error processing filespace 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: Processing stopped. User Response: Report the problem to your system administrator, and then retry the operation. ANE4014E Error processing filespace 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. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, see your administrator. ANE4015E Error processing filespace 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. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.
ANE4016E
Error processing filespace 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. System Action: File skipped. 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 Error processing filespace 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. System Action: File skipped. User Response: Ensure that you do not have a looping symbolic link for the file. ANE4018E Error processing filespace 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. ANE4019E Error processing filespace 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 Error processing filespace namepath-namefile-name: format unknown Explanation: Tivoli Storage Manager tried to restore or retrieve a file, but it had an unknown format. System Action: File skipped. User Response: See your system administrator. ANE4021E Error processing filespace namepath-namefile-name: file system not ready Explanation: The file system/drive was not ready for access. System Action: Processing stopped. User Response: Ensure that the drive is available to Tivoli Storage Manager, and then retry the operation.
606
IBM Tivoli Storage Manager: Messages
ANE4022E
Error processing filespace namepath-namefile-name: file system is invalid Explanation: The drive was not available for access. A directory exists that does not have either a '.' or '..' entry. System Action: Processing stopped. User Response: Ensure that the drive is operational, and then retry the operation. If unsuccessful, have your service representative check the error log. ANE4023E Error processing filespace namepath-namefile-name: file input/output error Explanation: An error was found while reading from or writing to the file. System Action: File skipped. 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 Error processing filespace namepath-namefile-name: file write error Explanation: An error was found while writing to the file. System Action: File skipped. User Response: Check your system to ensure that it is operating properly. ANE4025E Error processing filespace 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)
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) System Action: File skipped. User Response: Ensure that the system limits are set properly. ANE4026W Error processing filespace 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 Error processing filespace namepath-namefile-name: internal program message value encountered Explanation: An unexpected catastrophic program failure occurred, indicated by value. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, see your system administrator or service representative. ANE4028E Error processing filespace namepath-namefile-name: cannot create file/directory entry Explanation: The directory path for files being restored or retrieved cannot be created. System Action: File skipped. User Response: Ensure that you have the proper authorization to create the directory for file being restored or retrieved. ANE4029E Error processing filespace 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. System Action: Processing stopped. 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.
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)
Chapter 4. Client Events Logged to Server (ANE40004999)
607
ANE4030E
Error processing filespace namepath-namefile-name: disk space limit for this process reached Explanation: The disk space allocated for the client owner is full. System Action: Processing stopped. User Response: Free up disk space and retry the restore or retrieve operation. ANE4031E Error processing filespace 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. System Action: Processing stopped. User Response: Specify a destination path that, when combined, is less than the system maximum. ANE4032E Error processing filespace namepath-namefile-name: file is not compressed. Explanation: A file that was flagged as compressed was not compressed, and the system failed. System Action: Processing stopped. User Response: See your system administrator to report this problem. This error is a system failure. ANE4033E Error processing filespace 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 and retry the operation. ANE4034E Error processing filespace namepath-namefile-name: unknown system 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. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.
ANE4035W
Error processing filespace namepath-namefile-name: file currently unavailable on server. Explanation: You tried to restore or retrieve a file that is currently not available from the server. System Action: Tivoli Storage Manager cannot restore or retrieve the file. User Response: See your system administrator to 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. User Response: See your system administrator. 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. ANE4038E An error occurred processing file system filespace name. Explanation: File system filespace name is corrupted or contains one or more corrupted directories and cannot be processed. System Action: File system is skipped. User Response: Check your system to ensure that it is operating properly. For the Windows environment, run CHKDSK utility for the failing drive. More information about corrupted directories can be found in dsmerror.log. ANE4040E Error processing filespace 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.
608
IBM Tivoli Storage Manager: Messages
ANE4041W
Error processing filespace 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. System Action: File skipped. User Response: You need to check the disk for errors. 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. User Response: None. ANE4900W Error processing filespace namepath-name file-name: the object is in use by another process Explanation: Access to the specified file or directory is denied. You tried to read from or write to a file and you do not have access permission for either the file or the directory. System Action: Processing stopped. User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location. ANE4987E File filespace namepath-namefile-name is currently unavailable on server and has been skipped. Explanation: You tried to restore or retrieve a file that 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
ANE4991I ANE4992W ANE4993E ANE4994S ANE4999E
appType appmsgId msg appType appmsgId msg appType appmsgId msg appType appmsgId msg
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 User Response: None.
Chapter 4. Client Events Logged to Server (ANE40004999)
609
610
IBM Tivoli Storage Manager: Messages
Part 3. Client and Data Protection for Lotus Notes Messages
Copyright IBM Corp. 1993, 2004
611
612
IBM Tivoli Storage Manager: Messages
Chapter 5. Client and Data Protection for Lotus Notes 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 for Lotus Notes 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 TSM error log that you can use when working with your service representative.
ANS0201E Invalid parameter was found. User Response: Correct the value for the objName. ANS0205E Unable to open error log file.
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 system is unable to open the error log file. System Action: The system returns to the calling procedure. 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: The client is not authorized to restore the other node's data. System Action: The system returns to the calling procedure. User Response: Get authorization from the other node. ANS0203E The objName field has no leading directory separator.
Explanation: There was an error writing to the log file. System Action: The system returns to the calling procedure. 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. ANS0207E The log file name was not specified.
Explanation: The objName field does not have a leading directory separator. System Action: The system returns to the calling procedure. User Response: Correct the value for the objName. ANS0204E Wildcards are not allowed in the objName directory path.
Explanation: The system is unable to open the error log file. System Action: The system returns to the calling procedure. 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.
Explanation: Wildcards are not allowed in the objName directory path. System Action: The system returns to the calling procedure.
Copyright IBM Corp. 1993, 2004
613
ANS0208E ANS0219E
ANS0208E The TCP/IP WINSOCK.DLL file cannot be found. ANS0214E There is no server session information.
Explanation: The TCP/IP WINSOCK.DLL file cannot be found. System Action: Processing stopped. User Response: Verify your TCP/IP installation. ANS0209E An error occurred while loading a library.
Explanation: The server did not respond with the session information. System Action: The system returns to the calling procedure. User Response: Verify the server status. ANS0215E There is no server policy information.
Explanation: An error occurred while loading a library. The TCP/IP DLL load failed. System Action: Processing stopped. User Response: Verify your TCP/IP installation. ANS0210E The TCP/IP load function failed.
Explanation: The server did not respond with the policy information. System Action: The system returns to the calling procedure. User Response: Verify the server policy definitions. ANS0216E The dataBlk bufferLen value is zero.
Explanation: An error occurred while locating a function. The TCP/IP load function failed. System Action: Processing stopped. User Response: Verify your TCP/IP installation. ANS0211E The object name pointer is NULL.
Explanation: The value for the dataBlk bufferLen is zero. System Action: The system returns to the calling procedure. User Response: Provide a non-zero value for the bufferLen. ANS0217E The dataBlk bufferPtr is NULL.
Explanation: There is no value provided for the object name pointer. System Action: The system returns to the calling 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 dataBlk bufferPtr. System Action: The system returns to the calling procedure. User Response: Provide an address for the bufferPtr. ANS0218E The objType is invalid.
Explanation: There is no value provided for the data block pointer. System Action: The system returns to the calling procedure. User Response: Provide an address for the DataBlk structure. ANS0213E The object attribute pointer is NULL.
Explanation: The value for the objType is invalid. System Action: The system returns to the calling 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. ANS0219E The dsmEndTxn vote is invalid.
Explanation: There is no value provided for the object attribute pointer. System Action: The system returns to the calling procedure. User Response: Provide an address for the ObjAttr structure.
Explanation: The dsmEndTxn vote is invalid. System Action: The system returns to the calling procedure. User Response: The vote must be DSM_VOTE_COMMIT or DSM_VOTE_ABORT.
614
IBM Tivoli Storage Manager: Messages
ANS0220E ANS0229E
ANS0220E An invalid option was found during option parsing. ANS0225E Low level qualifier of the object name should start with the directory delimiter.
Explanation: An invalid option was found. System Action: The system returns to the calling 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/QOPTITSM(APIOPT). ANS0221E There was an error in the ITSM API internals.
Explanation: The low level qualifier for the object name is invalid. System Action: The system returns to the calling procedure. User Response: Start the low level qualifier of the object name with the directory delimiter. ANS0226E The object owner is invalid.
Explanation: The system encountered an error in the API internals. System Action: The system returns to the calling 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. ANS0222E The repository type is invalid.
Explanation: The object owner must be either the root user, or the object owner must be the same as the session owner. System Action: The system returns to the calling procedure. User Response: Verify the session owner and object owner. ANS0227E The dsmBindMC sendType is invalid.
Explanation: The dsmBindMC sendType is invalid. System Action: The system returns to the calling procedure. User Response: The sendType must be one of the following: stBackup stArchive stBackupMountWait stArchiveMountWait ANS0228E The dsmSendObj sendType is invalid.
Explanation: The repository type is invalid. System Action: The system returns to the calling 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. ANS0223E Filespace name should start with the directory delimiter.
Explanation: The dsmSendObj sendType is invalid. System Action: The system returns to the calling procedure. User Response: The sendType must be one of the following: stBackup stArchive stBackupMountWait stArchiveMountWait ANS0224E The object name is either an empty string or has no leading delimiter. ANS0229E The dsmDeleteObj delType is invalid.
Explanation: The filespace name is invalid. System Action: The system returns to the calling procedure. User Response: Filespace name should start with the directory delimiter.
Explanation: The object name is invalid because of an empty string or there is no leading delimiter. System Action: The system returns to the calling procedure. User Response: Verify the format of the dsmObjName full path.
Explanation: The dsmDeleteObj delType is invalid. System Action: The system returns to the calling procedure. User Response: The delType must be dtBackup or dtArchive.
Chapter 5. Client and Data Protection for Lotus Notes Messages
615
ANS0230E ANS0239E
ANS0230E The query Backup objState is invalid. ANS0235E The old password value is NULL or blank.
Explanation: The query Backup objState is invalid. System Action: The system returns to the calling 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: There is no value provided for old password. System Action: The system returns to the calling procedure. User Response: Provide an old password on dsmChangePW. ANS0236E On dsmInit, the owner is not allowed when PASSWORDACCESS=generate.
Explanation: A query or send operation is unable to find the management class name. System Action: The system returns to the calling procedure. User Response: Verify the management class name. ANS0232E The drive letter is not an alphabetic character.
Explanation: PASSWORDACCESS=generate establishes a session with the current login user as the owner. System Action: The system returns to the calling procedure. User Response: When using PASSWORDACCESS=generate, set clientOwnerNameP to NULL. ANS0237E On dsmInit, the node is not allowed when PASSWORDACCESS=generate.
Explanation: The drive letter is not an alphabetic character. This return code is valid on Microsoft Windows only. System Action: The system returns to the calling 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.
Explanation: PASSWORDACCESS=generate establishes a session with the current hostname as the node. System Action: The system returns to the calling procedure. User Response: When using PASSWORDACCESS=generate, set clientNodeNameP to NULL. ANS0238E The sequence of calls is invalid.
Explanation: There is no value provided for the Register Filespace name. System Action: The system returns to the calling procedure. User Response: Provide a filespace name on dsmRegisterFS. ANS0234E The new password value is NULL or blank.
Explanation: The sequence of calls is invalid. System Action: The system returns to the calling procedure. User Response: Verify the transaction call sequence. ANS0239E On dsmSendObj, wildcards are not allowed for the objName.
Explanation: There is no value provided for new password. System Action: The system returns to the calling procedure. User Response: Provide a new password on dsmChangePW.
Explanation: On dsmSendObj, wildcards are not allowed for the objName. System Action: The system returns to the calling procedure. User Response: Provide a fs, hl, and ll on the dsmObjName.
616
IBM Tivoli Storage Manager: Messages
ANS0240E ANS0249E
ANS0240E The filespace to delete/set access cannot be found. ANS0245E The callers structure version is different than the ITSM library version.
Explanation: The filespace to delete cannot be found. System Action: The system returns to the calling procedure. User Response: Verify the filespace name. ANS0241E On dsmSendObj, dsmDeleteObj, or dsmUpdateFS the filespace is not registered.
Explanation: The caller's structure version is different than the ITSM library version. System Action: The system returns to the calling 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. ANS0246E Issue dsmEndTxn and then begin a new transaction session.
Explanation: On dsmSendObj, dsmDeleteObj, or dsmUpdateFS, the filespace is not registered. System Action: The system returns to the calling procedure. User Response: Verify the filespace name. ANS0242W On dsmRegisterFS the filespace is already registered.
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. System Action: The system returns to the calling procedure. User Response: Issue dsmEndTxn and start a new transaction session. ANS0247E The backup or archive object is excluded from processing.
Explanation: On dsmRegisterFS the filespace is already registered. System Action: The system returns to the calling procedure. User Response: Verify the filespace name. ANS0243E On dsmBeginGetData the objID is NULL.
Explanation: The backup or archive object is excluded from processing. System Action: The system returns to the calling procedure. User Response: Verify the objName and Exclude lists. ANS0248E The backup object does not have a copy group.
Explanation: On dsmBeginGetData, the objID is NULL. System Action: The system returns to the calling procedure. User Response: Verify the following: The dsmGetList is not NULL. Each objID is not NULL. The dsmGetList numObjId is not zero. ANS0244E On dsmInit the callers API version is different than the ITSM library version.
Explanation: The backup object does not have a copy group. System Action: The system returns to the calling procedure. User Response: Verify server policy definitions. ANS0249E The archive object does not have a copy group.
Explanation: On dsmInit the caller's API version has a higher value than the ITSM library version. System Action: The system returns to the calling procedure. User Response: Install the latest ITSM API library and trusted agent module.
Explanation: The archive object does not have a copy group. System Action: The system returns to the calling procedure. User Response: Verify server policy definitions.
Chapter 5. Client and Data Protection for Lotus Notes Messages
617
ANS0250E ANS0260E
ANS0250E Memory used by the ITSM API has been corrupted. User Response: The fs field must be less than or equal to DSM_MAX_FS_LENGTH. ANS0256E The sendObj dsmObjName.ll is too long.
Explanation: Memory used by the ITSM API has been corrupted. System Action: The system returns to the calling procedure. User Response: Retry the operation. If the problem continues, contact your system administrator or service representative. ANS0251E The sendObj Archive description is too long.
Explanation: The sendObj dsmObjName.ll is too long. System Action: The system returns to the calling 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.
Explanation: The sendObj Archive description is too long. System Action: The system returns to the calling procedure. User Response: The sndArchiveData.descr string must be less than or equal to DSM_MAX_DESCR_LENGTH. ANS0252E The sendObj ObjAttr.objInfo is too long.
Explanation: On RegisterFS or UpdateFS the fsAttr's fsInfo is too long. System Action: The system returns to the calling procedure. User Response: The fsInfo field must be less than or equal to DSM_MAX_FSINFO_LENGTH. ANS0258I On dsmGetNextQObj or dsmGetData there is more available data.
Explanation: The sendObj ObjAttr.objInfo is too long. System Action: The system returns to the calling 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: On dsmGetNextQObj or dsmGetData there is more available data. System Action: The system returns to the calling procedure. User Response: Call the function again. ANS0259E The dataBlk buffer is too small for the query response.
Explanation: The sendObj dsmObjName.hl is too long. System Action: The system returns to the calling procedure. User Response: The hl field must be less than or equal to DSM_MAX_HL_LENGTH. ANS0254E The dsmChangePW password is too long.
Explanation: The dataBlk buffer is too small for the query response. System Action: The system returns to the calling procedure. User Response: On dsmGetNextQObj ensure that the dataBlk buffer is at least as big as the query response structure. ANS0260E An invalid option keyword was found during option parsing.
Explanation: The dsmChangePW password is too long. System Action: The system returns to the calling procedure. User Response: The password field must be less than or equal to DSM_MAX_VERIFIER_LENGTH. ANS0255E The sendObj dsmObjName.fs is too long.
Explanation: An invalid option keyword was found in the dsmInit configuration file, the option string, dsm.sys, or dsm.opt. System Action: The system returns to the calling 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 sendObj dsmObjName.fs is too long. System Action: The system returns to the calling procedure.
618
IBM Tivoli Storage Manager: Messages
ANS0261E ANS0271E
ANS0261E The configuration file specified on dsmInit cannot be opened. ANS0266I The dsmEndTxn vote is ABORT, so check the reason field.
Explanation: The configuration file specified on dsmInit cannot be opened. System Action: The system returns to the calling procedure. User Response: Verify the file name. ANS0262E The Include/Exclude definition file 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. System Action: The system returns to the calling 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
Explanation: The Include/Exclude definition file was not found. System Action: The system returns to the calling procedure. User Response: Verify the file name on the Inclexcl option. ANS0263E Either the dsm.sys file was not found, or the Inclexcl file specified in dsm.sys was not found.
Explanation: The option is not valid on this command line. System Action: Processing stops User Response: Verify that the option and value are not misspelled and are valid with the current command. ANS0268E Server problem: Destination not defined.
Explanation: Either the dsm.sys file was not found, or the Inclexcl file specified in dsm.sys was not found. System Action: The system returns to the calling 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: Server problem: Destination not defined. System Action: Processing stopped. User Response: Have your service representative check the error log. ANS0269S The structured file data type is unknown.
Explanation: Only a UNIX root user can execute dsmChangePW or dsmDeleteFS. System Action: The system returns to the calling procedure. User Response: Run this program as a root user.
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. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. ANS0270S The data buffer overflowed.
ANS0265E
You must issue dsmBindMC before dsmSendObj.
Explanation: The data buffer overflowed. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. ANS0271E No more files can be restored or retrieved since the destination directory is full.
Explanation: You must issue dsmBindMC before dsmSendObj. System Action: The system returns to the calling procedure. User Response: Modify your program.
Explanation: No more files can be restored or retrieved since the destination directory is full. System Action: Processing stopped.
Chapter 5. Client and Data Protection for Lotus Notes Messages
619
ANS0272I ANS0283E
User Response: Free up disk space, or restore or retrieve the file to another disk. ANS0272I The operation is finished. ANS0278S The transaction will be aborted. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator.
Explanation: The operation is finished. System Action: The system returns to the calling procedure. User Response: Proceed with next function call. ANS0273E The trusted agent execution/owner permissions are invalid.
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: The trusted agent execution/owner permissions are invalid. System Action: Processing stopped. User Response: Have your system administrator check the installation instructions for the client to ensure that the trusted agent permissions are set correctly. ANS0274S Process killed.
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. System Action: File skipped. User Response: Verify the application sets the mountWait value correctly on dsmBeginGetData. ANS0280E Unable to find Trusted Agent module.
Explanation: Processing stopped. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. ANS0275S Trusted agent would block the operation.
Explanation: ITSM was unable to find the ITSM Trusted Agent module in the specified directory. The name of the ITSM Trusted Agent module is dsmtca. System Action: ITSM ends. User Response: Make sure the Trusted Agent module is in the directory specified by DSMI_DIR. ANS0281E Access denied for dsmapitca.
Explanation: The trusted agent blocks the operation. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. ANS0276S The area for the include/exclude pattern is too small.
Explanation: An attempt to access a system function has been denied. System Action: Processing stopped. User Response: Contact your system administrator. ANS0282E Password file is not available.
Explanation: The area for the include/exclude pattern is too small. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. ANS0277S There is no closing bracket in the pattern.
Explanation: The file containing the stored password for the specified server-name is unavailable. System Action: ITSM ends. User Response: The root user must set and store a new password. ANS0283E High level qualifier of the object name should start with the directory delimiter.
Explanation: There is no closing bracket in the pattern. This is a programming failure and the client program ends.
Explanation: The high level qualifier for the object name is invalid.
620
IBM Tivoli Storage Manager: Messages
ANS0284E ANS0301E
System Action: The system returns to the calling procedure. User Response: High level qualifier of the object name should start with the directory delimiter. ANS0284E The number of objects on dsmBeginGetData exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ. ANS0296I Encryption key passwords are not the same. Please try again...
Explanation: ITSM 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. ANS0297E Error opening specified file.
Explanation: The number of objects (numObjId) specified on the dsmBeginGetData call exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ. System Action: The system returns to the calling 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. ANS0285E The update action is invalid.
Explanation: The specified file could not be located or opened. System Action: Attempts to open file failed. 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. User Response: Check with your system administrator to find out why your user id is locked. ANS0299E Scheduler cannot be started manually because the value of MANAGEDSERVICES option is SCHEDULE.
Explanation: The dsmUpdateFS or dsmUpdateObj action is invalid. System Action: The system returns to the calling procedure. User Response: Correct the action value. Valid values are defined in dsmapitd.h and documented in our Using the API book. ANS0286E The key file is missing.
Explanation: The key file for Tivoli Storage Manager data protection application client for Oracle cannot be found. System Action: The system returns to the calling procedure. User Response: Ensure that you have ordered the Tivoli Storage Manager data protection application client which contains TDP for Oracle, and install the key file. ANS0287E The key file content is invalid.
Explanation: if MANAGEDSERVICES SCHEDULE is indicated in the option file, the ITSM scheduler cannot be started in the traditional manner. System Action: Scheduler stopped. 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. ANS0301E The ITSM DLL dsm3270.dll cannot be found in the users path.
Explanation: The ITSM DLL dsm3270.dll cannot be found in the user's path. System Action: Communications link is not established. User Response: Make sure that the ITSM DLL dsm3270.dll is in a directory that is included in the user's path.
Explanation: The key file content for Tivoli Storage Manager data protection application client for Oracle is invalid. System Action: The system returns to the calling procedure. User Response: Ensure that you have ordered the Tivoli Storage Manager data protection application client which contains the TDP for Oracle, and install the key file.
Chapter 5. Client and Data Protection for Lotus Notes Messages
621
ANS0302I ANS0318E
ANS0302I Successfully done. ANS0309E Remote operation failed to start on obj-name. Status: status
Explanation: The operation successfully completed. System Action: None. User Response: None. ANS0304E Unable to generate password because password access is not set to GENERATE.
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. User Response: Contact your system administrator for more information. ANS0315E Unable to open message text file.
Explanation: User issued the Generate Password command, but password access is not set to GENERATE in the options file. System Action: ITSM none. User Response: Add PASSWORDACCESS GENERATE to your dsm.opt file . ANS0305E Unable to generate password because no NAS Node was 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). System Action: The system returns to the calling 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: User issued the Generate Password command with class=NAS, but no NAS node was specified. System Action: None. User Response: Retry the command and use the -nasnodename option. ANS0306E Unable to generate password because Class type is invalid or unknown.
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). System Action: The system returns to the calling procedure. User Response: Install the message text file again. ANS0317E Unable to use message text file.
Explanation: User issued the Generate Password command with an invalid or unknown class. System Action: None. User Response: Retry the command and use a supported class type option (class=CLIENT or class=NAS). ANS0307I Password generated.
Explanation: The system is unable to use the message 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). System Action: The system returns to the calling procedure. User Response: Install the message text file again. ANS0318E Invalid value for DATEFORMAT specified.
Explanation: User issued the Generate Password command and it was successful. System Action: None. User Response: None. 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: ITSM ended the current operation. User Response: Contact your system administrator for more information.
Explanation: An invalid value is specified for DATEFORMAT. System Action: The system returns to the calling procedure. User Response: Specify a valid value.
622
IBM Tivoli Storage Manager: Messages
ANS0319E ANS0331E
ANS0319E Invalid value for TIMEFORMAT specified. ANS0325E Partial Object Retrieve is not supported on this server.
Explanation: An invalid value is specified for TIMEFORMAT. System Action: The system returns to the calling procedure. User Response: Specify a valid value. ANS0320E Invalid value for NUMBERFORMAT specified.
Explanation: The ITSM server specified by the user does not support partial object retrieve. System Action: The system returns to the calling procedure. User Response: Specify a ITSM server which supports the partial object retrieve function. ANS0326E Node has exceeded max tape mounts allowed.
Explanation: An invalid value is specified for NUMBERFORMAT. System Action: The system returns to the calling procedure. User Response: Specify a valid value. ANS0321E msg parameter for dsmRCMsg is a NULL pointer.
Explanation: All the tape mount points for this node are in use. System Action: The system returns to the calling procedure. User Response: Increase the number of allowed tape mounts for this node on the server. ANS0327E A duplicate object was found, operation cannot complete.
Explanation: The message parameter for dsmRCMsg is a NULL pointer. System Action: The system returns to the calling procedure. User Response: Allocate enough space for the message parameter. ANS0322E no text available for this return code.
Explanation: A duplicate object was found, operation cannot complete. System Action: The requested operation failed. User Response: Try the operation with a different file specification. ANS0328E The specified objects failed the merge test.
Explanation: The dsmRC parameter for dsmRCMsg is an unsupported return code. System Action: The system returns to the calling procedure. User Response: Specify a valid value. ANS0323E partialObjOffset value for partial object retrieve is invalid.
Explanation: The specified objects failed the merge test, operation cannot complete. System Action: The requested operation failed. User Response: See documentation for the merge test parameters. ANS0330E The dsmSetAccess access Type is invalid.
Explanation: The partialObjOffset value for partial object retrieve is invalid. System Action: The system returns to the calling procedure. User Response: Specify a valid value. ANS0324E partialObjLength value for partial object retrieve is invalid.
Explanation: The dsmSetAccess accessType is invalid. System Action: The system returns to the calling procedure. User Response: The accessType must be one of the following: atBackup atArchive ANS0331E No files have been previously backed up for this filename/filespace.
Explanation: partialObjLength value for partial object retrieve is invalid. System Action: The system returns to the calling procedure. User Response: Specify a valid value.
Explanation: You tried to set access to files when no files for the specified filename, drive or file system were previously backed up.
Chapter 5. Client and Data Protection for Lotus Notes Messages
623
ANS0332E ANS0342E
System Action: Processing stopped. 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. 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. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. ANS0338E An invalid operation was attempted on a node
Explanation: You tried to set access to files when no files for the specified filename, drive or file system were previously archived. System Action: Processing stopped. User Response: Ensure that the correct drive or file system was specified and that files are archived for you to set access. ANS0333E Unknown Remote Mover type
Explanation: The operation is not valid. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. ANS0339E The specified target storage pool is not defined.
Explanation: The specified Remote Mover type is unknown. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. ANS0334E An Operation for the requested node and filespace is already in progress.
Explanation: The storage pool is not defined. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. ANS0340E A target storage pool does not have the correct data format for the given node type.
Explanation: A request has been made to use a data mover to perform an operation for the indicated node and filespace. Since an operation for this node and filespace is already in progress, the new operation cannot be performed. System Action: ITSM ended the current operation. User Response: Retry the operation at a later time. ANS0335E System resource in use
Explanation: none System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. ANS0341E No associated data mover is defined for the given node.
Explanation: A required resource is in use by another command or process. System Action: ITSM ended the current operation. User Response: Retry the operation at a later time. ANS0336E Server plugin communication error
Explanation: none System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. ANS0342E The CRC received from the Server does not match the CRC calculated by the client.
Explanation: Communication between a server plugin module and a NAS filer failed. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information.
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 the failure to the server and retry the operation. User Response: Check the trace log for additional
624
IBM Tivoli Storage Manager: Messages
ANS0343E ANS0404E
information and retry the operation. If the problem persists, contact your system administrator. ANS0343E An invalid operation was attempted on a group leader or group member. ANS0349E Transaction failed because of a problem during a store operation.
Explanation: An invalid operation was attempted on a logical group. System Action: The current operation stops. User Response: Retry a valid operation. ANS0344E Cannot Send data with a zero byte sizeEstimate.
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 seperate txns. ANS0400E License file could not be opened.
Explanation: You cannot send data for an object with size estimate = 0. System Action: The system returns to the calling procedure. User Response: Set size estimate greater than 0 in dsmSendObj. ANS0345E Remote disk not defined.
Explanation: The license file was not found, or could not be opened because of permissions or the file is corrupted. System Action: The system returns to the calling procedure. User Response: Check permissions on file. See if the license file is in the correct place. ANS0401E Read failure on the license file.
Explanation: An operation was attempted on a remote disk that is not defined. System Action: The current operation stops. User Response: Define the proper remote disk. ANS0346E Input destination does not match expected destination.
Explanation: The license file was not found, or could not be opened because of permissions, or the file is corrupted. System Action: The system returns to the calling procedure. User Response: Check permissions on file. See if the license file is in the correct place. ANS0402E Write failure on the license file.
Explanation: Input destination does not match expected destination. System Action: The current operation stops. User Response: Retry operation with proper destination. ANS0347E Data mover is not available.
Explanation: The license file was not found, or could not be opened because of permissions or the file is corrupted. System Action: The system returns to the calling procedure. User Response: Check permissions on file. See if license file is in the correct place. ANS0403E Data in the license file is not in a valid format.
Explanation: Data mover is not available. System Action: The current operation stops. User Response: Retry operation with a proper Data mover. ANS0348E Operation failed because the copy continue option was set to NO.
Explanation: The license file is not valid. System Action: The system returns to the calling procedure. User Response: User needs to obtain a new license. ANS0404E The checksum in the license file does not match the licenseregistration string.
Explanation: Operation failed because the copy continue option was set to NO. System Action: The current operation stops. 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.
Explanation: The registration string is not valid. System Action: The system returns to the calling procedure.
Chapter 5. Client and Data Protection for Lotus Notes Messages
625
ANS0405E ANS0903E
User Response: User needs to obtain a new license. ANS0405E This is an expired try and buy license. ANS0416E Wrong Read State
Explanation: The operation must be in READ state. System Action: The system returns to the calling procedure. User Response: Contact your service representative. ANS0417E Runtime API version is outdated
Explanation: The registration string is not valid. System Action: The system returns to the calling procedure. User Response: User needs to obtain a new license. ANS0410E Oracle passed invalid mode
Explanation: Runtime API is lower than compile time API. System Action: The system returns to the calling 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: Invalid mode passed by Oracle. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANS0411E Oracle passed null file name
Explanation: Null filename passed by Oracle. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANS0412E Wrong data block size
Explanation: The operation must be in WRITE state. System Action: The system returns to the calling procedure. User Response: Contact your service representative. ANS0419E Invalid flag passed
Explanation: Wrong Block Size System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANS0413E Object exists
Explanation: Invalid flag passed from Oracle. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANS0900I dsmnotes completed.
Explanation: Backup or Restore Object already exists. System Action: The system returns to the calling procedure. User Response: If backing up an object, be sure to generate a unique object name. ANS0414E Not same Oracle handle
Explanation: The dsmnotes command completed successfully. System Action: The program completes. User Response: Not Applicable. ANS0901S Cannot allocate memory.
Explanation: The handle passed from Oracle is not the same handle that ITSM passed back. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANS0415E End of file reached
Explanation: An attempt was made to allocate memory but failed. System Action: Processing stops. User Response: Check the LOG.DSM file for further details about the failure. ANS0903E I/O error opening file.
Explanation: End of file reached. System Action: The system returns to the calling procedure. User Response: None
Explanation: An I/O error occurred when an attempt was made to open one of the supporting files (for example: a trace file or log file). This message does not suggest an I/O error in a Notes database. System Action: Processing stops.
626
IBM Tivoli Storage Manager: Messages
ANS0904E ANS0915E
User Response: Check all supporting files, including the log file, and trace file. Consider updating the environment variables in the NOTES.INI file to avoid using the problem file, or check access permission on the file. ANS0904E I/O error writing to a file. System Action: Processing stops. User Response: Check the syntax of the command. Correct the syntax and reissue the command. ANS0910E Invalid option keyword.
Explanation: An I/O error occurred when an attempt was made to write to a supporting file like a trace file or log file. This message does not suggest an I/O error in a Notes database. System Action: Processing stops. User Response: Check all supporting files, including the log file, and trace file. Consider updating the environment variables in the NOTES.INI file to avoid using the problem file. Also check your available disk space. ANS0905S Error getting current working directory.
Explanation: An invalid option keyword was specified on a dsmnotes command. System Action: Processing stops. User Response: Identify and correct the invalid keyword. Then reissue the command. ANS0912E The specified password is too long.
Explanation: The ITSM password you entered is too long. System Action: Processing stops. User Response: If you are resetting a new ITSM password, you need to choose a shorter password. If you are entering a current ITSM password, check that the password is correct. If the password is correct but the problem still occurs, ask your ITSM administrator to reset your password to a new value. If you do this, choose a shorter password. ANS0913E An invalid option value was specified.
Explanation: An error occurred while trying to retrieve the current working directory. System Action: Processing stops. User Response: Check the LOG.DSM file for any further details on the specific error. There may be an error in your operating system since it cannot determine your current working directory. ANS0907E Error in getting file system information.
Explanation: An invalid value was specified for an option on a dsmnotes command. System Action: Processing stops. User Response: Identify and correct the invalid value. Then reissue the dsmnotes command. ANS0914E Required keywords are missing.
Explanation: An error was encountered when an attempt was made to obtain the file system information for the drive on which the Notes database resides. System Action: Processing stops. User Response: Check the drive on which the Notes database you are processing resides. Be sure that the volume has a label and your disk is attached. Check the LOG.DSM file for details about the error. ANS0908E Error getting database volume label.
Explanation: One or more required keywords are missing from the dsmnotes command. System Action: Processing stops. User Response: Identify and check the proper syntax and provide the missing keywords and values. Then reissue the dsmnotes command. ANS0915E An invalid date was entered.
Explanation: An error was encountered when an attempt was made to obtain the volume label of the drive on which the Notes database resides. System Action: Processing stops. User Response: Check the drive on which the Notes database you are processing resides. Be sure that the volume has a label and your disk is attached. ANS0909E Error in parsing options.
Explanation: An invalid date value was entered. Either the syntax of the value was not correct, or an actual value (for example, 45 for month) was invalid. System Action: Processing stops. User Response: Identify and correct the invalid date value. Refer to the users guide of the corresponding platform for the correct date syntax.
Explanation: A general parsing error occurred on a dsmnotes command. Either you entered too many path names, or a hyphen (-) or an equal (=) sign is missing in the option.
Chapter 5. Client and Data Protection for Lotus Notes Messages
627
ANS0916E ANS0926E
ANS0916E An invalid time was entered. ANS0921E Usage: dsmnotes restdel <options> <db pathname>
Explanation: An invalid time value was entered. Either the syntax of the value was not correct, or an actual value (for example, 75 for hour) was invalid. System Action: Processing stops. User Response: Identify and correct the invalid date value. Refer to the users guide of the corresponding platform for the correct time syntax. ANS0917E Usage: dsmnotes <actions> <options> <db pathname>
Explanation: A syntax error occurred on the restore deletion stubs command. System Action: Processing stops. User Response: Refer to the users guide of the corresponding platform for the correct syntax. Correct the syntax and reissue the command. ANS0923E Database path name is invalid.
Explanation: No parameters were specified on the dsmnotes command. Some parameters are required such as action parameter and database name parameter. System Action: Processing stops. User Response: Refer to the users guide of the corresponding platform for the correct syntax of your command, including required parameters. Correct the syntax and reissue the command. ANS0918E dsmnotes action (1st parm) is unrecognized.
Explanation: The given path name does not resolve to a valid Notes database file name. System Action: Processing stops. User Response: Validate that the given path name is correct. If wildcard symbols are used, refer to the users guide of the corresponding platform for the correct usage of these symbols. Also check for defaulting to the Notes data directory to ensure that the path name is not defaulting incorrectly. ANS0924E Cannot restore to original database.
Explanation: A syntax error was made on a dsmnotes command. The first parameter on the command is generally used to identify what kind of action is to be performed (for example, INCR for incremental backup), but this first parameter on the command was not recognized as a valid action. System Action: Processing stops. User Response: Refer to the users guide of the corresponding platform for the correct command syntax. Correct the syntax and reissue the command. ANS0919E Usage: dsmnotes incr <options> <db pathname>
Explanation: An attempt was made to rebuild a Notes database from backup copies of notes, but the original database file was specified as the target database. System Action: Processing stops. User Response: Choose an original name for the target database. The name cannot belong to an existing file. ANS0925E -days value cannot be negative (OS/2). The days value cannot be negative (AIX and Windows NT)
Explanation: Only a positive number of days can be specified. System Action: Processing stops. User Response: Either specify a positive number of days or let the system default to restore all the deleted documents that it can identify. ANS0926E Cannot open database.
Explanation: A syntax error occurred on the incremental backup command. System Action: Processing stops. User Response: Refer to the users guide of the corresponding platform for the correct syntax. Correct the syntax and reissue the command. ANS0920E Usage: dsmnotes restore <options> <db pathname>
Explanation: An attempt to open a Notes database was unsuccessful. System Action: Processing stops. User Response: Check the LOG.DSM file for more information about the error. Verify the path name of your database. If the path name is correct, then verify the database itself to ensure that it can be opened through the Notes workspace.
Explanation: A syntax error occurred on the incremental backup command. System Action: Processing stops. User Response: Refer to the users guide of the corresponding platform for the correct syntax. Correct the syntax and reissue the command.
628
IBM Tivoli Storage Manager: Messages
ANS0928I ANS0938E
ANS0928I Restore of Note(s) done. ANS0934E ITSM new passwords do not match.
Explanation: Restoration of one or more notes was successful. System Action: The program completes successfully. User Response: None. ANS0929E User interrupted operation.
Explanation: An attempt was made to change the ITSM password through the Lotus Notes workspace but the two new ITSM passwords entered did not match. System Action: Processing stops. User Response: Retry the command with matching new ITSM passwords. ANS0935E This Notes database file not on server.
Explanation: The user has interrupted the operation (for example, by pressing an interrupt key such as <Ctrl C>). System Action: Processing stops. User Response: None ANS0930I Database rebuild done.
Explanation: Either the given database file was not backed up on the server, or the database file space was removed from the server. System Action: Processing stops.
Explanation: Database rebuild from backup copies of notes was successfully completed. System Action: The program completes successfully. User Response: None. ANS0931E Cannot log errors.
User Response: Check the name of the database to ensure that it is the correct database, and check the DSM.OPT file to ensure that you are accessing the correct ITSM server. You can ask the ITSM administrator to check the filespaces for your node. A database name is equivalent to a filespace. ANS0936E This action is not allowed on a remote database.
Explanation: An attempt was made to initiate error logging, which includes either opening or creating a LOG.DSM file. The attempt failed. System Action: Processing stops. User Response: Check the LOG.DSM file to see why it cannot be opened or created. ANS0932I No matching data on server.
Explanation: The action you tried to perform is not allowed on a database that is not local. System Action: Processing stops. User Response: If the action is not allowed through the Notes workspace interface, but allowed through the ITSM Notes application client command-line interface, then use the appropriate dsmnotes command. An alternative is to complete the action on the appropriate machine. ANS0937E Cannot enter new database name (OS/2). Must restore to original database (AIX and Windows NT).
Explanation: An attempt was made to query one or more backup copies of notes on the ITSM server, but no copies existed or an attempt was made to merge the data notes (documents) from the ITSM server into the original database, but no data notes existed. System Action: The program ends. User Response: If you believe that some matching data should exist on the server, check your database path name to ensure that you are using the correct database file name. If the -merge keyword is used, your database might only have nondata notes (documents). ANS0933E The days value is invalid.
Explanation: You are not allowed to enter a new target database name for this restore operation. For OS/2, refer to the dsmnotes restore -FROMDATE option in the users guide documentation. System Action: Processing stops. User Response: If your interface is the Notes workspace, then replace the database name in the entry field with blanks. If your interface is a command, then do not specify a target (-TO) database. ANS0938E Database name required.
Explanation: The days value is either negative or greater than 65535. System Action: Processing stops. User Response: Use correct days value.
Explanation: You are required to enter a database name. System Action: Processing stops.
Chapter 5. Client and Data Protection for Lotus Notes Messages
629
ANS0939I ANS0952E
User Response: Enter the database name. ANS0939I No deletion stubs in database. ANS0944E dsmnotes errors occurred.
Explanation: Errors occurred on one or more databases. System Action: The program partially completes. User Response: Check the LOG.DSM file for further details about the failure. ANS0947E Error initializing Notes.
Explanation: There are no deletion stubs in the given database. System Action: The program ends. User Response: If there are no deletion stubs in the database to initiate the restore, then you may need to rebuild the database by restoring the older version of the database file through the ITSM client. ANS0940E Some options are mutually exclusive.
Explanation: Error occurred while initializing the Lotus Notes runtime system. System Action: Processing stops. User Response: Check the Lotus Notes environment. Try to bring up your Notes workspace if you have not already done so. Also, check the NOTES.INI file to see if it has the correct setup for the Tivoli Storage Manager data protection application client. Refer to the users guide of the corresponding platform. ANS0948E Pathname is a directory.
Explanation: Some of the options specified are mutually exclusive. For example: v For OS/2, the options -MERGE=NO, -TO and -FROMDate cannot all be specified simultaneously because a new target database may not be operable if some documents (such as view and form design documents) are excluded. Design documents are normally backed up with the initial incremental, and not subsequently modified. In this situation, allowing the FROMDate option would cause some design documents to be excluded when creating the new database. v For AIX and Windows NT, the options -MERGE and -TO are mutually exclusive because a new target database cannot be specified for a merge. System Action: Processing stops. User Response: Correct the syntax of the command and then reissue the command. ANS0941E Invalid date/time range.
Explanation: An attempt was made to restore a single Database but the pathname specified was a directory. System Action: Processing stops. User Response: If you want to restore a single database, make sure your database name ends with a .nsf extension. ANS0950E Data on server has an invalid version.
Explanation: Data structure for the application is not compatible with the data stored on the server. System Action: Processing stops. User Response: Check the users software version. ANS0951E Lotus Notes error: error_code occurred.
Explanation: An invalid date or time range was given. For example, the TO time is earlier than the FROM time. System Action: Processing stops. User Response: Correct the date or time range and rerun the program. Be sure that all year, month, day, hour, and minute values are in the correct order and are valid values. ANS0942E No notes chosen.
Explanation: A Lotus Notes error has occurred but the Tivoli Storage Manager data protection application client was not able to translate the error code into a valid Lotus Notes error message. System Action: Processing stops.
Explanation: An attempt was made to restore a note or notes, but no notes documents were chosen. System Action: Processing stops. User Response: On the lotus Notes Workspace, select the notes to be restored by placing a checkmark next to the notes.
User Response: The supported Lotus Notes version is 4.50 for AIX and NT, or 4.52 or above for OS/2. You probably have a downlevel Lotus Notes software installed on your system. Check with your Lotus Notes Administrator for assistance. ANS0952E ITSM error: error_code occurred.
Explanation: A ITSM error has occurred but the Tivoli Storage Manager data protection application client was not able to translate the error code into a valid ITSM error message.
630
IBM Tivoli Storage Manager: Messages
ANS0953E ANS0964E
System Action: Processing stops. User Response: Check with your ITSM Administrator for assistance. ANS0953E No license or license expired. ANS0958E Usage: dsmnotes change -adsmpw=old -newadsmpw=new
Explanation: The syntax of the dsmnotes change command is incorrect. System Action: Processing stops. User Response: Use correct syntax. Refer to the users guide of the corresponding platform for the correct syntax. ANS0959I ITSM password changed.
Explanation: You do not have a valid Tivoli Storage Manager data protection application client license or your license has already expired. System Action: Processing stops. User Response: Refer to the users guide of the corresponding platform or call the IBM sales representatives for license information. ANS0955E Database IDs do not match.
Explanation: The ITSM password has been changed successfully. System Action: The program completes successfully. User Response: None. ANS0960E Cannot write over data in buffer.
Explanation: An attempt was made to back up a database that has the same path and name as a database that is previously backed up to the ITSM server. These two databases have the same name, but they have different database IDs. As a result, they were treated as two different databases. System Action: Processing stops. User Response: Rename the database to be backed up. If the database that is previously backed up in the ITSM server is no longer needed, ask your ITSM administrator to delete the databases filespace on the server. ANS0956E The ITSM password is needed.
Explanation: An attempt was made to overwrite valid data in the buffer. System Action: Processing stops. User Response: Check the integrity of the database by opening it in the Lotus Notes workspace. If the database opens successfully, reissue the command. If the error is persistent, contact the IBM technical support. ANS0961E Database not allowed.
Explanation: A ITSM password is required. System Action: Processing stops. User Response: If the ITSM PASSWORDACCESS PROMPT option in the option file is used, you are required to enter the password by using the -adsmpw keyword. If the ITSM PASSWORDACCESS GENERATE option is used, issue the dsmnotes change command with appropriate parameters to create a password file. Refer to the users guide of the corresponding platform for the correct syntax to use. ANS0957E An operation is already active.
Explanation: A database name is not allowed with this command. System Action: Processing stops. User Response: Remove the database name and reissue the command. ANS0962E Filespace not allowed.
Explanation: A filespace name is not allowed with this command. System Action: Processing stops. User Response: Remove the filespace name and reissue the command. ANS0964E Invalid Notes Build Version.
Explanation: An active restore operation is being processed. System Action: Processing stops. User Response: Wait for the active restore operation to complete before starting a second one.
Explanation: A wrong version of Tivoli Storage Manager data protection application client is being used. System Action: Processing stops. User Response: Check the Tivoli Storage Manager data protection application client Readme file to verify if the installed Tivoli Storage Manager data protection application client supports the current version of Lotus
Chapter 5. Client and Data Protection for Lotus Notes Messages
631
ANS0970I ANS0980E
Notes on your workstation. Uninstall the current version of Tivoli Storage Manager data protection application client. Then reinstall and be sure to select the correct version of Tivoli Storage Manager data protection application client during the installation. ANS0970I Processing log file Logname. User Response: Enter the Lotus Notes log database (usually log.nsf). Refer to the users guide of the corresponding platform for further information. ANS0976E Error opening the log database DBname.
Explanation: The specified log database cannot be opened. System Action: Processing stops. User Response: Verify the path name of your log database. If the path name is correct, verify the log database itself to ensure that it can be opened through the Notes workspace. ANS0977E Error getting the mode of log database DBname.
Explanation: The Tivoli Storage Manager data protection application clients log file is being processed. System Action: Program continues. User Response: None. ANS0971E Too few parameters.
Explanation: One or more parameters are required. System Action: Processing stops. User Response: Refer to the users guide of the corresponding platform for the correct number of parameters. Enter the correct number of parameters and reissue the command. ANS0972E Too many parameters.
Explanation: The program cannot verify that the input log database is a valid database. System Action: Processing stops. User Response: Verify the path name of your log database. If the path name is correct, then verify the log database itself to ensure that it can be opened in the Notes workspace. ANS0978E DBname. is not a Lotus Notes database.
Explanation: Too many parameters were passed to the command. System Action: Processing stops. User Response: Refer to the users guide of the corresponding platform for the correct number of parameters. Enter the correct number of parameters and reissue the command. ANS0973E Invalid parameter: parameter.
Explanation: An invalid database has been specified. System Action: Processing stops. User Response: Verify the path name of your log database. If the path name is correct, verify the log database itself to ensure that it can be opened in the Notes workspace. ANS0979E Error closing log file Logname: system error code.
Explanation: An invalid parameter is entered. System Action: Processing stops. User Response: Correct the invalid parameter. Reissue the command. ANS0974E No log file is specified.
Explanation: An I/O error occurred when an attempt was made to close the Tivoli Storage Manager data protection application clients log file. System Action: Processing stops.
Explanation: The Tivoli Storage Manager data protection application clients log file is not entered. System Action: Processing stops. User Response: Enter a fully qualified Tivoli Storage Manager data protection application client log file, then reissue the command. ANS0975E No log database is specified.
User Response: Check the access permission on the Tivoli Storage Manager data protection application clients log file. ANS0980E Error deleting log file Logname: system error code.
Explanation: An I/O error occurred when an attempt was made to delete the Tivoli Storage Manager data protection application clients log file. System Action: Processing stops. User Response: Check the access permission on the Tivoli Storage Manager data protection application clients log file.
Explanation: The Lotus Notes log database is not entered. System Action: Processing stops.
632
IBM Tivoli Storage Manager: Messages
ANS0981E ANS1000E
ANS0981E Error getting log file start time. ANS0985E Error closing the database DBname: system error code.
Explanation: The program is not able to interpret the first date/time stamp in the Tivoli Storage Manager data protection application clients log file. The first date/time stamp format either does not match the date/time stamp format of your operating system, or it is corrupted. System Action: Processing stops. User Response: For consistency reason, the date/time stamp format of the log file must match the date/time stamp format of your operating system. Check the locale of your operating system to ensure that you have matching date/time stamp formats. ANS0982E Error getting log file end time.
Explanation: An I/O error occurred when an attempt was made to close the log database. System Action: Processing stops. User Response: Check the access permission on the log database. ANS0986I Log file Logname successfully written to DBname.
Explanation: The Tivoli Storage Manager data protection application clients log file has been successfully written to the log database. System Action: The program completes successfully. User Response: None. ANS0987E Log file Logname NOT written to DBname.
Explanation: The program is not able to interpret the last date/time stamp in the ITSMConnect Agents log file. The last date/time stamp format either does not match the date/time stamp format of your operating system, or it is corrupted. System Action: Processing stops. User Response: For consistency reason, the date/time stamp format of the log file must match the date/time stamp format of your operating system. Check the locale of your operating system to ensure that you have matching date/time stamp formats. ANS0983W Too large a record in log file.
Explanation: The Tivoli Storage Manager data protection application clients log file was not written to the log database due to error. System Action: Processing stops. User Response: Check the error messages that preceded this message. ANS0988I Log file Logname deleted.
Explanation: One of the records in the Tivoli Storage Manager data protection application client is too large, or there is no carriage return character in the log file. System Action: Program continues. User Response: If the command is successful, check the log database to ensure that the correct record was added to the database. If the command fails, verify that the data in the Tivoli Storage Manager data protection application clients log file is valid. ANS0984E Error opening the log file Logname: system error code.
Explanation: The Tivoli Storage Manager data protection application clients log file was deleted because the -d option was used. System Action: The program completes successfully. User Response: None. ANS0989E Log file Logname was NOT deleted, due to error.
Explanation: The user has used the option -d but the Tivoli Storage Manager data protection application clients log file was NOT deleted due to error. System Action: Processing stops. User Response: Check the error messages that preceded this message. ANS1000E Attempting to use a communications method that is not supported
Explanation: An I/O error occurred when an attempt was made to open the Tivoli Storage Manager data protection application clients log file. System Action: Processing stops. User Response: Verify the path name of the log file. Also Check the access permission on the log file.
Explanation: You specified a communication method that is not supported. System Action: Processing stopped. User Response: Specify a valid communication
Chapter 5. Client and Data Protection for Lotus Notes Messages
633
ANS1001E ANS1010E
interface for the ITSM client and your operating system. ANS1001E Volume being backed up was not a system volume. Skipped. transferring the data, and send statistics. You can also consider increasing the IDLETIMEOUT value in the server options file. ANS1006E TCP/IP write error on socket = socket-id, errno = error-code, reason : error-reason
Explanation: User specified to back up system volume only. This volume was not backed up since this volume is not a system volume. System Action: Volume was not backed up. User Response: Use All option or use image backup command to backup this volume. ANS1002I MOS image is being created. It may take a while.
Explanation: An attempt to send data using TCP/IP connection failed. System Action: Connection to server fails. User Response: Retry the operation. If the problem persists, contact your system administrator. ANS1007E Sending of object object-nameobjectnameobject-name failed: No Backup Copy Group
Explanation: Mini Operating System image is beging created. It may take a while to create it. System Action: ITSM is gathering necessary information. User Response: None. ANS1003E Backup failed to start for node = node-name, file system = fs-name, errno = error-code, reason : error-reason
Explanation: The management class for this file (object-name) did not have a backup copy group specified. System Action: TSM did not back up the file. User Response: See your system administrator. ANS1008E Sending of object object-nameobjectnameobject-name failed: No Archive Copy Group
Explanation: An attempt to start backup for remote node failed. System Action: Backup fails. User Response: Retry the operation. If the problem persists, contact the server administrator. ANS1004W Node has exceeded max tape mounts allowed. Operation for filespace-name will be tried again later.
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. User Response: See your system administrator. ANS1009W An error occurred processing the operating system include/exclude statements. The error was detected while processing: subsystemname.
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. ANS1005E TCP/IP read error on socket = socket-id, errno = error-code, reason : error-reason.
Explanation: The client encountered an error while obtaining the automatic include/exclude statements from the operating system. System Action: Processing continues without the full list of operating system include/exclude statements. User Response: Please report the error to your service representative. ANS1010E Error processing filespace-name: Unsupported file system operation.
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
Explanation: The file or directory being restored or retrieved from the server cannot be written to because the destination file system does not support performed operation. System Action: File skipped. User Response: Restore the file to another location.
634
IBM Tivoli Storage Manager: Messages
ANS1016I ANS1028S
ANS1016I No eligible files were found. User Response: Contact your system administrator for more information. ANS1023E Session rejected: Node type mismatch
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 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: 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: ITSM 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. ANS1024E Session rejected: Unable to locate required file WSOCK32.DLL
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 problem continues, see your system administrator for further help. ANS1018E Port port number is already in use
Explanation: The 32-Bit Windows Sockets DLL WSOCK32.DLL could not be located System Action: Communications link is not established. Session rejected. User Response: See your system administrator. ANS1025E Session rejected: Authentication failure
Explanation: The port specified by the TCPCLIENTPORT option is in use by a different process. System Action: Processing stopped. 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: Authentication failure. You entered an incorrect password. System Action: ITSM canceled the current operation. 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 Session rejected: Communications protocol error
Explanation: An error occurred while opening the volume for backup/restore operations. System Action: The requested logical volume operation is not performed. User Response: Re-try the operation, check error log for more information. Make sure the volume is available and is not exclusively locked by a different process. ANS1022E Cancel failed for node: node-name filesystem: fs-name operation: op-type error: error
Explanation: Communications protocol error. An unexpected communications message was received by the client. System Action: ITSM canceled the current operation. User Response: Verify that your communication path is functioning properly. If the problem continues, have your service representative check for a possible program error. ANS1028S Internal program error. Please see your service representative.
Explanation: An unexpected program failure occurred. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, see your system administrator or your service representative.
Explanation: The request to cancel a remote operation has failed. The node, filespace, operation and reason for the failure are shown. System Action: ITSM operation not cancelled.
Chapter 5. Client and Data Protection for Lotus Notes Messages
635
ANS1029E ANS1038S
ANS1029E Communications have been dropped. User Response: Check your options file for the correct TCPSERVERADDRESS statement. See your administrator for the correct name of the server. ANS1034E The specified TCP/IP host name is unreachable
Explanation: Communications with the server dropped. System Action: Processing stopped. User Response: Restart the ITSM client and retry the operation. ANS1030E System ran out of memory. Process ended.
Explanation: The TCP/IP host name specified in the TCPSERVERADDRESS statement cannot be reached. System Action: Processing stopped. User Response: Check your options file for the correct TCPSERVERADDRESS statement. See your administrator for the correct name of the server. ANS1035S Options file file-name not found
Explanation: ITSM cannot allocate storage for the specified operation. System Action: ITSM cannot complete the requested operation. User Response: Stop ITSM, restart ITSM, and retry the operation. If unsuccessful, close all unneeded applications and retry the operation. For UNIX systems that support resource limits, you can check if the memory resource limit is too low by entering the following command: ulimit -a 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. ANS1031E Establishment of a TCP/IP connection timed out before connection was made
Explanation: The options file specified by file-name cannot be found. System Action: The ITSM client ends. User Response: See if you have the environment variable DSM_CONFIG (or DSMI_CONFIG for the API) set, which explicitly identifies the ITSM options file. ( You can do this by entering the SET command at your system.) If this environment variable is set, ensure the file indicated by the variable exists. If it is not set, then ITSM looks for the file dsm.opt in the current directory. If neither of these cases is met, you receive this error message. ANS1036S Invalid option option found in options file file-name at line number : number Invalid entry : entry
Explanation: The attempt to establish a TCP/IP connection timed out before the connection was made. System Action: Processing stopped. User Response: Check for a networking problem. If the problem continues, see your system administrator. API applications should close the session with dsmTerminate. ANS1032E An attempt to establish a TCP/IP connection was rejected by the host
Explanation: The specified option in the ITSM options file (file-name) is in error. System Action: Processing stopped. User Response: Correct the options file entry. ANS1037S Invalid keyword specified
Explanation: An attempt to establish a TCP/IP connection was rejected by the server. System Action: Processing stopped. 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. ANS1033E An invalid TCP/IP host name was specified
Explanation: ITSM found an incorrect keyword in the options file. System Action: Processing stopped. User Response: Correct the options file with valid entries. ANS1038S Invalid option specified
Explanation: An incorrect option was specified to ITSM. System Action: Processing stopped. User Response: Correct the options used for running ITSM.
Explanation: An invalid TCP/IP host name or address was specified. System Action: Processing stopped.
636
IBM Tivoli Storage Manager: Messages
ANS1039S ANS1049E
ANS1039S Include/Exclude pattern too complex ANS1045S Environment variable syntax error.
Explanation: The include or exclude pattern issued is too complex to be accurately interpreted by ITSM. System Action: Processing stopped. User Response: Recode the include or exclude pattern as shown in one of the examples in the appropriate Using the Backup-Archive Client book for the particular operating system. ANS1040S Include/Exclude pattern is missing a closing bracket
Explanation: Incorrect syntax is specified in the options file. Make sure that the variable is enclosed in curly braces. System Action: ITSM 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 Environment string for variable environment-name too long. Anything beyond 1024 characters is being ignored
Explanation: The include or exclude pattern is incorrectly constructed. The closing bracket is missing. System Action: Processing stopped. User Response: Correct the syntax for the pattern. ANS1041S Include/Exclude pattern must start with a directory delimiter
Explanation: Environment variable expanded to a string which is too long. Make sure that the string is no more than 1023 characters long. System Action: ITSM attempts to continue the current operation. User Response: Check the length of environment string and break it up into smaller strings using multiple environment variables. ANS1047E Destination file space or drive letter filespace name is unavailable.
Explanation: The include or exclude pattern must start with a directory delimiter. System Action: Processing stopped. User Response: Correct the syntax for the pattern. 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. System Action: Processing stopped. User Response: Correct the syntax for the pattern. ANS1043S Quotes are not matched
Explanation: Trying to restore or retrieve to a destination that cannot be reached. The specified file space name or drive letter is not valid, does not exist, or you are specifying a local share name that cannot be resolved. System Action: Processing stopped. User Response: Retry the command and specify a different destination. ANS1048E Device volname is not local
Explanation: The quotes specified in the pattern are not the same and do not make a set. System Action: Processing stopped. 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 selected path is not a local device and therefore is not a valid object for image operations. System Action: The requested logical volume operation is not performed. User Response: Choose another object. ANS1049E filename is not a valid destination file for image restore
Explanation: The specified environment-name in the options file is invalid. System Action: ITSM attempts to continue the current operation. User Response: Check the environment variable in the options file and use a valid environment variable. Retry the operation.
Explanation: The filename you specified is not a valid name for a file or it is a directory. System Action: Restore processing stopped. User Response: Specify a correct filename for image restore.
Chapter 5. Client and Data Protection for Lotus Notes Messages
637
ANS1050S ANS1058E
ANS1050S DBCS Characters are not allowed in an Include/Exclude range ANS1055I 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: Only single-byte characters are allowed in an include/exclude list; you cannot use a double-byte character set (DBCS). System Action: Processing stopped. User Response: Remove the double-byte characters from the include/exclude list and retry the operation. ANS1051E Invalid password
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. System Action: Processing continues. User Response: None. ANS1056E Share/network path cannot be resolved. Path does not exist.
Explanation: You entered an invalid password. System Action: ITSM 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. System Action: Processing stopped. 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: 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. System Action: Processing stopped. User Response: Retry the command and specify a destination, or restore the directory tree first before trying to restore the share point. ANS1057I Trying to rename existing filespace filespace-name to new filespace filespace-name, but both filespaces exist. Ignore the old filespace and backup to the new filespace.
Explanation: The existing filespace name using the volume label has been renamed to the UNC format naming convention. System Action: Processing continues. User Response: None. ANS1054E Unable to rename existing filespace filespace-name to new filespace filespace-name.RC=retcode from cuFSUpd().
Explanation: Trying to rename the existing filespace name using the volume label to the UNC format naming convention but both filespaces exists. Leave the existing filespace alone and backup to the new filespace. System Action: Processing continues. User Response: None. ANS1058E Restore destination is unreachable.
Explanation: Unable to rename the existing filespace name using the volume label to the UNC format naming convention. System Action: Processing stopped. User Response: None.
Explanation: Trying to restore to destination that cannot be reached. Either the drive letter is not valid, or you are specifying a local share name that cannot be resolved. System Action: Processing stopped. User Response: Retry the command and specify a different destination.
638
IBM Tivoli Storage Manager: Messages
ANS1059E ANS1068E
ANS1059E Two inactive objects with the same image name were selected. Process terminates ANS1063E Invalid path specification
Explanation: The path specified is not a valid file-system or logical volume name. System Action: The requested logical volume operation is not performed. User Response: Retry the operation, using a valid path. ANS1064E Internal error
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. ANS1060E The specified path is not a mounted filesystem
Explanation: An error occurred in the image utility internals. System Action: The requested logical volume operation is not performed. User Response: Contact your ITSM administrator. ANS1065E Library version of the image utility does not match that of the ITSM API
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. System Action: The requested logical volume operation is not performed. User Response: Retry the operation, using name of a mounted file system. ANS1061E The specified device corresponds to a mounted file system, use the file system name.
Explanation: The current system has a mix of installed components. System Action: The requested logical volume operation is not performed. User Response: Re-install all ITSM components ANS1066E Restore successful. File system mount failed.
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. System Action: The requested logical volume operation is not performed. User Response: Retry the operation, using the file system name. ANS1062E Only a single image may be selected when a destination is entered.
Explanation: The file system was successfully restored, but the attempt to re-mount it failed. 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 Error in system call, check log file for more information
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.
Explanation: An error occurred during a system call, check the error log for more information. System Action: The requested logical volume operation is not performed. User Response: Check error log. ANS1068E Device 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 operation is not performed. User Response: Choose another object.
Chapter 5. Client and Data Protection for Lotus Notes Messages
639
ANS1069E ANS1079E
ANS1069E An error occurred while reading data from the device ANS1074W *** User Abort ***
Explanation: An error occurred while reading data from the device. Windows Only: This could be due to bad sectors on the drive. System Action: The requested logical volume operation is not performed. 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
Explanation: An abort signal to stop an operation was received. System Action: Processing stopped. User Response: Continue with normal operations. ANS1075E (): *** Program memory exhausted ***
Explanation: IBM Tivoli Storage Manager has encountered a condition where it can not allocate any more memory. 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: Processing stopped. User Response: Stop any unnecessary programs that are running and retry the operation. Reducing the scope of queries and the amount of data returned can also solve the problem. If the error reoccurs, contact your support representative, and be sure to provide the entire text of this message along with detailed information about how you got this message. ANS1076E *** Directory path not found ***
Explanation: An error occurred while writing data to the device. System Action: The requested logical volume operation is not performed. User Response: Re-try the operation, check error log for more information. ANS1071E Invalid domain name entered: domain-name
Explanation: You specified an incorrect directory path. System Action: Processing stopped. User Response: Correct the syntax specified and retry the operation. ANS1078S *** Unknown system error error-code; program ending ***
Explanation: You entered an invalid domain-name. System Action: Processing stopped. User Response: Enter a valid drive or file system name (domain). 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. System Action: Processing stopped. User Response: Use the system format utility to place a unique volume label on all drives on which you intend to run ITSM. ANS1073E File space correspondence for domain domain-name is not known
Explanation: An unknown and unexpected error-code occurred within the client program. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, see your administrator. ANS1079E No file specification entered
Explanation: You did not enter a file specification as prompted. System Action: ITSM did not continue with the requested operation. User Response: Enter a file specification to continue.
Explanation: The number defining the correspondence between drive letter or file (domain name) and volume label is not known to the server. System Action: Processing stopped. User Response: Report the program error to your service representative.
640
IBM Tivoli Storage Manager: Messages
ANS1081E ANS1090E
ANS1081E Invalid search file specification string entered ANS1086E File not found during Backup, Archive or Migrate processing
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. System Action: Processing stopped. User Response: Enter a correct file specification as described in the appropriate Using the Backup-Archive Client book for the particular operating system. ANS1082E Invalid destination file specification file-name entered
Explanation: The file being processed for backup, archive or migrate no longer exists on the client. Another process deleted the file before it could be backed up, archived or migrated by ITSM. System Action: File skipped. User Response: None. ANS1087E Access to the specified file or directory is denied
Explanation: You entered a destination file-name specification that contains incorrect characters or has wildcard characters in the specification. System Action: Processing stopped. User Response: Enter a correct file specification as described in the appropriate Using the Backup-Archive Client book for the particular operating system. ANS1083E No files have previously been archived for filespace-name
Explanation: Access to the specified file or directory is denied. You tried to read from or write to a file and you do not have access permission for either the file or the directory. System Action: Processing stopped. User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location. ANS1088E File space filespace-name does not exist
Explanation: The specified file space (domain) is incorrect or does not exist on the machine. System Action: Processing stopped. User Response: Retry the operation specifying an existing domain (drive letter or file system name). ANS1089E Destination directory path length exceeds system maximum
Explanation: You tried to retrieve files when no files for the specified drive or file system (filespace-name) were previously archived. System Action: Processing stopped. User Response: Ensure that the correct drive or file system was specified and that files are archived for you to retrieve. ANS1084E No files have previously been backed up for filespace-name
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. System Action: Processing stopped. User Response: Specify a destination path that, when combined, is less than the system maximum. ANS1090E Unable to build directory branch; A file exists with the same name as a directory. Failing path was: path-name.
Explanation: You tried to restore files when no files for the specified drive or file system (filespace-name) were previously backed up. System Action: Processing stopped. User Response: Ensure that the correct drive or file system was specified and that files are backed up for you to restore. ANS1085E No memory available to store Archive Management Class override name
Explanation: ITSM tried to create a directory path-name, but is unable to because a file exists that has the same name as a directory. System Action: Processing stopped. User Response: Remove the file that has the same name as the directory. Refer to the given failing path, and either remove or move the file that caused this problem and restart the restore/retrieve operation.
Explanation: Not enough memory was available for the operation. System Action: Processing stopped. User Response: Retry the operation or restart the system with fewer programs in memory.
Chapter 5. Client and Data Protection for Lotus Notes Messages
641
ANS1091E ANS1102E
ANS1091E Communications error with server during object query variable points to the correct directory containing the current level of ITSM program files. ANS1098E Process terminated; Program memory exhausted.
Explanation: An unexpected communications error occurred during an object query to the server. System Action: Processing stopped. 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: The program used all available storage. System Action: Processing stopped. 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
Explanation: You entered a search pattern or file name that cannot be found in the server database. System Action: Processing stopped. User Response: Ensure that your search pattern is correct, or specify a new search string. ANS1093E Server does not support point-in-time option.
Explanation: You tried to give access to a file, which is not stored on the server. System Action: Processing stopped. User Response: Ensure that the correct filename is specified. ANS1100E File filename not previously backed up
Explanation: The server to which you are connected, does not support point in time values. System Action: Processing stopped. User Response: Enter the command without specifying the point in time option. ANS1094E Server does not support Query Node command.
Explanation: You tried to give access to a file, which is not stored on the server. System Action: Processing stopped. User Response: Ensure that the correct filename is specified. ANS1101E User is not authorized to decrypt filename .
Explanation: The server to which you are connected does not support Query Node command. System Action: Processing stopped. User Response: Use a TSM Server that supports Query Node command. ANS1096S Either an Active Policy Set or a node was not found on the server; Unable to proceed
Explanation: The user is not authorized to decrypt the file; the user cannot restore the file. Only a TSM Authorized user or a root user can decrypt and restore the file. System Action: The file is not restored. User Response: Contact your system administrator to restore the file. ANS1102E Excessive number of command line arguments passed to the program!
Explanation: Either no Active Policy Set data was found on the server or a fromnode option contained a nodename not found on the server. System Action: Processing stopped. User Response: See your system administrator. ANS1097E Unable to read help text
Explanation: This command processing routine received more operands than it can use. Query can contain only one file specification. Restore and Retrieve can contain two file specifications. Archive, Delete, and Selective can contain a maximum of 20 file specifications. System Action: Processing stopped. User Response: Reduce the number of arguments and retry the operation. For UNIX-based systems, ensure that you do not omit the quotes around pattern matching characters.
Explanation: The Help facility cannot read the help text file. System Action: Processing stopped. User Response: Make sure the DSM_DIR environment
642
IBM Tivoli Storage Manager: Messages
ANS1103E ANS1113E
ANS1103E Invalid management class entered ANS1108E Invalid option (option) for the function command
Explanation: You entered an invalid management class. System Action: ITSM is unable to do the requested operation. User Response: Retry the operation using a valid management class. ANS1104E The management class for this file does not have a valid archive copy group. This file will not be archived.
Explanation: The option option was specified for a command or subcommand (function) that cannot make use of that option. System Action: Processing stopped. User Response: See the appropriate Using the Backup-Archive Client book for your operating system for correct use of the named option. ANS1109E User is not authorized to decrypt the file.
Explanation: The management class for this file does not have an archive copy group specified. This file will not be archived. System Action: Processing stopped. 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.
Explanation: The user is not authorized to decrypt the file; the user cannot restore the file. Only a TSM Authorized user or a root user can decrypt and restore the file. System Action: The file is not restored. User Response: Contact your system administrator to restore the file. ANS1110E Unable to open Help file file-name
Explanation: The management class for this file does not have a backup copy group specified. This file will not be backed up. System Action: Processing stopped. User Response: Add a valid backup copy group to the management class, and then retry the operation. ANS1106E ENCRYPTKEY SAVE not configured correctly. Encryption not used.
Explanation: The Help facility cannot find the help file file-name. System Action: Processing stopped. User Response: Ensure that the DSM_DIR environment variable points to the correct directory containing the current level of ITSM program files. ANS1111E Unable to get Help file table of contents
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. ANS1107E Invalid option/value: option
Explanation: The Help facility cannot read the help text file, or the file is corrupted. System Action: Processing stopped. User Response: Make sure the DSM_DIR environment variable points to the correct directory containing the current level of ITSM program files, and that the files are intact. ANS1113E The snapshot cache location is not valid.
Explanation: You specified an incorrect ITSM option option. System Action: Processing stopped. User Response: Specify a correct ITSM option as defined in the appropriate Using the Backup-Archive Client book for the particular operating system.
Explanation: The snapshot cache location must point to a local volume that is formatted. It can not be on the same volume which is being backed up; the default cache location is on the system drive. System Action: The client does not execute the snapshot backup operation. User Response: Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option.
Chapter 5. Client and Data Protection for Lotus Notes Messages
643
ANS1114I ANS1125E
ANS1114I Waiting for mount of offline media. ANS1120E Removal of file space filespace-name failed
Explanation: The server is waiting for the requested media to become available before the operation can continue. System Action: ITSM waits for requested data. User Response: None. ANS1115W File file-namefile-namefile-name excluded by Include/Exclude list
Explanation: Deletion of the specified filespace-name failed. System Action: Processing stopped. User Response: Try again. If the problem continues, see your system administrator to delete the file space for you. ANS1121I Removal of file space filespace-name successfully completed.
Explanation: You tried to back up or migrate a file (file-name) that was specified to be excluded from backup. System Action: ITSM did not back up or migrate the file. User Response: Specify the file using the Include option and retry the operation. ANS1116E Unable to read commands entered from keyboard. Exiting...
Explanation: ITSM successfully deleted the specified filespace-name. System Action: None. User Response: None. ANS1122W File space filespace-name does not exist on the server. The file space might have been deleted by another client using your clients node name or an administrator.
Explanation: Unable to read commands entered from keyboard. ITSM cannot process your intended command. System Action: Processing stopped. User Response: Ensure that you are entering a correct command. ANS1117E The PICK and LATEST options are not valid together
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. System Action: None. User Response: None. ANS1123E The vertical screen dimension is too small to display the Help directory. Increase your window height.
Explanation: During a restore, PICK and LATEST options cannot be used together. System Action: Processing stopped. User Response: Try again using either the PICK or the LATEST option. ANS1118I Invalid file space number entered. Try again.
Explanation: Execution of the HELP command requires space for both the user prompts and at least one line of the HELP directory. System Action: The help directory is not displayed, and the help command cannot complete. User Response: Increase the size of your display window to allow more rows of text to be displayed. ANS1125E Unmatched Quotes: string
Explanation: The number that represents a file space was incorrect while you were using the PICK option. System Action: ITSM waits for your specification. User Response: Enter a correct file space number. ANS1119I Initiating the removal of filespace-name file space.
Explanation: The quotes specified in the pattern are not the same and do not make a set. System Action: Processing stopped. User Response: Correct the pattern using matching quotes in the syntax.
Explanation: Indicates that file space deletion has started on the specified filespace-name. System Action: None. User Response: None.
644
IBM Tivoli Storage Manager: Messages
ANS1126E ANS1135E
ANS1126E Unable to delete the file space because this node does not have permission to delete archived data and/or backed up file space. ANS1131E Unable to continue operation. Duplicate labels exist.
Explanation: During a delete filespace operation, you specified a file space to which your node does not have permission to delete archived data and/or backed up data. System Action: Delete processing fails. User Response: See your system administrator. ANS1127E Your node does not have permission to delete archived files
Explanation: The selected drive has a duplicate volume label. Because ITSM 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: ITSM cannot select the drive. User Response: If the volume needs to be available to the system, exit ITSM, and assign a volume label to the drive. Restart ITSM and retry the operation. ANS1132E Access rule Access Rule already defined for node node. Old rule must be deleted before new one can be defined.
Explanation: Your node is not allowed by the server to delete archived files. System Action: ITSM did not delete the archived files. User Response: See your system administrator. ANS1128S Invalid Management Class assigned to directories. Please see the error log.
Explanation: You are trying to define authorization for the specified node, which already has authorization defined. System Action: ITSM 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 An expression might contain a wildcard not enclosed in quotes
Explanation: An invalid management class was assigned to directories. System Action: Processing stopped. User Response: Have your service representative check the error log. ANS1129S No backup copy group in the management class used for directories. Please see the error log.
Explanation: ITSM cannot process the command because a UNIX shell expands a wildcard expression, for example, asterisk (*) or question mark (?), that has no quotes. System Action: Command dependent. User Response: Enclose the wildcard expression in quotes and enter the command. ANS1134E Drive drive-name is an invalid drive specification
Explanation: The management class used for directories does not have a backup copy group. System Action: Processing stopped. User Response: Have your service representative check the error log. ANS1130E Unable to continue operation. Drive has no label.
Explanation: The specified drive-name was found to be invalid; the drive probably has not been defined. System Action: ITSM 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 Not a valid drive to be backed up
Explanation: The selected drive does not have a label. System Action: ITSM 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.
Explanation: The drive-name1 was found to be a substitute (SUBST) of another drive-name2. It is not available for backup/archive. System Action: ITSM skips the SUBST drive and continues to the next drive.
Chapter 5. Client and Data Protection for Lotus Notes Messages
645
ANS1136E ANS1149E
User Response: None. ANS1136E Not file owner ANS1144W Password authentication not active on server User Response: Try again using either the DIRSONLY or the FILESONLY option.
Explanation: The file cannot be backed up because the client is not the file owner. System Action: ITSM skips the file. User Response: None. ANS1137W Invalid Index number skipped.
Explanation: None. System Action: Processing stopped. User Response: Because password authentication is turned off on the server, you do not need to update the password. ANS1145E Maximum macro nesting level exceeded.
Explanation: An incorrect number was entered for the Index. System Action: Processing stopped. User Response: Correct the Index entry and retry the operation. ANS1138E The command-name command must be followed by a subcommand
Explanation: Too many levels of macro nesting are encountered. 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: You entered an incomplete command-name. System Action: Processing stopped. User Response: Enter the correct syntax of the command and continue. ANS1139E Post restore processing failed.
Explanation: A macro command has been entered that specifies the macro file name shown. However, that file cannot be opened for reading. System Action: The macro is ignored and an error is returned. User Response: Enter the command with the proper macro name. ANS1147E File is temporarily unavailable.
Explanation: Post restore processing failed due to an internal system error. System Action: Please see error log for more details. User Response: Please see your system administrator for assistance. ANS1140E Invalid format for Set Access command.
Explanation: File is temporarily unavailable. System Action: File skipped. User Response: Check and see if file is locked by other process. If not, retry the command. ANS1148I Command-name command successfully completed
Explanation: None. System Action: Processing stopped. User Response: Enter the SET ACCESS command using the correct syntax. ANS1141W Unknown command - command-name
Explanation: The specified command-name was successfully completed. System Action: ITSM completed the command. User Response: Continue with normal operations. ANS1149E No domain available for incremental backup
Explanation: You entered an incorrect command-name. System Action: None. User Response: Enter the correct command. ANS1143E The DIRSONLY and FILESONLY options are not valid together
Explanation: An incremental backup was started, but no domain was selected. System Action: Processing stopped. User Response: Choose a domain and restart the incremental backup.
Explanation: The DIRSONLY and FILESONLY options cannot be used together. System Action: Processing stopped.
646
IBM Tivoli Storage Manager: Messages
ANS1150E ANS1163E
ANS1150E Unable to restore current user profile because you are running as a local system account. then backup/archive the drive. Otherwise, you cannot backup/archive the drive. ANS1156E NODENAME cannot be the local machine name when CLUSTERNODE is set to YES
Explanation: The local system account does not have a profile. Therefore you cannot restore its profile. System Action: Processing stops. User Response: Log on to the user whose profile you want to restore. ANS1151E Drive drive-name1: is not a cluster disk. Not valid for backup/archive when CLUSTERNODE option is YES.
Explanation: When ITSM is running as a cluster node, the nodename cannot be the local machine name. System Action: Processing stops. User Response: Change the nodename either to the cluster name or to any other name, and restart ITSM. ANS1157I Backup/Restore of the registry is not allowed when running as a cluster node.
Explanation: The drive-name1 is not a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to YES. System Action: Processing stops. User Response: Set CLUSTERNODE option to NO, then backup/archive the drive. Otherwise, you cannot backup/archive the drive. ANS1152E Drive filespace is not a cluster disk. Not valid for backup/archive when CLUSTERNODE option is YES.
Explanation: When running as a cluster node, registry cannot be backed up or restored. System Action: Processing continues. User Response: None. ANS1158I Backup/Restore of the event logs is not allowed when running as a cluster node.
Explanation: When running as a cluster node, event logs cannot be backed up or restored. System Action: Processing continues. User Response: None. ANS1159E The specified file is being used by another process
Explanation: The filespace is not a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to YES. System Action: Processing stops. User Response: Set CLUSTERNODE option to NO, then backup/archive the drive. Otherwise, you cannot backup/archive the drive. ANS1153E Drive drive-name1: is a cluster disk. Not valid for backup/archive when CLUSTERNODE option is NO.
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. System Action: Processing stopped. User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location. ANS1162E Filesystem could not be mounted
Explanation: The drive-name1 is a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to NO. System Action: Processing stops. User Response: Set CLUSTERNODE option to YES, then backup/archive the drive. Otherwise, you cannot backup/archive the drive. ANS1154E Drive filespace is a cluster disk. Not valid for backup/archive when CLUSTERNODE option is NO.
Explanation: The system call to mount the file system failed. System Action: The file system remains unmounted. User Response: Use the mount command to mount the file system. On AIX, run fsck if requested by the operating system. ANS1163E Filesystem could not be unmounted.
Explanation: The filespace is a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to NO. System Action: Processing stops. User Response: Set CLUSTERNODE option to YES,
Explanation: The system call to unmount the file system failed. System Action: The logical volume operation is not performed.
Chapter 5. Client and Data Protection for Lotus Notes Messages
647
ANS1164E ANS1184W
User Response: Make sure the device or file system is not being accessed, then retry the operation. ANS1164E Filesystem is not mounted ANS1170I Invalid selection number entered. Try again.
Explanation: The named file system is not currently mounted. It must be mounted for ITSM to perform an image backup. System Action: The logical volume operation is not performed. User Response: Mount the file system.
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: ITSM waits for you to enter a valid selection. User Response: Enter a number from the list or Q to quit. ANS1177E Must specify a path for this operation.
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. ANS1166E Source and destination are not the same file system type.
Explanation: A path must be specified for this operation to execute successfully. System Action: Processing stops. User Response: Specify a valid path and execute the command again. ANS1181E Communication failure with the journal service.
Explanation: An error occurred using named pipe communication with the journal service. System Action: Processing stops. User Response: Attempt to restart the service and retry the backup. If the journal service is not running, a non-journaled backup will proceed. ANS1183E An unknown error occurred while processsing system object sys-obj-name: MS API function func-name failed with error error (error)
Explanation: The source and destination file system types do not match. System Action: The requested logical volume operation is not performed. User Response: Choose a destination that has the same file system type as the source. ANS1168E ERROR: could not create image object.
Explanation: Creation of the image object failed for one of the following reasons: v The image command was executed by a non-root user 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. ANS1169W There is no table of contents for image-name.
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. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. 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. System Action: No table of contents is displayed. User Response: Select another image object for TOC display.
Explanation: The command subcommand command is not supported for the client running on this operating system on this computer. User Response: None. System Action: The command is not processed.
648
IBM Tivoli Storage Manager: Messages
ANS1185W ANS1196E
ANS1185W Server not capable of server-free data movement. ANS1192E Specifying the error log link as a symbolic link is not allowed.
Explanation: The ITSM server that the ITSM 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 retried using LAN-free (if available) or LAN-based data movement. User Response: Remove the ENABLESERVERFREE option from the system option file. ANS1188E The selected filesystem is managed by HSM, and therefore is not a valid object for image operations
Explanation: Error log linkname cannot be a symbolic link. System Action: The symbolic link linkname is deleted, 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 symbolic link is not allowed.
Explanation: Trace file linkname cannot be a symbolic link. System Action: The symbolic link linkname is deleted, the trace file is recreated, and processing stops. User Response: Specify the trace file location with the tracefile option. ANS1194E Specifying the schedule log link as a symbolic link is not allowed.
Explanation: Due to the nature of HSM, image backup is not allowed on managed filesystems. System Action: The requested logical volume operation is not performed. User Response: None. ANS1189E The DIRSONLY and V2ARCHIVE options are not valid together
Explanation: The DIRSONLY and V2ARCHIVE options cannot be used together. System Action: Processing stopped. User Response: Try again using either the DIRSONLY or the V2ARCHIVE option. ANS1190E Symbolic link linkname to target was successfully deleted.
Explanation: Schedule log linkname cannot be a symbolic link. System Action: The symbolic link linkname is deleted, 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. ANS1195E An error occurred while accessing the image snapshot old-blocks index file: .
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 Unable to delete symbolic link link.
Explanation: During the image snapshot backup ITSM encountered an error while opening or reading the old-blocks index file. System Action: Processing stopped. User Response: Contact your ITSM administrator. ANS1196E An error occurred while accessing the image snapshot old-blocks data file: .
Explanation: Log linkname cannot be a symbolic link. System Action: Processing stops. User Response: Delete the symbolic link linkname.
Explanation: During the image snapshot backup ITSM encountered an error while opening or reading the old-blocks data file. System Action: Processing stopped. User Response: Contact your ITSM administrator.
Chapter 5. Client and Data Protection for Lotus Notes Messages
649
ANS1197E ANS1205E
ANS1197E The snapshot cache size was exceeded during the snapshot backup. System Action: The image snapshot backup continues, but with a warning return code of at least 8. 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. ANS1201E Unable to build a directory path; a file exists with the same name as a directory.
Explanation: The image snapshot backup was not able to complete because while creating the snapshot ITSM exceeded the snapshot cache size allowed via the SNAPSHOTCACHESize option. System Action: Processing stopped. User Response: Increase the SNAPSHOTCACHESize value for this volume and retry the operation. ANS1198E An invalid snapshot cache location was entered: .
Explanation: ITSM tried to create a directory path, but is unable to because a file exists that has the same name as a directory. System Action: Processing stopped. 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. ANS1202E TOC backup for the image failed. Check log files.
Explanation: The SNAPSHOTCACHELocation option value entered for this volume is not valid. The value for this option must be an existing, full directory path. System Action: Processing stopped. 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: An error occurred during backup of the table of contents. Check the error log for more information. System Action: The requested logical volume operation is not performed. User Response: Check error log. ANS1203E Deactivating the TOC object failed.
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 snapshot backup operation. 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: An error occurred while deactivating the table of contents object. System Action: Image backup was successful. But deactivating the TOC object from the previous backup failed. User Response: Check error log. ANS1204E Image restore failed. Check the error log.
Explanation: An error occurred while restoring the image. Check log file for more information. System Action: Restore stops. The file system is not mounted back. User Response: Check error log. ANS1205E Image backup failed. Check the error log.
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.
Explanation: An error occurred while backing up the image. Check log file for more information. System Action: Backup stopped. The file system is not mounted back. User Response: Check error log.
650
IBM Tivoli Storage Manager: Messages
ANS1206E ANS1217E
ANS1206E TOC backup of a raw device is not supported. But the raw device is backed up. User Response: None. ANS1214E Not enough space left in the volume group which contains the logical volume to be 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: On Linux platform, the snapshot is created in the same volume group like the logical volume on which it is made. In this volume group there must be enough free space for the snapshot. It is possible to change the size of the snapshot by using a different value for snapshotcachesize. System Action: None. User Response: Decrease the value for snapshotcachesize ANS1215E The snapshot cache location cannot be located on the same volume that is being backed up.
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: Backup the file system again with -TOC option. ANS1209E The input argument list exceeds the maximum length of maximum length characters.
Explanation: The snapshot cache location is on the same volume that is being backed up, but this is not allowed; The default cache location is on the system drive. System Action: The client does not execute the image snapshot backup operation. User Response: Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option. ANS1216E Not authorized to run ITSM. See the administrator for your system.
Explanation: Arguments list for ITSM program should not exceed maximum length characters. System Action: The command is not processed. User Response: Correct the command and retry the operation. ANS1212I Invalid Process number entered. Try again.
Explanation: You entered a number not shown in the list of processes. It is either less than one or greater than the highest item number displayed. System Action: ITSM waits for you to enter a valid selection. User Response: Enter a number from the list or Q to quit. ANS1213W Snapshot image backup is not possible for device devicename.Starting off-line image backup.
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 ITSM to this server. System Action: ITSM initialization fails and the program ends. User Response: See the ITSM 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
Explanation: On Linux platform, snapshot image backup is only possible for logical volumes created by the Linux logical volume manager (LVM). The default image backup type is snapshot. Backing up a partition with snapshot image backup automatically leads to a static image backup. In this case this warning appears. To aviod this message please specify static image backup or dynamic image backup. System Action: Snapshot image backup will failover to static image backup
Explanation: The system options file does not contain the SERVERNAME option. System Action: ITSM initialization fails and the program ends. User Response: See the ITSM administrator for your system, and make sure that the system options file contains the server name.
Chapter 5. Client and Data Protection for Lotus Notes Messages
651
ANS1218E ANS1227E
ANS1218E TCPSERVERADDRESS not defined for this server in the System Options File ANS1223E File is not compressed; System failure.
Explanation: The TCPSERVERADDRESS for this server is not defined in the server name stanza in the system options file. System Action: ITSM initialization fails and the program ends. User Response: See the ITSM administrator for your system, and make sure that the server to which you are trying to connect, has a valid TCPSERVERADDRESS defined in the system options file. ANS1219E NODENAME cannot be the same as HostName
Explanation: A file that was flagged as compressed was not compressed, and the system failed. System Action: Processing stopped. User Response: See your system administrator to report this problem. This error is a system failure. ANS1224E File compressed on a different client machine that has more memory
Explanation: The NODENAME defined in the options file cannot be the same as the system HostName. System Action: Initialization fails and the program ends. User Response: See your system administrator or the root user. ANS1220E Server out of resources
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: ITSM canceled the operation. User Response: Obtain a machine with more memory and retry the operation. ANS1225E Insufficient memory for file compression/expansion
Explanation: The server ran out of resources. A lack of storage or a condition does not allow any new activity. System Action: ITSM canceled the current operation. User Response: Retry the operation at a later time. If the problem continues, see your system administrator to isolate what resource is unavailable. ANS1221E Transaction aborted
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. System Action: Processing stopped. 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
Explanation: The current transaction between the server and the client stopped. A server, client, or communication failure cannot be recovered. System Action: ITSM canceled the current operation. User Response: Retry the operation. If the problem continues, see your system administrator to isolate the problem. ANS1222E Disk space limit for this process reached
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. ANS1227E Processing stopped; Disk full condition
Explanation: The disk space allocated for the client owner is full. System Action: Processing stopped. User Response: Free up disk space and retry the restore or retrieve operation.
Explanation: No more files can be restored or retrieved because the destination disk is full. System Action: Processing stopped. User Response: Free up disk space, or restore or retrieve the file to another disk.
652
IBM Tivoli Storage Manager: Messages
ANS1228E ANS1238S
ANS1228E Sending of object object-nameobjectnameobject-name failed ANS1233E Invalid file handle passed; System Error.
Explanation: The specified file (object-name) cannot be sent to the server. System Action: File skipped. User Response: Retry the operation. If the problem continues, see your system administrator to isolate the problem through use of the server console. ANS1229E MODE=INCREMENTAL is not valid on file-space. Image backup not processed.
Explanation: An internal system error occurred. A file operation failed because an invalid file handle was passed. System Action: Processing stopped. User Response: Report the problem to your system administrator, and then retry the operation. ANS1234E Protocol violation
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. System Action: File system skipped. 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. ANS1230E Stale NFS File Handle
Explanation: A communications protocol error occurred. The communication subsystem is not properly defined or is itself in error. System Action: ITSM ended the current operation. User Response: Verify that the communication processes are operating properly, and then retry the operation. ANS1235E Unknown system error
Explanation: An unknown error occurred. This might be a low-level system or communication error that ITSM cannot handle or recover from. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help. ANS1236E Unexpected error
Explanation: An NFS file system becomes stale. System Action: File system skipped. User Response: Check the NFS mounted filesystem. ANS1231E No file handles available
Explanation: An unexpected error occurred. This might be a low-level system or communication error that ITSM cannot handle or recover from. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help. ANS1237E Server problem. Please see error log.
Explanation: All file handles for your system are currently in use. No more are available. System Action: Processing stopped. 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. ANS1232E File exists
Explanation: This is a server problem. System Action: Processing stopped. User Response: Have your service representative check the error log. ANS1238S Internal Error. Please see error log.
Explanation: The file being restored or retrieved exists. System Action: File is replaced or skipped depending on client options. User Response: None.
Explanation: Server problem. Invalid policy binding. System Action: Processing stopped. User Response: Have your service representative check the error log.
Chapter 5. Client and Data Protection for Lotus Notes Messages
653
ANS1241E ANS1252E
ANS1241E File is in use; Write permission denied. ANS1247I Waiting for files from the server...
Explanation: The current file cannot be opened to write to because it is currently being run by another operation. System Action: File skipped. 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. ANS1242E Too many symbolic links were detected while resolving name
Explanation: Restore request has been sent to the server. The wait time depends on how many files you are restoring. System Action: ITSM waits for files to restore from the server. User Response: None. ANS1248E An active restore for the same source file specification exists. Unable to continue with this request.
Explanation: While trying to resolve the file name, too many symbolic links were found. System Action: File skipped. User Response: Ensure that you do not have a looping symbolic link for the file. ANS1243E File name too long
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. ANS1249W Server cannot restart the last restore request. Do you want to restore without restart or abort the request?
Explanation: The file name specified is too long to be handled by ITSM. 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 ITSM. ANS1244E File system is locked by system
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. ANS1251E File system/drive not ready
Explanation: File system cannot be accessed because it is locked by the system. System Action: ITSM cannot complete the operation. User Response: See your system administrator. ANS1245E Format unknown
Explanation: The file system/drive was not ready for access. System Action: Processing stopped. User Response: Ensure that the drive is available to ITSM, and then retry the operation. ANS1252E File system/drive is bad. A directory exists that is missing either a . or .. entry. Have your service representative check the error log.
Explanation: ITSM tried to restore or retrieve a file, but it had an unknown format. System Action: File skipped. User Response: See your system administrator. ANS1246E A command-line argument exceeded the maximum length (maximum length) for a single token.
Explanation: Command-line arguments may not exceed maximum length characters. System Action: The command is not processed. User Response: Correct the command and retry the operation.
Explanation: The drive was not available for access. A directory exists that does not have either a '.' or '..' entry. System Action: Processing stopped. User Response: Ensure that the drive is operational, and then retry the operation. If unsuccessful, have your service representative check the error log.
654
IBM Tivoli Storage Manager: Messages
ANS1253E ANS1263E
ANS1253E File input/output error ANS1259E The image snapshot operation failed during: .
Explanation: An error was found while reading from or writing to the file. System Action: File or file system is skipped. 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. ANS1254E File write error
Explanation: During the image snapshot backup ITSM encountered an error while performing the specified task. System Action: Processing stopped. User Response: Contact your ITSM administrator. ANS1260E File is being recalled or has been recalled.
Explanation: An error was found while writing to the file. System Action: File skipped. User Response: Check your system to ensure that it is operating properly. ANS1255E File exceeds system/user file limits
Explanation: The file is being recalled by another process or has been recalled. System Action: File skipped. User Response: None ANS1261W The archive description you specified is the empty string. ITSM will use the default description (Archive Date: current date).
Explanation: A file being restored or retrieved exceeds system set limits for this user. System Action: File skipped. User Response: Ensure that the system limits are set properly. ANS1256E Cannot make file/directory
Explanation: The description option on the archive command may not specify a null string. System Action: Processing continues, and the description option is ignored. User Response: None. Specify at least one character in the description ANS1262E Password is not updated. Either an invalid current password was supplied or the new password does not fulfill the server password requirements.
Explanation: The directory path for files being restored or retrieved cannot be created. System Action: File skipped. User Response: Ensure that you have the proper authorization to create the directory for file being restored or retrieved. Make sure that you have write access. ANS1257E Error preparing object for restore.
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. User Response: Enter another password. ANS1263E The active policy set does not contain any backup copy groups. Unable to continue with selective backup.
Explanation: Clean-up failed due to an internal system error. System Action: Please see error log for more details. User Response: Please see your system administrator for assistance. ANS1258E The image snapshot operation failed.
Explanation: ITSM was not able to take a snapshot of the specified volume. Please refer to the error log for more information on the cause of failure. System Action: Processing stopped. User Response: Contact your ITSM administrator.
Explanation: You tried to do a selective backup and have specified a policy set that does not contain a backup management information (the copy group). System Action: ITSM did not backup the file. User Response: Create a management class that has a backup copy group, bind the file to that management class in your include-exclude list, and retry the operation. If unsuccessful, see your system
Chapter 5. Client and Data Protection for Lotus Notes Messages
655
ANS1264E ANS1272E
administrator for more information. ANS1264E The active policy set does not contain any archive copy groups. Unable to continue with archive. management class with the appropriate Space Management Technique value. ANS1268E This file has been migrated.
Explanation: You tried to archive a file or group of files and have specified a policy set that does not contain an archive management information (the copy group). System Action: ITSM did not archive the file. User Response: Create a management class that has an archive copy group, assign the file to the management class, either through your include-exclude list or with the ARCHMC option, and retry the operation. If unsuccessful, see your system administrator for more information. ANS1265E Encountered bad mount or filesystem, processing stopped.
Explanation: File has been migrated. If files that are hard linked together are migrated then files subsequent to the first one encountered get this. System Action: File is skipped. User Response: None. ANS1269I File is implicitly excluded.
Explanation: You tried to back up or migrate a file that is implicitly excluded. System Action: ITSM will not back up or migrate an implicitly excluded file. User Response: None. ANS1270I Forcing compression off to enable future server-free restore.
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, and correct any errors. If unsuccessful, see your system administrator for more information. ANS1266E Encountered bad mount or filesystem, processing stopped.
Explanation: Because ENABLESERVERFREE had been specified, and an attempted server-free data movement fell back to non-server-free, the ITSM 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 ENABLESERVERFREE option from the system option file, or set COMPRESSION off in the option file. ANS1271E Error Loading WINSOCK.DLL - not in Search Path
Explanation: An error was encountered trying to determine what the mounted file systems are. System Action: Processing stopped. Cannot recover. User Response: There is a bad filesystem or mount point on your system. Look at file systems and mounts, and correct any errors. If you used to have an FSM (HSM) file system but then removed HSM from it, make sure that there is no FSM mount for that filesystem; if it is still there then unmount it. If unsuccessful, see your system administrator for more information. ANS1267E The management class for file file-name does not allow migration. This file will not be migrated.
Explanation: ITSM cannot find the Windows Socket support file (WINSOCK.DLL) in the current search path. This message only applies when using TCP/IP communications. System Action: Connection to server fails. User Response: Shut down Windows and place the directory where this file resides in the DOS path statement. ANS1272E The logical volume snapshot agent is not available for this volume.
Explanation: The management class for this file does not allow migration System Action: File is skipped. User Response: Either have the ITSM 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
Explanation: During the image snapshot backup ITSM was not able to communicate with the logical volume snapshot agent (LVSA). System Action: Processing stopped. User Response: Please verify that the LVSA is
656
IBM Tivoli Storage Manager: Messages
ANS1273E ANS1287E
correctly installed on your system. If the problem persists please contact your ITSM administrator. ANS1273E The image plugin was not able to acquire an exclusive lock on volume: 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. ANS1278W Virtual mount point filespace-name is a file system. It will be backed up as a file system.
Explanation: To perform an off-line image backup or an image restore ITSM requires exclusive use of the volume. System Action: Processing stopped. 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 ITSM must have exclusive use of the volume. ANS1274E Error Loading WINSOCK.DLL
Explanation: A virtual mount point that is a file system is invalid and should be deleted. System Action: The virtual mount point is ignored. User Response: Delete the virtual mount point.
Explanation: Error loading the Windows socket support file into memory. This error only applies when using TCP/IP communications. System Action: Connection to server fails. User Response: Because this error is caused by insufficient memory, shut down running applications and retry. If the problem persists, see your system administrator. ANS1275E Error Loading Function(s) from WINSOCK.DLL
ANS1279W
Virtual mount point filespace-name cannot be used in a file system handled by automounter and is ignored.
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. System Action: The virtual mount point is ignored. User Response: Delete the virtual mount point. ANS1286E -nasnodename option required for this operation.
Explanation: Error loading one or more functions from the Windows socket support file. System Action: Connection to server fails. 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: 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 Volume could not be locked.
Explanation: You specified a Windows user account which did not have the security right to run as a service System Action: ITSM 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: The system call to lock the volume failed. System Action: Processing stopped. 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 ITSM must have exclusive use of the volume.
Explanation: You specified a Windows user account which did not have the security right to run as a service. ITSM encountered a problem attempting to grant this right automatically.
Chapter 5. Client and Data Protection for Lotus Notes Messages
657
ANS1288E ANS1308E
ANS1288E The image plugin is not supported on this platform. ANS1303E Client ended transaction
Explanation: ITSM does not support image operations on this platform. System Action: Processing stopped. User Response: Contact your ITSM administrator.
Explanation: The client system ended the operation with the server and ended the current transaction. System Action: Processing stopped. User Response: Restart the session. ANS1304W Active object not found
ANS1289W
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. System Action: Processing continues. User Response: Make sure the volume data is not corrupt by using system tools like chkdsk (Windows) or fsck (UNIX). ANS1300E Unable to reconstruct : necessary component was not restored.
Explanation: ITSM did not find an active object flagged for expiration on the server. The object is marked as expired by another ITSM operation. System Action: None. User Response: None. ANS1305E No data on server
Explanation: ITSM tried to do a restore or retrieve on an object that has no data associated with it. System Action: ITSM ended the current operation. User Response: See your system administrator to verify the problem. If the problem continues, see your system administrator. ANS1306E Bad verifier
Explanation: A subfile component was not received by the client during the restore process. System Action: Processing stopped. User Response: Please check error log for more information. ANS1301E Server detected system error
Explanation: You entered an incorrect password (verifier). System Action: Processing stopped. User Response: Retry the session with the correct password. ANS1307E Node in use
Explanation: The server detected a system error and notified the clients. System Action: Processing stopped. User Response: See your system administrator for further information on server activity. ANS1302E No objects on server match query
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. System Action: Processing stopped. User Response: Retry the operation, or see your system administrator to see what other operations are running for your node. ANS1308E Expiration date must be greater than todays date
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. System Action: Processing stopped. 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.
Explanation: Archive expiration date is too low, the date must be greater than todays date. System Action: ITSM canceled the current operation. User Response: Retry archiving the file with an expiration date that is higher than todays date.
658
IBM Tivoli Storage Manager: Messages
ANS1309W ANS1316E
ANS1309W Requested data is offline ANS1313E Size estimate exceeded
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: ITSM waits for offline storage media to become available and then continues. User Response: None. ANS1310E Object too large for server limits
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. System Action: Processing stopped. User Response: Retry the operation. If the problem 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. ANS1314E File data currently unavailable on server
Explanation: The object is too large. The configuration of the server does not have any data storage space that accepts the object. System Action: File skipped. User Response: See your system administrator to 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. System Action: ITSM ended the current operation. User Response: You can take any of the following actions: v Request the system administrator to add space to the storage pool. v For ITSM 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. ANS1312E Server media mount not possible
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. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, see your system administrator to determine the problem from the server console or the activity log. 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. ANS1315E Unexpected Retry request
Explanation: Unexpected Retry request. The server found an error while writing data to the servers data storage. System Action: Client retries the operation. User Response: None. ANS1316E The server does not have enough recovery log space to continue the current operation
Explanation: Server media mount not possible. The server timed out waiting for a mount of an offline volume. System Action: File skipped. 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.
Explanation: The server ran out of recovery log space. System Action: ITSM ended the current operation. User Response: This error is a temporary problem. Retry later or see your system administrator.
Chapter 5. Client and Data Protection for Lotus Notes Messages
659
ANS1317E ANS1330S
ANS1317E The server does not have enough database space to continue the current operation User Response: See your system administrator. ANS1323S Open Registration failed because an invalid node name was specified
Explanation: The server ran out of database space. System Action: ITSM ended the current operation. User Response: See your system administrator. ANS1318E The server does not have enough memory to continue the current operation.
Explanation: Open registration failed because the specified node name contains invalid characters. System Action: ITSM canceled the current operation. User Response: Retry with another node name that does not have any invalid characters. ANS1326S Unexpected Wait For Space from the server
Explanation: The server ran out of memory. System Action: ITSM ended the current operation. User Response: This is a temporary problem. Retry later or see your system administrator. ANS1319E An error occurred while trying to rename this file space:
Explanation: The client received an unexpected Wait For Space message from the server. System Action: ITSM ended the current operation. User Response: See your system administrator. ANS1327E The snapshot operation for volname failed. Error code: retcode.
Explanation: This operation cannot be completed because the file space could not be renamed. System Action: ITSM ended the current operation. User Response: Contact system administrator for more information. 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: IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. System Action: Snapshot processing stopped. User Response: Contact your IBM Tivoli Storage Manager administrator. ANS1328E An error occured generating delta file for file-name, return code retcode.
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. System Action: ITSM canceled the current operation. User Response: Check the file space name to see if it is correct, and retry the operation. ANS1321S Open Registration failed because the specified node name is defined in the server
Explanation: An error occurred while generating the delta file. The delta file cannot be created. System Action: Full backup is taken of the file, and a new version of the reference file is stored in the client cache. User Response: If the problem recurs, report the program error to your service representative. ANS1329S Server out of data storage space
Explanation: The server does not have space available to store the object. System Action: ITSM ended the current operation. 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: Open registration failed because a node is defined in the server with the same name. System Action: ITSM canceled the current operation. 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. System Action: ITSM canceled the current operation.
Explanation: This operation can not be completed because a restartable restore session is pending. The
660
IBM Tivoli Storage Manager: Messages
ANS1331E ANS1342E
operation is not allowed because the restartable session and the current operation affect the same file space. System Action: ITSM ended the current operation. User Response: Issue a query restore to see the conflict. Issue the cancel restore command to delete any unneeded restartable restore sessions. ANS1331E Only a ITSM authorized user can perform this Action. ANS1336I RSM service must be restarted for changes to become effective. User Response: Ask your system administrator to check the error log.
Explanation: RSM database files have been restored from the server and imported. The RSM service must be restarted for the updates to become effective. System Action: Processing continues. User Response: None. ANS1337I Restarting the RSM service...
Explanation: User must be a ITSM authorized user to perform this action. User is not password authorized and this action requires authorization. System Action: Processing stopped. 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 Please run the Mac OS X version of the application.
Explanation: RSM database files have been restored from the server and imported. ITSM is about to stop then restart the RSM service. System Action: Processing continues. User Response: None. ANS1338I Restart of the RSM service is completed.
Explanation: IBM Tivoli Storage Manager applications can only be used by a System Administrator. System Action: IBM Tivoli Storage Manager will quit. User Response: Run the Mac OS X version of IBM Tivoli Storage Manager. You will be prompted for a System Administrator name and password. ANS1333I Used block list used for the snapshot image backup of is different than list acquired before the start of snapshot.
Explanation: RSM database files have been restored from the server and imported. ITSM has restarted the RSM service on the users behalf. System Action: Processing continues. User Response: None. ANS1339E Restart of the RSM service failed. Restart the RSM service manually.
Explanation: The snapshot image backup used block list is taken before and after the start of the snapshot for informational purposes. System Action: Processing continues. User Response: None. ANS1334E Restoring a volume mount point to a non-empty directory.
Explanation: RSM database files have been restored from the ITSM server and imported. ITSM has tried to restart the RSM service on the users behalf but has run into a problem. System Action: Processing stopped. User Response: Restart the RSM service manually. ANS1340E Exporting RSM database files failed. No files will be backed up.
Explanation: You are trying to restore a volume mount point to a non-empty directory which is not allowed. Volume mount point is not restored. System Action: Processing continues. User Response: None. ANS1335E Attempt to import RSM database files failed. No changes effected.
Explanation: An error occurred while exporting the RSM database files. The database will not be backed up. System Action: Processing stopped. User Response: Ask your system administrator to check the error log. ANS1342E Client cache is locked; unable to continue with operation.
Explanation: An error occurred while importing the RSM database files. The database will not be updated. Reboot the machine and then restore RSM again. System Action: Processing continues.
Explanation: The client cache is currently locked by another process. System Action: Processing stopped.
Chapter 5. Client and Data Protection for Lotus Notes Messages
661
ANS1343E ANS1350E
User Response: Report the program error to your service representative. ANS1343E Wrong Key entered; unable to restore the file. ANS1347E The image snapshot operation failed. The percent of space to use for the SNAPSHOTCACHELocation, specified via the SNAPSHOTCACHESize, has been exceeded.
Explanation: Key entered does not match the key used for the backed up file. System Action: Processing stopped. User Response: Recollect the key used for backup. 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. System Action: Processing stopped. User Response: Run the Job in the foreground. ANS1345E No objects on server match object-nameobject-nameobject-name
Explanation: ITSM was not able to take a snapshot of 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. System Action: Processing stopped. User Response: If the problem persists please increase the SNAPSHOTCACHESize and/or change the value of the SNAPSHOTCACHELocation. ANS1348E Unable to satisfy the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options due to volume write activity.
Explanation: The specified file (object-name) does not have a match on the server. System Action: File skipped. 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 The image snapshot operation failed. The SNAPSHOTCACHELocation does not contain enough space for this snapshot image backup.
Explanation: ITSM was not able to take a snapshot of 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. System Action: Processing stopped. User Response: If the problem persists please modify the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options to better fit the normal disk write activity of the volume being backed up. ANS1349E The Logical Volume Snapshot Agent driver failed.
Explanation: ITSM 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. 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. System Action: Processing stopped. User Response: If the problem persists please increase the SNAPSHOTCACHESize and/or change the value of the SNAPSHOTCACHELocation.
Explanation: ITSM was not able to take a snapshot of the specified volume due to an unexpected error. System Action: Processing stopped. User Response: If the problem persists please contact your ITSM administrator. 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.
662
IBM Tivoli Storage Manager: Messages
ANS1351E ANS1360I
User Response: Please wait until the other IBM Tivoli Storage Manager process finishes with the volume and then retry the operation. ANS1351E Session rejected: All server sessions are currently in use ANS1355E Session rejected: Server disabled
Explanation: The server is in a disabled state and cannot be accessed for normal activity. System Action: ITSM canceled the current operation. 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
Explanation: ITSM has all available sessions in use and cannot accept a new one at this time. System Action: ITSM canceled the current operation. User Response: Retry the operation. If the problem continues, see your system administrator to increase the number of concurrently active sessions to the server. ANS1352E Session rejected: Password has expired
Explanation: No authorization. Registration is required by your system administrator. The server is not configured to allow open registration. System Action: Session not started. User Response: You must obtain a ITSM node and password from your system administrator. ANS1357S Session rejected: Downlevel client code version
Explanation: Your ITSM password has expired. System Action: ITSM canceled the current operation. You are not allowed to connect to the server until the password is updated. User Response: Update your password. ANS1353E Session rejected: Unknown or incorrect ID entered
Explanation: The server version and your client version do not match. The client code is downlevel. System Action: ITSM canceled the current operation. User Response: See your system administrator to see what version of ITSM to run for your location. ANS1358S Session rejected: Downlevel server code version
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. System Action: ITSM canceled the current operation. 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 nodename must be the same node which migrated the file. User Response: Ensure that you entered your ITSM 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. ANS1354E Session rejected: Duplicate ID entered
Explanation: The server version and your client version do not match. The server code is downlevel. System Action: ITSM canceled the current operation. User Response: See your system administrator to see what version of ITSM to run for your location. ANS1359E Session Rejected: The specified node name is currently in use
Explanation: Another process using this node name is active with the server. System Action: ITSM cannot connect to the server. ITSM canceled the current operation. User Response: If you are running a UNIX-based system, ensure that another process is not active with ITSM 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.
Explanation: The node name you specified is in use on the server. System Action: Session was not started. 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 compressesion is greater than the size of the file before compressed. System Action: Even though the size of the file increased, the file is compressed.
Chapter 5. Client and Data Protection for Lotus Notes Messages
663
ANS1361E ANS1371E
User Response: None. ANS1361E Session Rejected: The specified node name is currently locked User Response: See your system administrator immediately. ANS1367E Session Rejected: The server does not allow a signon as a Unicode enabled client
Explanation: The node name you specified is currently locked on the server. System Action: Session was not started. User Response: Check with your system administrator to find out why your node name is locked. ANS1362S SLM LICENSE EXCEEDED: The client licenses for ITSM are exceeded. See your system administrator.
Explanation: The client can not establish a connection to the server because of a unicode enabling mismatch between server and client. System Action: Session was not started. User Response: See your system administrator immediately. ANS1368S Session Rejected: The server is not licensed for this platform type. See your system administrator.
Explanation: Adding a new enrollment will exceed the product license count for ITSM. System Action: Execution of the client enrollment or connection request ends. User Response: See your system administrator. ANS1363E Session Rejected: The server does not have enough memory to allow a connection to be established.
Explanation: The server is not licensed for the requesting client type. System Action: Execution of the client enrollment or connection request ends. User Response: See your system administrator. ANS1369E Session Rejected: The session was canceled by the server administrator.
Explanation: The server does not have enough memory to allow your client to establish a connection with the server. System Action: Session was not started. User Response: Retry later or see your system administrator. ANS1364E Session Rejected: The server does not have enough recovery log space to allow a connection to be established.
Explanation: The server administrator canceled the current client session. System Action: Execution of the client connection request ends. User Response: See your system administrator. ANS1370E The user ID entered does not have the correct level of authority to access the client machine.
Explanation: The server ran out of recovery log space. System Action: Session was not started. User Response: This error is a temporary problem. Retry later or see your system administrator. ANS1365E Session Rejected: The server does not have enough database space to allow a connection to be established.
Explanation: The user ID entered cannot access this ITSM client. System Action: The ITSM operation ends. User Response: Grant authority to this user ID on the ITSM server so that it can access this ITSM client. ANS1371E Unable to reconstruct from subfile components.
Explanation: The server ran out of database space. System Action: Session was not started. User Response: See your system administrator. ANS1366E Session Rejected: The server has an internal error
Explanation: An error occurred while reconstructing this file from its subfile components. System Action: Processing stopped. User Response: Please check error log for more information.
Explanation: The client cannot establish a connection to the server because of an internal server error. System Action: Session was not started.
664
IBM Tivoli Storage Manager: Messages
ANS1372E ANS1378E
ANS1372E An inconsistency was detected between the client node and the node that is registered to the ITSM server. ANS1375E The snapshot operation failed.
Explanation: The user has probably coded the node option incorrectly. For instance, the node that is registered to the ITSM server might be a type of NAS, but the node is actually a non-NAS client. System Action: The ITSM operation ends. 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. ANS1373E The PRESNAPSHOTCMD command failed.
Explanation: IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. Please refer to the error log for more information on the cause of failure. System Action: Snapshot processing stopped. User Response: Contact your IBM Tivoli Storage Manager administrator. ANS1376E Unable to perform operation using a point-in-time copy of the filesystem. The backup/archive operation will continue without snapshot support.
Explanation: The command specified by the PRESNAPSHOTCMD option must complete successfully in order to perform the snapshot backup/archive operation. If the command completed 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 backup/archive operation, but without using a snapshot. 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. ANS1374W The POSTSNAPSHOTCMD command completed with a non-zero return code.
Explanation: IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. Please refer to the error log for more information on the cause of failure. The operation will continue without snapshot support. System Action: Snapshot processing stopped. User Response: Contact your IBM Tivoli Storage Manager administrator. ANS1377E Unable to perform operation using a point-in-time copy of the filesystem on volname. The backup/archive operation will continue without snapshot support.
Explanation: IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. Please refer to the error log for more information on the cause of failure. The operation will continue without snapshot support. System Action: Snapshot processing stopped. User Response: Contact your IBM Tivoli Storage Manager administrator. ANS1378E The snapshot operation failed. The SNAPSHOTCACHELocation does not contain enough space for this snapshot operation.
Explanation: If the command specified by the 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. 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.
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.
Chapter 5. Client and Data Protection for Lotus Notes Messages
665
ANS1379E ANS1404E
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. System Action: Processing stopped. User Response: If the problem persists, increase the SNAPSHOTCACHESize or change the value of the SNAPSHOTCACHELocation. ANS1379E The snapshot operation failed. The percent of space to use for the SNAPSHOTCACHELocation, specified via the SNAPSHOTCACHESize, has been exceeded. allowed. The default cache location is on the system drive. System Action: The client does not execute the snapshot operation. User Response: Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option. ANS1382E Server does not allow client-initiated connections for this node.
Explanation: IBM Tivoli Storage Manager was not able 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. 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. System Action: Processing stopped. User Response: If the problem persists, increase the SNAPSHOTCACHESize or change the value of the SNAPSHOTCACHELocation. ANS1380E The snapshot operation failed. The filesystem write activity prevented the Logical Volume Snapshot Agent from satisfying the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options.
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. System Action: The IBM Tivoli Storage Manager 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. 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. ANS1403E Error loading a required DLL
Explanation: IBM Tivoli Storage Manager was not able to take a snapshot of 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. System Action: Snapshot processing stopped. User Response: If the problem persists, modify the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options to better fit the normal disk write activity of the volume being backed up. ANS1381E The snapshot cache location cannot be located on the same volume that is being backed up.
Explanation: An error occurred while loading a dynamic link library. The DLL load failed. System Action: Processing stopped. User Response: Verify that your system software is up to date and that all DLLs required by the ITSM client are present. ANS1404E Error loading one or more functions from a required DLL
Explanation: An error occurred while loading a function from a dynamic link library. The DLL load failed. System Action: Processing stopped. User Response: Verify that your system software is up to date.
Explanation: The snapshot cache location is on the same volume that is being backed up, but this is not
666
IBM Tivoli Storage Manager: Messages
ANS1405I ANS1415W
ANS1405I service-name service needs to be restarted. ANS1412E Directory or file has bad EA data or inconsistent data.
Explanation: The service must be restarted for the restored changes to take effect. System Action: Changes are not effected. User Response: Restart the service. ANS1406I Performing operation using point-in-time copy of the filesystem: volname.
Explanation: Directory or file has bad EA data or inconsistent data. System Action: The client terminates. User Response: Check failing directory or file for bad EA data. Copy the directory to a new location and retry the operation. ANS1413W File filespace namepath-namefile-name is not recognized by the system as a disk file and cannot be processed. The file is skipped.
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. System Action: Operation proceeds. User Response: None. ANS1407I Performing operation using point-in-time copy of the filesystem.
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 include AUX, CON, NUL, PRN, COMx or LPTx, where x is any digit from 1 to 9 (for example, COM1, LPT3, etc.). System Action: The file is skipped. 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: 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. System Action: Operation proceeds. User Response: None. ANS1409E The remote copy process process ID on server could not be canceled.
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. System Action: None. User Response: Contact your ITSM administrator. ANS1410E Unable to access the network path.
Explanation: An open image group exists on the ITSM server and cannot be deleted due to missing backup delete rights for this node. System Action: Processing continues.
Explanation: The network path cannot be accessed due to a possible network problem. System Action: The client terminates. User Response: Ensure that the network is up and the path can be accessed using a system command, and retry the operation. ANS1411E A communication session was dropped.
User Response: Ask your ITSM 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. User Response: Contact your ITSM administrator to correct problems with server-free data movement.
Explanation: A communication session was dropped due to a possible network problem. System Action: The client terminates. User Response: Ensure that the network is up and retry the operation.
Chapter 5. Client and Data Protection for Lotus Notes Messages
667
ANS1416W ANS1425W
ANS1416W Management class name to which volume filespace-name is bound does not allow server-free data movement. retried 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. User Response: Contact your ITSM administrator to correct problems with server-free data movement. ANS1421E The image object object-type was not found on server.
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 with out server-free data movement. User Response: Contact your ITSM administrator to allow server-free data movement from this system. ANS1417W An error occured while obtaining physical extent map for volume filespace-name.
Explanation: The image object type filespace-namecould not be located on the server. System Action: Processing stopped. User Response: Contact your ITSM administrator. ANS1422W The image data for volume filespace-name is either compressed or its compression information can not be determined.
Explanation: An error occured while obtaining volumes filespace-name logical and physical layout. System Action: The requested operation will be retried with out server-free data movement. User Response: Contact your ITSM administrator to correct problems with server-free data movement. ANS1418W A call to ITSM API API-name failed.
Explanation: The image data was backed up either with compression or by an older client version. This data format cannnot be restored on server-free path. System Action: The requested operation will be retried without server-free data movement. User Response: None. ANS1423W The image for volume filespace-name was backed-up in old format.
Explanation: An unexpected error occured while performing server-free data movement. System Action: The requested operation will be retried with out server-free data movement. User Response: Contact your ITSM administrator to correct problems with server-free data movement. ANS1419W Remote copy operation for volume filespace-name failed or could not be restarted, return code retcode.
Explanation: The image data was backed up in old image (single object) format. This data format cannnot be restored on server-free path. System Action: The requested operation will be retried with out server-free data movement. User Response: None. ANS1424W Retrying failed image operation for volume filespace-name.
Explanation: An error occurred on server when starting or during the remote copy operation for volume filespace-name. System Action: The requested operation will be retried with out server-free data movement. User Response: Contact your ITSM administrator to correct problems with server-free data movement. ANS1420W Server-free path is not available for one or more disks 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. User Response: None. ANS1425W Retry of failed image operation for volume filespace-name is not possible due to severe error.
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 ITSM client does not match with the disk definition on the ITSM server. System Action: The requested operation will be
Explanation: A retry of image operation is not possible, because an unrecoverable ITSM client or server error has occured. Check your error log to see cause of failure. System Action: None. User Response: Contact your ITSM administrator.
668
IBM Tivoli Storage Manager: Messages
ANS1426E ANS1439I
ANS1426E An error occurred creating the Backup Registry Directory structure ANS1433E Extraneous argument input after keyword keyword
Explanation: An error occurred while creating the directory structure to the save/replace registry key. System Action: Registry function fails. User Response: See your system administrator. ANS1427I Registry Backup function completed successfully.
Explanation: A registry command was incorrectly entered. System Action: Registry function not invoked. User Response: Refer to the command reference for this command. ANS1434E Invalid argument input after keyword keyword
Explanation: Registry backup was successful. System Action: None. User Response: Continue with normal operations. ANS1428E Registry Backup function failed.
Explanation: A registry command was incorrectly entered. System Action: Registry function not invoked. User Response: Refer to the command reference for this command. ANS1435E An Error Occurred saving the Key.
Explanation: An error occurred while backing up the registry. System Action: Registry backup function fails. User Response: See your system administrator. ANS1429I Registry Restore function completed successfully.
Explanation: The active registry key cannot be saved. System Action: Registry backup operation terminates. User Response: See your system administrator. ANS1436E An Error Occurred replacing the Key.
Explanation: Registry Restore was successful. System Action: None. User Response: Continue with normal operations. ANS1430I The machine must be rebooted for the changes to take effect
Explanation: The backed up registry key is restored from the server but cannot be made active into the registry. System Action: Current Registry key remains active. User Response: See your system administrator. ANS1437I Event Log Backup function completed successfully.
Explanation: The machine must be started for the restored registry changes to take effect. System Action: None User Response: Reboot the machine ANS1431E Registry Restore Function Failed.
Explanation: Event Log backup was successful. System Action: None. User Response: Continue with normal operations. ANS1438E Event Log Backup function failed.
Explanation: An error occurred while restoring the registry key(s) from the server. System Action: Registry restore function fails. User Response: See your system administrator. ANS1432E Keyword Expected after keyword keyword.
Explanation: An error occurred while backing up the event logs. System Action: Event log backup function fails. User Response: See your system administrator. ANS1439I Event Log Restore function completed successfully.
Explanation: A registry command was incorrectly entered. System Action: Registry function is not invoked. User Response: Refer to the command reference for this command.
Explanation: Event Log Restore was successful. System Action: None. User Response: Continue with normal operations.
Chapter 5. Client and Data Protection for Lotus Notes Messages
669
ANS1440E ANS1450W
ANS1440E Event Log Restore Function Failed. User Response: Retry the operation after correcting the cause for failure. ANS1446W The volume layout of name is not supported by server-free.
Explanation: An error occurred while restoring the event log(s) from the server. System Action: Event Log Restore function fails. User Response: See your system administrator. ANS1441E Keyword Expected after keyword keyword.
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. ANS1447I Current user does not need to back up the default profile.
Explanation: A event log command was incorrectly entered. System Action: Event Log function is not invoked. User Response: Refer to the command reference for this command. ANS1442E Extraneous argument input after keyword keyword
Explanation: You are currently using the default profile, and there is no need to back it up. System Action: None. User Response: None. ANS1448E An error occurred accessing NTFS security information
Explanation: A event log command was incorrectly entered. System Action: Event Log function not invoked. User Response: Refer to the command reference for this command. ANS1443E Invalid argument input after keyword keyword
Explanation: An error occurred while attempting to access NTFS security information. System Action: Object will not be processed. User Response: See your system administrator or bypass by using SkipNTSecurity option. ANS1449E A required NT privilege is not held
Explanation: A event log command was incorrectly entered. System Action: Event Log function not invoked. User Response: Refer to the command reference for this command. ANS1444E An error occurred creating the Backup Registry Directory structure
Explanation: The user account running ITSM does not possess a required NT user right/privilege for performing the current operation. System Action: Object will not be processed. User Response: See your system administrator. ANS1450W The -FILENAME option was specified without a file name. Output will be written to filename.
Explanation: An error occurred while creating the directory structure to the save/replace registry key. System Action: Registry function fails. User Response: See your system administrator. ANS1445E ERROR: could not create NAS image object.
Explanation: The -FILENAME option was specified, but the file name was omitted. System Action: The output is written to the default file. User Response: Reissue the command and specify a valid file name, or use the information that was written to the default file.
Explanation: Creation of the NAS image object failed for one of following reasons: v An unauthorized user invoked the NAS command v NAS operations are not supported on the current platform v Cannot find the NAS plugin library. System Action: The requested NAS operation is not performed.
670
IBM Tivoli Storage Manager: Messages
ANS1451W ANS1470E
ANS1451W name: this type of mirrored volume is not supported by server-free. ANS1456I Mirror synchronization completed.
Explanation: This layout of mirrored volume 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. ANS1452W Server-free backup of FAT volumes is not supported.
Explanation: Synchronization of the volumes mirrors completed successfully. System Action: Processing continues. User Response: ANS1457E Mirror synchronization failed.
Explanation: Synchronization of the volumes mirrors failed. System Action: Processing stopped. User Response: Check the error log for more errors. Contact your systems administrator. ANS1458I OBF file for volume name is too small for serverfree data transfer.
Explanation: Backup of FAT volumes is not supported by server-free. System Action: Processing continues using non-server-free data movement. User Response: Refer to the documentation for information on what filesystems are supported by server-free. ANS1453W Used blocks backup of FAT filesystems is not supported. The entire volume will be backed up.
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. System Action: Processing continues. User Response: None. ANS1460W The file segment size entered is greater than the max size. Please increase the max size or decrease the file segment size.
Explanation: Used blocks backup of FAT volumes is not supported. The imagegapsize option option will be ingored and the entire volume will be backed up. System Action: Processing continues. User Response: Refer to the documentation. ANS1454W Used blocks information could not be obtained for name. The entire volume will be backed up.
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. ANS1469I Error processing filespace namepath-namefile-name: invalid encryption key
Explanation: Used blocks information could not be obtained for this volume. The imagegapsize option option will be ingored and the entire volume will be backed up. System Action: Processing continues. User Response: Contact your systems administrator. ANS1455I Resynching mirrors. Please wait.
Explanation: Key entered does not match the key used for the backed up file. System Action: Processing stopped. User Response: Recollect the key used for backup. ANS1470E Shared library libgpfs.so is not loaded for GPFS support: skip path_name
Explanation: The destination volume for server-free restore has mirrored layout. The mirrors are being resynched after the data restored. System Action: Processing continues. User Response:
Explanation: The load library that is provided to handle the GPFS ACL is not available on this system. System Action: Object skipped. User Response: Ensure that the GPFS software is installed on the system.
Chapter 5. Client and Data Protection for Lotus Notes Messages
671
ANS1473E ANS1481E
ANS1473E Session rejected: TCP/IP connection failure for Shared Memory ANS1477E CLUSTERNODE is set to YES but the cluster load library is not valid.
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. 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 problem continues, see your system administrator for further help. ANS1474E An error occurred using the Shared Memory protocol
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. System Action: Processing ends. User Response: Ensure that the latest cluster software is installed on the system. ANS1478E CLUSTERNODE is set to YES but the cluster software is not availableon this system.
Explanation: An error has occurred while reading or writing data through the Shared Memory communications protocol. System Action: ITSM cannot complete the requested operation. User Response: Check the trace log for additional information and retry the operation. If the problem continues, see your system administrator for further help. ANS1475E Insufficient authority to connect to the shared memory region
Explanation: The load library that the operating systems provides to obtain the cluster name is not available on this system. System Action: Processing ends. User Response: Ensure that the cluster software is installed on the system. 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. System Action: Processing ends. User Response: Ensure that the cluster software is configured properly. If the cluster is in the process of initialization, retry the operation at a later time. ANS1480E CLUSTERNODE is set to YES but the cluster service is not enabledon this system.
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. ANS1476E CLUSTERNODE is set to YES but the Cluster Information Daemon is notstarted.
Explanation: The cluster service has not been enabled on this system. System Action: Processing ends. User Response: Enable the cluster service on the system. ANS1481E The CLUSTERNODE option is not supported on this system.
Explanation: The HACMP Cluster Information Daemon must be started in order to specify the CLUSTERNODE option. System Action: Processing ends. User Response: Start the HACMP Cluster Information Dameon.
Explanation: This option is not supported on this system. System Action: Processing ends. User Response: Disable the CLUSTERNODE option in the local options file.
672
IBM Tivoli Storage Manager: Messages
ANS1482E ANS1493S
ANS1482E An unexpected error (retcode) occurred while the program was trying to obtain the clustername from the system. ANS1489E The WMI service failed to stop. No files will be restored.
Explanation: An unknown error occurred while the program was trying to obtain the cluster name from the cluster services. System Action: Processing ends. User Response: Contact your system administrator for more information. ANS1483I Schedule log pruning started.
Explanation: An error occurred while stopping the WMI service. The database will not be restored up. System Action: Processing stopped. User Response: Ask your system administrator to check the error log. ANS1490W File specification file-spec ignored. A file list has already been specified.
Explanation: The schedule log pruning function has begun. System Action: The schedule log is pruned. User Response: None. ANS1484I Schedule log pruning finished successfully.
Explanation: A non-option argument (file specification) was encountered after the -FILELIST has been processed. System Action: The argument is ignored. User Response: You may have either a -FILELIST or explicit file specifications on this command, but not both. ANS1491E Only one -FILELIST option allowed.
Explanation: The schedule log pruning function completed with no errors. System Action: None. User Response: None. ANS1485E Schedule log pruning failed.
Explanation: The -FILELIST option may only be specified once per command System Action: The command is not executed. User Response: Enter only one -FILELIST option on the command. ANS1492S Invalid virtual mountpoint filespace-name: File not found.
Explanation: The schedule log pruning function failed. System Action: The schedule log pruning function stops. User Response: Retry the command with the tracing turned on to help determine why the pruning function failed. ANS1486E Restoring WMI repository failed. No changes will be in effect.
Explanation: The specified VIRTUALMOUNTPOINT in the system options file is invalid because it could not be found in the file system. System Action: ITSM attempts to continue the current operation. User Response: Check the virtual mountpoint in the system options file and make sure it exists in the file system. Retry the operation. ANS1493S Invalid virtual mountpoint filespace-name: Access denied.
Explanation: An error occurred while restoring the WMI repository. The database will not be updated. System Action: Processing stopped. User Response: Ask your system administrator to check the error log. ANS1487E Backing up WMI repository failed. No files will be backed up.
Explanation: The specified VIRTUALMOUNTPOINT in the system options file is invalid because access to it is denied. System Action: ITSM attempts to continue the current operation. User Response: Check the VIRTUALMOUNTPOINT in the system options file and make sure it is accessible. Retry the operation.
Explanation: An error occurred while backing up the WMI repository. The database will not be backed up. System Action: Processing stopped. User Response: Ask your system administrator to check the error log.
Chapter 5. Client and Data Protection for Lotus Notes Messages
673
ANS1494S ANS1503E
ANS1494S Invalid virtual mountpoint filespace-name: Symbolic link. User Response: Ask your system administrator to check the error log. ANS1499E Creation of table of contents failed.
Explanation: The specified VIRTUALMOUNTPOINT in the system options file is invalid because it is a symbolic link and FOLLOWSYMBOLIC is not set. System Action: ITSM attempts to continue the current operation. User Response: Set the option FOLLOWSYMBOLIC to YES in the user options file. Retry the operation. ANS1495S Invalid virtual mountpoint filespace-name: Other error, rc = return-code.
Explanation: A failure occurred on the server during creation of the table of contents. System Action: The table of contents was not created. 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. ANS1500E Module dsmtca not found in secure directory.
Explanation: The specified VIRTUALMOUNTPOINT in the system options file is invalid. System Action: ITSM attempts to continue the current operation. 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: ITSM cannot find the Trusted Communication Agent module (dsmtca) in the appropriate directory. System Action: ITSM ends. 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 ANS1501E Trusted agent execution/owner permissions are invalid
Explanation: ITSM found a duplicate statement while processing the client options file, which might produce unexpected results. System Action: Processing continues. 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 Duplicate include/exclude option option file-name found while processing the client options passed by the server. This might produce unexpected results.
Explanation: The Trusted Communication Agent execution/owner permissions are invalid. System Action: ITSM ends. User Response: Have your system administrator check the installation instructions for the client to ensure that the Trusted Communication Agent permissions are set correctly. This error can be caused by installing ITSM 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: ITSM found a duplicate statement while processing the client options by the server, which might produce unexpected results. System Action: Processing continues. 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: The permissions of the Trusted Communication Agent do not allow it to be accessed by the user of the ITSM client. System Action: ITSM ends. User Response: See your system administrator. ANS1503E Valid password not available for server server-name. The administrator for your system must run ITSM and enter the password to store it locally.
Explanation: An error occurred while stopping the IIS services. The metabase will not be restored up. System Action: Processing stopped.
Explanation: The file containing the stored password for the specified server server-name is unavailable.
674
IBM Tivoli Storage Manager: Messages
ANS1504E ANS1513E
System Action: ITSM ends. User Response: The administrator for your system must set and store a new password. ANS1504E Error starting the Trusted Communication Agent process. ANS1509E Error setting semaphore value or waiting on semaphore.
Explanation: An error has occurred while attempting to set or wait on a semaphore. System Action: Processing ends. User Response: Probable system error. If the problem persists, restart the workstation. ANS1510E Trusted Communications Agent error attaching shared memory.
Explanation: An error has occurred starting the Trusted Communication Agent process; specifically, the fork() function has failed. System Action: ITSM ends. User Response: Probable system error. If the problem persists, restart the workstation. ANS1505E Trusted Communication Agent has terminated unexpectedly.
Explanation: An error has occurred while attaching the trusted agents shared memory. System Action: Return to caller. User Response: Stop application, check shared memory usage and retry the command. Read the tca.log file for the system error number. ANS1511I Invalid Restore session number entered. Try again.
Explanation: The Trusted Communication Agent has terminated unexpectedly. System Action: ITSM ends. User Response: Check the error log for more information. Retry the activity. If the problem persists, contact your service representative. ANS1506E Trusted Communication Agent received invalid request.
Explanation: You entered a number not shown in the list of restartable restores. The number you entered is either less than one or greater than the highest item number displayed. System Action: ITSM waits for you to enter a valid selection. User Response: Enter a number from the list or Q to quit. ANS1512E Scheduled event event failed. Return code = value.
Explanation: The Trusted Communication Agent has received an unknown request from the ITSM client. System Action: ITSM ends. User Response: Internal error. If the problem recurs, contact your service representative. ANS1507E This action requires ITSM administrative authority on this system.
Explanation: The scheduled event did not complete successfully. System Action: Scheduled event failed. User Response: Ensure that your environment is set up correctly. If the problem continues, see your system administrator to correct the problem. ANS1513E The object is skipped from rename. Error_condition.
Explanation: An activity has been attempted that must be performed by the ITSM administrator (for example, open registration, filespace delete or password update). System Action: ITSM ends. User Response: If the activity is required, the administrator for this system must perform it. ANS1508E Error allocating semaphores.
Explanation: An error has occurred because the semaphores you are attempting to allocate have become insufficient. System Action: Processing ends. User Response: Ask your system administrator for assistance, and possibly increase the number of semaphores in your system.
Explanation: ITSM skips the specified object from renaming because the object with the same long name but with different attributes exists on the server. System Action: The backup operation will continue. The specified object will be expired during the next incremental backup. User Response: The object is skipped if one of the following condition takes place: The long name object(LN) has more recent insert date than the short name object(SN).
Chapter 5. Client and Data Protection for Lotus Notes Messages
675
ANS1514W ANS1808E
The management classes for LN and SN dont match. The copygroups for LN and SN dont match. LN and SN have different owners. 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. ANS1805E Unable to restore symbolic link file-name.
Explanation: The client operating system is not able to create a symbolic link because the link points to a filename that is not given. System Action: Processing continues. User Response: Try the restore on a different operating system. ANS1806W Size exceeded the maximum file size limit on your system for filespace namepath-namefile-name of file-size.
Explanation: The key passwords are different. System Action: ITSM allows you to try again. User Response: Enter the correct password. ANS1515E Loading a table of contents failed.
Explanation: You tried to restore or retrieve a file that has exceeded the maximum file size limitation on your system. System Action: ITSM 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. ANS1807E Unable to recall file from server due to error from recall daemon.
Explanation: A failure occurred on the server during loading of the table of contents. System Action: The table of contents was not loaded. 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. ANS1802E Incremental backup of file-name finished with number failure
Explanation: The incremental backup of the specified file-name completed with the specified number of failures. System Action: Processing continues. User Response: Check the reasons for the failures. ANS1803E Archive processing of file-space name finished with failures.
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. System Action: File skipped. 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 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 archive of the specified file-space name completed with failures. System Action: Processing continues. User Response: Check the reasons for the failures. ANS1804E Selective Backup processing of file-space name finished with failures.
Explanation: The selective backup of the specified file-space name completed with failures. System Action: Processing continues. User Response: Check the reasons for the failures.
Explanation: The selected operation requires the current level of the Logical Volume Snapshot Agent. Use the Setup Wizard to update the LVSA.
676
IBM Tivoli Storage Manager: Messages
ANS1809W ANS1821E
System Action: The selected operation is not performed. User Response: Retry the operation after updating the Logical Volume Snapshot Agent. ANS1809W Session is lost; initializing session reopen procedure. 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 Invalid scheduling mode
Explanation: The session with the server has been lost. System Action: The system will attempt to reestablish session with ITSM. User Response: None. ANS1810E ITSM session has been reestablished.
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 retry the operation. ANS1817E Schedule function can only be run by a ITSM authorized user.
Explanation: The session with the server has been reestablished. System Action: Processing will now continue. User Response: None. ANS1811S ITSM session could not be reestablished.
Explanation: An attempt to use the schedule function failed because of improper authority. System Action: Processing stopped. User Response: See the ITSM authorized user for schedule function information. ANS1818E Schedule function not allowed in loop mode.
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. v The network connection to the server is down. v The communication program that ITSM is interacting with has encountered some problem. System Action: Processing is stopped. User Response: Check network connection to the server. Insure that the ITSM server is running. Insure that the communication program underlying ITSM is working properly. ANS1814E Unable to start scheduled event event
Explanation: The operation cannot be scheduled during a loop mode. System Action: Event does not occur. User Response: Enter the command again without the loop. ANS1819E Server cannot register address
Explanation: An address for a server was entered that cannot be recorded. System Action: Processing stopped. User Response: Ensure that you have the server specified correctly, and retry the operation. ANS1820E Command line options must be preceded by a -
Explanation: Scheduled event was 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, see your system administrator to correct the problem on the server. ANS1815E Either the window has elapsed or the schedule has been deleted
Explanation: An option was specified without a '' delimiter. System Action: Processing stopped. User Response: Enter the command again with a dash preceding each option. ANS1821E Unable to start POSTSCHEDULECMD/ PRESCHEDULECMD command
Explanation: Scheduled event was no longer valid on the server.
Explanation: The requested action required a new process to be created. Either an option or a schedule
Chapter 5. Client and Data Protection for Lotus Notes Messages
677
ANS1822E ANS1832S
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 ANS1827W Directories cannot be selected with the table of contents currently loaded on the server. User Response: Change the TRACEFILE value so that it is a location to which you have write access.
Explanation: The restore cannot be performed, because too many objects were selected. System Action: The restore is not performed. User Response: Retry the operation after reducing the number of objects selected. ANS1823E Invalid trace keyword - keyword
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. System Action: The directory is not selected for restore. 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. ANS1828E Screen size is too small for using the PICK option.
Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect. System Action: Client program did not initialize or tracing was not enabled in the applet. User Response: Correct the value. See the entry for TRACEFLAGS in the Trace Facility Guide document for a list of valid trace flags. ANS1824E Invalid trace file name (name too long).
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: ITSM 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: 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. ANS1825E Unable to close trace output file file-name.
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. ANS1831E Password expired. The administrator for this system must run ITSM to update the password.
Explanation: An error occurred during the closing of a trace output file-name (for example, not enough disk space). System Action: Processing continues. User Response: Check the options.doc file for a description of possible causes of the error, or see your system administrator. ANS1826E Unable to open trace output file file-name.
Explanation: The password expired. System Action: ITSM ends. User Response: The administrator for this system must update the password. ANS1832S Unable to send generated password using MailProg option
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. System Action: Client program did not initialize.
Explanation: ITSM cannot send the file containing the generated password to the user ID specified in the MailProg option. System Action: ITSM ends.
678
IBM Tivoli Storage Manager: Messages
ANS1834S ANS1865E
User Response: Have your service representative check the error log for reasons why the file was not sent to the user ID. ANS1834S Unable to write to file-name for storing password System Action: ITSM attempts to open default option file. User Response: Make sure specified option file exists and is valid. ANS1839E Cannot read password.
Explanation: ITSM cannot write to the specified file-name. System Action: Processing continues. User Response: Check access permissions and disk space. If unsuccessful, see your system administrator. ANS1835E 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: An error occurred in setting up the input file (for example, the terminal) to be read. System Action: Processing stopped. User Response: Check the attributes of the terminal. ANS1852E Server could not load the table of contents. Status: status reason: reason
Explanation: Either the password is not stored locally, or it was changed at the server. System Action: ITSM prompts you for the password if ITSM is running in the foreground. User Response: If ITSM was running as a background process, issue any ITSM command from the foreground. Enter the password in answer to the prompt. Then try your background ITSM command again. ANS1836S MailProg file-name failed with return code = value.
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: An error occurred with the specified MailProg file-name. System Action: ITSM ends. User Response: Check the return code for the MailProg file-name. See your system administrator if you are unable to resolve the problem. ANS1837S File space filespace-name is ignored. Processing continues.
Explanation: The specified filespace-name in the system options file is invalid. System Action: ITSM attempts to continue the current 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: 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.
Explanation: The specified options file-name could not be located or opened.
Explanation: An attempt to connect to the server 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.
Chapter 5. Client and Data Protection for Lotus Notes Messages
679
ANS1867E ANS1876E
System Action: Processing stopped. User Response: Retry the operation, or wait until the 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. ANS1867E The server generated a CRC for verb type CRC verb which does not match the verb received received verb. User Response: Make sure the client and server are at compatible levels. ANS1872E Unable to connect to NetWare target service server-name. Make sure the TSA NLM is loaded on the specified machine.
Explanation: ITSM interacts with the Target Service Agent (TSA) and the connection cannot be made to the Netware server-name. System Action: Processing stopped. User Response: Ensure that the TSA is loaded and retry the ITSM command. ANS1873E An unknown error occurred while processsing system object sys-obj-name: utility function func-name failed with error error
Explanation: The server calculates a CRC and notes the verb type. This did not match the verb received. System Action: The client indicates protocol error. User Response: Check the trace log for additional information and retry the operation. If the problem continues, see your system administrator for further help. 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: 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. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. ANS1874E Login denied to NetWare Target Service Agent server-name.
Explanation: SMS requires the parent of the object (container) to be present before the child or object can be created. System Action: Processing stops. 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. Please contact Novell to resolve it.
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. System Action: Processing stopped. User Response: Retry the ITSM command, supplying the correct LAN password. ANS1875E Unable to connect to target service. Out of memory.
Explanation: This error message is being returned from the NDS call ResolveName. It indicates that the read/write partition that the object resides on has been found but is unavailable at this time. Basically, there is no communication between the backup server and the server that has the read/write partition that contains this object. System Action: Object skipped. User Response: Report the program error to your service representative. ANS1871W The server CRC version is server CRC version which does not match the client version client CRC version.
Explanation: Not enough memory to connect to the Target Service Agent (TSA). System Action: Processing stopped. User Response: Either add memory to the server or free memory by unloading some programs, or by restarting the server. ANS1876E Unable to connect to target service. NetWare SMS return code = value.
Explanation: The server is using a CRC version that does not match the client. System Action: The client does no CRC checking.
Explanation: Unexpected return code value. System Action: Processing stopped. User Response: See your service representative.
680
IBM Tivoli Storage Manager: Messages
ANS1877E ANS1892W
ANS1877E The name is too long for ITSM to process. 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 ITSM is unable to use NWPWFILE password_file to connect TSA target service TSA_Target_Service, the file is corrupted.
Explanation: The name was being parsed. The parsing routine detected that ITSM cannot process it. System Action: ITSM canceled the current operation. User Response: See your service representative if this error persists. ANS1878E An unknown error occurred while processsing system object sys-obj-name: Service service-name and its dependent services could not be stopped.
Explanation: An unknown error occurred while 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. System Action: ITSM ended the current operation. User Response: Manually stop the service and retry the operation. ANS1879E NetWare NDS error on restore processing: **object nds_objectnds_object **TSA error tsa_error, tsa_error_text
Explanation: ITSM could not use the NWPWFILE to connect to Novell TSA interface. The file was corrupted. 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 ITSM will overwrite the corrupted file with correct information. ANS1882E Unable to stop service service-name; error error
Explanation: ITSM received an unexpected error from the Novell TSA interface. System Action: Object skipped. User Response: Report the program error to your service representative. ANS1880E TSA Connect error, NWSMConnectToTargetService TSA_Target_Service password file password_file. Userid = NetWare_userid failed with cc = TSA_ccode
Explanation: The service could not be stopped by the program. System Action: ITSM ended the current operation. User Response: Manually stop the service and retry the operation. ANS1891W SUBDIR is not a valid option when using FILELIST, SUBDIR will be ignored.
Explanation: ITSM received an unexpected error from 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. The user-id/password is invalid or expired. The user-id has inadequate security access. The user-id has insufficent rights to files and directorys. The user-id specified has a login restriction based on time-0f-day.
Explanation: When Specifing 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 Expire command is not allowed on the ITSM journaled filespace filespace.
Explanation: You cannot expire files from the server on a ITSM journaled filespace. System Action: The expire command will not work on this filespec User Response: If you want to expire this filepec
Chapter 5. Client and Data Protection for Lotus Notes Messages
681
ANS1895I ANS1902E
remove it from the local filesystem. ANS1895I Highest macro return code was return code value. ANS1900I Return code is 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 System Action: None. User Response: For return codes other than 0, the user may wish to verify the results of the client operation(s) and take diagnostic and repair actions, as necessary. ANS1896I ***** Restored number objects *****
Explanation: The return code has been issued for the preceding client command. 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 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. System Action: None. User Response: For return codes other than 0, the user may wish to verify the results of the client operation and take diagnostic and repair actions, as necessary. ANS1901I Highest return code was return code value.
Explanation: Indicates the number of objects ITSM 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. User Response: None. ANS1897I ***** Retrieved number objects *****
Explanation: Indicates the number of objects ITSM has retrieved. During a retrieve session, the running total is periodically printed to the screen of a command line client. System Action: Continue with retrieve. User Response: None. ANS1898I ***** Processed count files *****
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: 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 System Action: None. User Response: For return codes other than 0, the user may wish to verify the results of the client operation(s) and take diagnostic and repair actions, as necessary. ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
Explanation: ITSM has processed the specified number of files. System Action: Processing continues. User Response: None. ANS1899I ***** Examined count files *****
Explanation: ITSM has examined the specified number of files. System Action: Processing continues. User Response: None.
Explanation: The command specified by the 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. System Action: The client does not execute the scheduled event, and the result code of the scheduled event will be 12. User Response: Identify and repair the problem that caused the command to fail. If it is not necessary for
682
IBM Tivoli Storage Manager: Messages
ANS1903W ANS1912E
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. ANS1906I Destination must be specified for this operation when using FROMNODE.
Explanation: The user must specify a destination with a Restore/Retrieve command when using FROMNODE processing. System Action: Processing stopped. User Response: Retry the Restore/Retrieve command with a destination specified. ANS1907E An error occurred while trying to perform an object merge operation on the server.
Explanation: If the command specified by the 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. System Action: At a minimum, the result code of the scheduled event is 8. User Response: Identify and repair the problem that 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: Netware: The server is unable to perform a NetWare long name conversion. UNIX or Windows image backup: The open group used to group associated image components could not be closed. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. Netware: It is possible that a more recent level of the server can perform the conversion. 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. User Response: None. ANS1909E The scheduled command failed.
Explanation: Descriptions for archive files must not contain wildcard characters. System Action: Processing stopped. User Response: Enter an archive description that does not contain wildcard characters. ANS1905E NetWare SMS error processing filespace-namepath-namefile-name: error-text
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. 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. ANS1912E An invalid registry hive was specified.
Explanation: ITSM received an unexpected error from the Novell SMS interface. System Action: Object skipped. User Response: Report the program error to your service representative.
Explanation: The specified registry hive is invalid. System Action: Processing stopped. User Response: Correct the command and retry the operation.
Chapter 5. Client and Data Protection for Lotus Notes Messages
683
ANS1913E ANS1924E
ANS1913E An invalid registry subkey was specified. ANS1919E The specified eventlog is not valid.
Explanation: The specified eventlog is not valid. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1920E Too many arguments specified for the BACKUP EVENTLOG command.
Explanation: The specified registry subkey is invalid. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1914E The specified subkey isnt valid for the specified hive.
Explanation: The specified registry subkey is invalid for the specified registry hive. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1915E Too many arguments specified for the BACKUP REGISTRY command.
Explanation: Too many arguments were specified for the BACKUP EVENTLOG command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1921E Too many arguments specified for the RESTORE EVENTLOG command.
Explanation: Too many arguments were specified for the BACKUP REGISTRY command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1916E Too many arguments specified for the RESTORE REGISTRY command.
Explanation: Too many arguments were specified for the RESTORE EVENTLOG command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1922E Too few arguments specified for the BACKUP EVENTLOG command.
Explanation: Too many arguments were specified for the RESTORE REGISTRY command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1917E Too few arguments specified for the BACKUP REGISTRY command.
Explanation: Too few arguments were specified for the BACKUP EVENTLOG command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1923E Too few arguments specified for the RESTORE EVENTLOG command.
Explanation: Too few arguments were specified for the BACKUP REGISTRY command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1918E Too few arguments specified for the RESTORE REGISTRY command.
Explanation: Too few arguments were specified for the RESTORE EVENTLOG command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1924E The specified system object is not valid.
Explanation: The specified system object is not valid. System Action: Processing stopped. User Response: Correct the command and retry the operation.
Explanation: Too few arguments were specified for the RESTORE REGISTRY command. System Action: Processing stopped. User Response: Correct the command and retry the operation.
684
IBM Tivoli Storage Manager: Messages
ANS1925E ANS1937E
ANS1925E The specified system object type is not valid. ANS1932E An error replacing one or more registry keys.
Explanation: The specified system object type is not valid. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1926E The specified system object type is only valid on Windows NT.
Explanation: An error occurred replacing one or more registry keys. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1933E Error accessing file or device name.
Explanation: The specified system object type is only valid on Windows NT. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1928E An error occurred creating the registry staging directory.
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: An error occurred creating the registry staging directory. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1929E An error saving one or more registry keys.
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 Too many arguments specified for the BACKUP NTDS command.
Explanation: An error occurred saving one or more registry keys. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1930E An error occurred creating the eventlog staging directory.
Explanation: Too many arguments were specified for the BACKUP NTDS command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1936E Not enough arguments specified for the BACKUP NTDS command.
Explanation: An error occurred creating the eventlog staging directory. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1931E An error saving one or more eventlogs.
Explanation: Not enough arguments were specified for the BACKUP NTDS command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1937E No NTDS server name specified for the BACKUP NTDS command.
Explanation: An error occurred saving one or more eventlogs. System Action: Processing stopped. User Response: Correct the command and retry the operation.
Explanation: No NTDS server name was specified for the BACKUP NTDS command. System Action: Processing stopped. User Response: Specify NTDS server name at the command and retry the operation.
Chapter 5. Client and Data Protection for Lotus Notes Messages
685
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. System Action: Processing stopped. User Response: Install Active Directory before performing backup operation. ANS1939E File Replication Service backup failed.
Explanation: The operation cannot be performed because server version is downlevel. System Action: Processing stopped. User Response: Use correct server version. ANS1944E Error accessing file or device.
Explanation: IBM Tivoli Storage Manager encountered an error while backing up files under control of the Windows 2000 File Replication Service System Action: Processing stopped. 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. ANS1940E File Replication Service restore failed.
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. ANS1945E The long namespace has been removed from the local filespace. If you wish to proceed wth the backup/archive operation, rename your filespace on the server.
Explanation: IBM Tivoli Storage Manager encountered an error while restoring files under control of the Windows 2000 File Replication Service System Action: Processing stopped. 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 restore operation. ANS1941E System Volume backup failed.
Explanation: ITSM 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. System Action: Processing stopped. User Response: Add the long namespace support to the volume or rename(remove) the corresponding server filespace. ANS1946W File exists, skipping
Explanation: IBM Tivoli Storage Manager encountered an error while backing up files of the Windows 2000 System Volume System Action: Processing stopped. User Response: Examine the Windows 2000 File 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.
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).
Explanation: IBM Tivoli Storage Manager encountered an error while restoring files under control of the Windows 2000 File Replication Service System Action: Processing stopped. User Response: Examine the Windows 2000 File Replication Service Event log to insure the system volume was successfully initialized. Restart the service and retry the restore operation.
686
IBM Tivoli Storage Manager: Messages
ANS1947W ANS1958W
ANS1947W Directory exists, skipping ANS1951E Restore via Microsoft Volume Shadow Copy failed. See error log and the event log for more details.
Explanation: The client tried to restore or retrieve the 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 logged in dsmerror.log, and restore or retrieve processing continues with the next object. 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 Query system components via Microsoft Volume Shadow Copy failed.
Explanation: IBM Tivoli Storage Manager encountered an error while restoring via the Microsoft Volume Shadow Copy Service. System Action: Processing stopped. User Response: Retry the operation, restart the Volume Shadow Copy Service or contact your IBM Tivoli Storage Manager administrator. ANS1952E Initializing the COM Security failed. MS API function func-name failed with error error (error)
Explanation: IBM Tivoli Storage Manager encountered an error while initializing the COM Security. System Action: Processing stopped. User Response: Contact your IBM Tivoli Storage Manager administrator. ANS1954E Backup processing of file-space name finished with failures.
Explanation: IBM Tivoli Storage Manager encountered an error while querying the system writers under control of the Windows Volume Shadow Copy Service. See error log and the event log for more details. System Action: Processing stopped. User Response: Retry the operation, restart the Volume Shadow Copy Service, reboot the machine or contact your IBM Tivoli Storage Manager administrator. ANS1949E Initialize Microsoft Volume Snapshot failed.
Explanation: The backup of the specified file-space name completed with failures. System Action: Processing continues. User Response: Check the reasons for the failures. ANS1956E Too few arguments specified for the BACKUP GROUP command.
Explanation: IBM Tivoli Storage Manager encountered an error while initializing the Microsoft Volume Shadow Copy Service for backup or restore. System Action: Processing stopped. User Response: Retry the operation, restart the Volume Shadow Copy Service, reboot the machine or contact your IBM Tivoli Storage Manager administrator. ANS1950E Backup via Microsoft Volume Shadow Copy failed. See error log for more detail.
Explanation: Too few arguments were specified for the BACKUP GROUP command. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS1957E Showmembers and inactive are mutually exclusive parameters on a query.
Explanation: Showmembers and inactive are mutually exclusive parameters on a query.< /p> System Action: Processing terminates. User Response: Specify one of the mutually exclusive parameters on the query ANS1958W No base group found, attempting a full backup.
Explanation: IBM Tivoli Storage Manager encountered an error while performing backup via the Microsoft Volume Shadow Copy Service. System Action: Processing stopped. User Response: Restart the failing system service, restart the Volume Shadow Copy Service or reboot the system and then try the operation again.
Explanation: A differential backup requires a previous full backup to have been performed.< /p>
Chapter 5. Client and Data Protection for Lotus Notes Messages
687
ANS1959W ANS1976E
System Action: Processing continues, and a full backup is attempted. User Response: None. Perform a full backup before attempting a differential backup ANS1959W Removing previous incomplete group name Id:hi-lo ANS1964E A failure occured while contacting the WebSphere component-name.
Explanation: The attempted operation on the WebSphere component failed. System Action: Processing stops User Response: Check the error log for more details. ANS1971E ANS1972E Could not start dsmagent executable. Could not read portnumber, connection to agent failed. VSS writer for system object name does not exist. Restore skipped.
Explanation: A previous group backup failed without cleaning up the temporary groups correctly. System Action: The previous incomplete groups are removed and processing continues. User Response: None. ANS1960I Contacting the WebSphere component-name. This step could take a few minutes...
ANS1973I
Explanation: The application needs to contact the WebSphere component to obtain configuration information. System Action: Processing continues User Response: None. ANS1961E Could not detect any installation of the WebSphere Deployment Manager or Application Server.
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.. System Action: Object skipped. User Response: Install or enable the affected system service and retry the operation. ANS1974W Error removing previous incomplete group Id:hi-lo
Explanation: The application could not detect a supported WebSphere component installed. At this time, only the WebSphere Deployment Manager and Application Server are supported. System Action: Processing stops User Response: Verify that the intended WebSphere component is installed on this machine, and retry the operation. ANS1962E Operation Failed.
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. User Response: None. ANS1975W Error reason closing and renaming the group
Explanation: An error was encountered closing and renaming the temporary group. System Action: The backup is unsuccessful. User Response: Ensure that the user has the proper authority to update the group and retry the operation. ANS1976E The specified system service is not valid.
Explanation: The attempted operation on the WebSphere component failed. System Action: Processing stops 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 System Action: Processing stops User Response: Verify that the process has access to the indicated filespec and retry the operation.
Explanation: The specified system service is not valid. System Action: Processing stopped. User Response: Correct the command and retry the operation.
688
IBM Tivoli Storage Manager: Messages
ANS2000I ANS2603S
ANS2000I Unable to convert file names because MEMORYEFficientbackup option is ON. extent as possible, but the file should be examined to verify that it is usable. ANS2600S Browser trying to establish connection to client; received socket exception: exception-name
Explanation: ITSM has detected that a local name space change has occurred on the volume that is currently being backed up. ITSM would convert the file names to the new name space, but cannot because the option MEMORYEFficientbackup, is on. System Action: ITSM continues to backup using the old name space. User Response: Edit the dsm.opt file, and set MEMORYEFficientbackup to OFF. ANS2025E Login failed to NetWare file server server-name.
Explanation: The browser received the exception exception-name trying to connect to the ITSM client machine. System Action: The ITSM operation ends. User Response: Determine what might be causing this kind of an exception. Validate that the LAN is up and that you are trying to connect to the correct port number. ANS2601S Browser trying to establish connection to client; received unknown host exception: exception-name
Explanation: IBM Tivoli Storage Manager cannot establish an authorized connection to Netware file server through NDS. You could run out of connection numbers. System Action: Processing stopped. User Response: See your service representative. ANS2026W Bad sectors were detected on the volume volname.
Explanation: The browser received the exception exception-name trying to connect to the ITSM client machine. System Action: The ITSM operation ends. 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 ITSM client machine. ANS2602S Browser trying to establish connection to client; received IO exception: exception-name
Explanation: Bad sectors are skipped during image backup/restore operations. System Action: Processing continues. User Response: Make sure the volume data is not corrupt by using system tools like chkdsk (Windows) or fsck (Unix). ANS2048E Named stream of object object-namepath-namefile-name is corrupt.
Explanation: The browser received the exception exception-name trying to connect to the ITSM client machine. System Action: The ITSM operation ends. User Response: Determine what might be causing this kind of an exception. Retry the problem, and check if the LAN is down. ANS2603S Browser trying to establish connection to client; received exception: exception-name
Explanation: One or more of the files named streams are corrupt. System Action: The named stream is not restored/retrieved. 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: The browser received the exception exception-name trying to connect to the ITSM client machine. System Action: The ITSM operation ends. User Response: Determine what might be causing this kind of an exception. Determine if the LAN may be down, or if the ITSM Client Acceptor Daemon on the ITSM machine is up and running.
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
Chapter 5. Client and Data Protection for Lotus Notes Messages
689
ANS2604S ANS2612S
ANS2604S The Web client agent was unable to authenticate with the server. ANS2609S TCP/IP communications failure between the browser and the client machine.
Explanation: The ITSM Web client agent was unable to authenticate with the ITSM server. System Action: The ITSM operation ends. 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 ITSM Web client agent for any relevant messages. ANS2605S Browser could not re-establish connection to client; received protocol error.
Explanation: This error can occur due to any of the following: v The LAN connection to the ITSM client machine went down. v You are trying to connect to the ITSM client machine using the wrong port number. v The Client Acceptor Daemon on the ITSM client machine is not up and running and accepting connections. System Action: The ITSM operation ends. 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 ITSM client machine, and that it is listening on the correct port number. ANS2610S TCP/IP communications failure between the client and the server machine.
Explanation: The browser received a protocol error trying to re-connect to the ITSM client machine. System Action: The ITSM operation ends. User Response: Determine what might be causing this kind of an error. Determine if the ITSM browser and the ITSM client code might be out of sync. ANS2606S An invalid password was sent to the server.
Explanation: This error can occur if the LAN connection between the ITSM client machine and the server machine went down. System Action: The ITSM client ends. User Response: Retry the operation and make sure the LAN is up. Make sure that both the ITSM server and the ITSM client are up and running. ANS2611S An unknown error occurred in the browser.
Explanation: The ITSM password that was sent to the ITSM server was invalid. System Action: The ITSM operation ends. 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: An unknown error occurred in the applet running in the browser. System Action: The ITSM operation ends. User Response: Retry the operation. If the problem persists, turn on tracing and see if the trace to the browser console gives the reason for the error. ANS2612S An unknown error occurred in the client Please check the ITSM Error Log for any additional information
Explanation: The ITSM browser could not connect to the ITSM client machine. System Action: The ITSM operation ends. User Response: Determine what might be causing this kind of a problem. Determine if the LAN is down, or if the ITSM Client Acceptor Daemon on the ITSM machine is up and running. ANS2608S Nothing was selected so no operation was performed.
Explanation: An unknown error occurred in the ITSM client. System Action: The ITSM client ends. User Response: Retry the operation. If the problem persists, check the ITSM Error Log for any additional information.
Explanation: No object was selected in the GUI for the operation to be performed upon. System Action: The ITSM operation ends. 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.
690
IBM Tivoli Storage Manager: Messages
ANS2613S ANS2622S
ANS2613S A protocol error occurred in communications between the browser and the client. ANS2618S Browser trying to retrieve resources; received resource exception: exception-name
Explanation: A protocol error happened between the applet running in the browser and the ITSM client. System Action: The ITSM operation ends. User Response: Retry the operation. If the problem persists, turn on tracing and see if the trace to the browser console gives the reason for the error. ANS2614S A protocol error occurred in communications between the client and the server.
Explanation: The browser received the exception exception-name trying to retrieve resources from the ITSM client machine. System Action: The ITSM operation ends. User Response: Verify that the resources are installed correctly on the ITSM client machine. ANS2619S The Client Acceptor Daemon was unable to start the Remote Client Agent.
Explanation: A protocol error happened between the ITSM client and the ITSM server. System Action: The ITSM client ends. User Response: Retry the operation. If the problem persists, check the ITSM 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 nodename configured on the client machine.
Explanation: The ITSM Client Acceptor Daemon could not start the ITSM Remote Client Agent. System Action: The ITSM operation ends. User Response: Check the error log on the ITSM Web client agent for any relevant messages. Then correct the problem and retry. ANS2620W 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?
Explanation: The user ID that was entered is not the same as the nodename on this ITSM client. System Action: The ITSM operation ends. User Response: Verify that the nodename entered is configured correctly on the ITSM client. ANS2616I The machine must be rebooted for the changes to take effect
Explanation: The expand entire branch operation could take a long time and cannot be canceled once it is started. System Action: Processing stopped; waiting for user intervention. User Response: Answer 'Yes' to start the expand entire branch operation. If you answer 'No', the current operation will be canceled. ANS2621W This function is not available on the client platform
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 browser received a request that is not available on the ITSM client machine. For example, registry backup and restore are available only on the Windows platform. System Action: The ITSM operation ends. User Response: Request only those functions that are valid for the platform of the ITSM client machine. ANS2622S Invalid ID or password submitted.
Explanation: The user specified a destination target directory for restore or retrieve which is invalid. System Action: The ITSM operation ends. User Response: Retry the operation specifying a valid directory name.
Explanation: An invalid ID or an invalid password was submitted. System Action: The ITSM operation ends. User Response: Verify that the ID and the password that you entered are correct. If going to a different server (for example by hyperlinking) then make sure
Chapter 5. Client and Data Protection for Lotus Notes Messages
691
ANS2623S ANS3007I
that the different server has the same ID defined with the same password. ANS2623S Web Client applet level is out of sync with Web Client agent. unable to start, correct the problem, and restart the client. ANS3002I Session started for user userid (communication-method address).
Explanation: The Web Client applet and Web Client agents are at incompatible levels. System Action: The ITSM operation ends. 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 This operation requires client owner authority.
Explanation: A session was started for the specified user. System Action: None. User Response: None. ANS3003I Session ended for user userid.
Explanation: A session ended for the specified user. System Action: None. User Response: None. ANS3004E Session for user userid terminated invalid password entered.
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: 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: 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. ANS3000I communication-type communications available on port port-number.
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 ITSM Web Client (ip-address).
Explanation: The specified communications are available on the specified port number. System Action: None. User Response: None. ANS3001E Error initializing HTTPS communications - Secure HTTP not available.
Explanation: A request for the Web Client is being processed. System Action: None. User Response: None. ANS3007I ITSM client-name terminating - idle for idle-minutes minutes.
Explanation: An error occurred initializing HTTPS communications. Processing will continue, but secure 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
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.
692
IBM Tivoli Storage Manager: Messages
ANS3008E ANS4002E
User Response: None. ANS3008E Too many symbolic links were detected while resolving name file_name Use the Setup Wizard to install the LVSA. System Action: The selected operation is not performed. User Response: Retry the operation after installing the Logical Volume Snapshot Agent. ANS3013E The Logical Volume Snapshot Agent volume filter driver file was not found.
Explanation: While trying to resolve the file name, too many symbolic links were found. System Action: File skipped. User Response: Ensure that you do not have a looping symbolic link for the file. ANS3009E The Logical Volume Snapshot Agent plugin library was not found.
Explanation: The selected operation cannot be performed because the Logical Volume Snapshot Agent device driver file was not found. System Action: The selected operation is not performed. User Response: Retry the operation after correcting the cause for failure. ANS4000E Error processing filespace-name: file space does not exist
Explanation: The selected operation cannot be performed because the Logical Volume Snapshot Agent plugin library was not found. System Action: The selected operation is not performed. User Response: Retry the operation after correcting the cause for failure. ANS3010E The Logical Volume Snapshot Agent wizard operation failed.
Explanation: The Logical Volume Snapshot Agent wizard operation failed with a non-zero return code. Check the error log for additional information. System Action: The selected operation is not performed. User Response: 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: The specified file space (domain) is incorrect or does not exist on the workstation. If the message results from the BACKUP IMAGE command with the -MODE=INCREMENTAL option, it may mean that you have entered the name of a raw logical volume. The MODE=INCREMENTAL option is not valid for raw logical volumes. System Action: Processing stopped. User Response: Retry the operation specifying an existing domain (drive letter or file system name). If the message resulted from improper use of the MODE=INCREMENTAL option, retry the command, omitting that option. ANS4001E Error processing filespace-name: file space not known to server
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. System Action: The selected operation is not performed. 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 Install the Logical Volume Snapshot Agent.
Explanation: The number defining the correspondence between drive letter or file (domain name) and volume label is not known to the server. System Action: Processing stopped. User Response: Report the program error to your service representative. ANS4002E Error processing filespace-name: volume label does not exist
Explanation: The selected drive does not have a label. System Action: ITSM 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.
Explanation: The selected operation requires the Logical Volume Snapshot Agent, but it is not installed.
Chapter 5. Client and Data Protection for Lotus Notes Messages
693
ANS4006E ANS4020E
ANS4006E Error processing filespace namepath-namefile-name: directory path not found User Response: None. ANS4014E Error processing filespace namepath-namefile-name: unknown system error (error-code) encountered. Program ending.
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 Error processing filespace namepath-namefile-name: access to the object is denied
Explanation: An unknown and unexpected error-code occurred within the client program. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, see your administrator. ANS4015E Error processing filespace namepath-namefile-name: unexpected error (error-code) encountered
Explanation: An unexpected error occurred. This might be a low-level system or communication error that ITSM cannot handle or recover from. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help. ANS4016E Error processing filespace namepath-namefile-name: file is being executed; write permission denied
Explanation: Access to the specified file or directory is denied. You tried to read from or write to a file and you do not have access permission for either the file or the directory. System Action: Processing stopped. User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location. ANS4011E Error processing filespace namepath-namefile-name: no file handles available
Explanation: The current file cannot be opened to write to because it is currently being run by another operation. System Action: File skipped. 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. ANS4017E Error processing filespace namepath-namefile-name: too many symbolic links were detected while resolving name
Explanation: All file handles for your system are currently in use. No more are available. System Action: Processing stopped. 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. ANS4012E Error processing filespace namepath-namefile-name: file already exists
Explanation: While trying to resolve the file name, too many symbolic links were found. System Action: File skipped. User Response: Ensure that you do not have a looping symbolic link for the file. ANS4020E Error processing filespace namepath-namefile-name: format unknown
Explanation: The file being restored or retrieved exists. System Action: File is replaced or skipped depending on client options.
Explanation: ITSM tried to restore or retrieve a file, but it had an unknown format. System Action: File skipped.
694
IBM Tivoli Storage Manager: Messages
ANS4021E ANS4032E
User Response: See your system administrator. ANS4021E Error processing filespace namepath-namefile-name: file system not ready Windows ME (FAT32) 4,294,967,295 (4GB) Windows NT/2000 (NTFS) 17,592,185,978,880 (16TB-64K) System Action: File skipped. User Response: Ensure that the system limits are set properly. ANS4026W Error processing filespace namepath-namefile-name: size of file-size exceeded the maximum file size limit on your system
Explanation: The file system/drive was not ready for access. System Action: Processing stopped. User Response: Ensure that the drive is available to ITSM, and then retry the operation. ANS4022E Error processing filespace namepath-namefile-name: file system is invalid
Explanation: The drive was not available for access. A directory exists that does not have either a '.' or '..' entry. System Action: Processing stopped. User Response: Ensure that the drive is operational, and then retry the operation. If unsuccessful, have your service representative check the error log. ANS4025E Error processing filespace namepath-namefile-name: file exceeds user or system file limit
Explanation: You tried to restore or retrieve a file that has exceeded the maximum file size limitation on your system. System Action: ITSM 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. ANS4027S Error processing filespace namepath-namefile-name: internal program message value encountered
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)
Explanation: An unexpected catastrophic program failure occurred, indicated by value. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, see your system administrator or service representative. ANS4030E Error processing filespace namepath-namefile-name: disk space limit for this process reached
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)
Explanation: The disk space allocated for the client owner is full. System Action: Processing stopped. User Response: Free up disk space and retry the restore or retrieve operation. ANS4032E Error processing filespace namepath-namefile-name: file is not compressed.
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)
Explanation: A file that was flagged as compressed was not compressed, and the system failed. System Action: Processing stopped. User Response: See your system administrator to report this problem. This error is a system failure.
Chapter 5. Client and Data Protection for Lotus Notes Messages
695
ANS4033E ANS4988W
ANS4033E Error processing filespace namepath-namefile-name: file compressed on a different client machine that has more memory System Action: ITSM 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. ANS4041W Error processing filespace namepath-namefile-name: Out of free space or inodes in file system to migrate or recall.
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: ITSM canceled the operation. User Response: Obtain a machine with more memory and retry the operation. ANS4034E Error processing filespace namepath-namefile-name: unknown system error
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: ITSM terminates the current operation for this file system. User Response: Remove some files in the file system, and then run reconciliation. Retry the operation. ANS4900W Schedule schedule name has opened a new session with the server.
Explanation: An unknown error occurred. This might be a low-level system or communication error that ITSM cannot handle or recover from. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help. ANS4036E An error occurred saving the registry key.
Explanation: A scheduled event ended due to a connection failure. The scheduled event had to be restarted outside it's normal start-up window to continue the operation. System Action: Be advised that there are multiple sessions associated with the scheduled event. User Response: none. ANS4987E Error processing filespace namepath-namefile-name: the object is in use by another process
Explanation: The active registry key cannot be saved. System Action: Registry backup operation terminates. User Response: See your system administrator. ANS4038E An error occurred processing file system filespace name.
Explanation: File system filespace name is corrupted or contains one or more corrupted directories and cannot be processed. System Action: File system is skipped. User Response: Check your system to ensure that it is operating properly. For the Windows environment, run CHKDSK utility for the failing drive. More information about corrupted directories can be found in dsmerror.log. ANS4040E Error processing filespace namepath-namefile-name: file system filespace name has exceeded its space management quota.
Explanation: Access to the specified file or directory is denied. You tried to read from or write to a file and you do not have access permission for either the file or the directory. System Action: Processing stopped. User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location. ANS4988W File filespace namepath-namefile-name is currently unavailable on server and has been skipped.
Explanation: You tried to restore or retrieve a file that is currently not available from the ITSM server. System Action: ITSM 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.
Explanation: ITSM detects that the file system has exceeded its quota. No more data can be migrated out of this file system.
696
IBM Tivoli Storage Manager: Messages
ANS4989E ANS5004S
ANS4989E Error processing filespace namepath-namefile-name: the directory is in use by another process. All objects in the directory and any of its subdirectories are skipped. ANS4999E 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 User Response: None. ANS5000W Unable to update password
Explanation: The specified directory is being used by another process. You tried to read from or write to a directory that is currently being used by another process. The objects contained in the directory and its subdirectories are not backed up. System Action: Processing stopped for that directory. If other files and directories were also specified in this backup, they are processed User Response: Ensure that you specified the correct 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. ANS4991I Application Type Application Message Id Application Message
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 ITSM to register with server
Explanation: This is a message sent by the application you are currently running with ITSM. System Action: ITSM logs the application message. User Response: Refer to the documentation for the application that you are using. ANS4992W Application Type Application Message Id Application Message
Explanation: This client must be registered with this server. System Action: ITSM ends. User Response: The root user must register the client with the server. ANS5002E Open registration failed
Explanation: This is a message sent by the application you are currently running with ITSM. System Action: ITSM logs the application message. User Response: Refer to the documentation for the application that you are using. ANS4993E Application Type Application Message Id Application Message
Explanation: During the change password, update password, or open register dialog, the open registration failed. System Action: ITSM did not register this system. User Response: Reenter the password, or see your system administrator to register this system. ANS5003S Invalid Management Class assigned to directories. Please see the error log.
Explanation: This is a message sent by the application you are currently running with ITSM. System Action: ITSM logs the application message. User Response: Refer to the documentation for the application that you are using. ANS4994S Application Type Application Message Id Application Message
Explanation: An invalid management class was assigned. System Action: ITSM cannot perform the requested operation. User Response: Retry the operation using a valid management class. If unsuccessful, have your service representative check the error log. ANS5004S No backup copy group in the management class used for directories. Please see the error log.
Explanation: This is a message sent by the application you are currently running with ITSM. System Action: ITSM logs the application message. User Response: Refer to the documentation for the application that you are using.
Explanation: The management class contained no backup copy group for directories.
Chapter 5. Client and Data Protection for Lotus Notes Messages
697
ANS5005E ANS5016E
System Action: ITSM did not complete the backup operation. User Response: Have your service representative check the error log. ANS5005E Table of contents information is not available for the selected images. 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. User Response: Continue with normal operations. ANS5012E Server out of backup data storage space
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. System Action: Processing stopped. User Response: Start a new restore window to get current information. ANS5006W The policy set does not contain any backup copy groups. Unable to continue with backup.
Explanation: The server ran out of space in its backup data storage. System Action: ITSM cannot complete the requested backup operation. Any files displayed on the lower half of the backup activity panel were successfully backed up. User Response: See your system administrator. ANS5013E Not enough memory for backup operation
Explanation: You tried to back up the files using a policy set that contained no backup management information (the copy group). System Action: ITSM did not back up the file(s). User Response: Change the management class that binds the files, and retry the operation. ANS5007W The policy set does not contain any archive copy groups. Unable to continue with archive.
Explanation: ITSM cannot allocate memory for the specified backup operation. System Action: ITSM cannot complete the requested operation. User Response: Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned might also help, or see your system administrator. ANS5014I Backup completed
Explanation: You tried to archive the files using a policy set that contains no archive management information (the copy group). System Action: ITSM did not archive the files. User Response: Change the management class that binds the files, and retry the operation. ANS5008W Incorrect password entered
Explanation: The backup was completed. System Action: ITSM backed up the files. User Response: Continue with normal operations. ANS5015I Restore stopped by user
Explanation: You entered a password that was incorrect. System Action: ITSM cannot connect to the server without the correct password. User Response: Reenter the password, or ask your system administrator for the current password. ANS5009W New password entries are not the same
Explanation: You requested to stop the restore operation. Attention: If you were restoring files with overwrite option specified, the file you restored last can be damaged (partially overwritten). System Action: Restore stopped. User Response: Continue with normal operations. ANS5016E Not enough memory for restore operation
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
Explanation: ITSM cannot allocate memory for the requested restore operation.
698
IBM Tivoli Storage Manager: Messages
ANS5017I ANS5091S
System Action: ITSM cannot complete the requested restore operation. User Response: Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned can also help, or see your system administrator. ANS5017I Restore completed Attention: If you were retrieving files with overwrite option specified, the file you retrieved last can be damaged (partially overwritten). System Action: Retrieve stopped. User Response: Continue with normal operations. ANS5023E Not enough memory for retrieve operation
Explanation: A restore was completed. System Action: ITSM restored the files. User Response: Continue with normal operations. ANS5018E Not enough memory for archive operation
Explanation: ITSM cannot allocate memory for the specified retrieve operation. System Action: ITSM cannot complete the requested retrieve operation. User Response: Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned might also help, or see your system administrator. ANS5024I Retrieve completed
Explanation: ITSM cannot allocate memory for the requested archive operation. System Action: ITSM cannot complete the archive operation. User Response: Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned might also help, or see your system administrator. ANS5019I Archive stopped by user
Explanation: A retrieve was completed. System Action: ITSM retrieved the files. User Response: Continue with normal operations. ANS5025E The nodename contains invalid characters.
Explanation: You requested to stop the archive operation. System Action: Archive stopped. User Response: Continue with normal operations. ANS5020E Server out of archive data storage space
Explanation: The specified node name has invalid characters. System Action: ITSM canceled the current operation. User Response: Retry with another node name that has valid characters. ANS5026W MatchAllChar and MatchOneChar options MUST precede Include/Exclude options
Explanation: The server ran out of space in its archive data storage. System Action: ITSM cannot complete the requested archive operation. Any files displayed on the lower half of the archive activity panel were successfully archived. User Response: See your system administrator. ANS5021I Archive completed
Explanation: The MatchAllChar and MatchOneChar options must precede any include-exclude options. System Action: The ITSM client ends the current application. User Response: Move the MatchAllChar and MarchOneChar options before any include-exclude options. ANS5091S Unexpected Wait_For_Space from the server.
Explanation: An archive was completed. System Action: ITSM archived the files. User Response: Continue with normal operations. ANS5022I Retrieve stopped by user
Explanation: You requested to stop the retrieve operation.
Explanation: The client received an unexpected Wait For Space message from the server. System Action: ITSM ended the current operation. User Response: See your system administrator.
Chapter 5. Client and Data Protection for Lotus Notes Messages
699
ANS5092S ANS5128E
ANS5092S Server out of data storage space. ANS5124S Open registration failed because there is no default domain.
Explanation: The server does not have any more space available to store the object. System Action: ITSM ended the current operation. User Response: Report to your system administrator that a storage pool on the server is full. ANS5093S SLM_LICENSE_EXCEEDED: The client licenses for ITSM are exceeded. See your system administrator.
Explanation: Open registration failed because a default policy domain does not exist for you to place your node. System Action: ITSM canceled the current operation. User Response: See your system administrator. ANS5125S Open registration failed because an invalid node name was specified.
Explanation: Adding a new enrollment will exceed the product license count for ITSM System Action: Execution of the client enrollment or connection request ends. User Response: See your system administrator. ANS5094E Session Rejected. Sufficient server memory is not available.
Explanation: Open registration failed because the specified node name has invalid characters. System Action: ITSM canceled the current operation. User Response: Retry with another node name that does not have any invalid characters. ANS5126S Filespaces with duplicate names are not supported. Please unmount the duplicate filespace.
Explanation: The server does not have enough memory to allow your client to establish a connection with the server. System Action: Session was not started. User Response: Retry later or see your system 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 selected filespace has a duplicate volume label. Because ITSM 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: ITSM cannot select the volume. User Response: If the filespace needs to be available to the system, exit ITSM, and assign a volume label to the filespace. Restart ITSM and retry the operation. Otherwise, unmount the duplicate filespace. ANS5127W File excluded
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. System Action: ITSM ends the current operation. User Response: Retry your operation. The filespace you were working on should not exist any more. See your system administrator for more information. ANS5123S Open registration failed because the specified node name is already defined in the server.
Explanation: A file cannot be processed because it is explicitly excluded by the include-exclude list defined in the options file. System Action: ITSM did not back up the file. User Response: Look in the options file for the include-exclude list of that file. Consider changing the options file or see your system administrator. ANS5128E No Backup Copy Group
Explanation: Open registration failed because a node is defined on the server with the same name. System Action: ITSM canceled the current operation. User Response: Retry with another node name.
Explanation: The management class for this file did not have a backup copy group specified. System Action: ITSM did not back up the file. User Response: See your system administrator.
700
IBM Tivoli Storage Manager: Messages
ANS5129E ANS5146W
ANS5129E No Archive Copy Group ANS5136E Not enough memory for archive delete operation
Explanation: The management class for this file did not have an archive copy group specified. System Action: ITSM did not archive the file. User Response: See your system administrator. ANS5130W No filespaces selected for deletion
Explanation: ITSM cannot allocate memory for the specified archive delete operation. System Action: ITSM cannot continue with the requested archive delete operation. User Response: Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned might also help, or see your system administrator. ANS5138I Archive delete completed
Explanation: You requested a deletion operation without selecting a client domain. System Action: ITSM cannot perform a deletion without a domain selected. User Response: Select the volumes you want to delete and retry the operation. ANS5132I Filespace deletion canceled by user
Explanation: An archive delete was completed. System Action: ITSM deleted the archived files. User Response: Continue with normal operations. ANS5139E Your node does not have permission to delete archived files.
Explanation: You requested to cancel the filespace deletion operation. System Action: The filespace deletion operation stopped. User Response: Continue with normal operations. ANS5133I Filespace filespace was deleted
Explanation: Your node is not allowed by the server to delete archived files. System Action: ITSM did not delete the archived files. User Response: See your system administrator. ANS5145W Server cannot restart the last restore request. Do you want to restore without restart?
Explanation: The specified filespace was successfully deleted. System Action: ITSM deleted the filespace. User Response: Continue with normal operations. ANS5134E Unable to delete the filespace because this node does not have permission to delete archived data and/or backed up data.
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. ANS5146W You cannot perform this operation while accessing data for another node. Do you wish to switch back to accessing your own node?
Explanation: You tried to delete a filespace that you do not have permission to access. System Action: ITSM canceled the operation. User Response: Ensure that you specify the correct filespace, or specify a filespace you have access to. ANS5135I Archive delete stopped by user
Explanation: The user cannot perform the selected operation while accessing another users data. System Action: Processing stopped; waiting for user intervention. User Response: Answer Yes to switch back to accessing the server as the original node.
Explanation: You requested to stop the archive delete operation. System Action: Archive delete stopped. User Response: Continue with normal operations.
Chapter 5. Client and Data Protection for Lotus Notes Messages
701
ANS5148W ANS5158S
ANS5148W 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? ANS5153E Session Rejected: The server does not allow a signon as a Unicode enabled client.
Explanation: The client cannot establish a connection to the server because of a unicode enabling mismatch between server and client. System Action: Session was not started. User Response: See your system administrator immediately. ANS5154I File is implicitly excluded
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. System Action: Processing stopped; waiting for user 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: You tried to back up or migrate a file that is implicitly excluded. System Action: ITSM will not back up or migrate an implicitly excluded file. User Response: None. ANS5155E Valid password not available. The ITSM administrator for your system must run ITSM and enter the password to store it locally.
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 This node currently has a pending restartable restore session. The requested operation cannot complete until this session either completes or is canceled.
Explanation: The file containing the stored password for the specified server server-name is unavailable. System Action: ITSM ends. User Response: The ITSM administrator for your system must set and store a new password. ANS5157E This action requires ITSM administrative authority on this system.
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. System Action: ITSM ended the current operation. 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 system administrator.
Explanation: An activity has been attempted that must be performed by the ITSM administrator (for example, open registration, filespace delete or password update). System Action: ITSM canceled the operation. User Response: If the activity is required, the ITSM administrator for this system must perform it. ANS5158S Filespace deletion is in progress. Try again later.
Explanation: The filespace is in the process of being deleted. System Action: ITSM cannot complete the requested operation. 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.
Explanation: The server is not licensed for the requesting client type. System Action: Execution of the client enrollment or connection request ends. User Response: See your system administrator.
702
IBM Tivoli Storage Manager: Messages
ANS5164E ANS5182E
ANS5164E Backing up/Archiving drives with duplicate volume labels is not allowed. ANS5174E A required NT privilege is not held.
Explanation: You tried to back up or archive a drive that has a duplicate volume label. Because ITSM 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: ITSM cannot select the drive. User Response: If the volume needs to be available to the system, exit ITSM, and assign a volume label to the drive. Restart ITSM and retry the operation. ANS5165E Drive has no volume label.Backup/Archive not allowed.
Explanation: The user account running ITSM does not possess a required NT user right/privilege for performing the current operation. System Action: Object will not be processed. User Response: See your system administrator. ANS5178E Restart of the RSM service failed. Restart the RSM service manually.
Explanation: RSM database files have been restored from the ITSM server and imported. ITSM has tried to restart the RSM service on the users behalf but has run into a problem. System Action: Processing stopped. User Response: Restart the RSM service manually. ANS5179E Restoring a volume mount point to a non-empty directory.
Explanation: You tried to backup or archive a drive that has no volume label. System Action: ITSM rejected the selected drive. 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. ANS5166E An error occurred saving the registry key
Explanation: You are trying to restore a volume mount point to a non-empty directory which is not allowed. Volume mount point is not restored. System Action: Processing continues. User Response: None. ANS5181E Invalid selection; A specific backup set must be selected.
Explanation: The active registry key cannot be saved. System Action: Registry backup operation terminates. User Response: See your system administrator. ANS5169E The destination path must contain a drive letter
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: The entered path must begin with a drive letter, colon, and root slash. System Action: ITSM did not continue with the requested operation. User Response: Enter the destination path in the correct format. ANS5173E An error occurred accessing NTFS security information.
Explanation: An error occurred while attempting to access NTFS security information. System Action: Object will not be processed. User Response: See your system administrator or bypass by using SkipNTSecurity option.
Explanation: Multiple backup sets were selected to be restored, 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.
Chapter 5. Client and Data Protection for Lotus Notes Messages
703
ANS5183W ANS5193E
ANS5183W Objects of different types cannot be restored at the same time. ANS5189E Unable to set APF extended attribute for file:pathnameReturn code: returncode strerrorReason code: reasoncode
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. System Action: No processing takes place. User Response: Select objects of the same type to perform restore operation. ANS5184E Illegal Operation On Following Object: object
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. System Action: File processed without setting attribute. User Response: The attribute must be set manually. ANS5190E Unable to set PROGCTL extended attribute for file:pathnameReturn code: returncode strerrorReason code: reasoncode
Explanation: Requested operation cannot be performed on this object. System Action: This object will be skipped. User Response: Try another operation on this object, or try the same operation on another object. ANS5186E Server is downlevel, System Services and System State backup disabled for this session.
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. System Action: File processed without setting attribute. User Response: The attribute must be set manually. ANS5191E NT Active Directory is not online. Offline backup is not supported.
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 Unable to set SHAREAS extended attribute for file: pathname Return code: returncode strerror Reason code: reasoncode
Explanation: NT Active Directory is not online when performing a backup operation. Offline backup is not supported. System Action: Processing stopped. User Response: Reboot computer and turn on Active Directory, and try the operation again. ANS5192E NT Active Directory is online. Online restore is not supported.
Explanation: You must be the file owner or have superuser authority. System Action: File processed without setting attribute. User Response: The attribute must be set manually. ANS5188E Unable to clear SHAREAS extended attribute for file: pathname Return code: returncode strerror Reason code: reasoncode
Explanation: NT Active Directory is online when performing a restore operation. Online restore is not supported. System Action: Processing stopped. User Response: Reboot computer and enter Active Directory repair mode, then try the operation again. ANS5193E Certificate Services is not online. Offline backup is not supported.
Explanation: You must be the file owner or have superuser authority. System Action: File processed without setting attribute. User Response: The attribute must be set manually.
Explanation: Certificate Services is not online when performing a backup operation. Offline backup is not supported. System Action: Processing stopped. User Response: Start Certificate Services and try the operation again.
704
IBM Tivoli Storage Manager: Messages
ANS5194E ANS5205E
ANS5194E Certificate Services is online. Online restore is not supported. ANS5200I service-name service needs to be restarted.
Explanation: Certificate Services is online when performing a restore operation. Online restore is not supported. System Action: Processing stopped. User Response: Stop Certificate Services and try the operation again. ANS5196W Invalid key password entered.
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 key password is invalid. System Action: ITSM allows you to try again. User Response: Enter the correct password. ANS5197E File Replication Service backup failed.
Explanation: The specified function is not implemented. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS5202E An error occurred creating the registry staging directory
Explanation: IBM Tivoli Storage Manager encountered an error while backing up files under control of the Windows 2000 File Replication Service System Action: Processing stopped. 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. ANS5198E File Replication Service restore failed.
Explanation: An error occurred creating the registry staging directory. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS5203E An error saving one or more registry keys
Explanation: IBM Tivoli Storage Manager encountered an error while restoring files under control of the Windows 2000 File Replication Service System Action: Processing stopped. 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 restore operation. ANS5199I The machine must be rebooted for the changes to take effect. Would you like to reboot the machine now?
Explanation: An error occurred saving one or more registry keys. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS5204E An error occurred creating the eventlog staging directory
Explanation: An error occurred creating the eventlog staging directory. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS5205E An error saving one or more eventlogs
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: ITSM None. User Response: Select YES to reboot the machine immediately.
Explanation: An error occurred saving one or more eventlogs. System Action: Processing stopped. User Response: Correct the command and retry the operation.
Chapter 5. Client and Data Protection for Lotus Notes Messages
705
ANS5206E ANS6001S
ANS5206E An error replacing one or more registry keys ANS5211E The Cluster Service is offline. The Cluster Service must be online to perform a restore operation.
Explanation: An error occurred replacing one or more registry keys. System Action: Processing stopped. User Response: Correct the command and retry the operation. ANS5207I The machine must be rebooted for the changes to take effect
Explanation: The Cluster Service is offline. The Cluster Service must be online to restore the cluster database. System Action: ITSM None. User Response: Start the Cluster Service and retry the operation. ANS5212E An error occurred while trying to rename file space.
Explanation: The machine must be started for the changes to take effect. System Action: ITSM backed up the files. User Response: Reboot the machine ANS5208E An invalid date or time was entered.
Explanation: This operation can not be completed because the file space could not be renamed. System Action: ITSM ended the current operation. User Response: Contact system administrator for more information. ANS5213W NAS objects cannot be selected with other objects for backup.
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. System Action: Processing stops. 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.
Explanation: Backing up NAS objects with other types of objects is not allowed. System Action: No processing takes place. User Response: Select NAS objects without other objects to perform backup NAS operation. ANS5214W NAS objects cannot be selected with other objects for restore.
Explanation: IBM Tivoli Storage Manager encountered an error while backing up files of the Windows 2000 System Volume System Action: Processing stopped. User Response: Examine the Windows 2000 File Replication Service Event log to insure the system volume was successfully initialized. Restart the service and retry the backup operation ANS5210E System Volume restore failed.
Explanation: Restoring NAS objects with other types of objects is not allowed. System Action: No processing takes place. User Response: Select NAS objects without other objects to perform restore NAS operation. ANS5222E Archive description is too long.
Explanation: IBM Tivoli Storage Manager encountered an error while restoring files of the Windows 2000 System Volume System Action: Processing stopped. User Response: Examine the Windows 2000 File Replication Service Event log to insure the system volume was successfully initialized. Restart the service and retry the restore operation.
Explanation: The archive description exceeds the maximum value. System Action: Processing stopped. User Response: Reissue the command and specify a valid archive description. 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. ITSM cannot backup/restore such files.
706
IBM Tivoli Storage Manager: Messages
ANS7421W ANS7524E
System Action: ITSM cannot complete the requested operation. User Response: Remove the NULL character by renaming the file or folder. ANS7421W Unable to reset the Windows archive attribute for file filename. The return code from Windows API SetFileAttributes() is rc. ANS7507W Invalid node entry
Explanation: An invalid entry is entered on the Node Name field. System Action: ITSM prompts you to enter a valid node name. User Response: Enter a valid node name or see your system administrator for the correct syntax. ANS7508W Duplicate authorization
Explanation: The Backup-Archive client was unable to reset the archive attribute for the file listed in the message. This error is due to an error received from the Windows API function SetFileAttributes(). System Action: Processing stopped. User Response: Report this error to the system administrator. ANS7503W Invalid drive entry
Explanation: The authorization rule entered by the user is already defined. Duplicate rules are not allowed. System Action: ITSM allows you to enter a different rule. User Response: Enter an authorization rule that has not been defined yet or cancel defining authorization rules. ANS7509W Drive and/or volume label do not exist
Explanation: An invalid entry is entered on the Drive field. System Action: ITSM prompts you to enter a valid drive letter. User Response: Enter a valid drive letter or see your system administrator for the correct syntax. ANS7504W Invalid directory entry
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: ITSM 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. ANS7521E Error Loading WINSOCK.DLL - not in Search Path
Explanation: An invalid entry is entered on the Directory field. System Action: ITSM prompts you to enter a valid directory. User Response: Enter a valid directory or see your system administrator for the correct syntax. ANS7505W Invalid filename entry
Explanation: ITSM cannot find the Windows Socket support file (WINSOCK.DLL) in the current search path. This message only applies when using TCP/IP communications. System Action: Connection to server fails. User Response: Shut down Windows and place the directory where this file resides in the DOS path statement. ANS7524E Error Loading WINSOCK.DLL
Explanation: An invalid entry is entered on the Filename field. System Action: ITSM prompts you to enter a valid file name. User Response: Enter a valid file name or see your system administrator for the correct syntax. ANS7506W Invalid label entry
Explanation: Error loading the Windows socket support file into memory. This error only applies when using TCP/IP communications. System Action: Connection to server fails. 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: An invalid entry is entered on the Label field. System Action: ITSM prompts you to enter a valid volume label. User Response: Enter a valid volume label or see your system administrator for correct syntax.
Chapter 5. Client and Data Protection for Lotus Notes Messages
707
ANS7525E ANS7532E
ANS7525E Error Loading Function(s) from WINSOCK.DLL of the Logical Volume Snapshot Agent. User Response: See the appropriate Using the Backup-Archive Client book for your operating system for correct use of the named option. ANS7529E The logical file system specified with the (-SNAPSHOTROOT) option is identical to the logical file system specified in the file specification.
Explanation: Error loading one or more functions from the Windows socket support file. System Action: Connection to server fails. 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. ANS7526E The (-SNAPSHOTROOT) option is not valid in conjunction with any of the following options: -FILELIST, -GROUPNAME, and -VIRTUALFSNAME.
Explanation: The logical file system specified with the (-SNAPSHOTROOT) option cannot match the logical file system specified in the file specification. The (-SNAPSHOTROOT) option is intended to indicate a logical file system different than the logical file system in the file specification. System Action: Processing stopped. User Response: See the appropriate Using the Backup-Archive Client book for your operating system for correct use of the named option. ANS7530E The snapshot_volume_name cannot end with a directory delimiter.
Explanation: The (-SNAPSHOTROOT) option is incompatible with the -FILELIST, -GROUPNAME, and -VIRTUALFSNAME options and cannot be used in conjunction with any one of those options. System Action: Processing stopped. User Response: See the appropriate Using the Backup-Archive Client book for your operating system for correct use of the named option. ANS7527E The (-SNAPSHOTROOT) option is not valid in conjunction with num-specs file specifications.
Explanation: The snapshot_volume_name cannot end with a directory delimter. This name should specify the root of a logical volume, e.g., /snapshot, x:, \\machine\x$, SNAP_VOL:, etc. System Action: Processing stopped. User Response: See the appropriate Using the Backup-Archive Client book for your operating system for correct use of the named option. ANS7531E The (-SNAPSHOTROOT) option is invalid when processing the NetWare NDS or Server Specific Information.
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. System Action: Processing stopped. User Response: See the appropriate Using the Backup-Archive Client book for your operating system for correct use of the named option. ANS7528W The (-SNAPSHOTROOT) option is not valid in conjunction with the Logical Volume Snapshot Agent. Processing will continue without the use of the Logical Volume Snapshot Agent.
Explanation: The (-SNAPSHOTROOT) option is only inteneded with NetWare file server volumes and is not compatible with processing the NDS or Server Specific Information on NetWare. System Action: Processing stopped. User Response: See the appropriate Using the Backup-Archive Client book for your operating system for correct use of the named option. ANS7532E The logical file system specified with the (-SNAPSHOTROOT) option cannot be a remote NetWare file system.
Explanation: The (-SNAPSHOTROOT) option is incompatible with the Logical Volume Snapshot Agent. The Logical Volume Snapshot Agent provides a comprehensive snapshot solution withot 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. System Action: Processing continues without the use
Explanation: The (-SNAPSHOTROOT) option is only inteneded with local NetWare file server volumes and is not compatible with remote NetWare volumes. System Action: Processing stopped. User Response: See the appropriate Using the Backup-Archive Client book for your operating system
708
IBM Tivoli Storage Manager: Messages
ANS7551E ANS7701E
for correct use of the named option. ANS7551E The source path cannot contain a drive letter information, it cannot back up or archive files from a drive with a duplicate volume label. System Action: ITSM cannot select the drive. User Response: If the volume needs to be available to the system, exit ITSM, and assign a volume label to the drive. Restart ITSM and retry the operation. ANS7641E Registry Backup failed
Explanation: The entered path cannot contain a drive letter. System Action: ITSM did not continue with the requested operation. User Response: Enter the source path in the correct format. ANS7555E The destination path must contain a drive letter
Explanation: ITSM An error occurred while backing up the registry. System Action: Registry backup function fails. User Response: See you system administrator. ANS7642E An Error occurred creating the registry directory structure
Explanation: The entered path must begin with a drive letter, colon, and root slash. System Action: ITSM did not continue with the requested operation. User Response: Enter the destination path in the correct format. ANS7556E An invalid drive letter was entered
Explanation: An error occurred while creating the directory structure to save/replace registry key. System Action: Registry function fails. User Response: See you system administrator. ANS7643E An error occurred saving the registry key
Explanation: You entered an invalid drive letter. System Action: ITSM prompts you for the correct drive ID. User Response: Reenter the drive ID in the correct format. ANS7560E Drive drive-name has no volume label. Backup/Archive not allowed.
Explanation: The active registry key cannot be saved. System Action: Registry backup operation terminates. User Response: See your system administrator. ANS7650E An error occurred replacing the registry key
Explanation: The specified drive-name selected cannot be backed up. System Action: ITSM rejected the selected drive. 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. ANS7561E Drive drive-name is unavailable
Explanation: The backed up registry key(s) were restored from the server but cannot be made active into the registry. System Action: Current Registry key remains active. User Response: See your system administrator. ANS7660E Registry activation failed
Explanation: An error occurred while restoring the registry key from the server. System Action: Registry restore function fails. User Response: See your system administrator. ANS7701E Create directory failed
Explanation: In an attempt to process a file, the specified drive-name was found unavailable. System Action: ITSM did not process the file. User Response: Determine why the drive was not available, make it ready, and retry the operation. ANS7564E Backing up/Archiving drives with duplicate volume labels is not allowed.
Explanation: The specified new directory cannot be created. System Action: Specify another directory name. User Response: See your system administrator.
Explanation: You tried to back up or archive a drive that has a duplicate volume label. Because ITSM uses the volume label to keep track of backup/archive
Chapter 5. Client and Data Protection for Lotus Notes Messages
709
ANS7709E ANS8014E
ANS7709E Restore operation failed. Not all files were restored. System Action: This value is used as the program exit code. User Response: None. ANS8003I Process number process ID started.
Explanation: Restore operation failed due to an error. System Action: Operation completed. User Response: Check the error log for more details. ANS7730E Event Log Backup failed
Explanation: An error occurred while backing up the event logs. System Action: Event log backup function fails. User Response: See your system administrator.
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. System Action: None. User Response: None. ANS8008W Redirection inside macro whose output is redirected is ignored.
ANS7731E
Event Log Restore failed
Explanation: An error occurred while restoring the event logs from the server. System Action: Event Log restore function fails. User Response: See your system administrator. ANS7732E An Error occurred creating the event log directory structure
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. User Response: None. ANS8009E Exiting due to command or option errors.
Explanation: An error occurred while creating the directory structure to save the event logs. System Action: Event Log function fails. User Response: See your system administrator. ANS8000I Server command: command
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: Fix the option file parameter in error and restart the client, or restart the client with proper command line parameters. ANS8012E Option processing storage exhausted.
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. User Response: None. ANS8001I Return code return code value.
Explanation: During processing of the client options file, the client runs out of memory. System Action: The client session is ended. User Response: Make more memory available and restart the administrative client. ANS8014E Insufficient information to connect to host.
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. System Action: None. User Response: None. ANS8002I Highest return code was return code value.
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
Explanation: At exit from the client, the highest return code encountered during the session is displayed.
710
IBM Tivoli Storage Manager: Messages
ANS8015E ANS8024E
communications method and then specify all that information in your client options file or on the administrative client command line. ANS8015E File file spec, error code error code from options processing. User Response: Reissue the command and include the -ID and -PASSWORD parameters on the command line. ANS8020E Unable to open file file spec for output.
Explanation: The file name specified in the -OUTFILE option cannot be opened. System Action: The -OUTFILE parameter is ignored. User Response: Allow processing to continue or exit the session and correct the file name. ANS8021E Exiting Batch mode session due to output file error.
Explanation: An unknown error code is returned from the routine that processes the client options file. System Action: The administrative client session is 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 file specified in the -OUTFILE parameter cannot be opened for a session running in Batch mode. System Action: The administrative client session is ended. User Response: Reissue the command with a valid output file name or make space available for the output file. ANS8022E Output will be written only to stdout.
Explanation: The specified command line parameter exceeds the maximum length for a command line parameter. System Action: The administrative client session is ended. User Response: Reissue the command with a shorter parameter. ANS8017E Command line parameter parameter number: parameter is not valid.
Explanation: The file specified in the -OUTFILE parameter cannot be opened, so output is written only to the standard output stream. System Action: Output that would have been written to the output file is written to the standard output stream. User Response: Allow processing to continue or exit the session and correct the file name. ANS8023E Unable to establish session with server.
Explanation: The command line parameter shown is not a valid administrative client parameter. System Action: The administrative client session is ended. User Response: Reissue the command with valid parameters. 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. System Action: The administrative client session is ended. User Response: Reissue the command with no server command. ANS8019E Id and password must be supplied in Batch mode.
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. System Action: The administrative client session is ended. User Response: Attempt to correct the error. If the problem persists, contact your service representative. ANS8024E End of macro after continued command line.
Explanation: A server command has been encountered on the command line, but no administrator ID or password, or both, are specified. System Action: The administrative client session is ended.
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. User Response: Correct the macro in error.
Chapter 5. Client and Data Protection for Lotus Notes Messages
711
ANS8025E ANS8036E
ANS8025E I/O Error reading command input. 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: The client is unable to read an input command from the terminal. System Action: The administrative client session is ended. User Response: Correct the problem on the terminal and retry the administrative session. ANS8026E Input line longer than maximum of max length characters. Use continuation.
Explanation: A macro command is encountered that does not contain a macro name. System Action: The command is ignored. User Response: Reissue the macro command with a macro file name. ANS8032E Could not allocate storage to process macro file spec.
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: The client cannot allocate enough memory to process the macro shown. System Action: The macro is ignored and an error is returned. User Response: Make more memory available to the client and retry the macro command. ANS8034E Your administrator ID is not recognized by this server.
Explanation: An input command contains an opening comment mark but no closing comment mark. System Action: The input command is ignored. User Response: Reissue the command with matching comment marks. ANS8028E Command longer than maximum of max length characters.
Explanation: The administrator ID entered is not known to the requested server. System Action: The administrative session terminates. User Response: Ensure that you are using a registered administrative ID for the server to which you are connecting. ANS8035E Interrupted by user.
Explanation: An input command longer than the maximum command length allowed has been entered. System Action: The input command is ignored. User Response: Reissue the command with fewer characters. This could mean replacing series of repeating blanks with a single blank. ANS8029E Macro processing terminated.
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 Administrative command not valid in Mount mode.
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: The Mount Mode option has been specified but the client encounters what appears to be a server command on the command line. System Action: The administrative client session is ended. User Response: Reissue the command with no server command.
Explanation: After variable substitution, an input command is longer than the maximum command length allowed. System Action: The input command is ignored.
712
IBM Tivoli Storage Manager: Messages
ANS8037E ANS8054E
ANS8037E Missing name for redirection file. ANS8047E Buffer overflow.
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 Unable to open file file spec for redirection.
Explanation: A communications buffer overflow occurs. System Action: The client session is ended. User Response: Retry the operation. If the problem persists, contact your service representative. ANS8049E Connection timed out.
Explanation: The connection to the server cannot be established. System Action: The client session is ended. User Response: Check for a networking problem. If the problem persists, contact your service representative. ANS8051E User is not authorized to get prompted for encryption key
Explanation: A command has been entered that specifies an output redirection file, but the file cannot be opened. System Action: The command is ignored and an error is returned. User Response: Reissue the command with a valid output file name or make space available for the output file. ANS8041E The server connection has been lost and cannot be re-established.
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 ITSM 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 ITSM authorized user backs up a file). ANS8052E Unable to decrypt file filespace namepath-namefile-name ....Please try to restore this file individually
Explanation: During an administrative session, the client discovers that the connection with the server has been severed; an attempt to reestablish the connection fails. System Action: The client session is ended. User Response: Determine the cause of the failure; then try to restart the session at a later time. If the problem persists, contact your service representative. ANS8045E Communications error.
Explanation: File could not be decrypted and restored. System Action: File is not restored. User Response: Restore the file separately. ANS8053E Network cannot be accessed.
Explanation: An unexpected communications error occurs during an administrative session. System Action: The client session is ended. 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. ANS8046E System failure.
Explanation: An error occurs accessing the network. System Action: The client session is ended. User Response: Retry the administrative session. If the problem persists, contact your service representative. ANS8054E No memory available to service request.
Explanation: The client connection with the server has terminated due to a system error. System Action: The client session is ended. User Response: Contact your service representative.
Explanation: Sufficient server memory is not available. System Action: The client session is ended. User Response: Retry the administrative session. If the problem persists, contact your service representative.
Chapter 5. Client and Data Protection for Lotus Notes Messages
713
ANS8055E ANS8500I
ANS8055E No server resources available. ANS8064E Communication timeout. Reissue the command.
Explanation: Sufficient server resources are not available. System Action: The client session is ended. User Response: Retry the administrative session. If the problem persists, contact your service representative. ANS8056E Your administrator ID is locked.
Explanation: The connection to the server is ended because of a communication timeout from the server. System Action: The server does not process the command. User Response: Reissue the command. If necessary, increase the values of IDLETIMEOUT and COMMTIMEOUT options in the server options file. ANS8494E Error during buffer operation (file name:line number) error code: error code
Explanation: The administrative ID entered has been locked by a system administrator and cannot be used. System Action: The client session is ended. User Response: Contact your system administrator to unlock your ID. ANS8057E The requested language files are not available.
Explanation: Error occurs when doing the following operations: 1. Creating input buffer. 2. Retrieving data from buffer. 3. Retrieving the pointer to field data. 4. Clearing input buffer. 5. Deleting input buffer. System Action: The administrative client session ends. User Response: Contact your service representative. ANS8495E Error while writing data (file name:line number) error Code: error code
Explanation: The NLS repository for the language specified is not available. System Action: The client session is ended. 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: An error occurs while writing data to the session. System Action: The administrative client session ends. User Response: Contact your service representative. ANS8496E Error during session operation (file name:line number) error code: error code
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. ANS8061E Session Rejected: The server does not allow a signon as a Unicode enabled administrative client
Explanation: An error occurs during one of the following operations: 1. Retrieving session description. 2. Initializing session description. 3. Initializing window description. 4. Creating the session. 5. Writing title to the display. 6. Writing prompt to the display. System Action: The administrative client session ends. User Response: Contact your service representative. ANS8500I User action cannot be completed due to the following error:
Explanation: The administrative client is unable to establish a connection to the server because of a unicode enabling mismatch between server and client. System Action: The client session is ended. User Response: Register a new administrator from a different administrative client or the server console, and signon with the new administrator ID.
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.
714
IBM Tivoli Storage Manager: Messages
ANS8501E ANS9003E
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 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 ITSM Administrators graphical user interface while attempting to display an informational, warning, or error message related to the current window or your requested action. System Action: The system may or may not process your requested action. 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. ANS8516E The values entered for the New Password and Reenter New Password fields do not match. Type the same value into both fields.
Explanation: An internal processing error has occurred in the ITSM Administrators graphical user interface while processing your requested action. Message ANS8000I, which displays with this message, identifies your requested action. System Action: The system does not process your requested action. User Response: 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 ITSM 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 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: You have entered different values into the New Password and Reenter New Password fields. System Action: The system does not process your requested action. 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.
Explanation: You have not entered or selected a value for a required field. System Action: The system does not process your requested action. User Response: Enter or select a valid value for this required field. ANS9003E program-name: file system for path-name is not in the dsmmigfstab file.
Explanation: A severe error has occurred. The message displaying with this message identifies the actual error. System Action: The ITSM Administrators graphical user interface closes. User Response: v Restart the ITSM 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.
Explanation: ITSM cannot find the file system in the dsmmigfstab file. System Action: ITSM cannot complete the requested operation. User Response: Ensure that the file system is both valid and local, and that it is an FSM file system.
Chapter 5. Client and Data Protection for Lotus Notes Messages
715
ANS9004E ANS9024E
ANS9004E program-name: cannot update file-system because it is not an FSM file system. System Action: ITSM 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: The program cannot find the file system in the dsmmigfstab file. The update failed. System Action: ITSM cannot complete the requested operation. User Response: The file system cannot be updated because it is not an FSM file system. You must first add space management to the file system before you can update space management settings for the file system. ANS9012E error-program: Command must be run by root user.
Explanation: Input is incorrect or is not in correct format. System Action: ITSM continues. User Response: Retry operation with correct usage syntax. ANS9021E error-program Unknown recall daemon (pid process-ID) terminated abnormally, status: status.
Explanation: ITSM requires that a root user perform this operation. System Action: ITSM terminates the operation. User Response: Change to root user, and then retry the operation. ANS9016E Cannot get space management migration status for path.
Explanation: A recall daemon is terminated abnormally. System Action: ITSM terminates the operation. User Response: Retry operation. If problem persists, contact your service representative. ANS9022E error-program Recall daemon (pid process-ID) terminated abnormally, status: status.
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. System Action: ITSM terminates the operation. User Response: The root user should check the permissions of the status file, or contact the service representative. 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.
Explanation: A recall daemon is terminated abnormally. System Action: ITSM terminates the operation. User Response: Retry operation. If problem persists, contact your service representative. ANS9023I error-program: Subsidiary recall daemon process exiting.
Explanation: The process is interrupted and exiting. The user has terminated the process. System Action: ITSM detected an interrupt. The recall daemon is terminated and exiting. User Response: None. ANS9024E Starting with this release all candidate processing is done internally by the ITSM monitor daemon. Thus -c is no longer a valid option for dsmreconcile.
Explanation: A minimum number of recall daemons has been entered that is greater than the maximum number of recall daemons. System Action: ITSM uses defaults instead of the values specified in the client system options file (dsm.sys). User Response: Correct the MINRECALLDAEMONS and MAXRECALLDAEMONS options in the client system options file and retry the operation. ANS9018W program-name: option option value value invalid, range min-value to max-value.
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: ITSM detected an invalid option. dsmreconcile is exiting. User Response: Dont use options -c and -Candidates with dsmreconcile anymore.
Explanation: An invalid value has been entered. Value should be in the range specified by the message.
716
IBM Tivoli Storage Manager: Messages
ANS9025W ANS9060W
ANS9025W program-name: cannot truncate inode inode-number on file system (file-system-ID, file-system-ID): error. system, migrate the file, and then retry the operation. ANS9036W program-name: migrated file(s) are missing on server for number stub file(s). Look in file-spec for file names.
Explanation: ITSM cannot truncate the file to its correct stub file size. The file remains one full block in size. System Action: ITSM continues. User Response: Retry the operation. If error persists, reboot the system. If error still persists, contact your service representative. ANS9028E program-name: cannot determine the file system name for fsid (file-system-ID, file-system-ID).
Explanation: ITSM cannot find the migrated file(s) on the server. System Action: ITSM continues. 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. ANS9054E error-program: cannot set specified execution mode: error.
Explanation: ITSM is unable to determine the name of the file system with the specified file-system-id. System Action: ITSM is unable to recall the requested file. User Response: Determine if the file system which 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. ANS9030W Cannot set conflicting attributes to file file-name.
Explanation: ITSM cannot set the execution mode successfully. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation. If the problem persists, contact your service representative. ANS9057W error-program: cannot get space information for file-system: error.
Explanation: ITSM cannot get the space information for the file system. System Action: ITSM continues. User Response: Verify that space management has been added to the file system. ANS9058E error-program: cannot close file-spec: error.
Explanation: ITSM cannot set the file attributes because the requested attributes are in conflict with one another. System Action: ITSM 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: ITSM cannot close the file. System Action: ITSM terminates the current operation. User Response: Retry the operation. If problem persists, contact your system administrator. ANS9059E error-program: process cannot detach to become a daemon.
Explanation: ITSM can only set file attributes to a migrated file. This file has not been migrated. System Action: ITSM does not set the file attributes. User Response: Migrate this file, and then retry the operation. ANS9032W File file-name is not in an FSM file system.
Explanation: ITSM process cannot detach itself to become a daemon. System Action: ITSM cannot start the daemon as requested. ITSM stops. User Response: Retry the operation. ANS9060W error-program: cannot get and increase limit of open files.
Explanation: ITSM detects that the file is not in an FSM file system, and therefore, it cannot perform the operation requested. System Action: ITSM does not set the file attributes. User Response: Add space management to the file
Explanation: ITSM either cannot get the limit of the number of open files, or cannot increase the limit of the number of open files.
Chapter 5. Client and Data Protection for Lotus Notes Messages
717
ANS9063E ANS9075W
System Action: ITSM 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. ANS9063E error-program: file system file-system is out of inodes. ANS9070I program-name: space management is now deactivated for all FSM file systems.
Explanation: ITSM has deactivated space management for all file systems listed in the dsmmigfstab file. System Action: ITSM continues. User Response: Continue with normal operation. ANS9071W program-name: error reactivating space management for all FSM file systems.
Explanation: ITSM cannot get space for the file system because the file system is out of inodes. System Action: ITSM 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: ITSM found an error in trying to reactivate space management. System Action: ITSM does not reactivate space management for FSM file systems. User Response: Make sure space management is installed correctly and retry the operation. ANS9072W error-program: error deactivating space management for all FSM file systems.
Explanation: ITSM cannot fork a new process that is needed. System Action: ITSM cannot complete the requested operation. User Response: Free some file space by ending some processes or removing some files, and retry the operation. ANS9067W error-program: error updating dsmmigfstab file for file-system.
Explanation: ITSM found an error in trying to deactivate space management. System Action: ITSM does not deactivate space management for FSM file systems. User Response: Make sure space management is installed correctly and retry the operation. ANS9073W program-name: error deactivating space management for file system file-system.
Explanation: ITSM found an error in updating the dsmmigfstab file for this file system. System Action: ITSM 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 program-name: dsmmigfstab file updated for file system file-system.
Explanation: ITSM found an error in trying to deactivate the file system. System Action: ITSM does not deactivate space management for the file system. User Response: Make sure space management is installed correctly and retry the operation. ANS9074I program-name: FSM file system file-system is now deactivated.
Explanation: ITSM successfully updated the dsmmigfstab file for the file system. System Action: ITSM continues. User Response: Continue with normal operation. ANS9069I program-name: all file systems are reactivated to previous states.
Explanation: ITSM has deactivated space management for the file system. System Action: ITSM continues. User Response: Continue with normal operation. ANS9075W program-name: error reactivating space management for file system file-system.
Explanation: ITSM has reactivated all file systems managed by HSM to their previous states before the global deactivation. System Action: ITSM continues. User Response: Continue with normal operation.
Explanation: ITSM found an error in trying to reactivate space management for the file system. System Action: ITSM does not reactivate space management for the file system. User Response: Correct the error if possible and retry
718
IBM Tivoli Storage Manager: Messages
ANS9076I ANS9086E
the operation. If the problem persists, contact your service representative. ANS9076I program-name: space management is now active for file system file-system. ANS9081W program-name: orphaned stub file(s) detected in file system file-system.
Explanation: ITSM has reactivated space management for the file system. System Action: ITSM continues. User Response: Continue with normal operation. ANS9077I program-name: removed space management from file system file-system.
Explanation: ITSM 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: ITSM 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: ITSM removed space management. The file system is now a native file system. System Action: ITSM continues. User Response: Continue with normal operation. ANS9078W Space management is not removed from file system file-system.
Explanation: ITSM encountered an error performing reconciliation on the file system. System Action: ITSM continues. User Response: Refer to other messages displayed or 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: ITSM was not able to remove space management from this file system. Possible causes: Kernel extension is downlevel. Program is downlevel. Insufficient disk space. System Action: ITSM is unable to complete the requested operation. User Response: Refer to the immediately preceding error message and retry the operation. ANS9079W program-name: no migrated files matching search criteria found.
Explanation: ITSM cannot deactivate space management on the file system. System Action: ITSM continues. User Response: Correct the error if possible and retry the operation. ANS9085E program-name: space management has not been added to file system file-system.
Explanation: ITSM did not find any migrated files matching the search criteria. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation with a different search criteria. ANS9080E program-name: not enough space to recall all migrated files.
Explanation: There is no entry for the file system in the dsmmigfstab file. System Action: ITSM will not perform space management functions on this file system. User Response: Add space management to the file system, if appropriate, and then retry the operation. ANS9086E program-name: error adding FSM to file system file-system.
Explanation: ITSM detects there is not enough space in the file system to hold all the migrated files if all are recalled. System Action: ITSM 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. Retry the operation.
Explanation: ITSM encountered an error and cannot add FSM to the file system. System Action: ITSM continues. User Response: Refer to the preceding error message and retry the operation.
Chapter 5. Client and Data Protection for Lotus Notes Messages
719
ANS9087I ANS9126E
ANS9087I Space management is successfully added to file system file-system. 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: ITSM 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. System Action: ITSM continues. User Response: Continue with normal operation. ANS9088W program-name: an entry for file system file-system is already in the dsmmigfstab file.
Explanation: ITSM 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. User Response: None. ANS9099E program-name: space management is not active for file system file-system.
Explanation: ITSM found that the file system is already listed in the dsmmigfstab file. System Action: ITSM continues. User Response: None. ANS9090E program-name: file-system is not a valid file system name.
Explanation: ITSM 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 Space management has not been added to file system file-system, or FSM is not mounted.
Explanation: ITSM received an invalid file system name. The file system is not mounted, or is not mounted correctly. System Action: ITSM continues. User Response: Correct the file system name, and retry the operation. ANS9093W program-name: cannot update migration candidates list file-name.
Explanation: ITSM found the file system was not in a migratable state. Either space management was not added to the file system, or the FSM is not mounted. System Action: Processing of the file system stopped. User Response: Either add space management to the file system, or mount the FSM if it is not mounted. Refer to the Users Guide for the correct syntax for mounting the FSM. ANS9101I No migrated files matching file-name were found.
Explanation: ITSM cannot update the migration candidates list because not enough memory is available to create a temporary file. System Action: Processing stops. 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.
Explanation: You entered a search pattern or file name that cannot be found in the server database as a migrated file. System Action: Processing stopped. User Response: Ensure that your search pattern is correct, or specify a new search string. ANS9126E program-name: cannot get the state of space management for file-system: error.
Explanation: ITSM found no files eligible for migration in the file system after running dsmreconcile. System Action: ITSM continues. User Response: Continue with normal operation. ANS9096E User is not the owner of file filesystem-namedirectory-namefile-name so file is skipped.
Explanation: ITSM cannot determine whether space management is activated, deactivated, or globally deactivated on the file system. System Action: ITSM stops the operation. User Response: Retry the operation.
Explanation: The user does not own this file and cannot perform this operation. System Action: ITSM skips the file.
720
IBM Tivoli Storage Manager: Messages
ANS9128I ANS9142W
ANS9128I program-name: exported space management file system file-system. ANS9135W program-name: invalid premigration percentage (value).
Explanation: ITSM has exported the indicated space managed file system. You must import this file system to gain access to the migrated files. System Action: ITSM continues. User Response: Continue with normal operation. ANS9130W program-name: High threshold (value) less than low threshold (value).
Explanation: An invalid value has been entered for premigration percentage. System Action: ITSM logs the condition and continues. User Response: Correct the invalid input value. ANS9136W program-name: invalid high threshold (value).
Explanation: ITSM 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: ITSM logs the condition and continues processing other parameters. User Response: Correct the invalid input value.
Explanation: An invalid value has been entered for high threshold. System Action: ITSM logs the condition and continues. User Response: Correct the invalid input value. ANS9137W program-name: invalid low threshold (value).
ANS9131W
program-name: invalid size factor (value).
Explanation: An invalid value has been entered for the size factor. System Action: ITSM logs the condition and continues processing other parameters. User Response: Correct the invalid input value. ANS9132W program-name: invalid stub file size (value).
Explanation: An invalid value has been entered for low threshold. System Action: ITSM logs the condition and continues. User Response: Correct the invalid input value. ANS9140W program-name: invalid size factor (value) for file-system, range value..value.
Explanation: An invalid value has been entered for the stub file size setting. System Action: ITSM logs the condition and continues processing other parameters. User Response: Correct the invalid input value. ANS9133W program-name: invalid quota factor (value).
Explanation: An invalid value has been entered for the size factor setting. Value should be in the range specified by the message. System Action: ITSM does not change value. User Response: Correct the invalid input value. ANS9141W program-name: invalid age factor (value) for file-system, range value..value.
Explanation: An invalid value has been entered for the quota setting for the file system. System Action: ITSM logs the condition and continues. User Response: Correct the invalid input value. ANS9134W program-name: invalid age factor (value).
Explanation: An invalid value has been entered for the age factor setting. Value should be in the range specified by the message. System Action: ITSM does not change the value. User Response: Correct the invalid input value. ANS9142W program-name: file-spec: high threshold (value) less than low threshold (value) for file-system.
Explanation: An invalid value has been entered for the age factor setting. System Action: ITSM logs the condition and continues. User Response: Correct the invalid input value.
Explanation: ITSM detects that high and low thresholds specified for the file system are invalid values. The high threshold must be greater than or equal to the low threshold. System Action: ITSM logs the condition and stops.
Chapter 5. Client and Data Protection for Lotus Notes Messages
721
ANS9144W ANS9154E
User Response: Enter valid values for the high and low thresholds. ANS9144W program-name: file-spec: invalid high threshold (value) for file-system, range 0..100. ANS9149E program-name: cannot create transition stub file: error.
Explanation: ITSM cannot create transition stub file. System Action: ITSM cannot complete the requested operation. Processing continues. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9150W Space management is not exported from file system file-system.
Explanation: ITSM detects an invalid high threshold value for the file system. System Action: ITSM 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: ITSM was not able to export the space managed file system. Possible causes: Kernel extension is downlevel. Program is downlevel. System Action: ITSM is unable to complete the requested operation. User Response: Refer to the immediately preceding error message and retry the operation. ANS9152E program-name: cannot deactivate space management for whole system: error.
Explanation: ITSM detects an invalid low threshold value for the file system. System Action: ITSM 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: Cannot deactivate space management for this whole system (whole machine). System Action: ITSM cannot deactivate space management support. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9153E program-name: cannot reactivate space management for whole system: error.
Explanation: ITSM detects too many or too few fields in an entry in the dsmmigfstab file. System Action: ITSM cannot complete the requested 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.
Explanation: Cannot reactivate space management for this whole system (whole machine). System Action: ITSM cannot reactivate space management support. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9154E program-name: cannot deactivate space management for file system file-system: error.
Explanation: ITSM cannot read this file. System Action: ITSM cannot fully complete the requested operation. User Response: Retry the operation. Try to determine why the read failed. If the problem continues, check with your system administrator. ANS9148E program-name: cannot find mount point for file system file-system.
Explanation: Cannot deactivate space management for this file system. System Action: ITSM unable to deactivate space management support for the file system. User Response: Retry the operation. If the problem continues, check with your system administrator.
Explanation: ITSM cannot find file system mount point. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system administrator.
722
IBM Tivoli Storage Manager: Messages
ANS9155E ANS9178E
ANS9155E program-name: cannot reactivate space management for file system file-system: error. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9165E program-name: cannot open directory directory-spec: error.
Explanation: Cannot reactivate space management for this file system. System Action: ITSM cannot reactivate space management support to the file system. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9157W program-name: cannot turn off ENOSPC checking in kernel: error.
Explanation: ITSM cannot open the directory. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9168E program-name: cannot open database file-spec: error.
Explanation: ITSM cannot turn off ENOSPC checking. System Action: ITSM cannot turn off ENOSPC checking. Processing continues. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9158W program-name: cannot turn on ENOSPC checking in kernel: error.
Explanation: ITSM cannot successfully open (lock/unlock) the database. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9169E program-name: cannot create directory directory-spec, reason.
Explanation: ITSM cannot turn on ENOSPC checking. System Action: ITSM cannot turn on ENOSPC checking. Processing continues. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9159E program-name: unable to create temporary file.
Explanation: ITSM cannot create this directory. System Action: ITSM 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: ITSM cannot create a temporary file. System Action: ITSM cannot complete its operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9160E program-name: cannot write to temporary file file-spec: error.
Explanation: ITSM did not find that this file system is properly mounted. System Action: ITSM ignores the file system. User Response: Verify that this file system is local and mounted and activated properly. ANS9171E Internal string is too long: error.
Explanation: ITSM cannot complete writing to the temporary file. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation. Determine why the write failed. If the problem continues, check with your system administrator. ANS9162E program-name: file-spec invalid: not found in path/path.
Explanation: ITSM internally has a long string that is beyond its capability. System Action: ITSM cannot complete the requested operation and stops processing. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9178E program-name: cannot open file file-spec: error.
Explanation: ITSM cannot find an entry for the file system in the dsmmigfstab file. System Action: ITSM cannot complete the requested operation.
Explanation: ITSM cannot open the file. System Action: ITSM cannot complete the requested operation.
Chapter 5. Client and Data Protection for Lotus Notes Messages
723
ANS9183E ANS9196W
User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9183E program-name: file system file-system is not in the dsmmigfstab file. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9192I Cannot disable file-system.
Explanation: ITSM cannot disable the file system. System Action: ITSM ignores the request. User Response: ITSM space management is not installed correctly. Read the space management documentation for installation instructions, or check with your system administrator. ANS9193I Cannot open file-system.
Explanation: ITSM cannot find the file system in the dsmmigfstab file. System Action: ITSM cannot complete the requested operation. User Response: Ensure that the file system is both valid and local. Retry the operation. If the problem continues, check with your system administrator. ANS9184E program-name: cannot allocate memory, error: error.
Explanation: ITSM cannot open the file system. System Action: ITSM ignores the request. User Response: Verify whether this file system exists and whether space management has been added to it. ANS9194W A selective migration is in progress. Wait until it completes and retry the recall.
Explanation: ITSM cannot allocate adequate storage for the user. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9186E program-name: cannot open mounted file system file-system: error.
Explanation: You tried a recall operation while a selective migration is in progress. System Action: ITSM ignores the request. 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: ITSM cannot open mounted file system. System Action: ITSM ignores the file system. User Response: Verify that this file system is mounted and activated properly. ANS9188E Not enough memory for recall operation
Explanation: ITSM cannot allocate storage for the requested recall operation. System Action: ITSM cannot complete the requested operation. User Response: Retry the recall operation. If the problem continues, check with your system administrator. ANS9189I Recall stopped by user
Explanation: You initiated a migration operation while a selective recall is in progress. System Action: ITSM ignores the request. User Response: Wait until the selective recall is complete and retry the migration operation. ANS9196W The PASSWORDACCESS option in your dsm.sys file is not set to GENERATE. Reset it to GENERATE and restart the HSM client.
Explanation: You requested that ITSM stop the recall operation. System Action: Recall stopped. User Response: Continue with normal operations. ANS9191E Error checking file system state
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: ITSM terminates the client. User Response: The root user must set the PASSWORDACCESS option to GENERATE in the dsm.sys file.
Explanation: The system cannot open /dev/dsm or cannot open the file system. System Action: Transaction stopped.
724
IBM Tivoli Storage Manager: Messages
ANS9197E ANS9251E
ANS9197E File: file-name has already been recalled. System Action: ITSM left FSM mounted on the file system. User Response: Determine why unmounting the FSM failed. If the reason is Device Busy, try unmounting the FSM by issuing the umount command for the file system. If umount again fails, check to see if the current directory is in the file system, or if another process is referencing the file system, such as an NFS mount or an open file. After the file system is clear of references, issue the umount command for the file system. No problems will result in continuing to run with the FSM mounted and a machine reboot will eliminate the FSM. ANS9240W Couldnt acquire serial number of disk disk-name at LUN LUN-id.
Explanation: You tried to recall the a file that has already been recalled. System Action: ITSM does not highlight the file. User Response: None. ANS9198E File: file-name is a resident file.
Explanation: You tried to recall a file that is resident. System Action: ITSM will not highlight the file. User Response: None. ANS9199S Cannot open /dev/fsm
Explanation: ITSM cannot open the space management device file, /dev/fsm. System Action: ITSM cannot complete the operation. User Response: Check to see whether ITSM is installed correctly and that the /dev/fsm file exists. Correct the problem and retry the operation. ANS9201W LAN-free path failed.
Explanation: ITSM 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. System Action: Server-free data movement will not be possible for data residing on the specified disk. User Response: None. ANS9249E File file-namefile-namefile-name accessed during migration. File skipped.
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 specified file-name was not migrated because the file was accessed by another process during the attempt to migrate it. System Action: ITSM 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: The TSM client has detected that HSM is installed on the system. LanFree is not a valid option when HSM is installed. This error occurs on AIX when this file is found: /usr/tivoli/tsm/client/hsm/bin/dsmrecalld or on Solaris when this file is found: /opt/tivoli/tsm/client/hsm/bin/dsmrecalld System Action: An invalid option is detected and processing stops. User Response: Remove the ENABLELANFREE option from the system option file. ENABLELANFREE can only be used when HSM is not installed. ANS9230E Cannot unmount FSM from file system file-system. Message from umount command:
Explanation: ITSM has finished reconciling the file system. System Action: ITSM continues. User Response: Continue with normal operations. ANS9251E ProgramName: Cannot parse command-line options correctly.
Explanation: Space management control files have been updated or deleted, or both, for the file system. However, FSM cannot be unmounted because the file system is being referenced by another process.
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, and then
Chapter 5. Client and Data Protection for Lotus Notes Messages
725
ANS9254E ANS9282E
retry the request. If this problem continues, contact your service representative. ANS9254E Error encountered while adding implicit excludes to the include-exclude list. The attempt to reserve the transition stub file will be made again during reconciliation. System Action: ITSM cannot reserve space for the transition stub files. Processing continues. User Response: If possible, make more space or inodes available and run reconciliation. ANS9267E program-name: File system file-system has exceeded its quota.
Explanation: Error encountered when implicitly excluded files are being added to the include-exclude list. System Action: ITSM cannot proceed. User Response: Retry the operation. If the problem persists, contact your service representative. ANS9255E program-name: invalid value found in the dsmmigfstab file for file system file-spec.
Explanation: ITSM detects that the file system has exceeded its quota. No more data can be migrated out of this file system. System Action: ITSM 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. ANS9280E program-name: cannot get space management kernel extension ID. Error : error.
Explanation: ITSM detects invalid values in the dsmmigfstab file. The entry that contains the invalid values is for file system file-spec System Action: ITSM cannot perform migration until 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.
Explanation: The program cannot determine the level of space management client kernel extension. System Action: ITSM stops the operation. User Response: Ensure that space management is installed correctly, and then retry the operation. If the problem continues, check with your system administrator. ANS9281E Space management kernel extension is downlevel from the user program.
Explanation: The specified file-name was not migrated because the file was open by one or more other processes. System Action: ITSM left the file resident. User Response: If you want the file migrated, stop the processes which currently have the file open and retry the migration. ANS9257E Server server-name does not support space management.
Explanation: The space management kernel extension on the system is downlevel from the user program that is currently running. Unexpected results may occur. System Action: ITSM stops processing the kernel extension. User Response: Upgrade the space management kernel extension to the correct level, and then retry the operation. ANS9282E User program is downlevel from the space management kernel extension.
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: ITSM 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 program-name: cannot reserve transition stub file for file system file-system: reason.
Explanation: The user program that is currently running is downlevel from the space management kernel extension on the system. Unexpected results may occur. System Action: ITSM stops processing the extension. User Response: Upgrade the user program to the correct level, and then retry the operation.
Explanation: ITSM cannot reserve transition stub file. ITSM tries to reserve some space for the transition stub file for emergency cases. At this point, there is either not enough space or inodes to allow the reservation.
726
IBM Tivoli Storage Manager: Messages
ANS9283K ANS9292E
ANS9283K Tivoli Space Manager is recalling a migrated file. ANS9289I Object dir-name is a directory. It is skipped for migration.
Explanation: The space management kernel extension is attempting to access a file that is not stored locally. If the file is migrated, ITSM is attempting to access it from an ITSM space management server. System Action: ITSM waits for the kernel to access the file. User Response: None.
Explanation: The object is a directory. It is not migrated. Space management does not migrate directories. System Action: ITSM does not migrate this object because it is a directory. User Response: None. ANS9290I File file-name of type file-type is skipped for migration.
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: ITSM waits until the file migration is completed. User Response: None.
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: ITSM does not migrate this file. User Response: None. ANS9291E 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.
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 ITSM migration server. The file cannot be recalled to the local machine. The server could be temporarily disabled. System Action: ITSM terminates the current operation. User Response: Check to see whether the server has been disabled by the system administrator, then retry the operation. ANS9286K File migration has been discontinued.
Explanation: ITSM 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: ITSM 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: Migration stops because the file is being migrated by another process. System Action: ITSM terminates the current operation. User Response: None. ANS9288I File file-name of size file-size is too small to qualify for migration.
Explanation: ITSM 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. System Action: ITSM will not run the program at this time. User Response: Check the permissions on the directories leading up to the lock file and also the permissions on the program executable.
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: ITSM does not migrate this file because it will not free additional space. User Response: None.
Chapter 5. Client and Data Protection for Lotus Notes Messages
727
ANS9293E ANS9302E
ANS9293E ITSM space management cannot access ERRORPROG error-program:error file that does not require a current backup copy. Retry the operation. ANS9299I Cannot get the number of migrated files for file system file-system.
Explanation: ITSM 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: ITSM 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.
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. System Action: If you are removing space management from the file system, processing stops. Space management is not removed. User Response: Run reconciliation to reconcile the file system. Retry operation. ANS9300I Migrated files found in file system file-system. Check for any error encountered during recall.
Explanation: You entered a search pattern or file name that cannot be found in the local file system. System Action: Processing stopped. User Response: Ensure that your search pattern is correct, or specify a new search string. ANS9297I File file-name is skipped for migration: No backup copy found.
Explanation: Remove space management failed because there are migrated files in the file system. ITSM was unable to recall any files, or some of the migrated files may have failed during a recall operation. System Action: ITSM 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: 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: ITSM checks only the migration server for a backup copy. If the migration server and backup server are different servers, ITSM does not find a backup copy of the file. System Action: ITSM does not migrate this 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.
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: ITSM does not remove the entry from the dsmmigfstab file. User Response: Manually edit the dsmmigfstab file and delete the entry. ANS9302E Mount FSM: ERROR - file-system is not in the dsmmigfstab file. Check the /etc/adsm/SpaceMan/config/dsmmigfstab file, or add space management to the file system.
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, the backup copy found on the migration server is an old version. This file will not be migrated. Note: ITSM 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. System Action: ITSM does not migrate this file. User Response: Back up the current file on the migration server, or assign a management class to this
Explanation: ITSM cannot mount the file system because it is not listed in the dsmmigfstab file. System Action: ITSM does not mount the FSM to the file system. User Response: If you previously added space
728
IBM Tivoli Storage Manager: Messages
ANS9303E ANS9311E
management to the file system, check the /etc/adsm/SpaceMan/config/dsmmigfstab file to see whether the entry has been removed or commented out. If you want to add space management to the file system, use 'dsmmigfs add'. ANS9303E Mount FSM: ERROR - file system type FSM was not found. ITSM space management is not installed correctly. Please read the space management documentation for installation instructions. ANS9307W Mount FSM: ITSM space management is already mounted on mount-path
Explanation: ITSM cannot mount the file system because the file system is already mounted. System Action: ITSM does not mount the FSM to the file system. User Response: None. ANS9308E Mount FSM: ERROR - mount-path is not a supported native file system
Explanation: ITSM cannot mount the file system because the file 'FSM' entry is missing from /etc/vfs. System Action: ITSM does not mount the FSM to the file system. User Response: AIX only. ITSM space management is not installed correctly. Read the space management documentation for installation instructions. ANS9304E Mount FSM: ERROR - invalid source (object) path source-path: error
Explanation: ITSM cannot mount the file system because it is not a supported native file system. System Action: ITSM does not mount the FSM to the file system. User Response: The file system must be one of the supported native file systems in order for the ITSM space management to mount it. ANS9309I Mount FSM: ITSM space management mounted on mount-path
Explanation: ITSM cannot mount the file system due to an invalid path. System Action: ITSM does not mount the FSM to the file system. User Response: Correct the problem and retry the mount. ANS9305E Mount FSM: ERROR - invalid mount (stub) path mount-path: error
Explanation: ITSM successfully mounted the FSM to the file system. System Action: ITSM space management now manages the file system. User Response: None. ANS9310E Mount FSM: ERROR - cannot FSM mount source-path on mount-path: error
Explanation: ITSM cannot mount the file system due to an invalid path. System Action: ITSM does not mount the FSM to the file system. User Response: Correct the problem and retry the mount. Make sure the directory exists. ANS9306E Mount FSM: ERROR - mount-path must be a directory
Explanation: ITSM cannot mount the file system due to the specified error. System Action: ITSM does not mount the FSM to the file system. User Response: Correct the problem and retry the mount. ANS9311E Mount FSM: ERROR - cannot unlock file system, internal error: error
Explanation: ITSM cannot mount the file system because the mount path is not a directory. System Action: ITSM does not mount the FSM to the file system. User Response: Correct the problem and retry the mount. Make sure the mount path is a directory.
Explanation: ITSM cannot unlock the internal file system lock. System Action: ITSM does not allow non-root user access to the file system. User Response: Attempt to unmount the file system, and try the mount again. If the problem continues, contact your service representative.
Chapter 5. Client and Data Protection for Lotus Notes Messages
729
ANS9312S ANS9404W
ANS9312S program-name: Cannot change owner/group on file: file-name: error ANS9400W program-name: Recovered program-name. The daemon was either not started or in corrupted state.
Explanation: ITSM cannot change the ownership or group, or both for the specified file. This change is necessary for space management to run properly. System Action: ITSM cannot continue processing. User Response: Ensure that directory permissions allow the file owner or group to be changed. Reissue the command. ANS9318W program-name: error encountered while undeleting file system file-system.
Explanation: ITSM HSM daemon breakdown with automatic recovery by the dsmwatchd. System Action: Restarting the daemon. User Response: Continue with normal operation. ANS9401E program-name: Cannot kill recall daemon.
Explanation: ITSM A request for killing the recall daemon failed. This may happen 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: ITSM encountered an error performing undelete on the file system. System Action: ITSM continues. User Response: Continue with normal operation. ANS9349I Selective Recall completed
Explanation: The selective recall was completed. System Action: ITSM recalled the files. User Response: Continue with normal operations. ANS9353I Selective Recall stopped by user.
Explanation: ITSM In order to takeover the functionality of a malfunctional partner node the dsmwatchd must notify the local daemons. System Action: none. User Response: Contact service representative. ANS9403E program-name: The local HSM functionality cannot be recovered. Trying to initiate failover to another node.
Explanation: You requested to stop the selective recall operation. System Action: Selective recall stopped. User Response: Continue with normal operations. ANS9354E Not enough memory for selective recall operation.
Explanation: ITSM 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 with frame ID . Trying to takeover remote filesystems.
Explanation: ITSM cannot allocate memory for the requested recall operation. System Action: ITSM cannot complete the requested recall operation. User Response: Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned can also help, or see your system administrator. ANS9357E The dsmscout executable cannot be used on the user level.
Explanation: ITSM The local dsmwatchd received a notification about a failing HSM node. It will try to takeover its managed filesystems. System Action: HSM will try to takeover the managed filesystems from a failure node. User Response: Check failure node.
Explanation: The dsmscout process is exclusively started by the dsmmonitord. System Action: ITSM aborts the operation. User Response: None.
730
IBM Tivoli Storage Manager: Messages
ANS9405W ANS9423E
ANS9405W program-name: The takeover of filesystem path succeeded. ANS9418W program-name: File file-name is locked at the moment. Will try to acquire the SDR lock in a few seconds again.
Explanation: ITSM During a failover scenario the local node will try to takeover the managed filesystems of a failure node. System Action: HSM will try to takeover the managed filesystems from a failure node. User Response: Check failure node. ANS9412E program-name: Failover is disabled on the local machine. Aborting failover ...
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. System Action: ITSM None. User Response: Wait. If the situation does not get resolved within a reasonable amount of time (about 1 min.), execute dsmmigfs SDRreset. This will reset all 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 contol of a remote HSM instance.
Explanation: ITSM Failover operations were disabled either by the system or the user. System Action: None. User Response: Check failover policy if necessary. ANS9413W program-name: The remote node was able to recover from failure situation. Aborting takeover ...
Explanation: A GPFS filesystem can be managed just once. System Action: Aborting operation. User Response: Execute dsmmigfs query -detail to have a look at the current HSM configuration within the local GFPS node set. ANS9420E 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: The remote dsmwatchd was able to recover from the failure situation during the local takeover operation. System Action: None. User Response: Check failure node for consistency. ANS9414E program-name: Unable to create file-name in the SDR. Aborting ...
Explanation: An update of an SDR object failed. System Action: Aborting operation. User Response: Check SDR consistency. ANS9415W program-name: The HSM service provider on Node ID: node with Frame ID: frame left the failover group voluntarily.
Explanation: You cannot update configuration files in the SDR when failover is disabled on the local machine. System Action: ITSM Aborting operation. User Response: Do nothing, or activate failover by using dsmmigfs enableFailover before running dsmmigfs SDRupdate. ANS9421W program-name: Recovered from Lock on SDR File file-name
Explanation: Failover was disabled on a remote HSM node. System Action: None. User Response: None. ANS9416W program-name: The HSM service provider on Node ID: node with Frame ID: frame joined the failover group.
Explanation: This output relates to ANS9418W. A previously blocked SDR file got unlocked. System Action: ITSM continues. User Response: None. ANS9423E program-name: Setting the default partiton name failed! Aborting operation ...
Explanation: ITSM Failover was activated on a remote HSM node. System Action: None. User Response: None.
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. System Action: Aborting operation.
Chapter 5. Client and Data Protection for Lotus Notes Messages
731
ANS9424E ANS9451E
User Response: Check node consistency. ANS9424E program-name: Severe problem! It was not possible to send a message to the SP Group Services. 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: The Failover environment requires proper access to the SP Group Services. The distribution of a message failed. System Action: Aborting operation. User Response: Check node consistency. 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: There can only be one instance of dsmmigfs add/rem/update running within a GPFS nodeset at the same time. System Action: Aborting operation. 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: Some HSM commands need to inform the dsmwatchd about the current operation. This notification failed. System Action: Aborting operation. 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 filesystem failed.
Explanation: The operation relies on an active failover environment. System Action: Aborting operation. User Response: Run dsmmigfs enableFailover on the local node and repeat the operation. ANS9449W program-name: Forced deactivation of the local failover environment!
Explanation: A remote node requested the takeover of a filesystem but the local activation failed. System Action: Aborting operation. User Response: Check whether the filesystem gets managed by another node. If not, recover the initial node and restart the HSM service. ANS9432E Severe problem! 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.
Explanation: ITSM Failover was initiated or a problem with the group services occured. 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: Unable to start required thread. System Action: Aborting operation. User Response: Check node consistency. ANS9433E program-name: dm_send_msg failed with errno Errno.
Explanation: None of the locally mounted GPFS filesystems matches with the remotely managed filesystems of the failure node. System Action: Aborting takeover operation. User Response: Check that the filesystems of the remote failure node get managed elsewhere within the node set. ANS9451E program-name: GPFS or the SP switch is down locally. Aborting takeover activies ...
Explanation: Unable to execute DMApi call. System Action: Aborting operation. User Response: Check consistency of the GPFS daemon.
Explanation: ITSM GPFS is not functional locally. System Action: Aborting takeover operation.
732
IBM Tivoli Storage Manager: Messages
ANS9452E ANS9501W
User Response: Check switch and VSD status. The local system must be unfenced. ANS9452E program-name: The DMApi is not functional locally. Aborting takeover activies ... 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 operation stopped because the DMApi interface is not accessible. System Action: Aborting takeover operation. User Response: Check GPFS status. ANS9454W program-name: Performing synchronization between the local and global file event handling.
Explanation: ITSM user executed dsmmigfs with failover flag on an unsupported platform. System Action: ITSM Abort operation. User Response: None. ANS9469E Warning! Unable to write a complete migration candidate list due to low space in the parent filesystem of name.
Explanation: The local node received a request from a remote node to synchronize with the global file event handling (DMApi event disposition). System Action: Synchronizisation proceeds. User Response: None. ANS9455E program-name: Unable to join the local failover group with rc=return-code!
Explanation: ITSM Low space in filesystem which stores the migration candidates files. System Action: ITSM The executable writes a partial migration candidates list. User Response: Increase the filesystem size or create a dedicated filesystem with sufficient size under the given path. ANS9500W program-name: cannot disposition the mount event. Reason: error
Explanation: SP Group services reported a problem accessing/creating an HSM group. System Action: Aborting operation. User Response: Check PSSP environment on the local node. ANS9458W program-name: Joined successfully to the local failover group!
Explanation: The system wide mount event could not be dispositioned. Mount events will not be received by this daemon. System Action: ITSM continues. 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 ITSM space management supported file system has been added using dsmmigfs or after a file system has been mounted using the mount command. ANS9501W program-name: cannot set event disposition on session session for file system mountdir token = token. Reason : error
Explanation: Joining the Group Services HSM failover group succeeded. System Action: Processing continues. User Response: None. ANS9459E 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: 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. System Action: ITSM continues. User Response: The file system must be one of the supported native file systems in order for the ITSM space management to support it. Verify that the mount options the file system are correct. Correct the problem and remount the file system.
Explanation: ITSM 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: ITSM Abort operation.
Chapter 5. Client and Data Protection for Lotus Notes Messages
733
ANS9502W ANS9512E
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. System Action: ITSM continues. User Response: Correct the problem and retry the operation. ANS9503I program-name: events have been set and dispositioned on session session for file system filesystem-name
Explanation: ITSM space management cannot release the right on a file. System Action: Processing of the file is interrupted. User Response: Continue with normal operation. ANS9509W program-name: received an unexpected event of type event-type on session session.
Explanation: Setting events and dispositioning these on a DM session enables the file system for ITSM space management support. System Action: ITSM continues. User Response: Continue with normal operation. ANS9504W program-name: The file system filesystem-name is not mounted or is mounted with wrong options.
Explanation: ITSM space management daemon received an unexpected event. This event has not been dispositioned. System Action: ITSM ignores event and continues. User Response: Continue with normal operation. ANS9510E program-name: cannot get event messages from session session, expected max message-length = msglen, returned message-length = return-length. Reason : error
Explanation: Either the file system is not mounted or it has been mounted with incorrect options. System Action: ITSM continues. User Response: Mount the file system or remount it with corrected mount options. ANS9505E program-name: cannot initialize DM services. Reason: error
Explanation: ITSM space management encountered an error while trying to receive a message on a DM session. System Action: ITSM continues. User Response: Continue with normal operation. ANS9511E program-name: cannot read DM attributes on session session for file handle = handle token = token. Reason : error
Explanation: ITSM space management cannot initialize the DM services. System Action: ITSM cannot start space management support. User Response: Correct error and retry operation. Make sure that DM services have been installed on the system (Hierarchical Storage Management Support). ANS9507E program-name: cannot request the right on session session for file handle filehandle token = token. Reason : error
Explanation: ITSM space management cannot read the DM attributes of a DM object, usually a file. System Action: Processing of the file is interrupted. User Response: Continue with normal operation. ANS9512E program-name: cannot set DM attributes on session session for file handle = filehandle token = token. Reason : error
Explanation: ITSM space management cannot set DM attributes for a DM object, usually a file. System Action: Processing of the file is interrupted. User Response: Continue with normal operation.
Explanation: ITSM space management cannot request the required right on a file. System Action: Processing of the file is interrupted. User Response: Continue with normal operation.
734
IBM Tivoli Storage Manager: Messages
ANS9513E ANS9524W
ANS9513E program-name: cannot remove DM attributes on session session for file handle = filehandle token = token. Reason : error System Action: ITSM space management continues. User Response: If a user process is unexpectely 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: ITSM space management cannot remove DM attributes for a DM object, usually a file. System Action: Processing of the file is interrupted. User Response: Continue with normal operation. ANS9514E program-name: cannot create a file handle from path. 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. System Action: ITSM space management continues. User Response: Resolve the problem and retry the operation. ANS9520E program-name: cannot set a managed region on session session for file handle = filehandle token = token. Reason : error
Explanation: ITSM space management cannot create a file handle from the given file. System Action: Processing of the file is interrupted. User Response: Continue with normal operation. ANS9515E program-name: cannot set the migration information. Reason: error
Explanation: ITSM 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. System Action: Processing of the file is interrupted. User Response: Continue with normal operation. ANS9516E program-name: cannot create an user event message on session session. Reason: error
Explanation: A managed region could not be set on a file. No events will be generated for this file. System Action: Processing of the file is interrupted. User Response: If this error recurs, see your system administrator. ANS9521E program-name: cannot get the file attributes on session session for file handle = handle token = token. Reason : error
Explanation: ITSM space management cannot create an user event message, needed to reference rights on a file to be processed. System Action: Processing of the file is interrupted. User Response: Continue with normal operation.
Explanation: ITSM space management cannot read the attributes of a file. System Action: Processing of the file is interrupted. User Response: If this error recurs, see your system administrator. ANS9523E program-name: is unable to verify the stubsize for the file on session session file handle = filehandle token = token. Reason : error
ANS9517E
program-name: cannot clear all event messages from session session. Reason: error
Explanation: ITSM space management is in the process of destroying a DM session. There are still unexpected - event messages on this session that could not be responded to. System Action: ITSM DM session is not destroyed. User Response: See your system administrator.
Explanation: A correct stubsize could not be determined by the system. System Action: ITSM stopped migration of the file. User Response: Resolve the problem and retry the operation. 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
ANS9518E
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).
Explanation: The predefined stubsize for the file was not valid. The system corrected the stubsize.
Chapter 5. Client and Data Protection for Lotus Notes Messages
735
ANS9525E ANS9534W
System Action: ITSM space management continues. User Response: Continue with normal operation. ANS9525E program-name: is unable to create a stubfile on session session for file handle = handle token = token. Reason : error ANS9530W program-name: cannot remove an entry for file-system from the global state file.
Explanation: An error occurred while creating a stub file. System Action: Processing of the file is interrupted. User Response: Continue with normal operation. ANS9526E program-name: cannot open the state file filename for writing. Reason: error
Explanation: The entry for the file system in the dmiFSGlobalState 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: ITSM does not remove the entry from the global state file. User Response: Resolve the problem and retry the operation. ANS9531E program-name: cannot create a DM session: old session = oldsession session info = session-info. Reason : error
Explanation: The state file (global or file system state file) could not be opened. System Action: ITSM stops processing. User Response: Resolve the problem and retry the operation. ANS9527E program-name: cannot write to the state file filename. Reason: error
Explanation: ITSM space management could not create a DM session. System Action: ITSM stops processing. User Response: See your system administrator. ANS9532W program-name: cannot destroy the session session. Reason: error
Explanation: ITSM space management could not write to the state file. System Action: ITSM stops processing. User Response: Resolve the problem and retry the operation. ANS9528W program-name: cannot read from the state file filename. Reason: error
Explanation: ITSM space management could not destroy a DM session. System Action: ITSM continues. User Response: See your system administrator. ANS9533W program-name: failed getting all sessions. Reason: error
Explanation: ITSM space management could not read from the state file. System Action: ITSM stops processing. User Response: Resolve the problem and retry the operation. ANS9529W program-name: cannot obtain handle of file system state file
Explanation: ITSM space management could not get all DM sessions on the system. System Action: ITSM stops processing. User Response: See your system administrator. ANS9534W program-name: cannot query a session. Reason: error
Explanation: ITSM space management could not find the handle of a file system state file, that is stored in the global state file. This can be true 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: ITSM continues or stops processing, depending on the situation. User Response: If processing has stopped, resolve the problem and retry the operation.
Explanation: ITSM space management could not query a DM session on the system. System Action: ITSM continues. User Response: Continue with normal operation.
736
IBM Tivoli Storage Manager: Messages
ANS9535E ANS9552E
ANS9535E program-name: a file handle could not be created from the file descriptor file-descriptor. Reason: error ANS9544W program-name: cannot obtain allocation info on session sessionL file handle = filehandle token = tokenL offset=offsetL number of extents = nextents (returned = nreturned) Reason: error
Explanation: ITSM space management could not create a file handle. System Action: Processing of the file is interrupted. User Response: If this error recurs, see your system administrator. ANS9538W program-name: request request for DM file attributes not recognized
Explanation: ITSM space management could not get allocation information of a file. System Action: Processing of the file is interrupted. User Response: If this error recurs, see your system administrator. ANS9545E program-name: cannot get lock for lockdirlockfile to continue processing.
Explanation: An unknown request type has been encountered that cannot be handled. System Action: ITSM continues. User Response: Continue with normal operation. ANS9539E program-name: cannot create a file system handle from the file handle = filehandle. Reason : error
Explanation: ITSM space management could not obtain a lock for a file. System Action: Processing stopped. User Response: Resolve the problem and retry the operation. ANS9548W Cannot complete remote file access.
Explanation: A file system handle could not be created from a file handle. System Action: ITSM continues. User Response: Continue with normal operation. ANS9542E program-name: the file attributes could not be set on session session for file handle = filehandle token = token flag = flag Reason : error
Explanation: ITSM space management cannot complete the remote file access. The file may be migrated to an ITSM migration server. The file cannot be recalled to the local machine. The server could be temporarily disabled. System Action: ITSM terminates the current operation. 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.
Explanation: ITSM space management could not update file attributes. System Action: Processing of the file is interrupted. User Response: If this error recurs, see your system administrator. ANS9543W program-name: cannot reserve blocks for nospace condition on file system filesystem-name. Reason: error
Explanation: Recall stops because the file being recalled would cause the file system to run out of space. System Action: ITSM terminates the current operation. 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 fsm to file-system; path includes non-local file system.
Explanation: ITSM space management could not reserve blocks on the file system to be used in a nospace condition. System Action: ITSM continues. User Response: Resolve the problem, then restart the monitor daemon.
Explanation: An attempt was made to add space management to a file system whose path contains non-local elements. System Action: Processing stopped.
Chapter 5. Client and Data Protection for Lotus Notes Messages
737
ANS9553I ANS9739E
User Response: File system must be entirely local. ANS9553I Wrote temporary candidates list to file-name. reason these files are not selected, for example, inclexcl list. ANS9735E Error doing realtime initialization
Explanation: Due to out of space condition, the candidates list was written to the named temporary file. System Action: Temporary file created. User Response: Temporary file can be copied to the appropriate .SpaceMan directory when space is made available. ANS9613E program-name: Stubsize of stubsize bytes is not supported on filesystem.
Explanation: ITSM ran out of resource (either processes or shared storage) that prevents it from starting a migrate or recall operation. Your file selections remain intact. System Action: ITSM cannot start the migrate or recall operation. User Response: Retry the operation. If unsuccessful, see your system administrator. ANS9736E Not enough memory for authorization list table
Explanation: The given stubsize value not a multiple of the file system blocksize and cannot be supported. System Action: The program aborts the operation. User Response: Use a correct stub size. ANS9641S Invalid option option found in options file file-name at line number : number Invalid entry : entry
Explanation: ITSM cannot allocate enough storage for the authorization list. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation. If unsuccessful, see your system administrator. ANS9737E Authentication failed -- Exit ITSM to retry
Explanation: The specified option in the ITSM options file (file-name) is in error. System Action: Processing stopped. User Response: Correct the options file entry. ANS9732E No Backup Copy Group for Management Class: management-class
Explanation: You typed an incorrect password four times in a row. System Action: ITSM cannot connect to the server without a correct password. User Response: Exit and restart ITSM if authorized; otherwise, see your system administrator. ANS9738S Out of memory
Explanation: The management class for this file does not have a backup copy group specified. System Action: Processing stopped. User Response: See your system administrator. ANS9733E File: File-name excluded by the Include/Exclude list
Explanation: ITSM found an error allocating storage at initialization. System Action: ITSM cannot continue. User Response: See your system administrator. ANS9739E Cannot get shared memory
Explanation: You tried to back up the named file-name that was specified to be excluded from backup. System Action: ITSM did not back up the file. 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: The system ran out of shared storage resources. System Action: ITSM 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.
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
738
IBM Tivoli Storage Manager: Messages
ANS9740S ANS9790I
ANS9740S This program is not installed correctly. Please 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. ANS9778E Errors were detected in options file: Do you want ITSM to comment out all lines with errors?
Explanation: Invalid options or option values were encountered while reading the options file. System Action: This message is displayed. Further action depends on your response. User Response: Click Yes to allow ITSM to turn the invalid lines into comments. If you click No, you will exit immediately. ANS9779E Unable to open options file for writing.
Explanation: ITSM cannot find its resource file (Sm) in the default directory (directory-name). A problem may have occurred during installation. System Action: ITSM cannot start. User Response: See your system administrator. ANS9741E Not enough memory to hold directory structure
Explanation: An error occured while ITSM 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: ITSM cannot allocate storage for the requested directory structure. This error can happen under migrate or recall operations. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation. If unsuccessful, see your system administrator. ANS9742E Error reading directory structure
Explanation: ITSM was unable to update your options file, possibly because of disk full condition. System Action: Program exits. User Response: Check if you have enough disk space or correct invalid entries in your options file manually. ANS9781E After completing repair ITSM found an invalid option, keyword or parameter in your options file.
Explanation: ITSM 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. System Action: ITSM cannot complete the requested operation. User Response: Retry the operation. If unsuccessful, see your system administrator. ANS9743W No files selected in directory tree
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. System Action: Program exits. User Response: Make sure no other application modified your options file and restart ITSM. You may also use a text editor to correct invalid entries in your options file. ANS9790I File is skipped for migration: No backup copy found.
Explanation: You did not select any files to list for migrate or recall. System Action: ITSM cannot complete the requested 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: ITSM cannot recall the file. User Response: Recall this file on a system that supports the file size. See your system administrator.
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: ITSM checks only the migration server for a backup copy. If the migration server and backup server are different servers, ITSM does not find a backup copy of the file.
Chapter 5. Client and Data Protection for Lotus Notes Messages
739
ANS9791I ANS9803W
System Action: ITSM does not migrate this 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. dsmreconcile dsmautomig dsmmigfs remove. Also dsmmigfs remove cannot run while a migration process is running in the file system. System Action: ITSM 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: 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, the backup copy found on the migration server is an old version. This file will not be migrated. Note: ITSM 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. System Action: ITSM does not migrate this file. 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. ANS9792W A tree view of a file system is being built. Please wait until it completes, and then retry the operation.
Explanation: ITSM cannot open a temporary file to process the mount command for this file system. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator. ANS9800W Cannot create temp file for mount command.
Explanation: ITSM cannot create a temporary file to process the mount command for this file system. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator. ANS9801W Cannot create transaction file.
Explanation: You tried to choose Selective Migration or Selective Recall when a tree view of a file system is being built. System Action: ITSM ignores the request. User Response: Wait until the tree view build completes, and then retry the operation. ANS9796E Cannot access lock file for file-system file system.
Explanation: Cannot create transaction file for this file system. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator. ANS9802W Cannot create status file.
Explanation: ITSM 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. System Action: ITSM will not run the program at this time. 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: Cannot create status file for this file system. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator. ANS9803W Cannot create premigration database.
Explanation: Cannot create a premigration database for this file system. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator.
Explanation: ITSM 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:
740
IBM Tivoli Storage Manager: Messages
ANS9804W ANS9817W
ANS9804W Cannot create migration candidates list. System Action: The transaction will show incorrect results. User Response: Refresh the file systems to reflect local file systems. ANS9813W Incorrect data shown. Run reconcile.
Explanation: Cannot create a migration candidates list for this file system. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator. ANS9805W Cannot create .SpaceMan directory.
Explanation: Information in the space management status file is not synchronized with the file system. System Action: ITSM continues processing. User Response: To correct the information, run reconcile, and then refresh the current window. ANS9814W Cannot create migration object ID.
Explanation: Cannot create .SpaceMan directory for this file system. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator. ANS9806W File system type is not supported.
Explanation: The file system is full. No more free space can be allocated for the migration object ID when a file is being migrated or recalled. System Action: ITSM terminates the current operation for this file system. User Response: Remove some files in the file system, and then run reconciliation. Retry the operation. ANS9815W Out of free space or inodes in file system to migrate or recall.
Explanation: The file system is not a type supported by space management. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator. ANS9808W Invalid field in the dsmmigfstab file.
Explanation: There is an invalid field in the dsmmigfstab file entry for the file system. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator. ANS9809W Cannot open the dsmmigfstab file.
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: ITSM terminates the current operation for this file system. User Response: Remove some files in the file system, and then run reconciliation. Retry the operation. ANS9816W File system has exceeded its quota.
Explanation: ITSM cannot open the dsmmigfstab file. System Action: ITSM cannot add space management to the file system. User Response: Check with the system administrator. ANS9811W Server did not respond. Check the server connection. Select OK to exit. Explanation: ITSM detects that the file system has exceeded its quota. No more files can be migrated to ITSM storage for this file system. System Action: ITSM will not migrate files from this 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: Server did not respond. System Action: ITSM stops processing. User Response: Exit dsmhsm. Check the server connection and try again later. ANS9812I Files not found in current directory. Refresh file systems.
Explanation: Some files are not found in the local file system.
Explanation: The file system is in a global inactive state. System Action: ITSM cannot continue the process. User Response: Wait until the system administrator globally reactivates the file system.
Chapter 5. Client and Data Protection for Lotus Notes Messages
741
ANS9818W ANS9829W
ANS9818W A selective recall is in progress. Stop the recall, and then close the window. ANS9823W Current password is not entered.
Explanation: You did not enter the current password. System Action: The Change password dialog will display again. User Response: Enter the current password. ANS9824W Cannot update space management settings for file-system
Explanation: You tried to close the Selective Recall Status window while a selective recall was in progress. System Action: ITSM ignores the request. User Response: Stop the selective recall process, and then close the window. ANS9819W A selective migration is in progress. Stop the process, and then close the window.
Explanation: You tried to update space management settings for a file system, and the update failed. System Action: ITSM continues with normal operation. User Response: Check with the system administrator. ANS9825W Total migrated space is greater than quota for file system.
Explanation: You tried to close the Selective Migration Status window while a selective migration was in progress. System Action: ITSM ignores the request. 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: ITSM total migrated space is greater than quota. System Action: ITSM continues. User Response: You can remove this warning message by increasing the quota for the file system. ANS9827W Error accessing the Recall daemon lock file: file name.
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 System Action: ITSM ignores the request. 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: There is a problem accessing the recall daemon lock file. System Action: ITSM 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: 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: There is a problem accessing the space monitor daemon. System Action: ITSM 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. ANS9829W Recall daemon is not running.
Explanation: You did not enter the new password. System Action: The Change password dialog will display again. User Response: Enter the new password.
Explanation: An ITSM recall daemon is not running. System Action: ITSM recall fails. User Response: Ask the system administrator to start a recall daemon by issuing the dsmrecalld command.
742
IBM Tivoli Storage Manager: Messages
ANS9830W ANS9855W
ANS9830W Space monitor daemon is not running. ANS9846W Cannot add space management to file system.
Explanation: The space monitor daemon is not running. System Action: ITSM is unable to perform space management functions. User Response: Ask the system administrator to start the space monitor daemon by issuing the dsmmonitord command. ANS9840W Cannot open /dev/fsm.
Explanation: ITSM cannot add space management to the file system. System Action: ITSM continues with normal operation. User Response: Check with the system administrator. ANS9848W Cannot activate file system file system.
Explanation: While attempting to add space management to a file system, ITSM was unable to open the /dev/fsm device, which is the space management (hsm) device driver. System Action: ITSM terminates the requested process and returns to normal operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9841E Cannot get user name for the user ID.
Explanation: ITSM cannot activate space management for the specified file system. System Action: ITSM file system state is not changed. User Response: Check with your system administrator. 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. System Action: ITSM continues with normal operation. User Response: Check with your system administrator. ANS9853W The space management client program is downlevel.
Explanation: ITSM cannot get the user name for the user ID. System Action: ITSM terminates the requested process and returns to normal operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9843E Cannot connect to migration server.
Explanation: The space management client is downlevel compared to the kernel level. System Action: ITSM continues with normal operation. User Response: Check with your system administrator. ANS9854W The space management kernel is downlevel.
Explanation: ITSM cannot connect to the migration server specified in your client system options file. System Action: ITSM terminates the requested process and returns to normal operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ANS9844E Cannot close the premigrated files database.
Explanation: The space management kernel is downlevel compared to the client level. System Action: ITSM continues with normal operation. User Response: Check with your system administrator. ANS9855W File is accessed during migration. File skipped.
Explanation: ITSM 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. System Action: ITSM terminates the requested process, and returns to normal operation. User Response: Retry the operation. If the problem continues, check with your system administrator.
Explanation: The specified file-name was not migrated because the file was accessed by another process during the attempt to migrate it. System Action: ITSM left the file resident.
Chapter 5. Client and Data Protection for Lotus Notes Messages
743
ANS9856E ANS9878W
User Response: If you want the file migrated, stop the 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. System Action: ITSM accepts your request. User Response: To see all attributes in full length, increase the column width. ANS9873W This function should not be used on large file systems. Continue anyway ?
Explanation: The specified file was not migrated because the file was opened by one or more other processes. System Action: ITSM left the file resident. User Response: If you want the file migrated, stop the processes which currently have the file open, and retry the migration operation. ANS9858E Bit file for image on push button cannot be found. Please check to make sure the pixmap file exists in your ITSM installed directory.
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: ITSM waits for your response. User Response: If you want to continue, select OK. Otherwise, select Cancel. ANS9875W 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. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 14400. ANS9876W Refresh time must be a positive number.
Explanation: ITSM failed to find the pixmap file defined for the push button. System Action: ITSM continues with normal operation. User Response: Check to see whether the pixmap file exists in the ITSM installation directory. ANS9860W Some selected files are hidden. Change View option to see all.
Explanation: You have entered an invalid value for Refresh time. It must be a positive number between 0 and 14400. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 14400. ANS9877W Size Factor must be a numeric value between 0 - 999999999.
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: ITSM proceeds normally. User Response: If you want to see all selected files, change the View option from the View menu bar option. ANS9862W Do you want to exit ITSM space management?
Explanation: You have entered an invalid value for Size Factor. It must be a positive number between 0 and 999999999. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 999999999. ANS9878W Size Factor must be a positive number.
Explanation: You have selected Exit from the File menu bar option. System Action: ITSM 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 an invalid value for Size Factor. It must be a positive number between 0 and 999999999. System Action: ITSM continues with normal operation.
Explanation: You have entered a column width that is too small to display all digits of the largest attribute.
744
IBM Tivoli Storage Manager: Messages
ANS9879W ANS9887W
User Response: Enter a positive number between 0 and 999999999. ANS9879W Age Factor must be a numeric value between 0 - 999999999. User Response: Enter a positive number between 0 and 999999999. ANS9884W Quota must be a positive number.
Explanation: You have entered an invalid value for Age Factor. It must be a positive number between 0 and 999999999. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 999999999. ANS9880W Age Factor must be a positive number.
Explanation: You have entered an invalid value for Quota. It must be a positive number between 0 and 999999999. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 999999999. ANS9885I 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: You have entered an invalid value for Age Factor. It must be a positive number between 0 and 999999999. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 999999999. ANS9881W Premigration Percent must be a numeric value between 0 - 100.
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. System Action: ITSM waits until you select 'Add' or 'Update' to apply your premigration percentage to the system. User Response: When you have changed the space management attribute, select 'Add' or 'Update', and then the system will apply your new premigration percentage. ANS9886W Enter a positive number for Column Width.
Explanation: You have entered an invalid value for Premigration Percentage. It must be a positive number between 0 and 100. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 100. ANS9882W Premigration Percent must be a positive number.
Explanation: You have entered an invalid value for Column Width. It must be a positive number between 0 and 18. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 18. ANS9887W Enter a positive number for Space Between Column.
Explanation: You have entered an invalid value for Premigration Percentage. It must be a positive number between 0 and 100. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 100. ANS9883W Quota must be a numeric value between 0 - 999999999.
Explanation: You have entered an invalid value for Space Between Column. It must be a positive number between 0 and 18. System Action: ITSM continues with normal operation. User Response: Enter a positive number between 0 and 18.
Explanation: You have entered an invalid value for Quota. It must be a positive number between 0 and 999999999. System Action: ITSM continues with normal operation.
Chapter 5. Client and Data Protection for Lotus Notes Messages
745
ANS9889W ANS9915I
ANS9889W Space management has not been added to file-system file system. Do you want to build the directory tree anyway? ANS9903E Space management is deactivated for this file system.
Explanation: You selected a file system that is not managed by HSM. System Action: ITSM 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 ITSM main window, and then selecting Add under the Selected menu option. ANS9891W Please mark either or both check boxes before proceeding.
Explanation: You tried to migrate a file in a file system for which space management is inactive. System Action: ITSM continues to migrate files only in active file systems. User Response: Reactivate space management for the file system, and retry the migration operation. ANS9904E Transaction failed, migration aborted.
Explanation: The specified file-name was not migrated because the file was accessed by another process during the attempt to migrate it. System Action: ITSM migration is aborted. User Response: If you want the file migrated, stop the process that is accessing the file, and then retry the migration. ANS9908E System Error.
Explanation: You have not marked either of the check boxes. System Action: ITSM 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: ITSM detects an error in reading the state of the file system. System Action: ITSM proceeds with normal operation. User Response: Report the error to your system administrator. ANS9909I Error in accessing migration candidates list file.
Explanation: You tried to select a file in a file system for which space management is inactive. System Action: ITSM continues with normal operation. User Response: Reactivate space management for the file system, and then proceed with selecting files. ANS9900E FSM kernel extension not installed.
Explanation: ITSM detects an error in reading the migration candidates list file. This file resides in the .SpaceMan directory of the file system. System Action: ITSM proceeds with normal operation. User Response: Report the error to your system administrator. ANS9914I Space management settings have been modified successfully on file-system file system.
Explanation: The file system selected is not fully activated. The system received an error trying to open /dev/fsm. System Action: ITSM operation stops. User Response: Check to see whether /dev/fsm entry exists, and check space management installation. ANS9901E Cannot migrate ITSM system internal file.
Explanation: Space management settings have been updated successfully. System Action: ITSM updated space management settings for the file system. User Response: Continue with normal operation. ANS9915I Space management has been added successfully to file-system file system.
Explanation: You tried to select files that are used internally by the HSM client. You cannot migrate ITSM internal files. System Action: ITSM ignores your request. User Response: None.
Explanation: Space management has been added successfully. System Action: ITSM added and activated space management for the file system.
746
IBM Tivoli Storage Manager: Messages
ANS9918E ANS9941I
User Response: Continue with normal operation. ANS9918E Cannot open migration candidates list for file-system. ANS9935I Start Threshold Migration only works on an Active file system. If you want to make file-system file system Active, select Add Space Management.
Explanation: ITSM cannot access the migration candidates list for the specified file system. System Action: ITSM continues normal operation. User Response: Select OK to return. ANS9928I Space management has been deactivated successfully on file-system file system.
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. System Action: Processing stopped. User Response: Select OK to return. Select Add if you want to add space management to the file system. ANS9936I Start Threshold Migration only works on an Active file system. If you want to make file-system file system Active, select Reactivate.
Explanation: Space management is deactivated successfully. System Action: ITSM deactivated space management for the file system. User Response: Select OK to return. ANS9929I Space management has been reactivated successfully on file-system file system.
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. System Action: Processing stopped. User Response: Select OK to return. Select 'Reactivate' to reactivate space management for the file system. ANS9938I Space management has not been added to file-system file system. You do not need to deactivate space management.
Explanation: Space management is reactivated successfully. System Action: ITSM reactivated space management for the file system. User Response: Select OK to return. 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 deactivate space management on a file system to which space management has not been added. System Action: Processing stopped. User Response: Select OK to return. ANS9941I Space management has not been added 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 display the migration candidates list for a Native file system (a file system to which space management has not been added). System Action: Processing stopped. 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. System Action: Processing stopped. User Response: Select OK to return. Select Add if you want to add space management to the file system.
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. System Action: Processing stopped. User Response: Select OK to return. Select Add if you want to add space management to the file system.
Chapter 5. Client and Data Protection for Lotus Notes Messages
747
ANS9942S ANS9954E
ANS9942S Space management has not been added to file-system file system. Do you want to add space management now? ANS9948E File: file-spec size is less than the minimum size required for migration.
Explanation: You tried to update space management settings for a file system to which space management has not been added. System Action: Processing stopped. 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.
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. System Action: ITSM will not highlight the file. User Response: None. 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. System Action: Processing stopped. User Response: Select OK to return. ANS9944I Space management has been deactivated on file-system file system. You must reactivate space management before you can remove it.
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. System Action: ITSM will not highlight the file. User Response: None. ANS9950E File: file-spec is not qualified for migration because the Space Management Technique attribute is set to None.
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. System Action: Processing stopped. User Response: Select OK to return. Select Reactivate, and then select Remove to remove space management. ANS9945I Space management has not been added to file-system file system. You do not need to remove space management.
Explanation: The Space Management Technique attribute in the management class is set to None, which does not allow a file to be migrated. System Action: ITSM will not highlight the file. User Response: Assign a management class to the file that specifies Automatic or Selective for the Space Management Technique attribute. ANS9951E File: file-name file has already been migrated.
Explanation: You tried to migrate a file that is already migrated. System Action: ITSM will not highlight the file. User Response: None. ANS9953E The management class assigned to this file does not allow migration.
Explanation: You tried to remove space management from a file system to which space management has not been added. System Action: Processing stopped. User Response: Select OK to return. ANS9947E File: file-spec is in a file system to which space management has not been added.
Explanation: The management class assigned to this file does not allow migration. System Action: ITSM does not migrate the file. User Response: None. ANS9954E This file has already been migrated.
Explanation: You tried to migrate a file that resides in a file system to which space management has not been added. System Action: ITSM will not highlight/process the file. User Response: Switch over to the Space Manager window, and add space management to the file system.
Explanation: The file has been previously migrated. System Action: File is skipped. User Response: None.
748
IBM Tivoli Storage Manager: Messages
ANS9958E ANS9998E
ANS9958E File file-namefile-namefile-name has not yet reached the age for migration. File skipped. ANS9965S Please select a file system first.
Explanation: You did not select any file system for the Migrate window. System Action: ITSM 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. ANS9966S No file system has been selected.
Explanation: This file cannot be migrated because it has not yet reached the age for migration. System Action: ITSM will not highlight the file. User Response: None. ANS9960W 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: ITSM 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. ANS9961E Server out of migrate data storage space.
Explanation: You did not select a file system. System Action: ITSM ignores the request and continues. User Response: Select at least one file system and retry the operation ANS9988S As part of the remove process, all migrated files in file-system will be recalled from ITSM server. Do you want to continue with the remove process now?
Explanation: The server ran out of space in its migrate data storage. System Action: ITSM cannot complete the migrate operation. Any files displayed in the Successful list of the Migrate Status window were successfully migrated. User Response: Check with your system administrator. ANS9962I Migration stopped by user.
Explanation: When you remove space management from a file system, ITSM recalls all migrated files. System Action: ITSM 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 The selective migration, selective recall, or policy information window is displayed. Stop any operations, close the window, and then retry the operation.
Explanation: You requested that ITSM stop the migrate operation. System Action: Migration stopped. User Response: Continue with normal operations. ANS9963I Selective Recall completed. Check failure list for possible errors.
Explanation: The recall was completed. System Action: ITSM recalled the files. User Response: Continue with normal operations. ANS9964I Selective Migration completed. Check failure list for possible errors.
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. System Action: ITSM ignores the request. User Response: Close the selective migration, selective recall, or policy information window, and then retry the operation. ANS9998E The migration server changed after the selective migration or selective recall window was displayed. Close the window, and then retry the operation.
Explanation: The migration was completed. System Action: ITSM migrated the files. User Response: Continue with normal operations.
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.
Chapter 5. Client and Data Protection for Lotus Notes Messages
749
ANS9999E ANS13408W
User Response: Close the selective migration or selective recall window, and then retry the operation. ANS9999E (): ANS13402W name: A system call func failed with code rc. Explanation: Failed to get volume information. System Action: User Response: Contact your system administrator or ITSM administrator. ANS13403W Cannot open the volume name for reading. System error code err. Explanation: The volume could not be opened for reading. System Action: User Response: Contact your system administrator. ANS13404W Error reading the volume name. Explanation: The volume could not be read. System Action: User Response: Contact your system administrator. ANS13041I Backup system component is excluded from processing. ANS13405W Unknown filesystem fs on volume name. Explanation: The filesystem found on the volume is not recognized. System Action: Processing continues. User Response: Contact your systems administrator. ANS13406W Physical mapping of the volume name is not supported. Explanation: The logical volume layout is not currently supported for physical mapping. System Action: User Response: Refer to the documentation for information on what volume layouts are supported for physical mapping. ANS13407W name is not local. Explanation: The drive or filesystem is not local and is not suitable for image backup. System Action: Processing stopped. User Response: Specify a volume that is local. ANS13408W The volume name contains bad blocks. Explanation: The volume contains bad blocks and is not suitable for server-free operations. System Action: Processing continues using non-server-free data movement. User Response: Contact your system administrator.
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 ITSM 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. User Response: 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 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.
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. ANS13042I 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. ANS13401W The volume name is invalid. Explanation: A volume with this name could not be found or is not suitable for server-free operations. System Action: Processing stopped. User Response: Specify the correct name.
750
IBM Tivoli Storage Manager: Messages
ANS13409W ANS25548E
ANS13409W Error writing to the volume name. Explanation: An error occured while attempting to write to the volume. System Action: User Response: Contact your system administrator. ANS25537T WebSphere Application Server ANS25538T Network Deployment Manager ANS25539T Application Server ANS25540T WARNING! Restoring data other than at the group level can corrupt your WebSphere installation. It is strongly recommended that you restore data at the Network Deployment Manager node or Application Server node level only. Do you want to continue? ANS25541E Node entered has been federated into a Network Deployment, federated nodes cannot be backed up. ANS25544E Error in WAS procesing.
Explanation: There has been a fatal error in WAS processing. System Action: None User Response: Run dsmc q was -wastype=local to see the nodes that may be backed up. Make sure all information is correct and try again. If the error persists contact you system administrator. ANS25545I WAS Processing has succsessfully completed.
Explanation: WAS Processing has succsessfully completed. System Action: None User Response: None ANS25546E Failed to lock the WebSphere Configuration Repository
Explanation: Failed to lock the WebSphere Configuration Repository. System Action: None User Response: Make sure that the WebSphere server is up. If the server is already up, make sure that the repository is unlocked. Make sure that you are backing the correct node up. To see a list of available nodes that can be backed up run: dsmc q was -wastype=local. ANS25547E Failed to unlock the WebSphere Configuration Repository
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. ANS25542E Incorrect WAS backup type entered, no node of that name and type exists.
Explanation: Failed to unlock the WebSphere Configuration Repository. System Action: None User Response: Make sure that the WebSphere server is up. If the repository is locked, then unlock it and try the operation again. Make sure that the correct node up is being backed up. To see a list of available nodes that can be backed up run: dsmc q was -wastype=local. ANS25548E A supported version of WebSphere is not installed on this machine.
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. ANS25543E 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.
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.
Chapter 5. Client and Data Protection for Lotus Notes Messages
751
ANS25549E ANS25550E
ANS25549E No Application Server instances found to backup
Explanation: Application Server is not installed on this machine. ANS25550E No Network Deployment Manager instances found to backup
Explanation: Deployment Manager is not installed on this machine.
752
IBM Tivoli Storage Manager: Messages
Part 4. Data Protection Products Messages
This section contains messages for the following Data Protection products: v Data Protection for Lotus Domino v Data Protection for Microsoft Exchange Server v Data Protection for Microsoft SQL Server v Data Protection for Oracle v Data Protection for mySAP.com Technology for DB2 UDB v Data Protection for mySAP.com Technology for Oracle v Data Protection for EMC Symmetrix for mySAP.com Technology v v v v Data Data Data Data Protection Protection Protection Protection for for for for IBM IBM IBM IBM ESS for mySAP.com Technology for DB2 UDB ESS for mySAP.com Technology for Oracle Enterprise Storage Server for DB2 UDB Enterprise Storage Server for Oracle
Note: The Data Protection for Lotus Notes messages have a prefix (ANU) that is common with administrative clients, API clients, backuparchive clients, and HSM clients. See Part III for a listing of those messages. Each of the Data Protection products in this section has a unique prefix or numeric range for its messages. The prefix (and numeric range) that corresponds to each Data Protection product is as follows: ACD (00009999) Data Protection for Lotus Domino ACN (00009999) Data Protection for Microsoft Exchange Server ACO (00009999) Data Protection for Microsoft SQL Server ANU (00009999) Data Protection for Oracle BKI (00009999) Data Protection for mySAP.com Technology for DB2 UDB and Data Protection for mySAP.com Technology for Oracle IDS (00000999) Data Protection for EMC Symmetrix for mySAP.com Technology IDS (10002999) Data Protection for ESS for mySAP.com Technology for DB2 UDB and Data Protection for ESS for mySAP.com Technology for Oracle EEP (00009999) Data Protection for Enterprise Storage Server for DB2 UDB EEO (00009999) Data Protection for Enterprise Storage Server for Oracle For each Data Protection product, the messages are listed in numeric order.
Copyright IBM Corp. 1993, 2004
753
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.
754
IBM Tivoli Storage Manager: Messages
Chapter 6. Data Protection for Lotus Domino (ACD0000ACD9999)
This chapter describes the messages issued by Data Protection for Lotus Domino. The messages begin with the prefix ACD and are listed in numerical order.
ACD0003S An internal processing error has occurred. ACD0055E Write failure on license file (licensefile).
Explanation: An internal processing error has occurred. System Action: Processing ends. User Response: Retry the operation. If this error persists, contact your service representative. ACD0004E An unknown error has been detected.
Explanation: An attempt to write to the license file failed. System Action: Processing ends. 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 internal processing error has occurred that prevents the generation of a message for a return code. System Action: Processing continues. User Response: Retry the operation. If this error persists, contact your service representative. ACD0005E Out of memory. Stop other processes and try the operation again.
Explanation: An attempt to read information from the license file failed. System Action: Processing ends. User Response: Install the product again. ACD0057E The checksum in the license file (licensefile) does not match the license string text.
Explanation: The machine has run out of memory. System Action: Processing continues. User Response: Close unnecessary processes and try the operation again. ACD0053E License file (licensefile) could not be opened.
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. System Action: Processing ends. User Response: Reinstall the product. ACD0058E The Try and Buy license has expired.
Explanation: An attempt to read from the license file failed. System Action: Processing ends. User Response: Install the product again. This ensures that the correct license file is installed. ACD0054E Read failure on license file (licensefile).
Explanation: This Try and Buy license that was detected has expired. System Action: Processing ends. User Response: This product is no longer valid for use. A valid license must be obtained before running the product. ACD0100E Incomplete command:
Explanation: An attempt was made to read from the license file. This attempt failed. System Action: Processing ends. User Response: Reinstall the product. This will ensure that the correct license file is installed.
Explanation: This message displays the incomplete command that was entered. System Action: Processing ends. User Response: Re-enter the complete command.
Copyright IBM Corp. 1993, 2004
755
ACD0101E ACD0152I
ACD0101E Invalid argument: ACD0133W Could not locate installation directory. Attempting to continue...
Explanation: This message displays the command that was entered, up to and including the invalid command or option argument that was detected. System Action: Processing ends. User Response: Re-enter the command specifying a valid argument for the command or option. ACD0102E Invalid command:
Explanation: An attempt was made to read the registry to determine where the Tivoli Data Protection application client was installed. This attempt failed. System Action: Processing will continue with the command entered. 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...
Explanation: This message displays the invalid command that was entered. System Action: Processing ends. User Response: Re-enter a valid command. ACD0103E Invalid option for the specified command:
Explanation: This message displays the command that was entered, up to and including the option that was detected as invalid for the command. System Action: Processing ends. User Response: Re-enter the command specifying valid command options. ACD0104E Invalid option:
Explanation: An attempt was made to read the registry to determine where the Tivoli Data Protection application client log is located. This attempt failed. System Action: Processing will continue with the command entered. 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. ACD0150I Operation canceled by user.
Explanation: This message displays the command that was entered, up to and including the invalid option that was detected. System Action: Processing ends. User Response: Re-enter the command specifying valid command options. ACD0105E Missing argument:
Explanation: The user has requested that the Tivoli Storage Manager application client end by entering ctrl-C. System Action: Processing ends. User Response: None ACD0151E Errors occurred while processing the request.
Explanation: This message displays the command that was entered, up to and including the command or option whose required argument is missing. System Action: Processing ends. User Response: Re-enter the command specifying a valid argument for the command or option. ACD0132W Tracing could not be started. Processing will continue.
Explanation: Attempting to process the request entered, an error occurred. System Action: Processing ends. User Response: Attempt to determine the source of the errors from viewing the log file. Correct the problems and try running the command again. ACD0152I Performance stats: seconds seconds spent in apicall API calls
Explanation: A problem prevented tracing from beginning. System Action: Processing will continue with the command entered. User Response: Refer to the other messages that display with this message to determine the problem.
Explanation: The indicated number of seconds were spent making API calls for the indicated system. System Action: Processing continues. User Response: None
756
IBM Tivoli Storage Manager: Messages
ACD0153I ACD0200E
ACD0153I Performance stats: seconds seconds spent in function ACD0160E An authentication error occurred with your stored Tivoli Storage Manager password.
Explanation: The indicated number of seconds were spent the named function. System Action: Processing continues. User Response: None ACD0154E The Tivoli Storage Manager application client cannot work with the version of the Tivoli Storage Manager API you have installed. Please install version version.release.level or greater.
Explanation: You were unable to log on to the Tivoli Storage Manager server due an authentication error. System Action: Processing stops. 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: The version of the Tivoli Storage Manager API currently installed on the system is older than the version used to build the Tivoli Storage Manager application client. System Action: Processing ends. User Response: Install a version of the Tivoli Storage Manager API at or later than the indicated level. A copy is distributed with the Tivoli Storage Manager application client. ACD0155E The Tivoli Storage Manager application client cannot work with the release of Tivoli Storage Manager API you have installed. Please install release version.release.l evel or greater.
Explanation: An incorrect password was entered. System Action: Processing stops. User Response: Enter the correct Tivoli Storage Manager password and try again. ACD0162E The passwords entered do not match. Please enter them again.
Explanation: An incorrect password was entered. System Action: Processing stops. User Response: Enter the passwords again. ACD0163E The directory path needs to be fully-qualified.
Explanation: The release of the Tivoli Storage Manager API currently installed on the system is older than the release used to build the Tivoli Storage Manager application client. System Action: Processing ends. User Response: Install a release of the Tivoli Storage Manager API at or later than the indicated level. A copy is distributed with the Tivoli Storage Manager application client. ACD0156E Could not load the Tivoli Storage Manager API.
Explanation: The /intopath option was specified without a fully-qualified path. System Action: Processing stops. 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: The Tivoli Storage Manager API could not be loaded. System Action: Processing ends. User Response: Ensure the Tivoli Storage Manager API is correctly installed. Run the Tivoli Storage Manager 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.
Explanation: An attempt was made to use a fully-qualified file name that was too long. This attempt failed. System Action: Processing ends. 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. System Action: Processing ends. User Response: None
Chapter 6. Data Protection for Lotus Domino
757
ACD0201E ACD0213E
ACD0201E File (filename) could not be opened for writing. ACD0208E There is not enough disk space for the operation attempted.
Explanation: An attempt was made to open a file for writing. This attempt failed. System Action: Processing ends. User Response: None ACD0202E Read failure on file (filename).
Explanation: An attempted operation required more disk space than was available. The attempt failed. System Action: Processing ends. User Response: None ACD0209E The rename of file (filename1) to (filename2) failed.
Explanation: An attempt was made to read from a file. This attempt failed. System Action: Processing ends. User Response: None ACD0203E Write failure on file (filename).
Explanation: An attempt was made to rename a file. This attempt failed. System Action: Processing ends. User Response: None ACD0210E The Tivoli Storage Manager high level qualifier is too long.
Explanation: An attempt was made to write to a file. This attempt failed. System Action: Processing ends. User Response: None ACD0204E File (filename) could not be closed.
Explanation: An attempt was made to use a Tivoli Storage Manager high level qualifier that was too long. This attempt failed. System Action: Processing ends. User Response: None ACD0211E The Tivoli Storage Manager low level qualifier is too long.
Explanation: An attempt was made to close a file. This attempt failed. System Action: Processing ends. User Response: None ACD0205E File (filename) statistics could not be obtained.
Explanation: An attempt was made to use a Tivoli Storage Manager low level qualifier that was too long. This attempt failed. System Action: Processing ends. User Response: None ACD0212E The Tivoli Storage Manager filespace name is too long.
Explanation: An attempt was made to obtain file statistics. This attempt failed. System Action: Processing ends. User Response: None ACD0206E Directory (directory) could not be created.
Explanation: An attempt was made to use a Tivoli Storage Manager filespace name that was too long. This attempt failed. System Action: Processing ends. User Response: None ACD0213E The maximum number of objects allowed per Tivoli Storage Manager transaction is t oo small.
Explanation: An attempt was made to create a directory. This attempt failed. System Action: Processing ends. 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. System Action: Processing ends. User Response: None
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 Tivoli Storage Manager application client. System Action: Processing ends.
758
IBM Tivoli Storage Manager: Messages
ACD0214E ACD0259E
User Response: Increase the maximum number of 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. ACD0219E The Tivoli Storage Manager low level qualifier is invalid.
Explanation: The low level qualifier name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the low level qualifier name length, characters, and directory delimeters are valid. ACD0256E 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: The Tivoli Storage Manager server has indicated that the backup objects management class backup copy group does not exist. System Action: Processing ends. User Response: Contact your Tivoli Storage Manager server administrator. ACD0215E All backup objects do not have the same management class backup copy destination.
Explanation: In order to maintain backup data integrity, multiple backup objects are sent to the Tivoli 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. System Action: Processing ends. User Response: Contact your Tivoli Storage Manager server administrator. ACD0216E Unable to obtain space information for volume (volumename).
Explanation: Your Tivoli Storage Manager password has expired. You need to change your password. System Action: Processing ends. 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.
Explanation: Your Tivoli Storage Manager password has expired. A new password needs to be obtained. System Action: Processing ends. User Response: Obtain a new password for your Tivoli Storage Manager node using the change password command or by asking your Tivoli Storage Manager Administrator to change your password. ACD0258E You did not enter a valid password. Processing ends.
Explanation: An attempt was made to obtain space information for a volume. This attempt failed. System Action: Processing ends. User Response: None ACD0217E The Tivoli Storage Manager filespace name is invalid.
Explanation: The filespace name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the filespace name length, characters, and directory delimeters are valid. ACD0218E The Tivoli Storage Manager high level qualifier is invalid.
Explanation: The password that was entered was not a valid password. System Action: Processing ends. User Response: Re-enter the command specifying a valid password. ACD0259E 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 high level qualifier name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the high level qualifier name length, characters, and directory delimeters are valid.
Explanation: The password you entered for verification of your new password does not match the new password that was entered. System Action: Processing ends.
Chapter 6. Data Protection for Lotus Domino
759
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. ACD0266E Could not find the Tivoli Storage Manager HTML books.
Explanation: An attempt was made to read the registry to determine where the Tivoli Storage Manager books were installed. This attempt failed. System Action: Processing ends. User Response: It may be necessary to reinstall the application client code. This will ensure that the registry entries are set up correctly. ACD0267E The verify password entered does not match the new password entered.
Explanation: The change password command completed successfully System Action: Processing ends. User Response: None ACD0261I There are no backups for the server named servername.
Explanation: There are no backups on the Tivoli Storage Manager server for the specified server name. System Action: Processing ends. User Response: None ACD0263E Failed to start Web browser with a return code of returncode.
Explanation: The verify password does not match the new password. System Action: Processing ends. User Response: Retry the command with a matching verify password. ACD0300E Invalid restore type.
Explanation: An attempt was made to start the web browser to view the TSM HTML b ook. This attempt failed. System Action: Processing ends. 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.
Explanation: The type of restore requested is invalid. System Action: Processing ends. User Response: Re-enter the command specifying a valid restore type. ACD0301E Invalid backup type.
Explanation: The type of backup requested is invalid. System Action: Processing ends. User Response: Re-enter the command specifying a valid backup type. ACD351E Invalid trace keyword - keyword
Explanation: An attempt was made to read the registry to determine the default browser. However, a default browser is not defined. A determination will be made where Microsoft Internet Explorer is installed. System Action: Processing continues. 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. ACD0265E Could not find Internet Explorer.
Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect. System Action: Client program did not initialize or tracing was not enabled in the applet. User Response: Correct the value. ACD357E Unable to open trace output file file-name.
Explanation: An attempt was made to read the registry to determine where Microsofts Internet Explorer was installed. This attempt failed. System Action: Processing ends. User Response: Make sure that the registry is set up correctly for Internet Explorer.
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. System Action: Client program did not initialize. User Response: Change the TRACEFILE value so that it is a location to which you have write access.
760
IBM Tivoli Storage Manager: Messages
ACD366E ACD5110E
ACD366E Unable to close trace output file file-name. ACD385E Unable to delete symbolic link link.
Explanation: Log linkname cannot be a symbolic link. System Action: Processing stops. User Response: Delete the symbolic link linkname. ACD476E program-name: cannot open file file-spec: error.
Explanation: An error occurred during the closing of a trace output file-name (for example, not enough disk space). System Action: Processing continues. User Response: Check the options.doc file for a description of possible causes of the error, or see your system administrator. ACD367E Unable to write to trace file tracefile. Tracing disabled.
Explanation: TSM cannot open the file. System Action: TSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ACD5022I A new configuration file has been created.
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. ACD368E Invalid trace file name (name too long).
Explanation: The /configfile value specified a file name that does not exist. A new file was created. System Action: Processing continues. User Response: None. ACD5023W The configuration file cannot be found, using default settings.
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. ACD383E Specifying the trace file link as a symbolic link is not allowed.
Explanation: The /configfile value specified a file that cannot be found. Default settings are used. System Action: Processing continues. 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: Trace file linkname cannot be a symbolic link. System Action: The symbolic link linkname is deleted, the trace file is recreated, and processing stops. User Response: Specify the trace file location with the tracefile option. ACD384E Symbolic link linkname to target was successfully deleted.
Explanation: The PASSWORDACCESS option specifies generate in the client options files. There is currently no stored password. An initial password needs to be stored. System Action: Processing ends. 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).
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.
Explanation: The Tivoli Storage Manager application client could not find the Domino server configuration file (notes.ini) file. System Action: Processing ends.
Chapter 6. Data Protection for Lotus Domino
761
ACD5111E ACD5204I
User Response: Ensure that either the notes.ini file is specified in the PATH statement or that the NOTESInipath configuration parameter is correct. ACD5111E Error getting the name of the Domino data directory. User Response: Ensure that Tivoli Storage Manager and the Lotus Domino Server are properly installed, then try the operation again. ACD5200I Application Client: Starting backup of database database from server servername.
Explanation: The Lotus Domino API could not return the name of the Domino data directory. System Action: Processing ends. User Response: Ensure the Lotus Domino server is correctly installed. ACD5115E No databases were found that match the file specification entered.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a database backup begins. System Action: None User Response: None Centrally logged ACD5201I Application Client: Backup of database database from server servername completed successfully.
Explanation: The Lotus Domino Server was searched for databases that matched the entered file specification. No databases were found. System Action: Processing ends. User Response: Correct the file specification and try the operation again. ACD5128E The user specified NotesIniPath does not exist. Verify that the path setup for the NotesIniPath preference really exists.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a database backup completes successfully. System Action: None User Response: None Centrally logged ACD5202E Application Client: Backup of database database from server servername failed.
Explanation: The IBM Tivoli Storage Manager for Mail application client could not find the specified NotesIniPath. System Action: Processing ends. 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.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a database backup fails. System Action: None User Response: None Centrally logged ACD5203I Application Client: Starting archive of transaction log file transactionlog from server servername.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a transaction log file archive begins. System Action: None User Response: None Centrally logged ACD5204I Application Client: Archive of transaction log file transactionlog from server servername completed successfully.
Explanation: The Tivoli Storage Manager application client could not find the Lotus Domino Server program executable directory. System Action: Processing ends. User Response: Ensure that the PATH statement contains the Lotus Domino Server program executable directory, then retry the operation. ACD5130E Could not initialize the connection to Lotus Domino properly. error=errorcode
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a transaction log file archive completes successfully. System Action: None User Response: None Centrally logged
Explanation: The Tivoli Storage Manager application client could not initialize Lotus Domino properly. The error code is given. System Action: Processing ends.
762
IBM Tivoli Storage Manager: Messages
ACD5205E ACD5215E
ACD5205E Application Client: Archive of transaction log file transactionlog from server servername failed. ACD5210I Application Client: Starting transaction log archive from server servername.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a transaction log file archive fails. System Action: None User Response: None Centrally logged
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a transaction log archive begins. System Action: None User Response: None Centrally logged ACD5211I Transaction log archive from server servername complete. Total transaction log files archived: transactionlogs Total bytes transferred: bytes Elapsed processing time: time Secs Throughput rate: rate Kb/Sec
ACD5206I
Application Client: Starting incremental database backup from server servername.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when an incremental backup begins. System Action: None User Response: None Centrally logged ACD5207I Application Client: 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
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a transaction log archive ends. System Action: None User Response: None Centrally logged ACD5212I Application Client: Starting restore for server servername.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when an incremental backup ends. System Action: None User Response: None Centrally logged ACD5208I Application Client: Starting selective database backup from server servername.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a restore begins. System Action: None User Response: None Centrally logged ACD5213I Application Client: Restore database from server servername to server servername complete. Total Domino databases restored: numberdbs Total bytes transferred: bytes Elapsed processing time: time Secs Throughput rate: rate Kb/Sec
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 User Response: None Centrally logged ACD5209I Application Client: 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
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a restore ends. System Action: None User Response: None Centrally logged ACD5215E An error occurred trying to set the requested preference.
Explanation: This is informational message is written to the Tivoli Storage Manager Server activity log when a selective backup ends. System Action: None User Response: None Centrally logged
Explanation: An error occurred while writing to the preferences file. System Action: Processing ends. User Response: View other messages that display. Perform actions described in those messages, then run the command again.
Chapter 6. Data Protection for Lotus Domino
763
ACD5216E ACD5227W
ACD5216E The value for the preference preference is not valid. See the DOMDSMC HELP SET output or the Users Guide for valid SET command parameters. User Response: You may want to consider updating the logfile name using a fully qualified path. ACD5223E The database could not be placed into pending state. The pending database list was in use.
Explanation: The preference being set is not valid. System Action: Processing ends. 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 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 Could not obtain the current pending database list. The pending database list was not available.
Explanation: The preference was set successfully. System Action: Processing ends. User Response: None ACD5218E The Lotus Domino API could not be loaded. Could not load the nnotes.dll
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. System Action: None. User Response: Try the operation again. Contact your service representative if the error persists. ACD5225E Unknown Domino API error code received: returncode
Explanation: The Lotus Domino API, nnotes.dll, could not be loaded. System Action: Processing ends. User Response: Ensure the Lotus Domino Server is installed correctly. ACD5220I The logfile log file could not be pruned. Processing will continue.
Explanation: An attempt to prune the log was unsuccessful. System Action: Processing continues. 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: An unknown Domino API error code was received. The error code is specified in the text of the message. System Action: Processing ends. User Response: Try the operation again. Contact your service representative if the error persists. ACD5226W The logfile log file cannot be opened for writing. There will be no logging of events.
Explanation: The log mentioned pruned successfully. System Action: Processing continues. User Response: None. 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 log file mentioned could not be opened for appends. No logging is performed. System Action: Processing continues without logging. 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 The logfile log file cannot be opened for writing. The log was not pruned and there will be no logging of events.
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.
Explanation: The log file mentioned could not be opened for appends. No logging is performed and the request to prune now was ignored.
764
IBM Tivoli Storage Manager: Messages
ACD5228I ACD5237I
System Action: Processing continues without logging and without pruning. User Response: Determine why the log file could not be opened. The log file is either referring to a non-exixtent drive or partition, or the log file is designated read-only. ACD5228I Application Client: Starting restore of database database to database on server servername. User Response: None Centrally logged ACD5233E Application Client: Inactivation of transactionlog transaction log archive failed.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when an inactivation of a transaction log file archive fails. System Action: None User Response: None Centrally logged ACD5234I Application Client: Inactivation of transactionlog transaction log archive succeeded.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log when a database restore is started. System Action: None User Response: None Centrally logged ACD5229I Application Client: Restore of database database to server servername completed successfully.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when an inactivation of a transaction log file archive succeeds. System Action: None User Response: None Centrally logged ACD5235I Application Client: Starting inactivation of transaction log archive transactionlog.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a database restore completes successfully. System Action: None User Response: None Centrally logged ACD5230E Application Client: Restore of database database to server servername failed.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when an inactivation of a transaction log file archive begins. System Action: None User Response: None Centrally logged ACD5236I Application Client: Starting restore of transaction log files for server servername.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a database restore fails. System Action: None User Response: None Centrally logged ACD5231I Application Client: Starting inactivation of transaction log archives for server servername.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a restore of transaction log files begins. System Action: None User Response: None Centrally logged ACD5237I Application Client: Restore of log files for server servername complete. Total Domino log files restored: numberlogs Total bytes transferred: bytes Elapsed processing time: time Secs
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when an inactivation of transaction log file archives begins. System Action: None User Response: None Centrally logged ACD5232I Application Client: Ending inactivation of transaction log archives for server servername. There were numberlogs transaction log archives inactivated.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a restore of transaction log files ends. System Action: None User Response: None Centrally logged
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when an inactivation of transaction log file archives ends. System Action: None
Chapter 6. Data Protection for Lotus Domino
765
ACD5238I ACD5405E
ACD5238I Application Client: Starting restore of transaction log file transactionlog for server servername. ACD5327I No databases match the following file spec(s): filespec
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a restore of a transaction log file begins. System Action: None User Response: None Centrally logged
Explanation: The Domino API could not find databases that match this file specification. System Action: The file specification is ignored. User Response: Check for a misspelled file specification, then enter command again. ACD5332E No transaction log file archives were found that match the file specification entered.
ACD5239E
Application ClientRestore of transaction log file transactionlog failed.
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a restore of a transaction log file fails. System Action: None User Response: None Centrally logged ACD5240I Application Client: Restore of log file transactionlog succeeded.
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. System Action: Processing ends. User Response: Correct the file specification and retry the operation. ACD5335I No Transaction Log Files match the following file spec(s): filespec
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a restore of a transaction log file succeeds. System Action: None User Response: None Centrally logged ACD5242I Application Client: Restore of transaction log files for server servername complete. Total Domino transaction log files restored: numberlogs Total bytes transferred: bytes Elapsed processing time: time Secs Throughput rate: rate Kb/Sec
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. ACD5404E There is no keyfilename or serverKeyfilename entry in the notes.ini file
Explanation: This informational message is written to the Tivoli Storage Manager Server activity log when a restore of transaction log files ends. System Action: None User Response: None Centrally logged
Explanation: The name of the Lotus Domino Server ID file was not found in the notes.ini file System Action: Processing ends. User Response: Ensure the Lotus Domino Server is correctly installed. ACD5405E There is no server name in the Lotus Domino Server id file
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. System Action: Processing ends. User Response: Enter a seperate command for each set of transaction log files that correspond to a unique log identifier.
Explanation: The name of the Lotus Domino Server was not found in the ID file. System Action: Processing ends. User Response: Ensure the Lotus Domino Server is correctly installed.
766
IBM Tivoli Storage Manager: Messages
ACD5406E ACD5614E
ACD5406E The directory directory does not exist User Response: Specify a valid database name, then try the operation again. ACD5421I There are no backups matching the filespec directorypathfilename and the server name servername.
Explanation: The specified directory was not found. System Action: Processing ends. User Response: Ensure the directory exists, then try the command again. ACD5407E The database database does not exist
Explanation: There are no database backups on the Tivoli Storage Manager Server for the specified server name. System Action: Processing ends. User Response: None ACD5551E Screen size is too small for using the PICK option.
Explanation: The specified database was not found. System Action: Processing ends. 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.
Explanation: You cannot use the PICK option on a workstation that has a screen smaller than 20 characters 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.
Explanation: Notes initialization failed with the indicated return code. System Action: Processing ends. User Response: Ensure the Lotus Domino Server is installed correctly. 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: An attempt to create a file on the Domino server failed. System Action: Processing ends. User Response: Determine and fix the problem. ACD5613E You can only archive logs on a Domino Server with archival logging on. Domino return code: returncode.
Explanation: Errors were encountered during an atempt to run setup for the Tivoli Storage Manager API. System Action: Processing continues. User Response: Examine the dsierror.log file to 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: An attempt was made to archive logs on a Domino Server that is not running archival logging. System Action: Processing ends. 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. Domino return code: returncode.
Explanation: A query was issued to look at databases that are pending activation. There are no databases pending activation. System Action: Processing ends. User Response: None ACD5420E File filename is not a database.
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. System Action: Processing ends. User Response: This operation cannot be performed until logging is turned on for your Domino server.
Explanation: The specified file is not a database. System Action: Processing ends.
Chapter 6. Data Protection for Lotus Domino
767
ACD5615E ACD5710E
ACD5615E You cannot archive a Domino Log file when logging is turned off. Domino return code: returncode. System Action: Processing ends. 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 The high level qualifier of the transaction log file archive is invalid.
Explanation: An attempt was made to archive a Domino Log file for a Domino server that is not running archival logging. System Action: Processing ends. User Response: This operation cannot be performed 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 high level qualifier of a transaction log file archive is invalid. System Action: Processing ends. User Response: Contact your service representative. ACD5708I The applylogs option is ignored when activating databases restored from an alternate Domino server.
Explanation: The database file name to be generated is too long. System Action: Processing ends. 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: 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. User Response: None. ACD5709E The Domino environment variable (environmentvariable) is missing or invalid. Threshold criteria will be based upon all available disk space on the log volume.
Explanation: A Tivoli Storage Manager API error has occurred. System Action: Processing ends. User Response: Try the operation again. Contact your service representative if the error persists. ACD5702E A Domino API error has occured.
Explanation: A Domino API error has occured. System Action: Processing ends. User Response: Try the operation again. Contact your service representative if the error persists. ACD5703E The specified point-in-time is invalid.
Explanation: An attempt to obtain the value of the mentioned Domino environment variable from the notes.ini file failed. System Action: Processing continues with thresholds based upon all available transaction log disk space. 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: The specified point-in-time is invalid. System Action: Processing ends. 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
Explanation: An attempt to obtain the value of the Domino environment variable TRANSLOG_Path from the notes.ini file failed. System Action: Processing ends. 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 the operation again.
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.
768
IBM Tivoli Storage Manager: Messages
ACD5711I ACD5766I
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. 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: The alternate restore path specified by the notes.ini variable TRANSLOG_RECOVER_PATH is 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 Wildcards are not allowed as part of the database name specification:
Explanation: Incremental backup allows only one directory to be backup each time. System Action: Processing continues once either Yes or No is pressed. User Response: User needs to understand how the incremental and selective backup works. ACD5764I Changing this setting (to active only) will refresh the view. All selections will be lost. Do you want to continue?
Explanation: This message displays the incorrect database name specification. System Action: Processing ends. User Response: Re-enter the command with the correct database name specification. ACD5740E Unable to load the IBM Tivoli Storage Manager for Mail DLL, dll_name.
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. ACD5765I Changing this setting (to active/inactive) will refresh the view. All selections will be lost. Do you want to continue?
Explanation: Unable to load the DLL containing the resources for the IBM Tivoli Storage Manager for Mail GUI. System Action: Processing ends. User Response: Ensure that IBM Tivoli Storage Manager for Mail is correctly installed. ACD5741E Error writing option_name preference to the configuration file.
Explanation: The user has selected the Active/Inactive 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. 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?
Explanation: The specified preference could not write 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. ACD5742I The logfile_name log file did not need pruning.
Explanation: The user has selected the refresh toolbar button or pulldown menu item. 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 log file specified did not need to be pruned. System Action: Processing continues. 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.
Chapter 6. Data Protection for Lotus Domino
769
ACD5767I ACD5807W
ACD5767I You have not selected any pending databases to activate. 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: The user pressed the Activate button but has not selected any pending databases to activate. System Action: Processing ends. User Response: Do not press the Activate button until pending databases have been selected for activation. ACD5768I There are no databases pending activation.
Explanation: More than one backup of at least one database has been selected for restore. We will restore the backup with the latest date. System Action: Continues or ends processing as requested. User Response: Press Yes to continue. Press No to terminate the request. ACD5774I Changing the Point in Time setting will cause the tree to be refreshed. All selections will be lost. Do you want to continue?
Explanation: The user has selected the Active button but the list of pending databases is empty. System Action: Processing ends. User Response: None ACD5769I Logs cannot be applied to databases backed up from another Domino server. Do you wish to continue?
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. System Action: Continues or ends processing as requested. User Response: Press Yes to continue or press No to terminate the request. ACD5770I You have not selected any databases to restore.
Explanation: The user has exited the Point in Time dialog by pressing OK. System Action: Continues or ends processing as requested. User Response: Press Yes to continue or press No to terminate the request. ACD5806W The path specified does not contain a notes.ini file. Do you still want to save this?
Explanation: The user has pressed the Restore button but has not selected any databases to restore. System Action: Processing ends. User Response: Do not press the Restore button until databases have been selected to restore. ACD5771I There are no databases to restore.
Explanation: A notes.ini file could not be found in the specified directory path. System Action: Continues or ends processing as requested. User Response: Ensure the correct directory path is specified. ACD5807W The preference has been set successfully, however, the path specified does not currently contain a notes.ini file.
Explanation: The user has selected the Restore button but there are no backed up databases. System Action: Processing ends. User Response: None ACD5772E 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: A notes.ini file could not be found in the specified directory path. System Action: The preference has been set with the specified directory path. User Response: Ensure the correct directory path is specified.
Explanation: More than one database has been selected and the Restore Into specification does not contain an equal sign (=). System Action: Processing ends.
770
IBM Tivoli Storage Manager: Messages
ACD5809I ACD5820I
ACD5809I There are no database backups for the server named servername. User Response: Try the operation again. Contact your service representative if the error persists. ACD5815I You have not selected any databases for Incremental backup.
Explanation: There are no backups on the Tivoli Storage Manager Server for the specified server name. System Action: Processing ends. User Response: None ACD5810I There are no transaction log file archives for the server named servername.
Explanation: The user has pressed the Backup button but has not selected a directory for Incremental backup. System Action: Processing ends. 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: There are no transaction log file archives on the Tivoli Storage Manager Server for the specified server name. System Action: Processing ends. User Response: None ACD5811I There are no database backups matching the filespec filespec and the server name servername.
Explanation: The user cannot select more than one directory at a time for Incremental backup. System Action: Processing ends. 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: There are no database backups on the Tivoli Storage Manager Server for the specified server name. System Action: Processing ends. User Response: None ACD5812I There are no transaction log file archives matching the filespec filespec and the server name servername.
Explanation: An invalid selective backup list was created or found. System Action: Processing ends. User Response: Try the operation again. Contact your service representative if the error persists. ACD5818E Insert to the Backup List failed.
Explanation: There are no database backups on the Tivoli Storage Manager Server for the specified server name. System Action: Processing ends. User Response: None ACD5813I You have not selected any databases for Selective backup.
Explanation: Cannot insert the database to the Backup List. System Action: Processing ends. User Response: Try the operation again. Contact your service representative if the error persists. ACD5819E Invalid Domino server name is selected.
Explanation: The user has pressed the Backup button but has not selected any databases for a Selective backup. System Action: Processing ends. 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 Domino server name is selected. System Action: Processing ends. User Response: Try the operation again. Contact your service representative if the error persists. ACD5820I No transaction log file archives can be found.
Explanation: An invalid incremental backup list was created or found. System Action: Processing ends.
Explanation: There are no transaction log file archives. The transaction log may not have been previously archived. System Action: Processing ends.
Chapter 6. Data Protection for Lotus Domino
771
ACD5821E ACD5986W
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. 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: An invalid date was entered. System Action: The current dialog remains active and the focus is set to the invalid date. User Response: Enter a valid date. 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: The -INTO=filename parameter requires a complete filename. Directory names are not allowed. System Action: Processing ends. 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: More than one archive of at least one log file has been selected for restore. The log file archive with the latest date will be restored. System Action: Continues or ends processing as requested. User Response: Press Yes to continue or press No to terminate the request. ACD5823I A query for the transaction log file archives failed.
Explanation: The dominstall program could not find the symbolic link in /usr/lib directory that points to the TSM API library. System Action: Processing terminates. User Response: Complete the installation of the TSM API, including updating the symbolic link in /usr/lib and rerun the dominstall program. ACD5985E Unable to read the symbolic link linkname. error text.
Explanation: A query of the transaction log file archives failed with an error. System Action: Processing ends. User Response: Try the operation again. Contact your service representative if the error persists. ACD5827E The Restore Into name you entered is too long. Please enter a name no longer than numberofchars.
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. System Action: Processing terminates. User Response: Correct the error in the symbolic link to the TSM API library in /usr/lib and run the dominstall program again. ACD5986W Symbolic link /usr/lib/filename does not point to installed file filename. Check if the TSM API has been properly installed.
Explanation: The specified Restore Into name entered is too long. System Action: Processing ends. User Response: Provide a valid Restore Into name, then try the operation again. 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 symbolic link to the TSM API library does not point to the TSM API library that the dominstall program expects to use. System Action: Processing continues. 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.
Explanation: The Restore Into field requires a complete filename. Directory names are not allowed. System Action: Processing ends. User Response: Provide a valid Restore Into name, then try the operation again.
772
IBM Tivoli Storage Manager: Messages
ACD5987W ACD6002E
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. ACD5997E getpwuid() error for filename.
Explanation: The getpwuid() syscall could not find an entry for the owner of the specified file. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again. ACD5998E Symbolic link linkname points to a directory.
Explanation: The Program Control attribute has not been set for dsmc. System Action: Processing continues. User Response: Set the Program Control attribute for dsmc in order to use the scheduler 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 specified symbolic link points to a directory. This is not a valid symbolic link and should be removed before continuing. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again. ACD5999E Symbolic link linkname points to an unsupported file type.
Explanation: The Program Control attribute has not been set for dsmswitch System Action: Processing continues. User Response: Set the Program Control attribute for dsmswitch in order to use the schduler. ACD5990E Change owner error for filename.
Explanation: The specified symbolic link points to an unsupported file type. This is not a valid symbolic link and should be removed before continuing. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again. ACD6000E Error reading symbolic link linkname.
Explanation: An error occurred while trying to change the owner of a file. System Action: Processing terminates. User Response: Ensure the program has the proper authorization to change the owner of the file, then run the program again. ACD5991E Change permissions error for filename.
Explanation: An attempt to read the contents of the symbolic link failed. System Action: Processing terminates.
Explanation: An error occurred while trying to change the permissions of a file. System Action: Processing terminates. User Response: Ensure the program has the proper authorization to change the permissions of the file, then run the program again. ACD5996E The Application Client installation process did not complete successfully. Please correct the error and run this dominstall program again.
User Response: Correct the error and run the dominstall program again. ACD6001E A zero length symbolic link was encountered for linkname.
Explanation: An attempt to read the contents of the symbolic link failed. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again. ACD6002E Unable to follow symbolic link linkname.
Explanation: The installation program completed unsuccessfully. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again.
Explanation: The symbolic link points to a file that does not exist. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again.
Chapter 6. Data Protection for Lotus Domino
773
ACD6003E ACD6014E
ACD6003E An error was encountered opening directory directory name. ACD6011E Error on lstat to file filename.
Explanation: An attempt to open a directory failed. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again. ACD6005E Error removing file filename.
Explanation: An attempt to obtain file information from the system failed. System Action: Processing terminates. User Response: Correct the error by removing the file, then run the program again. ACD6014E You must run dominstall as a UID 0 user. Switch to a UID 0 user before running this program.
Explanation: An attempt to remove the file failed. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again. ACD6006E Error creating symbolic link linkname to filename.
Explanation: dominstall must be run run as a UID 0 user. System Action: Processing terminates. User Response: Switch to a UID 0 user, then run the program again.
Explanation: An attempt to create a symbolic link failed. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again. ACD6007E A directory exists with the same name as symbolic link to be created. Remove or rename the directory directory name before proceeding.
Explanation: An attempt to create a symbolic link failed. System Action: Processing terminates. User Response: Correct the error and run the dominstall program again. ACD6008I Symbolic link symoblic link to file name already exists.
Explanation: A symlink to the file to be linked already exists. System Action: Processing continues. User Response: None. ACD6010E An unknown file type was encountered when creating symlink linkname.
Explanation: An attempt to create a symbolic link failed. System Action: Processing terminates. User Response: Correct the error by either renaming the file or removing the file, then run the program again.
774
IBM Tivoli Storage Manager: Messages
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 An internal processing error has occurred. ACN0055E Write failure on license file (licensefile).
Explanation: An internal processing error has occurred. System Action: Processing ends. User Response: Retry the operation. If this error persists, contact your service representative. ACN0004E An unknown error has been detected.
Explanation: An attempt to write to the license file failed. System Action: Processing ends. User Response: Make sure enough space exists on the workstation to write to the license file. If enough space exists, run the command again. ACN0056E Data in the license file (licensefile) is not in a valid format.
Explanation: An internal processing error has occurred that prevents the generation of a message for a return code. System Action: Processing continues. User Response: Retry the operation. If this error persists, contact your service representative. ACN0005E Out of memory. Stop other processes and try the operation again.
Explanation: An attempt to read information from the license file failed. System Action: Processing ends. User Response: Install the product again. ACN0057E The checksum in the license file (licensefile) does not match the license string text.
Explanation: The machine has run out of memory. System Action: Processing continues. User Response: Close unnecessary processes and try the operation again. ACN0053E License file (licensefile) could not be opened.
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. System Action: Processing ends. User Response: Reinstall the product. ACN0058E The Try and Buy license has expired.
Explanation: An attempt to read from the license file failed. System Action: Processing ends. User Response: Install the product again. This ensures that the correct license file is installed. ACN0054E Read failure on license file (licensefile).
Explanation: This Try and Buy license that was detected has expired. System Action: Processing ends. User Response: This product is no longer valid for use. A valid license must be obtained before running the product. ACN0100E Incomplete command:
Explanation: An attempt was made to read from the license file. This attempt failed. System Action: Processing ends. User Response: Reinstall the product. This will ensure that the correct license file is installed.
Explanation: This message displays the incomplete command that was entered. System Action: Processing ends. User Response: Re-enter the complete command.
Copyright IBM Corp. 1993, 2004
775
ACN0101E ACN0152I
ACN0101E Invalid argument: ACN0133W Could not locate installation directory. Attempting to continue...
Explanation: This message displays the command that was entered, up to and including the invalid command or option argument that was detected. System Action: Processing ends. User Response: Re-enter the command specifying a valid argument for the command or option. ACN0102E Invalid command:
Explanation: An attempt was made to read the registry to determine where the Tivoli Data Protection application client was installed. This attempt failed. System Action: Processing will continue with the command entered. 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. ACN0134W Could not locate log directory. Processing will continue...
Explanation: This message displays the invalid command that was entered. System Action: Processing ends. User Response: Re-enter a valid command. ACN0103E Invalid option for the specified command:
Explanation: This message displays the command that was entered, up to and including the option that was detected as invalid for the command. System Action: Processing ends. User Response: Re-enter the command specifying valid command options. ACN0104E Invalid option:
Explanation: An attempt was made to read the registry to determine where the Tivoli Data Protection application client log is located. This attempt failed. System Action: Processing will continue with the command entered. 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. ACN0150I Operation canceled by user.
Explanation: This message displays the command that was entered, up to and including the invalid option that was detected. System Action: Processing ends. User Response: Re-enter the command specifying valid command options. ACN0105E Missing argument:
Explanation: The user has requested that the Tivoli Storage Manager application client end by entering ctrl-C. System Action: Processing ends. User Response: None ACN0151E Errors occurred while processing the request.
Explanation: This message displays the command that was entered, up to and including the command or option whose required argument is missing. System Action: Processing ends. User Response: Re-enter the command specifying a valid argument for the command or option. ACN0132W Tracing could not be started. Processing will continue.
Explanation: Attempting to process the request entered, an error occurred. System Action: Processing ends. User Response: Attempt to determine the source of the errors from viewing the log file. Correct the problems and try running the command again. ACN0152I Performance stats: seconds seconds spent in apicall API calls
Explanation: A problem prevented tracing from beginning. System Action: Processing will continue with the command entered. User Response: Refer to the other messages that display with this message to determine the problem.
Explanation: The indicated number of seconds were spent making API calls for the indicated system. System Action: Processing continues. User Response: None
776
IBM Tivoli Storage Manager: Messages
ACN0153I ACN0200E
ACN0153I Performance stats: seconds seconds spent in function ACN0160E An authentication error occurred with your stored Tivoli Storage Manager password.
Explanation: The indicated number of seconds were spent the named function. System Action: Processing continues. User Response: None ACN0154E The Tivoli Storage Manager application client cannot work with the version of the Tivoli Storage Manager API you have installed. Please install version version.release.level or greater.
Explanation: You were unable to log on to the Tivoli Storage Manager server due an authentication error. System Action: Processing stops. User Response: The stored Tivoli Storage Manager password may have become corrupted. Contact your Tivoli Storage Manager server administrator. ACN0161E Authentication error. The password entered is not valid. You are not logged on to the Tivoli Storage Manager server.
Explanation: The version of the Tivoli Storage Manager API currently installed on the system is older than the version used to build the Tivoli Storage Manager application client. System Action: Processing ends. User Response: Install a version of the Tivoli Storage Manager API at or later than the indicated level. A copy is distributed with the Tivoli Storage Manager application client. ACN0155E The Tivoli Storage Manager application client cannot work with the release of Tivoli Storage Manager API you have installed. Please install release version.release.l evel or greater.
Explanation: An incorrect password was entered. System Action: Processing stops. User Response: Enter the correct Tivoli Storage Manager password and try again. ACN0162E The passwords entered do not match. Please enter them again.
Explanation: An incorrect password was entered. System Action: Processing stops. User Response: Enter the passwords again. ACN0163E The directory path needs to be fully-qualified.
Explanation: The release of the Tivoli Storage Manager API currently installed on the system is older than the release used to build the Tivoli Storage Manager application client. System Action: Processing ends. User Response: Install a release of the Tivoli Storage Manager API at or later than the indicated level. A copy is distributed with the Tivoli Storage Manager application client. ACN0156E Could not load the Tivoli Storage Manager API.
Explanation: The /intopath option was specified without a fully-qualified path. System Action: Processing stops. User Response: Enter the command again and specify a fully-qualified path in the /intopath option. ACN0167E The fully-qualified file name is too long.
Explanation: The Tivoli Storage Manager API could not be loaded. System Action: Processing ends. User Response: Ensure the Tivoli Storage Manager API is correctly installed. Run the Tivoli Storage Manager 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.
Explanation: An attempt was made to use a fully-qualified file name that was too long. This attempt failed. System Action: Processing ends. User Response: None ACN0200E File (filename) could not be opened for reading.
Explanation: An attempt was made to open a file for reading. This attempt failed. System Action: Processing ends. User Response: None
Chapter 7. Data Protection for Microsoft Exchange
777
ACN0201E ACN0213E
ACN0201E File (filename) could not be opened for writing. ACN0208E There is not enough disk space for the operation attempted.
Explanation: An attempt was made to open a file for writing. This attempt failed. System Action: Processing ends. User Response: None ACN0202E Read failure on file (filename).
Explanation: An attempted operation required more disk space than was available. The attempt failed. System Action: Processing ends. User Response: None ACN0209E The rename of file (filename1) to (filename2) failed.
Explanation: An attempt was made to read from a file. This attempt failed. System Action: Processing ends. User Response: None ACN0203E Write failure on file (filename).
Explanation: An attempt was made to rename a file. This attempt failed. System Action: Processing ends. User Response: None ACN0210E The Tivoli Storage Manager high level qualifier is too long.
Explanation: An attempt was made to write to a file. This attempt failed. System Action: Processing ends. User Response: None ACN0204E File (filename) could not be closed.
Explanation: An attempt was made to use a Tivoli Storage Manager high level qualifier that was too long. This attempt failed. System Action: Processing ends. User Response: None ACN0211E The Tivoli Storage Manager low level qualifier is too long.
Explanation: An attempt was made to close a file. This attempt failed. System Action: Processing ends. User Response: None ACN0205E File (filename) statistics could not be obtained.
Explanation: An attempt was made to use a Tivoli Storage Manager low level qualifier that was too long. This attempt failed. System Action: Processing ends. User Response: None ACN0212E The Tivoli Storage Manager filespace name is too long.
Explanation: An attempt was made to obtain file statistics. This attempt failed. System Action: Processing ends. User Response: None ACN0206E Directory (directory) could not be created.
Explanation: An attempt was made to use a Tivoli Storage Manager filespace name that was too long. This attempt failed. System Action: Processing ends. User Response: None ACN0213E The maximum number of objects allowed per Tivoli Storage Manager transaction is t oo small.
Explanation: An attempt was made to create a directory. This attempt failed. System Action: Processing ends. User Response: None ACN0207E Directory path (directorypath) is too long.
Explanation: An attempt was made to use a directory path that was too long. This attempt failed. System Action: Processing ends. User Response: None
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 Tivoli Storage Manager application client. System Action: Processing ends.
778
IBM Tivoli Storage Manager: Messages
ACN0214E ACN0259E
User Response: Increase the maximum number of objects allowed per transaction on the Tivoli Storage Manager server and retry the operation. ACN0214E The backup objects management class backup copy group does not exist. ACN0219E The Tivoli Storage Manager low level qualifier is invalid.
Explanation: The low level qualifier name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the low level qualifier name length, characters, and directory delimeters are valid. ACN0256E 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: The Tivoli Storage Manager server has indicated that the backup objects management class backup copy group does not exist. System Action: Processing ends. User Response: Contact your Tivoli Storage Manager server administrator. ACN0215E All backup objects do not have the same management class backup copy destination.
Explanation: In order to maintain backup data integrity, multiple backup objects are sent to the Tivoli 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. System Action: Processing ends. User Response: Contact your Tivoli Storage Manager server administrator. ACN0216E Unable to obtain space information for volume (volumename).
Explanation: Your Tivoli Storage Manager password has expired. You need to change your password. System Action: Processing ends. 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. ACN0257E Your password has expired.
Explanation: Your Tivoli Storage Manager password has expired. A new password needs to be obtained. System Action: Processing ends. User Response: Obtain a new password for your Tivoli Storage Manager node using the change password command or by asking your Tivoli Storage Manager Administrator to change your password. ACN0258E You did not enter a valid password. Processing ends.
Explanation: An attempt was made to obtain space information for a volume. This attempt failed. System Action: Processing ends. User Response: None ACN0217E The Tivoli Storage Manager filespace name is invalid.
Explanation: The filespace name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the filespace name length, characters, and directory delimeters are valid. ACN0218E The Tivoli Storage Manager high level qualifier is invalid.
Explanation: The password that was entered was not a valid password. System Action: Processing ends. User Response: Re-enter the command specifying a valid password. ACN0259E 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 high level qualifier name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the high level qualifier name length, characters, and directory delimeters are valid.
Explanation: The password you entered for verification of your new password does not match the new password that was entered. System Action: Processing ends.
Chapter 7. Data Protection for Microsoft Exchange
779
ACN0260I ACN357E
User Response: Try again to change your password being sure to enter the same password for the new password and for the verification password. ACN0260I Password successfully changed. ACN0266E Could not find the Tivoli Storage Manager HTML books.
Explanation: An attempt was made to read the registry to determine where the Tivoli Storage Manager books were installed. This attempt failed. System Action: Processing ends. User Response: It may be necessary to reinstall the application client code. This will ensure that the registry entries are set up correctly. ACN0267E The verify password entered does not match the new password entered.
Explanation: The change password command completed successfully System Action: Processing ends. User Response: None ACN0261I There are no backups for the server named servername.
Explanation: There are no backups on the Tivoli Storage Manager server for the specified server name. System Action: Processing ends. User Response: None ACN0263E Failed to start Web browser with a return code of returncode.
Explanation: The verify password does not match the new password. System Action: Processing ends. User Response: Retry the command with a matching verify password. ACN0300E Invalid restore type.
Explanation: An attempt was made to start the web browser to view the TSM HTML b ook. This attempt failed. System Action: Processing ends. User Response: Start your web browser manually and point it to bookfrm.htm in the agent htm directory. ACN0264I Could not find the default browser defined. An attempt will be made to use Microsoft Internet Explorer.
Explanation: The type of restore requested is invalid. System Action: Processing ends. User Response: Re-enter the command specifying a valid restore type. ACN0301E Invalid backup type.
Explanation: The type of backup requested is invalid. System Action: Processing ends. User Response: Re-enter the command specifying a valid backup type. ACN351E Invalid trace keyword - keyword
Explanation: An attempt was made to read the registry to determine the default browser. However, a default browser is not defined. A determination will be made where Microsoft Internet Explorer is installed. System Action: Processing continues. 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. ACN0265E Could not find Internet Explorer.
Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect. System Action: Client program did not initialize or tracing was not enabled in the applet. User Response: Correct the value. ACN357E Unable to open trace output file file-name.
Explanation: An attempt was made to read the registry to determine where Microsofts Internet Explorer was installed. This attempt failed. System Action: Processing ends. User Response: Make sure that the registry is set up correctly for Internet Explorer.
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. System Action: Client program did not initialize. User Response: Change the TRACEFILE value so that it is a location to which you have write access.
780
IBM Tivoli Storage Manager: Messages
ACN366E ACN3503I
ACN366E Unable to close trace output file file-name. ACN385E Unable to delete symbolic link link.
Explanation: Log linkname cannot be a symbolic link. System Action: Processing stops. User Response: Delete the symbolic link linkname. ACN476E program-name: cannot open file file-spec: error.
Explanation: An error occurred during the closing of a trace output file-name (for example, not enough disk space). System Action: Processing continues. User Response: Check the options.doc file for a description of possible causes of the error, or see your system administrator. ACN367E Unable to write to trace file tracefile. Tracing disabled.
Explanation: TSM cannot open the file. System Action: TSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ACN3500I Application Client: Starting backup type backup of object name from server server name.
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. ACN368E Invalid trace file name (name too long).
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log when a backup is started. System Action: None User Response: None Centrally logged ACN3501I Application Client: backup type backup of object name from server server name completed successfully. bytes bytes sent in seconds seconds.
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. ACN383E Specifying the trace file link as a symbolic link is not allowed.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log when a backup completes successfully. System Action: None User Response: None Centrally logged ACN3502E Application Client: backup type backup of object name from server server name failed, rc = return code.
Explanation: Trace file linkname cannot be a symbolic link. System Action: The symbolic link linkname is deleted, the trace file is recreated, and processing stops. User Response: Specify the trace file location with the tracefile option. ACN384E Symbolic link linkname to target was successfully deleted.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log when a backup fails. System Action: None User Response: None Centrally logged ACN3503I Application Client: backup type backup of storage group name from server server name was cancelled by the user.
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.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log when a storage group backup was cancelled by the user. System Action: None
Chapter 7. Data Protection for Microsoft Exchange
781
ACN3504I ACN3513E
User Response: None Centrally logged ACN3504I Application Client: Starting restore for server servername. ACN3509I Application Client: backup type restore of storage group storage group name to server server name was cancelled by the user.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the start of a restore. System Action: None User Response: None Centrally logged ACN3505I Application Client: Restore from server servername to servername is complete. Total backups restored: Total bytes transferred: Elapsed processing time: Secs Throughput rate: Kb/Sec
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log when a storage group restore was cancelled by the user. System Action: None User Response: None Centrally logged ACN3510I Application Client: Attempting to inactivate the object: filespace - [filespace name], hl - [high level], ll - [low level]
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the end of a restore. System Action: None User Response: None Centrally logged
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the attempt to inactivate an object. System Action: None User Response: None Centrally logged ACN3511I Application Client: Inactivation of the previous objects succeeded.
ACN3506I
Application Client: Starting backup type restore of storage group storage group name to server server name.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the start of a storage group restore. System Action: None User Response: None Centrally logged ACN3507E Application Client: backup type restore of storage group storage group name to server server name completed successfully.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the success of the inactivation of objects. System Action: None User Response: None Centrally logged ACN3512E Application Client: Inactivation of the previous objects failed.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the failure of the inactivation of objects. System Action: None User Response: None Centrally logged ACN3513E Application Client: Inactivation of the previous objects was canceled.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log when a storage group restore completes successfully. System Action: None User Response: None Centrally logged ACN3508E Application Client: backup type restore of storage group storage group name to server server name failed, rc = return code.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the failure of the inactivation of objects because the task was canceled by the user. System Action: None User Response: None Centrally logged
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log when a storage group restore fails. System Action: None User Response: None Centrally logged
782
IBM Tivoli Storage Manager: Messages
ACN3514I ACN5056I
ACN3514I Application Client: Starting backup for server servername. System Action: Processing continues using default settings. User Response: Ensure that the configuration file exists, and enter the command again. ACN5052E An error occurred trying to set the preference preference.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the start of a backup. System Action: None User Response: None Centrally logged ACN3516I Application Client: Backup of server servername is complete. Total storage groups backed up: Total bytes transferred: Elapsed processing time: Secs Throughput rate: Kb/Sec
Explanation: An error occurred while writing to the preferences file. System Action: Processing ends. User Response: View any other messages that were displayed. Fix any of the problems indicated and enter the command again. ACN5053E 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: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the end of a backup request. System Action: None User Response: None Centrally logged ACN3517E Application Client: Backup of server servername failed, rc = returncode.
Explanation: The preference being set is not valid. System Action: Processing ends. User Response: Run the tdpexcc help set command or see the Users Guide for valid SET command parameters. ACN5054I The preference has been set successfully.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the failure of a backup request. System Action: None User Response: None Centrally logged ACN3518I Application Client: Backup of server servername failed. The request was canceled by the user.
Explanation: The preference was set successfully. System Action: Processing ends. User Response: None ACN5055E The Microsoft Exchange API could not be loaded.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity log indicating the failure of a backup request. The user canceled the backup. System Action: None User Response: None Centrally logged ACN5050I A new configuration file has been created.
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. System Action: Processing ends. User Response: Ensure that the Microsoft Exchange Server has been correctly installed. ACN5056I The logfile log file could not be pruned. Processing will continue.
Explanation: The /configfile value specified a file name that does not exist. A new file has been created. System Action: Processing continues. User Response: None. ACN5051W The configuration file cannot be found, using default settings.
Explanation: An attempt to prune the log was unsuccessful. System Action: Processing continues. 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.
Explanation: The /configfile value specified a file that cannot be found. Default settings will be used.
Chapter 7. Data Protection for Microsoft Exchange
783
ACN5057I ACN5065E
ACN5057I The logfile log file has been pruned successfully. ACN5062E The version of Microsoft Exchange that is running is not a supported version for IBM Tivoli Storage Manager for Mail.
Explanation: The specified log file was pruned successfully. System Action: Processing continues. User Response: None. 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: IBM Tivoli Storage Manager for Mail has detected a version of Microsoft Exchange Server that is not supported. System Action: Processing ends. 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 persists, contact your service representative. ACN5063E 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.
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. 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 The logfile log file cannot be opened for writing. There will be no logging of events.
Explanation: An attempt was made to read the registry to determine the level of Microsoft Exchange that is currently running. This attempt failed. System Action: Processing ends. User Response: Determine if the registry has been corrupted. Also, ensure that the Microsoft Exchange Server is installed on this machine. ACN5064W The service cannot be started when doing a restore.
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. 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. ACN5060E A Tivoli Storage Manager API error has occurred.
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. System Action: Processing ends. 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 Tivoli Storage Manager API api error has occurred. System Action: Processing ends. User Response: Try the operation again. If the error persists, contact your service representative. ACN5061E A Microsoft Exchange api error has occurred.
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. System Action: Processing ends. User Response: Stop the associated services and enter the restore command again.
Explanation: A Microsoft Exchange api error has occurred. System Action: Processing ends. User Response: Try the operation again. If the error persists, contact your service representative.
784
IBM Tivoli Storage Manager: Messages
ACN5066W ACN5076W
ACN5066W The storage group <storagegroup> does not exist. ACN5071W The Information Store is not running. The Information Store will not be backed up.
Explanation: The storage group that was entered that does not exist on the server specified. System Action: Processing ends. 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 Exchange 2003, the databases have not been dismounted.
Explanation: A request was made to backup the Information Store. However, the Information Store needs to be running in order to do the backup. System Action: Processing ends. User Response: Start the Information Store and enter the backup command again. ACN5072W Databases in storage group <storage group> are dismounted -- skipping.
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. System Action: Processing ends. 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: 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.
Explanation: The database that was entered does not exist in the storage group that was entered. System Action: Processing ends. 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: A request was made to backup a set of storage groups. However, each of the storage groups entered has at least one database that is dismounted. System Action: Processing ends. 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.
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 a set of storage groups or databases that do not. The storage group and database names might not have been entered using the correct casing. System Action: Processing ends. 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 was made to backup the Directory service. However, the Directory service needs to be running in order to do the backup. System Action: Processing ends. User Response: Start the Directory service and enter the backup command again.
Explanation: A request to inactivate some previous backup objects failed. System Action: Processing ends. User Response: When the next full backup of the
Chapter 7. Data Protection for Microsoft Exchange
785
ACN5083I ACN5237E
database is run, another attempt will be made to inactivate the failed objects. ACN5083I All of the storage groups entered have been excluded. ACN5140I Storage Group <storagegroup> does not exist - skipping.
Explanation: The storage group that was specified by the user is not found on this Exchange server. 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: 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. System Action: Processing ends. 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: 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: 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: The storage groups or databases could not be found on this Microsoft Exchange server. System Action: Processing ends. User Response: Ensure that the storage group or database names are spelled correctly and enter the command again. ACN5209I There are no backups matching the server name servername and the following filespecs:filespecs.
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. System Action: Processing ends. User Response: Enter the command specifying a storage group or dbname that exists. ACN5087E 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 -TSMPassword=xxx option will set and store your password.
Explanation: There are no database backups on the Tivoli Storage Manager server for the specified server name. System Action: Processing ends. User Response: None ACN5237E Unable to communicate with the Microsoft Exchange Server.
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. System Action: Processing ends. User Response: Invoke the command again using the -TSMPassword option. Any subsequent commands should then complete without specifying a password.
Explanation: An attempt was made to communicate the with the Microsoft Exchange Server that was entered. This attempt failed. System Action: Processing ends. 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.
786
IBM Tivoli Storage Manager: Messages
ACN5238E ACN5350E
ACN5238E Unable to retrieve the domain information for the Microsoft Exchange Server. ACN5302E Unable to get the value for the Site from the registry.
Explanation: An attempt was made to retrieve the domain information for the Microsoft Exchange Server. This attempt failed. System Action: Processing ends. User Response: Ensure that the Microsoft Exchange server is running. ACN5239E Unable to retrieve the storage group information.
Explanation: An attempt was made to read the registry to determine the site for the Microsoft Exchange Server. This attempt failed. System Action: Processing ends. User Response: Determine if there is a problem with the registry or ensure that the Microsoft Exchange Server is installed properly. ACN5303E Unable to get the value for Circular Logging from the registry.
Explanation: An attempt was made to retrieve the storage group information for the Microsoft Exchange Server. This attempt failed. System Action: Processing ends. User Response: Ensure that the Microsoft Exchange Server is running properly. ACN5240E Unable to retrieve the database information.
Explanation: An attempt was made to read the registry to determine the Circular Logging setting for either the IS or the DIR of the Microsoft Exchange Server. This attempt failed. System Action: Processing ends. User Response: Determine if there is a problem with the registry or ensure that the Microsoft Exchange Server is installed properly. ACN5304E Unable to open service to determine if running or not.
Explanation: An attempt was made to retrieve the database information for the storage group of the Microsoft Exchange Server. This attempt failed. System Action: Processing ends. User Response: Ensure that the Microsoft Exchange Server is running properly. ACN5241E The Microsoft Exchange Information Store is currently not running.
Explanation: An attempt to open a service failed. System Action: Processing ends. User Response: Determine if there is a problem with the Microsoft Exchange server. ACN5305E Unable to query service information.
Explanation: An attempt was made to retrieve the Microsoft Exchange Server information. This attempt failed. System Action: Processing ends. 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. ACN5301E Unable to get the value for the Organization from the registry.
Explanation: An attempt to query specific service information failed. System Action: Processing ends. User Response: Determine if there is a problem with 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. System Action: Processing ends. 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, contact your service representative.
Explanation: An attempt was made to read the registry to determine the organization for the Microsoft Exchange Server. This attempt failed. System Action: Processing ends. User Response: Determine if there is a problem with the registry or ensure that the Microsoft Exchange Server is installed properly.
Chapter 7. Data Protection for Microsoft Exchange
787
ACN5351E ACN5360E
ACN5351E The Exchange server application is not registered for backup. ACN5356E The database file name is undefined.
Explanation: The Exchange server application must be registered for backup with the Windows Server. The Windows NT event log may contain more information. System Action: Processing ends. 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, contact your service representative. ACN5352E The Exchange server application is not registered for offline restore.
Explanation: Every Microsoft Exchange database must specify a database file name. System Action: Processing ends. User Response: Verify the database properties and retry the operation. If the error persists, contact your service representative. ACN5357W The truncation of the transaction log failed.
Explanation: The truncation of the transaction log failed. System Action: Processing continues. User Response: Refer to other messages that are displayed to determine the problem. ACN5358E A Microsoft Exchange API protocol error has occurred.
Explanation: The Exchange server application must be registered for offline restore with the Windows Server. The Windows NT event log may contain more information. System Action: Processing ends. 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, contact your service representative. ACN5353E The Exchange server application is not registered for online restore.
Explanation: An unrecoverable Microsoft Exchange API protocol error has occurred. System Action: Processing ends. User Response: Contact your service representative. ACN5359E An attempt was made to get the TEMP environment variable. This attempt failed.
Explanation: The Exchange server application must be registered for online restore with the Windows Server. The Windows NT event log may contain more information. System Action: Processing ends. 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, contact your service representative. ACN5354E The storage group was not found.
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. System Action: Processing ends. 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: The specified storage group name was not found. System Action: Processing ends. 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: A partial storage group restore was requested with the /ERASEexistingdata option. The /ERASEexistingdata option is not allowed during a partial restore. System Action: Processing ends.
Explanation: The specified database name was not found. System Action: Processing ends. User Response: Verify the command input and retry the operation. If the error persists, contact your service representative.
User Response: Enter the command to restore the entire storage group or enter the command without the /ERASEexistingdata option.
788
IBM Tivoli Storage Manager: Messages
ACN5361E ACN5741I
ACN5361E It is invalid to have an * within a storage group name. ACN5706I The logfile_name log file did not need pruning.
Explanation: An attempt was made to backup a storage group that contains an *. It is invalid to have an * in a storage group name. System Action: Processing continues, but this storage group will not be backed up. User Response: Rename the storage group, otherwise this storage group cannot be backed up. ACN5362W The filespace <filespace> in an invalid filespace name.
Explanation: The log file specified did not need to be pruned. System Action: Processing continues. User Response: The log file will automatically be pruned at a later date. If the log file is too large now, lower the number of days the log entries are retained. ACN5707W 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. 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. ACN5500E The MultiByteToWideChar() function failed.
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 without logging and without pruning. 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. ACN5724I No databases have been selected for backup.
Explanation: An internal error occurred. System Action: Processing ends. User Response: Retry the operation. If this error persists, contact your service representative. ACN5501E The WideCharToMultiByte() function failed.
Explanation: The Backup button was pressed but no databases have been selected in the list in the graphical user interface. System Action: Processing stops. User Response: Select a database and press the Backup button. ACN5725I No Storage Groups have been selected for backup.
Explanation: An internal error occurred. System Action: Processing ends. User Response: Retry the operation. If this error persists, contact your service representative. ACN5705W 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: The Backup button was pressed but no Storage Groups have been selected in the tree or list in the graphical user interface. System Action: Processing stops. User Response: Select a Storage Group and press the Backup button. ACN5741I No Backups have been selected for restore.
Explanation: An attempt was made to run setup for the Tivoli Storage Manager API. However, errors were encountered. System Action: Processing continues. User Response: Examine the dsierror.log file to 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.
Explanation: The Restore button was pressed but nothing was selected in the tree or list view. System Action: Processing stops. User Response: Make a selection in the tree or list view and press the Restore button again.
Chapter 7. Data Protection for Microsoft Exchange
789
ACN5758W ACN5803W
ACN5758W At least one of the databases services that is selected for restore is running. Do you want to stop the service(s)? ACN5802W 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. 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?
Explanation: A service that you are trying to restore is running. The service cannot be running in order to perform the restore. 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)? ACN5803W
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. System Action: None. User Response: Press OK to continue the restore or press cancel to stop. 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. System Action: Processing ends. 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, contact your service representative. ACN5800E Backup is corrupt. See log file for additional information.
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. System Action: Processing ends. User Response: Retry the operation. If the error persists, contact your service representative.
790
IBM Tivoli Storage Manager: Messages
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 An internal processing error has occurred. ACO0055E Write failure on license file (licensefile).
Explanation: An internal processing error has occurred. System Action: Processing ends. User Response: Retry the operation. If this error persists, contact your service representative. ACO0004E An unknown error has been detected.
Explanation: An attempt to write to the license file failed. System Action: Processing ends. User Response: Make sure enough space exists on the workstation to write to the license file. If enough space exists, run the command again. ACO0056E Data in the license file (licensefile) is not in a valid format.
Explanation: An internal processing error has occurred that prevents the generation of a message for a return code. System Action: Processing continues. User Response: Retry the operation. If this error persists, contact your service representative. ACO0005E Out of memory. Stop other processes and try the operation again.
Explanation: An attempt to read information from the license file failed. System Action: Processing ends. User Response: Install the product again. ACO0057E The checksum in the license file (licensefile) does not match the license string text.
Explanation: The machine has run out of memory. System Action: Processing continues. User Response: Close unnecessary processes and try the operation again. ACO0053E License file (licensefile) could not be opened.
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. System Action: Processing ends. User Response: Reinstall the product. ACO0058E The Try and Buy license has expired.
Explanation: An attempt to read from the license file failed. System Action: Processing ends. User Response: Install the product again. This ensures that the correct license file is installed. ACO0054E Read failure on license file (licensefile).
Explanation: This Try and Buy license that was detected has expired. System Action: Processing ends. User Response: This product is no longer valid for use. A valid license must be obtained before running the product. ACO0100E Incomplete command:
Explanation: An attempt was made to read from the license file. This attempt failed. System Action: Processing ends. User Response: Reinstall the product. This will ensure that the correct license file is installed.
Explanation: This message displays the incomplete command that was entered. System Action: Processing ends. User Response: Re-enter the complete command.
Copyright IBM Corp. 1993, 2004
791
ACO0101E ACO0152I
ACO0101E Invalid argument: ACO0133W Could not locate installation directory. Attempting to continue...
Explanation: This message displays the command that was entered, up to and including the invalid command or option argument that was detected. System Action: Processing ends. User Response: Re-enter the command specifying a valid argument for the command or option. ACO0102E Invalid command:
Explanation: An attempt was made to read the registry to determine where the Tivoli Data Protection application client was installed. This attempt failed. System Action: Processing will continue with the command entered. 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. ACO0134W Could not locate log directory. Processing will continue...
Explanation: This message displays the invalid command that was entered. System Action: Processing ends. User Response: Re-enter a valid command. ACO0103E Invalid option for the specified command:
Explanation: This message displays the command that was entered, up to and including the option that was detected as invalid for the command. System Action: Processing ends. User Response: Re-enter the command specifying valid command options. ACO0104E Invalid option:
Explanation: An attempt was made to read the registry to determine where the Tivoli Data Protection application client log is located. This attempt failed. System Action: Processing will continue with the command entered. 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. ACO0150I Operation canceled by user.
Explanation: This message displays the command that was entered, up to and including the invalid option that was detected. System Action: Processing ends. User Response: Re-enter the command specifying valid command options. ACO0105E Missing argument:
Explanation: The user has requested that the Tivoli Storage Manager application client end by entering ctrl-C. System Action: Processing ends. User Response: None ACO0151E Errors occurred while processing the request.
Explanation: This message displays the command that was entered, up to and including the command or option whose required argument is missing. System Action: Processing ends. User Response: Re-enter the command specifying a valid argument for the command or option. ACO0132W Tracing could not be started. Processing will continue.
Explanation: Attempting to process the request entered, an error occurred. System Action: Processing ends. User Response: Attempt to determine the source of the errors from viewing the log file. Correct the problems and try running the command again. ACO0152I Performance stats: seconds seconds spent in apicall API calls
Explanation: A problem prevented tracing from beginning. System Action: Processing will continue with the command entered. User Response: Refer to the other messages that display with this message to determine the problem.
Explanation: The indicated number of seconds were spent making API calls for the indicated system. System Action: Processing continues. User Response: None
792
IBM Tivoli Storage Manager: Messages
ACO0153I ACO0200E
ACO0153I Performance stats: seconds seconds spent in function ACO0160E An authentication error occurred with your stored Tivoli Storage Manager password.
Explanation: The indicated number of seconds were spent the named function. System Action: Processing continues. User Response: None ACO0154E The Tivoli Storage Manager application client cannot work with the version of the Tivoli Storage Manager API you have installed. Please install version version.release.level or greater.
Explanation: You were unable to log on to the Tivoli Storage Manager server due an authentication error. System Action: Processing stops. User Response: The stored Tivoli Storage Manager password may have become corrupted. Contact your Tivoli Storage Manager server administrator. ACO0161E Authentication error. The password entered is not valid. You are not logged on to the Tivoli Storage Manager server.
Explanation: The version of the Tivoli Storage Manager API currently installed on the system is older than the version used to build the Tivoli Storage Manager application client. System Action: Processing ends. User Response: Install a version of the Tivoli Storage Manager API at or later than the indicated level. A copy is distributed with the Tivoli Storage Manager application client. ACO0155E The Tivoli Storage Manager application client cannot work with the release of Tivoli Storage Manager API you have installed. Please install release version.release.l evel or greater.
Explanation: An incorrect password was entered. System Action: Processing stops. User Response: Enter the correct Tivoli Storage Manager password and try again. ACO0162E The passwords entered do not match. Please enter them again.
Explanation: An incorrect password was entered. System Action: Processing stops. User Response: Enter the passwords again. ACO0163E The directory path needs to be fully-qualified.
Explanation: The release of the Tivoli Storage Manager API currently installed on the system is older than the release used to build the Tivoli Storage Manager application client. System Action: Processing ends. User Response: Install a release of the Tivoli Storage Manager API at or later than the indicated level. A copy is distributed with the Tivoli Storage Manager application client. ACO0156E Could not load the Tivoli Storage Manager API.
Explanation: The /intopath option was specified without a fully-qualified path. System Action: Processing stops. User Response: Enter the command again and specify a fully-qualified path in the /intopath option. ACO0167E The fully-qualified file name is too long.
Explanation: The Tivoli Storage Manager API could not be loaded. System Action: Processing ends. User Response: Ensure the Tivoli Storage Manager API is correctly installed. Run the Tivoli Storage Manager 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.
Explanation: An attempt was made to use a fully-qualified file name that was too long. This attempt failed. System Action: Processing ends. User Response: None ACO0200E File (filename) could not be opened for reading.
Explanation: An attempt was made to open a file for reading. This attempt failed. System Action: Processing ends. User Response: None
Chapter 8. Data Protection for Microsoft SQL
793
ACO0201E ACO0213E
ACO0201E File (filename) could not be opened for writing. ACO0208E There is not enough disk space for the operation attempted.
Explanation: An attempt was made to open a file for writing. This attempt failed. System Action: Processing ends. User Response: None ACO0202E Read failure on file (filename).
Explanation: An attempted operation required more disk space than was available. The attempt failed. System Action: Processing ends. User Response: None ACO0209E The rename of file (filename1) to (filename2) failed.
Explanation: An attempt was made to read from a file. This attempt failed. System Action: Processing ends. User Response: None ACO0203E Write failure on file (filename).
Explanation: An attempt was made to rename a file. This attempt failed. System Action: Processing ends. User Response: None ACO0210E The Tivoli Storage Manager high level qualifier is too long.
Explanation: An attempt was made to write to a file. This attempt failed. System Action: Processing ends. User Response: None ACO0204E File (filename) could not be closed.
Explanation: An attempt was made to use a Tivoli Storage Manager high level qualifier that was too long. This attempt failed. System Action: Processing ends. User Response: None ACO0211E The Tivoli Storage Manager low level qualifier is too long.
Explanation: An attempt was made to close a file. This attempt failed. System Action: Processing ends. User Response: None ACO0205E File (filename) statistics could not be obtained.
Explanation: An attempt was made to use a Tivoli Storage Manager low level qualifier that was too long. This attempt failed. System Action: Processing ends. User Response: None ACO0212E The Tivoli Storage Manager filespace name is too long.
Explanation: An attempt was made to obtain file statistics. This attempt failed. System Action: Processing ends. User Response: None ACO0206E Directory (directory) could not be created.
Explanation: An attempt was made to use a Tivoli Storage Manager filespace name that was too long. This attempt failed. System Action: Processing ends. User Response: None ACO0213E The maximum number of objects allowed per Tivoli Storage Manager transaction is t oo small.
Explanation: An attempt was made to create a directory. This attempt failed. System Action: Processing ends. User Response: None ACO0207E Directory path (directorypath) is too long.
Explanation: An attempt was made to use a directory path that was too long. This attempt failed. System Action: Processing ends. User Response: None
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 Tivoli Storage Manager application client. System Action: Processing ends.
794
IBM Tivoli Storage Manager: Messages
ACO0214E ACO0259E
User Response: Increase the maximum number of objects allowed per transaction on the Tivoli Storage Manager server and retry the operation. ACO0214E The backup objects management class backup copy group does not exist. ACO0219E The Tivoli Storage Manager low level qualifier is invalid.
Explanation: The low level qualifier name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the low level qualifier name length, characters, and directory delimeters are valid. ACO0256E 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: The Tivoli Storage Manager server has indicated that the backup objects management class backup copy group does not exist. System Action: Processing ends. User Response: Contact your Tivoli Storage Manager server administrator. ACO0215E All backup objects do not have the same management class backup copy destination.
Explanation: In order to maintain backup data integrity, multiple backup objects are sent to the Tivoli 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. System Action: Processing ends. User Response: Contact your Tivoli Storage Manager server administrator. ACO0216E Unable to obtain space information for volume (volumename).
Explanation: Your Tivoli Storage Manager password has expired. You need to change your password. System Action: Processing ends. 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. ACO0257E Your password has expired.
Explanation: Your Tivoli Storage Manager password has expired. A new password needs to be obtained. System Action: Processing ends. User Response: Obtain a new password for your Tivoli Storage Manager node using the change password command or by asking your Tivoli Storage Manager Administrator to change your password. ACO0258E You did not enter a valid password. Processing ends.
Explanation: An attempt was made to obtain space information for a volume. This attempt failed. System Action: Processing ends. User Response: None ACO0217E The Tivoli Storage Manager filespace name is invalid.
Explanation: The filespace name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the filespace name length, characters, and directory delimeters are valid. ACO0218E The Tivoli Storage Manager high level qualifier is invalid.
Explanation: The password that was entered was not a valid password. System Action: Processing ends. User Response: Re-enter the command specifying a valid password. ACO0259E 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 high level qualifier name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the high level qualifier name length, characters, and directory delimeters are valid.
Explanation: The password you entered for verification of your new password does not match the new password that was entered. System Action: Processing ends.
Chapter 8. Data Protection for Microsoft SQL
795
ACO0260I ACO357E
User Response: Try again to change your password being sure to enter the same password for the new password and for the verification password. ACO0260I Password successfully changed. ACO0266E Could not find the Tivoli Storage Manager HTML books.
Explanation: An attempt was made to read the registry to determine where the Tivoli Storage Manager books were installed. This attempt failed. System Action: Processing ends. User Response: It may be necessary to reinstall the application client code. This will ensure that the registry entries are set up correctly. ACO0267E The verify password entered does not match the new password entered.
Explanation: The change password command completed successfully System Action: Processing ends. User Response: None ACO0261I There are no backups for the server named servername.
Explanation: There are no backups on the Tivoli Storage Manager server for the specified server name. System Action: Processing ends. User Response: None ACO0263E Failed to start Web browser with a return code of returncode.
Explanation: The verify password does not match the new password. System Action: Processing ends. User Response: Retry the command with a matching verify password. ACO0300E Invalid restore type.
Explanation: An attempt was made to start the web browser to view the TSM HTML b ook. This attempt failed. System Action: Processing ends. User Response: Start your web browser manually and point it to bookfrm.htm in the agent htm directory. ACO0264I Could not find the default browser defined. An attempt will be made to use Microsoft Internet Explorer.
Explanation: The type of restore requested is invalid. System Action: Processing ends. User Response: Re-enter the command specifying a valid restore type. ACO0301E Invalid backup type.
Explanation: The type of backup requested is invalid. System Action: Processing ends. User Response: Re-enter the command specifying a valid backup type. ACO351E Invalid trace keyword - keyword
Explanation: An attempt was made to read the registry to determine the default browser. However, a default browser is not defined. A determination will be made where Microsoft Internet Explorer is installed. System Action: Processing continues. 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. ACO0265E Could not find Internet Explorer.
Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect. System Action: Client program did not initialize or tracing was not enabled in the applet. User Response: Correct the value. ACO357E Unable to open trace output file file-name.
Explanation: An attempt was made to read the registry to determine where Microsofts Internet Explorer was installed. This attempt failed. System Action: Processing ends. User Response: Make sure that the registry is set up correctly for Internet Explorer.
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. System Action: Client program did not initialize. User Response: Change the TRACEFILE value so that it is a location to which you have write access.
796
IBM Tivoli Storage Manager: Messages
ACO366E ACO3003I
ACO366E Unable to close trace output file file-name. ACO385E Unable to delete symbolic link link.
Explanation: Log linkname cannot be a symbolic link. System Action: Processing stops. User Response: Delete the symbolic link linkname. ACO476E program-name: cannot open file file-spec: error.
Explanation: An error occurred during the closing of a trace output file-name (for example, not enough disk space). System Action: Processing continues. User Response: Check the options.doc file for a description of possible causes of the error, or see your system administrator. ACO367E Unable to write to trace file tracefile. Tracing disabled.
Explanation: TSM cannot open the file. System Action: TSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ACO3000I Application Client: Starting backup type backup of database database name from server server name.
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. ACO368E Invalid trace file name (name too long).
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log when a backup is started. System Action: None User Response: None Centrally logged ACO3001I Application Client: backup type backup of database database name from server server name completed successfully.
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. ACO383E Specifying the trace file link as a symbolic link is not allowed.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log when a database backup completes successfully. System Action: None User Response: None Centrally logged ACO3002E Application Client: backup type backup of database database name from server server name failed, rc = return code.
Explanation: Trace file linkname cannot be a symbolic link. System Action: The symbolic link linkname is deleted, the trace file is recreated, and processing stops. User Response: Specify the trace file location with the tracefile option. ACO384E Symbolic link linkname to target was successfully deleted.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log when a database restore fails. System Action: None User Response: None Centrally logged ACO3003I Application Client: Starting restore type restore of backup object object name to database database name on server server name.
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.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log when a restore is started. System Action: None
Chapter 8. Data Protection for Microsoft SQL
797
ACO3004I ACO3011I
User Response: None Centrally logged ACO3004I Application Client: restore type restore of backup object object name to database database name on server server name completed successfully. ACO3008I Application Client: 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 transferred: bytes Elapsed processing time: time Secs
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log when a database restore completes successfully. System Action: None User Response: None Centrally logged ACO3005E Application Client: restore type restore of backup object object name to database database name on server server name failed.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log indicating the end of a backup request. System Action: None User Response: None Centrally logged ACO3009I Application Client: backup type backup of database database name from server server name canceled by user.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log when a database restore fails. System Action: None User Response: None Centrally logged ACO3006I Application Client: Starting backup for server server name.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log indicating that a backup request was canceled by the user. System Action: None User Response: None Centrally logged ACO3010I Application Client: Starting restore for server servername.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log indicating the start of a backup. System Action: None User Response: None Centrally logged ACO3007I Application Client: 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
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log indicating the start of a restore. System Action: None User Response: None Centrally logged ACO3011I Application Client: 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
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log indicating the end of a backup request. System Action: None User Response: None Centrally logged
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log indicating the end of a restore. System Action: None User Response: None Centrally logged
798
IBM Tivoli Storage Manager: Messages
ACO3012I ACO5057I
ACO3012I Application Client: restore type restore of backup object object name to database database name from server server name canceled by user. ACO5051I The configuration file cannot be found, using default settings.
Explanation: The file specififed in the /configfile parameter cannot be found. System Action: Processing continues. User Response: Ensure the correct file name is specified. ACO5052E An error occurred trying to set the requested configuration option.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log indicating that a backup request was canceled by the user. System Action: None User Response: None Centrally logged ACO3013I Application Client: Starting Inactivate processing for backup objects from server servername
Explanation: An error occurred while writing to the configuration file. System Action: Processing ends. User Response: View any other messages that were displayed. After reviewing the messages and performing necessary actions, run the command again. 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: This is an informational message written to the Tivoli Storage Manager Server activity log when an inactivate process begins. System Action: None User Response: None Centrally logged ACO3014I Application Client: 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
Explanation: The configuration option being set is not valid. System Action: Processing ends. User Response: Run TDPSQLC Help Set or refer to the Users Guide for valid Set command parameters. ACO5054I The configuration option was set successfully.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log to indicate the end of an inactivate command. System Action: None User Response: None ACO3015I Application Client: Inactivating backup type backup backup object.
Explanation: The configuration option specified on the Set command was set successfully. System Action: Processing ends. User Response: None ACO5056I The logfile log file could not be pruned. Processing will continue.
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log when an inactivation of a backup object is started. System Action: None User Response: None Centrally logged ACO5050I A new configuration file was created.
Explanation: An attempt to prune the log was unsuccessful. System Action: Processing continues. User Response: The log file may not exist. If the log file exists, view the log for indications of possible problems. ACO5057I The logfile log file was pruned successfully.
Explanation: The file specified in the /configfile parameter does not exist. A new file was created. System Action: Processing continues. User Response: None.
Explanation: The log file mentioned pruned successfully. System Action: Processing continues.
Chapter 8. Data Protection for Microsoft SQL
799
ACO5058W ACO5400E
User Response: None. ACO5058W The logfile name is greater than the maximum allowed. Processing will continue using a logfile name of logfile in the current directory. ACO5064W 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 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 The logfile log file cannot be opened for writing. There will be no logging of events.
Explanation: The log mentioned could not be opened for appends. Therefore, no logging or pruning is performed. System Action: Processing continues without logging and without pruning. User Response: Determine why the log file could not be opened. The log file may refer to a non-existent drive or partition, or the log file is marked read-only. ACO5065E The value specified for the /SQLUSer option does not match the registry entry.
Explanation: The log mentioned could not be opened for appends. Therefore, no logging is performed. System Action: Processing continues without logging. User Response: Determine why the log file could not be opened. The log file may refer to a non-existent drive or partition, or the log file is marked read-only. ACO5060E A Tivoli Storage Manager API error has occurred.
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. System Action: Processing ends. 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 PASSWORDACCESS is Generate. Either the stored password is incorrect or there is no stored password. If you do not have a stored password, use the -TSMPassword=xxx option to set and store your password.
Explanation: A Tivoli Storage Manager API error has occurred. System Action: Processing ends. User Response: Retry the operation. If the error persists, contact your service representative. ACO5061E A Microsoft SQL API error has occurred.
Explanation: A Microsoft SQL API error occurred. System Action: Processing ends. User Response: Retry the operation. If the error persists, contact your service representative. ACO5063I The logfile_name log file did not need pruning.
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. System Action: Processing ends. User Response: Invoke the command again using the -TSMPassword option. Any subsequent commands should now complete without specifying a password. ACO5400E The Virtual Device Interface is not registered with the Common Object Model.
Explanation: The log file specified did not need to be pruned. System Action: Processing continues. User Response: The log file will automatically be pruned at a later date. If the log file is currently too large, decrease the number of days the log entries are retained.
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. System Action: Processing ends. User Response: Verify that the SQL server is installed
800
IBM Tivoli Storage Manager: Messages
ACO5401E ACO5422E
properly and retry the operation. Contact your service representative if the error persists. ACO5401E The Virtual Device Interface could not be created. Windows NT event log may contain more information. System Action: Processing ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5406E The SQL server closed a virtual device prematurely.
Explanation: The virtual device interface could not be created. The SQL server virtual device interface log or Windows NT event log may contain more information. System Action: Processing ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5402E The Virtual Device Set could not be created.
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. System Action: Processing ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5407E The SQL server aborted the operation.
Explanation: The virtual device set could not be created. The SQL server virtual device interface log or Windows NT event log may contain more information. System Action: Processing ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5403E The configuration of the Virtual Device Set could not be obtained.
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. System Action: Processing ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5420E Explanation: A SQL API error has occurred. System Action: Processing for this operation ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5421E Received the following from the MS COM component: SQL message
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. System Action: Processing ends. User Response: If the SQL server messages do not help resolve the problem retry the operation. If the error persists, contact your service representative. 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 Windows NT event log may contain more information. System Action: Processing ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5405E An unknown virtual device error has been detected.
Explanation: A SQL error has occurred. System Action: Processing for this operation ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5422E Received the following from the MS SQL server: SQL message
Explanation: A SQL error has occurred. System Action: Processing for this operation ends. User Response: If the SQL server messages do not
Chapter 8. Data Protection for Microsoft SQL
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
801
ACO5423E ACO5432E
resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5423E The following string is too long: string ACO5428E The SQL server is not on the local machine: SQL message
Explanation: A SQL error has occurred. System Action: Processing for this operation ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5424E Could not connect to SQL server; SQL server returned: SQL message
Explanation: An attempt was made to use the application client specifying a SQL server that was not on the local machine. System Action: Processing for this operation ends. User Response: Retry the operation on the machine where the SQL server resides. ACO5429E Could not obtain an event from SQL server: SQL message
Explanation: A SQL error has occurred. System Action: Processing for this operation ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5430E The SQL Server Name is blank or NULL.
Explanation: A SQL error has occurred. System Action: Processing for this operation ends. User Response: If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists. ACO5425E The SQL server is not running: SQL message
Explanation: A SQL error has occurred. System Action: Processing for this operation ends. User Response: Start the SQL server and retry the operation. ACO5426E The SQL log on does not have the Sysadmin role: SQL message
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 attempt was made to logon to the SQL server but the specified logon name does not have the Sysadmin role. System Action: Processing for this operation ends. 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 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. System Action: Processing ends. User Response: Enter the command again with a valid value in the positional parameter or option. ACO5432E Equal numbers of the /RELOCATE and /TO options must be specified.
Explanation: An attempt was made to use Application Client Server V2 with a SQL server version earlier than the version 7.0 level. This is not allowed. System Action: Processing for this operation ends. User Response: Use the Application Client 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.
Explanation: Unequal numbers of the /RELOCATE and /TO options were specified on a RESTORE command. System Action: Processing ends. User Response: Re-enter the command specifying the same number of /RELOCATE and /TO options.
802
IBM Tivoli Storage Manager: Messages
ACO5433E ACO5454E
ACO5433E Wildcards are not allowed as part of the following parameters/options: 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: This message displays the positional parameters and/or options that were specified incorrectly. System Action: Processing ends. User Response: Re-enter the command specifying the correct parameters and/or options. ACO5434E The following options cannot be specified together:
Explanation: When a backup fails, the TSM 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. System Action: Processing continues. User Response: None. A backup of the database should detect the temporary backup data object and delete it from the TSM server. ACO5453E 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: This message displays the conflicting command options that were entered. System Action: Processing ends. User Response: Re-enter the command specifying valid command options. ACO5435E This command requires one of the following options:
Explanation: This message displays the options that were missing from the command entered. System Action: Processing ends. 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: 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. User Response: Try the operation again. Contact your service representative if this error persists. ACO5454E The maximum number of objects 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: A failure occurred on the numbered stripe. System Action: Processing ends. User Response: There should be other messages along with this one. Refer to the other messages to determine 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: 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).
Explanation: A failure occurred on the named virtual device. System Action: Processing ends.
Chapter 8. Data Protection for Microsoft SQL
803
ACO5455E ACO5552I
ACO5455E The backup is corrupt and can not be restored. ACO5500E The MultiByteToWideChar() function failed.
Explanation: The backup being restored is corrupt because the data object or objects found do not correspond to the metadata. System Action: Processing ends. User Response: Try the operation again. Contact your service representative if the error persists. ACO5456W The backup is corrupt and is not fully restorable. Processing will continue.
Explanation: This is an internal error that indicates corrupted storage. System Action: Processing for this database ends. User Response: Try the operation again. Contact your service representative if this error persists. ACO5501E The Common Object Model (COM) library failed to initialize.
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. System Action: Processing continues. User Response: Try the operation again. Contact your service representative if the error persists. ACO5457E An unknown SQL API error has occurred.
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 There are no backups matching the filespec directorypathfilename and the server name servername.
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. System Action: Processing ends. User Response: If the SQL server messages do not 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: There are no database backups on the Tivoli Storage Manager server for the specified server name. System Action: Processing ends. User Response: None ACO5551I There are no backups matching the criteria specified for server name servername.
Explanation: There are no database backups on the Tivoli Storage Manager server matching the query criteria for the specified server name. System Action: Processing ends. User Response: Specify a broader range of search criteria when issuing this query. ACO5552I No matches were found for the criteria specified.
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. System Action: Processing continues. 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.
Explanation: The SQL Server was searched for databases that matched the specified criteria. System Action: Processing ends. User Response: Check the specified search criteria (database name, group name, logical filename). Enter the command again.
804
IBM Tivoli Storage Manager: Messages
ACO5715E ACO5784E
ACO5715E Error writing option_name preference to the configuration file. TSM server or all active backups were inactivated. ACO5720I No databases have been selected for backup.
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. ACO5716W 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: The Backup button was pressed on the GUI but no databases were selected from the tree or list. System Action: Processing stops. User Response: Select a database and press the Backup button again. ACO5721I No backups have been selected for restore.
Explanation: Errors were encountered during an attempt to run setup for the Tivoli Storage Manager API. System Action: Processing continues. User Response: Examine the dsierror.log file to 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: The restore button was pressed on the GUI but no backup objects were selected from the tree or list. System Action: Processing stops. 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. System Action: Processing stops. User Response: Select a backup object and press the Inactivate button again. ACO5723E A named mark must be specified.
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 Stop At Mark or Stop Before Mark option was chosen but the named mark was not specified. System Action: Processing stops. User Response: Enter a named mark or choose the Stop At option. ACO5784E A log must be selected to use point in time.
Explanation: The refresh toolbar button or pulldown menu item has been selected. System Action: Processing continues. User Response: Select Yes to refresh the view or select No to leave the current view unchanged. ACO5719I There are currently no backups on TSM.
Explanation: A log must be selected before setting point in time parameters. System Action: Processing stops. User Response: Select at least one log for restore before specifying a point in time.
Explanation: The SQL server name expansion button was pressed on the Inactivate page. System Action: Processing stops. User Response: Either nothing was backed up to a
Chapter 8. Data Protection for Microsoft SQL
805
ACO5804I ACO5805W
ACO5804I Unable to get information. If data is backed up to tape check the Wait for Tape Mounts for File Information checkbox.
Explanation: Processing stops. System Action: None User Response: Try checking the box specified in the message. 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.
806
IBM Tivoli Storage Manager: Messages
Chapter 9. Data Protection for Oracle (ANU0000ANU9999)
The messages in this section are for the Data Protection for Oracle. The messages begin with the prefix ANU and are listed in numerical order.
ANU0003S An internal processing error has occurred. ANU0055E Write failure on license file (licensefile).
Explanation: An internal processing error has occurred. System Action: Processing ends. User Response: Retry the operation. If this error persists, contact your service representative. ANU0004E An unknown error has been detected.
Explanation: An attempt to write to the license file failed. System Action: Processing ends. User Response: Make sure enough space exists on the workstation to write to the license file. If enough space exists, run the command again. ANU0056E Data in the license file (licensefile) is not in a valid format.
Explanation: An internal processing error has occurred that prevents the generation of a message for a return code. System Action: Processing continues. User Response: Retry the operation. If this error persists, contact your service representative. ANU0005E Out of memory. Stop other processes and try the operation again.
Explanation: An attempt to read information from the license file failed. System Action: Processing ends. User Response: Install the product again. ANU0057E The checksum in the license file (licensefile) does not match the license string text.
Explanation: The machine has run out of memory. System Action: Processing continues. User Response: Close unnecessary processes and try the operation again. ANU0053E License file (licensefile) could not be opened.
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. System Action: Processing ends. User Response: Reinstall the product. ANU0058E The Try and Buy license has expired.
Explanation: An attempt to read from the license file failed. System Action: Processing ends. User Response: Install the product again. This ensures that the correct license file is installed. ANU0054E Read failure on license file (licensefile).
Explanation: This Try and Buy license that was detected has expired. System Action: Processing ends. User Response: This product is no longer valid for use. A valid license must be obtained before running the product. ANU0100E Incomplete command:
Explanation: An attempt was made to read from the license file. This attempt failed. System Action: Processing ends. User Response: Reinstall the product. This will ensure that the correct license file is installed.
Explanation: This message displays the incomplete command that was entered. System Action: Processing ends. User Response: Re-enter the complete command.
Copyright IBM Corp. 1993, 2004
807
ANU0101E ANU0152I
ANU0101E Invalid argument: ANU0133W Could not locate installation directory. Attempting to continue... Explanation: An attempt was made to read the registry to determine where the Tivoli Data Protection application client was installed. This attempt failed. System Action: Processing will continue with the command entered. 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. ANU0134W Could not locate log directory. Processing will continue... Explanation: An attempt was made to read the registry to determine where the Tivoli Data Protection application client log is located. This attempt failed. System Action: Processing will continue with the command entered. 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. ANU0150I Operation canceled by user.
Explanation: This message displays the command that was entered, up to and including the invalid command or option argument that was detected. System Action: Processing ends. User Response: Re-enter the command specifying a valid argument for the command or option. ANU0102E Invalid command:
Explanation: This message displays the invalid command that was entered. System Action: Processing ends. User Response: Re-enter a valid command. ANU0103E Invalid option for the specified command:
Explanation: This message displays the command that was entered, up to and including the option that was detected as invalid for the command. System Action: Processing ends. User Response: Re-enter the command specifying valid command options. ANU0104E Invalid option:
Explanation: This message displays the command that was entered, up to and including the invalid option that was detected. System Action: Processing ends. User Response: Re-enter the command specifying valid command options. ANU0105E Missing argument:
Explanation: The user has requested that the Tivoli Storage Manager application client end by entering ctrl-C. System Action: Processing ends. User Response: None ANU0151E Errors occurred while processing the request.
Explanation: This message displays the command that was entered, up to and including the command or option whose required argument is missing. System Action: Processing ends. User Response: Re-enter the command specifying a valid argument for the command or option. ANU0132W Tracing could not be started. Processing will continue. Explanation: A problem prevented tracing from beginning. System Action: Processing will continue with the command entered. User Response: Refer to the other messages that display with this message to determine the problem.
Explanation: Attempting to process the request entered, an error occurred. System Action: Processing ends. User Response: Attempt to determine the source of the errors from viewing the log file. Correct the problems and try running the command again. ANU0152I Performance stats: seconds seconds spent in apicall API calls
Explanation: The indicated number of seconds were spent making API calls for the indicated system. System Action: Processing continues. User Response: None
808
IBM Tivoli Storage Manager: Messages
ANU0153I ANU0200E
ANU0153I Performance stats: seconds seconds spent in function ANU0160E An authentication error occurred with your stored Tivoli Storage Manager password.
Explanation: The indicated number of seconds were spent the named function. System Action: Processing continues. User Response: None ANU0154E The Tivoli Storage Manager application client cannot work with the version of the Tivoli Storage Manager API you have installed. Please install version version.release.level or greater.
Explanation: You were unable to log on to the Tivoli Storage Manager server due an authentication error. System Action: Processing stops. User Response: The stored Tivoli Storage Manager password may have become corrupted. Contact your Tivoli Storage Manager server administrator. ANU0161E Authentication error. The password entered is not valid. You are not logged on to the Tivoli Storage Manager server.
Explanation: The version of the Tivoli Storage Manager API currently installed on the system is older than the version used to build the Tivoli Storage Manager application client. System Action: Processing ends. User Response: Install a version of the Tivoli Storage Manager API at or later than the indicated level. A copy is distributed with the Tivoli Storage Manager application client. ANU0155E The Tivoli Storage Manager application client cannot work with the release of Tivoli Storage Manager API you have installed. Please install release version.release.l evel or greater.
Explanation: An incorrect password was entered. System Action: Processing stops. User Response: Enter the correct Tivoli Storage Manager password and try again. ANU0162E The passwords entered do not match. Please enter them again.
Explanation: An incorrect password was entered. System Action: Processing stops. User Response: Enter the passwords again. ANU0163E The directory path needs to be fully-qualified.
Explanation: The release of the Tivoli Storage Manager API currently installed on the system is older than the release used to build the Tivoli Storage Manager application client. System Action: Processing ends. User Response: Install a release of the Tivoli Storage Manager API at or later than the indicated level. A copy is distributed with the Tivoli Storage Manager application client. ANU0156E Could not load the Tivoli Storage Manager API.
Explanation: The /intopath option was specified without a fully-qualified path. System Action: Processing stops. User Response: Enter the command again and specify a fully-qualified path in the /intopath option. ANU0167E The fully-qualified file name is too long.
Explanation: The Tivoli Storage Manager API could not be loaded. System Action: Processing ends. User Response: Ensure the Tivoli Storage Manager API is correctly installed. Run the Tivoli Storage Manager 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.
Explanation: An attempt was made to use a fully-qualified file name that was too long. This attempt failed. System Action: Processing ends. User Response: None ANU0200E File (filename) could not be opened for reading.
Explanation: An attempt was made to open a file for reading. This attempt failed. System Action: Processing ends. User Response: None
Chapter 9. Data Protection for Oracle
809
ANU0201E ANU0213E
ANU0201E File (filename) could not be opened for writing. ANU0208E There is not enough disk space for the operation attempted.
Explanation: An attempt was made to open a file for writing. This attempt failed. System Action: Processing ends. User Response: None ANU0202E Read failure on file (filename).
Explanation: An attempted operation required more disk space than was available. The attempt failed. System Action: Processing ends. User Response: None ANU0209E The rename of file (filename1) to (filename2) failed.
Explanation: An attempt was made to read from a file. This attempt failed. System Action: Processing ends. User Response: None ANU0203E Write failure on file (filename).
Explanation: An attempt was made to rename a file. This attempt failed. System Action: Processing ends. User Response: None ANU0210E The Tivoli Storage Manager high level qualifier is too long.
Explanation: An attempt was made to write to a file. This attempt failed. System Action: Processing ends. User Response: None ANU0204E File (filename) could not be closed.
Explanation: An attempt was made to use a Tivoli Storage Manager high level qualifier that was too long. This attempt failed. System Action: Processing ends. User Response: None ANU0211E The Tivoli Storage Manager low level qualifier is too long.
Explanation: An attempt was made to close a file. This attempt failed. System Action: Processing ends. User Response: None ANU0205E File (filename) statistics could not be obtained.
Explanation: An attempt was made to use a Tivoli Storage Manager low level qualifier that was too long. This attempt failed. System Action: Processing ends. User Response: None ANU0212E The Tivoli Storage Manager filespace name is too long.
Explanation: An attempt was made to obtain file statistics. This attempt failed. System Action: Processing ends. User Response: None ANU0206E Directory (directory) could not be created.
Explanation: An attempt was made to use a Tivoli Storage Manager filespace name that was too long. This attempt failed. System Action: Processing ends. User Response: None ANU0213E The maximum number of objects allowed per Tivoli Storage Manager transaction is t oo small.
Explanation: An attempt was made to create a directory. This attempt failed. System Action: Processing ends. User Response: None ANU0207E Directory path (directorypath) is too long.
Explanation: An attempt was made to use a directory path that was too long. This attempt failed. System Action: Processing ends. User Response: None
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 Tivoli Storage Manager application client. System Action: Processing ends.
810
IBM Tivoli Storage Manager: Messages
ANU0214E ANU0259E
User Response: Increase the maximum number of objects allowed per transaction on the Tivoli Storage Manager server and retry the operation. ANU0214E The backup objects management class backup copy group does not exist. ANU0219E The Tivoli Storage Manager low level qualifier is invalid.
Explanation: The low level qualifier name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the low level qualifier name length, characters, and directory delimeters are valid. ANU0256E 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: The Tivoli Storage Manager server has indicated that the backup objects management class backup copy group does not exist. System Action: Processing ends. User Response: Contact your Tivoli Storage Manager server administrator. ANU0215E All backup objects do not have the same management class backup copy destination.
Explanation: In order to maintain backup data integrity, multiple backup objects are sent to the Tivoli 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. System Action: Processing ends. User Response: Contact your Tivoli Storage Manager server administrator. ANU0216E Unable to obtain space information for volume (volumename).
Explanation: Your Tivoli Storage Manager password has expired. You need to change your password. System Action: Processing ends. 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. ANU0257E Your password has expired.
Explanation: Your Tivoli Storage Manager password has expired. A new password needs to be obtained. System Action: Processing ends. User Response: Obtain a new password for your Tivoli Storage Manager node using the change password command or by asking your Tivoli Storage Manager Administrator to change your password. ANU0258E You did not enter a valid password. Processing ends.
Explanation: An attempt was made to obtain space information for a volume. This attempt failed. System Action: Processing ends. User Response: None ANU0217E The Tivoli Storage Manager filespace name is invalid.
Explanation: The filespace name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the filespace name length, characters, and directory delimeters are valid. ANU0218E The Tivoli Storage Manager high level qualifier is invalid.
Explanation: The password that was entered was not a valid password. System Action: Processing ends. User Response: Re-enter the command specifying a valid password. ANU0259E 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 high level qualifier name or directory delimeter is invalid. System Action: Processing ends. User Response: Check that the high level qualifier name length, characters, and directory delimeters are valid.
Explanation: The password you entered for verification of your new password does not match the new password that was entered. System Action: Processing ends.
Chapter 9. Data Protection for Oracle
811
ANU0260I ANU357E
User Response: Try again to change your password being sure to enter the same password for the new password and for the verification password. ANU0260I Password successfully changed. ANU0266E Could not find the Tivoli Storage Manager HTML books.
Explanation: An attempt was made to read the registry to determine where the Tivoli Storage Manager books were installed. This attempt failed. System Action: Processing ends. User Response: It may be necessary to reinstall the application client code. This will ensure that the registry entries are set up correctly. ANU0267E The verify password entered does not match the new password entered.
Explanation: The change password command completed successfully System Action: Processing ends. User Response: None ANU0261I There are no backups for the server named servername.
Explanation: There are no backups on the Tivoli Storage Manager server for the specified server name. System Action: Processing ends. User Response: None ANU0263E Failed to start Web browser with a return code of returncode.
Explanation: The verify password does not match the new password. System Action: Processing ends. User Response: Retry the command with a matching verify password. ANU0300E Invalid restore type.
Explanation: An attempt was made to start the web browser to view the TSM HTML b ook. This attempt failed. System Action: Processing ends. User Response: Start your web browser manually and point it to bookfrm.htm in the agent htm directory. ANU0264I Could not find the default browser defined. An attempt will be made to use Microsoft Internet Explorer.
Explanation: The type of restore requested is invalid. System Action: Processing ends. User Response: Re-enter the command specifying a valid restore type. ANU0301E Invalid backup type.
Explanation: The type of backup requested is invalid. System Action: Processing ends. User Response: Re-enter the command specifying a valid backup type. ANU351E Invalid trace keyword - keyword
Explanation: An attempt was made to read the registry to determine the default browser. However, a default browser is not defined. A determination will be made where Microsoft Internet Explorer is installed. System Action: Processing continues. 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. ANU0265E Could not find Internet Explorer.
Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect. System Action: Client program did not initialize or tracing was not enabled in the applet. User Response: Correct the value. ANU357E Unable to open trace output file file-name.
Explanation: An attempt was made to read the registry to determine where Microsofts Internet Explorer was installed. This attempt failed. System Action: Processing ends. User Response: Make sure that the registry is set up correctly for Internet Explorer.
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. System Action: Client program did not initialize. User Response: Change the TRACEFILE value so that it is a location to which you have write access.
812
IBM Tivoli Storage Manager: Messages
ANU366E ANU2504E
ANU366E Unable to close trace output file file-name. ANU385E Unable to delete symbolic link link.
Explanation: Log linkname cannot be a symbolic link. System Action: Processing stops. User Response: Delete the symbolic link linkname. ANU476E program-name: cannot open file file-spec: error.
Explanation: An error occurred during the closing of a trace output file-name (for example, not enough disk space). System Action: Processing continues. User Response: Check the options.doc file for a description of possible causes of the error, or see your system administrator. ANU367E Unable to write to trace file tracefile. Tracing disabled.
Explanation: TSM cannot open the file. System Action: TSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system administrator. ANU2500E Oracle passed an invalid mode
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. ANU368E Invalid trace file name (name too long).
Explanation: Invalid mode passed by Oracle. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANU2501E Oracle passed a null file name
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. ANU383E Specifying the trace file link as a symbolic link is not allowed.
Explanation: Null file name passed by Oracle. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANU2502E Wrong data block size
Explanation: Wrong data block size. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANU2503E Backup object filespacehlll already exists on TSM Server.
Explanation: Trace file linkname cannot be a symbolic link. System Action: The symbolic link linkname is deleted, the trace file is recreated, and processing stops. User Response: Specify the trace file location with the tracefile option. ANU384E Symbolic link linkname to target was successfully deleted.
Explanation: The object has previously been backed up to the TSM Server. System Action: Application Client 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
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.
Explanation: The handle passed from Oracle is not the same handle that TSM passed back. System Action: The system returns to the calling procedure. User Response: Contact your system administrator.
Chapter 9. Data Protection for Oracle
813
ANU2505I ANU2517E
ANU2505I End of file reached User Response: Reduce the number of backup copies to that allowed by RMAN. ANU2512E Could not open license file: license file
Explanation: End of file reached. System Action: The system returns to the calling procedure. User Response: None. ANU2506E Wrong Read State
Explanation: The license file could not be opened. System Action: The system returns to the calling procedure. User Response: Check that the license file exists with the correct permissions. ANU2513E Could not read license file: license file
Explanation: The operation must be in READ state. System Action: The system returns to the calling procedure. User Response: Contact TSM support. ANU2507E Runtime API version is outdated
Explanation: The license file could not be read. System Action: The system returns to the calling procedure. User Response: Check that the license file permissions are correct. ANU2514E Could not write license file: license file
Explanation: Runtime API is lower than compile time API. System Action: The system returns to the calling procedure. User Response: Check compile time API level, obtain same or higher level of API library. ANU2508E Wrong write state
Explanation: The license file could not be written. System Action: The system returns to the calling procedure. User Response: Check that the license file permissions are correct. ANU2515E Invalid data format in license file: license file
Explanation: The operation must be in WRITE state. System Action: The system returns to the calling procedure. User Response: Contact TSM support. ANU2509E Invalid flag passed
Explanation: The license file data format is invalid. System Action: The system returns to the calling procedure. User Response: Reinstall the license that came with Application Client. ANU2516E Bad checksum of license file: license file
Explanation: Oracle passed an invalid flag. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANU2510E The Caller must be a root user
Explanation: The license file has a bad checksum. System Action: The system returns to the calling procedure. User Response: Reinstall the license that came with Application Client. ANU2517E Try and Buy Evaluation period is over for license file: license file
Explanation: Only a UNIX root user can execute password System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANU2511E Reduce the number of copies to that specified in RMAN
Explanation: The Try and Buy Evaluation period is over. System Action: The system returns to the calling procedure. User Response: Purchase the product or discontinue use.
Explanation: The duplex copy feature has reached maximum allowed copies. System Action: The system returns to the calling procedure.
814
IBM Tivoli Storage Manager: Messages
ANU2518E ANU2533E
ANU2518E License file: license file not valid for this application the range of the date values are valid.Valid days are: 1-31Valid months are: 1-12Valid years are:1990-2089 ANU2529E To Date cannot occur before From Date
Explanation: The license file is not intended for this application. System Action: The system returns to the calling procedure. User Response: Reinstall the license that came with Application Client. ANU2519E Could not read password
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. ANU2530E Screen size is too small to accurately display the PICK window.
Explanation: There is an invalid password or the password file cannot be not found. System Action: The system returns to the calling procedure. User Response: Check that password file exists and is valid. ANU2521E Error opening file name. Check permissions.
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: The operation was not completed. User Response: Retry the operation using a workstation that has a screen with the minimum size. ANU2531E Could not create a temporary file name for Application Client utility
Explanation: A directory could not be created. System Action: The system returns to the calling procedure. User Response: Check that permissions allow the creation of directories. ANU2522E No memory available
Explanation: A temporary file name could not be created by the Operating System call to tempnam(). System Action: The system returns to the calling procedure. 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. ANU2532E Unknown Error - View the Application Client error log
Explanation: There is not enough system memory to complete the action. System Action: The system returns to the calling procedure. User Response: Make more system resources available by closing other applications, then try the action again. ANU2523E The Management Class does not match
Explanation: There was an unknown error. View the tdpoerror.log. System Action: None User Response: None ANU2533E SQLPLUS error
Explanation: The management class for the query object could not be found. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANU2525E Input date does not match expected date format or range.
Explanation: The utility could not find SQLPLUS or there was a scripting error. System Action: The system returns to the calling procedure. User Response: Check that SQLPLUS is installed and located in your search path. Verify the password.
Explanation: The input date does not match the expected date format or range. System Action: The system returns to the calling procedure. User Response: Check that the format and length of the date entry matches TDP_DATE_FORMAT type and
Chapter 9. Data Protection for Oracle
815
ANU2534E ANU2601E
ANU2534E Option file error. ANU2571E Could not load the library: library Application Client
Explanation: The option or option file name is invalid. System Action: The system returns to the calling procedure. User Response: Check the tdpoerror.log file for an explanation of the error. ANU2535I File /fs/hl/ll = number bytes sent
Explanation: Library cannot be loaded. System Action: The system returns to the calling procedure. User Response: Check that the library exists. ANU2575E An error was detected while attempting to open the file filename for writing.
Explanation: This is the total bytes sent to the server for that file name System Action: The system returns to the calling procedure. User Response: Check the TSM Server activity log. ANU2536I File /fs/hl/ll = number bytes recieved
Explanation: The Application Client utility failed to open the file named in the error message. System Action: The system returns to the calling 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: This is the total bytes received from the server for that backup file name. System Action: The system returns to the calling procedure. User Response: Check the TSM Server activity log. ANU2537E Error found while parsing options in Application Client options file.
Explanation: The Application Client utility failed to open the temporary file named in the error message. System Action: The system returns to the calling 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: There was an error found while parsing the Application Client options file. System Action: The system returns to the calling procedure. User Response: Check that the options and the options file are valid. ANU2538E Error found while initializing tracing for Application Client.
Explanation: The Windows Registry entry was not found. System Action: The system returns to the calling procedure. User Response: Check that the TSM API is installed correctly. ANU2601E There is no Registry entry for the Application Client install path.
Explanation: Error found while initializing the Application Client trace facility. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. ANU2539E Function Name: Error - string pointer is NULL.
Explanation: The Registry Entry for the Application Client install path was not found. System Action: The system returns to the calling procedure. User Response: Check that Application Client was installed correctly.
Explanation: A NULL pointer was passed to Application Client. System Action: The system returns to the calling procedure. User Response: Contact your system administrator.
816
IBM Tivoli Storage Manager: Messages
ANU2602E ANU2616E
ANU2602E 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. System Action: The system returns to the calling 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 Application Client options file. System Action: The system returns to the calling procedure. User Response: Verify that your options are correct in the Application Client options file. ANU2614E Invalid sequence of function calls to Application Client
Explanation: Application Client received a function call from Oracle that is out of sequence. System Action: Application Client returns to the calling procedure. User Response: Contact Oracle or Application Client support. ANU2615E Options file filename not found.
Explanation: The option file name specified could not be located. System Action: The system returns to the calling procedure. User Response: Ensure that an option file exists in the default path or that the user specified option file is valid. ANU2616E Empty parameter specified for option option in options file filename.
Explanation: The option specified must have a parameter supplied. System Action: The system returns to the calling procedure. User Response: Ensure that a valid parameter for the given option is entered and valid.
Chapter 9. Data Protection for Oracle
817
818
IBM Tivoli Storage Manager: Messages
Chapter 10. Data Protection for mySAP.com Technology for DB2 UDB (BKI0000BKI9999)
This chapter describes the messages issued by Data Protection for mySAP.com Technology for DB2 UDB. The messages begin with the prefix BKI and are listed in numerical order.
BKI0000E Profile not specified. mySAP.com call will be completed at the estimated end_time. User Response: None. BKI0024I Return code is: return code
Explanation: Data Protection for mySAP.com cannot locate the profile. User Response: Ensure that a profile is available. BKI0005I Explanation: User Response: None. BKI0007E Mode mode requires the environment variable environment variables to be set. Start of program at: time
Explanation: Shows the return code of Data Protection for mySAP.com. 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: Not all environment variables required have been set. At least environment variables where missing. 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. User Response: Set name to an appropriate value. BKI0020I Explanation: User Response: None. BKI0021I Elapsed time: elapsedtime End of program at: time
Explanation: Data Protection for mySAP.com 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. User Response: None. BKI0031W Object not found or not accessible: objectname.
Explanation: The object was not found or is not accessible to Data Protection for mySAP.com. User Response: Check path and name and the permissions of that object and try again. BKI0032E Error opening file file name: system error description
Explanation: The time needed for the complete backup was elapsedtime. User Response: None. BKI0023I Time: current_time Done: saved_bytes (percent) of bytes Estimated end time: end_time
Explanation: A system error occurred during opening of the file file name. system error description will describe the error in more detail. User Response: Read the system error description.
Explanation: Data Protection for mySAP.com 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 Data Protection for
Copyright IBM Corp. 1993, 2004
819
BKI0033E BKI0060E
BKI0033E Error opening file file name: system error description BKI0054I Time: current_time Objects: current_num of total_num done: file_name with: bytes restored with description object_desc.
Explanation: See BKI0032E. User Response: See BKI0032E. BKI0049I 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 Data Protection for mySAP.com configuration file. User Response: Enter the password for the corresponding Tivoli Storage Manager server. BKI0050I Please enter password for node nodename on server server name again
Explanation: Data Protection for mySAP.com 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. User Response: None. BKI0055I Object objectname with size saved with description description.
Explanation: The object objectname was saved successfully. User Response: None. BKI0056I Object objectname with size restored with description description.
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 object objectname was restored successfully. User Response: None. BKI0057I Time: current_time Object objectname with size saved with description description.
Explanation: The password for the node nodename on the Tivoli Storage Manager server server name was changed successfully. User Response: None. BKI0052E Password verification for node nodename on server server name failed.
Explanation: The object objectname was saved successfully. User Response: None. BKI0058I Time: current_time Object objectname with size restored with description description.
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 Objects: current_num of total_num done: file_name with: bytes saved with description object_desc.
Explanation: The object objectname was restored successfully. User Response: None. BKI0059E You have to set the environment variable DSMI_CONFIG to the full filename of the Tivoli Storage Manager client option file dsm.opt.
Explanation: Data Protection for mySAP.com 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. User Response: None.
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 for Data Protection for mySAP.com is unknown. User Response: Check the specified command parameter and try again.
820
IBM Tivoli Storage Manager: Messages
BKI0063E BKI1001E
BKI0063E The UTL file file name is not valid. BKI0452E This version of Data Protection for mySAP.com technology (R) has expired.
Explanation: Data Protection for mySAP.com is not able 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: This is a test version that has expired. User Response: Order a release version of Data Protection for mySAP.com or contact your IBM/Tivoli Sales Representative. BKI0453W This version of Data Protection for mySAP.com technology (R) will expire in number days.
Explanation: A Data Protection for mySAP.com option is invalid or unknown. User Response: Check the specified option(s) and try again. BKI0065E The argument is missing for option option.
Explanation: This is a test version with a time limit. It will expire in number days. User Response: Order a release version of Data Protection for mySAP.com or contact your IBM/Tivoli Sales Representative before the version expires. BKI0454I *** This copy is NOT FOR RESALE. ***
Explanation: Every Data Protection for mySAP.com option requires an argument. User Response: Insert the missing argument and try again. BKI0101I Session session: Please enter cont to continue or stop to cancel.
Explanation: This version is not for resale. User Response: None. BKI0455E License file file name does not exist.
Explanation: If Data Protection for mySAP.com 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 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: Data Protection for mySAP.com indicates the reply you made. User Response: None. BKI0311E Request canceled by user.
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. BKI1000E Syntax error in line line: statement
Explanation: Data Protection for mySAP.com terminated at users request. User Response: None BKI0451I This version of Data Protection for mySAP.com technology (R) will expire on date.
Explanation: This is a test version that will expire on date. User Response: None.
Explanation: The statement statement in the Data Protection for mySAP.com profile is unknown or incorrect. User Response: Correct the error and try again. BKI1001E Syntax error in file file name. Exiting Program.
Explanation: Data Protection for mySAP.com has detected an syntax error in the file file name and stops any action.
Chapter 10. Data Protection for mySAP.com for DB2 UDB
821
BKI1002E BKI1014I
User Response: Correct the error(s) in the file file name and try again. BKI1002E BACKUPIDPREFIX must be number_of_characters characters. BKI1008E The MANAGEMENTCLASSNAME must be less than max_char characters.
Explanation: You have used a MANAGEMENTCLASSNAME with more than max_char characters. User Response: Use a shorter MANAGEMENTCLASSNAME. BKI1009W Please set MULTIPLEX to a number between 1 and max_multiplex. Now it is set to act_multiplex.
Explanation: The length of BACKUPIDPREFIX must be number_of_characters characters. User Response: Enter a BACKUPIDPREFIX with the required length (e.g., SAP___, BKI___). BKI1003W Please set REDOLOG_COPIES to a number between 1 and max_copies. Now it is set to act_copies.
Explanation: Data Protection for mySAP.com currently supports 1 to 9 copies of offline log files. User Response: Adapt the REDOLOG_COPIES settings in the Data Protection for mySAP.com profile. BKI1004W You should specify the BACKUPIDPREFIX before the TRACEFILE statement, so that the BACKUPIDPREFIX can be used in the tracefile name.
Explanation: You have set multiplexing to an unsupported number. Data Protection for mySAP.com 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 /db2/C21/dbs/initC21.bki BKI1012E The configfilename configuration_filename could not be opened.
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 Data Protection for mySAP.com profile (e.g., SAP___, BKI___). BKI1005W The tracefile name trace_filename should be absolute.
Explanation: Data Protection for mySAP.com is unable to read the file 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. BKI1013E Profile not found or permissions denied: profile_filename.
Explanation: None. User Response: Specify an absolute tracefile name, for example /db2/C21/saptrace/tracefile . BKI1006E The SERVERNAME must be less than max_char characters.
Explanation: Data Protection for mySAP.com is unable to open the profile profile_filename. User Response: Ensure that the file pointed to by DB2_VENDOR_INI contains a valid entry XINT_PROFILE. Furthermore, this file must be readable by Data Protection for mySAP.com. See chapter Installing Data Protection for mySAP.com for details. BKI1014I The parameter PERF_MONITOR is no longer supported. Now it is enabled by default.
Explanation: You have used a SERVERNAME with more than max_char characters. User Response: Use a shorter SERVERNAME. BKI1007E The NODENAME must be less than max_char characters.
Explanation: You have used a NODENAME with more than max_char characters. User Response: Use a shorter NODENAME.
Explanation: For version 2.7 or later of Data Protection for mySAP.com, the Performance Monitor of the Administration Assistant can be used by default.
822
IBM Tivoli Storage Manager: Messages
BKI1015I BKI1203E
Therefore, the profile parameter PERF_MONITOR is no longer needed. User Response: None. BKI1015I The parameter BACKAGENT is no longer needed. BKI1022E ProLE terminates the connection due to a previous error.
Explanation: See message BKI1021E. User Response: See message BKI1021E. BKI1023W Could not establish connection to log server log server name.
Explanation: For version 2.7 or later of Data Protection for mySAP.com, only one executable, called BACKINT, will be provided and needed. The former executable, called BACKAGENT, will no longer be supported or needed. User Response: None. BKI1016W The trace file name file name could not be opened for writing!
Explanation: In the Data Protection for mySAP.com technology 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 Data Protection for mySAP.com 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. BKI1200E Cannot read/write file: file name.
Explanation: The trace file could not be opened for writing. User Response: Ensure that you have specified a correct path for the trace file. BKI1017E The server server name is already defined. Please use another name!
Explanation: The server you want to configure is already defined. User Response: Specify another server name. Server names have to be unique. BKI1019E Failed to respond to a message received from XINT.
Explanation: Data Protection for mySAP.com is unable to read or write a data file (file name) of a tablespace being backed up or restored. User Response: Check the file access permission of the affected file(s). Try again. If the problem still exists, contact the mySAP.com administrator. BKI1201E There are no Tivoli Storage Manager Servers available.
Explanation: This messages indicates an internal error. User Response: Contact Data Protection for mySAP.com technology support. BKI1020 The compress info file file name should be absolute !
Explanation: Data Protection for mySAP.com cannot locate a Tivoli Storage Manager server. User Response: Install and specify at least one Tivoli Storage Manager server in the Data Protection for mySAP.com profile (keyword SERVER). BKI1203E Not enough sessions available (number of sessions required and number of sessions available).
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 ProLE terminates the connection due to a previous error.
Explanation: A fatal error has occurred which caused a shutdown of the communication channel between the ProLE process and this application. User Response: Look for previous error messages to detect the root cause of the problem.
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 Data Protection for mySAP.com profile, so that the condition mentioned in the explanation is fulfilled.
Chapter 10. Data Protection for mySAP.com for DB2 UDB
823
BKI1205E BKI2001E
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. 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 missmatch error. Check setup (%1$S:%2$S).
Explanation: Data Protection for mySAP.com 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 log file copies (parameter REDOLOG_COPIES). User Response: Define at least as many different Archive Management Classes as redo log copies requested. BKI1211E There is something wrong with your CONFIG_FILE file name.
Explanation: The version numbers of the installed backup library and ProLE do not match. User Response: Check your setup or contact Data Protection for mySAP.com support. BKI1223W A problem occurred during send of performance data to Administration Assistant .
Explanation: There is a problem with your Data Protection for mySAP.com configuration file setup. User Response: Check the file permission and the file name specified in the Data Protection for mySAP.com profile keyword CONFIG_FILE. BKI1213I Program ended with code = return code
Explanation: There was a problem sending the performance data to the Administration Assistant over the network. User Response: Check your setup or contact Data Protection for mySAP.com support. BKI1224W Unable to initialize connection to Administration Assistant.
Explanation: The return code of the program is displayed. User Response: None. BKI1214E TSM Error: error text
Explanation: There was a problem initializing the connection to the Administration Assistant over the network. User Response: Check your setup or contact Data Protection for mySAP.com support. BKI1227I Average compression factor was number.
Explanation: The specified TSM error occurred. User Response: Check error text and correct the problem. BKI1215I Average transmission rate was number GB/h (number MB/sec).
Explanation: The data transferred had been compressed by the factor number. User Response: None BKI2000I Successfully connected to ProLE on port portnumber.
Explanation: The average transmission rate is displayed. User Response: None. BKI1216E There are no BRBACKUPMGTCLASSES available.
Explanation: The backup library initiated a successful connection to the background process ProLE on port portnumber. User Response: None. BKI2001E Socket error while connecting to ProLE: reason.
Explanation: The BRBACKUPMGTCLASSES 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.
Explanation: The Data Protection for mySAP.com background process ProLE is not running. User Response: Start ProLE manually and try again.
824
IBM Tivoli Storage Manager: Messages
BKI2002E BKI2016I
BKI2002E No valid callback function of type func_type supplied. BKI2009I Deleting all versions with version number <= version_number on server server_name.
Explanation: Internal Data Protection for mySAP.com error User Response: Contact Data Protection for mySAP.com support. BKI2003I File file_name, BID deleted.
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. User Response: None. BKI2010E Error occurred processing FRONTEND
Explanation: The file file_name with the backup ID BID was deleted from the Tivoli Storage Manager. User Response: None. BKI2004E Connection to ProLE lost.
Explanation: An error occurred during the frontend processing. User Response: Check the frontend script/program and the settings in the Data Protection for mySAP.com profile (keyword FRONTEND) and try again. BKI2011E Error occurred processing BACKEND.
Explanation: During Data Protection for mySAP.com operation the connection to ProLE was lost. Network problems could be the reason. User Response: Check your network environment and if ProLE is still running and try again. BKI2005E Illegal parameter in message from ProLE. Exiting...
Explanation: An error occurred during the backend processing. User Response: Check the backend script/program and the settings in the Data Protection for mySAP.com profile (keyword BACKEND) and try again. BKI2012E Passwords do not match. Try again.
Explanation: This error occurs if the versions of ProLE and the backup library do not match. User Response: Check the versions of ProLE and of the backup library you are currently using. BKI2006E General exception in dispatcher. Exiting...
Explanation: The first and second password you entered do not match. User Response: Enter the password correctly. BKI2013I Starting FRONTEND Program.
Explanation: Internal Data Protection for mySAP.com error. User Response: Contact Data Protection for mySAP.com support. BKI2007E Unknown Port: port
Explanation: The frontend program is executing. User Response: None. BKI2014I FRONTEND program finished.
Explanation: The frontend program is finished. User Response: None. BKI2015I Starting BACKEND program.
Explanation: The port specified for communication between ProLE and the backup library is unknown. User Response: Check the port value specified when ProLE was started. Additionally, check the environment variable PROLE_PORT for the BACKINT environment. These two values must match. BKI2008E Unable to connect to ProLE.
Explanation: The backend program is executing. User Response: None. BKI2016I BACKEND program finished.
Explanation: Internal Data Protection for mySAP.com error. User Response: Contact Data Protection for mySAP.com support.
Explanation: The backend program is finished. User Response: None.
Chapter 10. Data Protection for mySAP.com for DB2 UDB
825
BKI2017I BKI4001E
BKI2017I Blocksize is set to num_bytes bytes. BKI2024E Error in connection to ProLE.
Explanation: The operational blocksize of Data Protection for mySAP.com is num_bytes bytes. User Response: None. BKI2018E Exception in main message loop: description
Explanation: The connection to ProLE terminated unexpectedly. This message might be displayed due to previous errors or after an unexpected termination of the ProLE process. User Response: Check for other error messages and restart ProLE if necessary. Try again. If the problem persists, contact Data Protection for mySAP.com support. BKI2025E Failed to respond to a message received from ProLE.
Explanation: An error occurred during processing. The error may contain a descriptive text. User Response: Contact your service representative. BKI2019E Socket error while connecting to ProLE on port number for tracing: description
Explanation: This is an internal error User Response: Contact Data Protection for mySAP.comsupport. BKI2026E Unexpected exception in handler: handler
Explanation: During processing, a socket error occurred on port number. description may contain the system error text. User Response: Check the description. If the error persists, contact your service representative. BKI2020E Error occurred for trace connection to ProLE on port number.
Explanation: This is an internal error. User Response: Contact Data Protection for mySAP.com support. BKI2027I Using TSM-API version your api version (compiled with compiled with version).
Explanation: The network connection that is used for tracing generated an error on port number. User Response: Contact your service representative. BKI2021E Unable to delete file file name: description
Explanation: Version information about the TSM-API. User Response: None BKI2028W Unable to terminate session session.
Explanation: Unable to delete the file file name. description may contain the system error text. User Response: Check the description. If the error persists, contact your service representative. BKI2022E Unable to change mode of file file name: description
Explanation: This is an internal error during cleanup that has no effect on the success of the service. User Response: None BKI4000W The attributes of file file name cannot be restored. Reason: errno (error_num) error_desc.
Explanation: Unable to change mode of file file name. description may contain the system error text. User Response: Check the description. If the error persists, contact your service representative. BKI2023E Error occurred during trace connection to ProLE. Tracing will stop now.
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. BKI4001E File file name cannot be created. Reason: errno (error_num) error_desc.
Explanation: Error occurred during trace connection to ProLE. User Response: Tracing will stop. If the problem persists, contact your service representative.
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.
826
IBM Tivoli Storage Manager: Messages
BKI4002E BKI5006E
User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future. Furthermore, check the write permission of the user who started the restore. BKI4002E Error during restore of file file name. Reason: errno (error_num) error_desc. BKI4007E 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. User Response: Contact your system administrator. BKI5000E Tivoli Storage Manager Error: error_message
Explanation: An error occurs during the restore process of the file file name. User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future. BKI4003E Error reading file file name. Only read num_bytes out of all_bytes.
Explanation: During a connection of Data Protection for mySAP.com 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. BKI5001E Tivoli Storage Manager Error: error_message
Explanation: An error occurs reading the file file name. Only num_bytes of all_bytes could be read. User Response: Try your last action again. If the error still exists, contact Data Protection for mySAP.com support. BKI4004E Error writing file filename. Only wrote num_bytes out of all_bytes.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5002E Tivoli Storage Manager Error: error_message
Explanation: An error occurs writing the file file name. Only num_bytes of all_bytes could be written. User Response: Try your last action again. If the error still exists, contact Data Protection for mySAP.com support. BKI4005E Error allocating memory block for file file name. BLOCKSIZE may be too large.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5003E Tivoli Storage Manager Error: error_message
Explanation: Data Protection for mySAP.com was not able 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 of Data Protection for mySAP.com. BKI4006E Error allocating memory block for file file name. BLOCKSIZE may be too large.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5004E Tivoli Storage Manager Error: error_message
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5005E Tivoli Storage Manager Error: error_message
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5006E Tivoli Storage Manager Error: error_message
Explanation: See BKI4005E. User Response: See BKI4005E.
Explanation: See BKI5000E. User Response: See BKI5000E.
Chapter 10. Data Protection for mySAP.com for DB2 UDB
827
BKI5007E BKI7056E
BKI5007E Tivoli Storage Manager Error: error_message BKI5015W Data description could not be restored, because it was backed up with a newer version (objInf=support information)
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5008E Tivoli Storage Manager Error: error_message
Explanation: The TSM server hosts backups (i.e. data description) which were made with a new version of backint. Backint ignores this data in the further processing. User Response: Upgrade backint BKI7049I The default ProLE port will be used.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5009E Tivoli Storage Manager Error: error_message
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5010E Tivoli Storage Manager Error: error_message
Explanation: The port for the internal communication of Data Protection for mySAP.com is set during installation. The message indicates that this port is being used. User Response: None. BKI7051E The environment variable XINT_PROFILE is not set. It must be set and contain the full qualified path to the *.utl file to be used.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5011E Tivoli Storage Manager Error: error_message
Explanation: The way Data Protection for mySAP.com works is specified in a profile. When called, Data Protection for mySAP.com looks for the environment variable XINT_PROFILE which must contain the fully qualified path to the profile. User Response: Check the environment for XINT_PROFILE of the user who started Data Protection for mySAP.com. BKI7053E Service setup failed due to previous error.
Explanation: See BKI5000E. User Response: See BKI5000E. 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. BKI5013E Value for name is too long. Current value: value
Explanation: The initialization of Data Protection for mySAP.com failed due to previous errors. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7055E Service open failed due to previous error in data mover.
Explanation: The value of the environment variable name has too many digits. User Response: Check if the variable is set correctly. BKI5014E Tivoli Storage Manager Error: error_message
Explanation: The Data Protection for mySAP.com command could not be started due to previous errors. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7056E Service open failed because configured TSM server could not be accessed.
Explanation: See BKI5000E. User Response: See BKI5000E.
Explanation: The Data Protection for mySAP.com command could not be started because the TSM server defined in the profile could not be accessed. User Response: Check the Data Protection for mySAP.com log file for further detailed messages.
828
IBM Tivoli Storage Manager: Messages
BKI7057E BKI7311I
BKI7057E Service open failed because all configured sessions are currently in use. are possibilities to recover from this error and continue operation. User Response: Use the information from error message and the output of DP for IBM ESS for mySAP.com to determine the cause of the problem and try again. BKI7307W DP ESS mySAP.com reported an error during FLASHCOPY operation. Do you want to continue to backup to TSM?
Explanation: The Data Protection for mySAP.com command could not be started because all configured sessions in the profile are currently in use. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7058E Service open failed because more than one file is found with the same name.
Explanation: The Data Protection for mySAP.com command could not be started because two or more files with the same name were found. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7059E Service open failed because cause the file is not found.
Explanation: The backup was requested to be stored on both the TSM server and the ESS disks. The flashcopy operation to ESS disks 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 Data Protection for mySAP.com command could not be started because a file specified was not found. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7303W Profiles for DP ESS mySAP.com are different. backup: file name restore: file name
Explanation: The current backup tried to store data on ESS disks only and did not finish successfully. User Response: Check the output from DP for IBM ESS for mySAP.com prior to this error message to detect the root cause of this error and try again. BKI7309W DP ESS mySAP.com reported an error during FLASHCOPY operation. Do you want to continue to restore from TSM?
Explanation: During backup the profile used by DP for IBM ESS for mySAP.com can be determined automatically. For restore and inquire operations the profile for DP for IBM ESS for mySAP.com must be specified in the profile using the parameter FCS_FILE. For restore DP for IBM ESS for mySAP.com must use the same profile as for backup. User Response: Correct the entry for the FCS_FILE parameter in the profile (init<SID>.utl). BKI7304I Performing DISK ONLY backup
Explanation: The data you wanted to be restored is located on the TSM server and ESS disks. The flashcopy operation from ESS disks has failed. The process can continue to restore data from the TSM server. 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. BKI7310W DP ESS mySAP.com reported an error during FLASHCOPY operation. CAUTION: Not all filesystems are available. Do you want to retry the operation?
Explanation: The data for this backup is stored on ESS disks only and will not be sent to TSM. User Response: None BKI7305E Error during call to DP ESS mySAP.com: error message
Explanation: In contrast to message BKI7309W not all filesystems are mounted. In this case it is not possible to continue the restore from the TSM server. User Response: Enter stop if you want to terminate this restore process. Enter cont if you want to retry the flash copy process. BKI7311I Profile used by DP ESS mySAP.com:
Explanation: DP for IBM ESS for mySAP.com 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 ESS disks or to ESS disks only, restore of data which is available on both TSM and ESS disks or on ESS disks only) there
Explanation: The message shows the name of the profile used by DP for IBM ESS for mySAP.com User Response: None
Chapter 10. Data Protection for mySAP.com for DB2 UDB
829
BKI7312W BKI7323W
BKI7312W Profile for DP ESS mySAP.com not specified in profile. For restore this must be specified BKI7319I Start TSM restore
Explanation: The restore uses data from Tivoli Storage Manager. User Response: None BKI7320I Start FLASHCOPY restore.
Explanation: For restore and inquire operation in conjunction with DP for IBM ESS for mySAP.com this parameter is mandatory. Without this parameter a restore using DP for IBM ESS for mySAP.com is not possible and DP for mySAP.com will continue to inquire/restore from the TSM server only. User Response: Add the parameter FCS_FILE to the DP for mySAP.com profile BKI7313W Inquire results from DP ESS mySAP.com are not available
Explanation: The restore uses data from ESS disks. User Response: None BKI7321E The DP ESS mySAP.com profile file name found in parameter FCS_FILE of the DP mySAP.com profile can not be used if you need to restore this backup.
Explanation: DP for mySAP.com was unable to retrieve information from DP for IBM ESS for mySAP.com about available backups on ESS disks. This message may be issued in consequence of message BKI7305E. User Response: Check the output from DP for IBM ESS for mySAP.com 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: In the DP for mySAP.com profile the FCS_FILE parameter is set, however the DP for IBM ESS for mySAP.com profile specified either v is not a DP for IBM ESS for mySAP.com profile v does not point to the same DP for IBM ESS for mySAP.com configuration file which was used by the preceding DP for IBM ESS for mySAP.com splitint operation. User Response: You need v to correct the FCS_FILE parameter thus a valid DP for IBM ESS for mySAP.com profile is used, e.g. the file DP for IBM ESS for mySAP.com had used when running its flashcopy function in the preceeding brbackup task (see preceeding message BKI7303W) to ensure that if different DP for IBM ESS for mySAP.com profiles are used, all use the same control file (the value of the IDS_CONTROL_FILE parameter in the DP for ESS profile) Request for a partial FLASHCOPY Restore or FLASHCOPY Restore with brrestore -m all is not supported. In case of brrestore attempt rerun with -m full.
Explanation: If a restore from ESS disks can not be finished successfully DP for mySAP.com tries to continue to restore data from the Tivoli Storage Manager server. But if the backup was performed on ESS disks only, the data can not be found on the TSM server. User Response: Check the output from DP for IBM ESS for mySAP.com prior to this error message to detect the root cause of this error and try again. BKI7316I The following backup types for the BACKUPID Backup ID have been found: - TSM - FLASHCOPY
BKI7322E
Explanation: The backup for the backup ID Backup ID was stored on the Tivoli Storage Manager as well as on ESS disks. For restore both data sources can be used. User Response: None. BKI7318E The DP ESS mySAP.com profile file name is not valid.
Explanation: DP for IBM ESS for mySAP.com 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 FLASHCOPY restore or FLASHCOPY restore with brrestore -m all is not supported. If you want to restore the backup: - with FLASHCOPY restore enter stop and rerun brrestore with -m full - from TSM enter cont
Explanation: The profile for DP for IBM ESS for mySAP.com specified in init<SID>.utl could not be accessed. User Response: Check the file name and the permissions for this file and try again.
Explanation: This message has the same reason as message BKI7322E, but in this case the data is also
830
IBM Tivoli Storage Manager: Messages
BKI7324E BKI8524E
available from the TSM server. So you may continue to restore this data without the flashcopy 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 FLASHCOPY restore of multiple backup IDs in one run is not possible. 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 data requested for this restore belongs to multiple backup IDs User Response: Make sure the files you want to restore belong to one single backup ID and try again. BKI7535W Error executing command command name. Reason: errno (error number) explanation.
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: 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: 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: The command command name is executed by the application. This message is followed by the output of the command executed. User Response: None BKI8511I The command is: command name.
Explanation: A command option requiring an argument was specified without an argument. User Response: Check the command syntax and correct the call. BKI8522E Invalid command command.
Explanation: This is an information message echoing the command. User Response: None. BKI8512I Return Code is: return code.
Explanation: backom was called with an invalid command. User Response: Check the command syntax and correct the call. BKI8523E Error during action.
Explanation: This message shows the return code of the Backup Object Manager. Valid return codes: 0 The requested action was performed successfully. 1 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. 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.
Explanation: An error occurred while performing the named action. User Response: Look for other error messages in order to analyze the problem. 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.
Chapter 10. Data Protection for mySAP.com for DB2 UDB
831
BKI8525E BKI8542E
BKI8525E The DB2 UDB instance name can consist of at most 8 characters. BKI8529E Invalid log sequence number. It must consist of the format log sequence format.
Explanation: The name given for the DB2 instance does not comply with the DB2 naming conventions. User Response: Correct the DB2 instance name and retry the action. BKI8526E The DB2 UDB database alias can consist of at most 8 characters.
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) and retry the action. BKI8530E File file name cannot be opened.
Explanation: The name given for the DB2 alias does not comply with the DB2 naming conventions. User Response: Correct the DB2 alias name and retry the action. BKI8527E Invalid node. It must consist of the format node format.
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. BKI8531E Directory file path does not exist or cannot be accessed.
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: Correct the DB2 node number and retry the action. BKI8528E Invalid timestamp. It must consist of 14 digits with format yyyymmddhhmmss or digits and wildcards * or ?.
Explanation: A file path cannot be accessed. 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. BKI8534E Command option command option is missing.
Explanation: The format of the timestamp is: yyyymmddhhmmss where: v yyyy is the year, specified as four digits, v v v v 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.
Explanation: A command was issued without specifying a required command option. User Response: Check the command syntax and correct the call. BKI8540I Using ProLE at host name:port number.
Explanation: The ProLe service named is used for the current action. User Response: None. BKI8541I Using profile profile path.
Any digits can be replaced by wildcards * or ?, where v * means any number of any digits, v ? means exactly one digit of any value. User Response: Correct the timestamp and retry the action.
Explanation: The profile named is used for the current action. User Response: None. 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.
832
IBM Tivoli Storage Manager: Messages
BKI8543I BKI8556E
User Response: Make sure that the profile is available at the location specified in option -e on the command line or in environment variable XINT_PROFILE. Check the attributes of the profile and the corresponding directory and make sure that the file can be accessed. BKI8543I Querying TSM for file(s) file list. BKI8550W 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. 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: The Backup Object Manager checks if the files listed are available on the TSM server(s) specified in the corresponding profile. User Response: None. BKI8545I 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: 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: 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. BKI8547I Using DB2_VENDOR_LIB lib path.
Explanation: After restoring raw or DB2 log file data, the target file could not be closed. User Response: Retry the action. BKI8553I Restore started with number session(s), number buffers and parallelism number.
Explanation: The library named is used for the current action. User Response: None. BKI8548I Elapsed time: time value.
Explanation: The DB2 database restore was started with a number of TSM sessions, a number of DB2 restore buffers and with a number of DB2 buffer manipulators writing data from the restore buffer pool into tablespace containers. User Response: None. BKI8555E Variable DB2DBDFT or command option alias is required.
Explanation: After restore and delete, the time elapsed during the action is displayed. User Response: None. BKI8549E Unable to create file file name.
Explanation: The password command needs the name/alias of the database, for which the DP for mySAP.com configuration file has to be adapted. User Response: Either set the environment variable DB2DBDFT or provide the command option alias with the password command and try again. BKI8556E Unable to get hostname.
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. Check the attributes of the target directory; write access is required. If the target file already exists, check that write access is granted
Explanation: The machines hostname could not be determined. User Response: Check the TCP/IP configuration of the machine.
Chapter 10. Data Protection for mySAP.com for DB2 UDB
833
BKI8557E BKI8805W
BKI8557E The config file configfile could not be created. User Response: Check if the alias specified does match to an entry in the DB2 system database directory. Further, check the argument for the Data Protection for mySAP.com profile keyword CONFIG_FILE and if necessary adapt it appropriately. BKI8800I The command is: command.
Explanation: The DP for mySAP.com configuration file configfile will be created, if it is not present at the location specified with the DP for mySAP.com profile keyword CONFIG_FILE. Either the parameter for CONFIG_FILE is wrong or the user does not have the appropriate permissions for creating the file. User Response: Check the CONFIG_FILE parameter and the users permissions and try again. BKI8558I Setting TSM password for partition on host hostname.
Explanation: Displays the Data Protection for mySAP.com command that was issued. The following commands are possible: Backup, Restore, Archive/Retrieve. User Response: None. BKI8801I PID of calling process: PID_number.
Explanation: The DP for mySAP.com TSM password will be set on host hostname for the DB2 partition partition. User Response: None. BKI8559W For partition switch to host hostname and issue the command again.
Explanation: Displays the process id of the DB2 process which called the Data Protection for mySAP.com shared library. User Response: None. BKI8802I Found number backup image(s) on TSM server.
Explanation: If the DP for mySAP.com profile keyword CONFIG_FILE points to a NFS mounted path on UNIX between all hosts (shared on Windows) in the DB2 ESE(EEE) environment, e.g. the instance home , the DP for mySAP.com configuration files can be adapted for all partitions simultaneously. Against it, if CONFIG_FILE points to a local path, only the configuration files for the local DB2 partitions will be adapted. User Response: If the TSM password(s) was/were successfully verified on one host, logon to the remaining hosts and issue the password command again. A recommendation is to put the DP for mySAP.com configuration files to a shared filesystem to avoid the administrative overhead. BKI8560E Partition number not found in the database configuration.
Explanation: For restore and delete operations Data Protection for mySAP.com queries TSM for backup images by means of a timestamp and shows the number of found images. User Response: None. BKI8803I The DB2 UDB backup image size for this session is about size.
Explanation: The estimated size of the data to be backed up is displayed. User Response: None. BKI8804W The recovery log could not be written.
Explanation: The DB2 partition number specified could not be found in the database configuration. User Response: Check the configuration of the DB2 ESE(EEE) environment (db2nodes.cfg, environment variable DB2NODE) and try again. BKI8561W Database alias not listed in the system database directory.
Explanation: After every backup or restore, Data Protection for mySAP.com 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: The database alias does not exist. Because there is a dependency between the alias and the settings for Data Protection for mySAP.com there might be problems during database backup or restore runs. Nevertheless, the Data Protection for mySAP.com configuration file (init<alias>.utl) will be created and adapted.
Explanation: During a restore, the user decided not to overwrite existing data. As a result, the action was cancelled User Response: None.
834
IBM Tivoli Storage Manager: Messages
BKI8810I BKI9205E
BKI8810I Cleaning up resources. Otherwise contact your Data Protection for mySAP.com support User Response: Contact Data Protection for mySAP.com support. BKI9201E BKI9000E System error: error Explanation: Data Protection for mySAP.com has found the following error: error. This is a catch-all error code for unpredictable system errors. User Response: Contact your service representative. BKI9001E Internal error: error Additional support information: An Exception was thrown at position: position.
Explanation: All resources used by Data Protection for mySAP.com will be released. User Response: None.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support User Response: Contact Data Protection for mySAP.com support. BKI9202E Additional support information: An Exception was thrown at position: position.
Explanation: Data Protection for mySAP.com has found the following internal error: error. User Response: Contact Data Protection for mySAP.com support. BKI9002E Error in stream task: %1$S
Explanation: There was an error in the processing of a data stream. Data Protection for mySAP.com will stop processing. User Response: Contact Data Protection for mySAP.com support. BKI9005E A not supported by B.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9203E Additional support information: An Exception was thrown at position: position.
Explanation: The installed version of product B does not support product A. Most likely you need to upgrade product B. User Response: Contact the Data Protection for mySAP.com support. BKI9006E Internal error while reading environment variable: variable.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support User Response: Contact Data Protection for mySAP.com support. BKI9204E Additional support information: An Exception was thrown at position: position (text=description).
Explanation: This is an internal error. User Response: Contact Data Protection for mySAP.com support. BKI9007W An error occurred while terminating the application: the error
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9205E Additional support information: Unable to instantiate name at position position.
Explanation: While terminating the application, an error occurred. This has no impact on the success of the operation. User Response: None BKI9200E Additional support information: An Exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support.
Explanation: This error message typically follows a previous error. If so this error message can be ignored.
Chapter 10. Data Protection for mySAP.com for DB2 UDB
835
BKI9206E BKI9300E
User Response: Contact Data Protection for mySAP.com support. BKI9206E Additional support information: Unable to use actual when expecting expected at position position. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9212E Additional support information: No handler registered for message type type. Thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9207E Additional support information: An Exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9213E Internal error: A memory allocation request failed at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9208E System error errno: errno text at position position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9219E Additional support information: Invalid error type typeencountered.
Explanation: A system call failed with errno. User Response: Check errno and errno text with you system administrator. If you cannot resolve the problem, contact Data Protection for mySAP.com support. BKI9209E Additional support information: No handler registered for message type message. Thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9220E Additional support information: Second call of call.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9210E ESD_AbortDispatchingException thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9300E Additional support information: Aborting send operation. See previous error.
Explanation: An internal error occurred. User Response: Contact Data Protection for mySAP.com support. BKI9211E Additional support information: An Exception was thrown at position: position. (State state)
Explanation: This error may have been caused by previous errors. User Response: Check for previous errors and correct them.
Explanation: This error message typically follows a previous error. If so this error message can be ignored.
836
IBM Tivoli Storage Manager: Messages
BKI9301E BKI9308E
BKI9301E Additional support information: State state does not match state pattern pattern. the same directory as BACKINT and has the same permission. Profile not specified. Please use 'backfm -p <ParFileName>' ! Explanation: Since Data Protection for mySAP.com File Manager calls Data Protection for mySAP.com, the profile for Data Protection for mySAP.com is required. User Response: Specify the full file name of the Data Protection for mySAP.com profile when starting Data Protection for mySAP.com File Manager, for example: backfm -p /oracle/C21/dbs/initC21.utl. BACKINT call was not successful! Explanation: The communication with the Tivoli Storage Manager server failed. User Response: Check that Data Protection for mySAP.com and the Tivoli Storage Manager server(s) work correctly. It must be possible to run Data Protection for mySAP.com directly from the command line, otherwise Data Protection for mySAP.com File Manager will also not work. Cannot open temporary file! Explanation: A temporary file could not be opened. This could have several reasons. User Response: UNIX Make sure the directory /tmp is not full and you have write permission for this directory.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9302E Additional support information: Unused ESD_ReturnChannel destroyed. Dumping callstack: callstack
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. 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 your Data Protection for mySAP.com support to analyze the cause of the problem. User Response: If you need to call Data Protection for mySAP.com 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
Windows Make sure that the current drive is not full. Unable to allocate memory! Unable to install SIGWINCH-handler! Unable to remove Backup IDs! Unable to install SIGINT-handler! Cant get window size! Explanation: These error messages indicate problems which usually cannot be resolved by the users themselves. User Response: Inform your system administrator or Data Protection for mySAP.com support about this problem.
Explanation: Data Protection for mySAP.com 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 Data Protection for mySAP.com support, provide the information given in this message together with the error information. BACKINT not found! Explanation: The executable BACKINT was not found. This executable is necessary to run Data Protection for mySAP.com File Manager. User Response: Make sure BACKFM is installed in
Chapter 10. Data Protection for mySAP.com for DB2 UDB
837
838
IBM Tivoli Storage Manager: Messages
Chapter 11. Data Protection for mySAP.com Technology for Oracle (BKI0000BKI9999)
This chapter describes the messages issued by Data Protection for mySAP.com Technology for Oracle. The messages begin with the prefix BKI and are listed in numerical order.
BKI0000E Profile not specified. BKI0008E The environment variable name is not set correctly. The current value is value.
Explanation: Data Protection for mySAP.com cannot locate the profile. User Response: Ensure that a profile is available. Note that the BACKINT call must have the following form: backint -p init<SID>.util . BKI0004E Function not defined.
Explanation: The value of the environment variable name is wrong. User Response: Set name to an appropriate value. BKI0020I End of program at: time
Explanation: SAPDBA, BRBACKUP, or BRARCHIVE passed an invalid argument to Data Protection for mySAP.com. User Response: Ensure that you have the correct version of SAPDBA, BRBACKUP, or BRARCHIVE installed. Valid functions are: -f backup or -f restore or -f password or -f delete or -f inquire. BKI0005I Start of program at: time
Explanation: Data Protection for mySAP.com returned control to SAPDBA, BRBACKUP, BRARCHIVE, or BRRESTORE at time. User Response: None. BKI0021I Elapsed time: elapsedtime
Explanation: The time needed for the complete backup was elapsedtime. User Response: None. BKI0023I Time: current_time Done: saved_bytes (percent) of bytes Estimated end time: end_time
Explanation: Data Protection for mySAP.com received control from SAPDBA, BRBACKUP, BRARCHIVE or BRRESTORE at time. User Response: None. BKI0006E Type for backup not defined [type]. Please use file or file_online.
Explanation: Data Protection for mySAP.com expects as backup type parameter only file or file_online. User Response: If you start Data Protection for mySAP.com manually to do a backup, ensure that the type option (-t) receives the correct arguments (file or file_online). If your Data Protection for mySAP.com 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) . BKI0007E Mode mode requires the environment variable environment variables to be set.
Explanation: Data Protection for mySAP.com 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 Data Protection for mySAP.com call will be completed at the estimated end_time. User Response: None. BKI0024I Return code is: return code
Explanation: Shows the return code of Data Protection for mySAP.com. 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
Explanation: Not all environment variables required have been set. At least environment variables where missing. User Response: Set the missing environment variables.
Copyright IBM Corp. 1993, 2004
839
BKI0030I BKI0055I
TSM Server: server name. Explanation: Data Protection for mySAP.com 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. User Response: None. BKI0030I Time: current_time Objects: current_num of total_num in process: file_name Size: bytes MB TSM Server: server name. BKI0050I 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. User Response: None. BKI0052E Password verification for node nodename on server server name failed.
Explanation: Data Protection for mySAP.com completed 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 Tivoli Storage Manager server server name is selected. User Response: None. BKI0031W Object not found or not accessible: objectname.
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 Objects: current_num of total_num done: file_name with: bytes saved with description object_desc.
Explanation: The object was not found or is not accessible to Data Protection for mySAP.com. User Response: Check path and name and the permissions of that object and try again. BKI0032E 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. User Response: Read the system error description.
Explanation: Data Protection for mySAP.com 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. User Response: None. BKI0054I Time: current_time Objects: current_num of total_num done: file_name with: bytes restored with description object_desc.
BKI0033E
Error opening file file name: system error description
Explanation: See BKI0032E. User Response: See BKI0032E. BKI0049I Please enter password for node nodename on server server name
Explanation: Data Protection for mySAP.com 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. User Response: None. BKI0055I Object objectname with size saved with description description.
Explanation: The password for the node nodename on the Tivoli Storage Manager server server name has to be entered for storing it in the Data Protection for mySAP.com configuration file. User Response: Enter the password for the corresponding Tivoli Storage Manager server.
Explanation: The object objectname was saved successfully. User Response: None.
840
IBM Tivoli Storage Manager: Messages
BKI0056I BKI0405I
BKI0056I Object objectname with size restored with description description. BKI0063E The UTL file file name is not valid.
Explanation: The object objectname was restored successfully. User Response: None. BKI0057I Time: current_time Object objectname with size saved with description description.
Explanation: Data Protection for mySAP.com is not able 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: The object objectname was saved successfully. User Response: None. BKI0058I Time: current_time Object objectname with size restored with description description.
Explanation: A Data Protection for mySAP.com option is invalid or unknown. User Response: Check the specified option(s) and try again. BKI0065E The argument is missing for option option.
Explanation: The object objectname was restored successfully. User Response: None. BKI0059E You have to set the environment variable DSMI_CONFIG to the full filename of the Tivoli Storage Manager client option file dsm.opt.
Explanation: Every Data Protection for mySAP.com option requires an argument. User Response: Insert the missing argument and try again. BKI0101I Session session: Please enter cont to continue or stop to cancel.
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: If Data Protection for mySAP.com 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 command parameter parameter for Data Protection for mySAP.com is unknown. User Response: Check the specified command parameter and try again. BKI0061W The output file file name is not valid.
Explanation: Data Protection for mySAP.com indicates the reply you made. User Response: None. BKI0311E Request canceled by user.
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.
Explanation: BACKINT terminated at users request. User Response: None BKI0400I TDP is waiting for BRBACKUP
Explanation: Data Protection for mySAP.com is waiting for BRBACKUP to set a tablespace in the begin/end backup mode. User Response: None.
Explanation: Data Protection for mySAP.com is not able to read the input file file name correctly. User Response: Check the path and name of the input file and the appropriate file access permission.
BKI0405I
TDP waited num_sec sec. for BRBACKUP in util_file_online communication.
Explanation: Data Protection for mySAP.com waited num_sec seconds for BRBACKUP to set a tablespace in begin/end backup mode.
Chapter 11. Data Protection for mySAP.com for Oracle
841
BKI0410E BKI0457E
User Response: None. BKI0410E Cannot open or delete switch file file name. Check permissions. BKI0451I This version of Data Protection for mySAP.com technology (R) will expire on date.
Explanation: If Data Protection for mySAP.com is not installed correctly (as the root user on UNIX or administrator group on Windows) then Data Protection for mySAP.com is not able to open the necessary communication file to the mySAP.com system. User Response: Check the file permission. BKI0411E Maximum time waiting for BRBACKUP expired.
Explanation: This is a test version that will expire on date. User Response: None. BKI0452E This version of Data Protection for mySAP.com technology (R) has expired.
Explanation: This is a test version that has expired. User Response: Order a release version of Data Protection for mySAP.com or contact your IBM/Tivoli Sales Representative. BKI0453W This version of Data Protection for mySAP.com technology (R) will expire in number days.
Explanation: The SAP database utilities did not respond within the expected time. User Response: Contact your mySAP.com administrator. BKI0412E BRBACKUP wasnt able to switch requested tablespace in BEGIN/END BACKUP mode.
Explanation: This is a test version with a time limit. It will expire in number days. User Response: Order a release version of Data Protection for mySAP.com or contact your IBM/Tivoli Sales Representative before the version expires. BKI0454I *** This copy is NOT FOR RESALE. ***
Explanation: Data Protection for mySAP.com 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. User Response: Contact your mySAP.com administrator. BKI0413E Error while requesting tablespace switch.
Explanation: This version is not for resale. User Response: None. BKI0455E License file file name does not exist.
Explanation: BRBACKUP could not switch tablespace in BEGIN or END backup mode. User Response: Contact your mySAP.com administrator. BKI0414E Error while requesting tablespace switch.
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: BRBACKUP reported an error while trying to switch a tablespace in BEGIN or END backup mode. User Response: Contact your mySAP.com administrator. BKI0450I Version 2 restore: file
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.
Explanation: A restore of data backed up with Data Protection for mySAP.com version 2 was executed. User Response: None.
842
IBM Tivoli Storage Manager: Messages
BKI0459E BKI1011W
BKI0459E More than one mux file is found with the same name detailed backup description. BKI1005W The tracefile name trace_filename should be absolute.
Explanation: Two or more data sources with name detailed backup description exist. User Response: Contact your Data Protection for mySAP Technology administrator. BKI1000E Syntax error in line line: statement
Explanation: None. User Response: Specify an absolute tracefile name, for example /oracle/C21/saptrace/tracefile . BKI1006E The SERVERNAME must be less than max_char characters.
Explanation: The statement statement in the Data Protection for mySAP.com profile is unknown or incorrect. User Response: Correct the error and try again.
Explanation: You have used a SERVERNAME with more than max_char characters. User Response: Use a shorter SERVERNAME. BKI1007E The NODENAME must be less than max_char characters.
BKI1001E
Syntax error in file file name. Exiting Program.
Explanation: Data Protection for mySAP.com has detected an syntax error in the file file name and stops any action. User Response: Correct the error(s) in the file file name and try again. BKI1002E BACKUPIDPREFIX must be number_of_characters characters.
Explanation: You have used a NODENAME with more than max_char characters. User Response: Use a shorter NODENAME. BKI1008E The MANAGEMENTCLASSNAME must be less than max_char characters.
Explanation: You have used a MANAGEMENTCLASSNAME with more than max_char characters. User Response: Use a shorter MANAGEMENTCLASSNAME. BKI1009W Please set MULTIPLEX to a number between 1 and max_multiplex. Now it is set to act_multiplex.
Explanation: The length of BACKUPIDPREFIX must be number_of_characters characters. User Response: Enter a BACKUPIDPREFIX with the required length (e.g., SAP___, BKI___). BKI1003W Please set REDOLOG_COPIES to a number between 1 and max_copies. Now it is set to act_copies.
Explanation: Data Protection for mySAP.com currently supports 1 to 9 copies of offline redo log files. User Response: Adapt the REDOLOG_COPIES settings in the Data Protection for mySAP.com profile. BKI1004W You should specify the BACKUPIDPREFIX before the TRACEFILE statement, so that the BACKUPIDPREFIX can be used in the tracefile name.
Explanation: You have set multiplexing to an unsupported number. Data Protection for mySAP.com 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 BKI1011W The sortfile name sortfile_filename should be absolute.
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 Data Protection for mySAP.com profile (e.g., SAP___, BKI___).
Explanation: None. User Response: Specify an absolute file name, for example /oracle/C21/dbs/sortfile.
Chapter 11. Data Protection for mySAP.com for Oracle
843
BKI1012E BKI1023W
BKI1012E The configfilename configuration_filename could not be opened. BKI1017E The server server name is already defined. Please use another name!
Explanation: Data Protection for mySAP.com is unable to read the file 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. BKI1013E Profile not found or permissions denied: profile_filename.
Explanation: The server you want to configure is already defined. User Response: Specify another server name. Server names have to be unique. BKI1019E Failed to respond to a message received from XINT.
Explanation: This messages indicates an internal error. User Response: Contact Data Protection for mySAP.com technology support. BKI1020 The compress info file file name should be absolute !
Explanation: Data Protection for mySAP.com is unable to open the profile profile_filename. User Response: Ensure that the SAP backup profile init<SID>.sap contains a valid entry util_par_file for the Data Protection for mySAP.com profile. Furthermore, this file must be readable by Data Protection for mySAP.com. BKI1014I The parameter PERF_MONITOR is no longer supported. Now it is enabled by default.
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 ProLE terminates the connection due to a previous error.
Explanation: For version 2.7 or later of Data Protection for mySAP.com, the Performance Monitor of the Administration Assistant can be used by default. Therefore, the profile parameter PERF_MONITOR is no longer needed. User Response: None. BKI1015I The parameter BACKAGENT is no longer needed.
Explanation: A fatal error has occurred which caused a shutdown of the communication channel between the ProLE process and this application. User Response: Look for previous error messages to detect the root cause of the problem. BKI1022E ProLE terminates the connection due to a previous error.
Explanation: See message BKI1021E. User Response: See message BKI1021E. BKI1023W Could not establish connection to log server log server name.
Explanation: For version 2.7 or later of Data Protection for mySAP.com, only one executable, called BACKINT, will be provided and needed. The former executable, called BACKAGENT, will no longer be supported or needed. User Response: None. BKI1016W The trace file name file name could not be opened for writing!
Explanation: In the Data Protection for mySAP.com technology 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 Data Protection for mySAP.com 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. User Response: Ensure that you have specified a correct path for the trace file.
844
IBM Tivoli Storage Manager: Messages
BKI1200E BKI1210E
BKI1200E Cannot read/write file: file name. User Response: Define at least as many different Archive Management Classes as redo log copies requested. BKI1206W 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: Data Protection for mySAP.com is unable to read or write a data file (file name) of a tablespace being backed up or restored. User Response: Check the file access permission of the affected file(s). Try again. If the problem still exists, contact the mySAP.com administrator. BKI1201E There are no Tivoli Storage Manager Servers available.
Explanation: Data Protection for mySAP.com cannot locate a Tivoli Storage Manager server. User Response: Install and specify at least one Tivoli Storage Manager server in the Data Protection for mySAP.com profile (keyword SERVER). BKI1202E You must specify either MAX_SESSIONS or all off MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS and MAX_RESTORE_SESSIONS
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 Directory backup not supported
Explanation: This option is not yet available. User Response: Wait for a future release of Data Protection for mySAP.com, which supports this option. BKI1208W The object file name will be retried [retry_num]
Explanation: There is a setup error with the SESSIONS parameters within the Data Protection for mySAP.com profile. User Response: Specify either MAX_SESSIONS and one of the more specific parameters MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS or MAX_RESTORE_SESSIONS or all of the three specific session parameters without the MAX_SESSIONS parameter. BKI1203E Not enough sessions available (number of sessions required and number of sessions available).
Explanation: There was an error with the object file_name. Data Protection for mySAP.com will try to save/restore the object one retry_num times. User Response: Look at the error messages in the Data Protection for mySAP.com protocol and correct the error for the next run. BKI1209E Object not found or not accessible objectname.
Explanation: Data Protection for mySAP.com cannot locate the Oracle object objectname. User Response: The backup integrity is affected. Contact the SAP or Data Protection for mySAP.com support. BKI1210E Input file not found or not accessible file name.
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 Data Protection for mySAP.com 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: Data Protection for mySAP.com cannot locate the temporary file file name. This file contains the list of Oracle objects to be backed up/restored. It is passed to Data Protection for mySAP.com by BRBACKUP, BRARCHIVE or BRRESTORE. User Response: Ensure that you have the correct version of SAPDBA, BRBACKUP, BRARCHIVE or BRRESTORE installed. See Prerequisites for the Installation of Data Protection for mySAP.com in the Data Protection for mySAP.com Technology Installation & Users Guide for Oracle.
Explanation: Data Protection for mySAP.com 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 copies (parameter REDOLOG_COPIES).
Chapter 11. Data Protection for mySAP.com for Oracle
845
BKI1211E BKI2002E
BKI1211E There is something wrong with your CONFIG_FILE file name. BKI1222E Version missmatch error. Check setup (%1$S:%2$S).
Explanation: There is a problem with your Data Protection for mySAP.com configuration file setup. User Response: Check the file permission and the file name specified in the Data Protection for mySAP.com profile keyword CONFIG_FILE. BKI1212W The file file name was not found in the manual sorting file.
Explanation: The version numbers of the installed executables BACKINT and ProLE do not match. User Response: Check your setup or contact Data Protection for mySAP.com support. BKI1223W A problem occurred during send of performance data to Administration Assistant .
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. BKI1213I Program ended with code = return code
Explanation: There was a problem sending the performance data to the Administration Assistant over the network. User Response: Check your setup or contact Data Protection for mySAP.com support. BKI1224W Unable to initialize connection to Administration Assistant.
Explanation: The return code of the program is displayed. User Response: None. BKI1214E TSM Error: error text
Explanation: There was a problem initializing the connection to the Administration Assistant over the network. User Response: Check your setup or contact Data Protection for mySAP.com support. BKI1227I Average compression factor was number.
Explanation: The specified TSM error occurred. User Response: Check error text and correct the problem. BKI1215I Average transmission rate was number GB/h (number MB/sec).
Explanation: The data transferred had been compressed by the factor number. User Response: None BKI2000I Successfully connected to ProLE on port portnumber.
Explanation: The average transmission rate is displayed. User Response: None. BKI1216E There are no BRBACKUPMGTCLASSES available.
Explanation: The BRBACKUPMGTCLASSES 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. BKI1217E There are no BRARCHIVEMGTCLASSES available.
Explanation: One of the Data Protection for mySAP.com modules BACKINT or the backup library libtdp_r3 initiated a successful connection to the background process ProLE on port portnumber. User Response: None. BKI2001E Socket error while connecting to ProLE: reason.
Explanation: The Data Protection for mySAP.com background process ProLE is not running. User Response: Start ProLE manually and try again. BKI2002E No valid callback function of type func_type supplied.
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.
Explanation: Internal Data Protection for mySAP.com error User Response: Contact Data Protection for mySAP.com support.
846
IBM Tivoli Storage Manager: Messages
BKI2003I BKI2018E
BKI2003I File file_name, BID deleted. BKI2010E Error occurred processing FRONTEND
Explanation: The file file_name with the backup ID BID was deleted from the Tivoli Storage Manager. User Response: None. BKI2004E Connection to ProLE lost.
Explanation: An error occurred during the frontend processing. User Response: Check the frontend script/program and the settings in the Data Protection for mySAP.com profile (keyword FRONTEND) and try again. BKI2011E Error occurred processing BACKEND.
Explanation: During Data Protection for mySAP.com operation the connection to ProLE was lost. Network problems could be the reason. User Response: Check your network environment and if ProLE is still running and try again. BKI2005E Illegal parameter in message from ProLE. Exiting...
Explanation: An error occurred during the backend processing. User Response: Check the backend script/program and the settings in the Data Protection for mySAP.com profile (keyword BACKEND) and try again. BKI2012E Passwords do not match. Try again.
Explanation: This error occurs if the versions of ProLE and the executable BACKINT or the backup library libtdp_r3 do not match. User Response: Check the versions of ProLE and BACKINT/backup library libtdp_r3 you are currently using. BKI2006E General exception in dispatcher. Exiting...
Explanation: The first and second password you entered do not match. User Response: Enter the password correctly. BKI2013I Starting FRONTEND Program.
Explanation: The frontend program is executing. User Response: None. BKI2014I FRONTEND program finished.
Explanation: Internal Data Protection for mySAP.com error. User Response: Contact Data Protection for mySAP.com support. BKI2007E Unknown Port: port
Explanation: The frontend program is finished. User Response: None. BKI2015I Starting BACKEND program.
Explanation: The port specified for communication between ProLE and BACKINT is unknown. User Response: Check the port value specified when ProLE was started. Additionally, check the environment variable PROLE_PORT for the BACKINT environment. These two values must match. BKI2008E Unable to connect to ProLE.
Explanation: The backend program is executing. User Response: None. BKI2016I BACKEND program finished.
Explanation: The backend program is finished. User Response: None. BKI2017I Blocksize is set to num_bytes bytes.
Explanation: Internal Data Protection for mySAP.com error. User Response: Contact Data Protection for mySAP.com support. BKI2009I Deleting all versions with version number <= version_number on server server_name.
Explanation: The operational blocksize of Data Protection for mySAP.com is num_bytes bytes. User Response: None. BKI2018E Exception in main message loop: description
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. User Response: None.
Explanation: An error occurred during processing. The error may contain a descriptive text. User Response: Contact your service representative.
Chapter 11. Data Protection for mySAP.com for Oracle
847
BKI2019E BKI4002E
BKI2019E Socket error while connecting to ProLE on port number for tracing: description BKI2026E Unexpected exception in handler: handler
Explanation: This is an internal error. User Response: Contact Data Protection for mySAP.com support. BKI2027I Using TSM-API version your api version (compiled with compiled with version).
Explanation: During processing, a socket error occurred on port number. description may contain the system error text. User Response: Check the description. If the error persists, contact your service representative. BKI2020E Error occurred for trace connection to ProLE on port number.
Explanation: Version information about the TSM-API. User Response: None BKI2028W Unable to terminate session session.
Explanation: The network connection that is used for tracing generated an error on port number. User Response: Contact your service representative. BKI2021E Unable to delete file file name: description
Explanation: This is an internal error during cleanup that has no effect on the success of the service. User Response: None BKI4000W The attributes of file file name cannot be restored. Reason: errno (error_num) error_desc.
Explanation: Unable to delete the file file name. description may contain the system error text. User Response: Check the description. If the error persists, contact your service representative. BKI2022E Unable to change mode of file file name: description
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. BKI4001E File file name cannot be created. Reason: errno (error_num) error_desc.
Explanation: Unable to change mode of file file name. description may contain the system error text. User Response: Check the description. If the error persists, contact your service representative. BKI2023E Error occurred during trace connection to ProLE. Tracing will stop now.
Explanation: Error occurred during trace connection to ProLE. User Response: Tracing will stop. If the problem persists, contact your service representative. BKI2024E Error in connection to ProLE.
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. User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future. Furthermore, check the write permission of the user who started the restore. BKI4002E Error during restore of file file name. Reason: errno (error_num) error_desc.
Explanation: The connection to ProLE terminated unexpectedly. This message might be displayed due to previous errors or after an unexpected termination of the ProLE process. User Response: Check for other error messages and restart ProLE if necessary. Try again. If the problem persists, contact Data Protection for mySAP.com support. BKI2025E Failed to respond to a message received from ProLE.
Explanation: An error occurs during the restore process of the file file name. User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future.
Explanation: This is an internal error User Response: Contact Data Protection for mySAP.comsupport.
848
IBM Tivoli Storage Manager: Messages
BKI4003E BKI5006E
BKI4003E Error reading file file name. Only read num_bytes out of all_bytes. BKI4009E Not enough space to write file file name. Possible reasons: disk full or ulimit exeeded.
Explanation: An error occurs reading the file file name. Only num_bytes of all_bytes could be read. User Response: Try your last action again. If the error still exists, contact Data Protection for mySAP.com support. BKI4004E Error writing file filename. Only wrote num_bytes out of all_bytes.
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. User Response: Contact your system administrator. BKI5000E Tivoli Storage Manager Error: error_message
Explanation: An error occurs writing the file file name. Only num_bytes of all_bytes could be written. User Response: Try your last action again. If the error still exists, contact Data Protection for mySAP.com support. BKI4005E Error allocating memory block for file file name. BLOCKSIZE may be too large.
Explanation: During a connection of Data Protection for mySAP.com 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. BKI5001E Tivoli Storage Manager Error: error_message
Explanation: Data Protection for mySAP.com was not able 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 of Data Protection for mySAP.com. BKI4006E Error allocating memory block for file file name. BLOCKSIZE may be too large.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5002E Tivoli Storage Manager Error: error_message
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5003E Tivoli Storage Manager Error: error_message
Explanation: See BKI4005E. User Response: See BKI4005E. BKI4007E File filename cannot be read. Reason: errno(errno number) errno text.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5004E Tivoli Storage Manager Error: error_message
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. User Response: Contact your system administrator. BKI4008E File filename cannot be opened. Reason: errno(errno number) errno text.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5005E Tivoli Storage Manager Error: error_message
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5006E Tivoli Storage Manager Error: error_message
Explanation: Data Protection for mySAP Technology could not open the file file namedue to some system specific problems. User Response: Contact your system administrator.
Explanation: See BKI5000E. User Response: See BKI5000E.
Chapter 11. Data Protection for mySAP.com for Oracle
849
BKI5007E BKI7051E
BKI5007E Tivoli Storage Manager Error: error_message BKI5015W Data description could not be restored, because it was backed up with a newer version (objInf=support information)
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5008E Tivoli Storage Manager Error: error_message
Explanation: The TSM server hosts backups (i.e. data description) which were made with a new version of backint. Backint ignores this data in the further processing. User Response: Upgrade backint BKI7001E Backup file file name already exists.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5009E Tivoli Storage Manager Error: error_message
Explanation: This is an RMAN internal error. User Response: See your Oracle documentation or contact your Oracle database administrator. BKI7002E Bad mode specified.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5010E Tivoli Storage Manager Error: error_message
Explanation: This is an RMAN internal error. User Response: See your Oracle documentation or contact your Oracle database administrator. BKI7012E Invalid arguments during call of function.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5011E Tivoli Storage Manager Error: error_message
Explanation: This is an RMAN internal error. User Response: See your Oracle documentation or contact your Oracle database administrator. BKI7020E Bad handle rman_handle during call of function.
Explanation: See BKI5000E. User Response: See BKI5000E. BKI5012E Cannot open TSM API message text file. Check if DSMI_DIR is set correctly. Current value of DSMI_DIR is: value
Explanation: This is an RMAN internal error. User Response: See your Oracle documentation or contact your Oracle database administrator. BKI7021E Bad flags during call of function.
Explanation: The TSM-API could not be initialized. User Response: Correct the value of the environment variable DSMI_DIR. BKI5013E Value for name is too long. Current value: value
Explanation: This is an RMAN internal error. User Response: See your Oracle documentation or contact your Oracle database administrator. BKI7049I The default ProLE port will be used.
Explanation: The value of the environment variable name has too many digits. User Response: Check if the variable is set correctly. BKI5014E Tivoli Storage Manager Error: error_message
Explanation: The port for the internal communication of Data Protection for mySAP.com is set during installation. The message indicates that this port is being used. User Response: None. BKI7051E The environment variable XINT_PROFILE is not set. It must be set and contain the full qualified path to the *.utl file to be used.
Explanation: See BKI5000E. User Response: See BKI5000E.
Explanation: The way Data Protection for mySAP.com works is specified in a profile. When called, Data
850
IBM Tivoli Storage Manager: Messages
BKI7053E BKI7308E
Protection for mySAP.com looks for the environment variable XINT_PROFILE which must contain the fully qualified path to the profile. User Response: Check the environment for XINT_PROFILE of the user who started Data Protection for mySAP.com. BKI7053E Service setup failed due to previous error. mySAP.com log file for further detailed messages. BKI7303W Profiles for DP ESS mySAP.com are different. backup: file name restore: file name
Explanation: The initialization of Data Protection for mySAP.com failed due to previous errors. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7055E Service open failed due to previous error in data mover.
Explanation: During backup the profile used by DP for IBM ESS for mySAP.com can be determined automatically. For restore and inquire operations the profile for DP for IBM ESS for mySAP.com must be specified in the profile using the parameter FCS_FILE. For restore DP for IBM ESS for mySAP.com must use the same profile as for backup. User Response: Correct the entry for the FCS_FILE parameter in the profile (init<SID>.utl). BKI7304I Performing DISK ONLY backup
Explanation: The Data Protection for mySAP.com command could not be started due to previous errors. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7056E Service open failed because configured TSM server could not be accessed.
Explanation: The data for this backup is stored on ESS disks only and will not be sent to TSM. User Response: None BKI7305E Error during call to DP ESS mySAP.com: error message
Explanation: The Data Protection for mySAP.com command could not be started because the TSM server defined in the profile could not be accessed. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7057E Service open failed because all configured sessions are currently in use.
Explanation: DP for IBM ESS for mySAP.com 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 ESS disks or to ESS disks only, restore of data which is available on both TSM and ESS disks or on ESS disks only) 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 IBM ESS for mySAP.com to determine the cause of the problem and try again. BKI7307W DP ESS mySAP.com reported an error during FLASHCOPY operation. Do you want to continue to backup to TSM?
Explanation: The Data Protection for mySAP.com command could not be started because all configured sessions in the profile are currently in use. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7058E Service open failed because more than one file is found with the same name.
Explanation: The Data Protection for mySAP.com command could not be started because two or more files with the same name were found. User Response: Check the Data Protection for mySAP.com log file for further detailed messages. BKI7059E Service open failed because cause the file is not found.
Explanation: The backup was requested to be stored on both the TSM server and the ESS disks. The flashcopy operation to ESS disks 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 ESS disks only and did not finish successfully. User Response: Check the output from DP for IBM ESS for mySAP.com prior to this error message to detect the root cause of this error and try again.
Explanation: The Data Protection for mySAP.com command could not be started because a file specified was not found. User Response: Check the Data Protection for
Chapter 11. Data Protection for mySAP.com for Oracle
851
BKI7309W BKI7321E
BKI7309W DP ESS mySAP.com reported an error during FLASHCOPY operation. Do you want to continue to restore from TSM? BKI7314E The data you want to restore is not available on the TSM server.
Explanation: The data you wanted to be restored is located on the TSM server and ESS disks. The flashcopy operation from ESS disks has failed. The process can continue to restore data from the TSM server. 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. BKI7310W DP ESS mySAP.com reported an error during FLASHCOPY operation. CAUTION: Not all filesystems are available. Do you want to retry the operation?
Explanation: If a restore from ESS disks can not be finished successfully DP for mySAP.com tries to continue to restore data from the Tivoli Storage Manager server. But if the backup was performed on ESS disks only, the data can not be found on the TSM server. User Response: Check the output from DP for IBM ESS for mySAP.com prior to this error message to detect the root cause of this error and try again. BKI7316I The following backup types for the BACKUPID Backup ID have been found: - TSM - FLASHCOPY
Explanation: In contrast to message BKI7309W not all filesystems are mounted. In this case it is not possible to continue the restore from the TSM server. User Response: Enter stop if you want to terminate this restore process. Enter cont if you want to retry the flash copy process. BKI7311I Profile used by DP ESS mySAP.com:
Explanation: The backup for the backup ID Backup ID was stored on the Tivoli Storage Manager as well as on ESS disks. For restore both data sources can be used. User Response: None. BKI7318E The DP ESS mySAP.com profile file name is not valid.
Explanation: The message shows the name of the profile used by DP for IBM ESS for mySAP.com User Response: None BKI7312W Profile for DP ESS mySAP.com not specified in profile. For restore this must be specified
Explanation: The profile for DP for IBM ESS for mySAP.com 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 FLASHCOPY restore.
Explanation: For restore and inquire operation in conjunction with DP for IBM ESS for mySAP.com this parameter is mandatory. Without this parameter a restore using DP for IBM ESS for mySAP.com is not possible and DP for mySAP.com will continue to inquire/restore from the TSM server only. User Response: Add the parameter FCS_FILE to the DP for mySAP.com profile BKI7313W Inquire results from DP ESS mySAP.com are not available
Explanation: The restore uses data from ESS disks. User Response: None BKI7321E The DP ESS mySAP.com profile file name found in parameter FCS_FILE of the DP mySAP.com profile can not be used if you need to restore this backup.
Explanation: DP for mySAP.com was unable to retrieve information from DP for IBM ESS for mySAP.com about available backups on ESS disks. This message may be issued in consequence of message BKI7305E. User Response: Check the output from DP for IBM ESS for mySAP.com to determine the cause of the error and try again.
Explanation: In the DP for mySAP.com profile the FCS_FILE parameter is set, however the DP for IBM ESS for mySAP.com profile specified either v is not a DP for IBM ESS for mySAP.com profile v does not point to the same DP for IBM ESS for mySAP.com configuration file which was used by the preceding DP for IBM ESS for mySAP.com splitint operation. User Response: You need
852
IBM Tivoli Storage Manager: Messages
BKI7322E BKI9006E
v to correct the FCS_FILE parameter thus a valid DP for IBM ESS for mySAP.com profile is used, e.g. the file DP for IBM ESS for mySAP.com had used when running its flashcopy function in the preceeding brbackup task (see preceeding message BKI7303W) to ensure that if different DP for IBM ESS for mySAP.com profiles are used, all use the same control file (the value of the IDS_CONTROL_FILE parameter in the DP for ESS profile) Request for a partial FLASHCOPY Restore or FLASHCOPY Restore with brrestore -m all is not supported. In case of brrestore attempt rerun with -m full. 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. User Response: None BKI9000E System error: error
BKI7322E
Explanation: Data Protection for mySAP.com has found the following error: error. This is a catch-all error code for unpredictable system errors. User Response: Contact your service representative. BKI9001E Internal error: error
Explanation: DP for IBM ESS for mySAP.com 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 FLASHCOPY restore or FLASHCOPY restore with brrestore -m all is not supported. If you want to restore the backup: - with FLASHCOPY restore enter stop and rerun brrestore with -m full - from TSM enter cont
Explanation: Data Protection for mySAP.com has found the following internal error: error. User Response: Contact Data Protection for mySAP.com support. BKI9002E Error in stream task: %1$S
Explanation: There was an error in the processing of a data stream. Data Protection for mySAP.com will stop processing. User Response: Contact Data Protection for mySAP.com support. BKI9003E Incompatible components installed: component name component name
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 flashcopy 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 FLASHCOPY restore of multiple backup IDs in one run is not possible.
Explanation: The components mentioned in the message text can not be used together. This may be the result of an incomplete upgrade. User Response: Contact DP for mySAP.com support. BKI9005E A not supported by B.
Explanation: The data requested for this restore belongs to multiple backup IDs User Response: Make sure the files you want to restore belong to one single backup ID and try again. BKI7535W Error executing command command name. Reason: errno (error number) explanation.
Explanation: The installed version of product B does not support product A. Most likely you need to upgrade product B. User Response: Contact the Data Protection for mySAP.com support. BKI9006E Internal error while reading environment variable: variable.
Explanation: This is an internal error. User Response: Contact Data Protection for mySAP.com support.
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.
Chapter 11. Data Protection for mySAP.com for Oracle
853
BKI9007W BKI9207E
BKI9007W An error occurred while terminating the application: the error BKI9203E Additional support information: An Exception was thrown at position: position.
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: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support User Response: Contact Data Protection for mySAP.com support. BKI9204E Additional support information: An Exception was thrown at position: position (text=description).
Explanation: The version of the application product name is not supported by this application. Most likely application product name needs to be upgraded. User Response: Contact DP for mySAP.com support. BKI9009W The following products are not compatible: product name (product version) and product name (product version).
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9205E Additional support information: Unable to instantiate name at position position.
Explanation: This message is similar to BKI9008E. But in this case its not obvious which one of the products needs to be upgraded. . User Response: Contact DP for mySAP.com support BKI9200E Additional support information: An Exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9206E Additional support information: Unable to use actual when expecting expected at position position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support User Response: Contact Data Protection for mySAP.com support. BKI9201E Additional support information: An Exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9207E Additional support information: An Exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support User Response: Contact Data Protection for mySAP.com support. BKI9202E Additional support information: An Exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support.
854
IBM Tivoli Storage Manager: Messages
BKI9208E BKI9218E
BKI9208E System error errno: errno text at position position. User Response: Contact Data Protection for mySAP.com support. BKI9214E Additional support information: An exception was thrown from a destructor. Callstack follows: callstack.
Explanation: A system call failed with errno. User Response: Check errno and errno text with you system administrator. If you cannot resolve the problem, contact Data Protection for mySAP.com support. BKI9209E Additional support information: No handler registered for message type message. Thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9215E Additional support information: An exception was thrown at position: positien.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9210E ESD_AbortDispatchingException thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9216E Additional support information: An exception was thrown at position: positien.
Explanation: An internal error occurred. User Response: Contact Data Protection for mySAP.com support. BKI9211E Additional support information: An Exception was thrown at position: position. (State state)
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9212E Additional support information: No handler registered for message type type. Thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9217E Additional support information: An exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9213E Internal error: A memory allocation request failed at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9218E Additional support information: An exception was thrown at position: positien.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support.
Chapter 11. Data Protection for mySAP.com for Oracle
855
BKI9219E BKI9308E
BKI9219E Additional support information: Invalid error type typeencountered. User Response: If you need to call Data Protection for mySAP.com 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: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9220E Additional support information: Second call of call.
Explanation: Data Protection for mySAP.com 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: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9300E Additional support information: Aborting send operation. See previous error.
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 Data Protection for mySAP.com support, provide the information given in this message together with the error information. BACKINT not found! Explanation: The executable BACKINT was not found. This executable is necessary to run Data Protection for mySAP.com File Manager. User Response: Make sure BACKFM is installed in the same directory as BACKINT and has the same permission. Profile not specified. Please use 'backfm -p <ParFileName>' ! Explanation: Since Data Protection for mySAP.com File Manager calls Data Protection for mySAP.com, the profile for Data Protection for mySAP.com is required. User Response: Specify the full file name of the Data Protection for mySAP.com profile when starting Data Protection for mySAP.com File Manager, for example: backfm -p /oracle/C21/dbs/initC21.utl. BACKINT call was not successful! Explanation: The communication with the Tivoli Storage Manager server failed. User Response: Check that Data Protection for mySAP.com and the Tivoli Storage Manager server(s) work correctly. It must be possible to run Data Protection for mySAP.com directly from the command line, otherwise Data Protection for mySAP.com File Manager will also not work.
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.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. BKI9302E Additional support information: Unused ESD_ReturnChannel destroyed. Dumping callstack: callstack
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your Data Protection for mySAP.com support. User Response: Contact Data Protection for mySAP.com support. 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 your Data Protection for mySAP.com support to analyze the cause of the problem.
856
IBM Tivoli Storage Manager: Messages
Cannot open temporary file! Explanation: A temporary file could not be opened. This could have several reasons. User Response: UNIX Make sure the directory /tmp is not full and you have write permission for this directory.
Windows Make sure that the current drive is not full. Unable to allocate memory! Unable to install SIGWINCH-handler! Unable to remove Backup IDs! Unable to install SIGINT-handler! Cant get window size! Explanation: These error messages indicate problems which usually cannot be resolved by the users themselves. User Response: Inform your system administrator or Data Protection for mySAP.com support about this problem.
Chapter 11. Data Protection for mySAP.com for Oracle
857
858
IBM Tivoli Storage Manager: Messages
Chapter 12. Data Protection for EMC Symmetrix for mySAP.com Technology (IDS0000IDS0999)
This chapter describes the messages issued by Data Protection for EMC Symmetrix for mySAP.com Technology. The messages begin with the prefix IDS and are listed in numerical order.
IDS0000E Profile not specified value in the profile for TDP for Symmetrix. IDS0009E Directory path <path> for the IDS control file does not exist.
Explanation: TDP for Symmetrix cannot locate the profile. User Response: Ensure that a profile is available. Note that the idscntl call must have the following form: <path>/idscntl -p <path>/init<SID>.fcs -f <function>.... IDS0001E Function not defined
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. IDS0010E Option -i <backup_list> not specified.
Explanation: An invalid argument has been specified for the -f option of TDP for Symmetrix. User Response: Ensure that you pass a valid function name with the option -f. Valid functions are: split, synchronize, unmount, password and inquire. IDS0004E Subfunction not defined.
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 backup when you call the function -f split. Note that the idscntl call must in this case have the following form: <path>/idscntl -p <path>/init<SID>.fcs -f split -i <backup_list> ... When the split function runs under the control of the R/3 DBA tool brbackup by means of the split_cmd statement of the R/3 DBA profile, you must ensure that the correct syntax is used there (e.g. ... -i $). brbackup replaces the $ character with the name of the list file. IDS0011E Option -f <function> not specified.
Explanation: An invalid argument has been specified for the -s option of TDP for Symmetrix. This option has been designed for internal idscntl use only and should not be used externally. User Response: Do not use the -s option with the idscntl call. IDS0005I Start of idscntl program at: time.
Explanation: TDP for Symmetrix started at time. User Response: None. IDS0007I End of idscntl program at: time.
Explanation: idscntl always requires the option -f <function> with a valid function. User Response: Ensure that the idscntl call has the following form: <path>/idscntl -p <path>/init<SID>.fcs -f <function>.... IDS0014I <subsystem message>
Explanation: TDP for Symmetrix ended at time. Control will be returned to either the shell or to brbackup when idscntl was called by brbackup based on the entries split_cmd and resync_cmd in the brbackup profile (e.g., init<SID>.sap) User Response: None. IDS0008E Parameter <keyword> in the profile file required.
Explanation: TDP for Symmetrix received an information message from the IDS subsystem. User Response: None. IDS0015W <subsystem message>
Explanation: The parameter <keyword> in the profile for TDP for Symmetrix could not be found. It must be defined. User Response: Set the parameter <keyword> and its
Copyright IBM Corp. 1993, 2004
Explanation: TDP for Symmetrix received a warning message from the IDS subsystem. User Response: None.
859
IDS0016E IDS0035I
IDS0016E <subsystem message> IDS0032W Information from TDP for R/3 was not found.
Explanation: TDP for Symmetrix received an error message from its IDS control part. User Response: See the subsystem error messages for more information and perform required action. IDS0024I Exiting with return code <rc>.
Explanation: The exchange data between TDP for Symmetrix and TDP for R/3 was not found during the execution of one of the functions synchronize or unmount. Either the TDP for R/3 you have installed does not support TDP for Symmetrix, or TDP for R/3 has failed after splitting the BCV/STD pairs. User Response: Check the run logs of brbackup. This error could have various reasons and should be resolved depending on the specific situation: Case 1: brbackup has finished successfully. Result: The backup on disks (BCVs) as well as the one done to the TSM server is valid. However, TDP for Symmetrix cannot show the BACKUPID in its report when using the function inquire. Reason for warning: It is very likely that TDP for R/3 does not have TDP for Symmetrix support (prior to version 3.1.0.3). Action: Install the appropriate TDP for R/3. Case 2: brbackup has terminated abnormally. Result: Check carefully the run log of brbackup for any BKI, ANS or ANR error messages. Most likely, the backup on disks (BCVs) is valid (check with idscntl -f inquire whether PSI is PSI_MOUNT_DONE or PSI_UNMOUNT_DONE), but the backup to the TSM server is invalid. Cause: Any problems with the network or on the TSM server caused TDP for R/3 running a backup to fail. Action: Depending on the error message, eliminate the reason for not getting a successful backup to the TSM server. IDS0033I Information from TDP for R/3 has been found with BACKUPID <backupid>.
Explanation: The idscntl program issues this message on terminating. The program returns the value 0, or nonzero if the execution of the called function failed. User Response: If the called function has failed, check for previous error messages. IDS0025I Time stamp: <current_time>
Explanation: TDP for Symmetrix performs several tasks in sequence (e.g. split BCVs on the production system and mount file systems on the backup system). Tracking the various time stamps allows analysis of how long each task took. User Response: None. IDS0026I Start of idscntl on the production system ...
Explanation: TDP for Symmetrix has issued a call to the production system and is waiting for the end of the execution. User Response: None. IDS0027I idscntl ended on the production system successfully.
Explanation: TDP for Symmetrix has ended the call to the production system successfully. User Response: None. IDS0030I Split started ...
Explanation: The command for the split of the BCVs has been issued on the production system, and the program idscntl waits until this action has finished. User Response: None. IDS0031I Split successful.
Explanation: The exchange data between TDP for R/3 and TDP for Symmetrix has been found during the execution of one of the functions synchronize or unmount. The backup on disks (BCVs) as well as to the TSM server is valid. The list of files has been saved in the Tivoli Storage Manager with the BackupID <backupid>. User Response: None. IDS0035I The IDS control file exists and a new backup cycle entry has been created.
Explanation: The command for the split of the BCVs has terminated successfully on the production system. User Response: None.
Explanation: At the start of the function -f split, TDP for Symmetrix inserts a record in the IDS control file for the new backup cycle. This record will be updated as the status of the new backup cycle changes (e.g. BCVs getting mounted, unmounted, synchronized). User Response: None.
860
IBM Tivoli Storage Manager: Messages
IDS0038I IDS0052I
IDS0038I The IDS control file <ids_control_file> does not exist. It will be created. backup host. A list of mount points or disk groups (VxVM) will be shown. User Response: None. IDS0047I End of listing.
Explanation: TDP for Symmetrix will write the first record to the IDS control file specified in the entry IDS_CONTROL_FILE of the profile. User Response: None. IDS0039E The IDS control file has no entry.
Explanation: Corresponds to start message IDS0046I. User Response: None.
Explanation: TDP for Symmetrix has found the IDS control file, but it has no records. This error occurs when you start one of the functions inquire, synchronize or unmount before you have run the split function for the first time. User Response: After you run at least one brbackup with a successful split, the problem will be resolved. IDS0043I The maximum number of backup cycles in the IDS control file has been reached.
IDS0048E
The progress status indicator cannot be PSI_MOUNT_DONE when you call the function split.
Explanation: TDP for Symmetrix has found that the progress status indicator of the latest backup cycle already has a value of PSI_MOUNT_DONE. This indicates that the file systems are still mounted when a new STD/BCV split is requested. User Response: Run the synchronize or unmount function and try again. IDS0050E The version of the idscntl program must be the same on the backup and production systems.
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. User Response: None. IDS0044I Delete backup cycle with BSEQ_N = <bseq_n> and all associated files ...
Explanation: The version of TDP for Symmetrix on the production system is different from the version on the backup system. User Response: Ensure that you install the same version of TDP for Symmetrix on the production and backup systems. You get the version number when you start idscntl without parameters. IDS0051I Enter the password for the user <user ID>
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. User Response: None. IDS0045W 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. IDS0046I Start of listing of importing disk groups/mounting file systems ...
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 TDP for Symmetrix program idscntl uses the user ID to execute a remote shell on the production system. User Response: Enter the password for the corresponding user ID. IDS0052I Enter the password for the user <user ID> again
Explanation: In order to avoid typing errors, you have to enter the password twice. User Response: Enter the password again.
Explanation: After splitting the STD/BCV pairs on the production system, TDP for Symmetrix will make the corresponding target resources (BCVs) available to the
Chapter 12. Data Protection for EMC Symmetrix for mySAP.com Technology
861
IDS0053I IDS0067E
IDS0053I The password entry does not match, please try again HOST_BACK in profile wrong or missing. Explanation: Either TDP for Symmetrix is unable to read one of the parameters LOGON_HOST_PROD/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> <user ID> LOGON_HOST_BACK <hostname> The hostnames must match the respective hostnames of the production and backup systems. The user ID specified must match the oracle DBA user ID (ora<sid>). User Response: Ensure that the profile contains valid entries for LOGON_HOST_PROD and LOGON_HOST_BACK. IDS0064E The parameter <keyword> in the profile is not known.
Explanation: The two entered passwords are not identical. You must enter the password again. User Response: Enter the password again. You are permitted three attempts before the program terminates. IDS0054E No password stored.
Explanation: The two entered passwords are not identical. You have tried three times, and the passwords were different in each case. User Response: You must start the idscntl program with the function -f password again. If no password is stored, or it is invalid, idscntl fails when the split function is used. IDS0055E The config file named <config_file> could not be opened for reading/writing.
Explanation: TDP for Symmetrix is unable to read the configuration file <config_file>. 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. IDS0060I Start of listing of deporting disk groups/unmounting file systems ...
Explanation: An unknown parameter <keyword> has been found in the profile. User Response: Check the specified parameter in the profile and try again. IDS0065W The progress status indicator (PSI) is already PSI_SYNCHRONIZED.
Explanation: You cannot run the synchronize/unmount function multiple times without having done a brbackup with a split request. Doing this will cause warnings. It might be that a previous split request failed due to network problems and the synchronization could therefore not be done. User Response: Make sure you run a brbackup with the function -f split prior to using the TDP for Symmetrix functions unmount or synchronize. IDS0066E The option -f split can only be used on the backup system.
Explanation: Before synchronizing the STD/BCVs pairs, TDP for Symmetrix will disable the corresponding resources from the backup host. A list of unmount points or deporting disk groups (VxVM) will be shown. User Response: None. IDS0062I The progress status indicator (PSI) is already PSI_UNMOUNT_DONE.
Explanation: You cannot start the split function on the production system. User Response: Make sure you start idscntl with the function -f split on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK. IDS0067E The options -f split -s performsplit can only be used on the production system.
Explanation: TDP for Symmetrix has been called with the function synchronize or unmount, but the PSI value of the latest backup cycle was already updated to PSI_UNMOUNT_DONE in a previous idscntl call. User Response: None. IDS0063E Parameters LOGON_HOST_PROD/LOGON_
Explanation: The option -s was designed for internal idscntl use only and should not be used externally. User Response: Make sure you start idscntl -f split on the backup system only. Ensure that the profile contains valid entries for LOGON_HOST_PROD and
862
IBM Tivoli Storage Manager: Messages
IDS0068E IDS0304E
LOGON_HOST_BACK. Do not use the -s option with the idscntl call. IDS0068E The option -f synchronize can only be used on the backup system. <LOG_TRACE_DIR>/idscntl_p_<time>.trace, <config_file>, <ids_control_file> or the field value EXCHANGE_FILE in a backup cycle record. User Response: Check the access permissions of the affected file and try again. IDS0302E The environment variable <env_var> must be set.
Explanation: You cannot start the function synchronize on the production system. User Response: Make sure you start idscntl with the function -f synchronize on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK. IDS0069E The option -f unmount can only be used on the backup system.
Explanation: The environment variable <env_var> is required. The following environment variables must be set when running TDP for Symmetrix: ORACLE_HOME: to the home directory of the user ID ORACLE_SID: to the R/3 Oracle DB system ID User Response: Set the missing environment variable and try again. IDS0303E The environment variable <env_var> is not correct.
Explanation: You cannot start the function unmount on the production system. User Response: Make sure you start idscntl with the function -f unmount on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK. IDS0070I Checking and if necessary synchronizing STD/BCV pairs.
Explanation: At this point, idscntl checks on the production system for the availability of synchronized STD/BCV pairs. If the pairs are not yet synchronized, idscntl will synchronize them at this point. However, this will take much more time than if the synchronization had been initiated on the backup system before running the brbackup that started a split request via the split_cmd statement. User Response: Avoid this type of late synchronization in a brbackup run and synchronize the BCVs with the STDs before starting brbackup or within brbackup via the resync_cmd statement. IDS0300E Cannot read file: <filename>.
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. IDS0304E File not found or not accessible: <filename>.
Explanation: The file <filename> was not found or is not accessible to TDP for Symmetrix. The affected files could be: <ORACLE_HOME>/dbs/init<SID>.fcs or the argument value of the option -i (that file contains the list of files to backup). User Response: Check path, name and the permissions of the file and try again.
Explanation: TDP for Symmetrix is unable to read the data file <filename>. The affected files could be e.g.: <ORACLE_HOME>/dbs/init<SID>.fcs, the argument value of the option -i (file containing the list of files to back up), <config_file>, <ids_control_file> or the field value of EXCHANGE_FILE in a backup cycle record. User Response: Check the access permissions of the affected file and try again. IDS0301E Cannot write file: <filename>.
Explanation: TDP for Symmetrix is unable to write to the data file filename. The affected files could be e.g.: <LOG_TRACE_DIR>/idscntl_b_<time>.log, <LOG_TRACE_DIR>/idscntl_p_<time>.log, <LOG_TRACE_DIR>/idscntl_b_<time>.trace,
Chapter 12. Data Protection for EMC Symmetrix for mySAP.com Technology
863
864
IBM Tivoli Storage Manager: Messages
Chapter 13. Data Protection for Enterprise Storage Server for mySAP.com Technogy for DB2 UDB (EEP0020EEP7900) and (IDS1000IDS2999)
This chapter describes the messages issued by Data Protection for ESS for mySAP.com Technology for DB2 UDB. The messages begin with the prefix EEP or IDS and are listed in numerical order.
EEP0020I ====>Performing DP FOR ESS <v1> command. EEP0059E The database was backed up using NOCOPY type of FlashCopy. The data in the target ESS volumes is not valid, and cannot be used to perform a FlashBack Restore.
Explanation: This message is displayed starting the specified function. User Response: None. EEP0022I AIX Version: <var1> Oslevel: <var2>.
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: Displays AIX version and oslevel. User Response: None. EEP0023I ESS CopyServices CLI Version: <var1>.<var2>.
Explanation: Displays ESS CopyServices CLI version. User Response: None. EEP0030I Number of ESS Volumes to be FlashCopied: <v1>
Explanation: Number of ESS volumes to be FlashCopied. User Response: None. EEP0056I Received error errno while disabling the new resources.
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 orginal source LUNs. User Response: The source / target information in the setup file cannot be modified. In order to backup the database to different target LUNs, use a different setup file. If you want to restore the database to a new location, restore it from the Tivoli Storage Manager server. EEP0065E IBM2105 Copy Service CLI is not installed.
Explanation: An error occurred when the process attempted to disable the resources obtained for performing the DB backup. User Response: Check the error log for details. EEP0058I Received error errno while resetting the target volumes.
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. EEP0066W 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: An error occurred when the process attempted to withdraw the FlashCopy relationship between the source and target volumes. User Response: Check the error log for details.
Explanation: Incremental FlashCopy is only supported on ESS Microcode and CopyServices CLI versions 2.3.0
Copyright IBM Corp. 1993, 2004
865
EEP0067W EEP0124I
or later. As this version of ESS CopyServices CLI is lower than 2.3.0, an incremental FlashCopy cannot be performed. User Response: Upgrade to ESS microcode and CopyServices CLI version 2.3.0 or later in order to take advantage of the incremental FlashCopy feature. EEP0067W WARNING!!! Incremental Change Recording is enabled. Performing incremental FlashCopy instead of COPY type of FlashCopy. 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 ESS volumes to target ESS volumes in case of backup or from target ESS volumes to source ESS volumes in case of restore. User Response: None. EEP0120E A null logical volume has been detected.
Explanation: Incremental Change Recording is enabled. Performing a copy type of FlashCopy will fail in this case. User Response: 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. EEP0068W WARNING!!! Incremental Change Recording is enabled. Performing incremental FlashCopy instead of NOCOPY type of FlashCopy.
Explanation: DP for ESS could not 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 A null volume group has been detected.
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 ESS volumes for this database, using the DP for ESS 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: DP for ESS could not determine a volume group 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.. 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 The physical volumes of the volume group <v1> were not found.
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. EEP0070E Some of the ESS volumes belonging to this database have Incremental Change Recording enabled while others do not.
Explanation: DP for ESS will issue the command lsvg -M <vgname> in an LVM mirror environment to determine the physical and logical volumes on which the production database is residing. This command failed. User Response: Check the return code of lsvg. Consult the AIX system documentation. EEP0124I Mounting filesystem : fs1.
Explanation: In order to perform an incremental FlashCopy, all the ESS volumes belonging to the database must have change recording enabled. User Response: Withdraw the FlashCopy relationships for those ESS volumes that have Incremental Change Recording enabled, using the DP for ESS withdraw command, and then retry the command. In the case of the monitor command (FlashCopy agent), withdraw the
Explanation: Currently attempting to mount the file system. User Response: None
866
IBM Tivoli Storage Manager: Messages
EEP0125E EEP0139W
EEP0125E The serial number for the device logdev could not be found. device is a member of an active volume group. Check for preceding errors. EEP0130W Removing the mount point directory <mntpt1> failed with rc: <rc1>.
Explanation: DP for ESS will determine the ESS volumes serial numbers from the list of database files passed. In order to do that, several system command will be used such as: lscfg -pvl devname or lsvpcfg or rsList2105s.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...
Explanation: An error occurred while trying to remove a mount point. Processing continues. User Response: None. EEP0131E The physical volume ID <pvid1> is duplicate on the production machine.
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: v If the hdisks with the same pvid belong to the same multipath, convert the ESS 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 issuing the AIX chdev command with the following arguments: chdev -l hdisk# -a pv=clear EEP0132W The umount command failed with rc <rc> for mount point <mntpt>.
Explanation: Currently trying to find a target device to match with the source device. User Response: None. EEP0127I Removing device : devname
Explanation: DP for ESS 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 ESS volumes. User Response: None EEP0128E Configuring the target volume would cause duplicate physical volume ID : pvid1
Explanation: An error occurred while trying to remove a mount point. Processing continues. User Response: None. 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: A different set of target volumes that were previously associated with the same source volumes was detected. User Response: Perform one of the following: 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 disk- remove 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.
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. User Response: None. EEP0139W Removing the file system on the mount point <mntpt1> failed with rc: <rc1>.
Explanation: DP for ESS will remove the logical devices from the Device Configuration database (ODM) on the backup system after the backup ended and prior to the withdraw of the relationships of the ESS volumes. The rmdev command has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check if the
Explanation: An error occurred while trying to remove a file system during the FlashBack Restore. Processing continues. The restore will resolve this problem.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
867
EEP0140I EEP0156I
User Response: None. 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. 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. User Response: Check the specific error message. Consult the AIX system documentation.. EEP0151E Varying off volume group vgname failed.
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. User Response: None. EEP0143E Unsupported volume group <v1> has been detected.
Explanation: Prior to the withdraw of the ESS FlashCopy relationships, DP for ESS will vary off the database volume group on the backup system. The command varoffvg has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors during the unmount process. EEP0152I Removing volume group fnm1 ....
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: Attempting to remove the volume groups. User Response: None. EEP0153I Varied off and exported volume group : vgname.
Explanation: A physical disk from the specified database volume group was not found in the Device Configuration database. User Response: Check the specific error message. Consult the AIX system documentation. Check if this device is a member of one active volume group. Check for preceding errors.. EEP0147I Exporting volume group vgname failed.
Explanation: The specified volume group was varied off and exported successfully. User Response: None EEP0154I <lvname> <copy> <pv> <serialno> <status>
Explanation: DP for ESS will issue the command exportvg prior to the withdraw of the ESS FlashCopy relationships to remove the volume group from the Device Configuration database. This command has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors during the unmount of the file systems. EEP0148I Importing volume groups now...
Explanation: Finding the source volumes of the production database in an LVM mirror environment, DP for ESS 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. User Response: None. EEP0156I Finding the serial numbers ...
Explanation: Processing an importing volume group command. User Response: None EEP0149I Newly imported volume group: vgname
Explanation: DP for ESS 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
Explanation: DP for ESS has successfully imported this new volume group on the backup system after the FlashCopy. User Response: None
868
IBM Tivoli Storage Manager: Messages
EEP0161E EEP0178I
EEP0161E No volume group was found. User Response: Check why you have stale partitions. If necessary, synchronize the logical volumes of the production database. EEP0172E Logical volume lvname must have mirror write consistency on.
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. User Response: Check the operating system error issued by lsvg. Consult the AIX documentation. EEP0164E Quorum of the volume group vgname must be off.
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 ESS requires that this capability be set for the logical volumes of the production database. User Response: Set mirror write consistency on. EEP0174E None of the mirror copies of the logical volume lvname resides completely on the specified ESS identifier.
Explanation: In a high-availability LVM mirror environment, DP for ESS 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. EEP0166E Logical volume vgname must have at least 2 copies.
Explanation: DP for ESS requires that all the partitions of one mirror set must reside on the physical volumes of one ESS. User Response: You have to reconfigure the allocation on the production system. EEP0176E Some of the partitions of lvname are stale on the specified ESS identifier.
Explanation: If the parameter for working with LVM mirrors is active, DP for ESS requires that two copies of each logical volume exist. User Response: Create a copy of each logical volume on separate ESS machines. Ensure that you have for each source volume a target volume for the FlashCopy in the same ESS and, for microcode level V1, in the same LSS. EEP0168E Logical volume lvname must have the parallel scheduling policy.
Explanation: DP for ESS 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 ESS that was chosen for the FlashCopy on this specific run must be free of stale partitions. User Response: Check the reason you have stale partitions. Synchronize the logical volumes of the production database. EEP0178I Could not determine the number of paths to target volumes. Using default value of 1.
Explanation: DP for ESS 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 ESS supports SDD (Subsystem Device Driver). SDD is a pseudo device driver designed to support the multipath configuration environments in the IBM ESS and is used to enhance data availability. DP for ESS will determine the number of multiple paths queryng the Device Configuration database (ODM). User Response: If you want to use the advantage of SDD, check the Subsystem Device Driver Users Guide for a correct configuration.
Explanation: DP for ESS 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 ESS that was chosen for the FlashCopy on this specific run must be free of stale partitions.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
869
EEP0180E EEP0290E
EEP0180E Failure in changing the mount point mp, return code rc from command chfs. User Response: You have to reconfigure your production database. EEP0191I Varying on volume group vgname failed.
Explanation: In a high-availability LVM mirror environment, DP for ESS 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 ESS must remove it by calling the command chfs to the original names. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors. EEP0182E The same hdisk devname cannot be associated with two different vpaths (serial numbers serial#1 and serial#2).
Explanation: Post to the importvg or recreatevg, DP for ESS will vary on the database volume group on the backup system. The command varonvg has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors. EEP0272I Flushing the buffers to disk...
Explanation: Currently synchronizing to force the buffers to disk. User Response: None EEP0273I Unmounting the file system mntpt1...
Explanation: DP for ESS has 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. EEP0184E lsvg command failed.
Explanation: Currently attempting to unmount the file system from the mount point. User Response: None EEP0274I Bringing up the volume groups...
Explanation: DP for ESS uses the command lsvg to determine the physical and logical volume of the volume group. This command has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors. EEP0186I Recreating the new volume groups...
Explanation: The new resources will be available after the FlashCopy. User Response: None EEP0275I There are too many file systems.
Explanation: The number of file systems exceeds compiled limit of 4096. User Response: You have to reconfigure your production database. EEP0290E The source volume with serial number serial # is no longer attached to the production system.
Explanation: In a high-availability LVM mirror environment, DP for ESS will use the recreatevg command to create the volume groups after the FlashCopy on the backup system. User Response: None EEP0188E lvm queryvg failed.
Explanation: DP for ESS uses the system routine lvm_queryvg to read information of the VGDA of the volumes. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors. EEP0190E The number of new volume groups is limited to 256.
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 ESS Web 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 ESS volumes.
Explanation: DP for ESS can support a database with maximum 256 volume groups.
870
IBM Tivoli Storage Manager: Messages
EEP0291E EEP0302E
EEP0291E The source volume with serial number serial # belongs to another volume group. 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: 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, DP for ESS 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 ESS volumes. EEP0292W The logical volume lvname on the mount point mp was renamed or newly added.
Explanation: DP for ESS 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 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 ESS hdisk device volume group vgname to a Subsystem Device Driver vpath device volume group.
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. User Response: DP for ESS 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 ESS 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: For the function FlashCopy backup, DP 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 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: Prior to the start of the FlashBack Restore, DP for ESS will display a list of all the file systems which are currently on production database system. User Response: None EEP0294I List of file systems which will be restored...
Explanation: For the function FlashBack Restore, DP for ESS 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. User Response: Check the return code and the error 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 ESS volumes. EEP0302E DP for ESS encountered a problem when using the FlashCopy function of the ESS Copy Services.
Explanation: Prior to the start of the FlashBack Restore, DP for ESS will display a list of all the file systems that were on production database system at the time of the FlashCopy backup. User Response: None 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 ESS will call this command during the FlashBack Restore to
Explanation: DP for ESS requested, for a set of ESS source/target volume pairs, that a FlashCopy 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, DP for ESS will provide the return code and then terminate.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
871
EEP0303E EEP0311W
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 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. 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 ESS volumes. EEP0307I Removing copies from the logical volumes ...
Explanation: On the backup system after the FlashCopy, DP for ESS 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.
Explanation: For 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 actual FlashCopy reverse. User Response: None EEP0308I Removing physical volumes from the volume groups ...
Explanation: The reducevg command removes physical volumes from a volume group. DP for ESS 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 on the ESS 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 on the ESS that is not yet involved in the FlashCopy User Response: Check the return code and the error message of the reducevg command. Consult the AIX system documentation. EEP0305W The extendvg command cmd ended with return code rc.
Explanation: For the function FlashBack Restore, after the rmlvcopy and prior to the exportvg and the actual FlashCopy reverse, DP for ESS will use the command reducevg to remove the physical volumes residing on the second ESS. 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 ESS will add the physical volumes residing on the second ESS to the database volume groups. User Response: None EEP0310I Adding copies to the logical volumes ...
Explanation: The extendvg command adds physical volumes to a volume group. DP for ESS will call it to add the volumes which reside on the ESS that is not yet involved in the FlashBack to the database volume groups. User Response: Check the return code and the error message of the extendvg command. Consult the AIX system documentation. EEP0306W The mklvcopy command cmd ended with return code rc.
Explanation: On the function FlashBack Restore, DP for ESS will use the command mklvcopy to add the copies of the logical volumes on the second ESS. 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. User Response: Check the return code and the error message of the specified command. Consult the AIX system documentation.
Explanation: DP for ESS will call the command mklvcopy to add a copy of a logical volume on the physical volumes residing on the second ESS. 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. User Response: Check the return code and the error
872
IBM Tivoli Storage Manager: Messages
EEP0312E EEP0322W
EEP0312E Importing the volume group from hdisk logdev failed. These will be restored by means of FlashBack. User Response: None. EEP0317W One or more errors were found disabling the production system resources. However, the FlashBack Restore will continue.
Explanation: DP for ESS 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. User Response: Check the return code and the error message of the importvg command. Consult the AIX system documentation. EEP0313E Recreating the volume group from the hdisks hdisks failed.
Explanation: This message will appear if, when running the function FlashBack Restore, an error occurs unmounting the existing file systems and removing the volume groups. However, DP for ESS will continue with the FlashBack Restore. User Response: None. 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.
Explanation: DP for ESS will use the 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 ESS where the FlashCopy was issued. User Response: Check the return code and the error message of the recreatevg command. Consult the AIX system documentation. EEP0314W Removing the logical device logdev with the same PVID pvid in the ODM.
Explanation: The output of the command lspv shows 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: There is still another 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: 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 ESS 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. EEP0322W The major number of the volume group <vgname> could not be determined.
Explanation: This message will appear if 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 contain currently any file system.
Explanation: This message will appear if, when running the function FlashBack Restore, no file system was found on the original database volume group. Following this, DP for ESS will display a list of the file systems that reside on the FlashCopy target volumes.
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.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
873
EEP0323W EEP0356E
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. 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. EEP0353E Unable to open file file1.
Explanation: DP for ESS 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. EEP0324E Production database does not reside on an LVM mirror environment.
Explanation: An error was detected when trying to open the file. The file may not exist. User Response: Make sure the file exists. EEP0354I Performing <fctype> FlashCopy of source ESS volume <src1> to target ESS volume <tgt1>
Explanation: A FlashCopy from the source volume to the target volume was requested. User Response: None. EEP0355E The ESS FlashCopy command failed.
Explanation: The LVM mirroring capability of DP for ESS 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. EEP0350E Error to get the size of the target volume src1 with return code rc1.
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 Enterprise Storage Server administrator to obtain the appropriate level of Copy Services command line interface and microcode. EEP0356E Cannot find a target volume to match with the source volume parm1.
Explanation: The ESS query command cannot determine the size of the target volume. 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. 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 Logical Subsystem (LSS) (unless microcode level V2 or above is used). 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. EEP0352E Wrong volume size for the target volume tgt1 is specified in the setup file.
Explanation: A target volume could not be found. User Response: If using microcode level V1, make sure the target volumes reside in the same Logical Subsystem (LSS) as the source volumes. Also, make sure that the target volumes are available to the backup system and that 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
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
874
IBM Tivoli Storage Manager: Messages
EEP0357I EEP0369E
EEP0357I Performing FlashCopy withdraw of source ESS volume <src1> from target ESS volume <tgt1> EEP0363I Primary Copy Services server is ready.
Explanation: The primary Copy Services server is ready. User Response: None EEP0364I The connection to the primary Copy Services server failed. The process continues to check the backup Copy Services server.
Explanation: A FlashCopy withdraw of the source volume from the target volume was requested. User Response: None. EEP0358E No target volume is available. Terminating......
Explanation: No target volume was found. User Response: If using microcode level V1, make sure the target volumes reside in the same Logical Subsystem (LSS) as the source volumes. Also, make sure that the target volumes are available to the backup system and that 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 EEP0359I Incremental Change Recording: <val1>
Explanation: The primary Copy Services server is not available. Verify that the TCP/IP connection is valid. User Response: None EEP0365I Checking the status of the backup Copy Services server...
Explanation: Currently verifying the backup Copy Services server status. User Response: None EEP0366I FlashCopy was performed with <parm1> option.
Explanation: Value of Incremental Change Recording. User Response: None. EEP0360I Querying the ESS for the size of volume volser1...
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 ESS overrides this value under certain conditions. User Response: None. EEP0367I Source and Target ESS 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.
Explanation: A query of the target volume was requested. User Response: None EEP0361I 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. User Response: None EEP0362I Checking the status of the primary Copy Services server...
Explanation: Whenever user performs an incremental FlashBack Restore operation, the source and target ESS volumes will be reversed. User Response: None. EEP0368I The backup Copy Services server is ready...
Explanation: The backup Copy Services server is ready. User Response: None EEP0369E Both the primary Copy Services server and the backup Copy Services server are not available...
Explanation: Currently verifying the primary Copy Services server status. User Response: None
Explanation: The primary Copy Services server and the backup Copy Services server are not available.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
875
EEP0370E EEP7366E
User Response: Use the ESS Copy Service Web Interface to verify that the TCP/IP connection is valid for both Copy Services servers. Also, verify that the ESS is configured correctly. EEP0370E A Copy Services backup server has not been specified. Exiting... 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 An invalid value: <parm1> has been specified for FlashCopy type.
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 connection is valid for the backup Copy Services server. Also, verify that the ESS is configured correctly on the backup Copy Services server. EEP0371I Value of FlashCopy type is: <parm1>.
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 ESS for pending sectors for volume: <volser1>
Explanation: None. User Response: None. EEP0372I A primary Copy Services server has not been specified.
Explanation: A query of all the source and target volumes was requested to ensure that background copy is not in progress between them. User Response: None. EEP0400E Error on running command: parm1
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 ESS for the status of volumes volser1...
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: 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 Error: ESS volumes are involved in a FlashCopy or a PPRC operation.
Explanation: Not enough memory was available to continue processing. User Response: Ensure that your system has sufficient real and virtual memory. Close unnecessary applications. EEP0640E Could not open trace file <v1>.
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. EEP0376E Error: ESS target volume v1 involved in the previous backup does not exist in the setup file.
Explanation: There were some problems opening tracefile. Make sure you can open the trace file which was specified in the setup file. User Response: None. EEP0641E Could not create the trace object.
Explanation: There was a problem creating the trace class object. User Response: None. EEP7366E Unable to close trace output file <file-name>.
Explanation: The list of target volumes specified in the setup file for restoring a specified database using FlashBack Restore need 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
Explanation: An error occurred during the closing of a trace output file-name (for example, not enough disk space).
876
IBM Tivoli Storage Manager: Messages
EEP7367E IDS1016E
User Response: Check the specific operating system error message. EEP7367E Unable to write to trace file <tracefile>. Tracing disabled. IDS1008E Parameter <keyword> in the profile file required.
Explanation: The parameter <keyword> in the profile for DP for ESS could not be found. It must be defined. User Response: Set the parameter <keyword> and its value in the profile for DP for ESS. IDS1009E Directory path <path> for the IDS control file does not exist.
Explanation: An error occurred when writing to the specified tracefile. User Response: Ensure the device for the tracefile is available and has sufficient space for the file. Retry the command. EEP7826E Unable to open trace output file <file-name>.
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 DP for ESS 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. IDS1000E Profile 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 idscntl call must in this case have the following form: <path>/idscntl -p <path>/init<SID>.fcs -f getresources -i <backup_list> ... IDS1011E Option -f <function> not specified.
Explanation: DP for ESS cannot locate the profile. User Response: Ensure that a profile is available. Note that the idscntl call must have the following form: <path>/idscntl -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 ESS. User Response: Ensure that you pass a valid function name with the option -f. Valid functions are: withdraw, flashcopy, password, unmount, inquire, and query. IDS1004E Subfunction not defined.
Explanation: idscntl always requires the option -f <function> with a valid function. User Response: Ensure that the idscntl call has the following form: <path>/idscntl -p <path>/init<SID>.fcs -f <function>.... IDS1014I <subsystem message>
Explanation: An invalid argument has been specified for the -s option of DP for ESS. This option has been designed for internal idscntl use only and should not be used externally. User Response: Do not use the -s option with the idscntl call. IDS1005I Start of idscntl program at: time.
Explanation: DP for ESS received an information message from the IDS subsystem. User Response: None. IDS1015W <subsystem message>
Explanation: DP for ESS received a warning message from the IDS subsystem. User Response: None. IDS1016E <subsystem message>
Explanation: DP for ESS started at time. User Response: None. IDS1007I End of idscntl program at: time.
Explanation: DP for ESS ended at time. Control will be returned to either the shell or to tdpessdb2 when idscntl was called by tdpessdb2. User Response: None.
Explanation: DP for ESS received an error message from its IDS control part. User Response: See the subsystem error messages for more information and perform required action.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
877
IDS1016E
IDS1016E Neither the primary nor the backup ESS server has been specified. IDS1016E The logical volume <logical volume> must have at least 2 copies.
Explanation: Neither the SHARK_SERVERNAME_PRIMARY nor SHARK_SERVERNAME_BACKUP parameter has been specified in the DP for ESS profile (init<SID>.fcs). User Response: Ensure that the profile contains entries for SHARK_SERVERNAME_PRIMARY and SHARK_SERVERNAME_BACKUP and that their values form a valid TCP/IP address. IDS1016I(E) The ESS primary server is down or has an invalid address. Explanation: The ESS primary server with the TCP/IP address specified in the parameter SHARK_SERVERNAME_PRIMARY is down or cannot be reached. User Response: If this message appears as a information message, SHARK_SERVERNAME_BACKUP was specified and the connection will be made via its TCP/IP address. Otherwise, this message will appear as an error. Ensure that the profile contains entries for SHARK_SERVERNAME_PRIMARY and SHARK_SERVERNAME_BACKUP and their values form a valid TCP/IP address. IDS1016E There is a problem with both ESS copy services.
Explanation: DP for ESS requires that each logical volume making up the production database have at least 2 copies. User Response: Add an AIX copy for the displayed logical volume. IDS1016E The logical volume <logical volume> must have the parallel scheduling policy.
Explanation: DP for ESS requires that the property scheduling policy of a logical volume be set to parallel. User Response: Set the scheduling policy property to parallel. IDS1016W The logical volume <lv name> has <# of stale partitions> stale partitions.
Explanation: DP for ESS issues a warning if one of the logical volumes has stale partitions, independent of whether or not it resides on the selected ESS. User Response: Check why the system has stale partitions. Check the AIX error log. Synchronize the AIX mirror copies. IDS1016E Some of the partitions of <logical volume> are stale on the specified ESS <ESS id>.
Explanation: Neither the connection to the ESS primary server nor the one to the ESS backup server is working properly. User Response: Ensure that the profile contains entries for SHARK_SERVERNAME_PRIMARY and SHARK_SERVERNAME_BACKUP and their values form a valid TCP/IP address. Contact your ESS administrator. IDS1016E None of the mirror copies of <logical volume> resides completely on the specified ESS <ESS id>.
Explanation: The displayed logical volume has one copy residing completely on the specified ESS id, but this copy contains some stale partitions. In this case, DP for ESS will end immediately. User Response: Check why the system has stale partitions. Synchronize the AIX mirror copies. IDS1016E The logical volume <lv name> must have mirror write consistency set to yes.
Explanation: All existing copies of the displayed logical volume are spread over physical volumes that reside on multiple ESS units. User Response: Check the LVM mirroring configuration of the production database and ensure that each AIX mirror copy resides on a separate ESS. IDS1016E Quorum of the volume group <volume group> must be off.
Explanation: DP for ESS requires that the property mirror write consistency of a logical volume be set to yes. User Response: Set the property mirror write consistency of the corresponding logical volume to yes using smitty. IDS1016E Unable to find the journaled file system log.
Explanation: DP for ESS requires that the quorum property of a mirrored volume group be set to off. User Response: Set the quorum to off.
Explanation: DP for ESS requires that one copy of the journaled file system log of each volume group reside on the specified ESS.
878
IBM Tivoli Storage Manager: Messages
IDS1016E IDS1032W
User Response: Ensure that each volume group has a copy of the journaled file system log on the specified ESS. IDS1016E The mount point <mount point> already exists IDS1026I Start of idscntl on the production system ...
Explanation: DP for ESS has issued a call to the production system and is waiting for the end of the execution. User Response: None. IDS1027I idscntl ended on the production system successfully.
Explanation: Prior to enabling the new resources on the backup system, DP for ESS checks if the file system has an entry in /etc/filesystems. If so, the program terminates immediately. User Response: Run DP for ESS (tpdessdb2) with the option -f withdraw to disable all the resources for the last run. IDS1016E The same hdisk <disk name> cannot be associated with two different vpaths (serial numbers <ser_no_1> and <ser_no_2>).
Explanation: DP for ESS has ended the call to the production system successfully. User Response: None. IDS1028E idscntl ended with errors on the production system.
Explanation: This is an incorrect SDD configuration. User Response: The IBM publication Subsystem Device Driver Users Guide explains how to configure SDD. IDS1020I The FlashBack Restore ended successfully.
Explanation: The remote exec call to the production system has ended with errors. User Response: Check the specific error message. IDS1030I Flashcopy started ...
Explanation: The high-performance restore issued with the FlashCopy from the target volumes to the source volumes was completed successfully. User Response: None. IDS1023I Exiting with return code <rc>.
Explanation: The command with the flashcopy function has been issued on the production system, and the program idscntl waits until this action has finished. User Response: None. IDS1031I Flashcopy successful.
Explanation: The idscntl program issues this message on terminating. The program returns the value 0, or nonzero if the execution of the called function failed. User Response: If the called function has failed, check for previous error messages. IDS1024I Exiting with return code <rc>.
Explanation: The command for the FlashCopy of the volume pairs has terminated successfully on the production system. User Response: None. IDS1032W Information from DP for mySAP.com has not been found.
Explanation: The idscntl program issues this message on terminating. The program returns the value 0, or nonzero if the execution of the called function failed. User Response: If the called function has failed, check for previous error messages. IDS1025I Time stamp: <current_time>
Explanation: The exchange data between DP for ESS and DP for mySAP.com was not found. As of DP for mySAP.com version 3.3.10, the information is exchanged through the call of the DP for ESSs 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.com you have installed does not support DP for ESS, or DP for mySAP.com has failed after a successful FlashCopy and mount. User Response: Check the run logs of tdpessdb2. This error could have various reasons and should be resolved depending on the specific situation: Case 1: tdpessdb2 has finished successfully. Result: The backup on disk (FlashCopy target volumes) as well as the one done to the TSM server are valid.
Explanation: DP for ESS 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. User Response: None.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
879
IDS1033I IDS1042W
However, DP for ESS cannot show the backup ID in its report when using the function inquire. Reason for warning: It is very likely that DP for mySAP.com (AIX version) does not have DP for ESS support (prior to version 3.1.0.3). Action: Install the appropriate DP for mySAP.com version. Case 2: tdpessdb2 has terminated abnormally. Result: Check carefully the run log of tdpessdb2 for any BKI, ANS or ANR error messages. Most likely, the backup on disk (FlashCopy target volumes) is valid (check with idscntl -f inquire whether PSI is PSI_MOUNT_DONE or PSI_UNMOUNT_DONE), but the backup to the TSM server is invalid. Cause: Any problems with the network or on the TSM server caused DP for mySAP.com running a backup to fail. Action: Depending on the error message, eliminate the reason for not getting a successful backup to the TSM server. IDS1033I Information from DP for mySAP.com has been found with BACKUPID <backupid>. IDS1038I The IDS control file <ids_control_file> does not exist. It will be created.
Explanation: DP for ESS will write the first record to the IDS control file specified in the entry IDS_CONTROL_FILE of the profile. User Response: None. IDS1039E The IDS control file has no entry.
Explanation: DP for ESS 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: After you run at least one tdpessdb2 with a successful FlashCopy, the problem will be resolved. IDS1040E The IDS control file must be read or inserted before update.
Explanation: DP for ESS has detected a logical error when processing the IDS control file. User Response: Contact Data Protection for mySAP.com support. IDS1041W The value of the field field_name in the file file_name is empty.
Explanation: The exchange data between DP for mySAP.com and DP for ESS has been found during the execution of the function unmount. The backup 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>. User Response: None. IDS1034E Entry <field_name> in the current backup cycle of the IDS control file is missing.
Explanation: The program tdpessdb2 updates the IDS repository after the Tivoli Storage Manager backup but also in case of 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 other errors prior to this one. IDS1035I The IDS control file exists and a new backup cycle entry has been created.
>>> input_file <file list> <<< input_file If one of the fields of the topic backint_data is empty, this message is displayed. If the backup ID is empty, the process terminates with error IDS1036E. User Response: None. IDS1042W Info data from DP for mySAP.com /tmp/bki<SID>.ids cannot be read.
Explanation: At the start of the function -f getresources, DP for ESS 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). User Response: None.
Explanation: Before the unmount process, DP for ESS will read /tmp/bki<SID>.ids, which contains information about the backup that was done by DP for
880
IBM Tivoli Storage Manager: Messages
IDS1043I IDS1053I
mySAP.com. 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 This message will be issued if DP for mySAP.com terminated unsuccessfully for some reason. User Response: Ensure that DP for mySAP.com runs successfully. IDS1043I The maximum number of backup cycles in the IDS control file has been reached. IDS1048I The unmount process will be skipped because the progress status indicator (PSI) has a value of psi. IDS1047I End of listing.
Explanation: Corresponds to start message IDS1046I. User Response: None.
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: Table 5 in Data Protection for IBM ESS for mySAP.com Technology Installation and Users Guide for DB2 UDBshows the permissible functions depending on the backup progress status indicator. IDS1050E The version of the idscntl program must be the same on the backup and production systems.
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. User Response: None. 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. User Response: None.
Explanation: The version of DP for ESS on the production system is different from the version on the backup system. User Response: Ensure that you install the same version of DP for ESS on the production and backup systems. You get the version number when you start idscntl without parameters. IDS1051I Enter the password for the user <user ID>
IDS1045W
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 Start of listing of importing volume groups/mounting file systems ...
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 ESS program idscntl uses the user ID to execute a remote shell on the production system. User Response: Enter the password for the corresponding user ID. IDS1052I Enter the password for the user <user ID> again
Explanation: After initiating the FlashCopy source/target volumes on the production system, DP for ESS will make the corresponding target volumes available to the backup host. A list of mount points or volume groups will be shown. User Response: None.
Explanation: In order to avoid typing errors, you have to enter the password twice. User Response: Enter the password 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. User Response: Enter the password again. You are
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
881
IDS1054E IDS1064E
permitted three attempts before the program terminates. IDS1054E No password stored. IDS1060I Start of listing of exported volume groups/unmounting file systems ...
Explanation: The two entered passwords are not identical. You have tried three times, and the passwords were different in each case. User Response: You must start the idscntl program with the function -f password again. If no password is stored, or it is invalid, idscntl fails when the flashcopy function is used. IDS1055E The config file named <config_file> could not be opened. Please call idscntl with the password function to create that file.
Explanation: A list of unmount points or exported disk groups will be shown. Due to the usage of the unmount function on the backup host, DP for ESS will unmount the file systems and export volume groups on the backup host that had been imported or mounted when the DP for ESS flashcopy function was executed. User Response: None. 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 on the ESS. User Response: None. IDS1062I The progress status indicator (PSI) is already PSI_UNMOUNT_DONE.
Explanation: DP for ESS is unable to read the configuration file <config_file>. User Response: This error could have various reasons. Try the following: 1. Call idscntl with the password function to create the file. 2. Check the path of the configuration file. The path must be specified in the profile (parameter CONFIG_FILE). 3. Make sure that the file access permissions are set correctly. IDS1056E The information of DP for mySAP.com could not be set in the IDS repository.
Explanation: DP for ESS 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 idscntl call. User Response: None. IDS1063E Parameters LOGON_HOST_PROD/ LOGON_HOST_BACK in profile wrong or missing.
Explanation: After the mount of the file systems on the backup system was finished, the call of DP for mySAP.com (backint) takes place. Backint calls then DP for ESS 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: Either DP for ESS 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 hostnames must match the respective hostnames of the production and backup 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: 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 SHARK_VOLUMES_FILE (.fct file).
Explanation: An unknown parameter <keyword> has been found in the profile. User Response: Check the specified parameter in the profile and try again.
882
IBM Tivoli Storage Manager: Messages
IDS1065E IDS1074E
IDS1065E You cannot run the function function if the progress status indicator (PSI) has a value of psi. IDS1070E The option -f flashback can only be used on the production system.
Explanation: The backup cycle was left in a state that does not allow DP for ESS to start the specified function. User Response: Table 5 in Data Protection for IBM ESS for mySAP.com Technology Installation and Users Guide for DB2 UDB shows the permissible functions depending on the backup progress status indicator. IDS1066E The option -f flashcopy can only be used on the backup system.
Explanation: The FlashBack Restore (option -f flashback) can only be started from the production machine. User Response: To start the FlashBack Restore, log on into the production machine. IDS1071E Topic named <topicname> could not be found in the file <filename>.
Explanation: DP for ESS could 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 SHARK_VOLUMES_FILE, you need to check whether the topic name has the format: >>> shark_volumes_set_# where # is a placeholder for the volume set number (1, 2, ..) When the affected file is another file, you likely have another error prior to this one. Otherwise, contact Data Protection for mySAP.com support. IDS1072E The source volume <serial number> cannot be specified as a target volume in the .fct file.
Explanation: You cannot start the flashcopy function on the production system. User Response: Make sure you start idscntl 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 idscntl use only and should not be used externally. User Response: Make sure you issue idscntl -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 idscntl call. IDS1068E The option -f withdraw can only be used on the backup system.
Explanation: DP for ESS 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 <shark_volumes_set_#> in file <filename>.
Explanation: You cannot start the function withdraw on the production system. User Response: Make sure you start idscntl with the function -f withdraw on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK. IDS1069E The option -f unmount can only be used on the backup system.
Explanation: DP for ESS has read file <filename> contained in the parameter SHARK_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 Structure of the DP for ESS Target Volumes File Data Protection for IBM ESS for mySAP.com Technology Installation and Users Guide for DB2 UDB. IDS1074E The backup ID (timestamp) is empty. This FlashCopy backup cannot be used for FlashBack Restore.
Explanation: You cannot start the function unmount on the production system. User Response: Make sure you start idscntl with the function -f unmount on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK.
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 tdpessdb2 was not able to generate a timestamp.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
883
IDS1075I IDS1085E
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 ... production systems with a single backup system will not work properly. User Response: Check the system error number and message with your system administrator. IDS1080W The semaphore could not be allocated. System error <sys_errno>: <sys_message>.
Explanation: When multiple production systems run a backup via a single backup system at the same time, DP for ESS 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 DP for ESS could not allocate 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. IDS1081W The semaphore could not be released. System error <sys_error>: <sys_message>.
Explanation: If the DP for ESS 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 IDS1077I Semaphore released.
Explanation: If DP for ESS could not allocate 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. IDS1082E Duplicate target volume serial number was found in the target list.
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: DP for ESS found a duplicate serial number for an ESS target volume in the file specified in the SHARK_VOLUMES_FILE parameter. User Response: Ensure that the serial numbers of the target volumes in the file SHARK_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: If DP for ESS 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. System error <sys_errno>: <sys_message>.
Explanation: DP for ESS 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 make a restore from a flashcopy backup of the type NOCOPY.
Explanation: If DP for ESS could not initialize the semaphore, the system error number and message will be issued as a warning. The concurrent run of multiple
Explanation: The ESS allows the FlashCopy types COPY, INCR and NOCOPY. Only the FlashCopy backups made with the parameter FLASHCOPY_TYPE set to the value COPY or INCR can be used for the FlashBack Restore.
884
IBM Tivoli Storage Manager: Messages
IDS1086E IDS1102E
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. mirroring: RSI_DISKANDLVM. User Response: Wait until the FlashCopy background process is finished. IDS1093E The target set id was not found.
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 the other value like BSI_START, BSI_TAPEONLY or BSI_INVALID are not allowed. User Response: Normally the calling program must 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 One or more errors were found disabling the production system resources.
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 SHARK_ID_LVM_MIRROR, which determines which ESS should be taken as the source, will be specified here inside the corresponding target set as well. Internally DP for ESS keeps the status of each target set (progress status, backup status, restore status, backup sequence number, etc) in the house keeping directory. After the FlashCopy, DP for ESS will reread the target set information again. This message will only be displayed if this information was destroyed, is corrupt or something unexpected occurs. User Response: Check for preceding errors. IDS1097E The option -f set_bki_info can only be used on the backup system.
Explanation: Before the actual FlashBack Restore to the database volume occurs, DP for ESS 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 ESS will issue a warning but the FlashBack Restore will continue. User Response: None IDS1089I The FlashBack Restore was previously started. Please enter c[ont] to restart again or s[top] to cancel.
Explanation: DP for mySAP.com (backint) calls DP for ESS 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 SHARK_ID_LVM_MIRROR has to be moved from the profile filename.fcs to the corresponding target set in filename.fct
Explanation: DP for ESS found that the user started a FlashBack Restore earlier and that the FlashCopy background process is still running. User Response: If you enter continue then the FlashCopy relationships between the volumes will be cut and the FlashBack will be initialized again. IDS1091E You cannot run the function if the restore status indicator (RSI) has a value of RSI_START.
Explanation: In case of AIX LVM mirroring the parameter SHARK_ID_LVM_MIRROR indicates the identifier of the ESS to be selected for the mirror copy that should be used for the FlashCopy. This parameter is now contained in the target set 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.
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 has either the value: RSI_DISKONLY or in case of LVM
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 SHARK_ID_LVM_MIRROR, which determines which ESS should be selected for the FlashCopy, will be specified inside of the corresponding target set as well. Internally DP for ESS keeps the status of each target set (progress status, backup status, restore status, backup sequence number, etc) in the housekeeping directory.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
885
IDS1103W IDS1131E
The file containing the information of the target set could not be read or written. User Response: Check for preceding errors. IDS1103W The restore status indicator (RSI) has a value of RSI_INVALID 5. All the partitions of each logical volume copy must reside on the physical volumes of the same ESS (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 The parameter CLEAR_TARGET_PVID in the profile filename.fcs is obsolete and will be ignored.
Explanation: If the restore status RSI of the target set has a value of RSI_INVALID, this means that a FlashBack Restore was initiated but not ended. Though, DP for ESS will issue this warning and continue with the FlashCopy backup. User Response: Check if the FlashCopy backup ended successfully. IDS1121I Getting the source volumes ...
Explanation: The first step of DP for ESS in a FlashCopy backup is to determine the source volumes from the list of files passed by the corresponding calling UI backup tool. User Response: None. IDS1122I FlashCopying the sources to the target volumes ...
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: After having found the pairs of volumes to be copied, DP for ESS 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 ESS copy services server. User Response: None IDS1123I Enabling the volumes and filesystems ...
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 or 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.com in the file temp_file is empty.
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 IDS1125I Checking AIX LVM mirroring ...
Explanation: In a high-availability LVM mirror environment, DP for ESS 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 ESS that was chosen for the FlashCopy must be free of stale partitions (see EEP0176E).
Explanation: DP for mySAP.com calls DP for ESS 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 ESS 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 ESS moves the complete data on a physical volume instead of individual files. Two requirements are necessary to build a backup of a database:
886
IBM Tivoli Storage Manager: Messages
IDS1133E IDS1179E
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 ESS ID in the parameter SHARK_ID_LVM_MIRROR for the corresponding target set in the .fct file <filename>. 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.com calls DP for ESS to inquire for disk backups on the target sets. The target sets are enumerated starting with 1. User Response: None. IDS1177E The FlashCopy run backup sequence number was not a valid disk backup.
Explanation: To do a FlashBack Restore of a valid disk backup must exist on one of the target sets. The backup status indicator (BSI) must have one of the value BSI_DISKONLY or BSI_DISKANDTAPE. User Response: Check the backup status indicator (BSI) of your target volumes calling the tdpessdb2 executable: tdpessdb2 -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: DP for ESS found that some of the logical volumes on which the production database is residing are mirrored using the mirror capability of the Logical Volume Manager. However, the parameter SHARK_ID_LVM_MIRROR was not specified in the .fct file. This parameter causes DP for ESS to make all the necessary checks to get a consistent copy through the FlashCopy on the target volumes in an LVM mirror environment. User Response: Set the parameter SHARK_ID_LVM_MIRROR with the ESS ID that is used for the FlashCopy. IDS1174E The option -b backup ID or -b backup sequence number must be specified.
Explanation: The backup status indicator can accept one of the following values in the IDSSAVE: BSI_START a disk backup as background copy was started and is still running, BSI_TAPEONLY only a backup on TSM is available, BSI_DISKONLY only a backup on disk is available, BSI_DISKANDTAPE both backup on disk and TSM are available, BSI_INVALID invalid entry for disk backup and - initial value Other value is not allowed and makes the backup cycle unusable. User Response: Check the backup status indicator (BSI) of your IDSSAVE calling the tdpessdb2 executable with the option -f inquire : tdpessdb2 -p initSID.fcs -f inquire -b backup sequence number Check for preceding errors. IDS1179E The backup status indicator (BSI) for target set number is not valid.
Explanation: The call of idscntl with the function -f flashback requires a backup sequence number (also called backup cycle number) or timestamp that is an unique identifier for the backup to be restored. With this identifier DP for ESS will find the volumes target set containing the disk backup to be restored. User Response: Normally the calling program must determine one valid backup ID or backup sequence number to be passed. Check for preceding errors. IDS1175E The backup ID or the backup sequence number identifier was not found.
Explanation: DP for ESS did not find any entry in the IDSSAVE for the specified backup ID or backup sequence number. User Response: Normally the calling program must determine one valid backup ID or backup sequence number to be passed. Check for preceding errors..
Explanation: The backup status indicator can accept one of the following values for one specific target set: BSI_START a disk backup as background copy was started and is still running, BSI_TAPEONLY only a backup on TSM is available BSI_DISKONLY only a backup on disk is available BSI_DISKANDTAPE both backup on disk and TSM are available BSI_INVALID invalid entry for disk backup - initial value Other value is not allowed and makes this backup cycle unusable. User Response: Check the backup status indicator (BSI) of your target volumes calling the tdpessdb2 executable with the option -f ts_inquire (target set inquire): tdpessdb2 -p initSID.fcs -f ts_inquire -n target set number Check for preceding errors.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
887
IDS1180E IDS1193I
IDS1180E The FlashCopy run backup sequence number is a valid disk backup. IDS1190E The information of the source / target volumes could not be found.
Explanation: DP for ESS has found that the selected backup to be restored has a valid disk backup with an entry in the IDSSAVE. User Response: None IDS1181E The FlashCopy run backup sequence number is not the last backup of target set number.
Explanation: The executable IDSCNTL will be started automatically as a daemon (sometimes referred as fcagent) to monitor the background copy. The ESS Copy Services CLI will be used to get the states of the copy process. This action has failed. User Response: Check the error log file idscntl_[p|b]_runagent_jjjjmmddHHMMSS.log in the directory specified in the parameter LOG_TRACE_DIR of the .fcs file. Check the connection from the host to the ESS with the command: SHARK_COPY_SERVICE_CODE/rsTestConnection.sh -v -s SHARK_SERVERNAME_PRIMARY or SHARK_COPY_SERVICE_CODE/rsTestConnection.sh -v -s SHARK_SERVERNAME_BACKUP Where SHARK_COPY_SERVICE_CODE, SHARK_SERVERNAME_BACKUP and SHARK_SERVERNAME_PRIMARY are values of parameters specified in the .fcs file. DP for ESS will restart the fcagent automatically. IDS1191I The target volumes set number does not contain a valid disk backup.
Explanation: The specified backup sequence number cannot be used for FlashBack because on the target volumes a newer FlashCopy run was already entered. User Response: Check the backup status indicator (BSI) of your target volumes calling the tdpessdb2 executable with the option -f ts_inquire (target set inquire): tdpessdb2 -p initSID.fcs -f ts_inquire -n target set number Select another backup Id for FlashBack. IDS1183I 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 ESS sets the value to COPY. User Response: None. IDS1184I Checking the backup status on Tivoli Storage Manager and on ESS disks ...
Explanation: This informational message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or DP for ESS) if one of the target sets contains an invalid disk backup. User Response: None. IDS1192I No disk backups were found on the target volumes.
Explanation: This message is displayed by DP for ESS during the inquire of the backups on Tivoli Storage Manager and on disk. User Response: None. IDS1185I Reading the SAP backup log <PATH>/back<SID>.log ...
Explanation: This informational message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or DP for ESS) 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.
Explanation: This message is displayed by DP for ESS while reading the backup of the SAP system ID <SID>. User Response: None. IDS1186E The parameter param in the profile <.sap file name> or the environment variable env_var is required.
Explanation: This info message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or DP for ESS) if one of the target sets contains a FlashCopy backup of type NOCOPY. User Response: None.
Explanation: This error is issued by DP for ESS 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.
888
IBM Tivoli Storage Manager: Messages
IDS1194I IDS1302E
IDS1194I The FlashCopy run backup_sequence_number has a backup status indicator (BSI) of status and is therefore not valid for FlashBack. 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. 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. IDS1300E Cannot read file: <filename>.
Explanation: This info message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or DP for ESs). 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. User Response: None. 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.com. At restore time, DP for ESS 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.com supporting FlashBack Restore. Otherwise, you will have to restore from Tivoli Storage Manager. IDS1197I The list of files to be restored does not exist for the FlashCopy run backup_cycle_number.
Explanation: DP for ESS is unable to 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 <ids_control_file> v the field value of EXCHANGE_FILE in a backup cycle record. User Response: Check the access permissions of the affected file and try again. IDS1301E Cannot write file: <filename>.
Explanation: This informational message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or DP for ESs) if the list of files was not found for one of the target sets. User Response: None. 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 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>:
Explanation: DP for ESS is unable to write to the data file filename. The affected files could be, e.g.: v <LOG_TRACE_DIR>/idscntl_b_<date time stamp>.log v <LOG_TRACE_DIR>/idscntl_p_<date time stamp>.log v <LOG_TRACE_DIR>/idscntl_b_<date time stamp>.trace v <LOG_TRACE_DIR>/idscntl_p_<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 ESS: v INSTHOME: to the home directory of the DB2 user v DB2INSTANCE: to the DB2 instance v DB2DBDFT: to the DB2 default database User Response: Set the missing environment variable and try again.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
889
IDS1303E IDS1318E
IDS1303E The environment variable <env_var> is not correct. prior to starting the FlashCopy again. IDS1310W The free space in the file system containing the directory path is only amount MB.
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 existing free space of the file systems containing the following directories will be checked: v the database home directory and v the directory specified by the parameter LOG_TRACE_DIR in the .fcs file and 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 ESS 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. IDS1311W Idscntl requires a free space of at least 5 MB in the file system containing the directory path.
Explanation: The file <filename> was not found or is not accessible to DP for ESS. 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 idscntl are not set to 4750. Since the s-bit is not set, DP for ESS cannot switch between the users db2<sid> and root during the execution of the program. v the file system in which idscntl is installed was mounted with the NOSUID option. User Response: v Check the idscntl file in the directory /usr/tivoli/tsm/tdpessr3/db2/x.y.z, and set the access rights for idscntl with chmod 4750 idscntl. After the installation, the command ls -l idscntl.... outputs a line such as:
-rwsr-x--- 1 root dba 1918611 Apr 11 17:09 idscntl
Explanation: If the free space of the checked file systems (see Explanation of 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>.
(This is what setup.sh would do if the user had used it.) v If the file system in which idscntl is installed was mounted with the NOSUID option, mount the file system with SUID allowed. IDS1308W Warning: File <file name> still exists on the backup system.
Explanation: DP for ESS encountered an unexpected message error during the execution of a system function. The respective operating system error and message text will be displayed. The message will appear, for example, as a result of v a wrong user ID on the parameter LOGON_HOST_PROD in the fcs file v a wrong password given for the user ID on the parameter LOGON_HOST_PROD in the fcs file v a wrong TCP/IP name on the parameter LOGON_HOST_PROD in the fcs file (for example: connection timeout) v a failure allocating memory through the function malloc, and the operating system cannot satisfy the request User Response: Check the specific error message.
Explanation: DP for ESS 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
890
IBM Tivoli Storage Manager: Messages
IDS1322I IDS1541I
IDS1322I The file filename is locked, waiting one second and retry! IDS1520E The FlashCopy agent can only be started if the last FlashCopy run was of type COPY or INCR.
Explanation: DP for ESS 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 ESS uses a lock mechanism. User Response: None. IDS1452E This version of Data Protection for IBM ESS for mySAP.com Technology has expired.
Explanation: DP for ESS 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 the value of COPY or INCR. User Response: Normally, the calling program will control this process. Check for preceding errors. IDS1531E Timestamp string cannot be converted.
Explanation: This is a test version that has expired. User Response: Order a release version of Data Protection for IBM ESS for mySAP.com Technology or contact your IBM/Tivoli sales representative. IDS1453W This version of Data Protection for IBM ESS for mySAP.com Technology 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 Data Protection for IBM ESS for mySAP.com Technology or contact your IBM/Tivoli sales representative before the version expires. IDS1454I *** This copy is NOT FOR RESALE. ***
Explanation: This version is not for resale. User Response: None. IDS1455E License file filename does not exist.
Explanation: The status of the background copy will be written by the DP for ESS 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 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 ESS. To calculate the transfer rate some conversion is needed. When doing this conversion, an error occurred. The rate value will be invalid. User Response: Check the date and time setting of the machine. IDS1540I Start of the FlashCopy agent on the backup system
Explanation: The license file agentess.lic was not found where expected. User Response: Make sure that the agentess.lic file resides in the same directory as the init<SID>.fcs profile. IDS1456E Unable to access license file file name.
Explanation: DP for ESS will 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: None IDS1541I Removing the FlashCopy agent on the backup system
Explanation: Unable to access license file. User Response: Make sure the access permissions allow read/write access. IDS1457E License file file name contains invalid data/checksum.
Explanation: DP for ESS will automatically stop the FlashCopy agent daemon after the background copy has finished on the backup system. User Response: None
Explanation: The license file is invalid. User Response: Make sure you have the right agentess.lic file installed.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
891
IDS1545I IDS1606E
IDS1545I Start of the FlashCopy agent on the production system IDS1553W The FlashCopy agent has already been removed from /etc/inittab.
Explanation: DP for ESS will automatically start a daemon (called the FlashCopy agent) to monitor the background copy after the start of a FlashBack Restore on the production system. User Response: None IDS1546I Removing the FlashCopy agent on the production system
Explanation: DP for ESS will automatically stop the FlashCopy agent daemon after the background copy has finished on the backup system or, in the case of FlashBack Restore, on the production system. The entry in /etc/inittab will be removed. However, DP for ESS detected that the entry no longer exists in the table. User Response: None. IDS1602I Waiting for SyncPoint number on all EEE nodes...
Explanation: DP for ESS will automatically stop the FlashCopy agent daemon after the background copy has finished the restore on the production system. User Response: None IDS1550E The FlashCopy agent could not be added to /etc/inittab.
Explanation: DP for ESS is waiting for all running tdpessdb2 processes to reach the specified SyncPoint. User Response: None. IDS1603E Timeout of number seconds on waiting for SyncPoint number on all EEE nodes reached.
Explanation: DP for ESS 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. However, DP for ESS was unable to add an entry to /etc/inittab. User Response: Check the rights of the DP for ESS executable (idscntl or splitint). IDS1551W The FlashCopy agent already exists in /etc/inittab.
Explanation: While DP for ESS is waiting for all running tdpessdb2 processes to reach the specified SyncPoint, a time out condition occurs. This error can have the following reasons: 1. The DP for ESS parameter DB2_EEE_SYNCTIMEOUT is set too low. Check the DP for ESS parameter DB2_EEE_SYNCTIMEOUT in the DP for ESS configuration file. 2. DP for ESS is not started for each production server. 3. One or more DP for ESS processes running for the production servers were terminated. User Response: 1. Check the DP for ESS parameter DB2_EEE_SYNCTIMEOUT in the DP for ESS configuration file. 2. Check that DP for ESS is running on the backup system for all production servers. 3. Check for error messages in the DP for ESS log files for each process. IDS1605I The last socket synchronization is still active.
Explanation: DP for ESS 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 ESS detected that an entry already existed. User Response: None IDS1552E The FlashCopy agent could not be removed from /etc/inittab.
Explanation: The last DP for ESS socket synchronization was not stopped. User Response: None. IDS1606E Socket synchronization could not be started.
Explanation: DP for ESS will automatically stop the FlashCopy agent daemon after the background copy has finished on the backup system or, in the case of FlashBack Restore, on the production system. The entry in /etc/inittab is removed. However, DP for ESS was unable to remove the entry. User Response: Check the rights of the DP for ESS executable (idscntl or splitint).
Explanation: The last DP for ESS socket synchronization was not stopped. DP for ESS 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.
892
IBM Tivoli Storage Manager: Messages
IDS1607I IDS2012E
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. IDS2007I End of tdpessdb2 program at: <time> . IDS2005I Start of tdpessdb2 program at: <time> .
Explanation: DP for ESS started at time. User Response: None.
Explanation: tdpessdb2 was called with function stopsocket to stop the socket server, but the socket server was not running. User Response: None. IDS1610E Invalid user name or password.
Explanation: DP for ESS ended at time. Control will be returned to either the shell or to a script when tdpessdb2 was called by a script. User Response: None.
Explanation: While tdpessdb2 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 ESS copy service server user is changed, the socket server has to be restarted. The password for the users has to be changed by calling the tdpessdb2 function configure. IDS1620E The TCPIP service port number could not be found in /etc/services.
IDS2008E
Parameter <keyword> in the profile file required.
Explanation: The parameter <keyword> in the profile for DP for ESS could not be found. It must be defined. User Response: Set the parameter <keyword> and its value in the profile for DP for ESS. IDS2009E Directory path <path> for the IDS control file does not exist!
Explanation: Either the entry for the parameter CONTROL_FILE is incorrect or the path does not exist. User Response: Ensure that the parameter CONTROL_FILE in the profile has a valid path. If the path does not exist, you must create it. IDS2010E Another instance of tdpessdb2 is running.
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 tdpessdb2 with function configure on the production system and that the backup system is configured with the script setupDB2BS or setupDB2EEEBS. 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 DB2 UDB EEE Considerations in Data Protection for IBM ESS for mySAP.com Technology Installation and Users Guide for DB2 UDB. IDS2000E Profile not specified.
Explanation: DP for ESS is already running or the last run was abnormally terminated. User Response: If another DP for ESS is running, you must wait for the end of this run before you can restart DP for ESS. If no other DP for ESS is running, you must remove the lock-file /db2/<SID>/dbs/work/.tdpessdb2_lock manually. IDS2011E Option -f <function> not specified.
Explanation: DP for ESS cannot locate the profile. User Response: Ensure that a profile is available. Note that the tdpessdb2 call must have the following form: <path>/tdpessdb2 -p <path>/init<SID>.fcs -f <function>.... IDS2001E Function not defined.
Explanation: tdpessdb2 always requires the option -f <function> with a valid function. User Response: Ensure that the tdpessdb2 call has the following form: <path>/tdpessdb2 -p <path>/init<SID>.fcs -f <function>.... IDS2012E The backup type <-t flashcopy> can only be used on the backup system.
Explanation: An invalid argument has been specified for the -f option of DP for ESS. User Response: Ensure that you pass a valid function name with the option -f. Valid functions are: backup, restore, query, flashcopy, withdraw, inquire, password.
Explanation: tdpessdb2 was called with function backup and backup type flashcopy. This combination of parameters is only valid on the backup system. User Response: Ensure that tdpessdb2 with function backup and backup type flashcopy is called on the backup system.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
893
IDS2013E IDS2028E
IDS2013E The arguments specified for the backup type <-t flashcopy> are not valid. User Response: Ensure that the tdpessdb2 with function flashcopy is called on the backup system. IDS2019E The option -f unmount can only be used on the backup system.
Explanation: tdpessdb2 was called with function 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.
Explanation: tdpessdb2 was called with function unmount. This parameter is only valid on the backup system. User Response: Ensure that the tdpessdb2 with function unmount is called on the backup system. IDS2020E The option -f withdraw can only be used on the backup system.
Explanation: tdpessdb2 was called with function 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. User Response: Ensure that you pass valid arguments 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.
Explanation: tdpessdb2 was called with function withdraw. This parameter is only valid on the backup system. User Response: Ensure that the tdpessdb2 with function withdraw is called on the backup system. IDS2022E 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] IDS2023E The socket options <-f initsocket> and <-f stopsocket> can only be used on the production system.
Explanation: tdpessdb2 was called with function backup and backup type online/offline. This combination of parameters is only valid on the production system. User Response: Ensure that the tdpessdb2 with function backup and backup type online/offline is called on the production system. IDS2016E The option -f restore 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 only be used on the production system. User Response: None IDS2024E The option -f dbresume can only be used on the production system.
Explanation: tdpessdb2 was called with function restore. This parameter is only valid on the production system. User Response: Ensure that the tdpessdb2 with function restore is called on the production system. IDS2017E The option -f query can only be used on the backup system.
Explanation: You tried to resume the DB2 database on the backup system but this function can only be used on the production system. User Response: None IDS2028E The arguments specified for the option -f restore are not valid.
Explanation: tdpessdb2 was called with function query. This parameter is only valid on the backup system. User Response: Ensure that the tdpessdb2 with function query is called on the backup system. IDS2018E The option -f flashcopy can only be used on the backup system.
Explanation: tdpessdb2 was called with function restore. You specified an invalid argument for the function restore. User Response: Ensure that you pass valid arguments with function restore. Valid arguments are: database, no/rollforward.
Explanation: tdpessdb2 was called with function flashcopy. This parameter is only valid on the backup system.
894
IBM Tivoli Storage Manager: Messages
IDS2029E IDS2038E
IDS2029E Error while checking filesystem size for DB2 Logdir <logdir>. PSI_MOUNT_DONE or PSI_UNMOUNT_DONE), but the backup to the TSM server is invalid. Cause: Any problems with the network or on the TSM server caused DP for mySAP.com running a backup to fail. Action: Depending on the error message, eliminate the reason for not getting a successful backup to the TSM server. IDS2033I Information from DP for mySAP.com has been found with BACKUPID <backupid>.
Explanation: tdpessdb2 checks the size of the DB2 Logdir filesystem. This check fails. User Response: Ensure that the DB2 Logdir filesystem exists and is mounted. IDS2030E Not enough freespace in DB2 logpath (<logdir>). Need at least 55% freespace.
Explanation: tdpessdb2 checks the freespace of the DB2 Logdir filesystem. tdpessdb2 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. IDS2031E Backup Timestamp <time> cannot be converted.
Explanation: The exchange data between DP for mySAP.com and DP for ESS has been found during the execution of the function unmount. The 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 on the production system.
Explanation: tdpessdb2 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 tdpessdb2 and is not corrupted. IDS2032W Information from DP for mySAP.com has not been found.
Explanation: You tried to start a restore on the backup system but the function restore can only be used on the production system. User Response: None IDS2036E The options -b <backup sequence number> or -b <backupID> must be specified.
Explanation: The exchange data between DP for ESS and DP for mySAP.com was not found during the execution of the unmount function. Either the DP for mySAP.com you have installed does not support DP for ESS, or DP for mySAP.com has failed after a successful FlashCopy and mount. User Response: Check the run logs of tdpessdb2. This error could have various reasons and should be resolved depending on the specific situation: Case 1: tdpessdb2 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 ESS cannot show the backup ID in its report when using the function inquire. Reason for warning: It is very likely that DP for mySAP.com (AIX version) does not have DP for ESS support (prior to version 3.1.0.3). Action: Install the appropriate DP for mySAP.com version. Case 2: tdpessdb2 has terminated abnormally. Result: Check carefully the run log of tdpessdb2 for any BKI, ANS or ANR error messages. Most likely, the backup on disk (FlashCopy target volumes) is valid (check with idscntl -f inquire whether PSI is
Explanation: The function you called needs the additional parameter b <backup sequence number> or -b <backupID>. User Response: Restart the function you called with the b option. IDS2037E The option -f configure can only be used on the production system.
Explanation: You tried to start the function configure on the backup system but this function can only be used on the production system. User Response: None IDS2038E 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.
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
895
IDS2039E IDS2064E
User Response: None IDS2039E The option -s <socket_port> can only be used in EEE environments. IDS2055E The config file named <config_file> could not be opened. Please call tdpessdb2 with the function configure to create this file.
Explanation: Explanation: You called tdpessdb2 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: DP for ESS is unable to read the configuration file <config_file>. User Response: This error could have various reasons. Try the following: 1. Call tdpessdb2 with the configure function to create the file 2. Check the path of the configuration file. The path must be specified in the profile (parameter CONFIG_FILE) 3. Make sure that the file access permissions are set correctly. IDS2062E Invalid value <value> specified for parameter <parameter> in the profile.
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 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 ESS program idscntl uses the user ID to execute an rexec on the production system. User Response: Enter the password for the corresponding user ID. IDS2052I Enter the password for the user <user ID> again
Explanation: The value specified for the parameter in the profile is not valid. User Response: Check the specified value in the profile and try again. IDS2063E Parameters LOGON_HOST_PROD/ LOGON_HOST_BACK in Profile wrong or missing.
Explanation: Either DP for ESS 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 <tcp_name> <user ID> LOGON_HOST_BACK <hostname> The tcp_name must match the TCP/IP name via which the production system can be reached from the backup system. The hostname must match the respective hostname of the backup system. 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. IDS2064E The parameter <keyword> in the profile is not known.
Explanation: In order to avoid typing errors, you have to enter the password twice. User Response: Enter the password again. IDS2053I The password entry does not match, please try again.
Explanation: The two entered passwords are not identical. You must enter the password again. User Response: Enter the password again. You are permitted three attempts before the program terminates. IDS2054E No password stored.
Explanation: The two entered passwords are not identical. You have tried three times, and the passwords were different in each case. User Response: You must start the tdpessdb2 program with the function -f password again. If no password is stored, or it is invalid, tdpessdb2 fails when the flashcopy function is used.
Explanation: An unknown parameter <keyword> has been found in the profile. User Response: Check the specified parameter in the profile and try again.
896
IBM Tivoli Storage Manager: Messages
IDS2065E IDS2200E
IDS2065E You cannot run the function <function> if the progress status indicator (PSI) has a value of <psi>. IDS2124I Exiting with return code <rc>.
Explanation: The backup cycle was left in a state that does not allow DP for ESS to start the specified function. User Response: Refer to the permissible functions depending on the backup progress status indicator. IDS2071E Topic named <topicname> could not be found in the file <filename>.
Explanation: The tdpessdb2 program issues this message on terminating. The program returns the value 0, or nonzero if the execution of the called function failed. User Response: If the called function has failed, check for previous error messages. IDS2175E The backup ID or backup sequence number number was not found.
Explanation: DP for ESS could 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 SHARK_VOLUMES_FILE, you need to check whether the topic name has the format: >>> shark_volumes_set_#, where # is a placeholder for the volume set number (1, 2, ..) When the affected file is another file, you likely have another error prior to this one. Otherwise, contact DP for mySAP.com support. IDS2090E The NLS catalog could not be loaded. Make sure that the catalog <%s/%s> exists.
Explanation: The specified Backup ID or backup sequence number could not be found in the DP for ESS housekeeping files. User Response: None IDS2185I reading <DP for mySAP.com recovery log> and checking backup status... housekeeping files.
Explanation: DP for ESS is reading the information from the DP for mySAP.com recovery log file and checks the entries with the DP for ESS User Response: None IDS2200E The exception CIdsException was thrown. Reason: <reason text>
Explanation: DP for ESS uses an English NLS catalog for the LVM and the ESS 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: 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 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. 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
Explanation: In an EEE environment, for a restore of the database, DP for ESS 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 ESS. User Response: You have to select the same type or restore. 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 ESS must be started on all production servers. You selected different Backup IDs to restore. This is just a warning. DP for ESS allows to restore different Backup IDs. User Response: None
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
897
IDS2300E IDS2310W
are not explicitly set, then the values are as shown in the table at the top of the file. IDS2300E Cannot read file: <filename>. IDS2305E 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 tdpessdb2 are not set to 4750. Since the s-bit is not set, DP for ESS cannot switch between the users db2<sid> and root during the execution of the program. v the file system in which tdpessdb2 is installed was mounted with the NOSUID option. User Response: v Check the tdpessdb2 file in the directory /usr/tivoli/tsm/tdpessr3/db2/1.x.y.z, and set the access rights for tdpessdb2 with chmod 4750 tdpessdb2. After the installation, the command ls -l tdpessdb2.... outputs a line such as:
-rwsr-x--- 1 root dba 1918611 Apr 11 17:09 tdpessdb2
Explanation: DP for ESS is unable to read the data file <filename>. The affected files could 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. User Response: Check the access permissions of the affected file and try again. IDS2301E Cannot write file: <filename>.
Explanation: DP for ESS is unable to write to the data file filename. The affected files could be, e.g.: v one of the log/trace files as listed in Appendix C, Summary of Log and Trace Files, in Data Protection for IBM ESS for mySAP.com Technology Installation and Users Guide for DB2 UDB. 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. IDS2302E Environment variable <env_var> must be set!
(This is what setup.sh would do if the user had used it.) v If the file system in which tdpessdb2 is installed was mounted with the NOSUID option, mount the file system with SUID allowed. IDS2306I Issuing command <cmd>
Explanation: The tdpessdb2 program issues this message when running a system command. User Response: None. IDS2307I Issuing DB2 command <cmd>
Explanation: The environment variable <env_var> is required. The following environment variables must be set when running DP for ESS: INSTHOME: to the home directory of the DB2 user DB2INSTANCE: to the DB2 instance DB2DBDFT: to the DB2 default database User Response: Set the missing environment variable and try again. IDS2303E Environment variable <env_var> is not correct!
Explanation: The tdpessdb2 program issues this message when running a DB2 command. User Response: None. IDS2310W The free space in the file system containing the directory <dir> is only <freespace>.
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. IDS2304E File not found or not accessible: <filename>.
Explanation: The existing free space of the file systems containing the following directories will be checked: v the database home directory and v the directory specified by the parameter LOG_TRACE_DIR in the .fcs file and 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 of 50 mega bytes, DP for ESS warns the user. If it is under 5 mega bytes 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.
Explanation: The file <filename> was not found or is not accessible to DP for ESS. 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.
898
IBM Tivoli Storage Manager: Messages
IDS2311E IDS2502E
IDS2311E Idscntl requires a free space of at least 5 MB in the file system containing the directory <dir>. IDS2408W Warning: File <file name> still exists on the backup system.
Explanation: If the free space of the checked file systems (see Explanation of IDS2310W) is under 5 mega bytes 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. IDS2315W Environment variable DB2NODE has value <value>.
Explanation: DP for ESS 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, then 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. IDS2500E DB2 command failed: <cmd>.
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 ESS, then DP for ESS must unset this variable for the DP for ESS execution. User Response: None
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.
IDS2316E
Environment variable DB2NODE could not be unset! Unset this variable and restart tdpessdb2.
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 ESS, then DP for ESS must unset this variable for the DP for ESS execution. While trying to unset the variable DB2NODE, DP for ESS encountered an error. User Response: You have to unset the variable DB2NODE manually and rerun DP for ESS. IDS2317I Environment variable DB2NODE is successfully unset.
Explanation: DP for ESS tried to connect to the DB2 database <DBname> on the production system via a db2 remote connection. While trying to connect, DP for ESS 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: 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 ESS, then DP for ESS must unset this variable for the DP for ESS execution. User Response: None 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.
Explanation: DP for ESS tried to attach to the DB2 instance <instance> on the production system via a db2 remote connection. While trying to attach, DP for ESS 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
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
899
IDS2505E IDS2522I
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 The DB2 instance <instance> is running in <bitwidth> bit mode but tdpessdb2 is running in <bitwidth> bit mode. User Response: Change all tablespaces to DMS IDS2517E Tablespace <TBSname> is not in NORMAL state.
Explanation: DP for ESS 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 ESS determined, that the DB2 instance <instance> is running in <bitwidth> bit mode. But the version of DP for ESS which is installed, is running in a different bit mode. This is not allowed. User Response: You have to install the DP for ESS package with the correct bitwidth IDS2510E The DB logretain mode is not supported. Please switch logretain to RECOVERY.
Explanation: DP for ESS 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: 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: DP for ESS 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. User Response: None. IDS2521I Database <DB alias name> has been cataloged
Explanation: On the backup system DP for ESS 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. User Response: None. IDS2522I Press [ENTER] when all logfiles are restored...
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: DP for ESS 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 restore 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.
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 ESS determined one or more tablespaces with an unsupported type on the production DB2 database. Only DMS tablespaces are supported. .
900
IBM Tivoli Storage Manager: Messages
IDS2550E IDS2609E
IDS2550E Database <DBname> cannot be set to write suspend mode 3. One or more DP for ESS processes running for the production servers were terminated User Response: 1. Check the DP for ESS parameter DB2_EEE_SYNCTIMEOUT in the DP for ESS configuration file. 2. Check that DP for ESS is running on the backup system for all production servers. 3. Check for error messages in the DP for ESS log files for each process. IDS2607I Enter the TCPIP service port for the socket server [57330]:
Explanation: DP for ESS 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 ESS 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 ESS tried to connect to the production system via TCP/IP socket communication. Normally the cause for this error is, that the DP for ESS socket server on the production system is not running or the configuration for the DP for ESS socket communication on the production and / or backup system is incorrect. User Response: User Response: Check the DP for ESS socket configuration (/etc/services, /etc/inittab) and check for a running DP for ESS socket server on the production system. IDS2600E Starting synchronization for all EEE nodes failed
Explanation: DP for ESS has 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 system. The DP for ESS function configure will perform this configuration on the production system. You have to enter a TCP/IP service port to use for DP for ESS. User Response: User Response: None IDS2608E The TCPIP service port <port> is already in use. Please select another port.
Explanation: DP for ESS has 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 system. The DP for ESS function configure will perform this configuration on the production system. You have to enter a TCP/IP service port to use for DP for ESS. 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.
Explanation: DP for ESS 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: DP for ESS has 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 system. The DP for ESS function configure will perform this configuration on the production system. You have to enter a TCP/IP service port to use for DP for ESS. User Response: You have to enter a valid TCP/IP port.
Explanation: While DP for ESS is waiting for all running tdpessdb2 processes to reach the specified SyncPoint, one or more tdpessdb2 processes have not reached this syncpoint. This error can have the following reasons: 1. The DP for ESS parameter DB2_EEE_SYNCTIMEOUT is set to small. Check the DP for ESS parameter DB2_EEE_SYNCTIMEOUT in the DP for ESS configuration file 2. DP for ESS is not started for each production servers
Chapter 13. Data Protection for ESS for mySAP.com Technology for DB2
901
902
IBM Tivoli Storage Manager: Messages
Chapter 14. Data Protection for Enterprise Storage Server for mySAP.com Technolgy for Oracle (EEO0020EEO7900) and (IDS1000IDS1999)
This chapter describes the messages issued by Data Protection for ESS for mySAP.com Technology for Oracle. The messages begin with either the refix EEO or IDS and are listed in numerical order.
EEO0020I ====>Performing DP FOR ESS <v1> command. EEO0059E The database was backed up using NOCOPY type of FlashCopy. The data in the target ESS volumes is not valid, and cannot be used to perform a FlashBack Restore.
Explanation: This message is displayed starting the specified function. User Response: None. EEO0022I AIX Version: <var1> Oslevel: <var2>.
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. EEO0062E 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: Displays AIX version and oslevel. User Response: None. EEO0023I ESS CopyServices CLI Version: <var1>.<var2>.
Explanation: Displays ESS CopyServices CLI version. User Response: None. EEO0030I Number of ESS Volumes to be FlashCopied: <v1>
Explanation: Number of ESS volumes to be FlashCopied. User Response: None. EEO0056I Received error errno while disabling the new resources.
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 orginal source LUNs. User Response: The source / target information in the setup file cannot be modified. In order to backup the database to different target LUNs, use a different setup 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.
Explanation: An error occurred when the process attempted to disable the resources obtained for performing the DB backup. User Response: Check the error log for details. EEO0058I Received error errno while resetting the target volumes.
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. 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: An error occurred when the process attempted to withdraw the FlashCopy relationship between the source and target volumes. User Response: Check the error log for details.
Explanation: Incremental FlashCopy is only supported on ESS Microcode and CopyServices CLI versions 2.3.0
Copyright IBM Corp. 1993, 2004
903
EEO0067W EEO0123E
or later. As this version of ESS CopyServices CLI is lower than 2.3.0, an incremental FlashCopy cannot be performed. User Response: 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. 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>
Explanation: Incremental Change Recording is enabled. Performing a copy type of FlashCopy will fail in this case. User Response: 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. EEO0068W WARNING!!! Incremental Change Recording is enabled. Performing incremental FlashCopy instead of NOCOPY type of FlashCopy.
Explanation: Displays the number of sectors yet to be 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. User Response: None. EEO0120E A null logical volume has been detected.
Explanation: DP for ESS could not 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. EEO0121E A null volume group has been detected.
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 ESS volumes for this database, using the DP for ESS withdraw command, if you are interested in a NOCOPY type of FlashCopy. EEO0069W WARNING!!! Incremental FlashCopy feature is not supported on this version of AIX: <v1>. A generic FlashCopy will be performed instead.
Explanation: DP for ESS could not determine a volume group 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.. EEO0122E 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. EEO0123E The physical volumes of the volume group <v1> were not found.
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. EEO0070E Some of the ESS volumes belonging to this database have Incremental Change Recording enabled while others do not.
Explanation: DP for ESS will issue the command lsvg -M <vgname> in an LVM mirror environment to determine the physical and logical volumes on which the production database is residing. This command failed. User Response: Check the return code of lsvg. Consult the AIX system documentation.
Explanation: In order to perform an incremental FlashCopy, all the ESS volumes belonging to the database must have Incremental Change Recording enabled. User Response: Withdraw the FlashCopy relationships for those ESS volumes that have Incremental Change Recording enabled, using the DP for ESS withdraw command, and then retry the command. In the case of
904
IBM Tivoli Storage Manager: Messages
EEO0124I EEO0138I
EEO0124I Mounting filesystem : fs1. EEO0129E Removing device parm1 failed.
Explanation: Currently attempting to mount the file system. User Response: None EEO0125E The serial number for the device logdev could not be found.
Explanation: DP for ESS will remove the logical devices from the Device Configuration database (ODM) on the backup system after the backup ended and prior to the withdraw of the relationships of the ESS volumes. The rmdev command has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check if the device is a member of an active volume group. Check for preceding errors. EEO0130W Removing the mount point directory <mntpt1> failed with rc: <rc1>.
Explanation: DP for ESS will determine the ESS volumes serial numbers from the list of database files passed. In order to do that, several system command will be used such as: lscfg -pvl devname or lsvpcfg or rsList2105s.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. EEO0126I Trying to find new devices to match the source device. This process will take some time...
Explanation: An error occurred while trying to remove a mount point. Processing continues. User Response: None. EEO0131E The physical volume ID <pvid1> is duplicate on the production machine.
Explanation: Currently trying to find a target device to match with the source device. User Response: None. EEO0127I Removing device : devname
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: v If the hdisks with the same pvid belong to the same multipath, convert the ESS 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 issuing the AIX chdev command with the following arguments: chdev -l hdisk# -a pv=clear EEO0132W The umount command failed with rc <rc> for mount point <mntpt>.
Explanation: DP for ESS 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 ESS volumes. User Response: None EEO0128E 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. User Response: Perform one of the following: 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 disk- remove 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 .
Explanation: An error occurred while trying to remove a mount point. Processing continues. User Response: None. EEO0138I 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.
Chapter 14. Data Protection for ESS for Oracle
905
EEO0139W EEO0154I
User Response: None. EEO0139W Removing the file system on the mount point <mntpt1> failed with rc: <rc1>. EEO0148I Importing volume groups now...
Explanation: Processing an importing volume group command. User Response: None EEO0149I Newly imported volume group: vgname
Explanation: An error occurred while trying to remove a file system during the FlashBack Restore. Processing continues. The restore will resolve this problem. User Response: None. EEO0140I 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: DP for ESS has successfully 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: 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. User Response: None. EEO0143E Unsupported volume group <v1> has been detected.
Explanation: An error has occurred determining the logical volume of a file in the list of database files. User Response: Check the specific error message. Consult the AIX system documentation.. EEO0151E Varying off volume group vgname failed.
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. EEO0146E A physical disk from the volume group vgname was not found.
Explanation: Prior to the withdraw of the ESS FlashCopy relationships, DP for ESS will vary off the database volume group on the backup system. The command varoffvg has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors during the unmount process. EEO0152I Removing volume group fnm1 ....
Explanation: A physical disk from the specified database volume group was not found in the Device Configuration database. User Response: Check the specific error message. Consult the AIX system documentation. Check if this device is a member of one active volume group. Check for preceding errors.. EEO0147I Exporting volume group vgname failed.
Explanation: Attempting to remove the volume groups. User Response: None. EEO0153I Varied off and exported volume group : vgname..
Explanation: DP for ESS will issue the command exportvg prior to the withdraw of the ESS FlashCopy relationships to remove the volume group from the Device Configuration database. This command has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors during the unmount of the file systems.
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 ESS 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. User Response: None.
906
IBM Tivoli Storage Manager: Messages
EEO0156I EEO0178I
EEO0156I Finding the serial numbers ... User Response: Set the scheduling policy of this logical volume to parallel. EEO0170W Logical volume lvname has number stale partitions.
Explanation: DP for ESS 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: DP for ESS 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 ESS that was chosen for the FlashCopy on this specific run must be free of stale partitions. User Response: Check why you have stale partitions. If necessary, synchronize the logical volumes of the production database. EEO0172E Logical volume lvname must have mirror write consistency on.
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. 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. User Response: Check the operating system error issued by lsvg. Consult the AIX documentation. EEO0164E Quorum of the volume group vgname must be off.
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 ESS 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 ESS identifier.
Explanation: In a high-availability LVM mirror environment, DP for ESS 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. EEO0166E Logical volume vgname must have at least 2 copies.
Explanation: DP for ESS requires that all the partitions of one mirror set must reside on the physical volumes of one ESS. User Response: You have to reconfigure the allocation on the production system. EEO0176E Some of the partitions of lvname are stale on the specified ESS identifier.
Explanation: If the parameter for working with LVM mirrors is active, DP for ESS requires that two copies of each logical volume exist. User Response: Create a copy of each logical volume on separate ESS machines. Ensure that you have for each source volume a target volume for the FlashCopy in the same ESS and, for microcode level V1, in the same LSS. EEO0168E Logical volume lvname must have the parallel scheduling policy.
Explanation: DP for ESS 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 ESS that was chosen for the FlashCopy on this specific run must be free of stale partitions. User Response: Check the reason you have stale partitions. Synchronize the logical volumes of the production database. EEO0178I Could not determine the number of paths to target volumes. Using default value of 1.
Explanation: DP for ESS 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.
Explanation: DP for ESS supports SDD (Subsystem Device Driver). SDD is a pseudo device driver designed to support the multipath configuration environments in the IBM ESS and is used to enhance data availability. DP for ESS will determine the number
Chapter 14. Data Protection for ESS for Oracle
907
EEO0180E EEO0290E
of multiple paths queryng the Device Configuration database (ODM). User Response: If you want to use the 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. EEO0190E The number of new volume groups is limited to 256.
Explanation: DP for ESS can support a database with maximum 256 volume groups. User Response: You have to reconfigure your production database. EEO0191I Varying on volume group vgname failed.
Explanation: In a high-availability LVM mirror environment, DP for ESS 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 ESS must remove it by calling the command chfs to the original names. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors. EEO0182E The same hdisk devname cannot be associated with two different vpaths (serial numbers serial#1 and serial#2).
Explanation: Post to the importvg or recreatevg, DP for ESS will vary on the database volume group on the backup system. The command varonvg has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors. EEO0272I Flushing the buffers to disk...
Explanation: Currently synchronizing to force the buffers to disk. User Response: None EEO0273I Unmounting the file system mntpt1...
Explanation: DP for ESS has 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. EEO0184E lsvg command failed.
Explanation: Currently attempting to unmount the file system from the mount point. User Response: None EEO0274I Bringing up the volume groups...
Explanation: DP for ESS uses the command lsvg to determine the physical and logical volume of the volume group. This command has failed. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors. EEO0186I Recreating the new volume groups...
Explanation: The new resources will be available after the FlashCopy. User Response: None EEO0275I There are too many file systems.
Explanation: The number of file systems exceeds compiled limit of 4096. User Response: You have to reconfigure your production database. EEO0290E The source volume with serial number serial # is no longer attached to the production system.
Explanation: In a high-availability LVM mirror environment, DP for ESS will use the recreatevg command to create the volume groups after the FlashCopy on the backup system. User Response: None EEO0188E lvm queryvg failed.
Explanation: DP for ESS uses the system routine lvm_queryvg to read information of the VGDA of the volumes. User Response: Check the specific error message. Consult the AIX system documentation. Check for preceding errors.
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 ESS Web 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
908
IBM Tivoli Storage Manager: Messages
EEO0291E EEO0301W
have a valid disk backup on the target ESS volumes. EEO0291E The source volume with serial number serial # belongs to another volume group. EEO0297W The newly added volume logdev will be deleted from the database volume group vgname.
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, DP for ESS 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 ESS volumes. EEO0292W The logical volume lvname on the mount point mp was renamed or newly added.
Explanation: The reducevg command removes physical volumes from a volume group. DP for ESS 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 EEO0299I The following commands should be run after the FlashCopy process in the background is finished to synchronize the LVM copies.
Explanation: DP for ESS 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 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 ESS hdisk device volume group vgname to a Subsystem Device Driver vpath device volume group.
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. User Response: DP for ESS 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 ESS 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 List of the current file systems on the backed up volume groups ...
Explanation: For the function FlashCopy backup, DP 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 on the backup system. User Response: Check the return code and the error message of the hd2vp command. Consult the AIX system documentation. EEO0301W The rmlv command lv ended with return code rc.
Explanation: Prior to the start of the FlashBack Restore, DP for ESS will display a list of all the file systems which are currently on production database system. User Response: None EEO0294I List of file systems which will be restored...
Explanation: Prior to the start of the FlashBack Restore, DP for ESS will display a list of all the file systems that were on production database system at the time of the FlashCopy backup. User Response: None
Explanation: For the function FlashBack Restore, DP for ESS 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. User Response: Check the return code and the error 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 ESS volumes.
Chapter 14. Data Protection for ESS for Oracle
909
EEO0302E EEO0310I
EEO0302E DP for ESS encountered a problem when using the FlashCopy function of the ESS Copy Services. EEO0306W The mklvcopy command cmd ended with return code rc.
Explanation: DP for ESS requested, for a set of ESS source/target volume pairs, that a FlashCopy 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, 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 will find the failing volume(s) along with details about possible causes of the problem. EEO0303E The file system fs already has an entry in /etc/filesystems.
Explanation: DP for ESS will call the command mklvcopy to add a copy of a logical volume on the physical volumes residing on the second ESS. 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. User Response: Check the return code and the error 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 ESS volumes. EEO0307I Removing copies from the logical volumes ...
Explanation: On the backup system after the FlashCopy, DP for ESS 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 with return code rc.
Explanation: For 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 actual FlashCopy reverse. User Response: None EEO0308I Removing physical volumes from the volume groups ...
Explanation: The reducevg command removes physical volumes from a volume group. DP for ESS 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 on the ESS 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 on the ESS that is not yet involved in the FlashCopy User Response: Check the return code and the error message of the reducevg command. Consult the AIX system documentation. EEO0305W The extendvg command cmd ended with return code rc.
Explanation: For the function FlashBack Restore, after the rmlvcopy and prior to the exportvg and the actual FlashCopy reverse, DP for ESS will use the command reducevg to remove the physical volumes residing on the second ESS. User Response: None EEO0309I 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 ESS will add the physical volumes residing on the second ESS to the database volume groups. User Response: None EEO0310I Adding copies to the logical volumes ...
Explanation: The extendvg command adds physical volumes to a volume group. DP for ESS will call it to add the volumes which reside on the ESS that is not yet involved in the FlashBack to the database volume groups. User Response: Check the return code and the error message of the extendvg command. Consult the AIX system documentation.
Explanation: On the function FlashBack Restore, DP for ESS will use the command mklvcopy to add the copies of the logical volumes on the second ESS. This will take effect after the importvg and the extendvg. User Response: None
910
IBM Tivoli Storage Manager: Messages
EEO0311W EEO0321E
EEO0311W The command cmd ended with return code rc. from the production database. EEO0316W The database volume groups do not contain currently any file system.
Explanation: The execution of the system command ended with the displayed return code. User Response: Check the return code and the error message of the specified command. Consult the AIX system documentation. EEO0312E Importing the volume group from hdisk logdev failed.
Explanation: This message will appear if, when running the function FlashBack Restore, no file system was found on the original database volume group. Following this, DP for ESS will display a list of the file systems that reside on the FlashCopy target volumes. These will be restored by means of FlashBack. User Response: None. EEO0317W One or more errors were found disabling the production system resources. However, the FlashBack Restore will continue.
Explanation: DP for ESS 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. User Response: Check the return code and the error message of the importvg command. Consult the AIX system documentation. EEO0313E Recreating the volume group from the hdisks hdisks failed.
Explanation: This message will appear if, when running the function FlashBack Restore, an error occurs unmounting the existing file systems and removing the volume groups. However, DP for ESS will continue with the FlashBack Restore. User Response: None. EEO0320E 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.
Explanation: DP for ESS will use the 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 ESS where the FlashCopy was issued. User Response: Check the return code and the error message of the recreatevg command. Consult the AIX system documentation. EEO0314W Removing the logical device logdev with the same PVID pvid in the ODM.
Explanation: The output of the command lspv shows 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 Physical volume <hdisk> is in the descriptor area of the volume group <vgname> but does not belong to this volume group.
Explanation: There is still another logical device (hdisk or vpath) in the state defined with the same PVID as one of the source volumes. User Response: None EEO0315I Could not mount all the filesystems originally present.
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 ESS 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
Chapter 14. Data Protection for ESS for Oracle
Explanation: This message will appear if 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
911
EEO0322W EEO0356E
documentation to repair the ODM. EEO0322W The major number of the volume group <vgname> could not be determined. EEO0352E Wrong volume size for the target volume tgt1 is specified in the setup file.
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. 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: 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 Unable to open file file1.
Explanation: An error was detected when trying to open the file. The file may not exist. User Response: Make sure the file exists. EEO0354I Performing <fctype> FlashCopy of source ESS volume <src1> to target ESS volume <tgt1>
Explanation: DP for ESS 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 on an LVM mirror environment.
Explanation: A FlashCopy from the source volume to the target volume was requested. User Response: None. EEO0355E The ESS FlashCopy command failed.
Explanation: The LVM mirroring capability of DP for ESS 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. EEO0350E Error to get the size of the target volume src1 with return code rc1.
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 Enterprise Storage Server administrator to obtain the appropriate level of Copy Services command line interface and microcode. EEO0356E Cannot find a target volume to match with the source volume parm1.
Explanation: The ESS query command cannot determine the size of the target volume. 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. 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 Logical Subsystem (LSS) (unless microcode level V2 or above is used). 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.
Explanation: A target volume could not be found. User Response: If using microcode level V1, make sure the target volumes reside in the same Logical Subsystem (LSS) as the source volumes. Also, make sure that the target volumes are available to the backup
912
IBM Tivoli Storage Manager: Messages
EEO0357I EEO0368I
system and that 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 EEO0357I Performing FlashCopy withdraw of source ESS volume <src1> from target ESS volume <tgt1> EEO0362I Checking the status of the primary Copy Services server...
Explanation: Currently verifying the primary Copy Services server status. User Response: None EEO0363I Primary Copy Services server is ready.
Explanation: The primary Copy Services server is ready. User Response: None EEO0364I The connection to the primary Copy Services server failed. The process continues to check the backup Copy Services server.
Explanation: A FlashCopy withdraw of the source volume from the target volume was requested. User Response: None. EEO0358E No target volume is available. Terminating......
Explanation: No target volume was found. User Response: If using microcode level V1, make sure the target volumes reside in the same Logical Subsystem (LSS) as the source volumes. Also, make sure that the target volumes are available to the backup system and that 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 EEO0359I Incremental Change Recording: <val1>
Explanation: The primary Copy Services server is not available. Verify that the TCP/IP connection is valid. User Response: None EEO0365I Checking the status of the backup Copy Services server...
Explanation: Currently verifying the backup Copy Services server status. User Response: None EEO0366I FlashCopy was performed with <parm1> option.
Explanation: Value of Incremental Change Recording. User Response: None. EEO0360I Querying the ESS for the size of volume volser1...
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 ESS overrides this value under certain conditions. User Response: None. EEO0367I Source and Target ESS 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.
Explanation: A query of the target volume was requested. User Response: None EEO0361I A NOCOPY FlashCopy was performed. Withdrawing the nocopy FlashCopy relationship
Explanation: Whenever user performs an incremental FlashBack Restore operation, the source and target ESS volumes will be reversed. User Response: None. EEO0368I The backup Copy Services server is ready...
Explanation: The FlashCopy relationship between the source and target volumes terminates after the NOCOPY FlashCopy is performed. User Response: None
Explanation: The backup Copy Services server is ready. User Response: None
Chapter 14. Data Protection for ESS for Oracle
913
EEO0369E EEO0640E
EEO0369E Both the primary Copy Services server and the backup Copy Services server are not available... EEO0376E Error: ESS target volume v1 involved in the previous backup does not exist in the setup file.
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 that the TCP/IP connection is valid for both Copy Services servers. Also, verify that the ESS is configured correctly. EEO0370E A Copy Services backup server has not been specified. Exiting...
Explanation: The list of target volumes specified in the setup file for restoring a specified database using FlashBack Restore need 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 An invalid value: <parm1> has been specified for FlashCopy type.
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 connection is valid for the backup Copy Services server. Also, verify that the ESS is configured correctly on the backup Copy Services server. EEO0371I Value of FlashCopy type is: <parm1>.
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 ESS for pending sectors for volume: <volser1>
Explanation: None. User Response: None. EEO0372I A primary Copy Services server has not been specified.
Explanation: A query of all the source and target volumes was requested to ensure that background copy is not in progress between them. User Response: None. EEO0400E Error on running command: parm1
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 EEO0374I Querying the ESS for the status of volumes volser1...
Explanation: An error was detected while running a system command. User Response: Gather log file information and contact your IBM service representative. EEO0630E A memory allocation error has occurred.
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. EEO0375E Error: ESS volumes are involved in a FlashCopy or a PPRC operation.
Explanation: Not enough memory was available to continue processing. User Response: Ensure that your system has sufficient real and virtual memory. Close unnecessary applications. EEO0640E Could not open trace file <v1>.
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.
Explanation: There were some problems opening tracefile. Make sure you can open the trace file which was specified in the setup file. User Response: None.
914
IBM Tivoli Storage Manager: Messages
EEO0641E IDS1011E
EEO0641E Could not create the trace object. IDS1005I Start of splitint program at: time.
Explanation: There was a problem creating the trace class object. User Response: None.
Explanation: DP for ESS started at time. User Response: None. IDS1007I End of splitint program at: time.
EEO7366E
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). User Response: Check the specific operating system error message. EEO7367E Unable to write to trace file <tracefile>. Tracing disabled.
Explanation: DP for ESS ended at time. 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) User Response: None. IDS1008E Parameter <keyword> in the profile file required.
Explanation: An error occurred when writing to the specified tracefile. User Response: Ensure the device for the tracefile is available and has sufficient space for the file. Retry the command. EEO7826E Unable to open trace output file <file-name>.
Explanation: The parameter <keyword> in the profile for DP for ESS could not be found. It must be defined. User Response: Set the parameter <keyword> and its value in the profile for DP for ESS. IDS1009E Directory path <path> for the IDS control file does not exist.
Explanation: The DP for ESS 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. IDS1000E Profile not specified
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: DP for ESS 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: 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>] When the FlashCopy function runs under the control of the mySAP.com DBA tool 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. IDS1011E Option -f <function> not specified.
Explanation: An invalid argument has been specified for the -f option of DP for ESS. User Response: Ensure that you pass a valid function name with the option -f. Valid functions are: withdraw, split, password, unmount, and inquire. IDS1004E Subfunction not defined.
Explanation: An invalid argument has been specified for the -s option of DP for ESS. 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.
Explanation: splitint always requires the option -f <function> with a valid function. User Response: Ensure that the splitint call has the
Chapter 14. Data Protection for ESS for Oracle
915
IDS1014I IDS1016W
following form: <path>/splitint -p <path>/init<SID>.fcs -f <function>.... IDS1014I <subsystem message> User Response: Ensure that the profile contains entries for SHARK_SERVERNAME_PRIMARY and SHARK_SERVERNAME_BACKUP and their values form a valid TCP/IP address. Contact your ESS administrator. IDS1016E None of the mirror copies of <logical volume> resides completely on the specified ESS <ESS id>.
Explanation: DP for ESS received an information message from the IDS subsystem. User Response: None. IDS1015W <subsystem message>
Explanation: DP for ESS received a warning message from the IDS subsystem. User Response: None. IDS1016E <subsystem message>
Explanation: All existing copies of the displayed logical volume are spread over physical volumes that reside on multiple ESS units. User Response: Check the LVM mirroring configuration of the production database and ensure that each AIX mirror copy resides on a separate ESS. IDS1016E Quorum of the volume group <volume group> must be off.
Explanation: DP for ESS received an error message from its IDS control part. User Response: See the subsystem error messages for more information and perform required action. IDS1016E Neither the primary nor the backup ESS server has been specified.
Explanation: DP for ESS requires that the quorum property of a mirrored volume group be set to off. User Response: Set the quorum to off. IDS1016E The logical volume <logical volume> must have at least 2 copies.
Explanation: Neither the SHARK_SERVERNAME_PRIMARY nor SHARK_SERVERNAME_BACKUP parameter has been specified in the DP for ESS profile (init<SID>.fcs). User Response: Ensure that the profile contains entries for SHARK_SERVERNAME_PRIMARY and SHARK_SERVERNAME_BACKUP and that their values form a valid TCP/IP address. IDS1016I(E) The ESS primary server is down or has an invalid address. Explanation: The ESS primary server with the TCP/IP address specified in the parameter SHARK_SERVERNAME_PRIMARY is down or cannot be reached. User Response: If this message appears as a information message, SHARK_SERVERNAME_BACKUP was specified and the connection will be made via its TCP/IP address. Otherwise, this message will appear as an error. Ensure that the profile contains entries for SHARK_SERVERNAME_PRIMARY and SHARK_SERVERNAME_BACKUP and their values form a valid TCP/IP address. IDS1016E There is a problem with both ESS copy services.
Explanation: DP for ESS requires that each logical volume making up the production database have at least 2 copies. User Response: Add an AIX copy for the displayed logical volume. IDS1016E The logical volume <logical volume> must have the parallel scheduling policy.
Explanation: DP for ESS requires that the property scheduling policy of a logical volume be set to parallel. User Response: Set the scheduling policy property to parallel. IDS1016W The logical volume <lv name> has <# of stale partitions> stale partitions.
Explanation: DP for ESS issues a warning if one of the logical volumes has stale partitions, independent of whether or not it resides on the selected ESS. User Response: Check why the system has stale partitions. Check the AIX error log. Synchronize the AIX mirror copies.
Explanation: Neither the connection to the ESS primary server nor the one to the ESS backup server is working properly.
916
IBM Tivoli Storage Manager: Messages
IDS1016E IDS1030I
IDS1016E Some of the partitions of <logical volume> are stale on the specified ESS <ESS id>. User Response: None. IDS1023I Exiting with return code <rc>.
Explanation: The displayed logical volume has one copy residing completely on the specified ESS id, but this copy contains some stale partitions. In this case, DP for ESS will end immediately. User Response: Check why the system has stale partitions. Synchronize the AIX mirror copies. IDS1016E The logical volume <lv name> must have mirror write consistency set to yes.
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 Exiting with return code <rc>.
Explanation: DP for ESS requires that the property mirror write consistency of a logical volume be set to yes. User Response: Set the property mirror write consistency of the corresponding logical volume to yes using smitty. IDS1016E Unable to find the journaled file system log.
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. IDS1025I Time stamp: <current_time>
Explanation: DP for ESS requires that one copy of the journaled file system log of each volume group reside on the specified ESS. User Response: Ensure that each volume group has a copy of the journaled file system log on the specified ESS. IDS1016E The mount point <mount point> already exists
Explanation: DP for ESS 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. User Response: None. IDS1026I Start of splitint on the production system ...
Explanation: DP for ESS has issued a call to the production system and is waiting for the end of the execution. User Response: None. IDS1027I splitint ended on the production system successfully.
Explanation: Prior to enabling the new resources on the backup system, DP for ESS checks if the file system has an entry in /etc/filesystems. If so, the program terminates immediately. User Response: Run DP for ESS (splitint) with the option -f withdraw to disable all the resources for the last run. IDS1016E The same hdisk <disk name> cannot be associated with two different vpaths (serial numbers <ser_no_1> and <ser_no_2>).
Explanation: DP for ESS has ended the call to the production system successfully. User Response: None. IDS1028E splitint ended with errors on the production system.
Explanation: This is an incorrect SDD configuration. User Response: The IBM publication Subsystem Device Driver Users Guide explains how to configure SDD. IDS1020I The FlashBack Restore ended successfully.
Explanation: The remote exec call to the production system has ended with errors. User Response: Check the specific error message. IDS1030I FlashCopy started ...
Explanation: The high-performance restore issued with the FlashCopy from the target volumes to the source volumes was completed successfully.
Explanation: The command with the split function has been issued on the production system, and the program splitint waits until this action has finished. User Response: None.
Chapter 14. Data Protection for ESS for Oracle
917
IDS1031I IDS1039E
IDS1031I FlashCopy successful. IDS1033I Information from DP for mySAP.com has been found with BACKUPID <backupid>.
Explanation: The command for the FlashCopy of the volume pairs has terminated successfully on the production system. User Response: None. IDS1032W Information from DP for mySAP.com was not found.
Explanation: The exchange data between DP for ESS and DP for mySAP.com was not found. As of DP for mySAP.com version 3.3.10, the information is exchanged through the call of the DP for ESSs 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.com you have installed does not support DP for ESS, or DP for mySAP.com 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 resolved depending on the specific situation: Case 1: brbackup has finished successfully. Result: The backup on disk (FlashCopy target volumes) as well as the one done to the Tivoli Storage Manager server are valid. However, DP for ESS cannot show the backup ID in its report when using the function inquire. Reason for warning: It is very likely that DP for mySAP.com (AIX version) does not have DP for ESS support (prior to version 3.1.0.3). Action: Install the appropriate DP for mySAP.com version. Case 2: brbackup has terminated abnormally. Result: Check carefully the run log of brbackup 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 Tivoli Storage Manager server is invalid. Cause: Any problems with the network or on the Tivoli Storage Manager server caused DP for mySAP.com running a backup to fail. Action: Depending on the error message, eliminate the reason for not getting a successful backup to the Tivoli Storage Manager server.
Explanation: The exchange data between DP for mySAP.com and DP for ESS has been found during the execution of the function unmount. The backup 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>. User Response: None. IDS1034E 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: Check for other errors prior to this one. IDS1035I 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 ESS 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). User Response: None. IDS1036E The backup ID was not passed by DP for mySAP.com. 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.com (backint) version 3.3.10. IDS1038I The IDS control file <ids_control_file> does not exist. It will be created.
Explanation: DP for ESS will write the first record to the IDS control file specified in the entry IDS_CONTROL_FILE of the profile. User Response: None. IDS1039E The IDS control file has no entry.
Explanation: DP for ESS has found the IDS control file, but it has no records. This error occurs when you start one of the functions inquire, withdraw or
918
IBM Tivoli Storage Manager: Messages
IDS1040E IDS1047I
unmount before you have run the split function for the first time. User Response: After you run at least one brbackup with a successful FlashCopy, the problem will be resolved. IDS1040E The IDS control file must be read or inserted before update. v List of files used for the backup v Backup type This message will be issued if DP for mySAP.com terminated unsuccessfully for some reason. User Response: Ensure that DP for mySAP.com runs successfully. IDS1043I The maximum number of backup cycles in the IDS control file has been reached.
Explanation: DP for ESS has detected a logical error when processing the IDS control file. User Response: Contact Data Protection for mySAP.com support. IDS1041W The value of the field field_name in the file file_name is empty.
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. User Response: None. IDS1044I Delete backup cycle with BSEQ_N = <bseq_n> and all associated files ...
Explanation: DP for mySAP.com (backint) calls DP for ESS (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
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. User Response: None. IDS1045W 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 Start of listing of importing volume groups/mounting file systems ...
>>> input_file <file list> <<< input_file If one of the fields of the topic backint_data is missing, this message is displayed. If the backup ID is empty, the process terminates with error IDS1036E. User Response: In order to use FlashBack Restore, ensure that you have installed DP for mySAP.com (backint) version 3.3.10. IDS1042W Info data from DP for mySAP.com /tmp/bki<SID>.ids cannot be read.
Explanation: After initiating the FlashCopy source/target volumes on the production system, DP for ESS will make the corresponding target volumes available to the backup host. A list of mount points or volume groups will be shown. User Response: None. IDS1047I End of listing.
Explanation: Before the unmount process, DP for ESS will read /tmp/bki<SID>.ids, which contains information about the backup that was done by DP for mySAP.com. Among the information read is: v Backup id v Util file used for the backup
Explanation: Corresponds to start message IDS1046I. User Response: None.
Chapter 14. Data Protection for ESS for Oracle
919
IDS1048I IDS1057E
IDS1048I The unmount process will be skipped because the progress status indicator (PSI) has a value of psi. IDS1054E No password stored.
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: Table 6 in Data Protection for IBM ESS for mySAP.com Technology Installation and Users Guide for Oracle 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 two entered passwords are not 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 split 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 ESS 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. 2. Check the path of the configuration file. The path must be specified in the profile (parameter CONFIG_FILE). 3. Make sure that the file access permissions are set correctly. IDS1056E The information of DP for mySAP.com could not be set in the IDS repository.
Explanation: The version of DP for ESS on the production system is different from the version on the backup system. User Response: Ensure that you install the same version of DP for ESS on the production and backup systems. You get the version number when you start splitint without parameters. IDS1051I 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 ESS program splitint uses the user ID to execute a remote shell on the production system. User Response: Enter the password for the corresponding user ID. IDS1052I Enter the password for the user <user ID> again
Explanation: After the mount of the file systems on the backup system was finished, the call of DP for mySAP.com (backint) takes place. Backint calls then DP for ESS 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: In order to avoid typing errors, you have to enter the password twice. User Response: Enter the password 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. User Response: Enter the password again. You are permitted three attempts before the program terminates.
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 SHARK_VOLUMES_FILE (.fct file).
920
IBM Tivoli Storage Manager: Messages
IDS1060I IDS1069E
IDS1060I Start of listing of exported volume groups/unmounting file systems ... IDS1065E You cannot run the function function if the progress status indicator (PSI) has a value of psi.
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 ESS will unmount the file systems and export volume groups on the backup host that had been imported or mounted when the DP for ESS split function was executed. User Response: None. IDS1061I Start the withdraw of the target-source pairs ...
Explanation: The backup cycle was left in a state that does not allow DP for ESS to start the specified function. User Response: Table 6 in Data Protection for IBM ESS for mySAP.com Technology Installation and Users Guide for Oracle shows the permissible functions depending on the backup progress status indicator. IDS1066E The option -f split can only be used on the backup system.
Explanation: The command with a withdraw has been issued from the backup system to the primary Copy Services server on the ESS. User Response: None. IDS1062I The progress status indicator (PSI) is already PSI_UNMOUNT_DONE.
Explanation: You cannot start the split function on the production system. User Response: Make sure you start splitint with the 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 only be used on the production system.
Explanation: DP for ESS 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. User Response: None. IDS1063E Parameters LOGON_HOST_PROD/ LOGON_HOST_BACK in profile wrong or missing.
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 The option -f withdraw can only be used on the backup system.
Explanation: Either DP for ESS is unable to read one of the parameters LOGON_HOST_PROD/ 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 hostnames must match the respective hostnames of the production and backup systems. 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>). 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: You cannot start the function withdraw on the production system. User Response: Make sure you start splitint with the function -f withdraw on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK. IDS1069E The option -f unmount can only be used on the backup system.
Explanation: You cannot start the function unmount on the production system. User Response: Make sure you start splitint with the function -f unmount on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK.
Explanation: An unknown parameter <keyword> has been found in the profile. User Response: Check the specified parameter in the profile and try again.
Chapter 14. Data Protection for ESS for Oracle
921
IDS1071E IDS1080W
IDS1071E Topic named <topicname> could not be found in the file <filename>. 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: DP for ESS could 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 SHARK_VOLUMES_FILE, you need to check whether the topic name has the format: >>> shark_volumes_set_# where # is a placeholder for the volume set number (1, 2, ..) When the affected file is another file, you likely have another error prior to this one. Otherwise, contact Data Protection for mySAP.com support. IDS1072E The source volume <serial number> cannot be specified as a target volume in the .fct file.
Explanation: If the DP for ESS 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 IDS1077I Semaphore released.
Explanation: DP for ESS 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 <shark_volumes_set_#> in file <filename>.
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: DP for ESS has read file <filename> contained in the parameter SHARK_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 Structure of the DP for ESS Target Volumes File in Data Protection for IBM ESS for mySAP.com Technology Installation and Users Guide for Oracle. IDS1070E The option -f flashback can only be used on the production system.
Explanation: If DP for ESS 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. System error <sys_errno>: <sys_message>.
Explanation: The FlashBack Restore (option -f flashback) can only be started from the production machine. User Response: To start the FlashBack Restore, log on into the production machine. IDS1075I Creating a semaphore for the critical part of importing/exporting ...
Explanation: If DP for ESS could not initialize 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. IDS1080W The semaphore could not be allocated. System error <sys_errno>: <sys_message>.
Explanation: When multiple production systems run a backup via a single backup system at the same time, DP for ESS will ensure that the critical parts of the code run for a single instance of the program at a time. These phases are:
Explanation: If DP for ESS could not allocate the semaphore, the system error number and message will be issued as a warning. The concurrent run of multiple
922
IBM Tivoli Storage Manager: Messages
IDS1081W IDS1089I
production systems with a single backup system will not work properly. User Response: Check the system error number and message with your system administrator. IDS1081W The semaphore could not be released. System error <sys_error>: <sys_message>. 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: If DP for ESS could not allocate 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. IDS1082E Duplicate target volume serial number was found in the target list.
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 value of the backup status indicator. Check for preceding errors. IDS1088W One or more errors were found disabling the production system resources.
Explanation: DP for ESS found a duplicate serial number for an ESS target volume in the file specified in the SHARK_VOLUMES_FILE parameter. User Response: Ensure that the serial numbers of the target volumes in the file SHARK_VOLUMES_FILE are unique. IDS1083I Function query ended successfully.
Explanation: DP for ESS has successfully ended the call of the function query to check the correct setup. User Response: None. IDS1084I This is your last chance to stop the FlashBack Restore. Enter c[ont] to continue, s[top] to cancel.
Explanation: Before the actual FlashBack Restore to the database volume occurs, DP for ESS 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 ESS will issue a warning but the FlashBack Restore will continue. User Response: None IDS1089I The FlashBack Restore was previously started. Please enter c[ont] to restart again or s[top] to cancel.
Explanation: This message is the breakpoint in the FlashBack Restore process. At this time, DP for ESS 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. User Response: Enter c to continue or s to stop. IDS1085E You cannot perform a restore from a FlashCopy backup of the type NOCOPY.
Explanation: Having a valid disk backup on the ESS target volumes, the user is always able to start the FlashBack Restore again, even though the background copy on the ESS of a prior FlashBack Restore is still running. This can be also 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 ESS volumes. User Response: If DP for ESS 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.
Explanation: The ESS allows the FlashCopy types COPY, INCR and NOCOPY. Only the FlashCopy backups made with the parameter FLASHCOPY_TYPE
Chapter 14. Data Protection for ESS for Oracle
923
IDS1090E IDS1122I
IDS1090E The NLS catalog could not be loaded. Make sure that the catalog exists. IDS1100E The parameter SHARK_ID_LVM_MIRROR has to be moved from the profile filename.fcs to the corresponding target set in filename.fct.
Explanation: DP for ESS uses an English NLS catalog for the LVM and the ESS part of the product. The installation process will copy the catalog to the displayed path. User Response: Check for errors during the installation procedure. IDS1091E You cannot run the function if the restore status indicator (RSI) has a value of RSI_START.
Explanation: In case of AIX LVM mirroring the parameter SHARK_ID_LVM_MIRROR indicates the identifier of the ESS to be selected for the mirror copy that should be used for the FlashCopy. This parameter is now contained in the target set 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.
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 has either the value: RSI_DISKONLY or in case of LVM mirroring: RSI_DISKANDLVM. User Response: Wait until the FlashCopy background process is finished. IDS1093E The target set id was not found.
Explanation: For the handling of 2 different LVM mirror sets, the user now must specify 2 different target sets in the .fct file. The parameter SHARK_ID_LVM_MIRROR, which determines which ESS should be taken as the source, will be specified here inside the corresponding target set as well. Internally DP for ESS keeps the status of each target set (progress status, backup status, restore status, backup sequence number, etc) in the house keeping directory. After the FlashCopy DP for ESS will reread the target set information again. This message can only be displayed if this information was destroyed, is corrupt or something unexpected occurs. User Response: Checks for other errors prior to this one. IDS1097E The option -f set_bki_info can only be used on the backup system.
Explanation: For the handling of 2 different LVM mirror sets, the user now must specify 2 different target sets in the .fct file. The parameter SHARK_ID_LVM_MIRROR, which determines which ESS should be selected for the FlashCopy, will be specified inside of the corresponding target set as well. Internally DP for ESS 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: Check for other errors prior to this one IDS1103W The restore status indicator (RSI) has a value of RSI_INVALID
Explanation: If the restore status RSI of the target set has a value of RSI_INVALID, this means that a FlashBack Restore was initiated but not ended. Though, DP for ESS will issue this warning and continue with the FlashCopy backup. User Response: Check if the FlashCopy backup ended successfully. IDS1121I Getting the source volumes ...
Explanation: DP for mySAP.com (backint) calls DP for ESS 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.
Explanation: The first step of DP for ESS in a FlashCopy backup is to determine the source volumes from the list of files passed by the corresponding calling UI backup tool. In an SAP environment this tool is the program brbackup. User Response: None. IDS1122I FlashCopying the sources to the target volumes ...
Explanation: After having found the pairs of volumes to be copied, DP for ESS signals to the calling program (brbackup) to set the database into backup mode, or, in case of backup type of offline_mirror, to shut down the database. Then the actual FlashCopy can be requested
924
IBM Tivoli Storage Manager: Messages
IDS1123I IDS1133E
to the ESS copy services server. User Response: None IDS1123I Enabling the volumes and filesystems ... 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.com in the file temp_file is empty.
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 IDS1125I Checking AIX LVM mirroring ...
Explanation: In a high-availability LVM mirror environment, DP for ESS 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). 2. Each logical volume must have at least two copies (see EEO0166E). 3. Each logical volume must have the parallel scheduling policy (see EEO0168E). 4. The mirror set that resides in the ESS 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 ESS (see EEO0174E). 6. Each logical volume must have the mirror write consistency 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: After brbackup has called DP for ESS to make the FlashCopy, DP for mySAP.com will be called and it will call DP for ESS 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 ESS 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 ESS 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 ESS ID in the parameter SHARK_ID_LVM_MIRROR for the corresponding target set in the .fct file <filename>.
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. 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 or incremental FlashCopy is copied. This helps reduce background copy completion time when
Explanation: DP for ESS found that some of the logical volumes on which the production database is residing are mirrored using the mirror capability of the Logical Volume Manager. However, the parameter SHARK_ID_LVM_MIRROR was not specified in the .fct file. This parameter causes DP for ESS to make all the necessary checks to get a consistent copy through the FlashCopy on the target volumes in an LVM mirror environment. User Response: Set the parameter
Chapter 14. Data Protection for ESS for Oracle
925
IDS1175E IDS1185I
SHARK_ID_LVM_MIRROR with the ESS ID that is used for the FlashCopy. IDS1175E The backup ID or the backup sequence number identifier was not found. BSI_START a disk backup as background copy was started and is still running, BSI_TAPEONLY only a backup on TSM is available BSI_DISKONLY only a backup on disk is available BSI_INVALID invalid entry for disk backup - initial value Other value is not allowed and makes this backup cycle unusable. User Response: Check the backup status indicator (BSI) of your target volumes calling the splitint executable with the option -f ts_inquire (target set inquire): splitint -p initSID.fcs -f ts_inquire -n target set number Check for preceding errors. IDS1180E IDS1176I The target set target_number does not contain a valid FlashCopy backup. (backup ID identifier). The FlashCopy run backup sequence number is a valid disk backup.
Explanation: DP for ESS did not find any entry in the IDSSAVE for the specified backup ID or backup sequence number. User Response: Normally the calling program must determine one valid backup ID or backup sequence number to be passed. Check for preceding errors..
Explanation: This message can be displayed when DP for mySAP.com calls DP for ESS to inquire for disk backups on the target sets. The target sets are enumerated starting with 1. User Response: None. IDS1177E The FlashCopy run backup sequence number was not a valid disk backup.
Explanation: DP for ESS has found that the selected backup to be restored has a valid disk backup with an entry in the IDSSAVE. User Response: None IDS1181E The FlashCopy run backup_sequence_number is not the last backup of target set number.
Explanation: To do a FlashBack Restore of a valid disk backup must exist on one of the target sets. The backup status indicator (BSI) must have the value BSI_DISKONLY. User Response: Check the backup status indicator (BSI) of your target volumes calling the splitint executable: splitint -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: This error message is issued if the FlashCopy backup run is no longer a valid disk backup. Normally, the calling UI (backint or tdpessora) ensures that the backups offered for selection are valid FlashCopy backups. User Response: Check for preceding errors. Call tdpessora and the inquire function of splitint to check this backup. IDS1183I A disk-only backup (option -d) was invoked, forcing the parameter FLASHCOPY_TYPE of the .fcs-file to COPY.
Explanation: The backup status indicator can accept one of the following values in the IDSSAVE: BSI_START a disk backup as background copy was started and is still running, BSI_TAPEONLY only a backup on TSM is available, BSI_DISKONLY only a backup on disk is available, BSI_INVALID invalid entry for disk backup and - initial value Other value is not allowed and makes the backup cycle unusable. User Response: Check the backup status indicator (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. IDS1179E The backup status indicator (BSI) for target set number is not valid.
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 ESS sets the value to COPY. User Response: None. IDS1184I Checking the backup status on Tivoli Storage Manager and on ESS disks ...
Explanation: This message is displayed by the program tdpessora during the inquire of the backups on Tivoli Storage Manager and on disk. User Response: None. IDS1185I Reading the SAP backup log <PATH>/back<SID>.log ...
Explanation: The backup status indicator can accept one of the following values for one specific target set:
Explanation: This message is displayed by the program tdpessora while reading the backup of the SAP system ID <SID>.
926
IBM Tivoli Storage Manager: Messages
IDS1186E IDS1198E
User Response: None. IDS1186E The parameter param in the profile <.sap file name> or the environment variable env_var is required. IDS1193I The FlashCopy run with backup ID id was of type NOCOPY.
Explanation: This error is issued by the program tdpessora 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. IDS1190E The information of the source / target volumes could not be found.
Explanation: This info message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or tdpessora) if one of the target sets contains a FlashCopy backup of type NOCOPY. User Response: None. IDS1194I The FlashCopy run backup_sequence_number has a backup status indicator (BSI) of status and is therefore not valid for FlashBack.
Explanation: The executable IDSCNTL will be started automatically as a daemon (sometimes referred as fcagent) to monitor the background copy. The ESS Copy Services CLI will be used to get the states of the copy process. This action has failed. User Response: Check the error log file idscntl_[p|b]_runagent_jjjjmmddHHMMSS.log in the directory specified in the parameter LOG_TRACE_DIR of the .fcs file. Check the connection from the host to the ESS with the command: SHARK_COPY_SERVICE_CODE/rsTestConnection.sh -v -s SHARK_SERVERNAME_PRIMARY or SHARK_COPY_SERVICE_CODE/rsTestConnection.sh -v -s SHARK_SERVERNAME_BACKUP Where SHARK_COPY_SERVICE_CODE, SHARK_SERVERNAME_BACKUP and SHARK_SERVERNAME_PRIMARY are values of parameters specified in the .fcs file. DP for ESS will restart the fcagent automatically. IDS1191I The target volumes set number does not contain a valid disk backup.
Explanation: This info message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or tdpessora). 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. User Response: None. 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.com. At restore time, DP for ESS 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.com supporting FlashBack Restore. Otherwise, you will have to restore from Tivoli Storage Manager. IDS1197I The list of files to be restored does not exist for the FlashCopy run backup_cycle_number.
Explanation: This informational message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or tdpessora) if one of the target sets contains an invalid disk backup. User Response: None. IDS1192I No disk backups were found on the target volumes.
Explanation: This informational message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or tdpessora) if the list of files was not found for one of the target sets. User Response: None. IDS1198E The last FlashCopy run was already assigned the backup ID identifier.
Explanation: This informational message is displayed during the call of the function get_disk_backups of DP for ESS (which is issued by the calling UI backint or tdpessora) if none of the target sets contains a valid backup. User Response: You will have to select a backup from Tivoli Storage Manager.
Explanation: After the mount of the file systems on the backup system finishes, the call of DP for mySAP.com (backint) takes place. Backint then calls DP for ESS with the function -f set_bki_info to set the Tivoli Storage Manager backup ID and other information. This message is displayed if this last call occurs more than once for the same FlashCopy run.
Chapter 14. Data Protection for ESS for Oracle
927
IDS1200E IDS1305E
User Response: Check the backup log of the program brbackup. IDS1200E The exception CIdsException was thrown. Reason: <reason text> v <LOG_TRACE_DIR>/splitint_b_<time>.trace v <LOG_TRACE_DIR>/splitint_p_<time>.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: At present, the only reason text is: Not enough memory space. Allocation error in file <file name>, line <line number>. User Response: Ensure that ora<sid> and the root user have the right setting for memory allocation. The 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. 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. IDS1300E Cannot read file: <filename>.
Explanation: The environment variable <env_var> is required. The following environment variables must be set when running DP for ESS: ORACLE_HOME: to the home directory of the user ID ORACLE_SID: to the mySAP.com for Oracle DB system ID User Response: Set the missing environment variable and try again. IDS1303E 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: DP for ESS is unable to read the data file <filename>. The affected files could be e.g.: v <ORACLE_HOME>/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 <ids_control_file> v the field value of EXCHANGE_FILE in a backup cycle record. User Response: Check the access permissions of the affected file and try again. IDS1301E Cannot write file: <filename>.
Explanation: The file <filename> was not found or is not accessible to DP for ESS. The affected files could be: <ORACLE_HOME>/dbs/init<SID>.fcs or the argument value of the option -i (that file 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 ESS 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 mounted with the NOSUID option. User Response: v Check the splitint file in the directory /usr/tivoli/tsm/tdpessr3/oracle/x.y.z, and set the access rights for splitint with chmod 4750 splitint.
Explanation: DP for ESS is unable to write to the data file filename. The affected files could be e.g.: v <LOG_TRACE_DIR>/splitint_b_<time>.log v <LOG_TRACE_DIR>/splitint_p_<time>.log
928
IBM Tivoli Storage Manager: Messages
IDS1308W IDS1322I
After the installation, the command ls -l splitint.... outputs a line such as:
-rwsr-x--- 1 root dba 1918611 Apr 11 17:09 splitint
IDS1318E
Operating system error <error_no>: <message text>.
(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. IDS1308W Warning: File <file name> still exists on the backup system.
Explanation: DP for ESS encountered an unexpected message error during the execution of a system function. The respective operating system error and message text will be displayed. The message will appear, for example, as a result of v a wrong user ID on the parameter LOGON_HOST_PROD in the fcs file v a wrong password given for the user ID on the parameter LOGON_HOST_PROD in the fcs file v a wrong TCP/IP name on the parameter LOGON_HOST_PROD in the fcs file (for example: connection timeout) v a failure allocating memory through the function malloc, and the operating system cannot satisfy the request User Response: Check the specific error message. IDS1320I Setting the tablespaces in backup mode or, in case of offline_mirror, the database will be shutdown.
Explanation: DP for ESS checks at the start of the split function whether 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. 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: 1. the database home directory 2. the directory specified by the parameter LOG_TRACE_DIR in the .fcs file and 3. 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 ESS 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. IDS1311E splitint requires a free space of at least 5 MB in the file system containing the directory path.
Explanation: DP for ESS 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 that the backup type is offline_mirror, to shut down the database. User Response: None. IDS1321I The tablespaces will end the backup mode or, in case of offline_mirror, the database will be started.
Explanation: DP for ESS 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 offline_mirror, to start the database again. User Response: None. IDS1322I The file filename is locked, waiting one second and retry!
Explanation: If the free space of the checked file systems (see Explanation of 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.
Explanation: DP for ESS 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 ESS uses a lock mechanism. User Response: None.
Chapter 14. Data Protection for ESS for Oracle
929
IDS1452E IDS1546I
IDS1452E This version of Data Protection for IBM ESS for mySAP.com Technology has expired. IDS1531E Timestamp string cannot be converted.
Explanation: This is a test version that has expired. User Response: Order a release version of Data Protection for IBM ESS for mySAP.com Technology or contact your IBM/Tivoli sales representative. IDS1453W This version of Data Protection for IBM ESS for mySAP.com Technology 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 Data Protection for IBM ESS for mySAP.com Technology or contact your IBM/Tivoli sales representative before the version expires. IDS1454I *** This copy is NOT FOR RESALE. ***
Explanation: The status of the background copy will be written by the DP for ESS 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 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 ESS. To calculate the transfer rate some conversion is needed. When doing this conversion, an error occurred. The rate value will be invalid. User Response: Check the date and time setting of the machine. IDS1540I Start of the FlashCopy agent on the backup system
Explanation: This version is not for resale. User Response: None. IDS1455E License file filename does not exist.
Explanation: The license file agentess.lic was not found where expected. User Response: Make sure that the agentess.lic file resides in the same directory as the init<SID>.fcs profile. IDS1456E Unable to access license file file name.
Explanation: DP for ESS will 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: None IDS1541I Removing the FlashCopy agent on the backup system
Explanation: Unable to access license file. User Response: Make sure the access permissions allow read/write access. IDS1457E License file file name contains invalid data/checksum.
Explanation: DP for ESS will automatically stop the FlashCopy agent daemon after the background copy has finished on the backup system. User Response: None IDS1545I Start of the FlashCopy agent on the production system
Explanation: The license file is invalid. 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.
Explanation: DP for ESS will automatically start a daemon (called the FlashCopy agent) to monitor the background copy after the start of a FlashBack Restore on the production system. User Response: None IDS1546I Removing the FlashCopy agent on the production system
Explanation: DP for ESS 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 the value of COPY or INCR. User Response: Normally, the calling program will control this process. Check for preceding errors.
Explanation: DP for ESS will automatically stop the FlashCopy agent daemon after the background copy has finished the restore on the production system. User Response: None
930
IBM Tivoli Storage Manager: Messages
IDS1550E IDS1553W
IDS1550E The FlashCopy agent could not be added to /etc/inittab.
Explanation: DP for ESS 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. However, DP for ESS was unable to add an entry to /etc/inittab. User Response: Check the rights of the DP for ESS executable (idscntl or splitint). IDS1551W The FlashCopy agent already exists in /etc/inittab.
Explanation: DP for ESS 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 ESS detected that an entry already existed. User Response: None IDS1552E The FlashCopy agent could not be removed from /etc/inittab.
Explanation: DP for ESS will automatically stop the FlashCopy agent daemon after the background copy has finished on the backup system or, in the case of FlashBack Restore, on the production system. The entry in /etc/inittab is removed. However, DP for ESS was unable to remove the entry. User Response: Check the rights of the DP for ESS executable (idscntl or splitint). IDS1553W The FlashCopy agent has already been removed from /etc/inittab.
Explanation: DP for ESS will automatically stop the FlashCopy agent daemon after the background copy has finished on the backup system or, in the case of FlashBack Restore, on the production system. The entry in /etc/inittab will be removed. However, DP for ESS detected that the entry no longer exists in the table. User Response: None.
Chapter 14. Data Protection for ESS for Oracle
931
932
IBM Tivoli Storage Manager: Messages
Chapter 15. Data Protection for Enterprise Storage Server for DB2 UDB (EEP0000EEP9999)
This chapter describes the messages issued by Data Protection for Enterprise Storage Server for DB2 UDB. The messages begin with the prefix EEP and are listed in numerical order.
EEP0010I v1 command completed successfully at: v2 User Response: Enter a supported command. See the Installation and Users Guide for information about supported commands. EEP0016I ====> Starting ITSM FOR HARDWARE - DP FOR ESS executable on the BACKUP SYSTEM: v1
Explanation: No error was detected. System Action: None. User Response: EEP0011E ERROR!!!Invalid number of arguments entered. Explanation: System Action: None. User Response: EEP0017E ERROR!!!You have to be root to run this program.
Explanation: Either incorrect arguments were entered or the specified file does not exist. System Action: Processing ends. User Response: Correct the arguments and start the process again. EEP0012E ERROR!!!Unexpected error occurred.
Explanation: You have to be root to run this product. System Action: Processing ends. User Response: Switch user id to root and try again. EEP0018E ERROR!!!More than one instance of this executable are running now.
Explanation: An unexpected error occurred. System Action: Processing ends. User Response: Gather information from the trace file and log file and contact your IBM service representative. EEP0013I Explanation: System Action: None. User Response: EEP0014I Exiting v1 command with errors!!! EEP0019I ====>Starting ITSM FOR HARDWARE - DP FOR ESS executable on the PRODUCTION SYSTEM: v1 Received signal v1. Exiting...
Explanation: You have to wait until previous backup is done before you can run this backup. System Action: Processing ends. User Response: Wait until previous backup is done and try again.
Explanation: System Action: None. User Response: EEP0020I Explanation: System Action: None. User Response: ====>Performing DP FOR ESS v1 command.
Explanation: Specified command failed with a non zero return code. System Action: None. User Response: Please correct the problem indicated by the previous error message and retry the command. EEP0015E ERROR!!!An invalid command was entered.
Explanation: An unsupported command was entered. System Action: Processing ends.
Copyright IBM Corp. 1993, 2004
933
EEP0021I EEP0031W
EEP0021I Completed Successfully. EEP0026I User aborted v1 command.
Explanation: No error was detected. System Action: None. User Response: EEP0022I AIX Version: var1 Oslevel: var2.
Explanation: Specified command was aborted by user. System Action: None. User Response: None. EEP0027I Database instance name: v1
Explanation: Displays AIX version and oslevel. System Action: None. User Response: None. EEP0023I ESS CopyServices CLI Version: var1.var2.
Explanation: Name of the database instance. System Action: None. User Response: None. EEP0028I Number of ESS lun pairs to be flashcopied: v1
Explanation: Displays ESS CopyServices CLI version. System Action: None. User Response: None. EEP0024I Filesystem consistency check completed successfully.
Explanation: Number of ESS lun pairs to be flashcopied. System Action: None. User Response: None. EEP0029I Database name: v1
Explanation: Filesystem consistency check on the flashcopied filesystems was successful. System Action: None. User Response: None.
Explanation: Name of the database. System Action: None. User Response: None. EEP0030I Number of ESS Volumes to be Flashcopied: v1
EEP0025E
ERROR!!!Filesystem consistency check failed.
Explanation: Filesystem consistency check on the flashcopied filesystems failed. This means that there were some inode changes on the filesystem when executing DP for ESS flashcopy 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.
Explanation: Number of ESS volumes to be flashcopied. System Action: None. User Response: None. EEP0031W 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. System Action: None. User Response: There was a problem while we were
934
IBM Tivoli Storage Manager: Messages
EEP0032E EEP0062E
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. EEP0032E ERROR!!! This command is supported only with AIX 5.1 or higher. User Response: Please check the error log for details. EEP0059E ERROR!!!The database was backed up using NOCOPY type of flashcopy.The data in the target ESS volumes is not valid, and cannot be used to perform a flashcopy restore.
Explanation: User is running this command with earlier version than AIX 5.1. System Action: Process stops. User Response: Make sure your AIX version is higher or equal to AIX 5.1. EEP0033E ERROR!!! This command is supported only with ESS V2.3.0 or higher.
Explanation: In order to restore the database using flashcopy restore, the database needs to be backed up using COPY or INCR type of flashcopy. System Action: Processing stops. User Response: Please restore the database from TSM Server using DB2 restore command or Data Protection for Oracle. EEP0060E ERROR!!!Flashcopy type of v1 is invalid when backup destination is: v2.
Explanation: User is running this command with earlier version than ESS V2.3.0. System Action: Process stops. User Response: Make sure your ESS version is higher or equal to ESS V2.3.0. EEP0052I Starting database backup process.
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. System Action: Processing stops. User Response: Set the correct values for flashcopy type and backup destination in the setup file and retry the command. EEP0061I Since a Nocopy type of Flashcopy operation is taking place there is no background copy to be monitored.
Explanation: Database backup process started. System Action: None. User Response: EEP0054I Backup to TSM completed with return code : rc1.
Explanation: Database backup process completed. System Action: None. User Response: EEP0056I Received error v1 while disabling the new resources.
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. System Action: Processing stops. User Response: None. EEP0062E 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: An error occured when the process attempted to disable the resources obtained for performing the DB backup. System Action: None. User Response: Please check the error log for details. EEP0058I Received error v1 while resetting the target volumes.
Explanation: An error occured when the process attempted to withdraw the flashcopy relationship between the source and target volumes. System Action: None.
Explanation: The source / target information in the setup file cannot be modified. In order to backup 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. System Action: Processing stops User Response: The source / target information in the
Chapter 15. Data Protection for ESS for DB2 UDB
935
EEP0065E EEP0072E
setup file cannot be modified. In order to backup the database to different target LUNs, please use a different setup file. If you wish to restore the database to a new location, please use the DB2 restore command to restore it from TSM. EEP0065E ERROR!!!IBM2105 Copyservice CLI is not installed. System Action: An incremental flashcopy will be performed instead. 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 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: We couldnt find ibm2105cli.rte file installed. lslpp -lc ibm2105cli.rte command failed. System Action: Processing continues. User Response: Make sure Copyservice CLI is installed on your host machine. EEP0066W 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 AIX versions 5.1.0 or later. As this version of AIX is 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. EEP0070E ERROR!!!Some of the ESS volumes belonging to this database have Incremental Change Recording Enabled while others do not.
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. EEP0067W WARNING!!! Incremental change recording is enabled. Performing incremental flashcopy instead of COPY type of flashcopy.
Explanation: In order to perform an incremental flashcopy, all the ESS volumes belonging to the database must have change recording enabled. System Action: Processing stops. User Response: Please withdraw the flashcopy relationships for those ESS volumes that have incremental change recording enabled, using the DP for ESS 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. EEP0071I Source volume: v1 Target volume: v2 Pending Sectors: v3
Explanation: Incremental change recording is enabled. Performing a copy type of flashcopy will fail in this case. System Action: An incremental flashcopy will be performed instead. 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. EEP0068W WARNING!!!Incremental change recording is enabled. Performing incremental flashcopy instead of NOCOPY type of flashcopy.
Explanation: Displays the number of sectors yet to be 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. System Action: None. User Response: None. EEP0072E ERROR!!!DP FOR ESS does not support flashcopy backup of DB2 UDB databases with multiple logical and/or physical partitions.
Explanation: Incremental change recording is enabled. Performing a nocopy type of flashcopy will fail in this case.
Explanation: DP FOR ESS only supports flashcopy backup of DB2 UDB databases having a single physical
936
IBM Tivoli Storage Manager: Messages
EEP0073E EEP0124I
partition and a single logical partition only. System Action: Processing stops. User Response: None. EEP0073E ERROR!!!DB2 UDB Server has not been installed. EEP0115E ERROR!!!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. System Action: Processing ends. User Response: Make sure you dont have control files and redo log files in the same volume group with Oracle datafiles. EEP0120E ERROR!!!A null logical volume has been detected.
Explanation: DB2 UDB Server has not been installed. System Action: Processing stops. User Response: Please install DB2 UDB Server and set up your database on Enterprise Storage Server, before invoking DP FOR ESS. EEP0074I DB2 UDB Server Version: v1.
Explanation: A null logical volume was detected. System Action: Processing ends. User Response: Verify the target database information is specified correctly in the Setup File. EEP0121E Explanation: System Action: Processing ends. User Response: EEP0122E ERROR!!!An error is detected in volume group : vg1. ERROR!!!A null volume group has been detected.
Explanation: Displays the DB2 UDB Server Version. System Action: None. User Response: None. EEP0075W 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. System Action: None. User Response: None. EEP0076E ERROR!!!Current ESS CLI Version does not support the function that you are trying to run.
Explanation: An error was returned from specified volume group. System Action: Processing ends. User Response: Verify the target database information 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. EEP0123E Explanation: System Action: Processing ends. User Response: EEP0124I Mounting filesystem : fs1. 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. System Action: Processing Ends. User Response: Please install ESS CLI V230 or higher. EEP0110I 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 User Response: None
Explanation: Currently attempting to mount the file system. System Action: None. User Response:
Chapter 15. Data Protection for ESS for DB2 UDB
937
EEP0125E EEP0136E
EEP0125E Explanation: System Action: Processing ends. User Response: EEP0126I Trying to find new devices to match the source device. This process will take some time....... ERROR!!!Serial number for the device v1 is not found. EEP0132W WARNING!!!The umount command failed with rc rc1 for mount point mntpt1.
Explanation: An error occurred while trying to remove a mount point. Processing continues. System Action: Processing continues. User Response: EEP0133E ERROR!!!Failed to open a logical volume device with errno errno for logical volume: lv.
Explanation: Currently trying to find a target device to match with the source device. System Action: None. User Response: EEP0127I Explanation: System Action: None. User Response: EEP0128E ERROR!!!Configuring the target volume would cause duplicate physical volume ID : pvid1. Removing device : parm1
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. System Action: Processing continues. User Response: Please contact AIX support to find out why the opening of a logical volume device failed. EEP0134E ERROR!!!Failed to suspend I/O on a logical volume device with errno errno for logical volume: lv.
Explanation: A different set of target volumes that were previously associated with the same source volumes was detected. System Action: Processing ends. 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 EEP0129E Explanation: System Action: Processing ends. User Response: EEP0130W WARNING!!!Removing the mount point directory mntpt1 failed with rc: rc1. ERROR!!!Removing device parm1 failed.
Explanation: An error occurred while trying to 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. System Action: Processing continues. User Response: Please contact AIX support to find out why the suspend I/O on a logical volume device failed. EEP0135E 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. 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. EEP0136E ERROR!!!Volume group removing failed with rc rc1 for volume group vg1.
Explanation: An error occurred while trying to remove a mount point. Processing continues. System Action: Processing continues. User Response:
Explanation: An error occurred while performing the exportvg command. System Action: Processing ends.
938
IBM Tivoli Storage Manager: Messages
EEP0138I EEP0150E
User Response: Verify that the volume group is not corrupt. Run the exportvg command with the volume group name from the command line. EEP0138I Flashcopy type is set to NOCOPY. Removing disk meta data for all target disks... This backup is NOT valid for a flashcopy restore. Please restore from TSM Server. EEP0144E ERROR!!!A logical volume v1 is not defined in volume group v2.
Explanation: The physical disk that database allocated is not found. System Action: Processing ends. User Response: If the problem persists, please collect the trace data and log file and present to IBM service representative. EEP0146E ERROR!!!An physicall disk for the volume group:v1 is not found.
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 flashcopy restore. You can only restore from TSM Server. System Action: None. User Response: None. EEP0140I Flashcopy type is set to COPY or INCR. Leaving disk meta data intact for all target disks... This backup is valid for a flashcopy restore.
Explanation: The physical disk that database allocated is not found. System Action: Processing ends. User Response: If the problem persists, please collect the trace data and log file and present to IBM service representative. EEP0147I Explanation: System Action: None. User Response: EEP0148I Importing volume groups now... Exporting volume group fnm1 failed.
Explanation: The target PVIDs are not cleared.This process leaves disk metadata intact for all target disks. This backup can be used for a flashcopy restore. System Action: None. User Response: None. EEP0141E ERROR!!!Unsupported volume v1 has been detected.
Explanation: Processing an importing volume group command. System Action: None. User Response: EEP0149I Explanation: System Action: None. User Response: EEP0150E ERROR!!!Logical Volume can not be found for the file fnm1. Newly imported volume group: vg1
Explanation: The volume that database has benn allocated is an unsupported type. System Action: Processing ends. User Response: EEP0142E ERROR!!!Unsupported file system has been detected.
Explanation: The file system that database allocated is an unsupported type. System Action: Processing ends. User Response: Make sure that the mount point exists and the file system is supported. EEP0143E ERROR!!!Unsupported volume group v1 has been detected.
Explanation: The resources reside in an unsupported volume. System Action: Processing ends. 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.
Explanation: The volume group that database has been allocated is an unsupported type. System Action: Processing ends. User Response: Make sure that volume group is not rootvg.
Chapter 15. Data Protection for ESS for DB2 UDB
939
EEP0151E EEP0172E
EEP0151E Explanation: System Action: None. User Response: EEP0162E EEP0152I Removing volume group fnm1 .... Explanation: System Action: Processing ends. User Response: EEP0164E EEP0153I Explanation: System Action: None. User Response: EEP0166E EEP0154I Explanation: System Action: None. User Response: EEP0156I Explanation: System Action: None. User Response: EEP0158I Explanation: System Action: None. User Response: EEP0160I <fn1> VOLUME GROUP : fn2 COPIES : fn3 SCHED POLICY : fn4 STALE PPs : fn5 MIRROR WRITE CONSISTENCY: fn6 LogDev=fn1 Serial Number=fn2 EEP0170W Explanation: System Action: None. User Response: EEP0172E Explanation: System Action: Processing ends. User Response: ERROR!!!Logical volume vg1 must have the mirror write consistency on. WARNING!!!Logical volume vg1 has vg2 stale partitions. Explanation: System Action: Processing ends. User Response: Finding the serial numbers ... <fnm1><fnm2><fnm3><fnm4><fnm5> Explanation: System Action: Processing ends. User Response: EEP0168E ERROR!!!Logical volume vg1 must have the parallel scheduling policy. ERROR!!!Logical volume vg1 must have at least 2 copies. Varied off and exported volume group : fnm1 Explanation: System Action: Processing ends. User Response: ERROR!!!Quorum of the volume group vg1 must be off. Explanation: Attempting to remove the volume groups. System Action: None. User Response: ERROR!!!Volume group vg1 can not be found. ERROR!!!Varying off volume group fnm1 failed. EEP0161E Explanation: System Action: Processing ends. User Response: ERROR!!!No volume group was found.
Explanation: System Action: None. User Response:
940
IBM Tivoli Storage Manager: Messages
EEP0174E EEP0275I
EEP0174E ERROR!!!None of the mirror copies of vg1 was completed on the specified ESS vg2. EEP0188E Explanation: System Action: None. User Response: EEP0190E Explanation: System Action: None. User Response: EEP0191I Explanation: System Action: None. User Response: EEP0270E ERROR!!!Invalid option found in the Setup File. Varying on volume group fnm1 failed. ERROR!!!The number of new volume groups is limited parm1. ERROR!!!lvm queryvg failed.
Explanation: System Action: Processing ends. User Response: EEP0176E Explanation: System Action: Processing ends. User Response: EEP0178I Could not determine the number of paths to target volumes. Using default value of 1. ERROR!!!Some of the partitions of vg1 are stale on the specified ESS vg2.
Explanation: System Action: None. User Response: EEP0180E ERROR!!!Failure in changing the mount point vg1, return code vg2 from command chfs.
Explanation: The parameter value is invalid. System Action: Processing ends. User Response: Correct the value and restart the processing. EEP0272I Flushing the buffers to disk...
Explanation: System Action: None. User Response: EEP0182E ERROR!!!The same hdisk vg1 can not be associated with two different vpaths (serial numbers vg2 and vg3). command chfs.
Explanation: Currently synchronizing to force the buffers to disk. System Action: None. User Response: EEP0273I Unmounting the file system mntpt1...
Explanation: System Action: None. User Response: EEP0184E Explanation: System Action: None. User Response: EEP0186I Explanation: System Action: None. User Response: Recreating the new volume groups.... ERROR!!!lsvg command failed.
Explanation: Currently attempting to unmount the file system from the mount point. System Action: None. User Response: EEP0274I Explanation: System Action: User Response: EEP0275I There are too many file systems. Bringing up the volume groups...
Explanation: The number of file systems exceeds compiled limit. System Action: None.
Chapter 15. Data Protection for ESS for DB2 UDB
941
EEP0280E EEP0292W
User Response: EEP0280E 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. System Action: None. User Response: None. EEP0290E 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. System Action: Processing ends. User Response: Please restore the database from TSM Server using DB2 restore command. EEP0282I 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 FlashCopy restore. If you continue, you will lose newly added logical volumes. Do you want to continue? Please enter Yes or No.
Explanation: The specified physical volume was found during the FlashCopy backup as part of the database volumes on the production system. Now, on the FlashBack restore, it could not be found anymore on the production system. System Action: Processing ends. User Response: Logon with the user root and issue the command lsvpcfg. Check if the volume is displayed. Use the ESS web 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 ESS volumes. EEP0291E ERROR!!!The source volume with serial number cmd belongs to another volume group.
Explanation: System Action: Processing ends. User Response: EEP0284I Could not query the operating system to obtain the list of file systems for the volume groups containing the database.
Explanation: The specified physical volume was found during the FlashCopy backup as part of the database volumes on the production system. Now, on the FlashBack restore, DP for ESS found it as member of another volume group and can not proceed with the restore. System Action: Processing ends. 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 ESS volumes. EEP0292W WARNING!!!The logical volume lv on the mount point mp was renamed or newly added.
Explanation: System Action: Processing ends. User Response: EEP0286I Could not query the operating system to obtain the list of disks for the volume groups containing the database.
Explanation: System Action: Processing ends. User Response: EEP0287W 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: 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. System Action: None. 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.
Explanation: database_control_file_restore is set to yes in the setup file. You will need to do the incomplete recovery after the restore.
942
IBM Tivoli Storage Manager: Messages
EEP0293I EEP0302E
EEP0293I List of the current file systems on the backed up volume groups ... EEP0299I The following commands should be run after the flashcopy process in background is finished to synchronize the LVM copies:
Explanation: Prior the start of the FlashBack restore, DP for ESS will display a list of all the file systems which are currently on production database system. System Action: Processing ends. User Response: None. EEP0294I List of file systems which will be restored...
Explanation: DP for ESS will not automatically synchronize the copies after the reconstruction of the LVM mirror. A basic command will be created and put out. System Action: Processing ends. User Response: You have to start the synchronization of the LVM mirror manually after the flashcopy process in background has finished. If necessary you have to add additional parameter to the commands to improve the performance of the synchronization. EEP0300E ERROR!!!Error converting the ESS hdisk device volume group vg to a Subsystem Device Driver vpath device volume group.
Explanation: Prior the start of the FlashBack restore, DP for ESS will display a list of all the file systems which were on production database system at the time of the FlashCopy backup. System Action: Processing ends. User Response: None. EEP0297W WARNING!!!The newly added volume cmd will be reduced from the database volume group rc.
Explanation: The reducevg command removes physical volumes from a volume group. DP for ESS is calling it here on FlashBack restore to remove the physical volumes added to the database volume groups after the FlashCopy backup. System Action: Processing ends. User Response: None. EEP0298I 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: On the function FlashCopy backup, DP 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 on the backup system. System Action: Processing ends. User Response: Check the return code and the error message of the hd2vp command. Consult the AIX system documentation. EEP0301W WARNING!!!The rmlv command lv ended with return code rc.
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. System Action: None. 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.
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. System Action: Processing ends. User Response: Check the return code and the error 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 ESS volumes. EEP0302E ERROR!!!DP for ESS encountered a problem when using the FlashCopy 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.
Chapter 15. Data Protection for ESS for DB2 UDB
943
EEP0303W EEP0310I
System Action: Processing ends. 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 possible causes of the problem. EEP0303W WARNING!!!The file system fs has already an entry in the /etc/filesystems. 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. System Action: Processing ends. User Response: Check the return code and the error 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 ESS volumes. EEP0307I Removing copies from the logical volumes ...
Explanation: DP for ESS found on the backup system after the flashcopy that the specified file system still exist in the /etc/filesystems. System Action: Processing ends. 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. EEP0304W WARNING!!!The reducevg command cmd ended with return code rc.
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. System Action: Processing ends. User Response: None. EEP0308I Removing physical volumes from the volume groups ...
Explanation: The reducevg command removes physical volumes from a volume group. DP for ESS 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 ESS 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 ESS that is not yet involved in the FlashCopy. System Action: Processing ends. User Response: Check the return code and the error message of the reducevg command. Consult the AIX system documentation. EEP0305W WARNING!!!The extendvg command cmd ended with return code rc.
Explanation: On the function FlashBack restore, after the rmlvcopy and prior to the exportvg and the actually flashcopy reverse, DP for ESS will use the command reducevg to remove the physical volumes residing on the second ESS. System Action: Processing ends. User Response: None. EEP0309I Adding physical volumes to the volume groups ...
Explanation: The extendvg command adds physical volumes to a volume group. DP for ESS will call it to add the volumes which are residing on the ESS that is not yet involved in the FlashBack to the database volume groups. System Action: Processing ends. User Response: Check the return code and the error message of the extendvg command. Consult the AIX system documentation. EEP0306W WARNING!!!The mklvcopy command cmd ended with return code rc.
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. System Action: Processing ends. User Response: None. EEP0310I Adding copies to the logical volumes ...
Explanation: On the function FlashBack restore, DP for ESS will use the command mklvcopy to add the copies of the logical volumes on the second ESS. This will take effect after the importvg and the extendvg. System Action: Processing ends. User Response: None.
Explanation: DP for ESS will call the command mklvcopy to add a copy of a logical volume on the physical volumes residing on the second ESS. This call
944
IBM Tivoli Storage Manager: Messages
EEP0311W EEP0351E
EEP0311W WARNING!!!The command cmd ended with return code rc. EEP0315I Could not mount all the filesystems originally present.
Explanation: The execution of the system command ended with the displayed return code. System Action: Processing ends. User Response: Check the return code and the error message of the specified command. Consult the AIX system documentation. EEP0312E ERROR!!!Importing the volume group from hdisk logdev failed.
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 the recovery, if this file system was already used from the production database. EEP0316W WARNING!!!The database volume groups do not contain currently any file system.
Explanation: DP for ESS 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. System Action: Processing ends. User Response: Check the return code and the error message of the importvg command. Consult the AIX system documentation. EEP0313E ERROR!!!Recreating the volume group from the hdisks hdisks failed.
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: User Response: None. EEP0317W WARNING!!!One or more errors were found disabling the production system resources. Though, the FlashBack restore will continue.
Explanation: DP for ESS will use the command recreatevg on the function FlashCopy backup if the production database is residing on an high-available LVM mirror environment. This command will be issued on the backup system 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 ESS where the flashcopy was issued. System Action: Processing ends. User Response: Check the return code and the error message of the recreatevg command. Consult the AIX system documentation. EEP0314W WARNING!!!Removing the logical device logdev whith the same PVID pvid in the ODM.
Explanation: This message will appear if running the function FlashBack restore, some error occurs unmounting the existing file systems and removing the volume groups. Though, DP for ESS will continue with the FlashBack restore. System Action: User Response: None. EEP0350E ERROR!!!Error while getting the size of the volume: src1 size.
Explanation: The ESS query command cannot determine the size of the volume. System Action: Processing ends. 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. EEP0351E ERROR!!!The size of source volume: src1 size1 and target volume: tgt1 size2 are different.
Explanation: There is still another logical device (hdisk or vpath) in the state defined with the same PVID as one of the source volumes. System Action: Processing continues. User Response: None.
Explanation: The size of the source volume and target volume are different. The source volume and target
Chapter 15. Data Protection for ESS for DB2 UDB
945
EEP0352E EEP0359I
volume must be the same size and reside in the same Logical Subsytem (LSS). System Action: Processing ends. 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. EEP0352E ERROR!!!Incorrect value size is specified for thetarget volume: tgt1 in the Setup File. target volumes. If the command line interface package and Copy Services microcode are not in sync, check with the Enterprise Storage Server administrator to obtain the appropriate level of Copy Services command line interface and microcode. EEP0356E ERROR!!!Cannot find a target volume to match with the source volume parm1.
Explanation: A target volume could not be found. System Action: Processing ends. 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. primary_copyservices_servername 5. shark_username 6. shark_password EEP0357I Performing flashcopy withdraw of source ESS volume src1 from target ESS volume tgt1
Explanation: The shark_target_volume parameter in the Setup File specifies an incorrect size for the target volume. System Action: Processing ends. 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. EEP0353E ERROR!!!Unable to open file file1.
Explanation: An error was detected when trying to open the file. The file may not exist. System Action: Processing ends. User Response: Make sure the file exists.
Explanation: A flashcopy withdraw of the source volume from the target volume was requested. System Action: None. User Response: EEP0358E ERROR!!!No target volume is available. Terminating......
EEP0354I
Performing fctype flashcopy of: Source ESS volume: src1 to Target ESS volume: tgt1
Explanation: No target volume was found. System Action: Processing ends. 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. primary_copyservices_servername 5. shark_username 6. shark_password EEP0359I Incremental Change Recording: val1
Explanation: A flashcopy from the source volume to the target volume was requested. System Action: None. User Response: EEP0355E 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. System Action: Processing ends. 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
Explanation: Value of Incremental change recording. System Action: None. User Response:
946
IBM Tivoli Storage Manager: Messages
EEP0360I EEP0370E
EEP0360I Querying the ESS for volume size ...Volume: volser1 volsize EEP0366I Flashcopy was performed with parm1 option.
Explanation: A query of the target volume was requested. System Action: None. User Response: EEP0361I A NOCOPY Flashcopy was performed. Withdrawing the nocopy flashcopy relationship...
Explanation: This is the type of flashcopy that was actually performed. It may be different from the value specified by the user as DP for ESS overrides this value under certain conditions. System Action: None. User Response: None. EEP0367I 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: The flashcopy relationship between the source and target volumes terminates after the NOCOPY Flashcopy is performed. System Action: None. User Response: EEP0362I Checking the status of the primary Copy Services Server:serv1
Explanation: Whenever user performs an incremental flashcopy restore operation, the source and target ESS volumes will be reversed. System Action: None. User Response: None. EEP0368I The backup Copy Services server is ready...
Explanation: Currently verifying the primary Copy Services server status. System Action: None. User Response: EEP0363I Primary Copy Services server is ready.
Explanation: The backup Copy Services server is ready. System Action: None. User Response: EEP0369E ERROR!!!Both the primary Copy Services server and the backup Copy Services server are not available...
Explanation: The primary Copy Services server is ready. System Action: None. User Response: EEP0364I The connection to the primary Copy Services server failed. The process continues to check the backup Copy Services server.
Explanation: The primary Copy Services server and the backup Copy Services server are not available. System Action: Processing ends. 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. EEP0370E ERROR!!!A Copy Services backup server has not been specified. Exiting...
Explanation: The primary Copy Services server is not available. Verify that the TCP/IP connection is valid. System Action: None. User Response: EEP0365I Checking the status of the backup Copy Services Server:serv1
Explanation: Currently verifying the backup Copy Services server status. System Action: None. User Response:
Explanation: The backup Copy Services server is not specified in the Setup File. System Action: Processing ends. 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.
Chapter 15. Data Protection for ESS for DB2 UDB
947
EEP0371I EEP0381I
EEP0371I Value of Flashcopy type is: parm1. Backup. This is necessary to ensure that a complete image of the database is available to the restore process. System Action: Processing ends. User Response: Ensure that the target volumes specified in the setup file are accurate. EEP0377I Background copy is in progress....Sleeping for v1 minutes....
Explanation: None. System Action: None. User Response: None. EEP0372I 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. System Action: None. User Response: EEP0373E ERROR!!!A required parameter tgtv1 is missing in the Setup File.
Explanation: Blocking for SHARK_QUERY_INTERVAL period prior to querying if the background copy operation has completed. System Action: None. User Response: None. EEP0378I Background copy is complete.
Explanation: A required parameter in the Setup File has not been specified. This may be caused by incorrect syntax in the Setup File. System Action: Processing ends. 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(:). EEP0374I Querying ESS for status of volume: volser1
Explanation: Background copy for flashcopy backup or restore is complete. System Action: None. User Response: None. EEP0379E ERROR!!!An invalid value: parm1 has been specified for backup destination.
Explanation: Backup destination can only be TSMONLY, DISKONLY or DISKANDTSM. System Action: Processing stops. User Response: Please specify TSMONLY, DISKONLY or DISKANDTSM for the option backup destination and retry the command. EEP0380E ERROR!!!An invalid value: parm1 has been specified for flashcopy type.
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. System Action: None. User Response: None. EEP0375E ERROR!!!ESS volumes are involved in a flashcopy or a PPRC operation.
Explanation: Flashcopy type can only be NOCOPY, COPY or INCR. System Action: Processing stops. User Response: Please specify NOCOPY, COPY or INCR for the option flashcopy type and retry the command. EEP0381I Querying ESS for pending sectors for volume: volser1
Explanation: ESS source or target volumes are involved in a flashcopy or a PPRC operation. Flashcopy backup or restore command will not be performed. System Action: Processing ends. 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. EEP0376E ERROR!!!ESS target volume v1 involved in the previous backup does not exist in the setup file.
Explanation: A query of all the source and target volumes was requested to ensure that background copy is not in progress between them. System Action: None. User Response: None.
Explanation: The list of target volumes specified in the setup file for restoring a specified database using Flashcopy Restore need to be the same as those specified in the setup file at the time of Flashcopy
948
IBM Tivoli Storage Manager: Messages
EEP0400E EEP0503E
EEP0400E ERROR!!!Error on running command: parm1 User Response: Please enter Yes to continue, or No to abort the restore operation. EEP0412I 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: An error was detected while running a system command. System Action: Processing ends. User Response: Gather log file information and contact your IBM service representative. EEP0402I Explanation: System Action: None. User Response: EEP0404I Explanation: System Action: None. User Response: EEP0406I User abort; Exiting Flashcopy Restore. Error: parm1 parm1
Explanation: Flashcopy Restore overwrites any existing data on all the source LUNs, including (but not 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: EEP0500E 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. System Action: Processing ends. 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. EEP0502E ERROR!!!Invalid license is detected.
Explanation: The user has chosen to terminate the Flashcopy Restore operation. 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. EEP0408I User input was yes; Continuing Flashcopy Restore.
Explanation: An invalid license was found. System Action: Processing ends. User Response: Check if there is a mismatch between the executables (for the production system and backup system) and the license file(agent.lic). EEP0503E ERROR!!!An error has been detected when calling TSM API setup.
Explanation: The user has chosen to continue the Flashcopy Restore operation. System Action: Restore processsing continues. User Response: EEP0410I 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: An error was detected when calling TSM API setup. System Action: Processing ends. 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.
Explanation: 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. System Action: System waits for a valid user response.
Chapter 15. Data Protection for ESS for DB2 UDB
949
EEP0504E EEP0637E
EEP0504E ERROR!!!An error has been detected when calling TSM API init. EEP0633E ERROR!!!A data for required parameter tgtv1 is missing in the Setup File.
Explanation: An error was detected when calling TSM API init. System Action: Processing ends. 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. EEP0505E ERROR!!!An error has been detected when calling TSM API terminate.
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. System Action: Processing ends. 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(:). EEP0634E ERROR!!!An incorrect incremental backup level found.
Explanation: An error was detected when calling TSM API terminate. System Action: Processing ends. 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. EEP0506E ERROR!!!An error has been detected when running the TSM Backup Archive Client command line interface.
Explanation: An incorrect incremental backup level was specified. System Action: Processing ends. User Response: The incremental backup level must be a decimal number greater than or equal to 1. EEP0635E ERROR!!!Temporary file cannot be opened for writing.
Explanation: An error was detected when running the TSM Backup Archive Client Client command line interface. System Action: Processing ends. User Response: Make sure the TSM Backup Archive Client is correctly installed and that the environmental variables are set correctly. EEP0630E ERROR!!!A memory allocation error has occurred.
Explanation: Temporary file cannot be opened for writing. System Action: Processing ends. User Response: Make sure you have enough space to create one file and have permission to create a file in that directory. EEP0636E ERROR!!!The metadata file cannot be created.
Explanation: The application could not create a temporary file in the root filesystem. System Action: Processing ends. User Response: Make sure you have enough space in the root file system, and have permission to create a file in that file system. EEP0637E ERROR!!!A temporary directory could not be created.
Explanation: Enough memory was not available to continue processing. System Action: Processing ends. User Response: Ensure that your system has sufficient real and virtual memory. Close unnecessary applications. EEP0632E ERROR!!!A duplicate target volume serial number tvol1 was found in the Setup File.
Explanation: The application could not create a temporary directory in the root filesystem. System Action: Processing ends. User Response: Make sure you have enough space in the root file system, and have permission to create a directory in that file system.
Explanation: A duplicate target volume was specified in the Setup File. System Action: Processing ends. User Response: Correct the duplicate volume serial number in the Setup File and remove the duplicate occurrences.
950
IBM Tivoli Storage Manager: Messages
EEP0638E EEP5011E
EEP0638E ERROR!!!Background copy operation for a flashcopy backup or restoreis not complete. EEP0643E 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 5.2.1. or later.
Explanation: The background copy operation for a flashcopy backup or restore command has not completed. System Action: Processing ends. User Response: Invoke essdb2p monitor command to ensure that the background copy operation is complete before issuing a flashcopy restore or backup command. EEP0639W WARNING!!!Could not copy setup file v1 to directory v2. Explanation:
System Action: None. User Response: EEP0644E ERROR!!!Database instance name has not been specified in the user setup file. Please specify the instance name and retry the operation.
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. System Action: Processing continues. User Response: None.
Explanation: Please specify the database instance name in the user setup file and retry the operation. System Action: None. User Response: Please specify the database instance name in the user setup file and retry the operation. EEP0645E ERROR!!!Database name has not been specified in the user setup file. Please specify the database name and retry the operation.
EEP0640E
ERROR!!!Could not open trace file v1.
Explanation: There were some problems opening tracefile. Please make sure you can open the trace file which was specified in the setup file. System Action: Processing terminates. User Response: None. EEP0641E ERROR!!!Could not create the trace object.
Explanation: Please specify the database name in the user setup file and retry the operation. System Action: None. User Response: Please specify the database name in the user setup file and retry the operation. EEP4000E ERROR!!!program-name: cannot open file file-spec: error.
Explanation: There were some problems creating trace class object. System Action: Processing terminates. User Response: None. EEP0642E ERROR!!!Invalid trace flag: v1.
Explanation: TSM cannot open the file. System Action: TSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system adminis trator. EEP5010I Explanation: System Action: None. User Response: EEP5011E ERROR!!!The DB2INIDB command failed on database: udbDBname. Issued db2inidb as standby.
Explanation: Some invalid trace flags are defined in the setup file. System Action: Processing terminates. User Response: None.
Explanation: The specified database can not split mirror as a standby database. The database may be in an exception state. Please verify the database from the
Chapter 15. Data Protection for ESS for DB2 UDB
951
EEP5012E EEP5023I
production system when it was mirrored. System Action: Processing ends. User Response: Ensure the database is in a normal state. Verify the error message from the trace file. Correct any error that may exist. Start the process again. EEP5012E ERROR!!!The BACKUP database:udbDBname command failed. information from the trace file and the configuration file and contact your technical service representative. EEP5017I Explanation: System Action: None. User Response: EEP5018I Explanation: System Action: None. User Response: EEP5019I Explanation: System Action: None. User Response: EEP5013I Explanation: System Action: None. User Response: EEP5014I Cleaning up the database name:udbDBname from the database system directory. The database:udbDBname backed up successfully. EEP5020I Explanation: System Action: None. User Response: EEP5021I Explanation: System Action: None. User Response: EEP5022W Explanation: System Action: None. User Response: EEP5023I EEP5016E ERROR!!!The database system directory may be empty. Explanation: System Action: None. User Response: Verify the authority of user:nmusr in group:nmgrp WARNING!!!No database log path defined for udbDBaname found. Verify the log path:udbLogpath for database:udbDBaname. Obtain the log path for the database. Complete the system directory scan. Get the next entry from the system directory. Scan the database system directory.
Explanation: The BACKUP command cannot be performed on the database. The detail error code and reason code is kept in the trace file. Backup processing terminates. System Action: Processing ends. User Response: Determine the error message from SQLCODE and SQLSTATE in the trace file. Correct any error that may exist. Issue the BACKUP command again. If the problem persists, gather information from the trace file and the configuration file and contact your technical service representative.
Explanation: System Action: None. User Response: EEP5015I Cleaning up the database alias name:udbDBname from the database system directory.
Explanation: System Action: None. User Response:
Explanation: An error was detected when scanning the database system directory. The database system directory may be empty. System Action: Processing ends. User Response: Determine the error message from SQLCA in the trace file. If the problem persists, gather
952
IBM Tivoli Storage Manager: Messages
EEP5024E EEP5040I
EEP5024E ERROR!!!Must run as a root user or a user ID with system group authority. EEP5032I Explanation: System Action: None. User Response: EEP5033E ERROR!!!Failed to set up database:udbDBname as udbDBaname on udbDBmntpt Set up database:udbDBname as udbDBaname on udbDBmntpt
Explanation: TDP must run as a root user or a user ID with system group authority. System Action: Processing ends. User Response: Log on as a root user or with a user ID that has system group authority. EEP5025E ERROR!!!Invalid database instance ID:ndbSID in the Group:udbGroup.
Explanation: System Action: Processing ends. User Response: EEP5034I Explanation: System Action: None. User Response: EEP5035E Explanation: System Action: Processing ends. User Response: EEP5036I Explanation: System Action: None. User Response: EEP5037E ERROR!!!Database Manager has not been started. Verify the database sfile is in recoverable mode. ERROR!!!A required parameter is missing in the setup file. STOP Database Manager.
Explanation: Verify the owner and the group for all of the database files. System Action: Processing ends. User Response: EEP5026I Explanation: System Action: None. User Response: EEP5028I Explanation: System Action: None. User Response: EEP5029I Explanation: System Action: None. User Response: EEP5030I Explanation: System Action: None. User Response: EEP5031I Explanation: System Action: None. User Response: Start Database Manager. Recycling database alias:udbDBname. Recycling database:udbDBname. Checking raw tablespace (j) rawTsps Checking tablespace mountpoints (ndbSID): mntpt
Explanation: Please start the database manager and retry the operation. System Action: Processing ends. User Response: Please start the database manager and retry the operation. EEP5040I Explanation: System Action: None. User Response: The database: udbDBname logging activities are suspended.
Chapter 15. Data Protection for ESS for DB2 UDB
953
EEP5041I EEP5056E
EEP5041I Explanation: System Action: None. User Response: EEP5042I Explanation: System Action: None. User Response: EEP5043I Explanation: System Action: None. User Response: EEP5049E EEP5044E ERROR!!!The tablespace: dataname is in an exception state. Explanation: System Action: Processing ends. User Response: EEP5050E Explanation: System Action: Processing ends. User Response: EEP5052I Explanation: System Action: None. User Response: EEP5054I EEP5046E ERROR!!!Failed connecting to the database:udbDBname with UID:udbSID. Explanation: System Action: Processing continues. User Response: EEP5056E ERROR!!!Error while setting the ownership of the DB filesystems and / or raw volumes to uid: v1, gid: rc1. Forcing all users off from the database. Start Database Manager was successful. ERROR!!!Error while starting the database manager for udbSID ERROR!!!Error on updating database configuration. Tablespace Container: tspname ok Connecting to the database: udbDBname ... The database: udbDBname logging activities are resumed. EEP5047E ERROR!!!Disconnecting from the database:udbDBname with UID:udbSID failed.
Explanation: An attempt to disconnect to the database failed. System Action: Processing ends. User Response: Determine the error message from SQLCA in the trace file. Run the operation again. If the problem persists, gather information from the trace file and the configuration file and contact your technical service representative. EEP5048I Explanation: System Action: None. User Response: Disconnecting from the database: udbDBname ...
Explanation: An exception state was detected for the tablespace. System Action: Processing ends. User Response: Correct the exception state of the tablespace. Start the process again. If the problem persists, gather information from the trace file and the configuration file and contact your technical service representative. EEP5045E ERROR!!!An unsupported tablespace: tspname found.
Explanation: System Managed Tablespace (SMS) is not supported. System Action: Processing ends. User Response: Create the tablespace again with Database Managed Tablespace (DMS).
Explanation: An attempt to connect to the database failed. System Action: Processing ends. User Response: Determine the error message from SQLCA in the trace file. Run the operation again. If the problem persists, gather information from the trace file and the configuration file and contact your technical service representative.
Explanation: System Action: Processing ends. User Response:
954
IBM Tivoli Storage Manager: Messages
EEP5058I EEP7383E
EEP5058I Failed to save the database control file. User Response: EEP7152I Performance stats: seconds seconds spent in apicall API calls
Explanation: An error occured when the process attempted to save the database control file. System Action: None. User Response: Please check the error log for details. EEP5062I No database found in the system directory with the name v2. Found a database alias with that name with db name v1. Please modify the setup file to indicate the correct database name for the option target_database_name:.
Explanation: The indicated number of seconds were spent making API calls for the indicated system. System Action: Processing continues. User Response: None EEP7366E ERROR!!!Unable to close trace output file file-name.
Explanation: The database alias name was probably specified in the setup file for the option target_database_name:, instead of the database name. System Action: None. User Response: Please modify the setup to accurately specify the database name. EEP5064E ERROR!!!Database instance v1 is either specified incorrectlyor does not exist. Please specify a correct instance name in the user setup file or recreate the instance and retry the operation.
Explanation: An error occurred during the closing of a trace output file-name (for example, not enough disk space). System Action: Processing continues. User Response: Check the options.doc file for a description of possible causes of the error, or see your system administrator. EEP7367E ERROR!!!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. EEP7368E ERROR!!!Invalid trace file name (name too long).
Explanation: Please specify a correct instance name in the user setup file or recreate the instance and retry the operation. System Action: Processing ends. User Response: Please specify a correct instance name in the user setup file or recreate the instance and retry the operation. EEP5068E ERROR!!!The database was backed up using CLEAR_TARGET_PVID: YES. A FLASHCOPY Restore operation is not supported with CLEAR_TARGET_PVID set to YES during backup. In order to be able to restore the database using FLASHCOPY Restore, it has to be backed up with CLEAR_TARGET_PVID: NO.
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. EEP7383E ERROR!!!Specifying the trace file link as a symbolic link is not allowed.
Explanation: System Action: None. User Response: EEP5070I Database restore completed successfully. The database is ready for application of logs.
Explanation: Trace file linkname cannot be a symbolic link. System Action: The symbolic link linkname is deleted, the trace file is recreated, and processing stops. User Response: Specify the trace file location with the tracefile option.
Explanation: System Action: None.
Chapter 15. Data Protection for ESS for DB2 UDB
955
EEP7384E EEP7826E
EEP7384E ERROR!!!Symbolic link linkname to target was successfully deleted.
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. EEP7385E ERROR!!!Unable to delete symbolic link link.
Explanation: Log linkname cannot be a symbolic link. System Action: Processing stops. User Response: Delete the symbolic link linkname. EEP7823E ERROR!!!Invalid trace keyword keyword
Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect. System Action: Client program did not initialize or tracing was not enabled in the applet. User Response: Correct the value. See the entry for TRACEFLAGS in the Trace Facility Guide document for a list of valid trace flags. EEP7826E ERROR!!!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. System Action: Client program did not initialize. User Response: Change the TRACEFILE value so that it is a location to which you have write access.
956
IBM Tivoli Storage Manager: Messages
Chapter 16. Data Protection for Enterprise Storage Server for Oracle (EEO0000EEO9999)
This chapter describes the messages issued by Data Protection for Enterprise Storage Server for Oracle. The messages begin with the prefix EEO and are listed in numerical order.
EEO0010I v1 command completed successfully at: v2 User Response: Enter a supported command. See the Installation and Users Guide for information about supported commands. EEO0016I ====> Starting ITSM FOR HARDWARE - DP FOR ESS executable on the BACKUP SYSTEM: v1
Explanation: No error was detected. System Action: None. User Response: EEO0011E ERROR!!!Invalid number of arguments entered. Explanation: System Action: None. User Response: EEO0017E ERROR!!!You have to be root to run this program.
Explanation: Either incorrect arguments were entered or the specified file does not exist. System Action: Processing ends. User Response: Correct the arguments and start the process again. EEO0012E ERROR!!!Unexpected error occurred.
Explanation: You have to be root to run this product. System Action: Processing ends. User Response: Switch user id to root and try again. EEO0018E ERROR!!!More than one instance of this executable are running now.
Explanation: An unexpected error occurred. System Action: Processing ends. User Response: Gather information from the trace file and log file and contact your IBM service representative. EEO0013I Explanation: System Action: None. User Response: EEO0014I Exiting v1 command with errors!!! EEO0019I ====>Starting ITSM FOR HARDWARE - DP FOR ESS executable on the PRODUCTION SYSTEM: v1 Received signal v1. Exiting...
Explanation: You have to wait until previous backup is done before you can run this backup. System Action: Processing ends. User Response: Wait until previous backup is done and try again.
Explanation: System Action: None. User Response: EEO0020I Explanation: System Action: None. User Response: ====>Performing DP FOR ESS v1 command.
Explanation: Specified command failed with a non zero return code. System Action: None. 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. System Action: Processing ends.
Copyright IBM Corp. 1993, 2004
957
EEO0021I EEO0031W
EEO0021I Completed Successfully. EEO0026I User aborted v1 command.
Explanation: No error was detected. System Action: None. User Response: EEO0022I AIX Version: var1 Oslevel: var2.
Explanation: Specified command was aborted by user. System Action: None. User Response: None. EEO0027I Database instance name: v1
Explanation: Displays AIX version and oslevel. System Action: None. User Response: None. EEO0023I ESS CopyServices CLI Version: var1.var2.
Explanation: Name of the database instance. System Action: None. User Response: None. EEO0028I Number of ESS lun pairs to be flashcopied: v1
Explanation: Displays ESS CopyServices CLI version. System Action: None. User Response: None. EEO0024I Filesystem consistency check completed successfully.
Explanation: Number of ESS lun pairs to be flashcopied. System Action: None. User Response: None. EEO0029I Database name: v1
Explanation: Filesystem consistency check on the flashcopied filesystems was successful. System Action: None. User Response: None.
Explanation: Name of the database. System Action: None. User Response: None. EEO0030I Number of ESS Volumes to be Flashcopied: v1
EEO0025E
ERROR!!!Filesystem consistency check failed.
Explanation: Filesystem consistency check on the flashcopied filesystems failed. This means that there were some inode changes on the filesystem when executing DP for ESS flashcopy 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.
Explanation: Number of ESS volumes to be flashcopied. System Action: None. User Response: None. 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. System Action: None. User Response: There was a problem while we were
958
IBM Tivoli Storage Manager: Messages
EEO0032E EEO0062E
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 ERROR!!! This command is supported only with AIX 5.1 or higher. User Response: Please check the error log for details. EEO0059E ERROR!!!The database was backed up using NOCOPY type of flashcopy.The data in the target ESS volumes is not valid, and cannot be used to perform a flashcopy restore.
Explanation: User is running this command with earlier version than AIX 5.1. System Action: Process stops. User Response: Make sure your AIX version is higher or equal to AIX 5.1. EEO0033E ERROR!!! This command is supported only with ESS V2.3.0 or higher.
Explanation: In order to restore the database using flashcopy restore, the database needs to be backed up using COPY or INCR type of flashcopy. System Action: Processing stops. User Response: Please restore the database from TSM Server using DB2 restore command or Data Protection for Oracle. EEO0060E ERROR!!!Flashcopy type of v1 is invalid when backup destination is: v2.
Explanation: User is running this command with earlier version than ESS V2.3.0. System Action: Process stops. User Response: Make sure your ESS version is higher or equal to ESS V2.3.0. EEO0052I Starting database backup process.
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. System Action: Processing stops. User Response: Set the correct values for flashcopy type and backup destination in the setup file and retry the command. EEO0061I Since a Nocopy type of Flashcopy operation is taking place there is no background copy to be monitored.
Explanation: Database backup process started. System Action: None. User Response: EEO0054I Backup to TSM completed with return code : rc1.
Explanation: Database backup process completed. System Action: None. User Response: EEO0056I Received error v1 while disabling the new resources.
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. System Action: Processing stops. User Response: None. 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: An error occured when the process attempted to disable the resources obtained for performing the DB backup. System Action: None. 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 between the source and target volumes. System Action: None.
Explanation: The source / target information in the setup file cannot be modified. In order to backup 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. System Action: Processing stops User Response: The source / target information in the
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
959
EEO0065E EEO0072E
setup file cannot be modified. In order to backup the database to different target LUNs, please use a different 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!!!IBM2105 Copyservice CLI is not installed. System Action: An incremental flashcopy will be performed instead. 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 NOCOPY type of flashcopy. EEO0069W WARNING!!!Incremental flashcopy feature is not supported on this version of AIX: v1. A generic flashcopy will be performed instead.
Explanation: We couldnt find ibm2105cli.rte file installed. lslpp -lc ibm2105cli.rte command failed. System Action: Processing continues. 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 AIX versions 5.1.0 or later. As this version of AIX is 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 ESS volumes belonging to this database have Incremental Change Recording Enabled while others do not.
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: In order to perform an incremental flashcopy, all the ESS volumes belonging to the database must have change recording enabled. System Action: Processing stops. User Response: Please withdraw the flashcopy relationships for those ESS volumes that have incremental change recording enabled, using the DP for ESS 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. EEO0071I Source volume: v1 Target volume: v2 Pending Sectors: v3
Explanation: Incremental change recording is enabled. Performing a copy type of flashcopy will fail in this case. System Action: An incremental flashcopy will be performed instead. 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. EEO0068W WARNING!!!Incremental change recording is enabled. Performing incremental flashcopy instead of NOCOPY type of flashcopy.
Explanation: Displays the number of sectors yet to be 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. System Action: None. User Response: None. EEO0072E ERROR!!!DP FOR ESS does not support flashcopy backup of DB2 UDB databases with multiple logical and/or physical partitions.
Explanation: Incremental change recording is enabled. Performing a nocopy type of flashcopy will fail in this case.
Explanation: DP FOR ESS only supports flashcopy backup of DB2 UDB databases having a single physical
960
IBM Tivoli Storage Manager: Messages
EEO0073E EEO0124I
partition and a single logical partition only. System Action: Processing stops. User Response: None. EEO0073E ERROR!!!DB2 UDB Server has not been installed. EEO0115E ERROR!!!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. System Action: Processing ends. User Response: Make sure you dont have control files and redo log files in the same volume group with Oracle datafiles. EEO0120E ERROR!!!A null logical volume has been detected.
Explanation: DB2 UDB Server has not been installed. System Action: Processing stops. User Response: Please install DB2 UDB Server and set up your database on Enterprise Storage Server, before invoking DP FOR ESS. EEO0074I DB2 UDB Server Version: v1.
Explanation: A null logical volume was detected. System Action: Processing ends. User Response: Verify the target database information is specified correctly in the Setup File. EEO0121E Explanation: System Action: Processing ends. User Response: EEO0122E ERROR!!!An error is detected in volume group : vg1. ERROR!!!A null volume group has been detected.
Explanation: Displays the DB2 UDB Server Version. System Action: None. User Response: None. EEO0075W 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. System Action: None. User Response: None. EEO0076E ERROR!!!Current ESS CLI Version does not support the function that you are trying to run.
Explanation: An error was returned from specified volume group. System Action: Processing ends. User Response: Verify the target database information 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 Explanation: System Action: Processing ends. User Response: EEO0124I Mounting filesystem : fs1. 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. System Action: Processing Ends. User Response: Please install ESS CLI V230 or higher. 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 User Response: None
Explanation: Currently attempting to mount the file system. System Action: None. User Response:
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
961
EEO0125E EEO0136E
EEO0125E Explanation: System Action: Processing ends. User Response: EEO0126I Trying to find new devices to match the source device. This process will take some time....... ERROR!!!Serial number for the device v1 is not found. EEO0132W WARNING!!!The umount command failed with rc rc1 for mount point mntpt1.
Explanation: An error occurred while trying to remove a mount point. Processing continues. System Action: Processing continues. User Response: EEO0133E ERROR!!!Failed to open a logical volume device with errno errno for logical volume: lv.
Explanation: Currently trying to find a target device to match with the source device. System Action: None. User Response: EEO0127I Explanation: System Action: None. User Response: EEO0128E ERROR!!!Configuring the target volume would cause duplicate physical volume ID : pvid1. Removing device : parm1
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. System Action: Processing continues. 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.
Explanation: A different set of target volumes that were previously associated with the same source volumes was detected. System Action: Processing ends. 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 Explanation: System Action: Processing ends. User Response: EEO0130W WARNING!!!Removing the mount point directory mntpt1 failed with rc: rc1. ERROR!!!Removing device parm1 failed.
Explanation: An error occurred while trying to 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. System Action: Processing continues. 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. 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. EEO0136E ERROR!!!Volume group removing failed with rc rc1 for volume group vg1.
Explanation: An error occurred while trying to remove a mount point. Processing continues. System Action: Processing continues. User Response:
Explanation: An error occurred while performing the exportvg command. System Action: Processing ends.
962
IBM Tivoli Storage Manager: Messages
EEO0138I EEO0150E
User Response: Verify that the volume group is not corrupt. Run the exportvg command with the volume group name from the command line. EEO0138I Flashcopy type is set to NOCOPY. Removing disk meta data for all target disks... This backup is NOT valid for a flashcopy restore. Please 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. System Action: Processing ends. 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: 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 flashcopy restore. You can only restore from TSM Server. System Action: None. User Response: None. EEO0140I Flashcopy type is set to COPY or INCR. Leaving disk meta data intact for all target disks... This backup is valid for a flashcopy restore.
Explanation: The physical disk that database allocated is not found. System Action: Processing ends. User Response: If the problem persists, please collect the trace data and log file and present to IBM service representative. EEO0147I Explanation: System Action: None. User Response: EEO0148I Importing volume groups now... Exporting volume group fnm1 failed.
Explanation: The target PVIDs are not cleared.This process leaves disk metadata intact for all target disks. This backup can be used for a flashcopy restore. System Action: None. User Response: None. EEO0141E ERROR!!!Unsupported volume v1 has been detected.
Explanation: Processing an importing volume group command. System Action: None. User Response: EEO0149I Explanation: System Action: None. User Response: EEO0150E ERROR!!!Logical Volume can not be found for the file fnm1. Newly imported volume group: vg1
Explanation: The volume that database has benn allocated is an unsupported type. System Action: Processing ends. User Response: EEO0142E ERROR!!!Unsupported file system has been detected.
Explanation: The file system that database allocated is an unsupported type. System Action: Processing ends. User Response: Make sure that the mount point exists and the file system is supported. EEO0143E ERROR!!!Unsupported volume group v1 has been detected.
Explanation: The resources reside in an unsupported volume. System Action: Processing ends. 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.
Explanation: The volume group that database has been allocated is an unsupported type. System Action: Processing ends. User Response: Make sure that volume group is not rootvg.
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
963
EEO0151E EEO0172E
EEO0151E Explanation: System Action: None. User Response: EEO0162E EEO0152I Removing volume group fnm1 .... Explanation: System Action: Processing ends. User Response: EEO0164E EEO0153I Explanation: System Action: None. User Response: EEO0166E EEO0154I Explanation: System Action: None. User Response: EEO0156I Explanation: System Action: None. User Response: EEO0158I Explanation: System Action: None. User Response: EEO0160I <fn1> VOLUME GROUP : fn2 COPIES : fn3 SCHED POLICY : fn4 STALE PPs : fn5 MIRROR WRITE CONSISTENCY: fn6 LogDev=fn1 Serial Number=fn2 EEO0170W Explanation: System Action: None. User Response: EEO0172E Explanation: System Action: Processing ends. User Response: ERROR!!!Logical volume vg1 must have the mirror write consistency on. WARNING!!!Logical volume vg1 has vg2 stale partitions. Explanation: System Action: Processing ends. User Response: Finding the serial numbers ... <fnm1><fnm2><fnm3><fnm4><fnm5> Explanation: System Action: Processing ends. User Response: EEO0168E ERROR!!!Logical volume vg1 must have the parallel scheduling policy. ERROR!!!Logical volume vg1 must have at least 2 copies. Varied off and exported volume group : fnm1 Explanation: System Action: Processing ends. User Response: ERROR!!!Quorum of the volume group vg1 must be off. Explanation: Attempting to remove the volume groups. System Action: None. User Response: ERROR!!!Volume group vg1 can not be found. ERROR!!!Varying off volume group fnm1 failed. EEO0161E Explanation: System Action: Processing ends. User Response: ERROR!!!No volume group was found.
Explanation: System Action: None. User Response:
964
IBM Tivoli Storage Manager: Messages
EEO0174E EEO0275I
EEO0174E ERROR!!!None of the mirror copies of vg1 was completed on the specified ESS vg2. EEO0188E Explanation: System Action: None. User Response: EEO0190E Explanation: System Action: None. User Response: EEO0191I Explanation: System Action: None. User Response: EEO0270E ERROR!!!Invalid option found in the Setup File. Varying on volume group fnm1 failed. ERROR!!!The number of new volume groups is limited parm1. ERROR!!!lvm queryvg failed.
Explanation: System Action: Processing ends. User Response: EEO0176E Explanation: System Action: Processing ends. User Response: EEO0178I Could not determine the number of paths to target volumes. Using default value of 1. ERROR!!!Some of the partitions of vg1 are stale on the specified ESS vg2.
Explanation: System Action: None. User Response: EEO0180E ERROR!!!Failure in changing the mount point vg1, return code vg2 from command chfs.
Explanation: The parameter value is invalid. System Action: Processing ends. User Response: Correct the value and restart the processing. EEO0272I Flushing the buffers to disk...
Explanation: System Action: None. User Response: EEO0182E ERROR!!!The same hdisk vg1 can not be associated with two different vpaths (serial numbers vg2 and vg3). command chfs.
Explanation: Currently synchronizing to force the buffers to disk. System Action: None. User Response: EEO0273I Unmounting the file system mntpt1...
Explanation: System Action: None. User Response: EEO0184E Explanation: System Action: None. User Response: EEO0186I Explanation: System Action: None. User Response: Recreating the new volume groups.... ERROR!!!lsvg command failed.
Explanation: Currently attempting to unmount the file system from the mount point. System Action: None. User Response: EEO0274I Explanation: System Action: User Response: EEO0275I There are too many file systems. Bringing up the volume groups...
Explanation: The number of file systems exceeds compiled limit. System Action: None.
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
965
EEO0280E EEO0292W
User Response: 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. System Action: None. User Response: None. 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. System Action: Processing ends. User Response: Please restore the database from TSM Server using DB2 restore command. EEO0282I 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 FlashCopy restore. If you continue, you will lose newly added logical volumes. Do you want to continue? Please enter Yes or No.
Explanation: The specified physical volume was found during the FlashCopy backup as part of the database volumes on the production system. Now, on the FlashBack restore, it could not be found anymore on the production system. System Action: Processing ends. User Response: Logon with the user root and issue the command lsvpcfg. Check if the volume is displayed. Use the ESS web 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 ESS volumes. EEO0291E ERROR!!!The source volume with serial number cmd belongs to another volume group.
Explanation: System Action: Processing ends. User Response: EEO0284I Could not query the operating system to obtain the list of file systems for the volume groups containing the database.
Explanation: The specified physical volume was found during the FlashCopy backup as part of the database volumes on the production system. Now, on the FlashBack restore, DP for ESS found it as member of another volume group and can not proceed with the restore. System Action: Processing ends. 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 ESS volumes. EEO0292W WARNING!!!The logical volume lv on the mount point mp was renamed or newly added.
Explanation: System Action: Processing ends. User Response: EEO0286I Could not query the operating system to obtain the list of disks for the volume groups containing the database.
Explanation: System Action: Processing ends. User Response: 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: 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. System Action: None. 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.
Explanation: database_control_file_restore is set to yes in the setup file. You will need to do the incomplete recovery after the restore.
966
IBM Tivoli Storage Manager: Messages
EEO0293I EEO0302E
EEO0293I List of the current file systems on the backed up volume groups ... EEO0299I The following commands should be run after the flashcopy process in background is finished to synchronize the LVM copies:
Explanation: Prior the start of the FlashBack restore, DP for ESS will display a list of all the file systems which are currently on production database system. System Action: Processing ends. User Response: None. EEO0294I List of file systems which will be restored...
Explanation: DP for ESS will not automatically synchronize the copies after the reconstruction of the LVM mirror. A basic command will be created and put out. System Action: Processing ends. User Response: You have to start the synchronization of the LVM mirror manually after the flashcopy process in background has finished. If necessary you have to add additional parameter to the commands to improve the performance of the synchronization. EEP0300E ERROR!!!Error converting the ESS hdisk device volume group vg to a Subsystem Device Driver vpath device volume group.
Explanation: Prior the start of the FlashBack restore, DP for ESS will display a list of all the file systems which were on production database system at the time of the FlashCopy backup. System Action: Processing ends. User Response: None. EEO0297W WARNING!!!The newly added volume cmd will be reduced from the database volume group rc.
Explanation: The reducevg command removes physical volumes from a volume group. DP for ESS is calling it here on FlashBack restore to remove the physical volumes added to the database volume groups after the FlashCopy backup. System Action: Processing ends. User Response: None. 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: On the function FlashCopy backup, DP 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 on the backup system. System Action: Processing ends. User Response: Check the return code and the error message of the hd2vp command. Consult the AIX system documentation. EEO0301W WARNING!!!The rmlv command lv ended with return code rc.
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. System Action: None. 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.
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. System Action: Processing ends. User Response: Check the return code and the error 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 ESS volumes. EEO0302E ERROR!!!DP for ESS encountered a problem when using the FlashCopy 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.
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
967
EEO0303W EEO0310I
System Action: Processing ends. 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 possible causes of the problem. EEO0303W WARNING!!!The file system fs has already an entry in the /etc/filesystems. 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. System Action: Processing ends. User Response: Check the return code and the error 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 ESS volumes. EEO0307I Removing copies from the logical volumes ...
Explanation: DP for ESS found on the backup system after the flashcopy that the specified file system still exist in the /etc/filesystems. System Action: Processing ends. 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. EEO0304W WARNING!!!The reducevg command cmd ended with return code rc.
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. System Action: Processing ends. User Response: None. EEO0308I Removing physical volumes from the volume groups ...
Explanation: The reducevg command removes physical volumes from a volume group. DP for ESS 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 ESS 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 ESS that is not yet involved in the FlashCopy. System Action: Processing ends. User Response: Check the return code and the error message of the reducevg command. Consult the AIX system documentation. EEO0305W WARNING!!!The extendvg command cmd ended with return code rc.
Explanation: On the function FlashBack restore, after the rmlvcopy and prior to the exportvg and the actually flashcopy reverse, DP for ESS will use the command reducevg to remove the physical volumes residing on the second ESS. System Action: Processing ends. User Response: None. EEO0309I Adding physical volumes to the volume groups ...
Explanation: The extendvg command adds physical volumes to a volume group. DP for ESS will call it to add the volumes which are residing on the ESS that is not yet involved in the FlashBack to the database volume groups. System Action: Processing ends. User Response: Check the return code and the error message of the extendvg command. Consult the AIX system documentation. EEO0306W WARNING!!!The mklvcopy command cmd ended with return code rc.
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. System Action: Processing ends. User Response: None. EEO0310I Adding copies to the logical volumes ...
Explanation: On the function FlashBack restore, DP for ESS will use the command mklvcopy to add the copies of the logical volumes on the second ESS. This will take effect after the importvg and the extendvg. System Action: Processing ends. User Response: None.
Explanation: DP for ESS will call the command mklvcopy to add a copy of a logical volume on the physical volumes residing on the second ESS. This call
968
IBM Tivoli Storage Manager: Messages
EEO0311W EEO0351E
EEO0311W WARNING!!!The command cmd ended with return code rc. EEO0315I Could not mount all the filesystems originally present.
Explanation: The execution of the system command ended with the displayed return code. System Action: Processing ends. User Response: Check the return code and the error message of the specified command. Consult the AIX system documentation. EEO0312E ERROR!!!Importing the volume group from hdisk logdev failed.
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 the recovery, if this file system was already used from the production database. EEO0316W WARNING!!!The database volume groups do not contain currently any file system.
Explanation: DP for ESS 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. System Action: Processing ends. User Response: Check the return code and the error message of the importvg command. Consult the AIX system documentation. EEO0313E ERROR!!!Recreating the volume group from the hdisks hdisks failed.
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: User Response: None. EEO0317W WARNING!!!One or more errors were found disabling the production system resources. Though, the FlashBack restore will continue.
Explanation: DP for ESS will use the command recreatevg on the function FlashCopy backup if the production database is residing on an high-available LVM mirror environment. This command will be issued on the backup system 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 ESS where the flashcopy was issued. System Action: Processing ends. User Response: Check the return code and the error message of the recreatevg command. Consult the AIX system documentation. EEO0314W WARNING!!!Removing the logical device logdev whith the same PVID pvid in the ODM.
Explanation: This message will appear if running the function FlashBack restore, some error occurs unmounting the existing file systems and removing the volume groups. Though, DP for ESS will continue with the FlashBack restore. System Action: User Response: None. EEO0350E ERROR!!!Error while getting the size of the volume: src1 size.
Explanation: The ESS query command cannot determine the size of the volume. System Action: Processing ends. 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. EEO0351E ERROR!!!The size of source volume: src1 size1 and target volume: tgt1 size2 are different.
Explanation: There is still another logical device (hdisk or vpath) in the state defined with the same PVID as one of the source volumes. System Action: Processing continues. User Response: None.
Explanation: The size of the source volume and target volume are different. The source volume and target
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
969
EEO0352E EEO0359I
volume must be the same size and reside in the same Logical Subsytem (LSS). System Action: Processing ends. 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!!!Incorrect value size is specified for thetarget volume: tgt1 in the Setup File. target volumes. If the command line interface package and Copy Services microcode are not in sync, check with the Enterprise Storage Server administrator to obtain the appropriate level of Copy Services command line interface and microcode. EEO0356E ERROR!!!Cannot find a target volume to match with the source volume parm1.
Explanation: A target volume could not be found. System Action: Processing ends. 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. primary_copyservices_servername 5. shark_username 6. shark_password EEO0357I Performing flashcopy withdraw of source ESS volume src1 from target ESS volume tgt1
Explanation: The shark_target_volume parameter in the Setup File specifies an incorrect size for the target volume. System Action: Processing ends. 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.
Explanation: An error was detected when trying to open the file. The file may not exist. System Action: Processing ends. User Response: Make sure the file exists.
Explanation: A flashcopy withdraw of the source volume from the target volume was requested. System Action: None. User Response: EEO0358E ERROR!!!No target volume is available. Terminating......
EEO0354I
Performing fctype flashcopy of: Source ESS volume: src1 to Target ESS volume: tgt1
Explanation: No target volume was found. System Action: Processing ends. 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. primary_copyservices_servername 5. shark_username 6. shark_password EEO0359I Incremental Change Recording: val1
Explanation: A flashcopy from the source volume to the target volume was requested. System Action: None. 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. System Action: Processing ends. 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
Explanation: Value of Incremental change recording. System Action: None. User Response:
970
IBM Tivoli Storage Manager: Messages
EEO0360I EEO0370E
EEO0360I Querying the ESS for volume size ...Volume: volser1 volsize EEO0366I Flashcopy was performed with parm1 option.
Explanation: A query of the target volume was requested. System Action: None. User Response: EEO0361I A NOCOPY Flashcopy was performed. Withdrawing the nocopy flashcopy relationship...
Explanation: This is the type of flashcopy that was actually performed. It may be different from the value specified by the user as DP for ESS overrides this value under certain conditions. System Action: None. User Response: None. 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: The flashcopy relationship between the source and target volumes terminates after the NOCOPY Flashcopy is performed. System Action: None. User Response: EEO0362I Checking the status of the primary Copy Services Server:serv1
Explanation: Whenever user performs an incremental flashcopy restore operation, the source and target ESS volumes will be reversed. System Action: None. User Response: None. EEO0368I The backup Copy Services server is ready...
Explanation: Currently verifying the primary Copy Services server status. System Action: None. User Response: EEO0363I Primary Copy Services server is ready.
Explanation: The backup Copy Services server is ready. System Action: None. 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 is ready. System Action: None. User Response: EEO0364I The connection to the primary Copy Services server failed. The process continues to check the backup Copy Services server.
Explanation: The primary Copy Services server and the backup Copy Services server are not available. System Action: Processing ends. 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 primary Copy Services server is not available. Verify that the TCP/IP connection is valid. System Action: None. User Response: EEO0365I Checking the status of the backup Copy Services Server:serv1
Explanation: Currently verifying the backup Copy Services server status. System Action: None. User Response:
Explanation: The backup Copy Services server is not specified in the Setup File. System Action: Processing ends. 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.
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
971
EEO0371I EEO0381I
EEO0371I Value of Flashcopy type is: parm1. Backup. This is necessary to ensure that a complete image of the database is available to the restore process. System Action: Processing ends. User Response: Ensure that the target volumes specified in the setup file are accurate. EEO0377I Background copy is in progress....Sleeping for v1 minutes....
Explanation: None. System Action: None. User Response: None. EEO0372I 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. System Action: None. User Response: EEO0373E ERROR!!!A required parameter tgtv1 is missing in the Setup File.
Explanation: Blocking for SHARK_QUERY_INTERVAL period prior to querying if the background copy operation has completed. System Action: None. User Response: None. EEO0378I Background copy is complete.
Explanation: A required parameter in the Setup File has not been specified. This may be caused by incorrect syntax in the Setup File. System Action: Processing ends. 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(:). EEO0374I Querying ESS for status of volume: volser1
Explanation: Background copy for flashcopy backup or restore is complete. System Action: None. User Response: None. EEO0379E ERROR!!!An invalid value: parm1 has been specified for backup destination.
Explanation: Backup destination can only be TSMONLY, DISKONLY or DISKANDTSM. System Action: Processing stops. User Response: Please specify TSMONLY, DISKONLY or DISKANDTSM for the option backup destination and retry the command. EEO0380E ERROR!!!An invalid value: parm1 has been specified for flashcopy type.
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. System Action: None. User Response: None. EEO0375E ERROR!!!ESS volumes are involved in a flashcopy or a PPRC operation.
Explanation: Flashcopy type can only be NOCOPY, COPY or INCR. System Action: Processing stops. 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
Explanation: ESS source or target volumes are involved in a flashcopy or a PPRC operation. Flashcopy backup or restore command will not be performed. System Action: Processing ends. 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. EEO0376E ERROR!!!ESS target volume v1 involved in the previous backup does not exist in the setup file.
Explanation: A query of all the source and target volumes was requested to ensure that background copy is not in progress between them. System Action: None. User Response: None.
Explanation: The list of target volumes specified in the setup file for restoring a specified database using Flashcopy Restore need to be the same as those specified in the setup file at the time of Flashcopy
972
IBM Tivoli Storage Manager: Messages
EEO0400E EEO0503E
EEO0400E ERROR!!!Error on running command: parm1 User Response: Please enter Yes to continue, or No 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: An error was detected while running a system command. System Action: Processing ends. User Response: Gather log file information and contact your IBM service representative. EEO0402I Explanation: System Action: None. User Response: EEO0404I Explanation: System Action: None. User Response: EEO0406I User abort; Exiting Flashcopy Restore. Error: parm1 parm1
Explanation: Flashcopy Restore overwrites any existing data on all the source LUNs, including (but not 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: 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. System Action: Processing ends. 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: The user has chosen to terminate the Flashcopy Restore operation. 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: An invalid license was found. System Action: Processing ends. User Response: Check if there is a mismatch between the executables (for the production system and backup system) and the license file(agent.lic). EEO0503E ERROR!!!An error has been detected when calling TSM API setup.
Explanation: The user has chosen to continue the Flashcopy Restore operation. System Action: Restore processsing continues. 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: An error was detected when calling TSM API setup. System Action: Processing ends. 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.
Explanation: 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. System Action: System waits for a valid user response.
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
973
EEO0504E EEO0637E
EEO0504E ERROR!!!An error has been detected when calling TSM API init. EEO0633E ERROR!!!A data for required parameter tgtv1 is missing in the Setup File.
Explanation: An error was detected when calling TSM API init. System Action: Processing ends. 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 ERROR!!!An error has been detected when calling TSM API terminate.
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. System Action: Processing ends. 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(:). EEO0634E ERROR!!!An incorrect incremental backup level found.
Explanation: An error was detected when calling TSM API terminate. System Action: Processing ends. 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. EEO0506E ERROR!!!An error has been detected when running the TSM Backup Archive Client command line interface.
Explanation: An incorrect incremental backup level was specified. System Action: Processing ends. User Response: The incremental backup level must be a decimal number greater than or equal to 1. EEO0635E ERROR!!!Temporary file cannot be opened for writing.
Explanation: An error was detected when running the TSM Backup Archive Client Client command line interface. System Action: Processing ends. User Response: Make sure the TSM Backup Archive Client is correctly installed and that the environmental variables are set correctly. EEO0630E ERROR!!!A memory allocation error has occurred.
Explanation: Temporary file cannot be opened for writing. System Action: Processing ends. User Response: Make sure you have enough space to create one file and have permission to create a file in that directory. EEO0636E ERROR!!!The metadata file cannot be created.
Explanation: The application could not create a temporary file in the root filesystem. System Action: Processing ends. 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!!!A temporary directory could not be created.
Explanation: Enough memory was not available to continue processing. System Action: Processing ends. User Response: Ensure that your system has sufficient real and virtual memory. Close unnecessary applications. EEO0632E ERROR!!!A duplicate target volume serial number tvol1 was found in the Setup File.
Explanation: The application could not create a temporary directory in the root filesystem. System Action: Processing ends. User Response: Make sure you have enough space in the root file system, and have permission to create a directory in that file system.
Explanation: A duplicate target volume was specified in the Setup File. System Action: Processing ends. User Response: Correct the duplicate volume serial number in the Setup File and remove the duplicate occurrences.
974
IBM Tivoli Storage Manager: Messages
EEO0638E EEO6011E
EEO0638E ERROR!!!Background copy operation for a flashcopy backup or restoreis not complete. 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 5.2.1. or later.
Explanation: The background copy operation for a flashcopy backup or restore command has not completed. System Action: Processing ends. User Response: Invoke essdb2p monitor command to ensure that the background copy operation is complete before issuing a flashcopy restore or backup command. EEO0639W WARNING!!!Could not copy setup file v1 to directory v2. Explanation:
System Action: None. User Response: EEO0644E ERROR!!!Database instance name has not been specified in the user setup file. Please specify the instance name and retry the operation.
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. System Action: Processing continues. User Response: None.
Explanation: Please specify the database instance name in the user setup file and retry the operation. System Action: None. 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.
EEO0640E
ERROR!!!Could not open trace file v1.
Explanation: There were some problems opening tracefile. Please make sure you can open the trace file which was specified in the setup file. System Action: Processing terminates. User Response: None. EEO0641E ERROR!!!Could not create the trace object.
Explanation: Please specify the database name in the user setup file and retry the operation. System Action: None. User Response: Please specify the database name in the user setup file and retry the operation. EEO4000E ERROR!!!program-name: cannot open file file-spec: error.
Explanation: There were some problems creating trace class object. System Action: Processing terminates. User Response: None. EEO0642E ERROR!!!Invalid trace flag: v1.
Explanation: TSM cannot open the file. System Action: TSM cannot complete the requested operation. User Response: Retry the operation. If the problem continues, check with your system adminis trator. EEO6011E ERROR!!!The Oracle database is currently in read-only mode.
Explanation: Some invalid trace flags are defined in the setup file. System Action: Processing terminates. User Response: None.
Explanation: The Oracle database is currently designated as read-only. Processing stops. System Action: Processing ends. User Response: Remove the read-only mode of the Oracle database and run the operation again.
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
975
EEO6012E EEO6022I
EEO6012E ERROR!!!An error occurred while attempting an alter system suspend action. EEO6017E ERROR!!!No table space was found for the Oracle database.
Explanation: An error occurred while attempting an alter system suspend action. System Action: Processing ends. 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. EEO6013E ERROR!!!An error occurred while attempting an alter system resume action.
Explanation: No table space was found for the Oracle database. System Action: Processing ends. User Response: Make sure the correct database system identifier (SID) is specified in the Setup File. 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. System Action: Processing ends. User Response: Make sure you have a valid password file for this database. EEO6019E ERROR!!!The log mode for this database is NOARCHIVELOG.
Explanation: An error occurred while attempting an alter system resume action. System Action: Processing ends. 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 log mode for this database is NOARCHIVELOG. System Action: Processing ends. User Response: Change the log mode for this database to ARCHIVELOG. EEO6020E ERROR!!!The database failed to shutdown during the flashcopy operation.
Explanation: The Backup type is online but the mount mode is either nomount or startup restricted. System Action: Processing ends. User Response: Change the mount mode to startup mount. EEO6015E ERROR!!!Oracle database data files were not found.
Explanation: The database attempted to shutdown because the backup type parameter is set to offline. The database failed to shutdown. System Action: Processing ends. User Response: Manually shutdown the database you are trying to back up, then run the operation again. EEO6021I Explanation: System Action: Processing continues. User Response: EEO6022I Explanation: System Action: Processing continues. User Response: Production datafile parm1 cataloged as parm2. Changing Oracle mode to: parm1.
Explanation: Oracle database data files were not found. System Action: Processing ends. User Response: Make sure the correct database system identifier (SID) is specified in the Setup File. EEO6016E ERROR!!!Oracle database control files were not found.
Explanation: Oracle database control files were not found. System Action: Processing ends. User Response: Make sure the correct database system identifier (SID) is specified in the Setup File.
976
IBM Tivoli Storage Manager: Messages
EEO6023I EEO7367E
EEO6023I Explanation: System Action: Processing continues. User Response: EEO6024E ERROR!!!RMAN Backup for the database v1 failed. EEO6031W WARNING!!!Remote process v1 failed. i Oracle DB on remote cluster node couldnt be brought down before Flashcopy Restore was started. Retrieved file parm1 from node: parm2. System Action: Processing ends. User Response: Make sure the correct database system identifier (SID) is specified in the Setup File.
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. System Action: Processing ends. User Response:
Explanation: We tried to remotely shutdown Oracle DB on the remote cluster node, but failed. System Action: None. User Response: May need to do Flashcopy Restore again. EEO6032W WARNING!!!Remote process v1 failed. i
EEO6025I Explanation:
The Oracle database v1 backed up successfully.
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. System Action: None. User Response: May need to do Flashcopy Restore again. EEO7152I Performance stats: seconds seconds spent in apicall API calls
System Action: Processing continues. User Response: EEO6026E ERROR!!!Failed to get parallel information.
Explanation: Failed to get parallel information using sqlplus. System Action: Processing terminates. User Response: EEO6027E ERROR!!!Failed to get oracle version information.
Explanation: The indicated number of seconds were spent making API calls for the indicated system. System Action: Processing continues. User Response: None EEO7366E ERROR!!!Unable to close trace output file file-name.
Explanation: Failed to get oracle version information using sqlplus. System Action: Processing terminates. User Response: EEO6028E ERROR!!!Oracle database redo log files were not found.
Explanation: An error occurred during the closing of a trace output file-name (for example, not enough disk space). System Action: Processing continues. User Response: Check the options.doc file for a description of possible causes of the error, or see your system administrator. EEO7367E ERROR!!!Unable to write to trace file tracefile. Tracing disabled.
Explanation: Oracle database redo log files were not found. System Action: Processing ends. User Response: Make sure the correct database system identifier (SID) is specified in the Setup File. EEO6030E ERROR!!!No host name was found for the Oracle database.
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: No host name was found for the Oracle database.
Chapter 16. Data Protection for Enterprise Storage Server for Oracle
977
EEO7368E EEO7826E
EEO7368E ERROR!!!Invalid trace file name (name too long). EEO7826E ERROR!!!Unable to open trace output file file-name.
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. EEO7383E ERROR!!!Specifying the trace file link as a symbolic link is not allowed.
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. System Action: Client program did not initialize. User Response: Change the TRACEFILE value so that it is a location to which you have write access.
Explanation: Trace file linkname cannot be a symbolic link. System Action: The symbolic link linkname is deleted, the trace file is recreated, and processing stops. User Response: Specify the trace file location with the tracefile option. EEO7384E ERROR!!!Symbolic link linkname to target was successfully deleted.
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. EEO7385E ERROR!!!Unable to delete symbolic link link.
Explanation: Log linkname cannot be a symbolic link. System Action: Processing stops. User Response: Delete the symbolic link linkname. EEO7823E ERROR!!!Invalid trace keyword keyword
Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect. System Action: Client program did not initialize or tracing was not enabled in the applet. User Response: Correct the value. See the entry for TRACEFLAGS in the Trace Facility Guide document for a list of valid trace flags.
978
IBM Tivoli Storage Manager: Messages
Part 5. Appendixes
Copyright IBM Corp. 1993, 2004
979
980
IBM Tivoli Storage Manager: Messages
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 I Severe error Error Warning Information Processing cannot continue. Processing cannot continue. Processing can continue, but problems might develop later. You should be cautious. Processing continues. User response is not necessary.
v The symbolic name. This name corresponds to the definition in the header file, dsmrc.h. Always use the symbolic name for a return code in your application rather than the return code number. v The explanation. This field explains the circumstances under which this return code might be generated. v The system action. This field describes what action 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.
Copyright IBM Corp. 1993, 2004
981
-452 E
DSM_RC_SHM_NOTAUTH
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
Explanation: An error has occurred while reading or writing data through the Shared Memory communications protocol. System Action: ITSM cannot complete the requested operation. User Response: Check the trace log for additional information and retry the operation. If the problem continues, see your system administrator for further help. -450 E DSM_RC_SHM_TCPIP_FAILURE
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. 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 problem continues, see your system administrator for further help. -190 E DSM_RC_NP_ERROR
Explanation: An attempt to connect to the server 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. System Action: Processing stopped. User Response: Retry the operation, or wait until the 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
Explanation: The ITSM DLL dsm3270.dll cannot be found in the user's path. System Action: Communications link is not established. User Response: Make sure that the ITSM DLL dsm3270.dll is in a directory that is included in the user's path. -057 E DSM_RC_TCPIP_LOADFAILURE
Explanation: An error occurred while locating a function. The TCP/IP load function failed. System Action: Processing stopped. User Response: Verify your TCP/IP installation.
982
IBM Tivoli Storage Manager: Messages
-056 E
DSM_RC_TCPIP_DLL_LOADFAILURE
Explanation: An error occurred while loading a library. The TCP/IP DLL load failed. System Action: Processing stopped. User Response: Verify your TCP/IP installation. -055 E DSM_RC_WINSOCK_MISSING
Explanation: The TCP/IP WINSOCK.DLL file cannot be found. System Action: Processing stopped. User Response: Verify your TCP/IP installation. -054 E DSM_RC_NETWORK_UNREACHABLE
Explanation: The TCP/IP host name specified in the TCPSERVERADDRESS statement cannot be reached. System Action: Processing stopped. 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
Explanation: An invalid TCP/IP host name or address was specified. System Action: Processing stopped. User Response: Check your options file for the correct TCPSERVERADDRESS statement. See your administrator for the correct name of the server. -052 E DSM_RC_CONN_REFUSED
Explanation: An attempt to establish a TCP/IP connection was rejected by the server. System Action: Processing stopped. 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. -051 E DSM_RC_CONN_TIMEDOUT
Explanation: The attempt to establish a TCP/IP connection timed out before the connection was made. System Action: Processing stopped. User Response: Check for a networking problem. If the problem continues, see your system administrator. API applications should close the session with dsmTerminate. -050 E DSM_RC_TCPIP_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 problem continues, see your system administrator for further help.
Appendix A. API Return Codes with Explanations
983
0000 I
DSM_RC_OK
Explanation: The operation successfully completed. System Action: None. User Response: None. 0001 E DSM_RC_ABORT_SYSTEM_ERROR
Explanation: The server detected a system error and notified the clients. System Action: Processing stopped. User Response: See your system administrator for further information on server activity. 0002 E DSM_RC_ABORT_NO_MATCH
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. System Action: Processing stopped. 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. 0003 E DSM_RC_ABORT_BY_CLIENT
Explanation: The client system ended the operation with the server and ended the current transaction. System Action: Processing stopped. User Response: Restart the session. 0004 W DSM_RC_ABORT_ACTIVE_NOT_FOUND
Explanation: ITSM did not find an active object flagged for expiration on the server. The object is marked as expired by another ITSM operation. System Action: None. User Response: None. 0005 E DSM_RC_ABORT_NO_DATA
Explanation: ITSM tried to do a restore or retrieve on an object that has no data associated with it. System Action: ITSM ended the current operation. User Response: See your system administrator to verify the problem. If the problem continues, see your system administrator. 0006 E DSM_RC_ABORT_BAD_VERIFIER
Explanation: You entered an incorrect password (verifier). System Action: Processing stopped. User Response: Retry the session with the correct password. 0007 E DSM_RC_ABORT_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. System Action: Processing stopped.
984
IBM Tivoli Storage Manager: Messages
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
Explanation: Archive expiration date is too low, the date must be greater than todays date. System Action: ITSM canceled the current operation. User Response: Retry archiving the file with an expiration date that is higher than todays date. 0009 W DSM_RC_ABORT_DATA_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: ITSM waits for offline storage media to become available and then continues. User Response: None. 0010 E DSM_RC_ABORT_EXCLUDED_BY_SIZE
Explanation: The object is too large. The configuration of the server does not have any data storage space that accepts the object. System Action: File skipped. User Response: See your system administrator to determine the maximum file (object) size for which your sites server is configured. 0011 E DSM_RC_ABORT_NO_REPOSIT_SPACE
Explanation: The server does not have any space available to store the object. System Action: ITSM ended the current operation. User Response: You can take any of the following actions: v Request the system administrator to add space to the storage pool. v For ITSM 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. 0012 E DSM_RC_ABORT_MOUNT_NOT_POSSIBLE
Explanation: Server media mount not possible. The server timed out waiting for a mount of an offline volume. System Action: File skipped. 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
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. System Action: Processing stopped. User Response: Retry the operation. If the problem 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.
Appendix A. API Return Codes with Explanations
985
0014 E
DSM_RC_ABORT_DATA_UNAVAILABLE
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. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, see your system administrator to determine the problem from the server console or the activity log. 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
Explanation: Unexpected Retry request. The server found an error while writing data to the servers data storage. System Action: Client retries the operation. User Response: None. 0016 E DSM_RC_ABORT_NO_LOG_SPACE
Explanation: The server ran out of recovery log space. System Action: ITSM ended the current operation. User Response: This error is a temporary problem. Retry later or see your system administrator. 0017 E DSM_RC_ABORT_NO_DB_SPACE
Explanation: The server ran out of database space. System Action: ITSM ended the current operation. User Response: See your system administrator. 0018 E DSM_RC_ABORT_NO_MEMORY
Explanation: The server ran out of memory. System Action: ITSM ended the current operation. User Response: This is a temporary problem. Retry later or see your system administrator. 0020 E DSM_RC_ABORT_FS_NOT_DEFINED
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. System Action: ITSM canceled the current operation. 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
Explanation: Open registration failed because a node is defined in the server with the same name. System Action: ITSM canceled the current operation. User Response: Retry with another node name.
986
IBM Tivoli Storage Manager: Messages
0022 S
DSM_RC_ABORT_NO_DEFAULT_DOMAIN
Explanation: Open registration failed because a default policy domain does not exist for you to place your node. System Action: ITSM canceled the current operation. User Response: See your system administrator. 0023 S DSM_RC_ABORT_INVALID_NODENAME
Explanation: Open registration failed because the specified node name contains invalid characters. System Action: ITSM canceled the current operation. User Response: Retry with another node name that does not have any invalid characters. 0024 S DSM_RC_ABORT_INVALID_POL_BIND
Explanation: Server problem. Invalid policy binding. System Action: Processing stopped. User Response: Have your service representative check the error log. 0025 E DSM_RC_ABORT_DEST_NOT_DEFINED
Explanation: Server problem: Destination not defined. System Action: Processing stopped. User Response: Have your service representative check the error log. 0026 S DSM_RC_ABORT_WAIT_FOR_SPACE
Explanation: The client received an unexpected Wait For Space message from the server. System Action: ITSM ended the current operation. User Response: See your system administrator. 0027 E DSM_RC_ABORT_NOT_AUTHORIZED
Explanation: During a delete filespace operation, you specified a file space to which your node does not have permission to delete archived data and/or backed up data. System Action: Delete processing fails. User Response: See your system administrator. 0028 E DSM_RS_ABORT_RULE_ALREADY_DEFED
Explanation: You are trying to define authorization for the specified node, which already has authorization defined. System Action: ITSM 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. 0029 S DSM_RC_ABORT_NO_STOR_SPACE_STOP
Explanation: The server does not have space available to store the object. System Action: ITSM ended the current operation. User Response: Report to your system administrator that a storage pool on the server is full.
Appendix A. API Return Codes with Explanations
987
0032 E
DSM_RC_ABORT_DUPLICATE_OBJECT
Explanation: A duplicate object was found, operation cannot complete. System Action: The requested operation failed. User Response: Try the operation with a different file specification. 0033 E DSM_RC_ABORT_INVALID_OFFSET
Explanation: The partialObjOffset value for partial object retrieve is invalid. System Action: The system returns to the calling procedure. User Response: Specify a valid value. 0034 E DSM_RC_ABORT_INVALID_LENGTH
Explanation: partialObjLength value for partial object retrieve is invalid. System Action: The system returns to the calling procedure. User Response: Specify a valid value. 0041 E DSM_RC_ABORT_EXCEED_MAX_MP
Explanation: All the tape mount points for this node are in use. System Action: The system returns to the calling procedure. User Response: Increase the number of allowed tape mounts for this node on the server. 0045 E DSM_RC_ABORT_MERGE_ERROR
Explanation: The specified objects failed the merge test, operation cannot complete. System Action: The requested operation failed. User Response: See documentation for the merge test parameters. 0047 E DSM_RC_ABORT_INVALID_OPERATION
Explanation: The operation is not valid. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. 0048 E DSM_RC_ABORT_STGPOOL_UNDEFINED
Explanation: The storage pool is not defined. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. 0049 E DSM_RC_ABORT_INVALID_DATA_FORMAT
Explanation: none System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information.
988
IBM Tivoli Storage Manager: Messages
0050 E
DSM_RC_ABORT_DATAMOVER_UNDEFINED
Explanation: none System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. 0051 E DSM_RC_REJECT_NO_RESOURCES
Explanation: ITSM has all available sessions in use and cannot accept a new one at this time. System Action: ITSM canceled the current operation. User Response: Retry the operation. If the problem continues, see your system administrator to increase the number of concurrently active sessions to the server. 0052 E DSM_RC_REJECT_VERIFIER_EXPIRED
Explanation: Your ITSM password has expired. System Action: ITSM canceled the current operation. You are not allowed to connect to the server until the password is updated. User Response: Update your password. 0053 E DSM_RC_REJECT_ID_UNKNOWN
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. System Action: ITSM canceled the current operation. 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 nodename must be the same node which migrated the file. User Response: Ensure that you entered your ITSM 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: Another process using this node name is active with the server. System Action: ITSM cannot connect to the server. ITSM canceled the current operation. User Response: If you are running a UNIX-based system, ensure that another process is not active with ITSM 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
Explanation: The server is in a disabled state and cannot be accessed for normal activity. System Action: ITSM canceled the current operation. User Response: Retry the operation after the server returns to an enabled state. If the problem continues, see your system administrator. 0056 E DSM_RC_REJECT_CLOSED_REGISTER
Explanation: No authorization. Registration is required by your system administrator. The server is not configured to allow open registration. System Action: Session not started. User Response: You must obtain a ITSM node and password from your system administrator.
Appendix A. API Return Codes with Explanations
989
0057 S
DSM_RC_REJECT_CLIENT_DOWNLEVEL
Explanation: The server version and your client version do not match. The client code is downlevel. System Action: ITSM canceled the current operation. User Response: See your system administrator to see what version of ITSM to run for your location. 0058 S DSM_RC_REJECT_SERVER_DOWNLEVEL
Explanation: The server version and your client version do not match. The server code is downlevel. System Action: ITSM canceled the current operation. User Response: See your system administrator to see what version of ITSM to run for your location. 0059 E DSM_RC_REJECT_ID_IN_USE
Explanation: The node name you specified is in use on the server. System Action: Session was not started. 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. 0061 E DSM_RC_REJECT_ID_LOCKED
Explanation: The node name you specified is currently locked on the server. System Action: Session was not started. User Response: Check with your system administrator to find out why your node name is locked. 0062 S DSM_RC_SIGNONREJECT_LICENSE_MAX
Explanation: Adding a new enrollment will exceed the product license count for ITSM. System Action: Execution of the client enrollment or connection request ends. User Response: See your system administrator. 0063 E DSM_RC_REJECT_NO_MEMORY
Explanation: The server does not have enough memory to allow your client to establish a connection with the server. System Action: Session was not started. User Response: Retry later or see your system administrator. 0064 E DSM_RC_REJECT_NO_DB_SPACE
Explanation: The server ran out of database space. System Action: Session was not started. User Response: See your system administrator. 0065 E DSM_RC_REJECT_NO_LOG_SPACE
Explanation: The server ran out of recovery log space. System Action: Session was not started. User Response: This error is a temporary problem. Retry later or see your system administrator.
990
IBM Tivoli Storage Manager: Messages
0066 E
DSM_RC_REJECT_INTERNAL_ERROR
Explanation: The client cannot establish a connection to the server because of an internal server error. System Action: Session was not started. User Response: See your system administrator immediately. 0067 S DSM_RC_SIGNONREJECT_INVALID_CLI
Explanation: The server is not licensed for the requesting client type. System Action: Execution of the client enrollment or connection request ends. User Response: See your system administrator. 0068 E DSM_RC_SESSION_CANCELED
Explanation: The server administrator canceled the current client session. System Action: Execution of the client connection request ends. User Response: See your system administrator. 0073 E DSM_RC_REJECT_INVALID_NODE_TYPE
Explanation: The user has probably coded the node option incorrectly. For instance, the node that is registered to the ITSM server might be a type of NAS, but the node is actually a non-NAS client. System Action: The ITSM operation ends. 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
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. System Action: The IBM Tivoli Storage Manager 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
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. 0101 W DSM_RC_USER_ABORT
Explanation: An abort signal to stop an operation was received. System Action: Processing stopped. User Response: Continue with normal operations.
Appendix A. API Return Codes with Explanations
991
0102 E
DSM_RC_NO_MEMORY
Explanation: IBM Tivoli Storage Manager has encountered a condition where it can not allocate any more memory. 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: Processing stopped. User Response: Stop any unnecessary programs that are running and retry the operation. Reducing the scope of queries and the amount of data returned can also solve the problem. If the error reoccurs, contact your support representative, and be sure to provide the entire text of this message along with detailed information about how you got this message. 0104 E DSM_RC_FILE_NOT_FOUND
Explanation: The file being processed for backup, archive or migrate no longer exists on the client. Another process deleted the file before it could be backed up, archived or migrated by ITSM. System Action: File skipped. User Response: None. 0105 E DSM_RC_PATH_NOT_FOUND
Explanation: You specified an incorrect directory path. System Action: Processing stopped. User Response: Correct the syntax specified and retry the operation. 0106 E DSM_RC_ACCESS_DENIED
Explanation: Access to the specified file or directory is denied. You tried to read from or write to a file and you do not have access permission for either the file or the directory. System Action: Processing stopped. User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location. 0106 E DSM_RC_ACCESS_DENIED
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. System Action: Processing stopped. User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location. 0107 E DSM_RC_NO_HANDLES
Explanation: All file handles for your system are currently in use. No more are available. System Action: Processing stopped. 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.
992
IBM Tivoli Storage Manager: Messages
0108 E
DSM_RC_FILE_EXISTS
Explanation: The file being restored or retrieved exists. System Action: File is replaced or skipped depending on client options. User Response: None. 0109 E DSM_RC_INVALID_PARM
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. 0110 E DSM_RC_INVALID_HANDLE
Explanation: An internal system error occurred. A file operation failed because an invalid file handle was passed. System Action: Processing stopped. User Response: Report the problem to your system administrator, and then retry the operation. 0111 E DSM_RC_DISK_FULL
Explanation: No more files can be restored or retrieved because the destination disk is full. System Action: Processing stopped. User Response: Free up disk space, or restore or retrieve the file to another disk. 0113 E DSM_RC_PROTOCOL_VIOLATION
Explanation: A communications protocol error occurred. The communication subsystem is not properly defined or is itself in error. System Action: ITSM ended the current operation. User Response: Verify that the communication processes are operating properly, and then retry the operation. 0114 E DSM_RC_UNKNOWN_ERROR
Explanation: An unknown error occurred. This might be a low-level system or communication error that ITSM cannot handle or recover from. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help. 0115 E DSM_RC_UNEXPECTED_ERROR
Explanation: An unexpected error occurred. This might be a low-level system or communication error that ITSM cannot handle or recover from. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help. 0116 E DSM_RC_FILE_BEING_EXECUTED
Explanation: The current file cannot be opened to write to because it is currently being run by another operation. System Action: File skipped.
Appendix A. API Return Codes with Explanations
993
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. 0117 E DSM_RC_DIR_NO_SPACE
Explanation: No more files can be restored or retrieved since the destination directory is full. System Action: Processing stopped. User Response: Free up disk space, or restore or retrieve the file to another disk. 0118 E DSM_RC_LOOPED_SYM_LINK
Explanation: While trying to resolve the file name, too many symbolic links were found. System Action: File skipped. User Response: Ensure that you do not have a looping symbolic link for the file. 0119 E DSM_RC_FILE_NAME_TOO_LONG
Explanation: The file name specified is too long to be handled by ITSM. 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 ITSM. 0120 E DSM_RC_FILE_SPACE_LOCKED
Explanation: File system cannot be accessed because it is locked by the system. System Action: ITSM cannot complete the operation. User Response: See your system administrator. 0121 I DSM_RC_FINISHED
Explanation: The operation is finished. System Action: The system returns to the calling procedure. User Response: Proceed with next function call. 0122 E DSM_RC_UNKNOWN_FORMAT
Explanation: ITSM tried to restore or retrieve a file, but it had an unknown format. System Action: File skipped. User Response: See your system administrator. 0123 E DSM_RC_NO_AUTHORIZATION
Explanation: The client is not authorized to restore the other node's data. System Action: The system returns to the calling procedure. User Response: Get authorization from the other node. 0124 E DSM_RC_FILE_SPACE_NOT_FOUND
Explanation: The specified file space (domain) is incorrect or does not exist on the machine. System Action: Processing stopped. User Response: Retry the operation specifying an existing domain (drive letter or file system name).
994
IBM Tivoli Storage Manager: Messages
0125 E
DSM_RC_TXN_ABORTED
Explanation: The current transaction between the server and the client stopped. A server, client, or communication failure cannot be recovered. System Action: ITSM canceled the current operation. User Response: Retry the operation. If the problem continues, see your system administrator to isolate the problem. 0126 E DSM_RC_SUBDIR_AS_FILE
Explanation: ITSM tried to create a directory path, but is unable to because a file exists that has the same name as a directory. System Action: Processing stopped. 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. 0127 E DSM_RC_PROCESS_NO_SPACE
Explanation: The disk space allocated for the client owner is full. System Action: Processing stopped. User Response: Free up disk space and retry the restore or retrieve operation. 0128 E DSM_RC_PATH_TOO_LONG
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. System Action: Processing stopped. User Response: Specify a destination path that, when combined, is less than the system maximum. 0129 E DSM_RC_NOT_COMPRESSED
Explanation: A file that was flagged as compressed was not compressed, and the system failed. System Action: Processing stopped. User Response: See your system administrator to report this problem. This error is a system failure. 0130 E DSM_RC_TOO_MANY_BITS
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: ITSM canceled the operation. User Response: Obtain a machine with more memory and retry the operation. 0131 S DSM_RC_SYSTEM_ERROR
Explanation: An unexpected program failure occurred. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, see your system administrator or your service representative.
Appendix A. API Return Codes with Explanations
995
0132 E
DSM_RC_NO_SERVER_RESOURCES
Explanation: The server ran out of resources. A lack of storage or a condition does not allow any new activity. System Action: ITSM canceled the current operation. User Response: Retry the operation at a later time. If the problem continues, see your system administrator to isolate what resource is unavailable. 0133 E DSM_RC_FS_NOT_KNOWN
Explanation: The number defining the correspondence between drive letter or file (domain name) and volume label is not known to the server. System Action: Processing stopped. User Response: Report the program error to your service representative. 0134 E DSM_RC_NO_LEADING_DIRSEP
Explanation: The objName field does not have a leading directory separator. System Action: The system returns to the calling procedure. User Response: Correct the value for the objName. 0135 E DSM_RC_WILDCARD_DIR
Explanation: Wildcards are not allowed in the objName directory path. System Action: The system returns to the calling procedure. User Response: Correct the value for the objName. 0136 E DSM_RC_COMM_PROTOCOL_ERROR
Explanation: Communications protocol error. An unexpected communications message was received by the client. System Action: ITSM canceled the current operation. User Response: Verify that your communication path is functioning properly. If the problem continues, have your service representative check for a possible program error. 0137 E DSM_RC_AUTH_FAILURE
Explanation: Authentication failure. You entered an incorrect password. System Action: ITSM canceled the current operation. 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
Explanation: The trusted agent execution/owner permissions are invalid. System Action: Processing stopped. User Response: Have your system administrator check the installation instructions for the client to ensure that the trusted agent permissions are set correctly. 0139 S DSM_RC_KILLED
Explanation: Processing stopped. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator.
996
IBM Tivoli Storage Manager: Messages
0145 S
DSM_RC_WOULD_BLOCK
Explanation: The trusted agent blocks the operation. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. 0146 S DSM_RC_TOO_SMALL
Explanation: The area for the include/exclude pattern is too small. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. 0147 S DSM_RC_UNCLOSED
Explanation: There is no closing bracket in the pattern. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. 0148 S DSM_RC_NO_STARTING_DELIMITER
Explanation: The include or exclude pattern must start with a directory delimiter. System Action: Processing stopped. User Response: Correct the syntax for the pattern. 0149 S DSM_RC_NEEDED_DIR_DELIMITER
Explanation: The include/exclude pattern has a ... without a beginning or ending directory delimiter. System Action: Processing stopped. User Response: Correct the syntax for the pattern. 0150 S DSM_RC_UNKNOWN_FILE_DATA_TYPE
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. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. 0151 S DSM_RC_BUFFER_OVERFLOW
Explanation: The data buffer overflowed. This is a programming failure and the client program ends. System Action: Processing stopped. User Response: Retry the operation. If the problem continues, contact your system administrator. 0154 E DSM_RC_NO_COMPRESS_MEMORY
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. System Action: Processing stopped. User Response: Free up extra storage for the operation to continue, or run the backup or archive process without compression enabled.
Appendix A. API Return Codes with Explanations
997
0155 T
DSM_RC_COMPRESS_GREW
Explanation: The size of the file after compressesion is greater than the size of the file before compressed. System Action: Even though the size of the file increased, the file is compressed. User Response: None. 0156 E DSM_RC_INV_COMM_METHOD
Explanation: You specified a communication method that is not supported. System Action: Processing stopped. User Response: Specify a valid communication interface for the ITSM client and your operating system. 0157 S DSM_RC_WILL_ABORT
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. 0158 E DSM_RC_FS_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. 0159 I DSM_RC_SKIPPED_BY_USER
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. System Action: File skipped. User Response: Verify the application sets the mountWait value correctly on dsmBeginGetData. 0160 E DSM_RC_TA_NOT_FOUND
Explanation: ITSM was unable to find the ITSM Trusted Agent module in the specified directory. The name of the ITSM Trusted Agent module is dsmtca. System Action: ITSM ends. User Response: Make sure the Trusted Agent module is in the directory specified by DSMI_DIR. 0161 E DSM_RC_TA_ACCESS_DENIED
Explanation: An attempt to access a system function has been denied. System Action: Processing stopped. User Response: Contact your system administrator. 0162 E DSM_RC_FS_NOT_READY
Explanation: The file system/drive was not ready for access. System Action: Processing stopped. User Response: Ensure that the drive is available to ITSM, and then retry the operation.
998
IBM Tivoli Storage Manager: Messages
0163 E
DSM_RC_FS_IS_BAD
Explanation: The drive was not available for access. A directory exists that does not have either a '.' or '..' entry. System Action: Processing stopped. User Response: Ensure that the drive is operational, and then retry the operation. If unsuccessful, have your service representative check the error log. 0164 E DSM_RC_FIO_ERROR
Explanation: An error was found while reading from or writing to the file. System Action: File or file system is skipped. 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. 0165 E DSM_RC_WRITE_FAILURE
Explanation: An error was found while writing to the file. System Action: File skipped. User Response: Check your system to ensure that it is operating properly. 0166 E DSM_RC_OVER_FILE_SIZE_LIMIT
Explanation: A file being restored or retrieved exceeds system set limits for this user. System Action: File skipped. User Response: Ensure that the system limits are set properly. 0167 E DSM_RC_CANNOT_MAKE
Explanation: The directory path for files being restored or retrieved cannot be created. System Action: File skipped. User Response: Ensure that you have the proper authorization to create the directory for file being restored or retrieved. Make sure that you have write access. 0168 E DSM_RC_NO_PASS_FILE
Explanation: The file containing the stored password for the specified server-name is unavailable. System Action: ITSM ends. User Response: The root user must set and store a new password. 0169 E DSM_RC_VERFILE_OLD
Explanation: Either the password is not stored locally, or it was changed at the server. System Action: ITSM prompts you for the password if ITSM is running in the foreground. User Response: If ITSM was running as a background process, issue any ITSM command from the foreground. Enter the password in answer to the prompt. Then try your background ITSM command again. 0173 E DSM_RC_INPUT_ERROR
Explanation: Unable to read commands entered from keyboard. ITSM cannot process your intended command. System Action: Processing stopped. User Response: Ensure that you are entering a correct command.
Appendix A. API Return Codes with Explanations
999
0174 E
DSM_RC_REJECT_PLATFORM_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: ITSM 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. 0175 E DSM_RC_TL_NOT_FILE_OWNER
Explanation: The file cannot be backed up because the client is not the file owner. System Action: ITSM skips the file. User Response: None. 0176 S DSM_RC_DBCS_IN_RANGE
Explanation: Only single-byte characters are allowed in an include/exclude list; you cannot use a double-byte character set (DBCS). System Action: Processing stopped. User Response: Remove the double-byte characters from the include/exclude list and retry the operation. 0177 S DSM_RC_UNMATCHED_QUOTE
Explanation: The quotes specified in the pattern are not the same and do not make a set. System Action: Processing stopped. User Response: Correct the pattern by using matching quotes in the syntax. 0184 E DSM_RC_TL_NOBCG
Explanation: The management class for this file does not have a backup copy group specified. This file will not be backed up. System Action: Processing stopped. User Response: Add a valid backup copy group to the management class, and then retry the operation. 0185 W DSM_RC_TL_EXCLUDED
Explanation: You tried to back up or migrate a file (file-name) that was specified to be excluded from backup. System Action: ITSM did not back up or migrate the file. User Response: Specify the file using the Include option and retry the operation. 0186 E DSM_RC_TL_NOACG
Explanation: The management class for this file does not have an archive copy group specified. This file will not be archived. System Action: Processing stopped. User Response: Add a valid archive copy group to the management class, and then retry the operation. 0187 E DSM_RC_PS_INVALID_ARCHMC
Explanation: You entered an invalid management class. System Action: ITSM is unable to do the requested operation. User Response: Retry the operation using a valid management class.
1000
IBM Tivoli Storage Manager: Messages
0188 S
DSM_RC_NO_PS_DATA
Explanation: Either no Active Policy Set data was found on the server or a fromnode option contained a nodename not found on the server. System Action: Processing stopped. User Response: See your system administrator. 0189 S DSM_RC_PS_INVALID_DIRMC
Explanation: An invalid management class was assigned to directories. System Action: Processing stopped. User Response: Have your service representative check the error log. 0190 S DSM_RC_PS_NO_CG_IN_DIR_MC
Explanation: The management class used for directories does not have a backup copy group. System Action: Processing stopped. User Response: Have your service representative check the error log. 0200 E DSM_RC_TCA_ATTACH_SHR_MEM_ERR
Explanation: An error has occurred while attaching the trusted agents shared memory. System Action: Return to caller. User Response: Stop application, check shared memory usage and retry the command. Read the tca.log file for the system error number. 0231 E DSM_RC_ABORT_MOVER_TYPE
Explanation: The specified Remote Mover type is unknown. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. 0232 E DSM_RC_ABORT_ITEM_IN_USE
Explanation: A request has been made to use a data 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. System Action: ITSM ended the current operation. User Response: Retry the operation at a later time. 0233 E DSM_RC_ABORT_LOCK_CONFLICT
Explanation: A required resource is in use by another command or process. System Action: ITSM ended the current operation. User Response: Retry the operation at a later time. 0234 E DSM_RC_ABORT_SRV_PLUGIN_COMM_ERROR
Explanation: Communication between a server plugin module and a NAS filer failed. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information.
Appendix A. API Return Codes with Explanations
1001
0235 E
DSM_RC_ABORT_SRV_PLUGIN_OS_ERROR
Explanation: A plugin module detected that a NAS filer is running an unsupported operating system or operating system level. System Action: ITSM ended the current operation. User Response: Contact your system administrator for more information. 0236E DSM_RC_ABORT_CRC_FAILED
Explanation: The server sent a CRC for a buffer. The client calculated a CRC for the same buffer. These did not match. The mismatch indicates a communication failure. System Action: In some cases, the client can indicate 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. 0237E DSM_RC_ABORT_INVALID_GROUP_ACTION
Explanation: An invalid operation was attempted on a logical group. System Action: The current operation stops. User Response: Retry a valid operation. 0238E DSM_RC_ABORT_DISK_UNDEFINED
Explanation: An operation was attempted on a remote disk that is not defined. System Action: The current operation stops. User Response: Define the proper remote disk. 0239E DSM_RC_ABORT_BAD_DESTINATION
Explanation: Input destination does not match expected destination. System Action: The current operation stops. User Response: Retry operation with proper destination. 0240E DSM_RC_ABORT_DATAMOVER_NOT_AVAILABLE
Explanation: Data mover is not available. System Action: The current operation stops. User Response: Retry operation with a proper Data mover. 0241E DSM_RC_ABORT_STGPOOL_COPY_CONT_NO
Explanation: Operation failed because the copy continue option was set to NO. System Action: The current operation stops. 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. 0242E DSM_RC_ABORT_RETRY_SINGLE_TXN
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 seperate txns.
1002
IBM Tivoli Storage Manager: Messages
0292 E
DSM_RC_TCA_FORK_FAILED
Explanation: An error has occurred starting the Trusted Communication Agent process; specifically, the fork() function has failed. System Action: ITSM ends. User Response: Probable system error. If the problem persists, restart the workstation. 0294 E DSM_RC_TCA_DIED
Explanation: The Trusted Communication Agent has terminated unexpectedly. System Action: ITSM ends. User Response: Check the error log for more information. Retry the activity. If the problem persists, contact your service representative. 0295 E DSM_RC_TCA_INVALID_REQUEST
Explanation: The Trusted Communication Agent has received an unknown request from the ITSM client. System Action: ITSM ends. User Response: Internal error. If the problem recurs, contact your service representative. 0296 E DSM_RC_TCA_NOT_ROOT
Explanation: An activity has been attempted that must be performed by the ITSM administrator (for example, open registration, filespace delete or password update). System Action: ITSM ends. User Response: If the activity is required, the administrator for this system must perform it. 0297 E DSM_RC_TCA_SEMGET_ERROR
Explanation: An error has occurred because the semaphores you are attempting to allocate have become insufficient. System Action: Processing ends. 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
Explanation: An error has occurred while attempting to set or wait on a semaphore. System Action: Processing ends. User Response: Probable system error. If the problem persists, restart the workstation. 0400 E DSM_RC_INVALID_OPT
Explanation: An invalid option was found. System Action: The system returns to the calling 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/QOPTITSM(APIOPT). 0405 E DSM_RC_NO_HOST_ADDR
Explanation: The TCPSERVERADDRESS for this server is not defined in the server name stanza in the system options file. System Action: ITSM initialization fails and the program ends.
Appendix A. API Return Codes with Explanations
1003
User Response: See the ITSM administrator for your system, and make sure that the server to which you are trying to connect, has a valid TCPSERVERADDRESS defined in the system options file. 0406 S DSM_RC_NO_OPT_FILE
Explanation: The options file specified by file-name cannot be found. System Action: The ITSM client ends. User Response: See if you have the environment variable DSM_CONFIG (or DSMI_CONFIG for the API) set, which explicitly identifies the ITSM options file. ( You can do this by entering the SET command at your system.) If this environment variable is set, ensure the file indicated by the variable exists. If it is not set, then ITSM looks for the file dsm.opt in the current directory. If neither of these cases is met, you receive this error message. 0408 E DSM_RC_MACHINE_SAME
Explanation: The NODENAME defined in the options file cannot be the same as the system HostName. System Action: Initialization fails and the program ends. User Response: See your system administrator or the root user. 0409 E DSM_RC_INVALID_SERVER
Explanation: The system options file does not contain the SERVERNAME option. System Action: ITSM initialization fails and the program ends. User Response: See the ITSM administrator for your system, and make sure that the system options file contains the server name. 0410 E DSM_RC_INVALID_KEYWORD
Explanation: An invalid option keyword was found in the dsmInit configuration file, the option string, dsm.sys, or dsm.opt. System Action: The system returns to the calling 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. 0411 S DSM_RC_PATTERN_TOO_COMPLEX
Explanation: The include or exclude pattern issued is too complex to be accurately interpreted by ITSM. System Action: Processing stopped. User Response: Recode the include or exclude pattern as shown in one of the examples in the appropriate Using the Backup-Archive Client book for the particular operating system. 0412 S DSM_RC_NO_CLOSING_BRACKET
Explanation: The include or exclude pattern is incorrectly constructed. The closing bracket is missing. System Action: Processing stopped. User Response: Correct the syntax for the pattern. 0600 E DSM_RC_DUP_LABEL
Explanation: The selected drive has a duplicate volume label. Because ITSM 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: ITSM cannot select the drive. User Response: If the volume needs to be available to the system, exit ITSM, and assign a volume label to the drive. Restart ITSM and retry the operation.
1004
IBM Tivoli Storage Manager: Messages
0601 E
DSM_RC_NO_LABEL
Explanation: The selected drive does not have a label. System Action: ITSM 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. 0610 E DSM_RC_NLS_CANT_OPEN_TXT
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). System Action: The system returns to the calling 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 . 0611 E DSM_RC_NLS_CANT_READ_HDR
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). System Action: The system returns to the calling procedure. User Response: Install the message text file again. 0612 E DSM_RC_NLS_INVALID_CNTL_REC
Explanation: The system is unable to use the message 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). System Action: The system returns to the calling procedure. User Response: Install the message text file again. 0613 E DSM_RC_NLS_INVALID_DATE_FMT
Explanation: An invalid value is specified for DATEFORMAT. System Action: The system returns to the calling procedure. User Response: Specify a valid value. 0614 E DSM_RC_NLS_INVALID_TIME_FMT
Explanation: An invalid value is specified for TIMEFORMAT. System Action: The system returns to the calling procedure. User Response: Specify a valid value. 0615 E DSM_RC_NLS_INVALID_NUM_FMT
Explanation: An invalid value is specified for NUMBERFORMAT. System Action: The system returns to the calling procedure. User Response: Specify a valid value. 0620 E DSM_RC_LOG_CANT_BE_OPENED
Explanation: The system is unable to open the error log file. System Action: The system returns to the calling procedure.
Appendix A. API Return Codes with Explanations
1005
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. 0621 E DSM_RC_LOG_ERROR_WRITING_TO_LOG
Explanation: There was an error writing to the log file. System Action: The system returns to the calling procedure. 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. 0622 E DSM_RC_LOG_NOT_SPECIFIED
Explanation: The system is unable to open the error log file. System Action: The system returns to the calling procedure. 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. 0927 E DSM_RC_NOT_ADSM_AUTHORIZED
Explanation: User must be a ITSM authorized user to perform this action. User is not password authorized and this action requires authorization. System Action: Processing stopped. 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). 961 E DSM_RC_DIRECT_STORAGE_AGENT_UNSUPPORTED
Explanation: You cannot connect directly to the Storage Agent. System Action: Processing stopped. 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
Explanation: ITSM 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. System Action: Processing stopped. User Response: Add the long namespace support to the volume or rename(remove) the corresponding server filespace. 2000 E DSM_RC_NULL_OBJNAME
Explanation: There is no value provided for the object name pointer. System Action: The system returns to the calling procedure. User Response: Provide an address for the dsmObjName structure. 2001 E DSM_RC_NULL_DATABLKPTR
Explanation: There is no value provided for the data block pointer. System Action: The system returns to the calling procedure. User Response: Provide an address for the DataBlk structure.
1006
IBM Tivoli Storage Manager: Messages
2002 E
DSM_RC_NULL_MSG
Explanation: The message parameter for dsmRCMsg is a NULL pointer. System Action: The system returns to the calling procedure. User Response: Allocate enough space for the message parameter. 2004 E DSM_RC_NULL_OBJATTRPTR
Explanation: There is no value provided for the object attribute pointer. System Action: The system returns to the calling procedure. User Response: Provide an address for the ObjAttr structure. 2006 E DSM_RC_NO_SESS_BLK
Explanation: The server did not respond with the session information. System Action: The system returns to the calling procedure. User Response: Verify the server status. 2007 E DSM_RC_NO_POLICY_BLK
Explanation: The server did not respond with the policy information. System Action: The system returns to the calling procedure. User Response: Verify the server policy definitions. 2008 E DSM_RC_ZERO_BUFLEN
Explanation: The value for the dataBlk bufferLen is zero. System Action: The system returns to the calling procedure. User Response: Provide a non-zero value for the bufferLen. 2009 E DSM_RC_NULL_BUFPTR
Explanation: There is no value provided for the dataBlk bufferPtr. System Action: The system returns to the calling procedure. User Response: Provide an address for the bufferPtr. 2010 E DSM_RC_INVALID_OBJTYPE
Explanation: The value for the objType is invalid. System Action: The system returns to the calling 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
Explanation: The dsmEndTxn vote is invalid. System Action: The system returns to the calling procedure. User Response: The vote must be DSM_VOTE_COMMIT or DSM_VOTE_ABORT.
Appendix A. API Return Codes with Explanations
1007
2012 E
DSM_RC_INVALID_ACTION
Explanation: The dsmUpdateFS or dsmUpdateObj action is invalid. System Action: The system returns to the calling 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
Explanation: The system encountered an error in the API internals. System Action: The system returns to the calling 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
Explanation: The repository type is invalid. System Action: The system returns to the calling 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
Explanation: The filespace name is invalid. System Action: The system returns to the calling procedure. User Response: Filespace name should start with the directory delimiter. 2017 E DSM_RC_INVALID_OBJNAME
Explanation: The object name is invalid because of an empty string or there is no leading delimiter. System Action: The system returns to the calling procedure. User Response: Verify the format of the dsmObjName full path. 2018 E DSM_RC_INVALID_LLNAME
Explanation: The low level qualifier for the object name is invalid. System Action: The system returns to the calling procedure. User Response: Start the low level qualifier of the object name with the directory delimiter. 2019 E DSM_RC_INVALID_OBJOWNER
Explanation: The object owner must be either the root user, or the object owner must be the same as the session owner. System Action: The system returns to the calling procedure. User Response: Verify the session owner and object owner.
1008
IBM Tivoli Storage Manager: Messages
2020 E
DSM_RC_INVALID_ACTYPE
Explanation: The dsmBindMC sendType is invalid. System Action: The system returns to the calling procedure. User Response: The sendType must be one of the following: stBackup stArchive stBackupMountWait stArchiveMountWait 2021 E DSM_RC_INVALID_RETCODE
Explanation: The dsmRC parameter for dsmRCMsg is an unsupported return code. System Action: The system returns to the calling procedure. User Response: Specify a valid value. 2022 E DSM_RC_INVALID_SENDTYPE
Explanation: The dsmSendObj sendType is invalid. System Action: The system returns to the calling procedure. User Response: The sendType must be one of the following: stBackup stArchive stBackupMountWait stArchiveMountWait 2023 E DSM_RC_INVALID_PARAMETER
Explanation: The dsmDeleteObj delType is invalid. System Action: The system returns to the calling procedure. User Response: The delType must be dtBackup or dtArchive. 2024 E DSM_RC_INVALID_OBJSTATE
Explanation: The query Backup objState is invalid. System Action: The system returns to the calling procedure. User Response: The qryBackupData.objState must be one of the following: DSM_ACTIVE DSM_INACTIVE DSM_ANY_MATCH 2025 E DSM_RC_INVALID_MCNAME
Explanation: A query or send operation is unable to find the management class name. System Action: The system returns to the calling procedure. User Response: Verify the management class name.
Appendix A. API Return Codes with Explanations
1009
2026 E
DSM_RC_INVALID_DRIVE_CHAR
Explanation: The drive letter is not an alphabetic character. This return code is valid on Microsoft Windows only. System Action: The system returns to the calling procedure. User Response: Verify that the drive designation is an alphabetic character. The referenced field is dsmDosFSAttrib.driveLetter. 2027 E DSM_RC_NULL_FSNAME
Explanation: There is no value provided for the Register Filespace name. System Action: The system returns to the calling procedure. User Response: Provide a filespace name on dsmRegisterFS. 2028 E DSM_RC_INVALID_HLNAME
Explanation: The high level qualifier for the object name is invalid. System Action: The system returns to the calling procedure. User Response: High level qualifier of the object name should start with the directory delimiter. 2029 E DSM_RC_NUMOBJ_EXCEED
Explanation: The number of objects (numObjId) specified on the dsmBeginGetData call exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ. System Action: The system returns to the calling 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. 2030 E DSM_RC_NEWPW_REQD
Explanation: There is no value provided for new password. System Action: The system returns to the calling procedure. User Response: Provide a new password on dsmChangePW. 2031 E DSM_RC_OLDPW_REQD
Explanation: There is no value provided for old password. System Action: The system returns to the calling procedure. User Response: Provide an old password on dsmChangePW. 2032 E DSM_RC_NO_OWNER_REQD
Explanation: PASSWORDACCESS=generate establishes a session with the current login user as the owner. System Action: The system returns to the calling procedure. User Response: When using PASSWORDACCESS=generate, set clientOwnerNameP to NULL. 2033 E DSM_RC_NO_NODE_REQD
Explanation: PASSWORDACCESS=generate establishes a session with the current hostname as the node. System Action: The system returns to the calling procedure. User Response: When using PASSWORDACCESS=generate, set clientNodeNameP to NULL.
1010
IBM Tivoli Storage Manager: Messages
2034 E
DSM_RC_KEY_MISSING
Explanation: The key file for Tivoli Storage Manager data protection application client for Oracle cannot be found. System Action: The system returns to the calling procedure. User Response: Ensure that you have ordered the Tivoli Storage Manager data protection application client which contains TDP for Oracle, and install the key file. 2035 E DSM_RC_KEY_BAD
Explanation: The key file content for Tivoli Storage Manager data protection application client for Oracle is invalid. System Action: The system returns to the calling procedure. User Response: Ensure that you have ordered the Tivoli Storage Manager data protection application client which contains the TDP for Oracle, and install the key file. 2041 E DSM_RC_BAD_CALL_SEQUENCE
Explanation: The sequence of calls is invalid. System Action: The system returns to the calling procedure. User Response: Verify the transaction call sequence. 2050 E DSM_RC_WILDCHAR_NOTALLOWED
Explanation: On dsmSendObj, wildcards are not allowed for the objName. System Action: The system returns to the calling procedure. User Response: Provide a fs, hl, and ll on the dsmObjName. 2060 E DSM_RC_FSNAME_NOTFOUND
Explanation: The filespace to delete cannot be found. System Action: The system returns to the calling procedure. User Response: Verify the filespace name. 2061 E DSM_RC_FS_NOT_REGISTERED
Explanation: On dsmSendObj, dsmDeleteObj, or dsmUpdateFS, the filespace is not registered. System Action: The system returns to the calling procedure. User Response: Verify the filespace name. 2062 W DSM_RC_FS_ALREADY_REGED
Explanation: On dsmRegisterFS the filespace is already registered. System Action: The system returns to the calling procedure. User Response: Verify the filespace name. 2063 E DSM_RC_OBJID_NOTFOUND
Explanation: On dsmBeginGetData, the objID is NULL. System Action: The system returns to the calling procedure. User Response: Verify the following: The dsmGetList is not NULL. Each objID is not NULL.
Appendix A. API Return Codes with Explanations
1011
The dsmGetList numObjId is not zero. 2064 E DSM_RC_WRONG_VERSION
Explanation: On dsmInit the caller's API version has a higher value than the ITSM library version. System Action: The system returns to the calling procedure. User Response: Install the latest ITSM API library and trusted agent module. 2065 E DSM_RC_WRONG_VERSION_PARM
Explanation: The caller's structure version is different than the ITSM library version. System Action: The system returns to the calling 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
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. System Action: The system returns to the calling procedure. User Response: Issue dsmEndTxn and start a new transaction session. 2080 E DSM_RC_OBJ_EXCLUDED
Explanation: The backup or archive object is excluded from processing. System Action: The system returns to the calling procedure. User Response: Verify the objName and Exclude lists. 2081 E DSM_RC_OBJ_NOBCG
Explanation: The backup object does not have a copy group. System Action: The system returns to the calling procedure. User Response: Verify server policy definitions. 2082 E DSM_RC_OBJ_NOACG
Explanation: The archive object does not have a copy group. System Action: The system returns to the calling procedure. User Response: Verify server policy definitions. 2090 E DSM_RC_APISYSTEM_ERROR
Explanation: Memory used by the ITSM API has been corrupted. System Action: The system returns to the calling procedure. User Response: Retry the operation. If the problem continues, contact your system administrator or service representative.
1012
IBM Tivoli Storage Manager: Messages
2100 E
DSM_RC_DESC_TOOLONG
Explanation: The sendObj Archive description is too long. System Action: The system returns to the calling procedure. User Response: The sndArchiveData.descr string must be less than or equal to DSM_MAX_DESCR_LENGTH. 2101 E DSM_RC_OBJINFO_TOOLONG
Explanation: The sendObj ObjAttr.objInfo is too long. System Action: The system returns to the calling procedure. User Response: The objInfo field must be less than or equal to DSM_MAX_OBJINFO_LENGTH. 2102 E DSM_RC_HL_TOOLONG
Explanation: The sendObj dsmObjName.hl is too long. System Action: The system returns to the calling procedure. User Response: The hl field must be less than or equal to DSM_MAX_HL_LENGTH. 2103 E DSM_RC_PASSWD_TOOLONG
Explanation: The dsmChangePW password is too long. System Action: The system returns to the calling procedure. User Response: The password field must be less than or equal to DSM_MAX_VERIFIER_LENGTH. 2104 E DSM_RC_FILESPACE_TOOLONG
Explanation: The sendObj dsmObjName.fs is too long. System Action: The system returns to the calling procedure. User Response: The fs field must be less than or equal to DSM_MAX_FS_LENGTH. 2105 E DSM_RC_LL_TOOLONG
Explanation: The sendObj dsmObjName.ll is too long. System Action: The system returns to the calling procedure. User Response: The ll field must be less than or equal to DSM_MAX_LL_LENGTH. 2106 E DSM_RC_FSINFO_TOOLONG
Explanation: On RegisterFS or UpdateFS the fsAttr's fsInfo is too long. System Action: The system returns to the calling procedure. User Response: The fsInfo field must be less than or equal to DSM_MAX_FSINFO_LENGTH. 2107 E DSM_RC_SENDDATA_WITH_ZERO_SIZE
Explanation: You cannot send data for an object with size estimate = 0. System Action: The system returns to the calling procedure. User Response: Set size estimate greater than 0 in dsmSendObj.
Appendix A. API Return Codes with Explanations
1013
2110 E
DSM_RC_INVALID_ACCESS_TYPE
Explanation: The dsmSetAccess accessType is invalid. System Action: The system returns to the calling procedure. User Response: The accessType must be one of the following: atBackup atArchive 2111 E DSM_RC_QUERY_COMM_FAILURE
Explanation: An unexpected communications error occurred during an object query to the server. System Action: Processing stopped. 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. 2112 E DSM_RC_NO_FILES_BACKUP
Explanation: You tried to set access to files when no files for the specified filename, drive or file system were previously backed up. System Action: Processing stopped. User Response: Ensure that the correct drive or file system was specified and that files are backed up for you to set access. 2113 E DSM_RC_NO_FILES_ARCHIVE
Explanation: You tried to set access to files when no files for the specified filename, drive or file system were previously archived. System Action: Processing stopped. User Response: Ensure that the correct drive or file system was specified and that files are archived for you to set access. 2114 E DSM_RC_INVALID_SETACCESS
Explanation: None. System Action: Processing stopped. User Response: Enter the SET ACCESS command using the correct syntax. 2120 E DSM_RC_STRING_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 User Response: None. 2200 I DSM_RC_MORE_DATA
Explanation: On dsmGetNextQObj or dsmGetData there is more available data. System Action: The system returns to the calling procedure. User Response: Call the function again.
1014
IBM Tivoli Storage Manager: Messages
2210 E
DSM_RC_BUFF_TOO_SMALL
Explanation: The dataBlk buffer is too small for the query response. System Action: The system returns to the calling procedure. User Response: On dsmGetNextQObj ensure that the dataBlk buffer is at least as big as the query response structure. 2228 E DSM_RC_NO_API_CONFIGFILE
Explanation: The configuration file specified on dsmInit cannot be opened. System Action: The system returns to the calling procedure. User Response: Verify the file name. 2229 E DSM_RC_NO_INCLEXCL_FILE
Explanation: The Include/Exclude definition file was not found. System Action: The system returns to the calling procedure. User Response: Verify the file name on the Inclexcl option. 2230 E DSM_RC_NO_SYS_OR_INCLEXCL
Explanation: Either the dsm.sys file was not found, or the Inclexcl file specified in dsm.sys was not found. System Action: The system returns to the calling 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. 2231 E DSM_RC_REJECT_NO_POR_SUPPORT
Explanation: The ITSM server specified by the user does not support partial object retrieve. System Action: The system returns to the calling procedure. User Response: Specify a ITSM server which supports the partial object retrieve function. 2300 E DSM_RC_NEED_ROOT
Explanation: Only a UNIX root user can execute dsmChangePW or dsmDeleteFS. System Action: The system returns to the calling procedure. User Response: Run this program as a root user. 2301 E DSM_RC_NEEDTO_CALL_BINDMC
Explanation: You must issue dsmBindMC before dsmSendObj. System Action: The system returns to the calling procedure. User Response: Modify your program. 2302 I DSM_RC_CHECK_REASON_CODE
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. System Action: The system returns to the calling procedure. User Response: Check the reason field for the code which explains why the transaction has been aborted.
Appendix A. API Return Codes with Explanations
1015
2400 E
DSM_RC_ALMGR_OPEN_FAIL
Explanation: The license file was not found, or could not be opened because of permissions or the file is corrupted. System Action: The system returns to the calling procedure. User Response: Check permissions on file. See if the license file is in the correct place. 2401 E DSM_RC_ALMGR_READ_FAIL
Explanation: The license file was not found, or could not be opened because of permissions, or the file is corrupted. System Action: The system returns to the calling procedure. User Response: Check permissions on file. See if the license file is in the correct place. 2402 E DSM_RC_ALMGR_WRITE_FAIL
Explanation: The license file was not found, or could not be opened because of permissions or the file is corrupted. System Action: The system returns to the calling procedure. User Response: Check permissions on file. See if license file is in the correct place. 2403 E DSM_RC__ALMGR_DATA_FMT
Explanation: The license file is not valid. System Action: The system returns to the calling procedure. User Response: User needs to obtain a new license. 2404 E DSM_RC_ALMGR_CKSUM_BAD
Explanation: The registration string is not valid. System Action: The system returns to the calling procedure. User Response: User needs to obtain a new license. 2405 E DSM_RC_ALMGR_TRIAL_EXPRD
Explanation: The registration string is not valid. System Action: The system returns to the calling procedure. User Response: User needs to obtain a new license. 2410 E DSM_RC_ORC_INVALID_MODE
Explanation: Invalid mode passed by Oracle. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. 2411 E DSM_RC_ORC_NULL_FILENAME
Explanation: Null filename passed by Oracle. System Action: The system returns to the calling procedure. User Response: Contact your system administrator.
1016
IBM Tivoli Storage Manager: Messages
2412 E
DSM_RC_ORC_WRONG_BLKSIZE
Explanation: Wrong Block Size System Action: The system returns to the calling procedure. User Response: Contact your system administrator. 2413 E DSM_RC_ORC_OBJ_EXISTS
Explanation: Backup or Restore Object already exists. System Action: The system returns to the calling procedure. User Response: If backing up an object, be sure to generate a unique object name. 2414 E DSM_RC_ORC_NOTSAME_HANDLE
Explanation: The handle passed from Oracle is not the same handle that ITSM passed back. System Action: The system returns to the calling procedure. User Response: Contact your system administrator. 2415 E DSM_RC_ORC_END_OF_FILE
Explanation: End of file reached. System Action: The system returns to the calling procedure. User Response: None 2416 E DSM_RC_ORC_WRONG_RDSTATE
Explanation: The operation must be in READ state. System Action: The system returns to the calling procedure. User Response: Contact your service representative. 2417 E DSM_RC_ORC_LOWER_APIVER
Explanation: Runtime API is lower than compile time API. System Action: The system returns to the calling procedure. User Response: Use the WHAT command to find out the compile time API level. Obtain the same or higher level of API library. 2418 E DSM_RC_ORC_WRONG_WRTSTATE
Explanation: The operation must be in WRITE state. System Action: The system returns to the calling procedure. User Response: Contact your service representative. 2419 E DSM_RC_ORC_INVALID_FLAG
Explanation: Invalid flag passed from Oracle. System Action: The system returns to the calling procedure. User Response: Contact your system administrator.
Appendix A. API Return Codes with Explanations
1017
4600 E
DSM_RC_CLUSTER_INFO_LIBRARY_NOT_LOADED
Explanation: The HACMP Cluster Information Daemon must be started in order to specify the CLUSTERNODE option. System Action: Processing ends. User Response: Start the HACMP Cluster Information Dameon. 4601 E DSM_RC_CLUSTER_LIBRARY_INVALID
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. System Action: Processing ends. User Response: Ensure that the latest cluster software is installed on the system. 4602 E DSM_RC_CLUSTER_LIBRARY_NOT_LOADED
Explanation: The load library that the operating systems provides to obtain the cluster name is not available on this system. System Action: Processing ends. User Response: Ensure that the cluster software is installed on the system. 4603 E DSM_RC_CLUSTER_NOT_MEMBER_OF_CLUSTER
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. System Action: Processing ends. User Response: Ensure that the cluster software is 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
Explanation: The cluster service has not been enabled on this system. System Action: Processing ends. User Response: Enable the cluster service on the system. 4605 E DSM_RC_CLUSTER_NOT_SUPPORTED
Explanation: This option is not supported on this system. System Action: Processing ends. User Response: Disable the CLUSTERNODE option in the local options file. 4606 E DSM_RC_CLUSTER_UNKNOWN_ERROR
Explanation: An unknown error occurred while the program was trying to obtain the cluster name from the cluster services. System Action: Processing ends. User Response: Contact your system administrator for more information.
1018
IBM Tivoli Storage Manager: Messages
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 PASE, ensure that there is sufficient paging space. v For VM, increase the size of the servers virtual machine. This requires that the default storage size be updated in the servers CP directory entry. v For OS/390 and z/OS, increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server. A minimum size of 128MB is recommended for 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.
Copyright IBM Corp. 1993, 2004
1019
1020
IBM Tivoli Storage Manager: Messages
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 OP Description 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 1025 for a list of operation codes. 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 1022 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. 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 1026 also provides additional information on the common values of ASC and ASCQ.
CC
KEY
Copyright IBM Corp. 1993, 2004
1021
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 1025 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 200 201 202 203 Hexadecimal X'C8' X'C9' X'CA' X'CB' Description The device indicated a failure condition, but sense data was unavailable. Device driver failure The device EEPROM failed. Manual intervention required Recommended Action Retry the failing operation. Contact Tivoli Storage Manager support. The device should be tested or serviced. Correct the problem on the device. This may be a stuck tape, dirty heads or a jammed library arm. No action necessary Check for loose cables, bent pins, bad cables, bad SCSI adaptors, improper termination or bad terminators. Check for loose cables, bent pins, bad cables, bad SCSI adaptors, improper termination or bad terminators. Ensure the device is on and ready. Ensure the DEFINE DRIVE and DEFINE DEVCLASS have been issued properly. Contact Tivoli Storage Manager support. Check the microcode level of the drive. Call the drives manufacturer and request latest level. Retry the failing operation.
204 205
X'CC' X'CD'
Recovered from an I/O error; for your information only SCSI adapter failure
206
X'CE'
General SCSI failure
207
X'CF'
Device is not in a state capable of performing request
208 209
X'D0' X'D1'
Command aborted Device microcode failure detected
210
X'D2'
The device was reset due to device power-up, SCSI bus reset, or manual tape load/eject. The SCSI bus was busy.
211
X'D3'
Ensure the SCSI ids are correctly assigned to the correct device, and the device is not being accessed by another process.
1022
IBM Tivoli Storage Manager: Messages
Completion Code Values for Media Changers
The following table shows the completion code values, in decimal and hexadecimal numbers, for the media changers. 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 2. Completion Code Values for Media Changers Decimal 300 301 Hexadecimal X'12C' X'12D' Description Cartridge entry/exit error Cartridge load failure Recommended Action Check the entry/exit ports for a jammed volume. Check the drive for jammed volumes. On AIX, display the errpt to check for hardware errors. Check the drive for jammed volumes. On AIX, display the errpt to check for hardware errors. Ensure the carousel is correctly in place and the door is shut. On AIX, display the errpt to check for hardware errors. Ensure the heads have been cleaned. On AIX, display the errpt to check for hardware errors. Ensure the heads have been cleaned. On AIX, display the errpt to check for hardware errors. Contact Tivoli Storage Manager support. Contact Tivoli Storage Manager support. Ensure that there are no jammed volumes. It is possible that the library audit is failing due to hardware errors. On AIX, display the errpt to check for hardware errors. Check for jammed volumes. Ensure the volumes have not been rearranged. If the library is not actually full, perform an AUDIT LIBRARY. Contact Tivoli Storage Manager support. Ensure that nothing is jammed in the slot. Ensure the volume is not jammed in the slot and that the volumes have not been rearranged. If problem persists, perform an AUDIT LIBRARY.
302
X'12E'
Cartridge in failed drive
303 304 305
X'12F' X'130' X'131'
Carousel not loaded Changer failure Drive failure
306
X'132'
Drive or media failure
307 308 309
X'133' X'134' X'135'
Entry/exit failure Entry/exit port not present Library audit error
310
X'136'
Library full
311 312 313
X'137' X'138' X'139'
Media export Slot failure Slot or media failure
314
X'13A'
The source slot or drive was empty in an Ensure the volumes have not been attempt to move a volume. rearranged. If problem persists, perform an AUDIT LIBRARY.
Appendix C. I/O Error Code Descriptions
1023
Table 2. Completion Code Values for Media Changers (continued) Decimal 315 Hexadecimal X'13B' Description The destination slot or drive was full in an attempt to move a volume. Recommended Action Ensure the volumes have not been rearranged, or that a volume is not stuck in the drive. If problem persists, perform AUDIT LIBRARY. Contact Tivoli Storage Manager support. Ensure the volumes have not been rearranged, or that a volume is not stuck in the drive. If problem persists, perform AUDIT LIBRARY. Contact Tivoli Storage Manager support. Ensure the volumes have not been rearranged. If problem persists, perform AUDIT LIBRARY. Perform AUDIT LIBRARY. Contact Tivoli Storage Manager support. Contact Tivoli Storage Manager support.
316 317
X'13C' X'13D'
Cleaner cartridge installed Media not ejected
318 319
X'13E' X'13F'
I/O port not configured First destination empty
320 321 322
X'140' X'141' X'142'
No inventory information Read element status mismatch Initialize range failed
Completion Code Values for Tape and Optical Drives
The following table shows the completion code values, in decimal and hexadecimal numbers, for tape and optical drives. 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 3. Completion Code Values for Tape and Optical Drives Decimal 400 402 Hexadecimal X'190' X'192' Description Physical end of media encountered Media corrupted Recommended Action Ensure the heads are clean on the drive. Ensure the heads are clean and the media is not physically damaged or too old. Ensure the heads are clean and the media is not physically damaged or too old. Ensure the correct length and type of media is being used. Internal server error. Contact Tivoli Storage Manager support. Ensure the volume is not write protected. Clean the drive heads with a cleaning cartridge that is not too old. Clean the heads and ensure the media is not physically damaged or too old. Retry the failing operation.
403
X'193'
Media failure
404 406 407 408 409 410
X'194' X'196' X'197' X'198' X'199' X'19A'
Media incompatibility Sector requested is invalid. Write protect Clean the media and the drive. Media fault Cleaning complete
1024
IBM Tivoli Storage Manager: Messages
Table 3. Completion Code Values for Tape and Optical Drives (continued) Decimal 412 Hexadecimal X'19C' Description Media not present in drive Recommended Action Ensure the media is correctly positioned in the drive. If problem persists, perform an AUDIT LIBRARY. Clean the drive heads. Internal server error. Contact Tivoli Storage Manager support. Ensure the heads are clean. On AIX, display the errpt to check for hardware errors. Contact Tivoli Storage Manager support. Contact Tivoli Storage Manager support. Clean the drive and media. Ensure the heads have been cleaned. Check operating system error logs for hardware errors. Clean the tape drive. Check operating system error logs for hardware errors. Possible bad media.
414 415 416
X'19E' X'19F' X'1A0'
Erase failure Attempted to overwrite written WORM media An incorrect length block was read.
417 418 419 420
X'1A1' X'1A2' X'1A2' X'1A4'
Open read only Open write only Media scan failed Logical write protect
422 423
X'1A6' X'1A7'
Cleaning required Optical media error
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 X'6D31' X'6D32' X'6D34' X'6D37' X'6D38' X'6D38' X'6D39' Name MTIOCLM MTIOCLDM MTIOCLSVC MTIOCLQ MTIOCLQMID MTIOCLQMID MTIOCLSDC Description Mount a volume on a specified drive. Demount a volume on a specified drive. Change the category of a specified volume. Return information about the tape library and its contents. Query the status of the operation for a given message ID. Query the status of the operation for a given message ID. Assign a category to the automatic cartridge loader for a specified device.
Appendix C. I/O Error Code Descriptions
1025
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 1029. See server message ANR8300E or ANR8302E for the recommended action. The following table provides descriptions for common values of the ASC and ASCQ codes. Each value has a prefix of 0x, which indicates that it is a hexadecimal constant.
Table 5. Common Values for ASC and ASCQ Codes ASC 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x02 0x03 0x03 0x03 0x04 0x04 0x04 0x04 0x04 0x05 0x06 0x07 0x08 0x08 0x08 0x09 0x0A 0x0C 0x11 0x11 0x11 0x11 0x11 0x11 ASCQ 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x00 0x00 0x01 0x02 0x00 0x01 0x02 0x03 0x04 0x00 0x00 0x00 0x00 0x01 0x02 0x00 0x00 0x00 0x00 0x01 0x02 0x03 0x08 0x09 Description No additional sense Filemark detected End-of-medium detected Setmark detected Beginning of medium End of data I/O process terminated No seek complete Device write fault No write current Excessive write errors Logical unit not ready Becoming ready Not ready, initializing command required Not ready, manual intervention required Not ready, formatting No response to select No reference position found Multiple devices selected Communication failure Communication timeout Communication parity error Track following error Error log overflow Write error Unrecovered read error Read retries exhausted Error too long to correct Multiple read errors Incomplete block read No gap found
1026
IBM Tivoli Storage Manager: Messages
Table 5. Common Values for ASC and ASCQ Codes (continued) ASC 0x11 0x14 0x14 0x14 0x14 0x14 0x15 0x15 0x15 0x17 0x17 0x17 0x17 0x18 0x1A 0x1B 0x20 0x21 0x21 0x24 0x25 0x26 0x26 0x26 0x26 0x27 0x28 0x28 0x29 0x2A 0x2A 0x2A 0x2B 0x2C 0x2D 0x2F 0x30 0x30 0x30 0x30 ASCQ 0x0A 0x00 0x01 0x02 0x03 0x04 0x00 0x01 0x02 0x00 0x01 0x02 0x03 0x00 0x00 0x00 0x00 0x00 0x01 0x00 0x00 00 0x01 0x02 0x03 0x00 0x00 0x01 0x00 0x00 0x01 0x02 0x00 0x00 0x00 0x00 0x00 0x01 0x02 0x03 Description Miscorrected error Recorded entity not found Record not found Filemark/setmark not found End-of-data not found Block sequence error Random positioning error Mechanical positioning error Read positioning error No error correction applied Recovered with retries Recovered with positive head offset Recovered with negative head offset ECC applied Parameter list length error Synchronous data transfer error Invalid operation code Block out of range Invalid element address Invalid field in CDB LUN not supported Invalid field in parameter list Parameter not supported Parameter value invalid Threshold parameters not supported Write protected Not-ready to ready Import/export element accessed Power-on, reset, bus reset Parameters changed Mode parameters changed Log parameters changed Copy cannot execute Command sequence error Overwrite error on update Command cleared by initiator Incompatible media Media unknown format Media incompatible format Cleaning cartridge installed
Appendix C. I/O Error Code Descriptions
1027
Table 5. Common Values for ASC and ASCQ Codes (continued) ASC 0x31 0x33 0x37 0x39 0x3A 0x3B 0x3B 0x3B 0x3B 0x3B 0x3B 0x3D 0x3E 0x3F 0x3F 0x3F 0x3F 0x43 0x44 0x45 0x46 0x47 0x48 0x49 0x4A 0x4B 0x4C 0x4E 0x50 0x50 0x50 0x51 0x52 0x53 0x53 0x53 0x5A 0x5A 0x5A 0x5A ASCQ 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x02 0x08 0x0D 0x0E 0x00 0x00 0x00 0x01 0x02 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x02 0x00 0x00 0x00 0x01 0x02 0x00 0x01 0x02 0x03 Description Media format corrupted Tape length error Rounded parameter Saving parameters not supported Medium not present Sequential positioning error Positioning error at BOT Positioning error at EOT Reposition error Medium destination element full Medium source element empty Invalid bits in message LUN not self-configured Operating conditions changed Microcode has been changed Changed operating definition Inquiry data has changed Message error Internal target failure Select/reselect failure Unsuccessful soft reset SCSI parity error Initiator detected message received Invalid message error Command phase error Data phase error LUN failed self-configuration Overlapped commands attempt Write append error Write append position error Position error (timing) Erase failure Cartridge fault Load/media eject failed Unload tape failure Media removal prevented Operator state changed Operator media removal Operator write protect Operator write permit
1028
IBM Tivoli Storage Manager: Messages
Table 5. Common Values for ASC and ASCQ Codes (continued) ASC 0x5B 0x5B 0x5B 0x5B ASCQ 0x00 0x01 0x02 0x03 Description Log exception Threshold condition met Log counter at maximum 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.
Appendix C. I/O Error Code Descriptions
1029
1030
IBM Tivoli Storage Manager: Messages
Appendix D. Device Errors in AIX Version 4 System Error Log
Tivoli Storage Manager logs certain device errors in the AIX Version 4 system error log. This section provides a brief description of the device error. It also provides the detail data and a description of the data. For a detailed description of the AIX error logging facility and of the information contained within an error report, refer to AIX Version 4 Problem Solving Guide and Reference. DEVICE ERROR and ERROR DESCRIPTION ADSM_DD_LOG1 (0xAC3AB953) DEVICE DRIVER SOFTWARE ERROR This error is logged by the ADSM device driver when a problem is suspected in the ADSM device driver software. For example, if the ADSM device driver issues a SCSI I/O command with an illegal operation code the command fails and the error is logged with this identifier. Report this error immediately to ADSM support personnel. Detail Data: Sense Data The sense data consists of information that can determine the cause of the error. All data in the error entry should be reported to ADSM support personnel. ADSM_DD_LOG2 (0x5680E405) HARDWARE/COMMAND-ABORTED ERROR This error is logged by the ADSM device driver when the device reports a particular hardware error or command-aborted error in response to a SCSI I/O command. Detail Data: Sense Data 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. Detail Data: Sense Data 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
Copyright IBM Corp. 1993, 2004
1031
device was opened and then closed again. Logging this event indicates that the activity occurred and that the library inventory may have been changed. Detail Data: Sense Data 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. 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_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. Detail Data: Sense Data 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.
1032
IBM Tivoli Storage Manager: Messages
Appendix E. Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the 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.
Copyright IBM Corp. 1993, 2004
1033
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. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Programming Interface
This publication is intended to help the customer with the IBM Tivoli Storage Manager messages. This publication documents information that is not intended to be used as programming interfaces of the IBM Tivoli Storage Manager.
1034
IBM Tivoli Storage Manager: Messages
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:
AIX AS/400 DB2 DFS DFSMS/MVS DFSMShsm DFSMSrmm DPI Enterprise Storage Server ESCON FICON FlashCopy IBM Informix iSeries Lotus Lotus 123 Lotus Approach Lotus Domino Lotus Notes Magstar MVS NetView OpenEdition OS/2 OS/390 OS/400 pSeries RACF Redbooks RS/6000 S/390 SANergy SecureWay StorageSmart SystemView Tivoli Tivoli Enterprise Console Tivoli Management Environment TotalStorage TME VTAM WebSphere z/OS zSeries
Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. 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. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others.
Appendix E. Notices
1035
1036
IBM Tivoli Storage Manager: Messages
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).
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. archive copy group. A policy object containing attributes that control the generation, destination, and
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 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,
Copyright IBM Corp. 1993, 2004
1037
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.
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). 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 a stub file on the client node. The space management attributes in the management class control this migration. See also space management.
B
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 Storage Manager database, and storage pools. Contrast with restore. See also database backup series and incremental backup.
1038
IBM Tivoli Storage Manager: Messages
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 database snapshot cannot have incremental database backups associated with it. See also database backup series. Contrast with full backup.
Glossary
1039
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 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
1040
IBM Tivoli Storage Manager: Messages
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.
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.
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.
Glossary
1041
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.
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.
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
1042
IBM Tivoli Storage Manager: Messages
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.
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.
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. 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. node. (1) A workstation or file server that is registered with an IBM Tivoli Storage Manager server to receive
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. 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. policy privilege class. A privilege class that allows an administrator to manage policy objects, register client
Glossary
1043
nodes, and schedule client operations for client nodes. Authority can be restricted to certain policy domains. See also privilege class. 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. 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. 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.
reclamation. A process of consolidating the remaining data from many sequential access volumes onto fewer new sequential access volumes. 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. 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. 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.
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.
1044
IBM Tivoli Storage Manager: Messages
S
schedule. A database record that describes scheduled client operations or administrative commands. See administrative command schedule and client schedule. 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.
shared library. A library device that is shared among multiple IBM Tivoli Storage Manager servers. 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. 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
1045
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.
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.
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
1046
IBM Tivoli Storage Manager: Messages
Program Number: 5608-HSM 5608-ISM 5608-ISX 5608-SAN 5608-TDR 5698-A11 5698-A12 5698-A13 5698-A25 5608-APD 5608-APE 5608-APH 5608-APW 5608-APR
Printed in USA
SC32-9090-02
Spine information:
IBM Tivoli Storage Manager
Version 5.3
Messages
You might also like
- Installation and Configuration of IBM FileNet Information Management Software: A step-by-step guide to installing and configuring IBM FileNet ECM and Case Manager on RHEL 8.0 (English Edition)From EverandInstallation and Configuration of IBM FileNet Information Management Software: A step-by-step guide to installing and configuring IBM FileNet ECM and Case Manager on RHEL 8.0 (English Edition)No ratings yet
- IBM Tivoli Storage Manager For Mail Version 6.3.0No ratings yetIBM Tivoli Storage Manager For Mail Version 6.3.086 pages
- IBM Tivoli Storage Manager For Databases Data Protection For Oracle For Windows Installation and User's Guide Version 5.4.1No ratings yetIBM Tivoli Storage Manager For Databases Data Protection For Oracle For Windows Installation and User's Guide Version 5.4.184 pages
- 622 Programming Interface Codes - Msgs - ClientNo ratings yet622 Programming Interface Codes - Msgs - Client328 pages
- IBM Tivoli Storage Manager Versions 5.4 and 5.5 Technical Guide Sg247447No ratings yetIBM Tivoli Storage Manager Versions 5.4 and 5.5 Technical Guide Sg247447408 pages
- IBM Tivoli Storage Manager For UNIX and Linux Backup-Archive Client Installation and User's Guide Version 5.5 - Ans50000No ratings yetIBM Tivoli Storage Manager For UNIX and Linux Backup-Archive Client Installation and User's Guide Version 5.5 - Ans50000627 pages
- IBM Tivoli Storage Manager For Databases Data Protection For Oracle For UNIX and Linux Installation and User's Guide Version 5.4.1No ratings yetIBM Tivoli Storage Manager For Databases Data Protection For Oracle For UNIX and Linux Installation and User's Guide Version 5.4.1116 pages
- TSM Cli - TDP For Mail 55 Exchange - DpexcNo ratings yetTSM Cli - TDP For Mail 55 Exchange - Dpexc262 pages
- Data Protection For SAP HANA Installation and User's Guide: IBM Tivoli Storage Manager For Enterprise Resource PlanningNo ratings yetData Protection For SAP HANA Installation and User's Guide: IBM Tivoli Storage Manager For Enterprise Resource Planning108 pages
- IBM Tivoli Storage Manager For AIX Installation Guide 6.2No ratings yetIBM Tivoli Storage Manager For AIX Installation Guide 6.2132 pages
- Unit 1: IBM Tivoli Storage Manager OverviewNo ratings yetUnit 1: IBM Tivoli Storage Manager Overview34 pages
- IBM Tivoli Storage Manager V5.4 Implementation and Administration Part Two Tm526instNo ratings yetIBM Tivoli Storage Manager V5.4 Implementation and Administration Part Two Tm526inst628 pages
- IBM Tivoli Monitoring Installation and Setup GuideNo ratings yetIBM Tivoli Monitoring Installation and Setup Guide278 pages
- Separate System Upgrade and Data Migration GuideNo ratings yetSeparate System Upgrade and Data Migration Guide68 pages
- TSM 5.4 Data Protection For Microsoft SQL Server Installation and User's GuideNo ratings yetTSM 5.4 Data Protection For Microsoft SQL Server Installation and User's Guide188 pages
- IBM Tivoli Monitoring Administrator's GuideNo ratings yetIBM Tivoli Monitoring Administrator's Guide236 pages
- System Center 2012 R2 Virtual Machine Manager CookbookFrom EverandSystem Center 2012 R2 Virtual Machine Manager CookbookNo ratings yet
- IBM DB2 Administration Guide: Installation, Upgrade and Configuration of IBM DB2 on RHEL 8, Windows 10 and IBM Cloud (English Edition)From EverandIBM DB2 Administration Guide: Installation, Upgrade and Configuration of IBM DB2 on RHEL 8, Windows 10 and IBM Cloud (English Edition)No ratings yet
