Starting GTF without trace options in a member

Figure 1 shows an installation-written procedure where there is no predefined member with trace options specified. The procedure contains no SYSLIB DD statement. When GTF is started with a procedure containing no SYSLIB DD statement, message AHL100A is issued to prompt for GTF trace options.

In this example, an installation-written cataloged procedure, USRPROC, is invoked to start GTF in external mode to a direct access data set, ABCTRC, on device 250. The trace options selected result in trace data being gathered for:

All SVC and IO interruptions
All SSCH operations
All matching SLIP traps with a tracing action specified or SLIP traps in DEBUG mode
All dispatcher events
All issuers of the GTRACE macro will have their user data recorded in the trace buffers.

The trace data is written into the data set ABCTRC. (Note that when the end of the primary extent is reached, writing continues at the beginning.)

Figure 1. Example: Starting GTF without trace options in a member

START USRPROC,250,333005,(MODE=EXT),DSN=ABCTRC


00 AHL100A SPECIFY TRACE OPTIONS
 
REPLY 00,TRACE=SVC,SSCH,IO,DSP,SLIP,USR
 
AHL103I TRACE OPTIONS SELECTED--USR,DSP,SVC,IO,SLIP,SSCH
 
01 AHL125A RESPECIFY TRACE OPTIONS OR REPLY U
 
REPLY 01,U
 
AHL031I GTF INITIALIZATION COMPLETE