Troubleshooting the SLSA Subsystem

TRACE [ / OUT <file> / ]
{ MON <lanmon> | PIF | PROCESS | SAC }
{ , STOP }
[ , BULKIO | NOBULKIO ]
[ , COUNT <count> ]
[ , LOCKSIZE <locksize> ]
[ , NOCOLL ]
[ , PAGES <pages> ]
[ , RECSIZE <size> ]
[ , SELECT <selectspec> ]
[ , TO <filespec> ]
[ , WRAP ] ... }
Note: If TO <file-spec> is specified, a new trace is initiated unless <file-spec> is invalid,
the file cannot be opened, or a trace is already active for the object. If TO <file-spec> and
STOP are both omitted, the TRACE command modifies the trace currently in progress, if
any. If TO <file-spec> is omitted and STOP is specified, the TRACE command stops the
trace currently in progress, if any.
OUT <file> causes any SCF output generated for this command to be directed to the
specified file.
<lanmon> specifies the LAN monitor process to be traced.
STOP discontinues a trace currently in progress.
BULKIO | NOBULKIO specifies whether the trace should use bulk I/O. BULKIO reduces
the number of missing frame errors reported by PTrace. A limitation of BULKIO is that only
one user can access the file at a time.
<count> specifies the number of trace records that can be captured. If <count> is omitted
or is -1, records are accumulated until the trace is stopped.
<locksize> designates how much memory space, in units of pages, is locked down at one
time. <locksize> must be less than or equal to <pages> and be in the range 4 through
1024. If PAGES is not specified, <locksize> must be less than or equal to 64. If LOCKSIZE
is omitted, <locksize> is the lesser of <pages> and 64.
NOCOLL specifies that the trace data from the extended segment is written to the disk file
specified in TO <filespec> only when one of the following occurs:
The trace is stopped.●
The number of trace records written to the extended data segment equals the count
specified in the SCF TRACE command that started the trace. If NOCOLL is not
specified, a trace collector process reads the trace records from the extended data
segment and writes them to the disk file as they become available.
●
<pages> designates how much space, in pages, is allocated in the extended data segment
used for tracing. PAGES can be specified only when a trace is being initiated. <pages> is