SNAX/HLS Configuration and Control Manual

Introduction
Product Overview
1–4 104705 Tandem Computers Incorporated
SNA Features Supported
by SNAX/HLS
SNAX/HLS follows the SNA architectural specifications given in the IBM SNA Format
and Protocol Reference Manual. This implementation supports the following features:
TS profiles 2, 3, 4, and 7
FM profiles 2, 3, 4, 7, and 18
Multiple RU chains managed by SNAX/HLS or a user application
Half-duplex flip-flop and contention send/receive mode
Full-duplex send/receive mode
Immediate and delayed request mode
Bracket support under both termination rules
Primary-to-secondary and secondary-to-primary pacing
MAXRU sizes up to 4,096 bytes
Pipeline LU support
Responses managed by SNAX/HLS or user application
Characterset translation
Support for multiple domains by using SNAX/CDF as the Tandem SNA access
method
Data Presentation and
Formatting Requirements
SNAX/HLS optionally handles (for the application program) most aspects of SNA
communications protocol except data presentation and formatting services; message
formats are the responsibility of the application. For example:
In applications involving SNA/RJE, the user must format the data buffer with
appropriate SNA Character Stream (SCS) characters prior to transmission.
In applications involving word processing, the user must format the data buffer to
meet device format requirements.
In applications involving database synchronization, the application might assume
control of issuing responses.
Personnel Required for
SNAX/HLS Development
To develop an application using SNAX/HLS, two levels of skill are required: the skill
of the system designer and of the developer.
The designer should have a fairly broad knowledge of SNA, the application, and
Tandem operations. The designer is called upon to establish such things as the BIND
and INIT-SELF databases and to specify the protocol used between SNAX/HLS and
the application program. Thus, the designer must understand basic SNA concepts
(such as BIND image, first speaker, and LU types).
The developer should have a thorough knowledge of the application. The developer is
mainly concerned with solving the application problem (and not the communications
problem). The SNAX/HLS programmatic interface is easy to comprehend and use,
and it requires little or no knowledge of SNA.