Using Internationalization with the PL/I Wrapper

RPC clients generated with the PL/I 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.

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. If they do not match, provide the codepage here. If a codepage is provided, it must also be a codepage supported by the broker and follow the rules described under Locale String Mapping.

The codepage is assigned to the RPC communication area in the field COM_CLIENT_CODEPAGE as described in Step 5: Optional Settings in the RPC Communication Area.

ERXCOM.COM_CLIENT_CODEPAGE = 'IBM-37';

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.