Which remote resources need to be defined?

Remote resources are resources that reside on a remote system but that need to be accessed by the local CICS® system. In general, you must define all these resources in your local CICS system, in a similar way as you define your local resources, by using CICS resource definition online (RDO) or resource definition macros, depending on the resource type.

You might need to define remote resources for CICS function shipping, DPL, asynchronous processing (START command shipping), and transaction routing. No remote resource definition is required for distributed transaction processing. However, see A note on daisy-chaining.

The remote resources that can be defined are as follows:
  • Remote files (function shipping)
  • Remote DL/I PSBs (function shipping)
  • Remote transient data destinations (function shipping)
  • Remote temporary storage queues (function shipping)
  • Remote programs for distributed program link (DPL)
  • Remote terminals (transaction routing)
  • Remote APPC connections (transaction routing)
  • Remote transactions (transaction routing and asynchronous processing).

All remote resources must also be defined on the systems that own them.