SNAX Connection Manager (SNAX/CM) Manual

ENABLE Command
SNAX/CM Commands
097842 Tandem Computers Incorporated 3–17
This fifth example shows how to use the ENABLE command to enable a line and
identify the same server process to receive CONNECTED, DISCONNECTED, and
ENABLE REJECTED messages, as well as CALL VALIDATION and XID
VALIDATION messages:
-> ENABLE LINE $SNAP1, PORT $X25AM1.#SU1, PROCESS $A,
VALXID $A,VALCALL $A
Users can write one server process, $A, to handle all of the functions shown in
this example.
The following example shows how to use the ENABLE command to enable a line,
identify two different server processes to validate XID and callstring values, and
provide a timeout for processing validation messages sent to the server:
-> ENABLE LINE $SNAP1, PORT $X25AM1.#SU1, VALXID $BBB,
VALCALL $AAA, TIMEOUT 500
SNAX/CM first allows $AAA to validate the callstring when the incoming call is
processed. If the callstring is accepted and the call-in operation continues,
SNAX/CM then allows $BBB to validate the XIDSTRING when the XID is
processed. If either $AAA or $BBB fails to complete the validation within the five
seconds specified, the call-in operation fails.
Call-In Operations for Secondary PUs
For call-in operations on secondary lines using multiple ports, a PU can be:
Preselected before call-in, using an SCF ADD PU command, or
Before an X.25 call-in operation, ASSOCIATESUBDEV must be specified using an
SCF ADD or ALTER PU command for PUs permanently subordinated to a line.
The PU is then assigned to the PORT specified by ASSOCIATESUBDEV when the
first SNAX/CM command is issued to the PU or PORT.
Selected dynamically during call in, either using CALLADDR validation or
selected from a pool of PUs that do not require validation.
Note XID validation is not used for selection because the PUID is not sent from the primary PU to the
secondary PU, but rather from the secondary PU to the primary PU.