| Author |
Message
|
| fcasali |
 Posted: Tue May 03, 2005 12:36 am Post subject: Channel Initiator Error on Startup |
 |
|
Novice
Joined: 09 Jul 2004
Posts: 12
Location: Torino, Italy
|
Hi all.
I'm working with WMQ 5.3 CSD09 on iSeries platform.
I have configured a Queue Manager named 'ITBSUAA1' with some local, remote and alias queues. That QMGR owns 2 sender channels triggered by the Channel Initiator listening on the SYSTEM.CHANNEL.INITQ.
The jobs for starting up the QMGR, the listener, the trigger monitor and the channel initiator were all correctly scheduled.
Now, at the startup I see the channel initiator active on the SYSTEM.CHANNEL.INITQ but if i look at the AMQERR01.LOG file I see these messages:
| Quote: |
...
-------------------------------------------------------------------------------
05/03/05 04:00:07
AMQ7163: WebSphere MQ job 78 started for ITBSUAA1.
EXPLANATION:
Cause . . . . . : The job's PID is 78 the CCSID is 37. The job name is 004211/QMQM/RUNMQCHI.
Recovery . . . : None
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
05/03/05 04:00:08
AMQ8024: WebSphere MQ channel initiator started.
EXPLANATION:
Cause . . . . . : The channel initiator for queue SYSTEM.CHANNEL.INITQ has
been started.
Recovery . . . : None.
Technical Description . . . . . . . . : None.
-------------------------------------------------------------------------------...
-------------------------------------------------------------------------------
05/03/05 04:00:08
AMQ9509: Program cannot open queue manager object.
EXPLANATION:
Cause . . . . . : The attempt to open either the queue or queue manager
object 'SYSTEM.CHANNEL.INITQ' on queue manager 'ITBSUAA1' failed with reason code 2042.
Recovery . . . : Ensure that the queue is available and retry the
operation.
Technical Description . . . . . . . . : None.
----- amquopra.c : 3906 -------------------------------------------------------
...
|
Any idea about the reason of such an error ?
Thank you
_________________
Regards,
Fabrizio Casali
IT Specialist Advisory |
|
| Back to top |
|
 |
| Gouldmar |
| Posted: Tue May 03, 2005 6:59 am Post subject: |
|
|
Novice
Joined: 03 May 2005
Posts: 11
Location: Munich, Germany
|
A 2042 return code is occuring as MQ is detecting that a process has the queue open for exclusive input. These may be due to channels trying to start when the channel initiator has been started successfully. You will need to check the queue to see what has got the queue open and how it has opened the queue. You will also need to check the definition of the queue as the default share option most likely will be set to 'Exclusive', this is how IBM supply the definition for a number of other platformss.
I would recommend not using the SYSTEM.CHANNEL.INITQ for application channels, this will meen that each channel will need to be defined with its own XMITQ, this will not only simplify you problem diagnosis but will also ensure that channel failures will not cause your XMITQ to become full and affect other applications.
If your problem persists list and post your channel definitions, this will help diagnose the problem. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue May 03, 2005 7:10 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
| I would recommend not using the SYSTEM.CHANNEL.INITQ for application channels, this will meen that each channel will need to be defined with its own XMITQ |
You certainly should use SYSTEM.CHANNEL.INITQ....just not for a XMITQ. If you are using it for an XMITQ you have your definitions incorrect.
If you have triggered channels then the XMITQ should be what is triggered. It should use the SYSTEM.CHANNEL.INITQ as its INITQ and the channel name as trigger data. No additional trigger monitor need be used. MQ will take care of things for you.
Hope this helps |
|
| Back to top |
|
|
| fcasali |
| Posted: Tue May 03, 2005 7:22 am Post subject: |
|
|
Novice
Joined: 09 Jul 2004
Posts: 12
Location: Torino, Italy
|
Currently I'm using the SYSTEM.CHANNEL.INITQ for triggering the channels for the 2 XMITQ we have.
Application queues triggering is done through the ITBSUAA1.TRIGGER.INITQ.
My doubts arise from the fact that I can't see any conflict:
channels have their init queue, local queues have another init queue.
Thanks
_________________
Regards,
Fabrizio Casali
IT Specialist Advisory |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue May 03, 2005 7:27 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is it possible you are trying to start up an additional CHIN?
It may be that you don't need to manually start the CHIN for your environment any more.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Gouldmar |
| Posted: Tue May 03, 2005 7:27 am Post subject: |
|
|
Novice
Joined: 03 May 2005
Posts: 11
Location: Munich, Germany
|
| Thanks for the correction kevinf2349, I have seen a similar problem with a new MQ site getting the same thing, their problem was using the SYSTEM.CHANNEL.INITQ without using a xmitq, just forgot to add the bit about using the SYSTEM.CHANNEL.INITQ on the xmitq. |
|
| Back to top |
|
|
| fcasali |
| Posted: Tue May 03, 2005 7:35 am Post subject: |
|
|
Novice
Joined: 09 Jul 2004
Posts: 12
Location: Torino, Italy
|
| jefflowrey wrote: |
Is it possible you are trying to start up an additional CHIN?
It may be that you don't need to manually start the CHIN for your environment any more. |
Mmmm ... I start the CHIN into the CL that starts also the QMGR, the listener and the trigger monitor ...
Is this correct or it si started automatically with the queue manager?
_________________
Regards,
Fabrizio Casali
IT Specialist Advisory |
|
| Back to top |
|
|
| vennela |
| Posted: Tue May 03, 2005 8:13 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Is this correct or it si started automatically with the queue manager? |
AFAIK, the CHIN starts automatically with the QMGR os iSeries
You can create a test QMGR and start the QMGR and see the processes (jobs) that are running for that QMGR and see if the CHIN is running.
CHIN automatically starts when the QMGR is started on distributed platforms. |
|
| Back to top |
|
|
| fcasali |
| Posted: Tue May 03, 2005 11:50 pm Post subject: Problem solved! |
|
|
Novice
Joined: 09 Jul 2004
Posts: 12
Location: Torino, Italy
|
Thank you very much indeed for all the kindly answers.
Thanks particularly to jefflowrey for the smart hint and to vennela for the confirmation of the automatic start of the CHIN.
No more errors now 
_________________
Regards,
Fabrizio Casali
IT Specialist Advisory |
|
| Back to top |
|
|
|
|
