Interesting.  Learn something new every day...  :)
-----Original Message-----
From: Glen Shubert [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 12, 2004 4:03 PM
To: [EMAIL PROTECTED]
Subject: Re: Channels in Retrying status, part 2.


Actually, according to IBM, there can be multiple messages per channel on the SYNCQ.  I was not given a reason why.  We found this out while fighting a problem last summer.  They then shipped me CSQ4SUTL which can identify problems and clean up messages on the queue.

Glen Shubert
[EMAIL PROTECTED]
Associate Director
TSYS - MQSeries Technical Support



"Carroll, Y. (Yvette)" <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>

02/12/04 03:01

Please respond to MQSeries List

       
        To:        [EMAIL PROTECTED]
        cc:        
        Subject:        Re: Channels in Retrying status, part 2.

Hi

The channel syncq maintains, among other things, the sequence numbers for
all the channels.  It should have one entry per channel.  
Sometimes there is more than one entry per channel and that can cause

sequence number errors.

But I'm not sure why or how the multiple entries get created though.

-----Original Message-----
From: Curt Dolny [
mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 11, 2004 7:04 PM

To: [EMAIL PROTECTED]

Subject: Channels in Retrying status, part 2.

Hi All,

Environment consists of MQ for z/OS 5.3 queue managers, MQ for HP-UX 5.2
and MQ for HP-UX 5.3 queue managers, and MQ for AIX 5.3 queue

managers...

A few weeks ago, I asked this fine list about a situation we are having
where we would periodically find some of our channels between the z/OS

queue managers and some of the other Unix queue managers in a Retrying

status.  A couple people suggested that I delete and redefine the

channels because something was wrong in the SYSTEM.CHANNEL.SYNCQ

queue...

Deleting and redefining the channels appears to work, in that I do not
see the channels in Retrying status when I issue the dis chs() commands.

My questions now are: Why did this work?  What specifically in the

entries in SYSTEM.CHANNEL.SYNCQ would have been messed up?  And

importantly, what might have caused this in the first place?  Someone

had also mentioned a utility from IBM that can analyze the

SYSTEM.CHANNEL.SYNCQ, but I couldn't find anything like this.  Anyone

know what/where this utility is?

Thanks much.

     Curt


This email and any accompanying attachments may contain confidential and proprietary information.  This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited.

Emails cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

If verification of this email or any attachment is required, please request a hard-copy version.



The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you


This email and any accompanying attachments may contain confidential and proprietary information.  This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited.

Emails cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient.

If verification of this email or any attachment is required, please request a hard-copy version.


Reply via email to