Use of cross-memory services for shared data tables

Cross-memory services are used to satisfy an application programming command when all the following conditions have been met:

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).

Connection

Commands cannot use cross-memory services until the SDT connection is made between the AOR and the remote data table. Also, if a browse sequence starts before the connection is made, all subsequent requests in the sequence use function shipping services. This is likely to occur if the connection cannot be established at the STARTBR command because the data table is not open, and the command causes the data table to be implicitly opened. The connection is then made on the next new request to the data table, but the original browse sequence continues to use function shipping services.

Disconnection

When a connection has been made, it remains in force until either the AOR deletes its remote file definition or the FOR closes or disables the file. The effects of close or disable are described below.

Related concepts
Application programming for data tables
Application programming for a CICS-maintained data table
Application programming for a user-maintained data table
Differences between function shipping and cross-memory services
Differences between shared data tables services and VSAM
[[ Contents Previous Page | Next Page Index ]]