RPC clients generated with the COBOL Wrapper do not convert your application data (in RPC IDL type A, K, AV and KV fields) before it is sent to the broker. The application's data is shipped as given by the RPC client program.

• For Operating System z/OS

  • By default, no codepage is transferred to the broker. It is assumed the broker's locale string defaults match. See Broker's Locale String Defaults.

  • You can provide the CCSID in the field COMM-CCSID of copybook ERXCOMM to tell the broker the encoding of your application data. Do this before issuing broker and RPC calls, for example in Step Optional Settings in the RPC Communication Area (Call Interface | CICS).

    Example:

    MOVE 37 TO COMM-CCSID.

  • If a CCSID is provided, it is sent as CP<number> to the broker. It must be a codepage supported by the broker and follow the rules described under Locale String Mapping.

• For Operating System Windows

  • The Generic RPC Service module assumes the data is given in the encoding of the Windows ANSI codepage configured for your system. A codepage identifier of this Windows ANSI codepage is automatically transferred to tell the broker how the data is encoded.

  • If you want to adapt the Windows ANSI codepage, see the Regional Settings in the Windows Control Panel and your Windows documentation.

• For all other Operating System

  • No codepage is transferred to the broker. It is assumed the broker's locale string defaults match. See Broker's Locale String Defaults.

Enable character conversion in the broker by setting the service-specific attribute CONVERSION to "SAGTRPC". See also Configuring ICU Conversion under z/OS | UNIX | Windows | BS2000. More information can be found under Internationalization with EntireX.