Unicode data

CICS® Transaction Server for z/OS® provides limited support for Unicode-encoded character data. Workstations can share UCS-2 or UTF-8 encoded data with CICS Transaction Server for z/OS provided that no conversion is required.

More extensive support for conversion to and from Unicode data is available in CICS if you use channels to communicate your data. See Enhanced inter-program data transfer using channels.

The following table lists the supported CCSIDs and shows the following information:
  • The value to be specified for the CLINTCP or SRVERCP keyword.
  • The code page identifier or identifiers (CPGIDs).
  • An IANA-registered character set name for the code page, where a suitable name exists and CICS supports the use of this name on EXEC CICS commands. The CICS-supported name might be the primary name or a preferred alias. In some cases, more than one name or alias is supported.
Table 1. Unicode
CLINTCP SRVERCP CCSID CPGID IANA character set name Comments
1200
UCS-2
 01200 01400 utf-16 Unicode with character set 65535. In the absence of a byte-order mark (BOM), assumed to be UTF-16 BE (big-endian).
1208
UTF-8
 01208 01400 utf-8 Unicode with character set 65535. UTF-8.
13488 13488 01400 iso-10646-ucs-2 Unicode with character set 3001 (fixed at Unicode 2.0 character repertoire). In the absence of a byte-order mark, assumed to be UTF16-BE (big-endian).
17584 17584 01400   Unicode with character set 3004 (fixed at Unicode 3.0 character repertoire). in the absence of a byte-order mark, assumed to be UTF16-BE (big-endian).