| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Open one particular CLUSQ got 2085 |
« View previous topic :: View next topic » |
| Author |
Message
|
| bruce2359 |
 Posted: Fri Oct 16, 2009 4:33 am Post subject: |
 |
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Since we've made no other progress, I'd next make both qmgrs FRs. (like chicken-soup, it can't hurt.)
If it's a defective definition in the repos, then the RESET CLUSTER command (with the queues(yes) option) seems like the next approach.
_________________
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 |
|
 |
| Vitor |
| Posted: Fri Oct 16, 2009 4:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| Since we've made no other progress, I'd next make both qmgrs FRs. (like chicken-soup, it can't hurt.) |
Each cluster should have exactly 2 FRs (and let's not start the usual discussion on possible exceptions to this rule!)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Oct 16, 2009 4:49 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I disagree. This is exactly how clusters get really botched up. Let the PMR direct the next course of action. If this is a test system and you don't mind it possibly completely breaking, go for it.
If you can put to one AIX queue from the mainframe, that proves the cluster channels are working. So focus on the the problem queue.
zhanghz, you realize there are TWO places an app can specify QM name? You have verified that the one used for the MQOD is blank and not the mainframe QM? We are not talking about the QM name used for the MQCONN.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Oct 16, 2009 5:16 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| ...really botched up |
I believe zhanghz is already there.
It appears that the repos is in-doubt. So, another simple experiment would be to take the functional and dysfunctional definitions out of the cluster WITH CLUSTER(), then put them back into the cluster - to see if the good one goes bad OR the bad one gets better.
Then the RESET thing.
_________________
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 |
|
|
| zhanghz |
| Posted: Sun Oct 18, 2009 6:02 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
This is a UAT environment. According to AIX, they tried to delete/redefine CLUSQB, but failed to resolve the problem. Only after they define the CLUSQB2 could Mainframe application (and Mainframe CSQ4 sample program) send messages to CLUSQB2 successfuly. Currently user is doing UAT using the CLUSQB2..
I have not gotten the definition of CLUSQB2 from AIX yet.
| PeterPotkay wrote: |
...
zhanghz, you realize there are TWO places an app can specify QM name? You have verified that the one used for the MQOD is blank and not the mainframe QM? We are not talking about the QM name used for the MQCONN. |
This is a CICS program and no MQCONN is needed as CICS handles the connection to MQ already. MQOD-OBJECTQMGRNAME is BLANKS when making MQOPEN call.
Now I don't think it's because of QMNAME as the same programs are used to send messages to CLUSQA, CLUSQB and CLUSQB2.
Anyway, I will wait for the response from support now. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Oct 19, 2009 5:34 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| According to AIX, they tried to delete/redefine CLUSQB, but failed to resolve the problem. |
Not sure what this means.
Did they try, but fail to delete/redefine CLUSQB? Or did they try, and successfully delete/define CLUSQB?
_________________
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 |
|
|
| zhanghz |
| Posted: Mon Oct 19, 2009 7:46 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
| bruce2359 wrote: |
| Quote: |
| According to AIX, they tried to delete/redefine CLUSQB, but failed to resolve the problem. |
Not sure what this means.
Did they try, but fail to delete/redefine CLUSQB? Or did they try, and successfully delete/define CLUSQB? |
sorry, wrong english grammar. "tried deleting/redefining".. they deleted and redefined CLUSQB. But problem still there..
Got support's reply, but the suggestion is only to remove CLUSQB from the cluster, delete the queue, and then redefine it.. For AIX' action. Well, waiting.. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 19, 2009 10:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Also make sure the cluster name / namelist in CLUSQB is defined correctly and matches exactly what is expected (including case). If it is a namelist, has that namelist been defined on the qmgr in question? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zhanghz |
| Posted: Tue Nov 03, 2009 1:15 am Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
just to close this. Support advised AIX to remove CLUSQB from cluster, delete CLUSQB, recreate CLUSQB in cluster. After AIX did that, I still got 2085 when putting messages into CLUSQB from MF; I did a refresh cluster repos(yes), putting messages to CLUSQB was successful!
Accrodingly to AIX, they did the same thing before, and I also remember I did refresh cluster repos(yes) too, but didn't solve the problem then. Don't understand why the same procedure can solve the problem now.
Anyway, I hope I do not get the same problem in production.. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
