SNAX Connection Manager (SNAX/CM) Manual

Validation Processes for Incoming Calls
SNAX/CM Server
097842 Tandem Computers Incorporated 4–5
Validation Processes
for Incoming Calls
This subsection describes the function of optional user-written server processes to
validate the call string and XID string, and describes the structure for messages sent by
SNAX/CM to the validation processes. The validation processes allow users to
perform functions that:
Supplement, but do not replace, the validation routines performed by the
SNAX/XF service manager process (in this example, using a default name of
$SSCP). When a user specifies PU attributes CALLADDR, PUIDNUM, or
PUIDBLK, the SNAX/XF service manager process performs those validation
routines.
Perform validation routines after the SNAX/XF service manager process performs
its validation.
Screen remote call-in requests in a way that the SNAX/XF service manager
process cannot by imposing additional connection criteria; for example:
A validation process can restrict the access of certain call-in PUs so that they
can connect only to a particular line.
A validation process can restrict the access of certain call-in PUs so that they
can connect only at particular times of day.
SNAX/CM allows a user-written VALIDATION process to check the callstring and/or
the XID string for call-in operations if specified by the ENABLE command that was
issued. The messages sent by SNAX/CM to the VALIDATION process will be in one
of the following structures.
Validating the XID String This message structure is used to validate the XID string:
STRUCT user^interface3 (*);
BEGIN
STRING base[ 0:-1 ]; ! used with VARSTRING
INT message^type; ! 3 = XID string validate
STRUCT xidstring(VARSTRING); ! Pointer to XID string
STRUCT linename(VARSTRING); ! Pointer to line name
STRUCT portname(VARSTRING); ! Pointer to X25AM SU name
STRUCT puname(VARSTRING); ! Pointer to PU name
STRING data[0:-1]; ! XID string, line name,
! X25AM SU name, and PU name
END;