ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexGeneral IBM MQ SupportResetting sequence numbers on QSG shared channels

Post new topicReply to topic
Resetting sequence numbers on QSG shared channels View previous topic :: View next topic
Author Message
zpat
PostPosted: Sat Sep 14, 2019 11:14 pm Post subject: Resetting sequence numbers on QSG shared channels Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5687
Location: UK

We have four QMs in a QSG on z/os (currently still MQ 7.1) and connecting to a QM on a distributed platform (Unisys) using a shared sender channel.

The Unisys was moved to another server and the sequence number of the receiver channel defaulted to 1. The sender was trying to send a higher number (like 123456).

I tried stopping, resetting to 1 and starting the sender channel on each of the z/OS QMs using CHLDISP(SHARED) but it just caused the sender channel to flip over to another member of the QSG and go into retry there.

Is there a particular technique needed to reset the sender sequence number on a shared channel in a QSG?

In the end we reset the sequence to the number being sent, on the receiver side and it worked.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
hughson
PostPosted: Mon Sep 16, 2019 11:08 pm Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1277
Location: Bay of Plenty, New Zealand

Was the sender channel INDOUBT(YES)?
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
zpat
PostPosted: Tue Sep 17, 2019 12:33 am Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5687
Location: UK

Dont think so but I did notice that DEFCDISP was set to PRIVATE even though the channel runs as shared. Its a group definition. I assume that DEFCDISP should be set to SHARED?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
hughson
PostPosted: Tue Sep 17, 2019 2:37 am Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1277
Location: Bay of Plenty, New Zealand

Does the channel run shared because you always type CHLDISP(SHARED) on your start command?

DEFCDISP is there in case you forget about the CHLDISP attribute. Yes, it probably should be set to SHARED if this channel is supposed to run as CHLDISP(SHARED), but if you never forget the CHLDISP parameter, it would never be employed.

I would have expected a RESET CHANNEL .... CHLDISP(SHARED) to have worked. You don't mention the exact command you were using - can you confirm?

Remember START CHANNEL ... CHLDISP(SHARED) means, "pick a member of the QSG to run this channel". So when it "flipped over to another member of the QSG" that is what you told it to do.

If you want to run a channel on a specific member of the QSG use START CHANNEL .... CHLDISP(FIXSHARED) to run it (as a CHLDISP(SHARED)) but right here on THIS queue manager.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
zpat
PostPosted: Tue Sep 24, 2019 12:26 pm Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5687
Location: UK

The RESET CHANNEL(xxx) SEQNUM(1) CHLDISP(SHARED) command was accepted but then the channel went into retry again with sequence number error after it was started.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
hughson
PostPosted: Tue Sep 24, 2019 8:19 pm Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1277
Location: Bay of Plenty, New Zealand

zpat wrote:
The RESET CHANNEL(xxx) SEQNUM(1) CHLDISP(SHARED) command was accepted but then the channel went into retry again with sequence number error after it was started.

I would be inclined to report that to IBM Service, because that sounds defective to me. Sounds like other members of the QSG are unable to pick up the sequence number that your command has set, and that is not by design.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
HubertKleinmanns
PostPosted: Wed Sep 25, 2019 1:25 am Post subject: Reply with quote

Shaman

Joined: 24 Feb 2004
Posts: 723
Location: Germany

Did you try to reset the receiving end with
Code:
RESET CHANNEL(xxx) SEQNUM(????)
In the error log / syslog you should find the expected seq no.
_________________
Regards
Hubert
Back to top
View user's profile Send private message Visit poster's website
hughson
PostPosted: Wed Sep 25, 2019 1:51 am Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1277
Location: Bay of Plenty, New Zealand

HubertKleinmanns wrote:
Did you try to reset the receiving end with
Code:
RESET CHANNEL(xxx) SEQNUM(????)
In the error log / syslog you should find the expected seq no.


He did.
zpat wrote:
In the end we reset the sequence to the number being sent, on the receiver side and it worked.

_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
HubertKleinmanns
PostPosted: Wed Sep 25, 2019 3:44 am Post subject: Reply with quote

Shaman

Joined: 24 Feb 2004
Posts: 723
Location: Germany

hughson wrote:
He did.
zpat wrote:
In the end we reset the sequence to the number being sent, on the receiver side and it worked.


I didn't read it - good idea .

But nevertheless RESET on shared channel should also be possible
_________________
Regards
Hubert
Back to top
View user's profile Send private message Visit poster's website
hughson
PostPosted: Wed Sep 25, 2019 7:47 pm Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1277
Location: Bay of Plenty, New Zealand

HubertKleinmanns wrote:
But nevertheless RESET on shared channel should also be possible

Agreed - I have suggested he report it to IBM Service.
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ SupportResetting sequence numbers on QSG shared channels
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.