IBM IMS: How to Setup and Gather Documentation for IMS Problems (Session E60)

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.


IBM IMS: How to Setup and Gather Documentation for IMS Problems (Session E60) - cover page
Brand
IBM
Category
Other software
Document type
Application Note
Language
English
Pages
63
File format
PDF
File size
1.3 MB
Published
30 November, 2023
Updated
30 November, 2023
MD5 checksum
818B4FFBEF8F195607B4CB8FFDAE4886

About this manual

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.

What's inside

  • MVS Setup Recommendations
  • IMS Setup Recommendations
  • Preservation of Standard Documentation
  • Manual Dump Intervention
  • Situation Specific Diagnostics
  • System Trace Table
  • Master Trace Table
  • Common Storage Tracker
  • RRS Related Errors
  • MSC Related Problems

Specifications

MVS System Trace table size (recommended)999K
MVS System Trace table default size64K
MVS Master Trace Table size (recommended)500K
Master Trace Table default size24K (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

Frequently asked questions

What IMS FMTO option produces an SDUMP for terminating and non-terminating errors?

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.

How do I request a Sysplex dump using the IEADMCxx parmlib members?

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.

How can CSA/ECSA ownership information be obtained in SVC dumps?

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.

What should be captured for IMS MSC (Multiple Systems Coupling) problems?

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.

Download PDF (1.3 MB)

More IBM Manuals


View all IBM manuals →