UCS16 BE and other code pages on ZOS in EngageOne Generate

Although we don't state specifically that UCS16 BE is supported, we do support UCS2 BE, which is the same in principle.  UCS16BE is simply an updated version of UCS2 BE.

If you are running production on a host system that only has a code page of UCS16 BE, then you could either select Host Default as your encoding scheme (either globally in the Data Format, or at individual field level), or select UCS 2BE, and all Chinese characters should appear correctly.

If you have multiple code pages in your host environment, and UCS16BE is not the default, but is one of the available codepages, then you can ensure this is selected by entering the following parameter in your JCL:


Where xxxxxx equals the code page required.

This resides in the EXEC card statement, ie:

EXEC card syntax:
EXEC PGM=DOC1GEN,PARM='DD:HipRef [OPS=DD:OpsRef] [ECP=DD:EcpRef] [SCP=CodePage] [#restart] [,symbols]'
UPDATED:  July 18, 2019