| Author |
Message
|
| pichelma |
 Posted: Fri Apr 19, 2002 12:02 pm Post subject: |
 |
|
Apprentice
Joined: 11 Mar 2002
Posts: 25
|
Hi all,
I am having problems starting my channel init. "after" creating it.
This is the error:
04/19/2002 13:02:02 AMQ9509: Program cannot open queue manager object.
This is the error code explained by MQRC:
D:MQS-TMP>MQRC amq9509
536909065 0x20009509 rrcE_MQOPEN_FAILED
536909065 0x20009509 urcMS_MQOPEN_FAILED
MESSAGE:
Program cannot open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object '<insert two>' on
queue manager '<insert three>' failed with reason code 1111.
ACTION:
Ensure that the queue is available and retry the operation.
I am manually running these commands in a (Windows)batch file:
rem Set Q-mgr to start automatically
mqmdain auto %state%_%env%
rem Create Channel initiator
amqmdain crtchi %state%_%env% SYSTEM.CHANNEL.INITQ
rem Create the Q-mgr listener.
amqmdain crtlsr %state%_%env% -t tcp -p 1416
rem Start listener
runmqlsr -t tcp -p 1416 -m %state%_%env%
rem Start Channel Initator
runmqchi -m %state%_%env% -q SYSTEM.CHANNEL.INITQ
What am I missing here?
Is there a proper sequence for the creation/startup of the initiator/listener?
Is my registry possible corrupted w/ the many removals/deletion of channels,queues and Q-mgr's?
RUNMQSC shows all normal attributes/settings. Compared w/ another MQS 5.2.1 machine as well.
Thanks for any help on this...
Scott
|
|
| Back to top |
|
 |
| StefanSievert |
| Posted: Fri Apr 19, 2002 2:36 pm Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
Scott,
is it possible that your channel initiator is already running (autostarted by the MQServices?) when you try to issue the runmqchi command? RUNMQCHI opens the channel initiq in exclusive mode so any subsequent attempt to start it will fail; usually with a different return code, though.
Hm....
Stefan
_________________
Stefan Sievert
IBM Certified * MQSeries
In the end everything is right. If not, it's not the end.
[ This Message was edited by: StefanSievert on 2002-04-19 15:40 ] |
|
| Back to top |
|
|
| pichelma |
| Posted: Fri Apr 19, 2002 2:54 pm Post subject: |
|
|
Apprentice
Joined: 11 Mar 2002
Posts: 25
|
Steven,
Thanks for the reply...however, that was not the case.
I tried starting it from Explorer(GUI) and w/ RUNMQCHI.
In MQservices it showed up as defined but "stopped".(startup/automatic)
Tryed right-clicking(start) on it, got an error msg. AMQ4208, nothing in MQRC on that.
However, AMQ9509 was reported when I issued from cmd line.
Maybe an APAR? This is straight 5.2.1 only no CSD's.
I know CSD01,02,03,04 are out. 05 is coming...right?
Any other suggestions?
Need more details or opther info? Please let me know.
Much appreciated, thanks!
Scott
|
|
| Back to top |
|
|
| pichelma |
| Posted: Thu Apr 25, 2002 7:59 am Post subject: |
|
|
Apprentice
Joined: 11 Mar 2002
Posts: 25
|
Hi all,
Figured this out....Either Windows/MQSeries does not "update" MQseries Services properly. A refresh or stop start of MQS Services does NOT work.
The solution was to stop/start MQSeries services "completely".
After, startup MQS Services again an "runmqchi" or Channel initiator shows up as "running"!
Scott
|
|
| Back to top |
|
|
| ping master |
| Posted: Wed Aug 27, 2003 1:15 pm Post subject: |
|
|
Centurion
Joined: 20 Sep 2002
Posts: 116
Location: USA
|
yes completely stop/start MQ services works.. or rebooting works too..
BUT, in your batch file, you could also add:
TASKKILL /F /IM RUNMQCHI.EXE
after you start qmgr call and it will work perfect also....
I had run into the same exact problem on MQ 5.3/ XP
$PM |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Thu Aug 28, 2003 6:33 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
I've noticed as well that the MQ Services panel isn't always accurate. It often says that the chinit is "stopped" even though it's running.
The surefire way to tell is check for the runmqchi process in task manager.
Cheers
Steve |
|
| Back to top |
|
|
|
|
