| Author |
Message
|
| knegarpetter |
 Posted: Fri Dec 17, 2004 5:56 am Post subject: The sequence of the channel |
 |
|
Apprentice
Joined: 10 Dec 2004
Posts: 39
|
How can i se e the sequence of the channel?
and do they have to match "on both sides"?
regards
petter |
|
| Back to top |
|
 |
| mq_abcd |
| Posted: Fri Dec 17, 2004 12:25 pm Post subject: |
|
|
Acolyte
Joined: 13 Jun 2004
Posts: 69
|
U can see the sequence numbers
runmqsc <qmgr name>
dis chs(*) all
yes they have to be the same
if they are not
see thee error logs and
for the sender chl
reset chl(CHLNAME)
READ THE "intercommunicaton manual"
Search this site u can find lots of info
ESSKAY |
|
| Back to top |
|
|
| JT |
| Posted: Fri Dec 17, 2004 12:58 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| How can i se e the sequence of the channel? |
What platforms?
RUNMQSC is not available on the z/OS platform, and I believe OS/400. |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Dec 17, 2004 1:01 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| JT wrote: |
| RUNMQSC is not available on the z/OS platform, and I believe OS/400. |
RUNMQSC is not but MQSC commands are available for those platforms also.
You can also use M072 to issue MQSC commands for any platform by client connecting. |
|
| Back to top |
|
|
| knegarpetter |
| Posted: Mon Dec 20, 2004 12:52 am Post subject: |
|
|
Apprentice
Joined: 10 Dec 2004
Posts: 39
|
LSTSEQNO(3) ?? or?
What would the error log look like if there where a sequense mis match??
regards
Petter |
|
| Back to top |
|
|
| csmith28 |
| Posted: Mon Dec 20, 2004 4:54 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Good question.
I don't recall ever having seen an error in the AMQERR0*.LOGS related to mismatching message sequences. That doesn't mean no entry was made but I am pretty sure I have looked in the logs when there was a Sequence issue and if I saw one I would remember it. Or atleast I think I would.....  But I have slept since then. 
I am not even sure if a sequence issue is reported in the SYSTEM.ADMIN.CHANNEL.EVENT queue.
But, if the channel is INDOUBT when you do a "dis chs(CHANNEL.NAME) all" against it the CURSEQNO is the first thing I would check.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| EKhalil |
| Posted: Tue Feb 08, 2005 5:46 am Post subject: |
|
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
From SDSF\DA on ZOS (channel initiator started task)
+CSQX526E !YOURQMGRNAME CSQXRESP Message sequence error for channel YOURCHANNEL.NAME, 599
sent=6042 expected=1 |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue Feb 08, 2005 6:25 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
From a AIX AMQERRxx.log
| Code: |
02/02/05 13:23:21
AMQ9526: Message sequence number error for channel 'TEST1_TO_THG_CHL'.
EXPLANATION:
The local and remote queue managers do not agree on the next message sequence
number. A message with sequence number 1 has been sent when sequence number
2013 was expected.
ACTION:
Determine the cause of the inconsistency. It could be that the synchronization
information has become damaged, or has been backed out to a previous version.
If the situation cannot be resolved, the sequence number can be manually reset
at the sending end of the channel using the RESET CHANNEL command.
----- amqrfpta.c : 334 --------------------------------------------------------
02/02/05 13:23:21
AMQ9506: Message receipt confirmation failed.
EXPLANATION:
Channel 'TEST1_TO_THG_CHL' has ended because the remote queue manager did not
accept the last batch of messages.
ACTION:
The error log for the channel at the remote site will contain an explanation of
the failure. Contact the remote Systems Administrator to resolve the problem.
----- amqrmrca.c : 670 --------------------------------------------------------
|
Just happened to have one lying around  |
|
| Back to top |
|
|
|
|
