SNAX/HLS Application Programming Manual

HLS-OPEN Verb
SNAX/HLS Verbs
5–34 104707 Tandem Computers Incorporated
1. Your application program resides on node \PARIS and issues an HLS–OPEN
specifying an APPLICATION–NAME of \TEXAS.$SNA1.TSO. However, the SNA
line on which your application resides is a secondary line, with the primary driven
from another Tandem node, \NEWYORK.$SNA8.
2. An INIT–SELF, bearing the application name of \TEXAS.$SNA1.TSO, flows out of
your node (\PARIS) and is received by the primary on \NEWYORK.$SNA8.
3. The Tandem Service Manager ($SSCP) on \NEWYORK, receiving this INIT–SELF
message, notes that the LU on which the INIT–SELF arrived is currently
uncommitted. It therefore examines the APPLICATION–NAME for a valid
network address, and, finding one, sends the message to \TEXAS.$SNA1. Note
that this can involve sending the message to a remote Tandem node, as illustrated
in this example.
4. The INIT–SELF message itself is modified to remove the Tandem portions,
reducing the APPLICATION–NAME down to TSO.
5. On node \TEXAS, an available LU is found on line $SNA1, which has been
configured to support the TSO application. A passthrough connection is made
back to \NEWYORK.$SNA8, and the INIT–SELF is sent toward IBM (bearing the
APPLICATION–NAME of TSO).