SNAX/XF and SNAX/APN Configuration and Management Manual

Introduction to SCF for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
11-3
SCF and the SNAX/XF and SNAX/APN Subsystems
SCF and the SNAX/XF and SNAX/APN
Subsystems
A SNAX subsystem consists of a service-manager process and one or more line-
handler processes, all residing on a single NonStop system (node).
The service manager performs a subset of the functions of the SNA system services
control point (SSCP). The line-handler processes implement line-specific protocols.
A single service manager can manage SNAX/XF and SNAX/APN. The service
manager handles some requests itself and sends others to one of the line handlers.
Display information and error messages from the service manager and line handlers
are returned through SCP and SCF, to the terminal or to a log file.
You can also configure multiple service managers to exist concurrently in a single
NonStop node; each service manager process controls its own network configuration
(that is, the lines, PUs, and LUs).
SCP and SCF can reside on separate NonStop nodes. An SCP must reside on the
same NonStop node as the SNAX service managers and line handlers it serves.
You can automate a sequence of SCF commands in a command (OBEY) file that can
be run when needed.
SCF Interface to SNAX/XF and SNAX/APN
The SCF product module for SNAX/XF and SNAX/APN runs as a separate process
started by SCF. The object-code file for this product module, shown in the SCF
LISTPM command, is named ZSX1SCF and has a file code of 100; this file normally
resides in $SYSTEM.SYSTEM.
Because this product module is a separate process, the “execute” attribute for its
object file should be secured for network access. However, the “read,” “write,” and
“purge” security attributes are not significant. Therefore, the ZSX1SCF file should be
secured “xxNx” where “x” can be any security level.