Subsystem Control Point (SCP) Management Programming Manual

Tr ac ing
Subsystem Control Point (SCP) Management Programming Manual—520619-001
B-8
The Trace Information Structure
The Trace Information Structure
Requesters include the extensible structured token ZTRC-MAP-TRACE-MODIF in
TRACE commands to specify the details of the trace. ZTRC-MAP-TRACE-MODIF is
based on ZTRC-DDL-TRACE-MODIF:
ZSTOP
specifies whether the command starts, modifies, or stops a trace. Valid values are:
ZPRIM
specifies the path to be traced. Valid values are:
ZREC-SIZE
specifies the size of the trace record, in bytes. Valid values are:
def ZTRC-DDL-TRACE-MODIF.
02 ZSTOP type ZSPI-DDL-BOOLEAN.
02 ZPRIM type ZSPI-DDL-BOOLEAN.
02 ZREC-SIZE type ZSPI-DDL-INT.
02 ZCNT type ZSPI-DDL-INT2.
02 ZXDS-PAGES type ZSPI-DDL-INT.
02 ZCOLL type ZSPI-DDL-BOOLEAN.
02 ZFNAME type ZSPI-DDL-FNAME32.
02 ZWRAP type ZSPI-DDL-BOOLEAN.
end.
ZSPI-VAL-TRUE The tracing process stops the trace.
ZSPI-VAL-FALSE or blank If ZFNAME contains a file name, SCP or the tracing
process initiates a trace. If ZFNAME is blank, SCP or
the tracing process modifies the existing trace.
ZSPI-VAL-TRUE or blank Trace the primary path.
ZSPI-VAL-FALSE Trace the backup path.
0 When modifying a trace (that is, if ZFNAME is blank), the current
record size is retained. When starting a trace (ZFNAME contains a
file name), the default record size of 120 bytes is used.
16 through 4050 The record size is set to the specified number of bytes.