Configuring TS and TD Queues for SOR Storage

The TSTDSRUE exit is called at queue access time with the following information:

Queue name
Queue type (TS|TD)
Scale-Out Repository (SOR) name

Note: The SOR name will be in upper case.

The exit needs to return whether or not to direct the queue to the input SOR:

0: Do not send to the SOR.
1: Send to the SOR.

A sample exit is provided with Enterprise Developer and can be found in the following locations src\enterpriseserver\exits\TSTDSRUE.CBL (Windows) or $COBDIR/src/enterpriseserver/exit/TSTDSRUE.CBL (UNIX).

The compiled program should be placed in the bin and\or bin64 (Windows) or $COBDIR/lib/es and/or $COBDIR/lib/es64 (UNIX).

If this exit is used, any SOR models which have been defined will be ignored.

Note: If a TS or TD queue name contains x'00' and that queue is to be written to a SOR, the name will be truncated from (and including) the x'00'. For example, x'AABB00CCDD' would be written with the name x'AABB'.

You must configure a TS model to ensure that Data File Editor correctly honors file locking across all enterprise server regions in a PAC. [6]

Separating queue data from system data when using Oracle Coherence

The default cache configuration file supports separating the storage of Temporary Storage (TS) and Temporary Data (TD) queue data from the general Performance and Availability Cluster (PAC) system data. Doing this enables the incompatible upgrade process to be performed. See Performing a Product Upgrade to a PAC Environment for more information. The system can be configured to always run in this way or be dynamically reconfigured when an upgrade is required. To separate the system and queue data, two sets of Coherence servers should be started, one set with the property mfescache.pacserver=false and the other with the property mfescache.qserver=false. Unless these properties are specified they will default to true so the server will store both system and queue data.