Contents formatted for FMTIMS options

FMTIMS options can be specified on the FMTIMS statement in any order.

Contents formatted for FMTIMS options

The options are listed in alphabetical order.

Some options state they are ignored for batch. If the dump was taken because batch processing (IMS DB or CICS®) failed, the control blocks for these options are either meaningless or not included in the dump data set. Therefore, the control blocks are not formatted even if you specify that option on the FMTIMS statement.

Most options can be specified with the MIN qualifier. Whenever possible, specify this qualifier to reduce the number of control blocks formatted. You can always format the dump data set again if you need the additional information.

ALL
Causes a full, formatted dump.

(ALL,MIN) formats the dump as if each option were specified with the MIN qualifier.

AOI
Formats the storage for the Type 2 Automated Operator Control blocks.
AUTO
Provides an optimal subset of the IMS dump formatting options without having to first analyze the dump and without having to understand the content or use of all of the IMS dump formatting options.

This option uses the failing ITASK type information to choose one of the formatter's functional areas, and selects the appropriate dump formatter options.

CBT
Formats storage management area control blocks, including:
  • Control Block Table Header
  • Individual Control Block Table entries

Output is the same if (CBT,MIN) is specified.

CBTE,cbteid
Formats all the IPAGEs for the identified CBTE type (cbteid), including:
  • Individual Control Block Table entries
  • All IPAGE storage of the requested CBTE type

For example, if you specify (CBTE,DPST), all DPST IPAGEs are formatted.

This option can be repeated as needed and has no defaults. The requested IPAGEs must be part of the dump data set. MIN is not valid for the CBTE option.

CLB/LLB
Permits formatting of an individual Communication Line Block or Link Line Block and its subordinate blocks. Select this option by the following:
  • Address
  • Node name
  • LTERM name
  • Communication ID
Select the LLB by address or link number.
The CLB/LLB format creates eye catchers and index entries similar to the following: 
**CLB/LLB                   REQUESTED CLB/LLB
DB
Formats areas and control blocks used for IMS Database functions. The following table shows the areas formatted under the (DB) and (DB,MIN) FMTIMS options.
Table 1. Formatted areas under the FMTIMS options DB and DB,MIN
(DB) (DB,MIN)
Data Base Tracker Blocks same
Coupling Facility Block same
PSB Directory same
DMB Directory same
Intent List not formatted
BFSP same
DL/I Trace same
Fast Path Trace (if Fast Path is active) same
OSAM Pool Control Blocks and buffers OSAM Pool Control Blocks only
Program Isolation blocks same
All PSTs and related control blocks, including PCBs, SDBs, Savearea set, alternate DL/I DECB, DSGLRKEY, hierarchical holder, delete work area, RPLI, VSAM PLH, and retrieve trace Active PSTs, with the same related control blocks
If Fast Path is present: EPSTs and related control blocks, including EPCBs, ESRTs, EMHBs, message buffers, XCRBs, DMHRs, and DEDB buffers If Fast Path is present: EPSTs and related control blocks, including EPCBs, ESRTs, EMHBs, XCRBs, and DMHRs
VSAM buffer pool control blocks same
RLPL for IRLM requests same

In a DL/I–SAS environment, DPST formatting does not format related control blocks if the DL/I address space was not included in the dump data set.

DBRC
Formats records used by DBRC in its processing, including:
  • DFSRCWKB block
  • DFSBRLSB block
  • Dump Router storage
  • Global Data block
  • GDBDLTAR block
  • GDBDSAAR block
  • GDBRECAR block
  • GDBLISAR block
  • DSPEXIAG block
  • DSPEXOPM block
  • VFYWSPAC block
  • DSPOCPAG block
  • DSPJCLAR block
  • GDBGPDAR block
  • GDBRUPAR block
  • GDBOLCAR block
  • GDBMNPTR block
  • GDBESAVE block
  • GDBISAVE block
  • GDBCSAVE block
  • GDBRSAVE block
  • DSPCMPAG block
  • DSPVFILE block
  • DBRC Internal Trace

Output is the same if (DBRC,MIN) is specified. DBRC blocks must be present in the dump data set to be formatted.

DC
Formats the data communication areas listed in the following table. This option is skipped if the CTL address space is not included in the dump data set.
Table 2. Data communication areas formatted by DC and DC,MIN
(DC) (DC,MIN)1
All CLBs, LXBs, and LCBs, with subordinate control blocks:
  • Current CTB or LTB, and CNT
  • Allocated I/O buffers
  • CIB, if using MFS processing
  • CCB, if using conversational processing
  • MFS work buffers
  • ECNT, EMHB, and message buffer, if the CTB shows a Fast Path terminal
 Active CLBs, LXBs, and LCBs, with the same subordinate control blocks except that current CTB or LTB and CNT are not formatted.
