For all Server Options only.
(ESD #2) Two new parameters, RPCPROGCCSID and RPCDATACCSID, have been added to the SYGWMCST configuration macro in the SYGWXCPH customization module. They can be used only if USEIBMUNICODE=Y. Instead of coding TDPROPS SET APIs in each Remote Procedure Call (RPC) application program, you can set the default Program and Data Coded Character Set Identifiers (CCSIDs) for RPCs across the region.
When using these parameters, consider the following:
You must use the new SYGWMCST macro to reassemble the customization module SYGWXCPH that will be used with this and later EBFs.
Set through TDPROPS API, the Program and Data CCSID properties are mainly intended for visualizing mainframe data by the server applications. In this case, they are usually set to an EBCDIC CCSID. However, they can also be useful in some internal data transformations, in which case they are not limited in value to EBCDIC CCSIDs.
The RPCPROGCCSID and RPCDATACCSID parameters should be set to EBCDIC CCSIDs only. Because the parameter values are not checked against a predefined list of valid CCSIDs, you need to verify that the CCSID is valid.
RPCPROGCCSID controls the conversion of data between the server and server application and has a default of 500. You should set it to an EBCDIC CCSID—ideally, to the one that is used internally by the z/OS subsystems. (For example, it can be the value of the SCCSID generation parameter in DB2.)
RPCDATACCSID controls the conversion for metadata and has a default of 500. It is usually set to the value of RPCPROGCCSID.
The new parameters can be used in place of, or together with, TDPROPS SET APIs. If needed, the TDS_PROG_CCSID and TDS_DATA_CCSID properties can be still used by the server application to dynamically change Program or Data CCSIDs.
All CCSIDs used to set Program and Data CCSID values must be described through the SYGWMCXL macro in the SYGWXCPH module. For these CCSID entries, there is no requirement to the name specified in the CHARSET parameter of the macro.
