When GTF trace is on, and the CICS® master trace flag is also on, CICS writes trace entries to a GTF data set. CICS writes these records by issuing the GTRACE macro with the following parameters specified:
You can print CICS trace entries written to GTF by invoking IPCS with the GTFTRACE subcommand, and specifying the USR parameter with the event trace identifier of the records you want IPCS to select for formatting. You can also specify most of the DFHTU640 selective trace control statements on the CICS(text) parameter. The CICS-supplied formatting routines are called DFHTG640 and DFHTR640, supplied in CICSTS31.CICS.SDFHLINK. DFHTG640 has the alias of AMDUSREF. The last two characters of the AMDUSREF alias ("EF") correspond to the format identifier (FID), and enable IPCS to invoke the CICS formatting routine automatically when you use the GTFTRACE subcommand.
Several CICS regions, at different CICS releases, can write to the same GTF data set. You can print GTF trace entries written to GTF using the same GTFTRACE command. To do so, you must make available the formatting routine for each CICS release. For example, for CICS Transaction Server for z/OS®, Version 3 Release 1, you would need to specify DFHTG640, its alias AMDUSREF, and DFHTR640.
To use IPCS to format and print CICS trace entries, you must specify the GTFTRACE subcommand. The following are the main IPCS GTFTRACE parameters that you need to process CICS trace entries:
Specify ALL to request formatting of all subsystem trace entries.
There are many other parameters that you can specify on the GTFTRACE subcommand of IPCS. For information about the GTFTRACE command, see the z/OS MVS IPCS Commands .
You can specify the GTFTRACE subcommand of IPCS in TSO, or in a batch job as shown in Figure 26.
//IPCSGTF JOB ( accounting info),
// CLASS=A,MSGCLASS=H,MSGLEVEL=(1,1),NOTIFY=userid
//PRINTTR EXEC PGM=IKJEFT01,REGION=4096K
//STEPLIB DD DSN=CICSTS31.CICS.SDFHLINK,DISP=SHR 1
// DD DSN=CICSTS23.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
/*
//
Notes: 1 The batch job in Figure 26 includes a STEPLIB statement for the load libraries that contain the modules (DFHTG640, its alias AMDUSREF, DFHTR640, DFHTG640, its alias AMDUSREF and DFHTR640) to be used to format the GTF trace entries. Depending on which releases of CICS have GTF trace entries to be printed, you should include the following libraries in the STEPLIB concatenation:
STEPLIB | CICS releases to be formatted |
---|---|
CICSTS31.CICS.SDFHLINK | CICS Transaction Server for z/OS, Version 3 Release 1 only. |
CICSTS31.CICS.SDFHLINK CICSTS23.CICS.SDFHLINK |
|
CICSTS31.CICS.SDFHLINK CICSTS22.CICS.SDFHLINK |
|
CICSTS31.CICS.SDFHLINK CICSTS13.CICS.SDFHLINK |
|
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 32.
To enable the CICS formatting routines to be invoked from TSO, copy the modules DFHTG640, AMDUSREF, DFHTR640, and DFHTRVR3 to a suitable library in the MVS™ linklist, or ensure that the CICS libraries listed above are included in the MVS linklist.
Ensure that you have sufficient TSO storage (specified for your TSO userid when you logon) for GTF trace formatting, because otherwise storage fragmentation causes formatting problems. When using one job to format trace entries for several CICS releases, the loading of the multiple release formatters needed uses more storage.