A UTM dump edited with KDCDUMP normally contains the following information:
KDCROOT with the KDCROOT tables and the DIAGAREAs UTM Diagarea, DB Diagarea, ...).
A summary (Summary information).
A table of contents.
In some cases the dump may contain addition areas which only can be evaluated by the system service and which therefore are not described in this manual (exception: CONS-ENTRIES table). This ares should be provided to the system service if necessary, see section “Producing error documentation”.
If the dump was produced due to a PEND ER (either programmed by the user or produced internally after KCRCCC >= 70Z), then the dump only contains the KDCROOT area.
UTM dump in tabular form
The length of the individual lines of a UTM dump (80 or 132 characters) depends on the EDIT operand of the KDCDUMP utility (see also "The KDCDUMP tool") so you may have to specify the -pb3 option in the lpr command in order to print out the dump file. With the exception of the PROGRAM table, each line of an edited dump has the form (for 32-bit platforms):
Where
| I | is the 4-digit index or sequence number; not all lines contain one. |
| A | is the 12-character address. |
X | is the data in hexadecimal form, 64 characters in length (corresponds to 32 bytes); not included in the PROGRAM table. |
C | is the data in plain text, if it consists of printable characters; 32 characters in length (except in the PROGRAM table). |
The header starts with the corresponding storage area dumped (e.g. KDCROOT) and the name of the table.
Only those tables are described in the following which you can find in a PENDER dump. In addition, the CONS_ENTRIES table is listed which is created in case of dumps with other reasons and which provides useful information for the user.
Note
Storage areas edited in hexadecimal format must be analyzed according to machine type. The examples used in this chapter were produced on INTEL machines.