SNAX/HLS Management Programming Manual

Standard SNAX/HLS Definitions
Common Definitions
6–20 104708 Tandem Computers Incorporated
When interpreted in the ZHLS–MAP–STATUS–SESS–SEND token, this field refers
to the sender of the SBI request. When interpreted in the
ZHLS–MAP–STATUS–SESS–RECV token, it refers to the receiver of the SBI
request. This field can have the following enumerated values:
ZHLS–VAL–FSM–SBI–NOBB
indicates that the response to the BIS request has been processed. The implied
half session has agreed not to begin any new brackets.
ZHLS–VAL–FSM–SBI–NULL
indicates that this FSM is not yet initialized or is not used in the current
session.
ZHLS–VAL–FSM–SBI–P–NOBB
indicates that a positive response to an SBI request has been processed. The
implied half session might continue to begin brackets, although it has been
asked to stop doing so.
ZHLS–VAL–FSM–SBI–RESET
indicates that no SBI–initiated quiesce operation is in progress; the implied
half session can continue to begin brackets.
Predefined Token and Field
Values
The SNAX/HLS subsystem defines the following token and field values:
ZHLS–VAL–BUFLEN
is the minimum buffer size, in bytes, for response messages from the SNAX/HLS
subsystem.
ZHLS–VAL–FILE–ROLE–RDT
occurs in the ZCMK–TKN–FILE–ROLE token. It specifies that the file described in
an event or response was used as the resource definition table (RDT) file.
ZHLS–VAL–HS–PLRTY–PRIM
represents the primary half session.
ZHLS–VAL–HS–PLRTY–SEC
represents the secondary half session.
ZHLS–VAL–MAXBUFLEN
is the maximum buffer size, in bytes, for command messages sent to the
SNAX/HLS subsystem.