Input Processing
From eMS Output I REG 1 Check user options, assign a
Parameter unique dump number, read first
List five records of dump, and write
the first records to the CMS file. [j
ump B List CMS File [J
ump EJ List . Dump File Notes Module 1 If there are no options specified, the DMMEDM
defaults are MAP, FORMAT and
HEX. If an invalid option is specified,
issue message: INVALID PARAMETER parm
PAGE REFERENCED NOT DMMINI AVAILABLE Read the next sequential number
from the summary record file, and
append it to the dump prefix 'PRB'.
The dump name will always be
PRBnnnnn, where 'nnnnn' is the
DMMEDM
unique dump number.
Read the records by branching and linking to the READCPR routine.
The spool records contain the following: Record Contents
1 Symbol Table
2 Dump Information record 3-4 Storage Protection Keys at
time of dump
5 First page of storage
dumped (0) Save the following from the informa· tion record (2): • First 256 bytes of storage • General and floating·point and
control registers • TOO clock and comparator • Address of the terminating
prefix storage area • Abend code
Create the item table from the bit
map in record 2.
Write the records to the CMS file that will contain the CP dump file (if
requested) by branching and linking
to the WTREC routine.
2 Determine if the user wants
this dump. If 'NO', erase spool file and
return. If 'YES', create CMS file containing dump and call the
data extraction routines: ToCMS • Determine proper dump file. • Initialize buffers. • Compress nucleus load map
(Diagram 2·6). label Ref Notes CHKOPT 2 To determine if the user wants this dump, issue the message: VM/370 SYSTEM ABEND xxxx
DATE (date) TIME (time)
ERRFND DO YOU WANT THIS DUMP? PRBDUMNO If the user responds 'NO', erase
the spool file and return to CMS. If the user responds 'YES', write a
record by branching and linking to the
WRT Routine, read another record by
RDUMP
branching and linking to the READCD
routine, and so on until the read returns
a non·zero condition code:
Code Meaning
1 End-of-file, 'DUMP PRBnnnnn
CREATED' message is issued
2 Issue message 'NO DUMP FILES EXIST' and return toCMS 3 Issue message 'UNABLE TO READ DUMP FROM READER' and return to CMS • Examine the dump list that resides in
DMMEDM as a constant to determine
the file name assigned to the dump;
move this name to the read 'FSCB' to facilitate subsequent reads to the
dump file. • Initialize buffers EXTPSA (terminating PSA in the dump) and EXTINREC (record 2 from the dump)
NXTWD by issuing FSREADs to the dump
file.
RDUMP • Call the nucleus load map module
(DMMMAP) to compress the nucleus load map. (See Diagram 2-6.)
Diagram 2-5. VMFDUMP IPCS Command (Part 1 of 3)
28 IBM VM/370 Service Routines Program Logic Module label Ref
REREAD LOOP DMPEND1 NODMP LOOP DMMINI EXTREAD
EXTREND

Input From
Diagram
2-6
Processing Output From
Diagram 2-7,2-8, or 2-9 3 Determine type of failure: • If program check, call DMMPRG (Diagram 2-7)_ • If coded abend, call DMMCPA (Diagram 2-8). • If operator cal! DMMINI (Diagram 2-9).
4 Prompt user for additional information: • Write problem report.
(Diagram 2-3, Step 3.) • Perform duplicate search. (Diagram 2-3, Step 4.)
Diagram
2-3
Notes Module Label Ref Notes
3 Examine the DMPABEND field of the
dump information record (EXTINREC) to determine the failure type: • If the failure type is a program check
(PRGxxl, call the program check
routine (DMMPRG). See Diagram
2-7. • If the failure type is other than PSA02, call the coded abend routine
(DMMCPA). See Diagram 2-8. DMMINI EXTPSWCK • If the failure type is PSA02, handle EXTPSCHK within DMMINI. See Diagram 2-9.
4 Prompt the user for the severity code, DMMPRM GETSEV examine the previously set switches in
the SHARECON data area to determine PRMTYPSW the failure. If it was system detected PRMSUPP (CP abend or program check), request
the file name and file type of any
supporting documentation, and a
free form entry description of the problem. Note: The prompting sequence for PRMLPPER
operator initiated dumps depends on the user's response to the QUery: THE DUMP INFORMATION IS INCONCLUSIVE ENTER LOOP, PERFORMANCE OR OTHER • All information necessary to create
the problem report has been gathered. Call module DMMWRT to order the
data and create the problem report. See Diagram 2-3, Step 4. • Call module DMMSEA to search for duplicate problems. See Diagram 2-3, Step 4.
Diagram 2-5. VMFDUMP IPCS Command (Part 2 of 3) SHARCON D Module Label NORMEXIT Chapter 2. IPCS--The Interactive Protlem Ref I I I system 29