The EntireX RPC Server for CICS® ECI allows standard RPC clients to communicate with CICS programs running on IBM CICS®. It supports the programming languages COBOL and PL/I and transforms the RPC requests from clients into messages to CICS ECI. This document covers the following topics:
The RPC Server for CICS ECI acts on one side as an RPC server and on the other side as a client for CICS ECI. The RPC Server for CICS ECI is a Java-based component that can run on a different host to the one where CICS is running. This allows it to operate with a zero footprint of EntireX on the CICS host.
For local extraction, all source files have to be stored locally on the same machine where the Designer is running.
For existing CICS COBOL programs, use the IDL Extractor for COBOL to extract the Software AG IDL File for the RPC clients.
For existing CICS PL/I programs, use the IDL Extractor for PL/I to extract the Software AG IDL File for the RPC clients.
Remote extraction requires an RPC server running under z/OS with Extractor Service (Batch | IMS).
For COBOL, see Step 2: Select a COBOL Extractor Environment or Create a New One in the IDL Extractor for COBOL documentation.
For PL/I, see Extract Software AG IDL File from a Remote PL/I RPC Environment in the IDL Extractor for PL/I documentation.
RPC requests are worked off inside the RPC server in worker threads. If you are using RPC conversations, each RPC conversation requires its own thread during the lifetime of the conversation. The RPC Server for CICS ECI can adjust the number of worker threads to the number of parallel requests. The RPC server provides two worker models:
FIXED
The fixed model creates a fixed number of worker threads. The number of worker threads does not increase or decrease during the lifetime
of an RPC server instance.
DYNAMIC
The dynamic model creates worker threads depending on the incoming load of RPC requests.
For configuration and technical details, see property entirex.server.fixedservers under Administering the RPC Server for CICS ECI.