SNAX/HLS Configuration and Control Manual

2 Planning the SNAX/HLS
Environment
0104705 Tandem Computers Incorporated 2–1
SNAX/HLS requires you to know little about SNA protocol requirements of the
session partner so you can concentrate on the business application. This characteristic
of SNAX/HLS requires careful planning of both the Tandem and partner SNA
environments by people knowledgeable in these areas. This section presents an
overview of the steps in planning the environment. Following the overview are
suggestions for planning each step.
Five Major Planning
Steps
The following paragraphs summarize the steps in planning a SNAX/HLS
environment and suggest who should do the planning.
1. Planning for session partner requirements.
Each session partner in a proposed application must be described in terms of
device requirements such as special data streams, FMH requirements, special SNA
request characteristics and any custom features, send/receive protocols, use of
SNA brackets, and SNA response requirements.
Tandem system analysts and analysts familiar with the environment in which the
session partner resides should plan session-partner requirements. If the session
partner resides on an IBM system, the VTAM/NCP system analysts and IBM
subsystem (for example, CICS, or IMS) analysts should plan session-partner
requirements. At least one of these people should be familiar with SNA.
2. Planning for SNAX/XF or SNAX/CDF requirements.
A SNAX/HLS application depends on reliable, efficient, SDLC communications.
The physical characteristics of the SDLC links must be described at this step in
preparation for system generation.
It helps to develop a good scheme for naming SNAX/HLS LUs, keeping in mind
that the format of a SNAX/HLS LU name differs from that of a VTAM node name.
Creating standards for relating the two names can simplify operational control
and coordination of the IBM/Tandem environment.
Tandem system analysts, VTAM/NCP system analysts, and operations
management should be responsible for this step.
For information on configuring links for SNAX/CDF in Envoy ACP/XF, refer to
the SNAX/CDF Configuration and Control Manual.
3. Planning for session BINDS.
SNAX/HLS always inspects the session-establishing SNA BIND message to
configure control blocks for the session, adhering rigorously to SNA architecture.
Some SNA products (including IBM devices), however, appear to be less rigorous
in following strict protocol. Because protocol violations can be fatal to an active
session, it is necessary to use a BIND that is both supported by a session partner
and consistent with the partner’s behavior.