SMB table not formatted
CTT table not formatted
SPQBs and the CNTs chained off unallocated SPQBs not formatted
Note:
  1. (DC,MIN) formats control blocks only for those lines, nodes, and links that meet at least one of the following criteria:
    1. MSC links
    2. Nodes in OPNDST or CLSDST processing
    3. Lines or nodes with allocated input, output, or receive any buffers
    4. CLBs that have an active SAP

Both DC options are ignored for batch.

DEDB
Formats the DEDB control blocks and areas. The areas included are listed in the following table.
Table 3. DEDB control block areas formatted by DEDB and DEDB,MIN
(DEDB) (DEDB,MIN)
ALDS same
DMCBs, SGTs, FDTs, and MRMBs for open DEDBs same
DMACs and ADSC for open DEDB areas same
XCRBs, DMHRs, and buffers XCRBs and DMHRs only
SRBs and ESRBs same
DISPATCH
Formats areas relating to the IMS Dispatcher and its functions. The following table shows the areas formatted under this FMTIMS option.
Table 4. Areas formatted by DISPATCH and DISPATCH,MIN
(DISPATCH) (DISPATCH,MIN)
Dispatcher work areas not formatted
Dispatcher Trace same
Scheduler Trace not formatted
Latch Trace same

(DISPATCH,MIN) is ignored for batch.

DPST,jobname
DPST,N,dependent region number
DPST,A,address
Permits formatting of an individual Dependent Region Partition Specification Table and its subordinate blocks for PSTs related to MPPs, BMPs, IFPs, and batch DL/I. You can specify one of the following choices:
  • job name
  • Dependent region number
  • DPST address
Output follows the DB formatting output in the dump formatter. The eye catchers and index entries appear as follows: 
**DPSTS                REQUESTED DPSTS
EMH
Formats the Expedited Message Handler areas that are used by IMS Fast Path, as shown in the following table. The CTL address space must be included in the dump data set for this option to be formatted.
Table 5. Areas formatted by EMH and EMH,MIN
EMH EMH,MIN
RCTEs same
BALGs, EMHBs, and message buffers BALGs and EMHBs only
LOG
Formats control blocks and areas used by the IMS logger. The areas included shown in the following table. These areas, except for the WADS and the DLOG trace, are repeated in the dump when the IMS Monitor is active.
Table 6. Areas formatted by LOG and LOG,MIN
LOG LOG,MIN
LCD same
Restart Log Work Area same
WADS and the data necessary to manage it WADS only
OLDS prefix and the buffer associated with it OLDS prefix only
Log DSET, which defines all OLDS currently available for use same
Message work areas and Logger message areas same
DLOG trace same
MSDB
Formats the Main Storage Databases used by IMS Fast Path. The areas included are listed in the following table.
Table 7. Main storage databases formatted by MSDB and MSDB,MIN
MSDB MSDB,MIN
MSDB headers same
all MSDBs not formatted
POOL, NAME, poolid
Invokes formatting of the storage manager control blocks and the pool storage for any of the following pools:
  • AIOP
  • ALL
  • CESS
  • CIOP
  • CMDP
  • DBWP
  • DLDP
  • DLMP
  • DPSB
  • DYNP
  • EMHB
  • EPCB
  • FPWP
  • HIOP
  • MFBP
  • PSBW
  • QBFL
  • QBUF
  • SPAP
  • LUMC
  • LUMP

NAME is an optional keyword indicating the pool name parameter. If NAME is omitted, the first parameter is assumed to be the pool name.

The poolid is a required 4-character pool name of an existing storage manager pool or the keyword ALL. If ALL is specified, the following storage pools are formatted:

  • AIOP
  • HIOP
  • CIOP
  • CMDP
  • CESS
  • DYNP
  • SPAP
  • EMHB
  • FPWP
  • QBUF
  • QBFL
  • DLMP
  • DPSB
  • DBWP
  • MFBP
  • EPCB
  • LUMP
  • LUMC

ALL triggers the formatting of any storage manager trace table entries along with the storage manager control blocks and pool storage.

MIN is an optional keyword. If MIN is specified for one of the dynamic pools (AOIP, CESS, CIOP, CMDP, DYNP, EMHB, FPWP, HIOP, LUMC, LUMP, or SPAP) only the storage manager pool header and block headers are formatted. If MIN is omitted, the pool header control block is formatted, along with the blocks and block headers that represent the dynamic storage pool.

QM
Formats the control blocks and areas of the IMS queue manager. The formatter skips this option if the CTL address space is not included in the dump data set. The areas included are shown in the following table.
Table 8. Areas formatted by QM and QM,MIN
QM QM,MIN
Qpool Prefix same
Qpool Buffer Prefix same
Qpool Buffer not formatted

Both QM options are ignored for batch.

