| Author |
Message
|
| prKinch |
 Posted: Wed Feb 03, 2010 3:16 pm Post subject: How to get the msg... |
 |
|
Novice
Joined: 31 Jan 2010
Posts: 15
|
When there is a lost in msg, While sending to one q mgr to another...The sequence number in the both channel will become diff and channel goes to retry status... We need to reset the channel sequencing no. To make a channel active
How to find the message which is lost... |
|
| Back to top |
|
 |
| mvic |
| Posted: Wed Feb 03, 2010 4:04 pm Post subject: Re: How to get the msg... |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| prKinch wrote: |
| We need to reset the channel sequencing no. |
It is unlikely you will ever need to reset a sequence number.
Please give more details for why you concluded you need to reset the channel sequence number.
Also I didn't understand the mention of a lost message. Again if you can share further details, perhaps we can help on that point too. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Feb 03, 2010 4:18 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
One of the most common reasons (my experience) that the sequence wrap fields get out of sequence is that a sysadmin deletes and redefines one end of the channel - either the sender channel or the receiver channel.
Did you redefine one end of the channel? Did someone else do this? Display the channel definition DEF CHL(channel-name) on BOTH ends. Look at the create dates.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Feb 03, 2010 10:58 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
i agree with bruce2359. one indicator for this "redefine" or "recreate" on one end is, that this one end is using sequence number 1.
if the sequence numbers differ, and no end is using "1", then maybe there has been a restore on one end to an older state. the reason could also be that someone fiddled around trying commands, purging stuff, ......
if not, then, yes, maybe, something is missing......
if something is missing, you can not look at it to find out what is missing. so you must talk to your applications and check what the one has send, and what the other has received, then maybe you will find out if there are really messages missing. On z/OS, logfile analysis can help (CSQ1LOGP utility), but you need some knowlege to interpret the output.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Feb 04, 2010 6:46 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Isn't another possibility a mismatched sequence number wrap value? |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Feb 04, 2010 7:02 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
yes, but who will fiddle about with this number ?!? who ever touched it and why? i remember from very early times, that some "exotic" MQ versions did nto support 999999999 but a lower value...... but is this still the case?
however, yes, it could be a reason, and i am sure there are other reasons too not mentioned in this thread so far.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| prKinch |
| Posted: Sun Feb 14, 2010 12:47 pm Post subject: |
|
|
Novice
Joined: 31 Jan 2010
Posts: 15
|
CSQX500I MQI6 CSQXRCTL Channel BWT_MQI6.TO.ISFGIM62T started
CSQX526E MQI6 CSQXRCTL Message sequence error for channel
BWT_MQI6.TO.ISFGIM62T, sent=184183 expected=184182
CSQX506E MQI6 CSQXRCTL Message receipt confirmation not received for
channel BWT_MQI6.TO.ISFGIM62T
This is the error log from mainframe..........
But prevously I got the same error msg for diff. channel..... But (expected=1) ::  :: |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Feb 14, 2010 4:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prKinch wrote: |
| But prevously I got the same error msg for diff. channel..... But (expected=1) :: :: |
This is an almost certain indicator someone's deleted /redefined the other end of the channel.
In the other case you quote, what does the log at the other end of the channel say?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| prKinch |
| Posted: Mon Feb 15, 2010 9:25 am Post subject: |
|
|
Novice
Joined: 31 Jan 2010
Posts: 15
|
| On the other end also, We got some what,same error log.... |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 15, 2010 9:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prKinch wrote: |
| On the other end also, We got some what,same error log.... |
Somewhat the same or exactly the same? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Feb 15, 2010 9:59 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| BWT_MQI6.TO.ISFGIM62T, sent=184183 expected=184182 |
A difference of 1.
What version, release and maintenance of WMQ are you running (both ends, please)?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Feb 15, 2010 7:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
 Intercommunications manual  and check the passage about needing to resolve a channel. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
