SNAX/XF LU Network Services Manual

Building the ESS Tables
Using LUNS
2–10 097841 Tandem Computers Incorporated
Thus, for the GATELINE operand, the format would be:
\ system-name .$ line-name
For the GATEPU operand, the format would be:
\ system-name .$ line-name .# pu-name
For the GATELU operand, the format would be:
\ system-name .$ line-name .# lu-name
In creating records for passthrough sessions, you can specify CMDTYPE as either
LOGON-INIT, LOGON-CHAR, or INITSELF-RECEIVED.
When the CMDTYPE is LOGON-INIT, the PLUNAME operand data is the name of a
PLU on the host. Optional operands include RECSIZE, CHARACTERSET, and
BINDENTRY. If specified, the BINDENTRY operand must name an entry in the host's
LOGMODE table.
SNAXUTL also allows you the option of specifying a USERDATA operand when the
CMDTYPE is LOGON-INIT. With this operand, you can specify user data to be placed
in the INIT-SELF built by LUNS. The value can be any string containing from 1 to 256
bytes; these bytes can be specified either as characters or as hexadecimal byte values.
In instances where a data string requires more than one line, this operand can be
represented using line continuation(s).
When the CMDTYPE is LOGON-CHAR, the PLUNAME operand remains unused,
and unless you specify otherwise, LUNS takes the character-coded command entered
at the terminal (along with any other characters entered on the same line of the screen)
and sends it to the host system for processing.
If you want a different character-coded command to be sent to the host, you can
include it in an operand called REPDATA. (Note that when the command name uses
the single-byte Katakana character set, you must use REPDATA to send the character-
coded command by which the host knows the application.) Figure 2-1 shows how
LUNS uses the logon record's REPDATA field.