Author |
Message
|
ycae |
Posted: Wed Aug 02, 2006 12:45 am Post subject: reply-to queue |
|
|
Newbie
Joined: 01 Aug 2006 Posts: 7
|
Hi,
How does it work with the reply-to queue?
Here is the situation. QmgrA sends a message to QmgrB. In this message there is a request for a reply to Queue X. But by doing that we get an error message on QmgrB that the report message could not be put to the Queue X on QmgrA with reason code 2035.
Do i have to define this reply-to queue?
i asked the guys from I5 (former as400) if they have any error message but they say that they don't see anything.....am i doing something wrong???
Thanks again for the help.
Yves |
|
Back to top |
|
 |
Vitor |
Posted: Wed Aug 02, 2006 12:50 am Post subject: Re: reply-to queue |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
ycae wrote: |
Do i have to define this reply-to queue?
|
I would say the queue is already defined or you'd have a different problem.
Have you tried looking up a 2035 reason code and following the suggestions? Indeed what problem investigation have you already performed? (there's no point us suggesting things you've already tried)  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
ycae |
Posted: Wed Aug 02, 2006 1:10 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2006 Posts: 7
|
what i found out is that the 2035 reason code means that there is an authority problem......but i checked with the other guys and they told me that there are no restrictions......that's strange.......
i also tried to define a remoteq on my side pointing to the reply-to queue on the remote system but of course this didn't help  |
|
Back to top |
|
 |
Vitor |
Posted: Wed Aug 02, 2006 1:21 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Your people say there are no restrictions; the queue manager says 2035. I think the queue manager has a better tactical position here
There are always restrictions, because the queue manager has security switched on. Now if what they mean is the site standard is to authorise everybody to do everything then that's fine (if a little silly) but it's not the same as no restrictions.
(Disclaimer - I'm not an i5 or AS/400 guy. Some of this may be stupidly wrong.)
One possible cause is that the user id doing the put being unrecognised. It's all very well saying that a public group can do anything, but you can't give that authority to unknown users. Check that the user id is at least defined to the remote system.
Also check that "your people" have done their usual trick on the reply to queue, i.e. that it allows anyone to do anything. There may be an authority missing.
Failing that enable authority events on the queue manager, try it again& see what the actual failure is. Don't forget to disable the events after you've finished - they're a serious overhead. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
zpat |
Posted: Wed Aug 02, 2006 2:23 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
If the reply-to-queue is remote, the QM will place it initially on the xmit queue - make sure the application has access to this queue. |
|
Back to top |
|
 |
ycae |
Posted: Wed Aug 02, 2006 3:40 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2006 Posts: 7
|
how can i check the authority of this queue??? |
|
Back to top |
|
 |
Vitor |
Posted: Wed Aug 02, 2006 3:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Please bear my earlier comment regarding AS/400 knowledge in mind...
I think what you want is the DSPMQMAUT command, which you'll find listed in the documentation.
I think you might also want to spend a little time doing some background reading, which will equip you to find answers to simple questions like this without waiting for a reply. I commend the Security manual to you, along with the Administration guide for your platform. Both contain a wealth of useful information.  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Hassan |
Posted: Wed Aug 02, 2006 10:21 am Post subject: |
|
|
 Voyager
Joined: 01 Apr 2004 Posts: 81 Location: Toronto, Canada
|
Check which User id are the messages being "put" under. Use the same Id to do sample puts to figure out exactly where the problem lies. (CALL PGM(QMQM/AMQSPUT0) PARM(QNAME QMNAME))
For auth commands on the i5 command line enter
go cmdmqm
which will bring up a list of all mq commands on i5, page down to the following for Auth Commands.
42. Display WebSphere MQ Object Authority DSPMQMAUT
43. Grant WebSphere MQ Object Authority GRTMQMAUT
44. Revoke WebSphere MQ Object Authority RVKMQMAUT
45. Refresh WebSphere MQ Object Authority RFRMQMAUT
46. Work with WebSphere MQ Authority WRKMQMAUT
47. Work with WebSphere MQ Authority Data WRKMQMAUTD
Make sure to use RFRMQMAUT after making ANY auth changes.
Having said that listen to Vitor and please do some background reading .... it would prove beneficial in the long run. |
|
Back to top |
|
 |
|