Which remote resources need to be defined?

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

You may 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. 14

The remote resources that can be defined are:

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

A note on "daisy-chaining"

The descriptions of how to define remote resources in this section usually assume that there is a direct link between the local CICS and that on which the remote resource resides. In fact, in all types of CICS intercommunication, the local and remote systems need not be directly connected. A request for a remote resource can be "daisy-chained" across CICS systems by defining the resource as remote in each intermediate system, as well as (where necessary) in the local system.

Note:
The following types of request cannot be daisy-chained:

Related concepts
Local and remote names for resources
Related tasks
Defining remote resources for function shipping
Defining remote resources for DPL
Defining remote resources for asynchronous processing
Defining remote resources for transaction routing
Defining remote resources for DTP
Defining local resources

14.
But see "A note on "daisy-chaining"".

[[ Contents Previous Page | Next Page Index ]]