Introduction to SNA Capabilities of Tandem NonStop Systems

Introduction to SNA Capabilities of Tandem NonStop Systems–134597
6-1
6
Configuration and Management
Getting Started
Enabling a system to function with Tandem SNA products requires several initial steps,
detailed below.
Controller and Process Definition
SNAX/XF, SNAX/APN, EnvoyACP/XF, X25AM, and TLAM all have I/O processes
that control physical lines. Some have separate management processes.
For Himalaya K-series servers, communications controllers, management processes, and
I/O processes are defined in the system generation input or added later—a process called
Dynamic System Configuration (DSC)—using the Configuration Utility Program
(COUP) utility.
For Himalaya S-series servers, the ServerNet wide area network concentrator,
management processes, and I/O processes are defined to the WAN subsystem through
profiles and Subsystem Control Facility (SCF) commands.
Startup
Some SNAX products, such as SNAX/XF and SNAX/APN, are started through an SCF
START command. Other products, such as SNAX/CDF and SNAX Creator-2, are
started by issuing a TACL RUN command or NEWPROCESS system procedure call.
Further Configuration
After system loading and startup, Tandem SNA products require further configuration to
extend the line definitions and to define other resources such as logical units and
applications. This is performed interactively (usually from an OBEY file) or
programmatically; see “Tools for Configuration and Management” later in this section.
The additional resources defined may also require startup.
The SNAX/XF LU network services (LUNS) interface is configured by building various
tables using the SNAX Utility Program (SNAXUTL).
Notes.
1. SNAX/XF and SNAX/APN Token-Ring and X.25 lines must also be defined as TLAM and
X25AM lines respectively.
2. SNAX/CDF uses EnvoyACP/XF lines.