Sample batch job to print CICS GTF trace entries

You can print CICS GTF trace entries by specifying the GTFTRACE subcommand of IPCS in TSO, or in a batch job as shown in this example.

Figure 1. Sample IPCS job to print CICS trace entries from a GTF data set
//IPCSGTF  JOB ( accounting info),
//             CLASS=A,MSGCLASS=H,MSGLEVEL=(1,1),NOTIFY=userid
//PRINTTR  EXEC PGM=IKJEFT01,REGION=4096K
//STEPLIB  DD DSN=CICSTS55.CICS.SDFHLINK,DISP=SHR             1 
//         DD DSN=CICSTSnn.CICS.SDFHLINK,DISP=SHR
//DFHTRACE DD DSN=GTF.TRACEnn,DISP=SHR
//IPCSDDIR DD DSN=ipcs.dump.directory,DISP=SHR           2 
//SYSABEND DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//IPCSPRNT DD SYSOUT=*
//SYSTSIN  DD *
IPCS NOPARM
SETDEF DD(DFHTRACE) NOPROBLEM PRINT NOCONFIRM NOTERMINAL LIST
PROFILE PAGESIZE(60)
GTFTRACE +
CICS((ABBREV,TERMID=LP1,TRANID=<ABRW,AORD>,)) +
CICS((TYPETR=(SM01FF-03BC),TASKID=(J01,J03-J05,TCP))) +
USR(F6C)
END
/*
//
Note:
  1. The batch job in Figure 1 includes a STEPLIB statement for the load libraries that contain the modules (DFHTG710, its alias AMDUSREF, DFHTR710, DFHTG710, its alias AMDUSREF and DFHTR710) to be used to format the GTF trace entries. It also includes CICS TSnn.CICS.SDFHLINK where nn denotes an earlier release of CICS if you require to format GTF trace entries from earlier releases.
  2. The IPCSDDIR statement specifies a directory data set needed by IPCS. A sample job to create an IPCS directory data set is given in Figure 1.