How do I use it?
Several new parameters have been introduced for Unicode support.
- There are two values supported for the existing CODE parameter - UTF8 or UTF16 format.
- There are two new parameters, LOCAL_CHARSET and REMOTE_CHARSET which allow you to specify the character-set of the local and remote files for the transfer.
- The MBCS_INPUTERROR and MBCS_CONVERROR parameters allow you to specify what action is taken in the event of a conversion error. If not specified the value of DEFAULT_INPUTERROR and DEFAULT_CONVERROR parameter values will be used.
- LOCAL_DELIM and REMOTE_DELIM are used to specify the encoding scheme that the corresponding character-set uses and a list of delimiters which exists within the data as record separators.
Both CA XCOM partners must be running r11.6 or higher.
How is the translation being done? Do I still have to provide tables?
No, you do not have to provide any tables.
- On z/OS, CA XCOM is using IBM Unicode Services to perform data conversion functions.
- On Windows and Linux, CA XCOM is using the ICU (International Components for Unicode) toolkit to perform data conversion functions.
Where can I find out more?
You can find out more by reading the Release Notes for your 11.6 product. The release notes have several pages of detailed information on this new support. For detailed usage documentation, please see the User Guide.
Does it replace translation tables?
Translation tables may still be used. However going forward use of the new Unicode support is a better way to handle translation for any language.
Use of Unicode would alleviate you having to keep translate tables up to date or the need for any new ones or calling support for help with a translation table.
You can setup and use the new Unicode support without having to remove your existing translate tables.
Is this support available on all XCOM platforms?
Unicode support and Multi-Byte Character set support are available in XCOM platforms starting with the 11.6 level.