How CICS DPL programs run under the CICS-WebSphere MQ bridge

A WebSphere® MQ message provides the data needed to run a CICS® DPL program. The CICS-WebSphere MQ bridge builds a COMMAREA or container from this data, and runs the program using EXEC CICS LINK.

Figure 1 shows the sequence of actions taken to process a single message to run a CICS DPL program.
Figure 1. Components and data flow to run a CICS DPL program
A diagram illustrating the components and data flow to run a CICS DPL program with the CICS-WebSphere MQ bridge, as described in the following paragraph.
  1. A message, with a request to run a CICS program, arrives on the request queue.
  2. The bridge monitor task, which is constantly browsing the queue, examines the message.
  3. The bridge monitor task starts the CICS DPL bridge task using either your specified transaction, or CKBC (if you chose to use a container), or you can use the default CKBP transaction (if you chose to use a COMMAREA). CKBC uses channels and containers, instead of a COMMAREA. The program used is DFHMQBP3. CKBP uses the COMMAREA, and the program used is DFHMQBP0. If you use your own specified transaction, you can select the relevant program you chose to use.
  4. The CICS DPL bridge task, for either program DFHMQBP0 or DFHMQBP3, receives the message from the request queue.
  5. The DFHMQBP3 program puts the message payload into container DFHREQUEST in channel DFHMQBR_CHANNEL, and issues EXEC CICS LINK to the specified program. The DFHMQBP0 program puts the message payload into a COMMAREA and issues EXEC CICS LINK to the specified program.
  6. The DFHMQBP3 program expects the application to place its response message payload in container DFHRESPONSE in channel DFHMQBR_CHANNEL. If the application does not provide a payload for the response message it should still return a container; in this case it is an empty container. The DFHMQBP0 program expects the application to place its response message payload in the COMMAREA used by the request.
  7. The DFHMQBP3 program puts the content of the DFHRESPONSE container into the reply message payload, and also puts the reply message to the reply-to queue. The DFHMQBP0 program puts the content of the COMMAREA into the reply message payload, and also puts the reply message to the reply-to queue.

The user transaction ends or requests more input. If this flow is the last one in the pseudo conversation, the transaction ends. If the message is not the last one, the transaction waits until the next message is received or the specified timeout interval expires.

Multiple CICS programs

A unit of work can be just a single user program, or it can be multiple user programs. The number of messages that you can send to build up a unit of work is not limited.

In this scenario, a unit of work built from many messages works in the same way, with the exception that the bridge task waits for the next request message in the final step unless it is the last message in the unit of work.



zc12220_.html | Timestamp icon Last updated: Sunday, 4 June 2017