You should review your use of CICS® on System/390® data conversion facilities.
If the ECI is used by a Client, consider the following:
- The client code page is always specified by the Client. Any client code page specified in the CICS conversion
table, DFHCNV, is overridden by the Client. (The code page overridden is the
value of the CLINTCP option on the DFHCNV TYPE=ENTRY macro for the server
program.)
- The server code page is that specified in the
DFHCNV conversion table (on the DFHCNV TYPE=ENTRY macro for the server program).
- For binary data conversion, the default binary format defined on DFHCNV
TYPE=FIELD entries is overridden by the Client.
If the EPI is used by a Client, consider the following:
- Data conversion is done in the terminal-owning region.
- The client code page is specified by the Client.
If the Client specifies an invalid code page, code page 850 is used.
- The server code page is determined from CICS on System/390’s
remote definition of the virtual Client terminal. The second value of the
CGCSGID option of the TYPETERM definition is used, if specified. If a value
is specified, it must be a code page that is supported by CICS on System/390. If no
value is specified, a default code page is used, as shown in Table 44.
- No binary data conversion is required for the EPI.
For more information about defining code pages and conversion tables for
data conversion between CICS on System/390 and non-System/390 systems, see Data conversion for communication with non-System/390 systems.
[[ Contents Previous Page | Next Page Index ]]