Formatted dump contents

The title for a formatted dump varies, depending on the parameters provided. The output includes eye catchers and an index to help you locate individual control blocks.

Dump title

The contents of the dump titles that are created by the dump assist module (DFSFDMP0) and the initialization routines vary, depending on the internal DFSDUMP parameters provided and the SDUMP errors met.

The following examples show five possible dump title formats.

Title format 1

DFSFDMP0 issued the SDUMP and passed the SDWA parameter. The CALLER parameter was either passed to DFSFDMP0 or the routine generated the parameter using the IMS TCB table.

ljjjjjjjj ABEND SYS sss USER uuuu-rrr, DATE.TIME: ddd.tttttt,
                CALLER=cccc, TCB=xxx, MODULE=mmmmmmmm,i

l: Length of title in hexadecimal - here 91 decimal.
jjjjjjjj: Job name.
sss: System abend code.
uuuu: User abend code.
rrr: Optional user abend reason code.
ddd: Julian day of year.
tttttt: Time, in the form HHMMSS.
cccc: DFSDUMP caller parameter or blanks.
xxx: Abending TCB or 'UNK'.
mmmmmmmm: Abending module or 'UNKNOWN', using the SDWA.
i: Indicator if primary (P) or secondary (S) request.

Title format 2

DFSFDMP0 issued the SDUMP, but did not have an SDWA. The CALLER parameter was either passed to DFSFDMP0 or the routine generated the parameter by using the IMS TCB table.

ljjjjjjjj  DATE.TIME: ddd.tttttt, IMS DUMP REQUESTED,
                CALLER=cccc, TCB=xxx, REASON=rrr,i

l: Length of title in hexadecimal - here 80 decimal.
jjjjjjjj: Job name.
ddd: Julian day of year.
tttttt: Time, in the form HHMMSS.
cccc: DFSDUMP caller parameter or blanks.
xxx: Abending TCB or 'UNK'.
rrr: Optional user reason code.
i: Indicator if primary (P) or secondary (S) request.

Title format 3

This format is generated for a DBCTL database resource adapter (DRA) SDUMP.

ljjjjjjjj DRAthd tnnnn mmmm...mmRTKN=rrrrrrrrxxxxxxxxxxxxxxxx

l

Length of title in hexadecimal - here X'5D'.

jjjjjjjj

DBCTL job name.

DRAthd

Abend component of DRA:

DRA: DRA control processing abended.
DRATHD: DRA thread abended.

t

Abend type:

S: System abend.
U: User abend.

nnnn

Abend code for:

Hex: System abend.
Decimal: User abend.

mmm...m

Message text (up to 40 characters) that describes the error. See the possible error messages following this example.

RTKN=

16-byte recovery token (present only for DRA thread abends).

rrr...r

First 8 bytes of the recovery token in characters. It identifies the ID of the CCTL region.

xxx...x

Second 8 bytes of the recovery token in hexadecimal.

The possible error messages for mmm...m follow. The issuing module precedes the message text.

DFSPRRA0,: DBCTL FAILURE DURING DRA TERM
DFSPRA10,: DBCTL FAILURE DURING IDENTIFY
DFSPRA20,: DBCTL FAILURE DURING RESYNC
DFSPRA50,: DBCTL FAILURE DURING PURGE
DFSPINI0,: FAILURE ESTABLISHING ESTAE
DFSPAT00,: GETMAIN FAILURE
DFSPINI0,: SSI FAILURE DURING SONCRT
DFSPINI0,: DBCTL FAILURE DURING SONCRT
DFSPSCH0,: SSI FAILURE DURING SCHED
DFSPSCH0,: DBCTL FAILURE DURING SCHED
DFSPUSC0,: SSI FAILURE DURING UNSCHED
DFSPUSC0,: DBCTL FAILURE DURING UNSCHED
DFSPSYN0,: DBCTL FAILURE DURING SYNC
DFSPDLI0,: DBCTL FAILURE DURING DLI
DFSPPTK0,: DBCTL FAILURE DURING PRIME
DFSPTTH0,: SSI FAILURE DURING TERMTHD
DFSPTTH0,: DBCTL FAILURE DURING TERMTHD
DFSPRA40,: PQE CANNOT BE PROCESSED
DFSPRRA0,: PQE OR PAPL IS INVALID
DFSFPRA0,: CONTROL TCB ESTAE INVOKED
DFSFPAT0,: THREAD TCB ESTAE INVOKED
DFSFPRA0,: DRA ESTAE FAILED TO ESTABLISH ESTAE
NO OTHER DRA MESSAGE

