SNAX/XF and SNAX/APN Configuration and Management Manual

SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
11-1
11
Introduction to SCF for SNAX/XF
and SNAX/APN
This manual describes the subsystem-specific details for using the Subsystem Control
Facility (SCF) interactive interface to configure and control the SNAX/XF (SNAX
Extended Facility) and SNAX/APN (SNAX Advanced Peer Networking) products.
SNAX/XF provides a NonStop system with the capability to do the following:

Interface to Systems Network Architecture (SNA) type 2.0 nodes

Interface to SNA hosts (type 5.0 nodes)

Pass SNA data transparently between type 2.0 and type 5.0 nodes
SNAX/APN gives a NonStop system the ability to act as a Systems Network
Architecture (SNA) type 2.1 node and participate as a Low Entry Networking (LEN)
node within IBM Advanced Peer-to-Peer Networking (APPN) networks.
SNAX/APN shares a common code base with SNAX/XF (SNAX Extended Facility).
This allows you to use SCF to define SNAX/APN objects and SNAX/XF objects on the
same line in multipoint configurations.
This section provides an overview of the SCF interface to SNAX/XF and SNAX/APN,
and is intended to help you get started. For information about using SCF with NonStop
S-series servers, see the SCF Reference Manual for G-series RVUs.
Tasks You Can Perform Using SCF
You can perform the following configuration and management functions:

Define application processes (such as user-written programs, SNAX Creator, or
SNAX Creator-2) that can communicate with the SNAX service manager.

Start operation of the subsystem and its configured lines, PUs, and LUs

Configure lines, physical units (PUs), and logical units (LUs) to each service
manager, changing the characteristics of those objects

Add or delete lines, PUs, and LUs from the configuration

Inquire about the names and characteristics configured for applications, lines, PUs,
LUs, and the subsystem

Request counts of the defined and active lines, PUs, and LUs, and request
statistical information about these objects and the subsystem as a whole

Inquire about the status of applications, lines, PUs, LUs, and the subsystem as a
whole