CA2E provides NLS support that allows applications generated by CA 2E to be language independent. This is done by removing hard-coded constants from panels and reports and placing them in message files. These message files can then be translated into several languages with the appropriate language resolved at execution time. This allows a single set of generated programs and panels to support multiple languages at execution time.
You can implement advanced NLS for a model, function, or field using external message identifiers. Using external messages, you can change from one national language to another, using the same set of application objects. Implementation of *MSGID at the field level would override implementation at the function level, as would function-level implementation override model-level implementation.
When you specify externalized screen constants for a model, function, or field,CA 2E converts screen text literals into messages (MSGID DDS keywords). There can be up to five messages for a literal, depending on the definitions: three for column headings, one for right-hand text, and one for left-hand text.CA 2E puts the messages in the message file specified by model value YPMTMSF at generation time. The generated application retrieves the messages from the message file at execution time.
Note: The default message file is xxPMTMSG in the generation library (GENLIB), where xx is the model object prefix defined by YCRTMDLLIB.
In order to facilitate maintenance of multi-language environments,CA 2E provides an exit program that automatically creates translated copies of prompt messages for each supported national language when you copy an NL-enabled device function.
For more information:
|
Copyright © 2014 CA.
All rights reserved.
|
|