Starting GTF with trace options stored in SYS1.PARMLIB

Figure 1 shows how to store trace options in a member of SYS1.PARMLIB. This can save you time when starting GTF. First store one or more combinations of trace options as members in SYS1.PARMLIB, and include a SYSLIB DD statement in the cataloged procedure. When you start GTF, GTF will then retrieve the trace options from SYS1.PARMLIB, instead of prompting you to supply them through the console. GTF displays the trace options for you, and then issues message AHL125A, to which you can reply U to accept the parmlib options.

This example shows the job control statements and utility JCL statements needed to add trace options to SYS1.PARMLIB using IEBUPDTE.

Figure 1. Example: Starting GTF with trace options stored in SYS1.PARMLIB

 //GTFPARM    JOB     MSGLEVEL=(1,)
 //           EXEC    PGM=IEBUPDTE,PARM=NEW
 //SYSPRINT   DD      SYSOUT=A
 //SYSUT2     DD      DSNAME=SYS1.PARMLIB,DISP=SHR
 //SYSIN      DD      DATA
 ./       ADD    NAME=GTFA,LIST=ALL,SOURCE=0
 TRACE=SYSP,USR
 SVC=(1,2,3,4,10),IO=(D34,D0C),SSCH=ED8,PI=15
 ./       ADD    NAME=GTFB,LIST=ALL,SOURCE=0
 TRACE=IO,SSCH,TRC
 ./       ADD    NAME=GTFC,LIST=ALL,SOURCE=0
 TRACE=SYS,PCI
 /*

A sample SYSLIB DD statement to be included in a GTF cataloged procedure might look like this:

//SYSLIB DD DSN=SYS1.PARMLIB(GTFA),DISP=SHR

The new member name can also be specified on the START command while using the IBM-supplied GTF procedure, as in the following example:

S GTF,,,(MODE=EXT,TIME=YES),MEMBER=GTFB

For more information see the following references:

See z/OS DFSMSdfp Utilities for descriptions of the statements.
See z/OS MVS JCL Reference for descriptions of the statements.
See z/OS MVS Initialization and Tuning Reference for further information about SYS1.PARMLIB.