Preserving standard diagnostic documentation
If an error occurs, you can preserve diagnostic data that might be helpful in problem diagnosis. You can create operating procedures to preserve commonly needed diagnostic information.
- Preserving the z/OS console (SYSLOG)
The z/OS® console log (SYSLOG) contains messages about the state of the operating system. Because these messages might indicate the source of the problem, retaining the SYSLOG data set is recommended. - Preserving LOGREC data
The log record (LOGREC) data contains messages about hardware and software errors. Therefore, retaining the LOGREC data is recommended. - Preserving the JES job logs for key DB2 address spaces
The JES job log from key DB2 address spaces contains relevant job-related messages. Therefore, retaining the JES job log is recommended. - Retention of DB2 dump data sets
To ensure that you have diagnostic data available if a problem occurs, you need to retain SYS1.DUMP data sets and dump data sets that were dynamically allocated. - Retention of DB2 logs
DB2 log data sets are often helpful when you diagnose problems. Therefore, retaining DB2 log data sets is recommended. - Requesting DB2 SVC dumps
You can use the system console DUMP command to request a DB2 supervisor call (SVC) dump. - Requesting data sharing environment DB2 SLIP traps
In a DB2 data sharing environment, a hang or problem on one DB2 member might originate in a separate member. To find the problem, you need to create a serviceability level indication processing (SLIP) trap to catch error events and to create supervisor call (SVC) dumps. - Factors to consider when preserving diagnostic data
Due to the interactions between address spaces, you might sometimes need to obtain a dump of associated address spaces so that you can diagnose problems. To ensure that information that is needed to diagnose the problem is available, you need to consider several factors when requesting dumps of data.
Parent topic: Collecting diagnostic data