Considerations

Keep in mind the following information about national language support with CA ACF2 for z/VM:

The CA ACF2 for z/VM execs are shipped in mixed case. To convert your execs to uppercase (if, for instance, you have uppercase only terminals), run ACFUPCAS EXEC. This exec converts your CMS and EXEC messages to uppercase until you reIPL CMS.
If the LANG operand of VMXAOPTS does not define a language set for a user or if the corresponding language module is unresolved when you generate CP, CA ACF2 for z/VM uses the CA ACF2 for z/VM base language.
CA ACF2 for z/VM uses the base language for any message not defined in the language module. This means that a site‑written language module does not need to include all messages. For example, you could include only the most common messages, leaving CA ACF2 for z/VM base language to issue the least common messages.
The CA ACF2 for z/VM base language does not have to be the same as the system default language. You can define the IBM default language as a CA ACF2 for z/VM alternate language. CA ACF2 for z/VM always uses the IBM CP logic language.
During system access through LOGON and DIAL, CA ACF2 for z/VM uses the IBM system default language because IBM sets the VMDBK during logon to the system default language. CA ACF2 for z/VM does not use the directory specified language to reset the VMDBK language pointer until logon processing verifies the user is allowed to log on.