MQSeries.net :: View topic - OS/390 IMS

PeterPotkay · Posted: Thu Oct 17, 2002 6:08 am Post subject: OS/390 IMS - MQCONN call

We incorporate an MQWrapper. All mainframe programs in the online environment that need to talk to MQ call this one program. We have a Batch version as well. In the Batch version, I wrote it so that a calling app can pass back and forth the connection handle and the object handle during a job. In this way, the wrapper does not have to Connect/Open and Close/Disconnect each time it is called. For the duration of the job, as long as the handles are maintained by the calling app, all is good.

Can this concept be implemented in any way in the Online environment? I don't think so, but want to be absolutely sure, since a new project we have that calls the wrapper is very time sensitive. Milliseconds count. The MQCONN/MQDISC combination takes on average 200 ms. And we need to do that every time we need to send a message. The reason I think it wont work is that in the Online environment, I have many different users in many different TCODES all calling the common module. I don't see how a connection handle could be shared among all of them. Even if it was possible, if any of them do a commit or rollback, everyone would be affected, since the connection handle to the QM is what ties an MQ UOW together. All actions under that handle would be affected. Also, when a TCODE ends, doesn't an implicit disconnect occur anyway, killing the handle whether you like it or not?

Am I correct in telling the customer that it is not possible to do this in the Online Environment. And even if it was, it wouldn't be safe anyway due to commits/rollbacks?
_________________
Peter Potkay
Keep Calm and MQ On