Set up CICS

1. Run the resource definition utility DFHCSDUP, using the sample thlqual.SCSQPROC(CSQ4CKBC) as input, to define the bridge transactions and programs:

   CKBR	Bridge monitor transaction
   CSQCBCDI	Data conversion exit
   CSQCBR00	Bridge monitor program
   CKBP	Bridge ProgramLink transaction
   CSQCBP00	Bridge ProgramLink program
   CSQCBP10	Bridge ProgramLink abend handler program
   CSQCBE30	3270 bridge exit for WebSphere MQ (CICS Transaction Server, V1.3)

2. Add the load library to the DFHRPL concatenation of your CICS startup JCL.

3. Add the group, CSQCKB, to your startup group list.

Notes:

1. The bridge uses CICS temporary storage IDs with the prefix CKB. You should make sure these are not recoverable.

2. By default, your CICS DPL programs are run under transaction code CKBP. The transaction to be run can be specified in the MQCIH CICS-bridge header in the message. For more information, see the WebSphere MQ Application Programming Reference manual. You need to change the TASKDATALOC attribute to 'BELOW' if you are going to run 24-bit programs, otherwise you will get a CICS abend AEZC.

   If you want to run your programs under different transaction codes we need to install copies of the definition of CKBP, changing the transaction name to the ones of your choice. DPL bridge transactions must not be routed to a remote system.

3. To ensure that the bridge monitor can route requests to the correct region, each CICS region that runs a bridge monitor must have CICS links defined to all of the other regions that run bridge monitors.