Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Defining messages for external translation z/OS Communications Server: SNA Network Implementation Guide SC27-3672-01 |
|
Messages for external translation are also defined in ISTVTMEU. All of the messages for external translation are messages that are written to the system console. You should not change the U.S. English form of these messages in ISTVTMEU, because ISTVTMEU must correspond exactly with ISTINCNO for external translation to occur. For operator messages, you should use the IBM-supplied default table, ISTINCNO, rather than using a customized operator USS table. For translation to other languages, provide a language skeleton
file similar to ISTVTMEU with the translated text. For example, VTAM® message IST001I is defined
as follows in ISTVTMEU:
The text of this message could be changed to French in a new skeleton file named ISTVTFRA. It is necessary to have two formats of this message: one for the message without the module name and one for the message with the module name. MMS will select the format that most closely matches the message received and perform the translation by selecting the corresponding message with the corresponding format number from the new French skeleton file. For example, assume ISTVTFRA has the following definition for IST001I:
With the above skeletons coded, a TSO/E 2.2 user using an MCS extended
console with the primary language of FRA will have the following VTAM message translated as shown
below:
The translated messages can be in any language supported by MMS, including double-byte character set languages. The only restriction is that the terminal being used for a given language must support that language with the correct character set and code page, or erroneous output or I/O errors can occur. Translated messages can also be defined as multiline messages if more than one line is needed to express the error in the translation language. |
Copyright IBM Corporation 1990, 2014
|