IBM Support

What documentation should I gather if IMS hangs?

Question & Answer


Question

What is the best type of dump to take for diagnosis of an IMS hang?

Answer

Obtain a z/os SVC DUMP of the Control, DLI, suspicious dependent region
or CCTL, DBRC, and IRLM regions
DUMP COMM=(dump title)
R id JOBNAME=(j1,j2,j3,j4,j5,j6),SDATA=(CSA,PSA,RGN,SQA,SUM,TRT,GRSQ), END
- Where j1 = IMS Control or DBCTL Region Jobname
j2 = IMS DLI Region Jobname
j3 = Suspicious IMS Dependent Region Jobname, if any
j4 = Suspicious CCTL (CICS) region name, if any
j5 = IRLM Region Jobname (If IRLM DB Locking used)
j6 = DBRC Region Jobname
Also hold on to the z/os syslog, IMS region joblogs, and IMS log records as they may be needed. . Additionally - IMS has many more address spaces and I would, if using, include CSL(SCI) address space at a minimum and suggest adding OM (operations manager address space) and RM (resource manager address space).

Once you have a dump of the address spaces, use the z/OS modify command to terminate IMS. I.e. F IMS,DUMP

I would also suggest using this SDATA parameter list. You'll only have one shot at this(hopefully). SDATA=(ALLNUC,COUPLE,CSA,GRSQ,LPA,LSQA,PSA,RGN,SQA,SUM,SWA,TRT,XESDATA)

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPH2","label":"IBM Information Management System (IMS)"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
29 June 2016

UID

dwa1284960