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. For an introduction to DCE RPCs, see DCE remote procedure calls.

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 manual.
Writing a server program
Note:
This is 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. For definitive information, see the OS/390 DCE Application Support Programming Guide.

CICS server programs must:

CICS server programs can:

The Application Support server does not support CICS application programs that:

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 DCE MVS/ESA 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.

Related concepts
What is DCE?
DCE remote procedure calls
Overview of DCE with CICS
What CICS server programs can do
Related tasks
Defining CICS programs as DCE servers
[[ Contents Previous Page | Next Page Index ]]