Configuring and Deploying WebSphere MQ for CA Gen › Configure z/OS Servers

Configure z/OS Servers

CA Gen supports applications running MQSeries with CICS or IMS serving as the TP monitor. By default, in both z/OS CICS and z/OS IMS, processing requests received by its queue manager triggers a CA Gen DPS, and it sends the processed result back to the DPC through the reply-to queue that is associated with the request. In this default configuration, every DPS is a process object to WebSphere MQ, and each DPS requires its own local queue.

CA Gen server managers deployed to either z/OS CICS or z/OS IMS rely on triggering. With IMS, you can use a trigger type of either FIRST or EVERY, but z/OS CICS users should configure their systems for trigger type EVERY.

With CA Gen, z/OS CICS users have the option of using the CA Gen WebSphere MQ Transaction Dispatcher for CICS. The Transaction Dispatcher for CICS (TDC) acts as a dispatcher between WebSphere MQ and one or more DPS applications. With the TDC, you can perform the following tasks:

• Share the same WebSphere MQ queue between multiple server managers.
• Tune the TDC operation through a user exit routine, the TIRMQTDX.

  Note: For more information about the TIRMQTDX user exit, see the User Exit Reference Guide.

• Support transaction-level security (see Transactional Security with the TDC).
• Spawn multiple copies of the TDC to process a queue in parallel (see Triggering and the TDC).

The following sections further explain the TDC.