GDSX Manual

Design and Development
Extended General Device Support (GDSX) Manual–134303
2-82
Turning On the Trace Facility
3. Open the trace file with the USER^OPEN^TRACE^FILE procedure. This
procedure causes TSCODE to allocate an extended segment for a trace file, which is
saved as TRACEP by a primary process or as TRACEB by a backup process. After
the trace file is open, depending on the settings of auto^trace^flag and
trace^control^flags, TSCODE automatically generates trace entries for the file. You
may also generate trace entries by calling ADD^TRACE^DATA or
ADD^TRACE^DATA^INT.
4. Issue an SCF command to start the trace. For example:
-> TRACE PROCESS $GDSX, SELECT SRMISC, TO MYTRACE
generates trace records for the SRMISC trace class. SCF requires a trace file name.
In this example, the trace file is named MYTRACE and is saved in the subvolume
where SCF is running.
The command:
-> TRACE PROCESS $GDSX, SELECT ALL, TO MYTRACE
traces all TSCODE events described in Table 2-6 and all USCODE-defined events.
The trace classes are defined by means of the SELECT option:
SELECT select-spec
where select-spec is one of the following specifications:
{ keyword }
{ ( keyword [ , keyword ] ... ) }
To view trace options settings, enter:
-> HELP GDS TRACE PROCESS
See the SCF Reference Manual for GDSX for the complete syntax of the TRACE
PROCESS command.
Table 2-7. Events Traced by USAMPLE (page 1 of 2)
SCF Trace
Class Keyword
Equivalent
trace^control^flags
DEFINE USCODE Events Traced by USAMPLE
TERMREQ TERM^REQ^TRACE Traces terminal requests
TERMDATA TERM^DATA^TRACE Traces terminal data
TERMINTL TERM^INTR^TRACE Traces internal activities within a
DEVICE^HANDLER task
LINEREQ LINE^REQ^TRACE Traces line requests
LINEDATA LINE^DATA^TRACE Traces line data
LINEINTL LINE^INTR^TRACE Traces internal activities within a
LINE^HANDLER task
SRCB SR^CB^TRACE Traces USCODE control block resources