SNAX/HLS Configuration and Control Manual

Objects and Attributes
Using the HLSRDT Utility
104705 Tandem Computers Incorporated 4-35
TRANSLATE
This PROFILE attribute has the value type yesno . The default value is NO.
TRANSLATE specifies whether data is to be converted between an outbound/external
format and an inbound/internal format. If selected, the interchange code set (the data
sent to and received from SNAX) is in the outbound format, and the presentation code
set (the data sent to and received from the application in HLS verbs) is in the inbound
format.
The mapping table to be used is either the default, as specified by the startup
parameter CHARMAPNAME (which itself defaults to table “1”—the standard ASCII-
EBCDIC translation), or that specified with the CHARMAP PROFILE attribute. FM-
header data and all formatted data (such as sense codes) is not translated.
When the interchange code set is EBCDIC, the most efficient way to design the
application is to treat all data without translation. However, EBCDIC is foreign to
Tandem applications, and translation to ASCII is almost always desirable. The
application designer can have the translation performed by the Tandem SNA access
method (SNAX/XF or SNAX/CDF). The cost is about the same, but only SNAX/HLS
translation provides the advantages of automatic code-set display when tracing in
SNAX/HLS and correct treatment of FMHs.
If the interchange code set is neither ASCII nor EBCDIC, then the code-set display
during tracing will not be reliable.
USER-RESPONSES
This PROFILE attribute has the value type yesno . The default value is NO.
USER-RESPONSES specifies whether SNAX/HLS (USER-RESPONSES NO) or the
application (USER-RESPONSES YES) generates responses to FMD data messages
from the partner LU. This feature, if enabled, inhibits the automatic generation of
responses by SNAX/HLS, and requires that the application program issue
HLS-RESPOND verbs to respond to all messages it receives.
This feature is used typically for those applications in which the SNA response implies
the commitment of a transaction; that is, the safe storage of some data.