| Author |
Message
|
| ind76 |
 Posted: Mon Sep 30, 2002 12:01 pm Post subject: Channel Sequence Number ! |
 |
|
Apprentice
Joined: 10 Apr 2002
Posts: 29
|
Hi
I have a problem on Widows2000 machine with Sender Channel which connects to OS/390 that goes to retry mode whenever it gets started, the error message in the error log tells the sequence number is out of sync and need to reset the sequence number as one of the possibilities.
We have to manually issue RESET channel everytime it gets started. Is there any way to fix this problem forever ? Why would the sequence number goes out of sync whenver the channel is started ? It has DISC INTERVAL and HBINT and the adoptMCA is enabled on both ends.
Any help is greatly appreciated.
Thanks,
ind76 |
|
| Back to top |
|
 |
| dgolding |
| Posted: Tue Oct 01, 2002 1:59 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Oct 01, 2002 3:31 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
When the mainframe is brought up are the queue/channel definitions refreshed ????
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| ind76 |
| Posted: Tue Oct 01, 2002 6:10 am Post subject: |
|
|
Apprentice
Joined: 10 Apr 2002
Posts: 29
|
Thank you dgolding and jeff.
I checked the SYSTEM. CHANNEL.SYNCQ. There are no duplicate messages. Jeff, the queues and channels on the mainframe are not refreshed. This problem started recently and we had no problem with this channel before.
Thanks for your replies.
ind76 |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Oct 01, 2002 6:37 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
We had a similar issue, when the mainframe was booted the MQSeries
definitions are replaced from a script and this would cause us our out of
sync issue. The problem revolved around the SYSTEM.DEF.RCVR Channel
it appears that some of it's attributes are propagated to all the other receivers on the mainframe, one of which was according to IBM, if the SYSTEM.DEF.RCVR had a reset command issued to it (just once) that it could cause this issue. They had us delete and recreate the SYSTEM.DEF.RCVR channel and this resolved the issue.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| ind76 |
| Posted: Tue Oct 01, 2002 9:32 am Post subject: |
|
|
Apprentice
Joined: 10 Apr 2002
Posts: 29
|
Thank you Jeff,
We are going to delete and create the channel and see what happens this afternoon. I'll let you know what happens.
Thanks,
ind76 |
|
| Back to top |
|
|
| ind76 |
| Posted: Tue Oct 01, 2002 3:01 pm Post subject: |
|
|
Apprentice
Joined: 10 Apr 2002
Posts: 29
|
Nope, it did not help, the same problem. We'll have to delete and recreate the queue manager, I guess.
Thanks for your help,
ind76 |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Oct 02, 2002 10:05 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
We recently had the same problems, and only with Win2K servers... we had a PMR open with IBM but were not able to provide the doc as it was hit and miss...
Let me know if you get any resolution to this problem.
Steve |
|
| Back to top |
|
|
| twegmann |
| Posted: Fri Oct 04, 2002 11:07 am Post subject: |
|
|
Novice
Joined: 09 Aug 2001
Posts: 23
Location: New Jersey
|
We had a similiar problem on AS/400 with channel sequence numbers getting out of sequence.
We have not identified what caused the sequence numbers to get out unsynched. IBM has indicated they guess it was a corrupt message, but haven't found a smoking gun to prove it.
The resetting of the channels resulted in us losing messages (and yes, we were using persistence!). IBM is currently trying to diagnose what the deal is on this. |
|
| Back to top |
|
|
|
|
