SNAX Connection Manager (SNAX/CM) Manual

ENABLE Command
SNAX/CM Commands
3–14 097842 Tandem Computers Incorporated
PORT $ device .# xxxxxxx
is the name of a TLAM IOP ($ device ), followed by a user-supplied
alphanumeric character string that follows the naming conventions for
subdevices.
Only one ENABLE command on a line using a particular sap value can be
active at any one time. The ENABLE command is rejected with an error if the
sap value specified in the ENABLE command is the same as a sap value of a
previously enabled port for the same line.
PROCESS { process-name | ( TACL , TACL-name ) }
PROCESS process-name
specifies the name of a user-written server process that gains control either
after a call-in operation is completed, when the ENABLE command is rejected,
or when a disconnection occurs. This PROCESS server should be started
before the ENABLE command is issued. Thereafter, messages about
commands rejected and the status of connections are sent to process-name .
PROCESS ( TACL , TACL-name )
specifies the name of a TACL process to be started by SNAX/CM only for
primary lines and PUs after a call-in operation is connected. (Note that
SNAX/CM cannot start a TACL process on a secondary LU.) SNAX/CM
starts a TACL process on the first alias LU only and assumes there is a TACL
on $SYSTEM.SYSTEM. If there is no TACL on $SYSTEM.SYSTEM, SNAX/CM
logs a message and no TACL is started.
If PROCESS is not specified, SNAX/CM does nothing after a call-in operation is
successfully completed. For permanently subordinated PUs, users can post a
CONTROL 11 request in the application programs and wait for the CONTROL 11
operation to be completed. For either switched floating or permanently
subordinated PUs, the LUNS interface can be used to start a session.
VALXID xidproc-name
specifies a user-written validation process that gains control after SNAX/XF
validation. This process can examine the XID and accept or reject the call-in. Note
that XID validation is meaningful only for primary lines.
VALCALL callproc-name
specifies a user-written validation process that gains control after SNAX/XF call
address validation. An incoming call has occurred but it has not yet been accepted.
The application can examine the calling number and accept or reject the call-in
request before it is connected.