GDSX (Extended General Device Support) Manual

Design and Development
Extended General Device Support (GDSX) Manual—529931-001
2-89
Examining the Trace
entries wrap is 4096. Calls to ADD^TRACE^DATA and ADD^TRACE^DATA^INT can
change the maximum number of records that can be generated for the TRACE file
before the entries wrap.
The TRACERECSIZE dynamic configuration parameter specifies the maximum size of
each record added to the trace file. The default for this size is 256 words. The
maximum record size can also be specified in a call to USER^OPEN^TRACE^FILE. If
the record size specified by the TRACERECSIZE configuration parameter differs from
that specified in a call to USER^OPEN^TRACE^FILE, the latter value has precedence.
Once a trace has been initiated, the set of trace classes for which trace records are
being generated can be changed. This is done within USCODE by setting
trace^control^flags or the equivalent DEFINE text. Trace classes cannot be changed
within SCF without first stopping the trace.
The trace can be stopped in two ways:
•
USCODE can call USER^CLOSE^TRACE^FILE to close the trace file in extended
memory. If USER^CLOSE^TRACE^FILE is called, all trace flags are set to zero,
the trace file is saved, and the extended segment for the trace is deallocated.
Then TSCODE does not generate trace entries for the file, and USCODE is not
allowed to generate trace entries for the file by calls to ADD^TRACE^DATA or
ADD^TRACE^DATA^INT. (See Section 8, Service Routines for detailed
information on this procedure.)
•
You can issue the following SCF command at the SCF prompt:
-> TRACE PROCESS $GDSX-process-name, STOP
When a trace STOP request is received by TSCODE, all trace flags are set to zero, the
trace file is saved, and the extended segment for the trace is deallocated.
Examining the Trace
Before you can display the trace data, the trace file must be closed. To examine trace
files created by GDSX, you use the PTrace utility. PTrace extracts data stored in
unstructured trace files and formats the data for output to terminals, printers, and disk
files.
The following is an example of using the PTrace formatter:
> RUN PTRACE
Ptrace - Trace Formatter-T9385C20- (10JUL89) -(092509)
? FROM TRACEP; OCTAL ON
? RECORD 1/10
? RECORD ALL ! The ALL command lists all records
? OUT TO $S.#LP1; RECORD ALL
? EXIT
PTrace supports standard commands for display of GDSX trace files. The SELMASK
command combined with the SELECT command may be used to select sets of trace
records within a trace file. The FILTER and TEXT commands are not supported.