Manuals / Brands / Portable Media / Storage / Tivoli Audio / Portable Media / Storage

Tivoli Audio Version 3 Release 7 - page 28

1 1473

Download 1473 pages, 2.77 Mb

xxvi

Version 3 Release 7

Contents

Main Page Page Page Contents Preface.................................................... vii Summary of Changes for Tivoli Storage Manager xvii Page Page Page Preface Messages Not Appearing in This Publication Message number ANR7831I and numbers in the range ANR79008199 are AS/400 Softcopy Publications Tivoli Storage Manager Publications The following table list TSM server publications. The following table list the TSM client publications. The following table list Tivoli Data Protection publications. Related AS/400 System Publications The following table lists related AS/400 publications. Referenced MVS System Publications The following table list referenced MVS publications. Related IBM Hardware Products Publications IBM International Technical Support Center Publications (Redbooks) Referenced Publications Software Developers Program Tivoli Storage Manager Web site Do You Have Comments or Suggestions? Translations Summary of Changes for Tivoli Storage Manager Changes for Version 3 Release 7April 2000 Product Repackaging ChangesSeptember 1999 Table1. Product Name Changes Table1. Product Name Changes (continued) Changes for Version 3 Release 7September 1999 Page Changes for Version 3January 1999 Changes for Version 3September 1998 Page Changes for Version 3March 1998 Changes for Version 3October 1997 Page Page Page Page Page Page Introduction Page Understanding Messages Message Format Page Page Page Obtaining Help with Tivoli Storage Manager Internet and IBMLink Assistance Internet IBMLink/ServiceLink Describing the Error with Keywords Component Identification Keyword Type-of-Failure Keyword The following keywords identify the type of failure that may occur: Tivoli Storage Manager 2. Obtaining Help with Command Keyword Obtaining Online HELP (Get Help on Error Messages) Contacting Your Service Representative Running Trace Commands Page Page Page Page Common and Platform Specific Messages (ANR0100ANR9999) Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Client Events Logged to Server (ANE40004999) Page Page Page Page Page Page Page IIIClient Messages Page Client Message Repository File (01000199) Page 5. Client Message Repository File Page Application Program Interface (02000479) Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Client Common Messages (10001999) Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page CommandLine Client Messages (10533999) Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Enterprise Management (25002999) Page Page Page Page Page Client Event Logging (40004999) Page Page Page Page Page Page Page Page Page Graphical User Interface Client (50005999) Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Windows Backup-Archive Client (70007999) Backup-Archive Client Page 13. Windows Backup-Archive Client Page Page Page Administrative Command Line Client (80008499) Page Page Page Page Page Page Page Page Page Page Page Tivoli Space Manager (90009999) Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Tivoli Data Protection for Lotus Notes (09000999) Page Page Page Page Page Page Page Page Page Page Page Page Page Tivoli Data Protection for Microsoft SQL (ACO0301-5203) Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Tivoli Data Protection for Oracle (05000599) 18. Tivoli Data Protection for Oracle Page Page Page Notices A Page Programming Interface Trademarks Page Page Allocating Additional Server Memory B Page I/O Error Code Descriptions for Server Messages C Completion Code and Operation Code Values Completion Code Values Common to All Device Classes Table2. Completion Code Values Common to All Device Classes Table2. Completion Code Values Common to All Device Classes (continued) Completion Code Values for Media Changers Table3. Completion Code Values for Media Changers Page Table3. Completion Code Values for Media Changers (continued) Completion Code Values for Tape and Optical Drives Table4. Completion Code Values for Tape and Optical Drives Table4. Completion Code Values for Tape and Optical Drives (continued) Operation Code Values for Tape Library Devices Table5. Operation Code Values for Tape Library Devices Table5. Operation Code Values for Tape Library Devices (continued) Common Values for ASC and ASCQ Codes Table6. Common Values for ASC and ASCQ Codes Page Page Page Windows NT Event Log Entries Device Errors in AIX System Error Log D Page Page Page Checklist for Contacting your Service Representative E Page Glossary A Page Page Page B C Page Page D Page Page Page E Page F G H I K L M Page Page Page N O P Page Q R Page S Page Page Page T U V