On IBM's site, this problem describes our scenario:
http://www-1.ibm.com/support/docview.wss?rs=0&q1=IY29028&uid=swg1IY29028&loc=en_US&cs=utf-8&lang=
but it says it was fixed in CSD06 on 5.2
This next link says the problem has apparently resurfaces in 5.3, and again CSD06 will fix it. This problem directly referances the above one and says the 2 are similiar:
http://www-1.ibm.com/support/docview.wss?rs=0&q1=IC39552&uid=swg1IC39552&loc=en_US&cs=utf-8&lang=
(Thanks JasonE for these links).
I don't know if we are going to take an outage to apply a CSD just for this relativily minor problem. Maybe I will just delete and recreate the channel. But reading those above links, it looks like if the delete / recreate fixes it, there is no guarantee it won't happen again until CSD06 is applied.
-----Original Message-----
From: Tibor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 2:18 AM
To: [EMAIL PROTECTED]
Subject: Re: SNDR channel INITIALIZING after QM bouncePeter,
I suspect a garbage in SYNCQ because I've already seen similar. There was 2 entry for 1 channel and only way for starting channel after deleting and re-defining. Wrong entries disappeared by command 'DELETE CHANNEL' from the sync queue.
Hope this helps,
Tibor
----
> All machines in question are Windows 2000. MQ 5.3 CSD4. Being Windows boxes,
> you know what that means - monthly security patches with reboots! Yay!!!!
> These regular server reboots have surfaced the following issue in 2 of my 4
> environments. I have a channel which needs to be up pretty much all the
> time, so I have the DISCINT set to 300000. And the channel speed is set to
> fast (probably not relevant). This channel goes from QM1 to QM2, and it has
> a partner going from QM2 to QM1. The channels perform as expected when the
> QMs are running.
> When the QMs get bounced, this channel (which was running when the QM went
> down) comes up ready for more message in all 4 environments from QM1 to QM2,
> and from QM2 to QM1 in the LAB and in PROD. But in DEV and QA, the
> QM2.QM1.FAST channel always comes up as initializing, and stays that way
> until I manually start it.
> All the servers and MQ versions are identical.
> All the channels are defined identically (really, they are).
> The only difference I can see is when I browse the SYSTEM.CHANNEL.SYNCQ. On
> the problem channels, the corresponding message in the SYNCQ looks like it
> was put by AMQPCSEA.EXE. But for all the SNDR channels that don't come up
> INITIALIZING (they trigger normally), the corresponding message in the SYNCQ
> was put by runmqchl.exe. The last 100 bytes of each message in the SYNCQ is
> all garbled, so I can't tell what it means or if there is a difference
> between the "good" channels and the "bad" channels.
> Any idea why these channels keep coming up in INITIALIZING mode, and then
> why they are stuck in INITIALIZING mode until I issue START?
> In the error log on the sending side, I see the following, until I manually
> restart the channel. A weird error, since the channel is most definitely
> there, just stuck in INITIALIZING.
> 05/20/2004 20:25:38
> AMQ9002: Channel program started.
> EXPLANATION:
> Channel program 'QM2.QM1.FS' started.
> ACTION:
> None.
> ----------------------------------------------------------------------------
> ---
> 05/20/2004 20:25:38
> AMQ9519: Channel 'QM2.QM1.FS' not found.
> EXPLANATION:
> The requested operation failed because the program could not find a
> definition
> of channel 'QM2.QM1.FS'.
> ACTION:
> Check that the name is specified correctly and the channel
> definition is
> available.
> ----- amqrccca.c : 452
> --------------------------------------------------------
> 05/20/2004 20:25:38
> AMQ9999: Channel program ended abnormally.
> EXPLANATION:
> Channel program 'QM2.QM1.FS' ended abnormally.
> ACTION:
> Look at previous error messages for channel program 'QM2.QM1.FS' in
> the error files to determine the cause of the failure.
> ----- amqrccca.c : 776
> --------------------------------------------------------
> Peter Potkay
> MQSeries Specialist
> The Hartford Financial Services
> [EMAIL PROTECTED]
> x77906
> IBM MQSeries Certified
> This communication, including attachments, is for the exclusive use of
> addressee and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, any use, copying,
> disclosure, dissemination or distribution is strictly prohibited. If
> you are not the intended recipient, please notify the sender
> immediately by return email and delete this communication and destroy all copies.
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
