You can use the sample thlqual.SCSQPROC(CSQ4CKBM) to define a queue named SYSTEM.CICS.BRIDGE.QUEUE, or define your own. If you define your own, set the following attribute:
If recovery is required, set the following attributes:
If you want to process messages in FIFO sequence, set the following attribute:
If the request queue is defined with QSGDISP(SHARED), you must also define it with INDXTYPE(CORRELID). This setting is also recommended for non-shared queues.
If you want to start the bridge by triggering, set the following attributes:
If the bridge is to be accessed remotely from WebSphere MQ, you need channel and transmission queue definitions, and a remote queue definition for the request queue. For more information about using remote queues see WebSphere MQ Intercommunication.
Consider specifying BOQNAME and BOTHRESH on the bridge requests queue to ensure that messages are put to the specified backout queue when a message has been processed and backed out BOTHRESH times, rather than being placed on the dead-letter queue. If you specify a backout queue, put a process in place to process messages on this queue.
If 3270 bridge reply messages are sent to a non-z/OS system, the sender channel should specify the CONVERT(YES) option.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsav0452 |