SNAX Connection Manager (SNAX/CM) Manual

4 SNAX/CM Server
097842 Tandem Computers Incorporated 4–1
This section describes a user-written server process that works with SNAX Connection
Manager, as well as message structures used by SNAX/CM and how to run the server
process.
A programming sample of a server process is provided in Appendix C and also on the
Site Update Tape (SUT). The example, named SNAX/CM Server (SXCMSV), includes
commands created specifically for the sample server process. This example is not a
prerequisite to using SNAX/CM. Users can use this example and these commands, or
create their own.
Note The sample server provided is not a supported file, but is included for purposes of illustration only.
Server for SNAX
Connection Manager
A server is a process that you write and customize according to what you want it to do
on behalf of a connection. A server accepts text commands that are used to build a
configuration; the configuration is then used to process messages received from the
SNAX Connection Manager process (SXCMGR).
For example, when a connection occurs, SNAX/CM sends a message to inform a
server, as well as provides the identity of the LUs (the alias LU names) and the alias
LU count. The server can then perform the functions you want on the basis of that
information, such as starting TACL to use that connection.
There can be a variety of interfaces to the server process, including XID validation and
call validation. A server may provide a facility to configure lists of XID values or call
address values, and options to tell the server what to do on behalf of a connection.
Refer to the server program in Appendix C for a sample of how to build LU lists and
validate calls.
SNAX/CM monitors connections and disconnections for all the lines it is controlling.
If a line has been enabled or connected by SNAX/CM and the connection is active,
SNAX/CM notifies the server process when that line is disconnected, regardless of
how the connection was terminated.
Figure 4-1 illustrates how SNAX/CM and the server process work together.
In this figure, the server (SXCMSV) is configured to send a NEWPROCESS request to
user-defined programs or to start an Exchange/SNA application. The user application
(APPL) configures the server using text commands. (The server process should be
started before you use SNAX /CM to make a connection.)
The user application then issues commands to the SNAX Connection Manager process
(SXCMGR) using WRITEREAD requests.