| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Problem with rollback MQGET, from COBOL,on z/Os, using RRSAF |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mr Butcher |
 Posted: Tue Jul 03, 2007 7:05 am Post subject: |
 |
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
did you use the ISPF RRS panels to verify (before the backout call) that you really have a UR with RRS running?
_________________
Regards, Butcher |
|
| Back to top |
|
 |
| advokaat |
| Posted: Wed Jul 04, 2007 12:09 am Post subject: |
|
|
Novice
Joined: 02 Jul 2007
Posts: 14
|
I will try to find the RRS-panels...
What is UR?
Anyhow: DB2 is rolled back correctly, only MQ isn't.... |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Jul 04, 2007 1:26 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
sorry - UnitofRecovery or UOW or whatever name exists for this
_________________
Regards, Butcher |
|
| Back to top |
|
|
| advokaat |
| Posted: Wed Jul 11, 2007 11:07 pm Post subject: |
|
|
Novice
Joined: 02 Jul 2007
Posts: 14
|
Specalists from my company have sent a "software request" to IBM.
(I have downgraded my cobol-program to a version without DB2, but still with MQ and RRSAF, and still the message GET from the queue isn't put back by an RRSAF-rollback) |
|
| Back to top |
|
|
| advokaat |
| Posted: Thu Jul 19, 2007 11:59 pm Post subject: |
|
|
Novice
Joined: 02 Jul 2007
Posts: 14
|
Answer from IBM:
============
MQGMO.Options in the trace has the following value:
MQGMO.Options = x'4045' (16453) = MQGMO_CONVERT + MQGMO_ACCEPT_TRUNCATED_MSG + MQGMO_NO_SYNCPOINT + MQGMO_WAIT
That's why Rollback doesn't restore the message in the queue. I look again the program and see an error when you set MQGMO.Options (don't pay attention the firt time I looked in the program). The value in the program is: COMPUTE MQGMO-OPTIONS = MQGMO-WAIT + MQGMO-ACCEPT-TRUNCATED-MSG + MQGMO-SYNCPOINT + MQMO-MATCH-CORREL-ID + MQGMO-CONVERT
Remove MQMO-MATCH-CORREL-ID and the value of MQGMO will be correct (x'4043').
If you want to match correlation ID: COMPUTE MQGMO-MATCHOPTIONS = MQMO-MATCH-CORREL-ID
Now it works, rollback occurs.
Can I conclude that in any options-assignment in MQ the right-hand-side should contain options with the same prefix? So all MQGMO and I should frown when seeing another prefix like MQMO?
(I used an existing program as the base for mine, and the error also occurs there)
Thanks for the help! |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jul 20, 2007 12:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| advokaat wrote: |
Can I conclude that in any options-assignment in MQ the right-hand-side should contain options with the same prefix? So all MQGMO and I should frown when seeing another prefix like MQMO?
|
You can. All the options are numerical values (bit patterns) and are added (anded) together, mixing options not intended for use together can give exactly the kind of unexpected reult you've seen.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 20, 2007 7:38 am Post subject: |
|
|
Guest
|
| MQGMO_NO_SYNCPOINT means that the MQGET will be not be part of the UR, will be comitted immediately, will not be rolled back. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
