SNAX Connection Manager (SNAX/CM) Manual

ENABLE Command
SNAX/CM Commands
097842 Tandem Computers Incorporated 3–15
TIMEOUT time-out
specifies the period of time (in 0.01-second units) during which validation is to be
completed. The default is 60 seconds.
Note This parameter is valid only when using the VALXID and/or VALCALL parameters in the ENABLE
command.
If the validation process fails to complete in the time allowed, an error message is
sent to the log file specified by the user, and the connection is broken.
return : (OUTFILE)
if received from the IN file, specifies the text message to be returned to the OUT
file. If received from the $RECEIVE file, returns a structured buffer that includes
any return codes and file-system error messages. See Appendix B for detailed
descriptions of return codes and error messages.
return : ($RECEIVE)
if received from the $RECEIVE file, returns a structured buffer that includes any
return codes (described in Appendix B) and file-system error messages.
Using the ENABLE Command
When a call-in operation occurs, SNAX/CM searches the PUs assigned to the
SNAX/XF service manager process (for switched floating lines) or the PUs assigned to
the LINE (for permanently subordinated lines) for the identified PU. The PU can be
either the PU name or a matching CALLADDR and PUID specification.
The ENABLE command can be used to accept any call-in request by allowing the
specification of a “generic PU”. This is a PU defined with no CALLADDR and a
default PUID. You can add one (or more) generic PU to the SNAX/XF service
manager process or to lines.
When generic PUs are used for call-in operations, SNAX/XF does not verify the
CALLADR or PUID. Instead, any PU calling in that does not match a PU configured
with explicit CALLADDR and/or PUID values are assigned to an available generic
PU. Call-in operations are accepted from as many unidentified PUs as there are
configured generic PUs.
If the ENABLE command specifies the use of a connection-manager server for call
validation (VALCALL) or XID validation (VALXID), the user can code validation of
the incoming caller. Because it cannot be predicted which generic PU will be selected
during call-in, the user should consider an identical LU configuration for generic PUs.
One SNAX/CM process can handle a maximum of 254 active connections. The total
connections include successful responses to SNAX/CM ENABLE commands, as well
as successful and in-process CONNECT commands.
SNAX/CM returns an ENABLE COMMAND ACCEPTED message to the user when
the command is forwarded to the service manager.