The usual style of CICS(R) programming is pseudo-conversational, that is, a series of independent transactions that are linked together to form a complete application.
When using the 3270 bridge, the link between the transactions of a pseudo-conversation is maintained by passing the Facility token and RemoteSysId returned by the first transaction of the sequence into subsequent messages of the conversation
.
When using a CICS system prior to CICS TS 2.2, for the first message for each transaction, you must set the:
shows a pseudo conversational 3270 transaction prior to CICS TS 2.2.
If your transaction is sending and receiving multiple messages, set:
If you want to end the transaction that is running, set the value of MQCIHCancelCode to a four-character abend code.
When using CICS TS 2.2 and subsequent releases, you can group the transactions of a pseudo-conversation together within a single bridge session, instead of using separate sessions for each transaction. Doing this reduces the overheads of the bridge monitor and improves performance. However, you can still use the multiple session approach if you need to maintain compatibility with older CICS releases, or if there might be long delays within a pseudo-conversation (for example waits for user input).
To group transactions into a single session, set:
If you want to end the transaction that is running, set the value of MQCIHCancelCode to a four-character abend code.
If you want to end a session between transactions set MQCIH.UOWControl to MQCUOWC_COMMIT.
The following diagram summarizes the values to use and expect in key fields in the MQMD and MQCIH in typical CICS 3270 bridge applications.
Figure 18 shows a conversational 3270 transaction.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq3wo2 |