Overview of DCE with CICS
The optional DCE Application Support server in z/OS enables a DCE client application anywhere in the DCE environment to access the resources of a CICS® system. The client program uses the simple DCE Remote Procedure Call (RPC), or the DCE Transactional Remote Procedure Call (TRPC), mechanism to call a CICS application program.
The client program does not need to know where the required CICS application is located, because MVS™ provides the location information. When the client and server are on different systems, the differences are transparent to the application programmer.
The Application Support server supports client programs written in C, and CICS application programs written in COBOL. The Application Support server automatically handles the conversions of the COBOL and C data types. Components of OS/390® Unix DCE Base MVS handle conversions of EBCDIC and ASCII data types, if needed.
Thus the Application Support server provides the powerful CICS application environments on the host, and the familiar (to the client workstation programmer) C language and RPC mechanism on the client.
- Coexists with all other ways of accessing CICS.
- Allows access to existing CICS applications and data.
- Allows new CICS applications to be developed as servers in the z/OS® UNIX System Services environment.
- Allows access to all files and databases available to CICS, including DB2® databases.
- Gives the host programmer continued access to all the facilities and tools in the CICS environments. This includes requests to run other programs on the same subsystem or different subsystems using the existing CICS mechanisms.
- Allows a client program to access CICS and does not require the client machine to have CICS transaction processing function installed.