Program definitions for remote CICS programs

Stabilized feature: CICS® support for Open Network Computing Remote Procedure Call (ONC RPC) is stabilized. Consider exposing and orchestrating applications as API services by using z/OS Connect Enterprise Edition or CICS web services, or by writing web applications in Java or Node.js. See also Stabilization notices and discontinued functions.

If a CICS program that is to service a remote procedure call runs in a different CICS system from CICS ONC RPC, a program definition is required on both the local system and the remote system.

The program resides on the remote system, so its definition there is straightforward. The program definition on the local system:
  • Must include a REMOTESYSTEM parameter to specify the system on which the program resides.
  • Can optionally include a REMOTENAME parameter if you want the names on the local system and remote system to be different.
  • Can optionally include a TRANSID parameter:
    • If TRANSID is not specified, the CICS program runs under the CICS mirror transaction on the remote CICS system.
    • If TRANSID is specified, the program in the remote CICS system runs under the transaction name given. See Transaction definitions for additional alias transactions for reasons why you may want a different name.

      If the remote transaction ID is specified, you must provide a matching transaction definition in the remote CICS system. This definition must specify the appropriate mirror program for the remote system (DFHMIRS for CICS for MVS/ESA and CICS Transaction Server for z/OS® systems).

If a CICS program is running on a CICS platform other than CICS for MVS/ESA or CICS Transaction Server for z/OS similar considerations apply, but you should refer to the DPL details for that platform.