Remote resource considerations - IBM - AS/400

It is possible for one CICS system to access any resource defined on another CICS system. This section describes the steps you need to take in order to access remote resources, and how to allow remote CICS terminals to access resources in your CICS system.

Defining remote resources

1. Ensure that your CICS system and the remote CICS system mutually define each other in their respective TCS tables, and that the relevant network configurations are in place.
2. Define the resource locally to your CICS system, using the appropriate resource definition command and specifying the SYSID that you gave the remote system in the TCS definition as the “Remote CICS system” on the resource definition.

Defining remote terminals
Remote terminals may be defined as described for remote resources. However, it is also possible to define local TCTs as being “shippable”. This permits the local terminal definition to be shipped to the remote system when and if required, without having to have an explicit TCT definition for the terminal on the remote system.

Example TCT definitions for remote and shippable terminals
Figure shows an example definition for terminal SUR1.

Example TCT entry for a remote terminal

Figure shows an example definition for terminal SHP1.

Example TCT entry for a shippable terminal