UNIVERSIDAD NACIONAL DE INGENIERIA Facultad de lngenierfa Civil

Attributes

The following SCF attributes specify certain conditions for an LU that are also specified by entries in an ESS table. If what you specify with SCF for these attributes differs from what is specified in the ESS table, LUNS uses the values specified in the ESS table. That is, LUNS will use the ESS table values to set up the session, and these values remain in effect for the duration of the session.

BINDENTRY Attribute The syntax for the BINDENTRY attribute is as follows:

BINDENTRY "bind-table-entry-name"

"bind-table-entry-name" specifies the record name of a BIND image used by this LU found in either a host LOGMODE table or in a BIND table created using SNAXUTL.

If the BINDENTRY attribute is specified in an ADD or ALTER LINE command (primary line only) or an ADD or ALTER PU command to which this LU is

permanently subordinated, the LU uses the BINDENTRY value of the superior object as a default unless it is overridden by a BINDENTRY value specified in an ADD or ALTER LU command for the LU.

For switched floating LUs, the BINDENTRY value must be specified in an ADD $SSCP or ALTER $SSCP LU command.

The BINDENTRY name can contain from one through eight alphanumeric or special characters ($, #, or @). Note that BINDENTRY names can be specified in uppercase or lowercase letters; SNAX/XF converts all lowercase letters to uppercase.

BINDTABLE Attribute The syntax for the BINDTABLE attribute is as follows:

BINDTABLE "bind-table-name"

"bind-table-name" specifies the name of a BIND table that has been created using SNAXUTL (see “SELECTFILE” in Appendix A). The BIND table contains the BIND image specified with a BINDENTRY attribute for a primary line and its subordinate objects.

ESS LU Attributes That Override SCF LU Attributes

If the BINDTABLE attribute is specified in an ADD or ALTER LINE command (primary line only) or an ADD or ALTER PU command to which this LU is

permanently subordinated, the LU uses the BINDTABLE value of the superior object as a default unless it is overridden by a BINDTABLE value specified in an ADD or ALTER LU command for the LU.

The BINDTABLE name can contain from one through eight alphanumeric or special characters ($, #, or @). Note that BINDTABLE names can be specified in uppercase or lowercase letters; SNAX/XF converts all lowercase letters to uppercase.

CHARACTERSET Attribute The syntax for the CHARACTERSET attribute is as follows:

CHARACTERSET { ASCII | EBCDIC | KATAKANA }

This attribute specifies whether SNAX/XF is to perform character translation for the specified LU. The following are valid values for this attribute when specified on an ADD LU command:

ASCII specifies that no translation is to take place. This implies that characters are in ASCII format.

EBCDIC specifies that translation from ASCII to EBCDIC is to take place. That is, EBCDIC turns translation on so that all data sent from the terminal to a Tandem application will be translated from EBCDIC to ASCII and all data sent from a Tandem application to the terminal is translated from ASCII to EBCDIC.

KATAKANA specifies that translation from EBCDIC Katakana to Tandem Katakana is to take place. Note that the value KATAKANA can be specified for the LU only. It cannot be specified in an ADD or ALTER command issued to the PU or LINE object.

For LUs permanently subordinated to a line, the CHARACTERSET attribute specified for the line (ASCII or EBCDIC) is used as a default value for the LUs if no

CHARACTERSET attribute was specified on an ADD or ALTER LU command. For switched floating LUs, the CHARACTERSET attribute must be specified in an ADD or ALTER LU command for the switched floating LU.

ESS LU Attributes That Override SCF LU Attributes

PROTOCOL Attribute The syntax for the PROTOCOL attribute is as follows:

PROTOCOL { CRT | ITI }

This attribute specifies the application interface protocol that SNAX/XF uses when communicating with the corresponding LU. If the LU is a terminal attached to a 6600 controller, the protocol selected must be either CRT or ITI. This attribute is required for the LU object type.

The different protocols that can be specified are as follows:

CRT specifies that this LU uses the standard 3270 full-screen block protocol. An application that communicates with this LU must define and expect to receive 3270 data streams that contain screen- formatting control characters.

ITI specifies that the device expects to converse with Tandem

applications using the standard 3270 conversational (line-at-a-time) mode.

RECSIZE Attribute The syntax for the RECSIZE attribute is as follows:

RECSIZE integer

This attribute specifies the length, in bytes, of a terminal or printer line, CRT screen, or RU, depending on the PROTOCOL attribute.

The following PROTOCOL dependencies apply:

If the PROTOCOL attribute specifies CRT, the RECSIZE attribute specifies the CRT screen or printer buffer size.

If the PROTOCOL attribute specifies PRT, the RECSIZE attribute specifies the printer line length plus 5 bytes.

If the PROTOCOL attribute specifies ITI, the RECSIZE attribute specifies the terminal line length plus 16 bytes.

If the PROTOCOL attribute specifies SNALU, the definition of RECSIZE is in addition to SNALU according to the following guidelines:

For LUs subordinate to a primary line, RECSIZE specifies the SNA RU length. For LUs subordinate to a secondary line, RECSIZE specifies the SNA RU length if byte 11 of the SNA BIND request is 0. If byte 11 is not 0, the value of RECSIZE is ignored.

The valid range for RECSIZE is from 1 to 4096 bytes. The default value for RECSIZE is 1024 bytes.

SCF Attribute Summary

SCF Attribute