RESTART
Formats the IMS restart control blocks and related areas, including:
  • Checkpoint ID table
  • SIDXs and their subordinate blocks:
    • All LCREs for the SIDX entry being processed
    • All RREs for the SIDX entry being processed
  • All RPSTs for the SIDX entry being processed
  • FRB, if present

Output is the same if (RESTART,MIN) is specified. Both RESTART options are ignored for batch.

SAP, ECBADR, ecbaddr
SAP, ADDRESS, sapaddr
The SAP option can be invoked using either the SAP address or the SAP's ECB address (providing that the ECB is a valid ITASK and has a prefix pointing to a SAP). The SAP option request can be placed either on the IMSDUMP verb line after FMTIMS or in the DFSFRMAT data set. The following examples show SAP option requests: 
VERBX IMSDUMP'imsjname,II,N,FMTIMS (SAP,ADDRESS,20864C0)'
VERBX IMSDUMP'imsjname,FMTIMS SCD,(SAP,ECBADR,3064250)'

For compatibility reasons, the MIN qualifier is allowed, but the output is the same. Individual SAP option formatting is also available on the IMS Low Level panel of the IMS IMS Dump Formatter dialog. The ADDRESS parameter can be omitted because ADDRESS is the default TYPE for the SAP option.

Individual SAP/save area formatting allows complete formatting of SAP/save areas when additional information is required. The output from individual SAP formatting is the same as the SAVEAREA option output. Individual SAP formatting provides the following eye catcher/index entry: 
**SAPS      REQUESTED SAPS
SAVEAREA
Formats the save area information, including:
  • Formatted SAPs and any UEHBs anchored off the SAPs.
    Restriction: The UEHBs cannot be formatted if the CTL address space is not included in the dump data set.
  • Formatted Save Area Sets associated with each SAP.
  • Unformatted dump of the IPAGEs containing the SAPs.

If the DL/I address space is not in the data set, then the DL/I SAPs are not formatted. If the CTL address space is not in the data set, then the non-DL/I SAPs are not formatted. Output is the same if (SAVEAREA,MIN) is specified. Both SAVEAREA options are ignored for batch.

The SAVEAREA also comes with a summary option that allows a faster overview scan of the IMS ITASK status within a dump. The SAVEAREA SUMmary output reduces the SAP/Savearea formatting to minimal data while adding keyword scan capability and automatic computation of the exit offsets. This reduces keystroke resources required to overview the ITASK status and ITASK module flow. The SAVEAREA SUMmary and individual SAP formatting provides the following eye catcher/index entry: 
**SSS       SAP/SAVE CONDENSED SUMMARY
SAVEAREA Summary formatting contains the following scannable keywords with their associated meanings:
RUN
ITASKs that are active are given a RUN indicator. Abend and loop analysis is usually concerned only with running ITASKs.
LATCHREQ
ITASKs that are waiting for an IMS SLX latch (not checkpoint restart LATE latches) are given a LATCHREQ indicator. Enabled wait problem analysis often requires analyzing ITASKs that are waiting for latches.
LATCHOWN
ITASKs that own an IMS SLX latch (not checkpoint restart LATE latches) are given a LATCHOWN indicator. Enabled wait problem analysis often requires analyzing ITASKs that own SLX latches.
ITASK type
The ITASK type is in the summary and is scannable. The ITASK type names are not at the end of the scan list, however. The ITASK type is preceded by the label type. The possible type names can be gotten from the DFSCIR macro prolog.
SB
Formats the control blocks, areas, and buffers of the Sequential Buffering function (SB) of IMS. This option also formats those DL/I control blocks which are important for debugging the SB function.
The SB information is divided into four sections. The following table shows which sections are formatted with the SB and SB,MIN options.
Table 9. Sections formatted by SB and SB,MIN
SB SB,MIN
Subsystem overview same
PST overview1 same2
Sorted blocks1 same2
Sorted buffers1 not formatted
Note:
  1. The DL/I address space must be included in the dump data set for these areas to be formatted.
  2. Formatted only if you requested a conditional SB activation for that application or PST.

