Collecting data about database problems

The first step to diagnosing an IMS problem is to collect data about the problem. If you call an IBM® service representative, you will be asked for documentation about the problem.

For database problems, obtain the following information:

  • The damaged database data set.
  • The database image copy of the damaged database in a state prior to damage.
  • The image copy of logically related databases.
  • The IMS OLDS from all data-sharing IMS subsystems.
    • Save from the last good database image copy of damaged database.
  • If possible, and not already set, use the following IMS commands and save the output: 
    /TRA SET ON TABLE DLI OPTION LOG
    and 
    /TRA SET ON TABLE LOCK OPTION LOG
  • The SYSOUT from the Pointer Checker jobs for the damaged database.
  • The SYSOUT from batch jobs that accessed the damaged database.
  • The LIST.RECON and LIST.HISTORY DBD from the damaged database.
  • The SMF 60, 62, and 64 records from all data-sharing systems back to the last good image copy of damaged database.
  • For VSAM data sets:
    • Issue IDCAMS LISTC for the damaged VSAM data set.
    • Issue IDCAMS DIAGNOSE and IDCAMS EXAMINE for the damaged VSAM KSDS data sets.