SNAX/XF LU Network Services Manual

Creating the Basic Configuration
Application Example
097841 Tandem Computers Incorporated 3–5
The HELP menu includes “new line” control characters so that the display will be
properly formatted. (For a discussion of New Line control characters, see the IBM 3270
Information Display System 3274 Control Unit Description and Programmer’s Guide.) Note
that New Line is the only control character accepted on the SSCP-LU session. Note
also that the New Line control characters are coded in ASCII-hexadecimal format
(%H85), rather than in EBCDIC-hexadecimal format (%H15). The characters must be
ASCII-hexadecimal because the Tandem service manager translates the entire message
from ASCII to EBCDIC automatically.
The HELP message also includes the keywords @@NDNAME, @@LNNAME,
@@PUNAME, and@@LUNAME. Inclusion of these keywords in any part of an ESS
message results in the display of the Tandem node name, the line name, the PU name,
and the terminal LU name respectively. Thus, for LU3, the top portion of the HELP
message would display the following:
PU: \SYS1.$P2.#PU2
LU: \SYS1.$P2.#LU3
Now that the commands that build the ESS table have been coded, a record for that
ESS table must be added to the SET table. This record assigns a name to the ESS table
and thereby identifies it to LUNS. It also specifies the name of the file where LUNS
can access the table information.
BEGIN
SELECTFILE $SYSTEM.SYS01.SNXSET, TYPE SET
ADD SETESS ESS1, &
FILENAME $SYSTEM.SNAX.ESSTAB1
END
It is assumed that the SET table referenced through the SELECTFILE command is the
starter SET table source file; hence an ALLOCATE command is not included. It is also
assumed that the SET table name was specified during stem generation. Thus, the
referenced SET table source file resides on the volume and subvolume from which
SNAX/XF was cold-loaded.
The second part of this application example shows you how to build your own SET
table and specify its name through the SETTAB parameter of the ADD/ALTER
SUBSYS $SSCP command.