SNAX/XF LU Network Services Manual

Creating the Basic Configuration
Application Example
097841 Tandem Computers Incorporated 3–3
Configuration Assumptions The following are configuration assumptions:
The starter SET table provided by Tandem has been made active through
SYSGEN. SNAX/XF has thus already initialized the LUNS component of $SSCP.
(Most users will prefer to build their own SET table and specify the SET table
name through the SETTAB parameter of the SCF ADD/ALTER SUBSYS $SSCP
command. The second part of the application example shows how to do this; see
“Using SCF to ADD the New Application and LU to \SYS2.”)
Only one ESS table will be created. It will have the table name ESS1 and will not
be flagged as the default table. SCF ADD APPL commands will define the TACL
application, the Tandem Creator process, and SNAXUTL to LUNS, giving these
processes subdevice names of #TACL, #CREATE, and #SNAXUTL, respectively.
Note that the inclusion of an ADD APPL command for SNAXUTL allows for the
dynamic modification of the ESS table. (In the second part of this application
example, ESS1 will be modified dynamically; see “Updating the ESS Table on
\SYS1.”)
TSO, and the Pathway application, Order Entry, need not be defined by an ADD
APPL statement.
Because ESS1 is not a default table, it must be associated with each terminal
individually. This is done through the ESSTABLE attribute of the SCF ADD LU
command that defines each terminal LU. (Also see “Performance
Considerations—ESS Table Allocation” in this section.)
Gateway LUs (LU1 and LU2) will have the SCF attribute PASSTHRU ON, but not
STATIC ON or ASSOCIATE.
Creating a Command File
for SNAXUTL
In the following edit command file, SNAXUTL commands add:
Logon and logoff records in the ESS table
A user message record (a HELP menu) in the ESS table
A record in the SET table that identifies the ESS table
Note that the ESS table is created first. Because a new table is being created, the
ALLOCATE command is used.