| Author |
Message
|
| mnance |
 Posted: Mon Oct 21, 2002 3:52 am Post subject: AMQMDAIN command |
 |
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
I am using this command to automatically start my Qmgr, Lsr, TrigMon, and chinit. However, when I use the command to start my listener it creates two listeners. This is all done usiing a script that is run during setup to configure the Qmgr and its components to automatically start. The command that I am issuing looks like this:
amqmdain crtlsr "QmgrName" -t TCP
Can anyone explain to me why it is creating TWO Listeners? Please help. Thanks.
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
 |
| nimconsult |
| Posted: Mon Oct 21, 2002 11:14 pm Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
The listener is automatically started with your queue manager (if you have defined a listener in the services snap-in with start-up automatic).
By the way it should be the same with chinit, trigmon and command server.
This is the big difference between AMQMDAIN and STRMQM. STRMQM only starts the queue manager, while AMQMDAIN starts all associated services defined with automatic start-up.
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
| mnance |
| Posted: Tue Oct 22, 2002 4:07 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
Well after the initial installation...the Qmgr is not set to startup automatically. So issue the following commands:
amqmdain auto "QmgrName"
amqmdain start "QmgrName"
amqmdain crtchi "QmgrName" SYSTEM.CHANNEL.INITQ
amqmdain crtlsr "QmgrName" -t TCP
amqmdain crttrm "QmgrName" "QmgrName".INITQ
If I understand correctly....all that I need to do is issue the first two commands above and the rest will start automatically? Currently only the listener is starting to instances with the following commands.
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| nimconsult |
| Posted: Tue Oct 22, 2002 11:49 pm Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
Well, check that your trigger monitor, channel initiator and command server are set to automatic start-up in the MQ Series services snap-in.
If they do not start check your error logs after start-up. Maybe one of the services fail starting.
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
| mnance |
| Posted: Wed Oct 23, 2002 5:00 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
The Trigger Monitor and Channel Init do not appear in the MQSeries Services Snap-in unless I issue the commands above. When I install MQSeries the only objects that appear are the Qmgr and Command Server. The Qmgr is not set to Automatic until I issue the amqmdain command in the script. Are you saying that once I issue the amqmdain auto/start "QmgrName" command that a listener will auto start as well?? How come it does not appear in the MMC?
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| 2189 |
| Posted: Thu Oct 24, 2002 5:28 am Post subject: |
|
|
Apprentice
Joined: 22 Oct 2002
Posts: 31
|
I just did this:
C:\T>crtmqm GAF
WebSphere MQ queue manager created.
Creating or replacing default objects for GAF.
Default objects statistics : 31 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
C:\T>amqmdain CRTLSR GAF TCP -p 1415
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
'GAF' listener created successfully
C:\T>amqmdain AUTO GAF
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Queue Manager 'GAF' successfully set to 'Automatic' mode
C:\T>amqmdain START GAF
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Queue Manager 'GAF' successfully started
Which created and started:
Qmgr
1 Commands server
1 Listener
1 Channel Initiator
Try doing the same commands and see what you get. If you still get 2 listeners then try it on another machine.
_________________
2189 errors make me  |
|
| Back to top |
|
|
| mnance |
| Posted: Thu Oct 24, 2002 11:35 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
2189, thanks for the help.
I gave it a shot and so far it works. I do not understand why the difference in order would fix such a problem...or rather why it makes a difference. Can anyone explain that??
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| 2189 |
| Posted: Mon Oct 28, 2002 4:15 am Post subject: |
|
|
Apprentice
Joined: 22 Oct 2002
Posts: 31
|
Not sure why you got two instances of the listener but I would have thought issuing the START option before creating the listener/trig monitor would have meant they exist but just wouldn't be in a running state.
Btw you may already know this but you can check how many listeners/trig monitors exist and the current status of these and all other MQ services by running amqmdain status QMGRNAME.
e.g.
amqmdain status ADMIN
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
The MQSeries service status is: Ready
Queue Manager 'ADMIN' is: Stopped
0 Queue Manager (Stopped)
1 Command Server (Stopped)
2 Channel Initiator (Stopped)
3 Listener (Stopped)
_________________
2189 errors make me |
|
| Back to top |
|
|
| mnance |
| Posted: Mon Oct 28, 2002 4:20 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
Thanks for the current status command....didnt know that. I was just using a tlist from a command prompt in order to see if their was more than one listener.
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
|
|