Title format 4

The SNAP call facility identifies calling routines that generate snap dumps. Supervisor call (SVC) dumps are generated only for the intended abend codes or status codes, and for unknown calling routines.

This dump is created by DFSERA20 when a SNAP dump is requested. The title is the format:

nnnnnnnn IMS USER ABEND uuuu, DATE.TIME:  ddd.tttttt,i

nnnnnnnn: IMS name.
uuuu: The user abend code or UNK if a SNAP was requested, but there was no abend set.
ddd: Julian day of year.
tttttt: Time, in the form HHMMSS
i: Indicator if primary (P) or secondary (S) requested.

Title format 5

This dump is created by DFSERA20 when a SNAP dump is requested. The format is generated for dumps that are taken when an unexpected DL/I status code is returned during HALDB Online Reorganization. The title is the format:

nnnnnnnn UNEXPECTED STATUS CODE cc, DATE.TIME:  ddd.tttttt,i

nnnnnnnn: IMS name.
cc: The unexpected status code returned during HALDB Online Reorganization.
ddd: Julian day of year.
tttttt: Time in the form HHMMSS.
i: Indicator if primary (P) or secondary (S) requested.

cc is the unexpected status code returned during HALDB Online Reorganization.

Eye catchers

To help you locate areas that are dumped, eye catchers are printed near the major control blocks in the formatted dump. Eye catchers are also useful when you are using IPCS to view the formatted dump. Examples of eye catchers are:

**SCD: System Contents Directory Area
**SSA: SAP and Save Area
**SB-1: Subsystem Overview for Sequential Buffering

Eye catchers are also listed at the top of the formatted dump.

Index

The formatted dump also contains an index at the end that is created by the z/OS® Index Service routine. Index entries are created each time an eye catcher is processed during formatting, and after the Offline Dump Formatter finishes processing.

Entry length is limited to 40 decimal characters.

Formatted dump output order

The following list shows the order in which the Offline Dump Formatter prints control blocks. If you specify FMTIMS ALL and all necessary data is available to the formatter, you get all of the areas listed. The order does not change when you specify subset options, but only the areas you specify are formatted. Descriptive information has been added for some control blocks where it is useful.

ODF Initialization Messages

These messages appear when the formatter is unable to find particular address spaces in the dump data set.

Eye catchers

Eye catchers of the areas that you requested to be formatted on this pass of the formatter.

An eye catcher could be included in this list even if the Offline Dump Formatter was unable to format the control block, because the list is built from the parameters you include in the FMTIMS statement.

Diagnostic Area

Contains the PSW, system and user completion codes, save area ID of the module that was executing, and registers in use when abnormal termination occurred.

Instruction Area

Contains the area of storage from 128 bytes before to 128 bytes after the address of the failing instruction in the PSW.

Register Area

This area contains 512 bytes above and 256 bytes below each register value in the passed SDWA. The address space ID (ASID) used is the one passed in the SDWA.

System Diagnostic Work Area

The mapping DSECT is IHASDWA.

Referenced SAP

The mapping DSECT is ISAP.

System Contents Directory

The mapping DSECT is ISCD.

SCD Latch Extension

The mapping DSECT is ISCD.

Scheduler Sequence Queues

Controls the status of each region. The mapping DSECT is ISCD.

Synchronous APPC/OTMA Shared Message Queue SCD Extension

The mapping DSECT is DFSCSCD.

FP ESCD

The mapping DSECT is DBFESCD.

Control Block Table

Contains entries of control blocks that macro DFSCBTS uses for tracking. The mapping DSECT is DFSCBTS.

Control Block Table Pools

All IPAGEs for CBTE types requested with the (CBTE,cbteid) option.

Save Area Trace

SAPs with their Active UEHBs

Save Area Prefix

All SAPs are SNAPed. Each SAP is followed by its save area set. At the end of this section, all of the SAP IPAGEs are dumped.

IMS Task Dispatch Work Area

The mapping DSECT is IDSPWRK.

DBRC Task Dispatch Work Area

If present in the system, it is mapped.

IMS Control Task Dispatch Work Area

Contains the same information as the IMS log task dispatch work area.

Dependent Region Dispatch Work Area

For every dependent region in IMS, the dispatcher work area is mapped.

Dispatcher Trace Data

DSECT IDSPWRK contains the function codes associated with the dispatcher and an explanation of each code.

Scheduler Trace Data

