Steps for obtaining a dump for the error

Use the following steps to obtain a dump and collect additional data using IPCS:

If a dump was not written for the abend, re-create the problem and obtain a dump by doing one of the following:
- Set a to obtain an SVC dump. For example:
```
SLIP SET,C=0C9,JOBNAME=RMF,A=SVCD,END
```
  This SLIP trap will request a dump when an ABEND0C9 occurs in the RMF address space. For more information, see the topic on the SLIP command in z/OS MVS System Commands.
- Insert a SYSABEND, SYSUDUMP or SYSMDUMP DD statement in the JCL for the abending job step to obtain an ABEND dump. For more information, see z/OS MVS JCL Reference.

Use IPCS to look at the dump. Use IPCS subcommands in the order indicated by the following list. If using IPCS interactively for an SVC dump, respond yes to the IPCS message that asks if summary data can be used by dump access.

STATUS FAILDATA

STATUS SYSTEM

Example: In the following STATUS SYSTEM output, AMDSADMP indicates that this dump was scheduled. Also note the date and time the dump was taken.

SYSTEM STATUS:
  Nucleus member name: IEANUC01
I/O configuration data:
     IODF data set name: IODF.IODF12
     IODF configuration ID: TC4SYST
     EDT ID: 00
  Sysplex name: ENGTEST2
  TIME OF DAY CLOCK: BE5E67AF 7ED6370E  02/15/2006 14:33:32.124515 GMT
  TIME OF DAY CLOCK: BE5E24A1 5B96370E  02/15/2006 09:33:32.124515 local
  Program Producing Dump: SADUMP
  Program Requesting Dump: AMDSADMP

STATUS CPU REGISTERS DATA CONTENTION
STATUS WORKSHEET
SUMMARY FORMAT
VERBEXIT LOGDATA
VERBEXIT SUMDUMP
SYSTRACE

VERBEXIT MTRACE

Example: In the following VERBEXIT MTRACE output, message IEF450I indicates a system abend of X'522' with a reason code of X'00'.

0001 007A5F54  N 0000000 ANO3     93039 10:26:08.31          00000281
               IEA989I SLIP TRAP ID=X13E MATCHED
0001 007A5F54  N 0000000 ANO3     93039 10:26:08.34          00000281
               IEA989I SLIP TRAP ID=X13E MATCHED
0001 007A5F54  N 0000000 ANO3     93039 10:26:08.43          00000281
               IEA989I SLIP TRAP ID=X13E MATCHED
0001 007A5F54  N 0000000 ANO3     93039 10:26:08.49          00000281
               IEA989I SLIP TRAP ID=X13E MATCHED
0001 007A5F54  N 4000000 ANO3     93039 10:26:09.21 TSU05807 00000091
               IEF450I LASSEC2 AAIRACF AAIRACF - ABEND=S522 U0000
               REASON=00000000
0001 007A7430  N 4000000 ANO3     93039 10:26:09.45 TSU06038 00000091
               IEF450I LAMMLF AAIUSER AAIUSER - ABEND=S522 U0000
               REASON=00000000
0001 007A7430  M 4000000 ANO3     93039 10:26:09.59 TSU05807 00000090
               IEF377I LASSEC2 AAIRACF AAIRACF
0001 007A5F54  E                                         064 00000090
               LASSEC2.SPFLOG1.LIST NOT CATLGD 2
0001 007EC02C  N 4000000 ANO3     93039 10:26:09.66 TSU05807 00000090
               /HASP395 LASSEC2 ENDED
0001 007A79C0  N 0200000 ANO3     93039 10:26:10.06 TSU05807 00000081
               /HASP250 LASSEC2 IS PURGED

Subcommands selected from the list below
VERBEXIT SYMPTOM

Before the VERBEXIT SYMPTOM subcommand, add other IPCS subcommands, depending on the problem indicated in the abend explanation or accompanying messages. Pick the subcommands from the following list:

