Control statements for KDCMTXT

KDCMTXT recognizes the following control statements:

OPTION	Specify name of message definition file
FU	Define function unit and national language
MSGBASE	Select message group for FU SYS: UTM (K messages) or XAPTP (P messages)
STDTXT	Define start of standard message text
ENDTXT	Define end of standard message text
END	Define end of input of control statements

The following rules apply to the input of statements:

• Comment lines are marked by means of an asterisk (*) in column 1.

• If a line ends with a comma, KDCMTXT then interprets the following line as a continuation line of the statement.

It is expedient to write the control statements for KDCMTXT to a file. When the control statement file KDCMTXT is created, the file SYSDAT.UTM.070.MTXTIN which is supplied with openUTM may be of assistance. This file contains the German and English standard message texts in the syntax of the KDCMTXT control statements. This file may be used as a template for the user’s own input file.

OPTION statement

OPTION can be used to specify the name of the message definition file which is to be modified by KDCMTXT.

The OPTION statement must, if specified, be the first control statement; otherwise a syntax error will be reported. If no OPTION statement is specified, KDCMTXT uses the message definition file SYSMSH.UTM.070.MSGFILE supplied as standard with openUTM.

For safety reasons it is advisable to copy the message definition file and work on the copy with KDCMTXT.

Operation	Operands
OPTION	MSGFILE=filename

filename

Name of the message definition file which is to be extended. Default: SYSMSH.UTM.070.MSGFILE

FU statement

This statement can be used to define the function unit and the natural language.

Operation	Operands
FU	[function-unit][,][LANG=language-id]

function-unit

Function unit for which the new natural language is to be entered. At present, the only value permitted is SYS. SYS represents the transaction monitor.

      SYS

K messages (K001-K399) or P messages (P001 - P049)

Default: SYS

LANG=language-id

The language ID can consist of a maximum of 3 characters. It can be freely assigned, but it must be unique within a message definition file.
You can use the language IDs found on cars or the language IDs defined in ISO IS/R639, for example.

Country IDs on cars	ISO IS/R639	Language
DK	Da	Danish
D	De	German
GB	En	English
E	Es	Spanish
FI	Fi	Finnish
F	Fr	French
GR	Gr	Greek
I	It	Italian
NL	Nl	Dutch
N	No	Norwegian
P	Pt	Portuguese
S	Sv	Sweden

Default: GB

It is only necessary to specify the comma if both function-unit and LANG=language-id are specified., e.g. FU SYS, LANG=DK.
The LANG= option is only used to identify the texts in the message definition file and bears no relation to the language identifier for a user generated with the KDCDEF parameter LOCALE.
For any given functional unit, all the message texts for one language must be specified so that the message texts for this language and functional unit are transferred in the message definition file.

After the FU statement has been processed, the MSGBASE UTM statement is executed implicitly.

CAUTION!

The message definition file supplied already contains the German and English message texts with language identifiers D and GB. If one of these identifiers is specified, KDCMTXT overwrites the corresponding standard message texts in the message definition file with the new message texts.

MSGBASE statement (only for FU SYS)

openUTM makes a distinction between two message groups within FU SYS: Messages of the UTM group, which start with the letter K, and messages of the XAPTP group, which start with the letter P.

The MSGBASE statement allows you to select the message group to which subsequent STDTXT statements are to apply until the next MSGBASE or FU statement is issued.

Operation	Operands
MSGBASE	{ UTM | XAPTP }

UTM	Select the UTM message group (K messages).
XAPTP	Select the XAPTP message group (P messages).

STDTXT and ENDTXT statements

The control statement STDTXT introduces the definition of the standard text of a message. The subsequent input lines describe the standard text.

ENDTXT terminates the definition of the message text. The translated message text is passed to KDCMTXT as follows:

Operation	Operands
STDTXT	msg-no text
ENDTXT

msg-no	Message number for which the standard text is intended. msg-no specifies the K or P message that is to be modified. The message number must lie within the message number range of the specified functional unit. The message number must be specified as three digits without the prefixed K or P. Mandatory operand.
text	The message text must be specified here; the syntax is the same as with the KDCMMOD utility (see "Control statements for KDCMMOD"). The same length restrictions similarly apply.

The control statements STDTXT and ENDTXT and also the message text must each begin in a new line.
The STDTXT / ENDTXT statements for a single functional unit and a single language must all be located after the FU statement for this functional unit and must precede the next FU statement.

KDCMTXT will only transfer the message texts for an additional language in the message definition file if the input data contain all the message texts for this language and if all message texts are error-free.

If the message texts for a language are already present in the message definition file, KDCMTXT will then also accept individual messages. Existing message texts with the same message number and the same language identifier are then overwritten.

END statement

This statement terminates the input of control statements to KDCMTXT. END has no operands.