| Author |
Message
|
| wmbwmq |
 Posted: Thu Jul 23, 2015 6:36 pm Post subject: Receiver channel behavior |
 |
|
Acolyte
Joined: 18 Jul 2011
Posts: 66
|
I needed some help with understanding holiest of holy; the receiver channel behavior
Basically we have a message exit on the receiver channel in our test environment. We have a temporary need to restart the exit at least once a day due to some constraints right now. For that I need to stop/start both sender/receiver. Now this involves getting the MQ guy from the sender side on the call who is usually grumpy and dazed at other times. Also We can't afford to restart the QMGR until we are sure every tester has hit the bar which usually happens only in the evenings.
Is there any workaround the cold start a receiver channel? I mean without impacting the sender/receiver consistency (not having to reset the seqnum , that is)
Thanks,
Pete |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Jul 23, 2015 8:22 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
You could simply issue the STOP CHANNEL command from the RECEIVER side, and subsequently issue the START CHANNEL from the RECEIVER side.
Have you tried it?
_________________
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 |
|
|
| wmbwmq |
| Posted: Fri Jul 24, 2015 4:51 am Post subject: |
|
|
Acolyte
Joined: 18 Jul 2011
Posts: 66
|
| I will try it. But I remember Paul Clarke once mentioning about unpredictability of stopping a receiver channel. I think it has something to do with HBINT that we would have to wait for HBINT+1 minute to be sure receiver is indeed stopped (sorry if I am misquoting him) |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jul 24, 2015 5:37 am Post subject: Re: Receiver channel behavior |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| wmbwmq wrote: |
| Now this involves getting the MQ guy from the sender side on the call who is usually grumpy |
A mainframe guy I bet. Can't live with 'em, can't live without 'em.
But he is probably grumpy because there is no need to bother them for this. Just stop your RCVR. If its acting unpredictably, it may be related to that exit you have on it, because there should be no harm or reason not for you to be able to stop a RCVR channel. Other than Mr.Grumpies complaining why his end of the channel is retrying and his XMITQ is backing up.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| wmbwmq |
| Posted: Fri Jul 24, 2015 6:01 am Post subject: |
|
|
Acolyte
Joined: 18 Jul 2011
Posts: 66
|
Thanks Peter.
We tried stopping the receiver but the sender goes retrying and it appears sender side is seeing the seqnum issue. We did this two more times and the same thing happened. So you are right the exit might be causing this.
Any other workaround to force MQ to reload the exit .so file? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 24, 2015 6:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| wmbwmq wrote: |
Thanks Peter.
We tried stopping the receiver but the sender goes retrying and it appears sender side is seeing the seqnum issue. We did this two more times and the same thing happened. So you are right the exit might be causing this.
Any other workaround to force MQ to reload the exit .so file? |
If you reset the seqnum on the sender side, it resets it on the receiver.
Or you could reset the seqnum on the reciever to whatever the sender expects. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 24, 2015 9:37 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| wmbwmq wrote: |
Thanks Peter.
We tried stopping the receiver but the sender goes retrying |
Working as designed.
| wmbwmq wrote: |
| and it appears sender side is seeing the seqnum issue. |
When exactly do you see the seqnum issue? Once the RCVR end goes into STOPPED state? When you next try to start the RCVR channel? Something else?
| wmbwmq wrote: |
| We did this two more times and the same thing happened. |
You did exactly what two more times?
| wmbwmq wrote: |
So you are right the exit might be causing this.
Any other workaround to force MQ to reload the exit .so file? |
IMS, the exit is loaded/reloaded when the channel next starts.
_________________
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 |
|
|
|
|
