SNAX/HLS Configuration and Control Manual

4 Using the HLSRDT Utility
104705 Tandem Computers Incorporated 4–1
Introduction The SNAX/HLS operating environment presumes the existence of a database known
as the resource definition table (RDT). This table contains PROFILE, BIND, and INIT
data. The application program, at execution time, references an entry in this database
through the use of the PROFILE name.
The PROFILE entries define many characteristics of the session about to begin. These
characteristics control the interface between the application program and SNAX/HLS,
and they also provide certain information about the session, such as the name of the
BIND or the INIT entry. The PROFILE entries also define whether this or the other
session partner takes the first step in establishing the session.
The BIND entries specify the text of the BIND messages sent to initiate a session.
These entries are used only by primary session partners. BIND messages are special
SNA messages that define the protocol of the session.
The INIT entries specify the text of the INIT-SELF messages sent to request the
initiation of a session. These entries are used only by secondary session partners that
acquire sessions.
Establishing the values in the RDT suitable for a particular application is a complex
task that requires knowledge of SNA protocol, the device (or application) protocol,
and the particular needs of the application. For this reason, these decisions are made
in a step outside the application program.
The HLSRDT control language allows symbolic reference to every option in the
PROFILE, BIND, and INIT objects. Even BIND images are created symbolically; hence
there is no need to decode hexadecimal strings, except for the SNA PS-USAGE field.
Running HLSRDT Start HLSRDT (from TACL) with the following syntax:
RUN HLSRDT [/ option [, ... ]/] obj-file [; command [; ...] ]
option is one of the following:
IN file-name
specifies the name of the standard input file. If omitted, the issuing terminal
becomes the input file.
OUT file-name
specifies the name of the standard output file on which all listings are produced.
If omitted, the issuing terminal becomes the output file.