Use of cross-memory services for shared data tables

Cross-memory services are used to satisfy an application programming command when all the conditions listed here have been met.

  • CICS® must retrieve the SYSID of the target system from the file's resource definition in the AOR. This condition is met when the application programming command either specifies no explicit SYSID, or specifies a SYSID the same as the AOR itself and the SYSID given in the file resource definition is the same as the FOR.

    Within a single browse sequence, an application should not change between specifying an explicit SYSID and not specifying one, as this is likely to lead to unpredictable results.

  • The serving system has logged on; that is, it has registered itself as a shared data table owner.
  • The requesting system has connected to the server for the files specified on the application programming command.
  • The file supports the requested function.
Note: Function shipping of a request might result in “daisy chaining”; that is, the request passes through one or more intermediate CICS nodes between the region issuing the request (an AOR) and the region owning the resource (the FOR). In such cases, use of shared data tables cross-memory services is limited to the final link (from the last intermediate system to the FOR).