Table 1. Summary of IPCS dump subcommands by problem
Problem involves	IPCS dump command
Allocation/unallocation of jobs	VERBEXIT ALCMWAIT
Asynchronous operations manager (AOM)	VERBEXIT AOMDATA 'TRCDUMP'
Auxiliary storage	ASMCHECK VERBEXIT ASMDATA
Availability management	VERBEXIT AVMDATA
Callable service requests	CBFORMAT addr STRUCTURE(CSRCPOOL) CBSTAT addr STRUCTURE(CSRCPOOL)
Communications	COMCHECK
Cross-system coupling facility	COUPLE SUMMARY ALL
(XCF)	COUPLE DETAIL ALL COUPLE EXCEPTION ALL
Data-in-virtual	DIVDATA SUMMARY ALL
Data lookaside facility of VLF	DLFDATA
Global resource serialization	VERBEXIT GRSTRACE
Input/output	IOSCHECK
JES2	VERBEXIT JES2
JES3	VERBEXIT JES3
Language Environment®	VERBEXIT LEDATA
MVS™ message service (MMS)	VERBEXIT MMSDATA
z/OS UNIX System Services (OMVS)	OMVSDATA SUMMARY OMVSDATA DETAIL OMVSDATA EXCEPTION
Real storage manager (RSM)	RSMDATA SUMMARY RSMDATA EXCEPTION
System resources manager (SRM)	VERBEXIT SRMDATA
Storage Management Subsystem (SMS)	VERBEXIT SMSDATA
Time sharing option (TSO)	VERBEXIT TSODATA
Virtual storage manager (VSM)	VERBEXIT VSMDATA
Virtual lookaside facility (VLF)	VLFDATA

Use the RSMDATA SUMMARY output to get a summary of real storage usage in the system. Use the RSMDATA EXCEPTION report to determine where errors might have occurred. The following is an example of RSMDATA SUMMARY output:

Figure 1. RSMDATA SUMMARY report

                   R S M   S U M M A R Y   R E P O R T							
																																
																																			
													 			  										Tot real      Prf real      Below Prf    ...
												      				 		 			------------- ------------- ----- -----  ...
In configuration . . . .        131,072        98,234  4,096 4,026    ...
Available for allocation        126,084        93,247  4,093 4,023    ...
Allocated  . . . . . . .         54,127        53,253    184   118    ...
Percent usage  . . . . .             42            57      4     2    ...
Common fixed frames  . .          3,291         3,145     19    19    ...
Percent of available .                2             3      0     0    ...
Total fixed frames . . .          8,283             -     28     -    ...
Percent of available .                6             -      0     -    ...


V=R Region:
First frame number X'00006'
Last frame number X'0004B'
Size (in frames)               70

Total disabled reference (DREF) pages in real:           2,309

Number of shared data pages:
Valid and fixed in real  . .              3
Valid and pageable in real .          1,356
On auxiliary storage . . . .              0

Number of 64-bit common memory pages:
Backed in real . . . . . . .                      513
Fixed in real  . . . . . . .                      144
DREF in real . . . . . . . .                      256
On auxiliary storage . . . .                        0

Examine the VRADATA output in the STATUS FAILDATA, VERBX LOGDATA or EREP report for an error for additional clues about the error. For some components, the data consists of a key, a length, and the contents.

Example: In the following Variable Recording Area from STATUS FAILDATA output, the VRA key is X'1A' and the length is X'94'.

VARIABLE RECORDING AREA (SDWAVRA)

  +000    Key: 1A     Length: 94
  +002    02000000    08004000    00040001    1D00E610    |...... .......W.|
  +012    E0001300    00000000    00000000    00000000    |\...............|
  +022    00000000    00000000    00000000    00000000    |................|
  +032    00000000    00000000    00000000    0000002B    |................|
  +042    00100000    00000000    00000000    00000000    |................|
  +052    00000000    00000000    00000000    FFFC0000    |................|
  +062    012DBD64    00000000    01A9CD24    00000C80    |.........z......|
  +072    00000000    019D6690    012DC698    00000000    |..........Fq....|
  +082    01B42000    00000000    00000000    00000000    |................|
  +092    00000000                                        |....            |

STATUS FAILDATA will not format an SDWA for a dump requested by SLIP. If SDWA data is not in the dump, obtain problem data from STATUS CPU REGISTERS or view the SDUMP 4K SQA buffer. (See Reading the SDUMPX 4K SQA buffer in z/OS MVS Diagnosis: Tools and Service Aids.)

You should now have extracted enough problem data to do a search for a known problem, identify the source of the problem, or report the new problem to IBM or the appropriate vendor.

Related information

For information about the SYSMDUMP DD, see
- z/OS MVS Diagnosis: Tools and Service Aids
- z/OS MVS IPCS Commands
- z/OS UNIX System Services Planning
- .
- z/OS MVS System Commands