The targetNLS build descriptor option specifies the national language code used to identify runtime messages. If the Java™ locale on the development system is associated with one of the supported languages, the default value of targetNLS is the supported language. Otherwise, targetNLS has no default value.
For COBOL programs, the code for the first program in the run unit determines the language used for messages for all programs in the run unit.
When you generate Java code, the targetNLS build descriptor option assigns a value to the vgj.nls.code Java runtime property, but only if the genProperties build descriptor option is set to GLOBAL or PROGRAM. You can also change the value at run time using the sysLib.setLocale system function. For more information about system function, see the EGL Language Reference.
The following table lists the supported languages. The code page for the language you specify must be loaded on your target platform.
Code | Languages | Supported for COBOL |
---|---|---|
CHS | Simplified Chinese | Yes |
CHT | Traditional Chinese | Yes |
CZE | Czech | No |
DEU | German | Yes |
ENU | US English | Yes |
ESP | Spanish | Yes |
FRA | French | Yes |
HUN | Hungarian | No |
ITA | Italian | Yes |
JPN | Japanese | Yes |
KOR | Korean | Yes |
PLK | Polish | No |
PTB | Brazilian Portuguese | Yes |
RUS | Russian | No |
For more information about the user message table used for programs, see the section on the messageTablePrefix property in "Program part properties" in the EGL Language Reference. For additional details on the message table used for VGUI records in VGWebTransaction programs, see the topic for the msgTablePrefix build descriptor option.
JSF Handlers do not use a message table, but use a JavaServer Faces message resource. For details on that resource, see the description of the msgResource property in “JSF Handler" in the EGL Language Reference,