SNAX/HLS Configuration and Control Manual

Step 4. Planning the Application Environment
Planning the SNAX/HLS Environment
2–16 104705 Tandem Computers Incorporated
Because the LU name is communicated as a standard Tandem file name that encodes
the identity of both the SNAX/HLS server and the LU name, it can be used in the
OPEN (to establish communication with the SNAX/HLS server), allowing the
program to omit the LU name from the HLS-ALLOCATE or OPEN-SESSION verb.
This feature is not available in a Screen COBOL (SCOBOLX) environment that uses the
server interface.
To implement this convention, use the following capabilities of Tandem languages:
BASIC Use FILENAME$(0) to retrieve the IN file-name , and then parse the
returned name to a PROFILE name. Use FILENAME$(-1) to retrieve
the OUT file-name . This name is suitable as a server and LU name.
COBOL Use the utility routine GETSTARTUPTEXT for IN and OUT file
retrieval. File names are in external form and must be converted to
internal form before parsing.
FORTRAN Use the utility routine GETSTARTUPTEXT for IN and OUT file
retrieval. The file names are in external form and must be converted to
internal form before parsing.
MUMPS Consult the MUMPS Reference Manual for details.
SCOBOLX Use special registers as discussed below along with other Pathway
configuration issues.
TAL Use the startup message to extract the PROFILE and LU name.
Other values for session establishment can be passed as PARAMs (as described in the
reference guides for individual languages). For example, the program invocation
might be used by a TAL program where the IN-file identifies the PROFILE name and
the OUT file identifies both the SNAX/HLS name and the LU name. Below is an
example of how the text of a USERDATA parameter might provide attribute text to be
appended to the BIND image.
Example
PARAM USERDATA "Hello from us"
RUN prog/IN pcics, OUT $hls.#sna1.lu1/
Using SNAX/HLS as a
Pathway Server
This subsection explains how to configure a Pathway environment for SCOBOLX
requesters that employ SNAX/HLS as a Pathway server. The information applies to
situations where a SCOBOLX requester enters into a session with an SLU session
partner or where the SCOBOLX requester enters into a session with a PLU session
partner (for example, CICS).
SCOBOLX requesters communicate verbs and retrieve session partner messages using
a SCOBOLX SEND request to a server class in which one copy of the SNAX/HLS
program is the only server entity. (SCOBOLX statements DISPLAY and ACCEPT are
not used for this purpose because the TCP alters both inbound and outbound
messages.)