SNAX/HLS Configuration and Control Manual

Step 1. Partner Requirements Planning
Planning the SNAX/HLS Environment
2–2 104705 Tandem Computers Incorporated
The SNAX/HLS product always adheres to the formal protocol but allows some
departures from protocol on the receiving side of a transmission. This permits the
use of certain SNA devices that do not adhere strictly to SNA protocol. See Section
7, “Interpreting SNA Protocol” for more information on the use of SNA protocols.
Tandem system analysts, VTAM/NCP system analysts, and IBM subsystem
programmers should be responsible for this step.
4. Planning the application environment.
The overall design of the application environment is critical to the timely
construction and efficient operation of SNAX/HLS applications. Special care
should be given to Pathway configuration files that maximize the flexibility of the
SNAX/HLS application. The management of PROFILE names, SNAX/HLS LU
names, the use of standard copybooks, and other configuration parameters are
critical here. Environments that do not use Pathway should be configured with
the same goal of flexibility.
Tandem system analysts, VTAM/NCP system analysts, and IBM subsystem
programmers should plan the application environment.
5. Planning for programming standards.
The SNAX/HLS environment is rich in features that promote the use of standard
programming guidelines and at the same time allow flexible, efficient, transaction
processing. Issues to be considered here include use of operator messages, correct
use of the CONVERT-ERROR-CODE verb, standard handling of messages, and
awareness of send/receive modes in SNAX/HLS applications.
Tandem system analysts, application development management, and application
programmers should plan for programming standards.
Step 1. Partner
Requirements
Planning
A session partner can be a device (for example, 3624 ATM, 4704 terminal) or an IBM
gateway application (for example, IMS or CICS). Each type of session partner is
discussed separately.
Device-Support Planning To support an SNA device, you should consider the points in the following
paragraphs.
Special Device Data Streams
Most programmable controllers have field-formatted data streams that are understood
only by the application program within the controller (the application program session
partner) and the SNAX/HLS application. Be sure that the data stream is understood
by the application staff before programming begins.
If the device is a 327x-type display/printer, consider using the SNA3270 interface of
SNAX/XF or SNAX/CDF. If this interface is inapplicable and you use a SNAX/HLS
application instead, device formatting becomes the responsibility of the SNAX/HLS
application. In this case, all 327x screen/print control characters must be passed in the
user buffer when a SEND-DATA verb is delivered to SNAX/HLS; RECEIVE-DATA
verbs complete with 327x formatted data.