Improved emulation with optimization

This example shows optimized data flows for the example 3270 transaction using the CICS-WebSphere MQ bridge.

CICS - WebSphere MQ Bridge Application 3270 Transaction

MQPUT to --MQCIH--------------------------------→ <Initial
start>
Bridge <business logic>
RequestQ

MQGET from ←--MQCIH+brmq_send_map+ADS+ADSDL--------- EC SEND MAP
FROM(ads)
Bridge EC RETURN
ReplyQ TRANSID(BAAA)

MQPUT to ----MQCIH+brmq_receive_map+ADS---------→ <Start>
Bridge
RequestQ EC RECEIVE MAP INTO(ads)
<business logic>

MQGET from ←--MQCIH+brmq_send_map+ADS+ADSDL--------- EC SEND MAP
FROM(ads)
Bridge EC RETURN
ReplyQ TRANSID(BAAA)
⋮

If you compare this sequence with the unoptimized flows shown in Exact emulation without optimization , you can see that the CICS® transaction does not have to send a RECEIVE MAP request vector, because the inbound RECEIVE MAP vector has already anticipated the requirement and the inbound map is already available to the transaction.



fg15700_.html | Timestamp icon Last updated: Monday, 5 June 2017