| Author |
Message
|
| mqjeff |
 Posted: Fri Apr 06, 2012 2:18 am Post subject: |
 |
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Michael Dag wrote: |
Interesting discussion 
| mqjeff wrote: |
| Even though they're really just different ways of sending messages to the command server! |
when using runmqsc locally the command server is not involved I was told once  |
That's at least somewhat true, as I understand it.
And part of the problem being complained about here. |
|
| Back to top |
|
 |
| rcp_mq |
| Posted: Fri Apr 06, 2012 6:45 am Post subject: |
|
|
Centurion
Joined: 13 Dec 2011
Posts: 133
|
@mqjeff
You're absolutley right. That is why i take pdf prints of all pages i need, rename and categorize them according to subject, and put in a folder...(It's a lot of pain, but way easier to refer back than to browse through 50 pages and search) |
|
| Back to top |
|
|
| mqtablet |
| Posted: Fri Apr 06, 2012 1:11 pm Post subject: |
|
|
Acolyte
Joined: 09 Jun 2009
Posts: 71
|
MQSC commands will not use the command server.
| Code: |
DIS QL(SYSTEM.ADMIN.COMMAND.QUEUE) CURDEPTH DEFPSIST
1 : DIS QL(SYSTEM.ADMIN.COMMAND.QUEUE) CURDEPTH DEFPSIST
AMQ8409: Display Queue details.
QUEUE(SYSTEM.ADMIN.COMMAND.QUEUE) TYPE(QLOCAL)
CURDEPTH(0) DEFPSIST(NO)
:
ALTER QL(SYSTEM.ADMIN.COMMAND.QUEUE) DEFPSIST(YES)
2 : ALTER QL(SYSTEM.ADMIN.COMMAND.QUEUE) DEFPSIST(YES)
AMQ8008: WebSphere MQ queue changed.
:
ALTER QMGR CMDEV(ENABLED)
3 : ALTER QMGR CMDEV(ENABLED)
AMQ8005: WebSphere MQ queue manager changed.
|
After restarting the queue manager
| Code: |
DIS QL(SYSTEM.ADMIN.COMMAND.QUEUE) CURDEPTH
1 : DIS QL(SYSTEM.ADMIN.COMMAND.QUEUE) CURDEPTH
AMQ8409: Display Queue details.
QUEUE(SYSTEM.ADMIN.COMMAND.QUEUE) TYPE(QLOCAL)
CURDEPTH(0)
:
DIS QL(SYSTEM.ADMIN.COMMAND.QUEUE) CURDEPTH
2 : DIS QL(SYSTEM.ADMIN.COMMAND.QUEUE) CURDEPTH
AMQ8409: Display Queue details.
QUEUE(SYSTEM.ADMIN.COMMAND.QUEUE) TYPE(QLOCAL)
CURDEPTH(0)
|
The CURDEPTH(0) indicates that no command events are generated when you run a command in runmqsc, and hence command server is not used. |
|
| Back to top |
|
|
| mvic |
| Posted: Fri Apr 06, 2012 1:52 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
I'm not sure what you have proved, with those commands.
Anyway, runmqsc does not communicate with the queue manager through the command server. You could seek to prove that point by ending the command server and then watching your MQSC commands continue to work. |
|
| Back to top |
|
|
| mqtablet |
| Posted: Sat Apr 07, 2012 12:07 am Post subject: |
|
|
Acolyte
Joined: 09 Jun 2009
Posts: 71
|
| mvic wrote: |
| ending the command server and then watching your MQSC commands continue to work. |
I've tried this way back in MQ 6 and the runmqsc commands work even when the command server is not running.
And it my previous post what I mean to say is - when the command events are enabled, and when you run a command - if it uses the command server to process the command an event is generated and put to SYSTEM.ADMIN.COMMAND.EVENT queue.
What I tried to explain there is - initially the command event queue is empty, later i enabled the command events of the queue manager, restarted the queue manager, ran a command in runmqsc to check if any messages were generated in the SYSTEM.ADMIN.COMMAND.EVENT. Since there were no messages in the above mentioned queue, it means that the command server is not used for runmqsc command. You can try this by sending a PCF command and you can see the event messages in the command event queue.
I enabled the queue to be persistant to hold the messages after the queue manager restart.
Thanks. |
|
| Back to top |
|
|
| mvic |
| Posted: Sat Apr 07, 2012 2:56 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
|
| Back to top |
|
|
| mqtablet |
| Posted: Sat Apr 07, 2012 9:38 am Post subject: |
|
|
Acolyte
Joined: 09 Jun 2009
Posts: 71
|
| mvic wrote: |
1. the DIS QL and ALTER QL commands you ran were not for the event queue.
|
You are right, I should have done this on the event queue. Sorry, my mistake. I tried now on the event queue. Same result though.
| mvic wrote: |
The easiest test still would be to end the cmd server and observe runmqsc continuing to work. |
 |
|
| Back to top |
|
|
|
|
