I’m not overly clear on what your environment is: where are the services and where is the client? You indicate that your RPC server is on Windows, but COBOL CICS is on the mainframe, not Windows…
However, I do understand your confusion…there are so many things called the “rpc server” and “rpc client” that it is difficult to keep them straight when starting out…
Assuming you mean that your .Net application is trying to retrieve data/services from the mainframe COBOL CICS environment, you will need:
- a .Net Client Wrapper
- EntireX RPC Server in CICS
EntireX CICS RPC Server calls the COBOL routine via an EXEC CICS LINK, passing parameters in the COMMAREA.
Just to clarify: RPCSRVI is needed if you are doing RPC calls from your COBOL programs - that is, if the COBOL programs are the client of an RPC server. I am working with a customer now that is serving up Oracle/Unix data via a Java RPC Server running on a Windows 2003 box to mainframe Natural/Cobol/Assembler clients. For this, we generate the COBOL Services (RPCSRVI) and the COBOL wrapper (a stub that is called from the mainframe programs to pass the call on via EntireX Communicator to the Java RPC Server).
On my machine, documentation on EntireX RPC in CICS is under C:\Program Files\Software AG\EntireX\Docu\install\os390\rpc_cics.htm. This will explain how to configure the EntireX RPC Server for CICS on the mainframe (z/OS or OS/390). (From the doc main menu, look under “Components of EntireX” for “EntireX RPC Servers”). For information on server programs (COBOL called from the EntireX RPC Server for CICS), check under “Components of EntireX” for “EntireX Developer’ Kit”, then “EntireX in your Application” for COBOL - “EntireX RPC for COBOL”.
For the client piece, you want to read the .Net Wrapper information under C:\Program Files\Software AG\EntireX\Docu\devkit\rpc_dnet\overview.htm.