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.

CICS definitions for remote resources all have a REMOTENAME option (RMTNAME on macro-level definitions) so that you can 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.

The following table shows local and remote resource naming. Related resources and attributes are shown by identical numbers.
Table 1. Local and remote resource naming
  CICSA (local system) CICSB (remote system)
System initialization parameters 
APPLID=CICSA        1 
 
 3       APPLID=CICSB
CONNECTION resources 
CONNECTION(CICR)    2 
NETNAME(CICSB)      3  
         CONNECTION(CICL)
 1       NETNAME(CICSA)
FILE resources 
FILE(FILEA)         4 
REMOTESYSTEM(CICR)  2 

FILE(FILEB)

FILE(local-name)
REMOTESYSTEM(CICR)  2 
REMOTENAME(FILEB)   5    
 4       FILE(FILEA)




 5       FILE(FILEB)
The table 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.