| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| API exits not working in MQv7.0.0.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Monk |
 Posted: Mon Apr 20, 2009 10:36 pm Post subject: API exits not working in MQv7.0.0.1 |
 |
|
Master
Joined: 21 Apr 2007
Posts: 282
|
Hi All,
I have a bit of a problem with the way API exits are working on MQ v7.0.0.1.
Let me explain whats happening.
As per the IBM documentation
| Quote: |
ExitUserArea (MQBYTE16)
This is a field that is available for the exit to use. It is initialized to binary zero for the length of the field before the first invocation of the exit for the task, and thereafter any changes made to this field by the exit are preserved across invocations of the exit. |
I initialize my exit user area with some member called 'testval'.
Now i change this value to 1 , in say MQPUT1_before() entry point and then when i try to read it from say MQOPEN_Before() or any of the Before entry points. I get this value to be zero.
But note that i call MQPUT1 first and then the rest of the API exits.
But the same code when run on MQv6 , it works, i.e it preserves the value across calls.
Is there something i m missing in MQv7 or should i raise a PMR?
_________________
Thimk |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Apr 20, 2009 11:43 pm Post subject: Re: API exits not working in MQv7.0.0.1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Monk wrote: |
| Is there something i m missing in MQv7 or should i raise a PMR? |
As I've said before, if you believe the product is working at varience to the documentation you should raise a PMR. Even if the product turns out to be working properly, it means the documentation needs to be revised.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Monk |
| Posted: Thu Apr 23, 2009 3:37 am Post subject: |
|
|
Master
Joined: 21 Apr 2007
Posts: 282
|
Hi All,
I found the solution on why exits dont work properly on AIX on MQ v7.
This is because we have a attribute on Server conn channels called "SHARECNV". this is also known as conversation sharing..
if you enable this , your exits will NOT work in the way you expect them..
Because your exits now run in different threads and you cannot pass info between them using exit user area...
however if you want to do this..you u disable conversation sharing and then your exits run in a single thread and everything will run just fine..
This one was a tricky one...
so be care full when u move ur exits from MQ v6 to MQ v7 and be aware of the new client connection features..
_________________
Thimk |
|
| Back to top |
|
|
| tkane |
| Posted: Mon Oct 26, 2009 10:13 am Post subject: |
|
|
Voyager
Joined: 23 Dec 2002
Posts: 82
Location: Kansas City
|
Is this documented anywhere? I think I'm running into something similar with a CHANNEL SECURITY exit.
I'm really struggling with the doc. There are references to serializing access to the MQCD but I think I'm seeing the same thing that you are. When many threads are present and shared conversations then I think the ExitUserArea might end up being updated in different threads (guess).
Oh the joy of new features! |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
