GDSX Manual

Design and Development
Extended General Device Support (GDSX) Manual–134303
2-75
Tracing GDSX
names; change $term-name to the name of the device where you want the messages to
be displayed. Then issue the following command at any terminal:
> OBEY $vol.subvol.LOADFILT
The EMS filter compiler runs at that terminal. When the compiler finishes, the cursor is
at the bottom left corner of the screen.
If you ran the LOADFILT file at a terminal other than the one where you want GDSX
messages to be displayed, press the Break key at the terminal where you issued the
OBEY command, and type in PAUSE at the display terminal. (If you ran the
LOADFILT file at the display terminal, no extra steps are necessary.)
To check if all is in order, you can start up a GDSX process. A START GDS event
message should be displayed.
Tracing GDSX
GDSX allocates an extended segment for a trace when a request is received to start a
trace. After the trace file is open, depending on settings of auto^trace^flag and the
trace^control^flags, as the GDSX process runs, TSCODE automatically generates trace
entries for the file. (You can also generate trace entries by calling ADD^TRACE^DATA
or ADD^TRACE^DATA^INT.)
GDSX deallocates the trace segment when a request is received to stop the trace. Once
the trace has been stopped, PTrace is used to display the trace records.
Here is an example of tracing a GDSX process and displaying the trace records:
1. Start a named GDSX process, $GDSX, for example:
> RUN GDSE /NAME $GDSX, NOWAIT/
2. Start an interactive SCF process:
> SCF
3. Issue an SCF TRACE command to trace all significant events (SELECT ALL)
occurring during execution of $GDSX and write the records to a file named
TRCFILE:
-> TRACE PROCESS $GDSX, TO TRCFILE, SELECT ALL
This SELECT option sets all the trace^control^flags to 1.
4. When GDSX processing is done, stop the trace session:
-> TRACE PROCESS $GDSX, STOP
-> EXIT
5. Run the PTrace utility to display all records in the file TRCFILE:
> PTRACE
? FROM TRCFILE
? OCTAL ON
? RECORD ALL