| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| COA/COD Error and setmqaut |
« View previous topic :: View next topic » |
| Author |
Message
|
| matth |
 Posted: Tue May 13, 2008 3:02 pm Post subject: COA/COD Error and setmqaut |
 |
|
Apprentice
Joined: 13 Feb 2007
Posts: 44
Location: Brazil
|
Hi:
I have this basic MQ enviroment:
app1 -> QM.A <-> QM.B -> app2
-QM.A is an MQ in Windows machine (MUSR_MQADMIN)
-QM.B is an MQ in Linux machine (mqm)
-QM.B have a transmition Queue QM.A to send messages do QM.A
-I have permission to manage only QM.B (QM.A is not mine).
So, after app1 send a message to app2, through QM.A, QM.B sends COA
report, but the COD report was not sent. In QM.B I´ve seen errors 2035.
I´ve searched for many foruns about this problem and found many explanations about authorization, etc, etc. I understood the problem, but
did´nt find any sollution.
I´ve tried to resolve problem with setmqaut commands, but it didn´t work (I don´t know if it´s necessary restart MQ after commands):
setmqaut -m QM.B -t qmgr -p mqm +connect
setmqaut -m QM.B -t queue -n QM.A -p mqm +allmqi
One solution which have worked is create an C program to use as MSGEXIT of receiver channel of QM.B. This program changes userid of
message to and user in QM.B machine and, when userid will be catch for create COD message, userid exits and not problem 2035 occours.
This solution works, but as I´m not C programmer, I can´t change it for
new version of MQ (was written to 5.3 release) either 64 bits machines.
(If anyone needs, I can send source code of Exit).
I seek a solution which doesn´t use Exits or external programs. If possible write de commands using parameters of enviroment explained above.
Regard´s |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue May 13, 2008 11:27 pm Post subject: Re: COA/COD Error and setmqaut |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| matth wrote: |
setmqaut -m QM.B -t qmgr -p mqm +connect
setmqaut -m QM.B -t queue -n QM.A -p mqm +allmqi
|
These commands are redundant. In a properly installed system, mqm has all authorities & this can't be changed.
| matth wrote: |
I seek a solution which doesn´t use Exits or external programs. If possible write de commands using parameters of enviroment explained above.
|
Don't use an exit. A problem this simple doesn't need an exit.
There was a recent dicsussion (which the search facility will find for you) on exactly this topic. It hinges on what id the COA & COD messages are put as. This user id needs to be valid & authorised on the target box.
My suggested actions:
- find this thread
- rip out this exit
- temporarially enable security events if you're having trouble working out which user is having problems
- think really, really carefully about using COA & COD. The search facility will turn up a number of discussions on the subject, most of them containing a post from me about how there's seldom a need for them but often a percieved need.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| matth |
| Posted: Wed May 14, 2008 6:54 am Post subject: Re: COA/COD Error and setmqaut |
|
|
Apprentice
Joined: 13 Feb 2007
Posts: 44
Location: Brazil
|
| Vitor wrote: |
Don't use an exit. A problem this simple doesn't need an exit.
There was a recent dicsussion (which the search facility will find for you) on exactly this topic. It hinges on what id the COA & COD messages are put as. This user id needs to be valid & authorised on the target box.
My suggested actions:
- find this thread
|
-I´ve searched for many threads about this problem, but no solution applied worked:
-1. I´ve set MCAUSER=mqm and keep PUTAUT=DEF on receiver channel of QM.B (stop/start channel after)
-2. I´ve set MCAUSER=mqm on SYSTEM.DEF.SVRCONN (stop/start app2 after)
| Vitor wrote: |
- rip out this exit
|
Ok.
| Vitor wrote: |
- temporarially enable security events if you're having trouble working out which user is having problems
|
Both MQs are standard installations. MUSR_MQADMIN on Windows and mqm no Linux. Problem, as described in DLQ, is that user mqm doesn´t have authorization on Windows machine (of course).
| Vitor wrote: |
- think really, really carefully about using COA & COD. The search facility will turn up a number of discussions on the subject, most of them containing a post from me about how there's seldom a need for them but often a percieved need. |
I understood security issues, but I don´t have access to standards of application (neither to change it), which is defined by business outside of my company. It is defined that COA and COD must works.
Regard´s |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 14, 2008 7:26 am Post subject: Re: COA/COD Error and setmqaut |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| matth wrote: |
| Both MQs are standard installations. MUSR_MQADMIN on Windows and mqm no Linux. Problem, as described in DLQ, is that user mqm doesn´t have authorization on Windows machine (of course). |
What do you mean "of course"? Even on Windoze mqm has rights in a standard installation. And if it doesn't (because you've used a non-standard user id for the install) then add an mqm user to the group.
| matth wrote: |
| Vitor wrote: |
- think really, really carefully about using COA & COD. The search facility will turn up a number of discussions on the subject, most of them containing a post from me about how there's seldom a need for them but often a percieved need. |
I understood security issues, but I don´t have access to standards of application (neither to change it), which is defined by business outside of my company. It is defined that COA and COD must works.
|
There is no business outside your company. You company is a business. A lot of which think WMQ is a syncronous messaging system like TCP/IP and insist on these response messages. Which often causes more trouble than they're worth.
http://www.mqseries.net/phpBB2/viewtopic.php?t=41880
http://www.mqseries.net/phpBB2/viewtopic.php?t=41001
http://www.mqseries.net/phpBB2/viewtopic.php?t=41237
For starters
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
