This document describes how to gather documentation for IMS problems. It consists of five sections: MVS setup recommendations, IMS setup recommendations, preservation of standard documentation, manual dump intervention, and situation specific diagnostics.
This document is the handout for IBM session E60, presented in Las Vegas in September 2003, titled "How to Setup and Gather Documentation for IMS Problems". It is a technical presentation aimed at system programmers who need to prepare MVS and IMS environments so that useful diagnostic data is captured when IMS problems occur.
The material is organized into five sections: MVS setup recommendations (System Trace and Master Trace table sizes, common storage tracking, CHNGDUMP MAXSPACE, automatic dump dataset allocation), IMS setup recommendations (including the FMTO=D EXEC parm and Sysplex IEADMCxx dump activation), preservation of standard documentation, manual dump intervention, and situation-specific diagnostics covering areas such as RRS-related errors and MSC (Multiple Systems Coupling) problems.
| MVS System Trace table size (recommended) | 999K |
|---|---|
| MVS System Trace table default size | 64K |
| MVS Master Trace Table size (recommended) | 500K |
| Master Trace Table default size | 24K (approx. 336 messages) |
| CHNGDUMP SDUMP MAXSPACE (default) | 500M |
| CHNGDUMP SDUMP MAXSPACE (standard for large dumps) | 2500M |
| VTAM Internal Trace dataspace size (MSC problems) | DSPSIZE=5, SIZE=999 |
Specify the IMS control region EXEC parm value FMTO=D, which produces an SDUMP for terminating and non-terminating errors such as IMS dynamic allocation failures and some ESAF failures.
Enter the MVS command DUMP TITLE=(IMS/CCTL SYSPLEX Dumps),PARMLIB=(I1,I2); two dump datasets are created on each MVS image in the SYSPLEX matching the REMOTE specifications for the JOBNAMEs.
Turn on the MVS common storage tracking function using the DIAGxx SYS1.PARMLIB member (for example VSM TRACK CSA(ON)); SVC dumps will then provide CSA/ECSA ownership information with jobname, time, and requesting module.
Take an SVC dump of the coupled IMS regions including the VTAM address space as close to the problem time as possible, save the IMS OLDS for both coupled systems, and issue DISPLAY LINK ALL commands to show logical and physical link status.