SNAX/XF LU Network Services Manual
Building the ESS Tables
Using LUNS
2–6 097841 Tandem Computers Incorporated
For a TACL, specify ITI as the protocol. Note that any protocol you specify in the ESS
table record will remain in effect only for that LU-LU session.
Other optional operands that override SCF LU attributes include:
RECSIZE
recsize
specifies the length, in bytes, of a line, screen, or RU, depending on the
terminal protocol chosen.
CHARACTERSET { EBCDIC | ASCII | KATAKANA }
specifies whether or not character translation should occur. If ASCII is
specified, no translation will occur. If EBCDIC is specified, ASCII/EBCDIC
translation will take place. If KATAKANA is specified for Japanese-language
SNA terminals, JIS 6220 Katakana/EBCDIC Katakana translation will take
place. (For EBCDIC terminals that establish sessions with Tandem
applications coded in ASCII and do not use the Katakana character set,
CHARACTERSET should be specified as EBCDIC.)
SNATYPE
sna-type
specifies the type of SLU support that the terminal will use. Valid values for
sna-type
are: 0, 1, 2, 3, 4, and 6.
The CONCDATA Operand
(APPLFILE | TACL)
For records pointing to applications on a Tandem system, SNAXUTL also provides the
CONCDATA operand:
CONCDATA
concatenated-data
The CONCDATA operand is used to specify data that LUNS will concatenate
with the CINIT command that is sent to the Creator process. The data can be
any string ranging from 1 to 1880 bytes in length.
Within the CONCDATA operand, bytes can be specified either as characters
or as hexadecimal or octal byte values. When data strings exceed one line, you
can use a line continuation sequence (a comma, followed by an ampersand
character: &). Note that if you specify CONCDATA in a record pointing to a
host process, SNAXUTL will reject it.
It is the CONCDATA operand that allows you to specify the necessary
NEWPROCESS procedure call parameters the Creator process uses to create
an APPLFILE (CRT or ITI process, including TACL) or TACL process and
establish the LU-LU session. If either APPLFILE or TACL is specified, the
Creator process issues a NEWPROCESS call to the APPLFILE process
configured with SCF.
It is recommended that the APPLFILE parameter be used for all subsequent
non-Pathway logon procedures, including TACL logons. However, note that
the APPLFILE and TACL parameters are synonymous and if the TACL
parameter was used previously, it does not need to be changed.
The following shows what can be specified as values for the CONCDATA operand
passed to the Creator process.