Application programming for DCE remote procedure calls
Support for DCE remote procedure calls (RPCs) enables a non-CICS client program running in an Open Systems Distributed Computing Environment (DCE) to link to a server program running in a CICS® system.
Writing a client program
For information about coding DCE client programs, see the z/OS® Distributed Computing Environment: Application Development Guide and the z/OS Distributed Computing Environment: Application Development Reference .
Writing a server program
This information gives an overview only of how to write CICS programs to act as servers to DCE remote procedure calls. For further related information, see Defining CICS programs as DCE servers.
- Use a communications area to pass input and output parameters.
- Pass input and output parameters by value (not by pointer).
- Contain only data-handling logic. Existing applications that have their data-handling and terminal input/output logic in separate programs can be used without modification.
- Ideally, be written in COBOL. This is because the Application Support server compiler produces only COBOL data structure definitions for your CICS communications area, to match the RPC parameters. You can, however, write your server application in another programming language, by manually defining a communications area data structure that exactly overlays that produced in COBOL by DCE.
- Use the same subset of EXEC CICS commands as CICS DPL server programs. For a list of the restricted commands, see Exception conditions for LINK command.
- Use CICS intercommunication facilities to access data and programs owned by other APPC-connected systems. For example, they can use the Front End Programming Interface (FEPI) to emulate a 3270 terminal, and thereby act as a front end for other unchanged CICS or IMS™ applications.
- Communicate with applications in remote CICS systems, using function shipping, DPL, or distributed transaction processing.
- Contain terminal input/output logic to the principal facility. (You can use APPC terminal control commands to do distributed transaction processing to a remote back-end system.)
- Use basic mapping support (BMS).
These restrictions are the same as those for CICS distributed program link servers. Thus, you may be able to use server programs written for CICS-to-CICS DPL as servers to DCE clients.
As described in Interface definition , you must use the z/OS DCE Application Support server compiler to generate a data structure definition for the RPC parameters passed to your server program, and an execution stub for the server. You must link-edit and load the stub into the server stub library.