Most of the messages in the message files are only issued in situations that make them visible to application developers. However, some of these messages are issued in situations that make them visible to end users of applications created by LANSA.
For example, if an end user displays a process menu and attempts to select an option with an incorrectly positioned screen cursor, message DCM0546 is issued. In English it looks like this:
"Screen cursor not positioned on same line as a valid function"
In non-multilingual partitions, all messages are issued from message file DC@M01 and appear only in English (unless changed to another language by directly changing the DC@M01 message file).
In a multilingual partition, a message file override command is issued from DC@M01 to DC@M01xxxx, where "xxxx" is the 4 character identifier of the language being used.
Thus when message DCM0546 is issued, message file DC@M01xxxx is searched first.
If the message is found in DC@M01xxxx, it is issued from there. If it is not found, it is issued from message file DC@M01 (in English, if the original file hasn't been altered).
If the LANSA environment has been left, message file language selection does not apply and the messages will always come from file DC@M01.
To provide messages in all your supported languages, check that the message file DC@M01xxxx exists (where xxxx is the 4 character language identifier) for each language you will be using and ensure that it has the correct owner (the same as the LANSA system owner).
In summary
a. Use the merge message file commands. Initially, both versions of the message will be in English.
b. Translate the copied messages into the desired language. In an IBM i environment use the operating system change message commands.
