ARTTSQ manages temporary storage queues, it serves the functionalities required by EXEC CICS: WRITEQ TS, READQ TS and DELETEQ TS. Two versions of ARTTSQ server are delivered : ARTTSQ (for Oracle db), and ARTTSQ_UDB (for UDB) . TMS and OPENINFO must be defined accordingly.

ARTTSQ publishes two main kinds of services:

• TSQUEUE: This service is published only once when the first ARTTSQ starts. TSQUEUE processes TSQ requests for queues matching no TSMODEL.
• {TSMODEL}_TSQUEUE: One of those services is published for each TSMODEL.

  The server publishing this service will accomplish all the operations needed on the queues matching this TSMODEL.

  One server will publish the TSMODELs belonging to the resource groups assigned to this server thru the -l option.

  A group of resources must be assigned to a single tsq serverto avoid trying to publish the same service twice. This is checked at boot time and will generate error messages during the boot phase when not respected, but no action will be taken.

  It is critical, and verified by TSQ servers at boot time, that MIN and MAX number of servers are set to 1.

  It is critical that the same server which created one queue (first write) also serves all other read/write delete requests to this queue. This is the reason why each service, either generic or corresponding to a specific model, must be advertised by a single server.

  This unicity is verified when services are published.

  The auxiliary TSQ data is lost after the server is down (e.g. stop or crash).