Scheduler trace data is mapped by DFSSCHED. The trace entries contain scheduler function codes.

Latch Trace Data

The trace entries contain latch and unlatch function codes. The mapping DSECT is IDLIVSAM TRACENT.

Timer Work Areas

These are control blocks used by the internal IMS timers.

System PSTs

These are system work areas for any online or batch region. The mapping DSECT is IPST.

Restart Work Areas

See RESTART Solving IMS problems by using the IMS Offline Dump Formatter for a list of these areas.

Log Control Directory

Contains information about the IMS log. The mapping DSECT is LCDSECT.

Log Work Areas

Log Buffers

Each log buffer contains buffer information and the log control DECB. The mapping DSECT is LCDSECT.

Open Record

Contains the type 06 log record. The mapping DSECT is ILOGREC.

Control Record

Contains the type 42 log record. The mapping DSECT is ILOGREC.

Monitor Log Directory

Contains the same information as the log control directory.

DLOG Trace Data

Trace table used to show IMS logging activity. The mapping DSECT is ILOGREC (67FA).

Subsystem Control Table

Attach Work Areas

PSB Directory

A SNAP of the PSB directory. The mapping DSECT is PDIR.

DMB Directory

A SNAP of the DMB directory. The mapping DSECT is DDIR.

Intent List

The DL/I address space must be in the dump data set for this list to be formatted.

Fast Path Trace

Dependent Region PST formatting

For each DPST:

PST
Savearea
PDIR
Intent List
PSB prefix
PSB Index Maintenance, Index I/O, I/O, SSA, and User Parms work areas
SMB
DB PCB blocks
Delete work area
Retrieve Trace
HD Space Trace
FLDS
RPL
IRLM area
PST log work area
Fast Path EPST and chain addresses, ECNTs, EMH message, EPCBs, XCRBs, and DMHR

BFSP

Formats the buffer pool prefix. The mapping DSECT is BFSP.

BFUS

Formats the subpool prefix. The mapping DSECT is BFUS. The mapping DSECT is RPLI.

DL/I Data

A dump of the DL/I lock activity and program isolation trace table. The mapping DSECT is IDLIVSAM TRACENT.

Lock Activity Trace Data

See DL/I Data.

Program Isolation Data

Includes the QEL, QCB and REQ areas. The mapping DSECT is XC00.

OSAM Control Blocks

The system attempts to follow the main pool, the subpool header, and the buffer prefix, and to dump the buffer. However, if an error is encountered during formatting, the entire buffer pool is SNAPed from the last valid subpool address.

DL/I Trace Table

Sequential Buffering Blocks

Sequential Buffering information is grouped into the following four sections. (See the explanation of the (SB) FMTIMS option Solving IMS problems by using the IMS Offline Dump Formatter for a complete list of the blocks dumped in each section.)

Subsystem Overview for Sequential Buffering
PST Overview of Sequential Buffering control blocks
Formatted Sequential Buffering control blocks
Sequential Buffering buffers

DEDB Formatting

Fast Path EMH Formatting

Fast Path MDSB Formatting

Communication Line Blocks and Subordinate Blocks ^¹

For each CLB line, all the control blocks associated with that line are formatted.

CTB ^¹

The mapping DSECT is ICLI CTBBASE=0.

Input Buffer ^¹

A SNAP of the input buffer, if input is active.

Output Buffer ^¹

A SNAP of the output buffer, if output is active.

CCB ^¹

Present if a conversation is active or held. The mapping DSECT is ICLI CCBBASE=0.

CIB ^¹

Present if MFS is in use. The mapping DSECT is ICLI CIBBASE=0.

Communication Terminal Table ^¹

Defines terminal characteristics. The mapping DSECT is ICLI CTTBASE=0.

SPQB Entries ^¹

Entries on the subpool queue block chain. Unallocated CNTs are also formatted here.

SMB Table ^¹

This table defines transaction characteristics in the IMS system. The mapping DSECT is IAPS SMBBASE=0.

Queue Manager Pool Prefix and Buffers ^¹

The mapping DSECTs are ICLI POOLBASE=0, ICLI BFRBASE=0, and QPOOL. The buffer prefix list contains the address of each buffer's prefix, status byte, and first and last pending and current device relative record number (DRRN).

Batch Utility Areas

DBRC Work Areas

LUM Trace

Allows LU 6.2 activities to be analyzed with the MVS/ESA APPC trace entries by the LU manager.

¹ These areas are not dumped in a DBCTL environment.