SNAX/HLS Management Programming Manual

Standard SNAX/HLS Definitions
Common Definitions
6–56 104708 Tandem Computers Incorporated
ZHLS–MAP–TRACE–OPT
This extensible structured token is used to control and report the tracing functions
within the process. This token occurs in the TRACE command and in the response to
the INFO command both for the SNAX/HLS process and for sessions.
def ZHLS–DDL–TRACE–OPT.
05 ZSNAX type ZSPI–DDL–BOOLEAN.
05 ZDFC type ZSPI–DDL–BOOLEAN.
05 ZLUSVM type ZSPI–DDL–BOOLEAN.
05 ZVERBS type ZSPI–DDL–BOOLEAN.
end.
When applied to the SNAX/HLS process, the values in this token are used as default
values assigned to each newly allocated session. This makes it possible to activate
tracing with session creation. Changing these values has no effect on existing sessions;
it has an effect only on sessions allocated thereafter.
When applied to individual sessions, the values in this token specify which events
contribute data to the trace records. This tracing is effective only if the tracing facility
has been enabled for the process.
ZSNAX
specifies whether traffic to and from the Tandem SNA access method, (SNAX/XF,
for example) should be traced. This is data sent to and received from the SNALU
interface.
ZDFC
specifies whether data processed by the data flow control (DFC) layer of SNA
should be traced. This tracing of data flow control provides a before and after
picture of the finite state machines that constitute the heart of the DFC layer.
ZLUSVM
specifies whether data processed by the LU Service Manager should be traced.
This level includes most of the high–level functions undertaken on behalf of the
application requests.
ZVERBS
specifies whether verb requests and responses should be traced. The only verb
missed is the verb request that allocates the session (with OPEN–SESSION or
HLS–ALLOCATE).