SNAX Connection Manager (SNAX/CM) Manual

Running a Server Process
SNAX/CM Server
097842 Tandem Computers Incorporated 4–11
Running a Server
Process
This subsection describes how to run the sample SXCMSV server as a named process.
User commands are issued to SXCMSV by way of an IN file, or by opening the process
by name and issuing messages using file-system procedures. SNAX/CM also issues
server interface messages to SXCMSV using the file system.
Two kinds of messages are accepted by the sample server process:
SXCMSV text commands, which can be SXCMGR commands for forwarding to a
selected connection manager process, or SXCMSV server commands (created
specifically for this example and described later in this section)
SNAX/CM server interface messages issued by the SXCMGR process (described
earlier in this section)
Users run SXCMSV either using a TACL RUN command or by calling the Guardian
NEWPROCESS procedure. The syntax for the RUN command is as follows; from this
description, the format of the STARTUP message needed with NEWPROCESS can be
deduced.
RUN SXCMSV / NAME sxcmsv name
[,IN infile ]
[,OUT outfile ]
[, other run-options ]/
[ backup CPU # ]
[; command list ]
sxcmsv name
is the name of the SXCMSV process. SXCMSV must be named when it is to be a
server. If SXCMSV is to act as a customer interface, then it does not need to be
named.
IN infile
is the name of an input file from which SXCMSV will read commands. infile
can be a device, an entry sequenced disk file, or an edit file. If EOF is encountered
on infile without an EXIT command specified, SXCMSV continues to read
commands from $RECEIVE. The default for infile is hometerm .
OUT outfile
is the name of an output file to which responses are sent to commands read from
infile , and messages resulting from the commands. Commands from
$RECEIVE are not echoed, nor are resulting messages sent to outfile . The
default for outfile is hometerm .
run-options
are any of the Guardian RUN options, separated by commas, described in the
TACL Reference Manual.