The table below shows the command-line options for the C Wrapper if the IDL Compiler is used. Default values are underlined. Options can be valid for client and server side, see column Client and Server.

Option	Client	Server	Value	Description
-DCONTEXT	Yes	No	0 | 1	Multithreaded Client. 0 Off. The generated client interface objects can be used in single-threaded client environments. 1 On. The generated client interface objects are thread-safe and can be used in multithreaded client environments. See Generate RPC Client for more information.
-DDATA_CONV_A	Yes	Yes	0 | 1	Mapping of IDL type A fields. 0 Map IDL data type A to the C data type unsigned char[..] without null termination (mainframe Natural, COBOL, PL/I style). 1 Map IDL data type A to C style strings See Mapping Options for more information.
-DDATA_CONV_NP	Yes	Yes	0 | 1	Mapping of IDL type P, PU, N and NU fields. 0 The IDL data types are mapped to C data type unsigned char[..] with packed or unpacked (mainframe Natural, COBOL, PL/I style) contents. 1 The IDL data types are mapped to C data type double. See Mapping Options for more information.
-DDATA_CONV_U	Yes	Yes	0 | 1	Mapping of IDL type U fields. 0 Map IDL Data type U to the C data type unsigned wchar_t[..] without null termination (mainframe Natural, COBOL, PL/I style). 1 Map IDL Data type U to wide char strings. See Mapping Options for more information.

See also Starting the IDL Compiler and IDL Compiler Usage Examples.

Example Generating an RPC Client

erxidl -t client.tpl -DDATA_CONV_A=1 -DDATA_CONV_U=1 example.idl

The generated C source files (client interface object and its associated header file) will be stored in parallel to the IDL file.

Example Generating an RPC Server

erxidl -t server.tpl -DDATA_CONV_A=1 -DDATA_CONV_U=1 example.idl

The generated C source files (server interface object and its associated header file) will be stored in parallel to the IDL file.