The SB information is divided into the following sections:

  1. Subsystem Overview of SB—provides an overview of SB control blocks from an IMS subsystem point-of-view. The SDCBs appear in the order in which they are anchored in the SBSCD. Each SDCB is followed by its SDSGs. The section contains the following information:
    • SB section of the SCD
    • SBSCD, including the SBHE blocks
    • SDCBs
    • SDSGs
  2. PST Overview of SB—formats the SB control blocks (and other IMS control blocks significant to SB) for each active PST. These blocks are sorted in hierarchical order. For example, the first DBPCB and its JCB, DSGs, EDSGs, and SDSGs; then the second DBPCB with its subordinate blocks, and so on. The section contains the following information:
    • SB and buffer-handler sections of the PST
    • PST DECB prefix
    • SB extensions to the PST
    • SB work area
    • SBPARMS
    • DBPCBs and their JCBs, DSGs, EDSGs, and SDSGs
  3. Sorted SB Blocks—contains SB control blocks (and other IMS control blocks significant to SB) sorted according to their virtual storage address. The section contains the following information:
    • DBPCBs
    • DCB with its OSAM extensions
    • DSGs
    • EDSGs
    • JCBs
    • OV-IO DECB prefix
    • PST DECB prefix
    • SB extensions to DCBs
    • SB extensions to DSGs
    • SB extensions to the PST
    • SB work area
    • SBPARMS
    • SBUFs
    • SCARs
    • SRANs
  4. Sorted SB Buffers—contains the SB buffers of each SB buffer pool. The SB buffers of one SB buffer pool are contiguous in storage and are formatted as one entity. The buffer pools are then sorted by virtual storage address.
SCD
Formats the IMS SCD and related areas. The areas included are listed in the following table.
Table 10. Areas formatted by SCD and SCD,MIN
(SCD) (SCD,MIN)
SCD same
Latch Extensions same
Scheduler Sequence Queues not formatted
Synchronous APPC/OTMA Shared Message Queue SCD Extension same
Fast Path SCD Extension, if Fast Path is active same
Formatted dumps of the batch key 7 SCD same
LU 6.2 SCD extension same
SPST
Formats the system PSTs, which are ITASKs used by IMS. This includes:
  • Global system PSTs
  • Local control region address space PSTs
  • Local DL/I address space PSTs
  • Areas related to the above PSTs, including LWA and IRLMA

Some SPSTs are not formatted if the CTL address space is not in the dump data set. Output is the same if (SPST,MIN) is specified. Both SPST options are ignored for batch.

SUBS
Formats the areas and control blocks that IMS uses to manage subsystems, including:
  • Subsystem trace
  • Global ESET block

Output is the same if (SUBS,MIN) is specified. Both SUBS options are ignored for batch.

SUMMARY
Formats the current diagnostic section.

The SUMMARY data areas are not formatted if the SDWA address space is not part of the dump data set. (For abends and batch processing, the SDWA address is saved by the ESTAE module. For online processing, the dump must be taken by DFSOFMD0, and the SDWA parameter must be passed at DFSDUMP time.)

The areas formatted with this option include:

  • Failing PSW
  • Abend code
  • Module name
  • Registers at time of abend
  • 256 byte instruction area—128 bytes above and below the failing PSW
  • 16 register storage areas—512 bytes above and 256 bytes below the registers at time of abend
  • SDWA address space of IMS
  • Failing SAP and its UEHB
  • Failing ITASK when the ITASK is a DPST, system PST, CLB, or LLB (dependent region errors, some systems services errors, terminal process errors, and MSC errors)

    The SUMMARY option names the ITASK type when it is determined, even if it is not one of the ITASK types that provide for additional formatting. The ITASK type name is two to four characters. If it is unknown, the type name is UNKN.

Output is the same if (SUMMARY,MIN) is specified.

SYSPST
Permits formatting of an individual system partition specification table and some of its subordinate blocks. Select this option by address or system PST name. This option creates eye catchers and index entries similar to the following: 
**SYSPSTS                 REQUESTED SYSTEM PSTS
SYSTEM
Formats the SUMMARY, SAVEAREA, and SCD areas as one group. The areas and control blocks formatted are the same as if each of the options were invoked separately.

(SYSTEM,MIN) is formatted as though each of the options were specified with MIN.

See the individual options for a list of the areas formatted.

TRACE, NAME, table-id
Gets a new search module that invokes the normal trace format control module (DFSATRA0) to format trace tables separately. This option enables viewing of trace table data without having to format the entire option that usually includes the formatted trace table. The TRACE option request uses the 2-character trace table EBCDIC ID code from the Trace Selection panel. The IMS Dump Formatter ISPF panels also accept an option of ALL to format all IMS trace table traces. The IMS Dump Formatter dialog TRACE SELECTION panel provides a selectable list of IMS trace tables with the trace name, internal ID, and description. The following examples are TRACE format requests, followed by comments for each. In each case, the NAME keyword can be omitted because NAME is the default TYPE parameter. The following example is a request for the DL/I trace table. 
FMTIMS...(TRACE,NAME,DL),...
The following is a request for the dispatcher trace table and the DL/I trace table with a MIN option that is ignored. 
FMTIMS...,(TRACE,NAME,DL,MIN),(TRACE,NAME,DS)...
UTIL
Formats the control blocks for the IMS Partial Database Reorganization utility, including:
  • Common area
  • Database table
  • Segment table
  • Action table

The output is the same if (UTIL,MIN) is specified. Both UTIL options are ignored for batch.