e-business Application Solutions on OS/390 Using ... - IBM Redbooks

BROWSER
HTML
JAVASCRIPT
Webserver
Figure 118. MQM Bridge to IMS Protocol
Non-Conversational Transaction
Connect
Open Replyqueue
Open toIMSqueue
Put message in toIMSqueue
out of syncpoint
Close toIMSqueue
Get message from Replyqueue
with correlid
Close Replyqueue
Disconnect
MQM V 1.1.4 / 1.2
Manager
M
Q
I
B
I
N
D
A
T
T
A
C
H
M
E
N
T
O
T
M
A
IMS/ESA
In both cases, the MQI/IMS bridge is used to reach IMS. As such, the command
flow used in both cases is about the same. The MQI/IMS bridge uses two
channels through a special storage class defined as communicator with IMS. One
channel will be used as a “To Channel,” the other one is the “From Channel.”
Following are the definitions of the channels as they were used during our testing.
DEFINE STGCLASS(TOIMSB) PSID(1) DESCR('OTMA TO IMSB') + ▌1▐
REPLACE XCFGNAME(ITSOIMS) XCFMNAME(APIMSA58) ▌2▐
DEFINE QLOCAL( 'MQS2.TOIMSB' ) + ▌3▐
REPLACE +
COMMON QUEUE ATTRIBUTES
DESCR( 'OTMA TO IMSB' ) +
SHARE +
NOTRIGGER +
DEFSOPT(SHARED) +
DEFPSIST(NO) +
LOCAL QUEUE ATTRIBUTES
GET( ENABLED ) +
STGCLASS(TOIMSB) +
INDXTYPE( NONE )
DEFINE QLOCAL( 'MQS2.FROMIMSB' ) + ▌4▐
REPLACE +
COMMON QUEUE ATTRIBUTES
DESCR( 'REPLYQ FROM IMSB' ) +
PUT( ENABLED ) +
DEFPRTY( 5 ) +
DEFSOPT(SHARED) +
DEFPSIST(NO) +
LOCAL QUEUE ATTRIBUTES
Chapter 11. Accessing IMS Transactions from the Web 237