Job control statements for the transaction dump utility program (DFHDUnnn)

To process CICS® transaction dump data, you must use the CICS transaction dump utility program that matches the CICS release level of the dump. For example, to process CICS TS beta transaction dump data, you must use DFHDU760. The job to run the transaction dump utility program must include an input and output data set. You can optionally include a SYSIN data set where you specify a selection of the dumps that you want printed. A sample JCL is provided to help you develop your own job to run the transaction dump utility program.

Required and optional data sets to be included

The job stream to run the CICS transaction dump utility program should include DD statements for the following data sets:
DFHDMPDS (mandatory)
The input data set, from which the dump data is to be processed.
DFHPRINT (mandatory)
The output data set, usually a printer, to which the dump data is written.
DFHTINDX (optional)
The output data set to which the dump index summary is written, needed if you want the index summary output. If you omit the DFHTINDX DD statement, the transaction dump utility program tries to open a SYSPRINT data set for dump index output. If it is unsuccessful, you get message IEC130I, and the dump index summary is not written.
SYSIN (optional)
The SYSIN data set in which you define the control statements for the transaction dump utility program, needed if you want to code specific selection parameters. If you omit the SYSIN DD statement, you get message IEC130I. See Format of the SYSIN control statements for the transaction dump utility program (DFHDUnnn).

Sample JCL

The following example is a sample job stream for the DFHDU760 program.
Figure 1. Sample job to format and print CICS transaction dump data sets
//PRNTDMP  JOB  accounting info,name,MSGLEVEL=(1,1),
//              CLASS=A,MSGCLASS=A,REGION=2M             1 
//         EXEC PGM=DFHDU760,PARM='command,command,...'  2 
//STEPLIB  DD   DSN=CICSTS64.CICS.SDFHLOAD,DISP=SHR      3 
//DFHDMPDS DD   DSN=CICSTS64.CICS.DFHDMPA,DISP=SHR
//DFHTINDX DD   SYSOUT=A
//DFHPRINT DD   SYSOUT=A,DCB=(BLKSIZE=133)
//SYSPRINT DD   SYSOUT=A
//SYSIN    DD   *
 SELECT TYPE=OR
 [selection parameters, each on a separate line]
 END
/*
//
  1. The sample JCL gives a region size of 2 MB that you might typically need to run the transaction dump utility program. You can use the sample region size as a basis for your own JCL, but must ensure that the region size is large enough to run this utility program in your CICS environment.
  2. The PARM options of the EXEC statement are as follows:
    NOABBREV
    Prevents the trace entries from being formatted in the abbreviated format in the transaction dump.
    NOFULL

    Prevents the trace entries from being formatted in the full format in the transaction dump.

    Trace formatting may be suppressed by using both the NOABBREV and NOFULL options. The default action is that the trace is printed in ABBREVIATED followed by FULL formats (see the ABBREV and FULL keywords of the CICS trace utility program, DFHTUnnn for details).

    Note: ABBREV and FULL are not valid keywords of the transaction dump utility program.
    DOUBLE|SINGLE
    For SINGLE, the transaction dump output is printed single-spaced.
    For DOUBLE the output is printed with a blank line between the printed lines.
    TRANSLATE=LC|FOLD|UC
    For LC, lowercase letters are printed as lowercase and uppercase letters as uppercase in the interpreted output on the right side of the dump output.
    For FOLD, all lowercase letters are converted to uppercase in the interpreted output.
    For UC, only the uppercase letters are printed in the interpreted output.
  3. To run the transaction dump utility program concurrently with CICS to process the inactive disk transaction dump data set, specify DISP=SHR in the DD statements defining the transaction dump data sets in the startup job stream.