CICS® resources are usually referred to by name: a file name for a file, a data identifier for a temporary storage queue, and so on. When you are defining 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.
CICS definitions for remote resources all have a REMOTENAME option (RMTNAME on macro-level definitions) to enable you to specify the name by which the resource is known on the remote system. If you omit this option, CICS assumes that the local and remote names of the resource are identical.
Local and remote resource naming is illustrated in Figure 52.
CICSA CICSB
(Local System) (Remote System)
DFHSIT TYPE= DFHSIT TYPE=
,APPLID=CICSA 1
3 ,APPLID=
DEFINE CONNECTION(CICR) 2
NETNAME(CICSB) 3
DEFINE CONNECTION(CICL)
1 NETNAME(CICSA)
4 DEFINE FILE(FILEA)
DEFINE FILE(FILEA) 4
REMOTESYSTEM(CICR) 2
DEFINE FILE(FILEB)
5 DEFINE FILE(FILEB)
DEFINE FILE(local-name)
REMOTESYSTEM(CICR) 2
REMOTENAME(FILEB) 5
Figure 52 illustrates the relationship between local and remote resource names. It shows two files, FILEA and FILEB, which are owned by a remote CICS system (CICSB), together with their definitions as remote resources in the local CICS system CICSA.
FILEA has the same name on both systems, so that a reference to FILEA on either system means the same file.
FILEB is provided with a local name on the local system, so that the file is referred to by its local name in the local system and by FILEB on the remote system. The "real" name of the remote file is specified in the REMOTENAME option. Note that CICSA can also own a local file called FILEB.
In naming remote resources, be careful not to create problems for yourself. You could, for instance, in Figure 52, define FILEA in CICSB with REMOTESYSTEM(CICL). If you did that, CICS would recursively reship any request for FILEA until all available sessions had been allocated.