Defining remote resources

This section contains guidance information about identifying and defining remote resources.

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.
Local and remote names for resources
CICS resources are usually referred to by name, for example, a file name for a file and a data identifier for a temporary storage queue. When you define remote resources, you must consider both the name of the resource on the remote system and the name by which it is known in the local system.
Defining remote resources for function shipping
If you use CICS function shipping, you might need to define the following remote resources: files, DL/I PSBs, transient data destinations, and temporary storage queues.
Defining remote resources for DPL
If you use CICS DPL, you might need to define remote server programs.
Defining remote resources for asynchronous processing
The only remote resource definitions needed for asynchronous processing are for transactions that are named in the TRANSID option of START commands.
Defining remote resources for transaction routing
CICS transactions can be routed to remote regions either statically or dynamically.
Defining remote resources for DTP
For MRO and LUTYPE6.1 links, there is no need to define any remote resources for DTP, provided that the front-end and back-end systems are directly connected. Both the remote system and the remote transaction are identified on the EXEC CICS commands issued by the front-end transaction. CICS therefore has all the necessary information to connect a session and attach the back-end transaction.

Parent topic: Defining intercommunication resources