Access to a TS pool by CICS® transactions running in an AOR is through a TS data sharing server that supports a named pool. In each MVS™ image in the sysplex, you need one TS server for each pool defined in a coupling facility which can be accessed from that MVS image. All TS pool access is performed by cross-memory calls to the TS server for the named pool.
An AOR can access more than one TS server concurrently. This multiserver access is required if you create multiple pools, because each TS server provides access to only one pool of TS queues.
CICS maps temporary storage requests to a TS server using the POOLNAME attribute of a TSMODEL resource definition, if one exists. Alternatively, if you are using a temporary storage table (TST) instead of TSMODEL resource definitions, CICS maps temporary storage requests to a TS server by means of the SYSIDNT option on the TST TYPE=SHARED macro.
The methods for specifying a TS pool make it easy to migrate queues from a QOR to a TS data sharing pool. You can use the TS global user exit, XTSEREQ, to modify the SYSID on a TS request so that it references a TS data sharing pool.
Figure 47 illustrates a parallel sysplex with three CICS AORs linked to the temporary storage server address space(s).
The server must be authorized to access the coupling facility list structure in which the temporary storage pool is defined; XES checks this. The server must also be authorized to act as a temporary storage server; AXM checks this. For information on how to define the necessary authorizations see the CICS RACF® Security Guide.
[[ Contents Previous Page | Next Page Index ]]