The following major diagnostic aids are provided here for the Object Access Method (OAM):

• Procedures for retrieving information from the OAM DB2® Databases
• A listing of the return and reason codes that are generated by the OSREQ macro
• A listing of the return and reason codes that are generated by the OAM macro
• A listing of the return and reason codes that are generated and invoked through the CBRXLCS macro
• A listing of Library Automation Communication Services (LACS) return and reason codes
• OAM Records Written to SYS1.LOGREC
• An explanation of how to dump OAM
• An explanation of how to use the SMS trace facility for gathering OAM diagnostics
• An explanation of OAM IPCS processing
• Descriptions of some common DB2 problems when using OAM and some related DB2 service aids

Before using these diagnostic aids, be sure that all of the installation requirements have been met. Verify that you have performed all of the following tasks:

• Properly installed your optical and tape library hardware
• Installed OAM correctly (see z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Supportz/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Supportz/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support and z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries)
• If using object storage, defined the DB2 database
• If using tape libraries, defined the tape configuration database (TCDB)
• Activated the IODF with your hardware configuration
• Started the OAM address space
• Entered at least one cartridge into each library