SNAX Connection Manager (SNAX/CM) Manual
Running SNAX/CM
Introduction to SNAX Connection Manager (SNAX/CM)
1–6 097842 Tandem Computers Incorporated
If the last command is not EXIT, SNAX/CM searches its IN file, if any, for the next
command:
If the IN file returns an EOF indicator without encountering an EXIT
command (whether or not there is a command list) and the process is named,
SNAX/CM continues to exist and can be accessed by using a WRITEREAD
request (read from its $RECEIVE file). This allows users to start up a
SNAX/CM process, making it available for processes to access it
programmatically.
If the IN file encounters an EXIT command and the process is not named, the
IN file acts on the EXIT command and stops SNAX/CM.
Note If users stop SNAX/CM using the EXIT command, lines that were enabled accept one more call-in
request, then accept no more.
SNAX/CM RUN Examples In this first example, the SNAX/CM process is $SX1, the primary CPU is 1 and the
backup CPU is 2:
RUN SXCMGR /NAME $SX1, CPU 1/2
SNAX/CM returns a two-character prompt displayed as >). If you enter an end-of-file
(EOF) indicator by pressing the CONTROL and Y keys simultaneously, the prompt
goes away. However, SNAX/CM ($SX1) is still active and can take commands from
its $RECEIVE file (via WRITEREAD). In this case, the user must explicitly stop the
process $SX1 using the TACL command STOP SX1.
X.25 lines can handle multiple SNAX/XF lines and vice versa. In situations with a
large number of lines to be managed, you might designate one SNAX/CM process to
control a specific set of SNAX/XF lines and designate a second SNAX/CM process to
control a different set of SNAX/XF lines. Each SNAX/CM process can control up to
254 active connections.
To run more than one connection manager process, use the RUN command, as
follows:
RUN SXCMGR /NAME $SX1, CPU 1/2
RUN SXCMGR /NAME $SX2, CPU 2/1
In this second example, the first SNAX/CM process is $SX1, the primary CPU is 1 and
the backup CPU is 2; the second SNAX/CM process is $SX2. The underlying
configuration determines which lines are managed by the process specified.
Figure 1-2 shows how SNAX /CM can be run either interactively or programmatically
in an X.25 environment or a Token-Ring network. Refer to Section 2 for configuration
examples.