Standard IMS diagnostic information
If you contact IBM® Software Support for assistance with a problem, you might be asked to collect a standard set of logs, data sets, and dumps that can help them determine the source of your problem. Collecting this information before you contact IBM Software Support will shorten the amount of time required to resolve your problem.
The following table describes the types of information that are most commonly requested by IBM Software Support:
| Log, data set, or dump name | Purpose | Which version to save |
|---|---|---|
| SYSLOG | The SYSLOG is useful when the dumped MTRACE buffer is not large enough to contain all necessary error messages. | Save the SYSLOG from time of IMS start up. |
| LOGREC data set | z/OS® failures are logged internally. | Save the LOGREC data set from IMS start up time. |
| IMS master console log | The master console log provides a different message set than the SYSLOG. | Save the master console log from IMS start up time. |
| IMS log data sets (OLDS) | The IMS log data sets track IMS transaction and database activity. | Save the IMS online data sets that are active at the time of the error. |
| IMS system log data sets (SLDS) | The IMS system log data sets track IMS transaction and database activity. | Save the SLDS from IMS start up time. |
| JES job log of jobs related to failure | The JES job log provides JCL start up parameters and isolated system messages. | Save the JES job log from IMS start up time. |
| All dumps created near the time of IMS failure | Multiple SYS1.DUMPs might be created for related failures. SYSMDUMP for the IMS Control, DLI/SAS, and DBRC regions might be created if the primary SYS1.DUMP encounters problems. Also, look for related SYSUDUMPs for IMS dependent regions | Save copies of these dump datasets. |
| z/OS log data sets | The z/OS log data sets provide information for structure rebuild and checkpoint related problems. | Save the current z/OS log data sets for the failing CQS job stream. |