DL/I trace

For full function databases, you can use DL/I trace with DBCTL by enabling the DL/I trace table in the DFSVSMxx member or by issuing the /TRACE command.

The /TRACE command is described in Controlling tracing of DBCTL events. Using the /TRACE command enables you to turn DL/I trace on and off while the system is running. Output is to the IMS log as type X'67FA' records. See Diagnosis in IMS product documentation for guidance on using DL/I trace for diagnosis, Operations and automation in IMS product documentation for guidance on the commands needed to invoke it, and Database utilities in IMS product documentation for guidance on printing its output.

Using the IMS log statistics utilities

You can use these IMS log statistics utilities to process the information from the IMS log. See DBCTL data returned to IMS log for a list of the data returned to the IMS log.
  • File select and formatting print utility, DFSERA10, formats, and prints selected records from the IMS log data set. The active OLDS must have been archived before you can access the log data. You normally specify the SLDS to DFSERA10. You can also use DFSERA10 with the program isolation trace record format and print module, DFSERA40, to format PI trace.
  • DEDB log analysis utility, DBFULTA0, prepares statistical reports for DEDBs based on data recorded on the IMS system log.
  • IMS program isolation trace report utility, DFSPIRP0. If you use program isolation (PI), you can use DFSPIRP0 with the IMS log to obtain information about deadlocked tasks. DFSPIRP0 prints a report that shows only those enqueue requests that required a wait because the resource was not immediately available.

See Database utilities in IMS product documentation for guidance on using these utilities.