DBCTL data returned to IMS log
In addition to the information returned to the monitor, IMS writes monitoring information to the log records. This information is always recorded; you do not have to request it.
For further information about the data returned to the monitor see IMS monitor reports with DBCTL.
IMS appends
the following information to the X'08' log records during scheduling.
- Total elapsed wait time due to intent conflict
- Total elapsed wait time due to pool space not being available
- Total elapsed time for a schedule request
- Total number of databases used involved in I/O
- Total number of DL/I database requests
- Total elapsed wait time due to databases involved in I/O
- Total elapsed wait time due to locking
- Total number of gets
- Total number of inserts
- Total number of replace
- Total number of deletes
Program isolation trace
For full function DL/I databases, you can use the program isolation (PI) trace to get records that indicate queueing activity taking place for program isolation. The PI trace records are written to the IMS log. You can then print them using the IMS file select and formatting utility. See IMS administration in IMS product documentation for further guidance on using PI trace.