A client has a
problem where his MQ application is failing but he says the MQ updates are not
rolling back. I'm sure he's got something wrong in his code but before I berate
him I just want to confirm my understanding and ask if there are any known
issues.
If an application
(WIN2K)gets a
A problem with an exit can result in an unexpected behavior, look in
Websphere MQ Application Programming Guide.
Gunter
Am Fr, den 11.06.2004 schrieb Kelly, Steve um 12:08:
A client has a problem where his MQ application is failing but he says
the MQ updates are not rolling back. I'm sure he's
Steve,
In general I would always suggest that applications explicitly issue MQBACK
or MQCMIT call since there are slight differences in behaviour on different
platforms. However, what you say is true. An MQDISC will implicitly commit
the transaction if possible. It is described in the Usage Notes
: Friday, June 11, 2004 8:53 AM
To: [EMAIL PROTECTED]
Subject: Re: MQ Rollback
Steve,
In general I would always suggest that applications explicitly issue MQBACK
or MQCMIT call since there are slight differences in behaviour on different
platforms. However, what you say is true. An MQDISC
