Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Defining messages for internal translation z/OS Communications Server: SNA Network Implementation Guide SC27-3672-01 |
|
The IBM-supplied file, ISTVTMEU, contains messages for internal and external translation.
The user messages defined in ISTVTMEU for internal translation are
USSMSG01 through USSMSG13 for USS and IKT00201I through IKT00405I
for TSO/VTAM. For example, USS message 1 is defined as follows:
You can change the wording of this message to different wording
if required. The &1. is an example of a substitution token and
is used here to identify where the incorrect command name is to be
placed in the message. Additional substitution tokens are &2.,
&3. and so on. Also, the &TIME., &DATE., &LUNAME.,
and &NETID. substitution tokens are used for the time, date, LU
name, and network ID. If you want to provide USS messages in other
languages using MMS, another skeleton file can be created for the
required language with the required message text. For example, you
could code the following in a new file named ISTVTFRA with the text
in French:
Then, if the user specified LANG(FRA) on a USS command, the above
message text would be provided in the case of a USS command syntax
error. The above message could also be defined as a multiline message,
and, when translation occurs, all of the lines in the translated message
are written to the LU. There is a 23-line limit on the number of lines
in a translated message for USS and an 8-line limit for TSO/VTAM.USS messages defined with MMS skeleton files must follow the same restrictions as USS messages defined with USS tables. Only a limited character set is available to SNA logical units on the SSCP-LU session. For TSO/VTAM messages, any character set supported by the user terminal can be used, including double byte-character sets. Using incompatible character sets and code pages can result in erroneous output or I/O errors. |
Copyright IBM Corporation 1990, 2014
|