System dump

A system dump is requested via the operand specification SCOPE=*SYSTEM of the CDUMP2 macro and is always cataloged under the user ID SYSDUMP.
It covers the entire class 6, class 5, class 3 and class 1 memory with the exception of those pages declared “secret pages”. Some system parameters influence memory area output (see section "Control by means of system parameters").

The areas containing the following tables are automatically output together with the class 5, class 3 and class 1 memory:

• EXVT

• SVMT

• UVMT

• TCB

• PCB stack

• JCB

• TTSAV

• P1-AUDIT

All data pages of class 4 memory are output except “secret pages”.

The system dump also contains those pages of class 4 and class 2 memory which are offset anywhere up to five pages before or after a reference address and the reference page itself. These reference addresses are pointed to by the program counters (PC) in the PCBs and the trace table and by the general-purpose registers in the PCBs and the bourse registers in the PCBs. Memory pages which have the attribute “secret pages” are not output.

A system dump also contains the following:

• the AIDSYSD, EOLDTAB, DMCHD, NSISINF and CLASS2OP modules

• the trace dump list area

• the REPLOG and SERSLOG system files
  (stored in separate dump segments, down to the last-page pointer).

In the CDUMP2 macro, buffering of the class 1, class 3 and the resident class 4 memory can be requested with the SNAP operand (privileged users only) before the actual creation of the dump. This so-called SNAP dump is then incorporated into the dump when generating the system dump.

The operator is issued a message (IDA0N52) inquiring as to whether the system dump is to be output to disk or tape. Output of the message can be suppressed with the DUMPCTRL and DUMPSD# system parameters .

Normally, a system dump can be requested only from the privileged system area (TPR). However, you can also request a system dump as a non-privileged user, provided you first set your read privileges to m≥3. You do this with the following command:

/MODIFY-TEST-OPTIONS PRIVILEGE=*PARAMETERS(READ=m,WRITE=1)

You are only authorized to do this if you have been assigned this option for setting privileges in the user catalog.If you have the right privileges (see above), you may convert a user dump into a system dump (with the MODIFY-TEST-OPTIONS command and the DUMP=*SYSTEM operand).The message IDA0N45 is suppressed. The operator can control whether a system dump is stored on disk or tape.In the event of an aborted system dump, message IDA0N99 is output, depending on the system parameter DUMPCTRL.

A system dump that was stored on tape must be copied to a disk with the COPY-FILE command or the PERCON utility routine. It can then be edited with the DAMP diagnostic routine. 

Example 1

/IMPORT-FILE SUPPORT=*TAPE
           VOLUME=<volume>,DEVICE=<device>, FILE-NAME=<filename> ——————  (1) 
/ADD-FILE-LINK LINK=DMCOPY11, FILE-NAME=<filename>,ACCESS-METHOD=*UPAM,
           BUF-LEN=*STD(2) ————————————————————————————————————————————  (2) 
/ADD-FILE-LINK LINK=DMCOPY22, FILE-NAME=<output-filename>,
           ACCESS-METHOD=*UPAM,BUF-LEN=*STD(2) ————————————————————————  (3) 
/COPY-FILE FROM-FILE=<original-filename>,TO-FILE=<output-filename>—————  (4) 

(1) (2) (3) (4)

Entry of the tape file in the system catalog. Specification of the link name DMCOPY11 for the tape file. Specification of the link name DMCOPY22 for the output file. The system dump is then copied from tape to disk using COPY-FILE.

See also the description of COPY-FILE in the “Commands” manual [8].

Example 2

/CREATE-FILE <output-filename> ————————————————————————————————————————  (1)
/ADD-FILE-LINK LINK-NAME=<link-name>,FILE-NAME=<output-filename>,-
/    ACCESS-METHOD=*PAM,BUFFER-LENGTH=*STD(SIZE=1)
/START-PERCON 
//ASSIGN-INPUT-FILE FILE=*TAPE-FILE(NAME=<filename>) ——————————————————  (2) 
//ASSIGN-OUTPUT-FILE FILE=*DISK-FILE(NAME=<output-filename>) ——————————  (3) 
//START-CONVERSION ————————————————————————————————————————————————————  (4) 
//END

(1) (2) (3) (4)

Creation of output file Specification of the input file on tape Specification of the output file on disk. Conversion of the input file from tape to output file on disk.

File name of a system dump

CDUMP saves a system dump under the SYSDUMP system ID and forms the file name of the system dump in accordance with the following basic pattern:

:catid:$SYSDUMP.{ ABSOLU | module }.pc.ec.tsn.date.time

Where:
catid	is the catalog ID of the public volume set on which the dump is stored. If the dump was output to tape, no catalog ID is displayed.
module	is the name of the module from which the dump is activated, max 8 characters.
ABSOLU	is used if no name for the module exists.
pc	is the address in the program counter (relative to the start of the module or absolute).
ec	is the event code (hexadecimal). If the system dump was initiated with the CREATE-DUMP command, the event code has the value 'C8'.
tsn	is the TSN of the activating task.
date	is the date in the form Dyymmdd (D=marker identifying the start of a date, yy=year, mm=month, dd=day).
time	is the time in the form hhmmss (hh=hours, mm=minutes, ss=seconds).