Defining remote temporary storage queues

A remote temporary storage queue is one that resides on another CICS system. CICS temporary storage requests that are made against a remote queue are shipped to the remote system by CICS function shipping.

Applications are typically designed to access temporary storage queues without being aware of their location. In the local CICS system, you can create TSMODEL resource definitions for temporary storage queues that match a specified prefix. To make the temporary storage model point to a remote system, use the following attributes:
  • REMOTEPREFIX (or XREMOTEPFX) specifies the prefix for the temporary storage queue on the remote system.
  • REMOTESYSTEM specifies the name of the connection that links the local system to the remote system where the temporary storage queue resides.
When an application specifies a temporary storage queue name that matches the prefix defined by the temporary storage model, CICS ships the request to the remote system.

It is also possible for CICS application programs to name a remote system explicitly on temporary storage requests, using the SYSID option, or to use the XTSEREQ global user exit program to direct the request to a system on which the appropriate queue is defined. With these methods, there is no need for the remote temporary storage queue to be defined in the local CICS system. However, note that TSMODEL resource definitions do not support these methods for specifying a temporary storage queue that resides in a temporary storage data sharing pool. If you want to specify an explicit SYSID for a shared queue pool, in your application program or through the XTSEREQ global user exit program, you must use a temporary storage table (TST) with a TYPE=SHARED entry for the shared queue pool.



dfht1c00150.html | Timestamp icon Last updated: Sunday, 4 June 2017