If the service requester is WebSphere® MQ-enabled,
you must use the WebSphere MQ-CICS Bridge to pass the request
message to the CICS SFR interface
program DFHMADPL.
Before you begin
There are many ways to start the WebSphere MQ-CICS
bridge. This section explains how to start the CICS® bridge
monitor program using WebSphere MQ triggering.
To
start the CICS bridge monitor program using WebSphere MQ
triggering, define the WebSphere MQ request queue
with TRIGGER, TRIGTYPE(FIRST) INITQ('initiation queue')
PROCESS('process') where:
- The initiation queue is the queue on which
the CKTI trigger monitor is listening.
- The PROCESS definition process must specify APPLTYPE(CICS)
APPLICID(CKBR). CKBR is the CICS bridge
monitor transaction ID. The USERDATA parameter
in the PROCESS definition can specify AUTH and WAIT options
for the CICS bridge monitor program.
About this task
The following steps describe how the run time is invoked
in asynchronous mode.
See Figure 1 for an illustration
of this process.
Procedure
- The service requester sends a request message to the request
queue. This message causes WebSphere MQ
to send a trigger message to the specified initiation queue.
- The WebSphere MQ trigger monitor program starts
the CICS bridge monitor task, which is part of the WebSphere MQ-CICS bridge.
- The CICS bridge monitor browses the request queue. If a message has arrived, the CICS bridge
monitor starts the CICS bridge link task, which is
part of the WebSphere MQ-CICS bridge.
- The CICS bridge link task links to the CICS SFR interface
program, passing the request message in a COMMAREA, and waits for
control to be returned. The request message that is passed
to the interface program does not include the WebSphere MQ
header data. The interface program defines and runs
a BTS process that starts the Navigation Manager, passes the information
from the request message in a series of BTS data-containers, and waits
for the service flow processing to complete.
- If a reply message is required, the CICS SFR interface
program passes it to the CICS bridge link task in the COMMAREA. The reply message contains the application data and the message
header.
- In synchronous processing, if the WebSphere MQ-CICS
bridge header (MQCIH) is not present in the request message, it does
not appear in the reply message, except in the case of an error.
- In asynchronous processing, the WebSphere MQ-CICS
bridge header (MQCIH) structure is always included in the reply message.
- The CICS bridge link task responds to the service
requester using an MQPUT command, if the MQMD ReplyToQ
and ReplyToQMgr are loaded.
Results
Figure 1. Invoking
the run time using WebSphere MQ-CICS Bridge