| Author |
Message
|
| zhanghz |
 Posted: Wed Oct 14, 2009 12:47 am Post subject: Open one particular CLUSQ got 2085 |
 |
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
Mainframe online program opens a cluster queue for writing messages. The cluster queue is defined on a AIX queue manager. The Maifnrame QMGR and the AIX QMGR form a cluster.
2 cluster queues defined on AIX QMGR, let name them CLUSQA and CLUSQB. Mainframe program can open and put messages to CLUSQA successfully, but open CLUSQB with 2085.
I checked the queue definition on AIX QMGR, CLUSQB is correctly defined with the correct cluster name.
What might be the cause here?
Thanks. |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Oct 14, 2009 12:55 am Post subject: Re: Open one particular CLUSQ got 2085 |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| zhanghz wrote: |
| ...I checked the queue definition on AIX QMGR, CLUSQB is correctly defined with the correct cluster name... |
Are you absolutely sure of that? Look for the queue in one of the FR's, because if it's not listed there, it aint in the cluster.
| zhanghz wrote: |
| ...What might be the cause here? |
Typo in the cluster name - copy and paste from the 'working' queue.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| zhanghz |
| Posted: Wed Oct 14, 2009 1:10 am Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
Yes, I am quite sure CLUSQB is defined correctly. I just compared the definition of the working CLUSQA and the definition of the 2085 CLUSQB, the only difference is with ALTDATE, ALTTIME, CRDATE, CRTIME, DEFBIND, DESCR.
And there is no typo. The program writes the error message to CICS log, I can see the log shows the correct queue name.
puzzled.. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Oct 14, 2009 1:19 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
which one is the FR and which one is PR?
what comes into my mind for a first check:
go to the FR and issue a display for both clusqs, if they are both listed.
if yes, check between application qmgr (assuming this is pr) and fr if all cluster channels are running
if no, check between aix qmgr and fr if all cluster channels are running so that the definition of CLUSQB reaches repository
alter CLUSQB (e.g. the descr) so it gets distributed to the cluster again, and try again.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| dk27 |
| Posted: Wed Oct 14, 2009 1:51 am Post subject: |
|
|
Acolyte
Joined: 28 Apr 2008
Posts: 51
|
| Can you try and do amqsput from some PR other than MF? |
|
| Back to top |
|
|
| zhanghz |
| Posted: Wed Oct 14, 2009 1:52 am Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
sorry, forgot to mention FR and PR. Yes you are correct, Mainframe QMGR is PR, AIX QMGR is FR.
display qc on FR listed all clusq defined on FR.
cluster channels are running.
AIX qmgr already re-defined CLUSQB, but still, Mainframe application encounters 2085. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 14, 2009 4:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| zhanghz wrote: |
sorry, forgot to mention FR and PR. Yes you are correct, Mainframe QMGR is PR, AIX QMGR is FR.
display qc on FR listed all clusq defined on FR.
cluster channels are running.
AIX qmgr already re-defined CLUSQB, but still, Mainframe application encounters 2085. |
Recheck the MF program. Make sure it does the put with an empty/ cleared qmgrname field. This applies to the open of the queue or the put1.
Have fun. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zhanghz |
| Posted: Wed Oct 14, 2009 5:44 am Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
| fjb_saper wrote: |
Recheck the MF program. Make sure it does the put with an empty/ cleared qmgrname field. This applies to the open of the queue or the put1.
Have fun. |
I have checked this. The program is not moving anything to QMgrName..
Also, MF application claimed that SIT and UAT programs are the same, but SIT ok, UAT not ok. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Oct 14, 2009 6:18 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
if you do a display qcluster(*), is clusqb visible or not?
If yes, then the application üprogram is performing a wrong mqopen.
If not, try to mqopen the queue with one of your favorites mq utilities on z/OS. e.g. the Q program or some self written rexx stuff if oyu have ma18 or ma19 utilities, or use one of the mq samples, and check if you get 2085. Also check the chin log for any cluster related messages (as the z/OS repository manager runs within the CHIN address space).
are you sure, the application program is really trying to open clusqb and nothing else? no qmgr name used? did anyone debug that?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| zhanghz |
| Posted: Wed Oct 14, 2009 8:05 am Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
dis qc(*) on MF qmgr does not see CLUSQB.
I went through MF application's program, nothing moved to QMGRNAME. Default is SPACES. And application team says they use the same program to put messages into CLUSQA and CLUSQB.
I do not have a Q program or utilities installed. I used the sample program (CSQ4 somethnig) to put messages, also got 2085.
when application sends to CLUSQB, MSGS of MF qmgr CLUSSDR remains unchanged.
I have tried removing MF qmgr from the cluster and re-joining the cluster, still the same.
I am requesting to open a PMR. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 14, 2009 8:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zhanghz wrote: |
| dis qc(*) on MF qmgr does not see CLUSQB. |
This is clearly the problem.
| zhanghz wrote: |
| I have tried removing MF qmgr from the cluster and re-joining the cluster, still the same. |
This doesn't prove the cluster is working correctly. If (as you intimated in a previous post) the same application works in one environment but gets a 2085 in another, this points to a cluster error in the failing environment.
| zhanghz wrote: |
| I am requesting to open a PMR. |
It's why you pay the license fee. Do please post the resolution when you find it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Oct 14, 2009 11:43 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I'm going to guess that this is one of those lower-case vs. UPPER-CASE vs. MiXeD-cAsE issues.
On z/OS, whenever you type lower-case, the editor folds it to UPPER-CASE. Is the queue name literally all caps?
Is it possible that the app program tried to open a mixed-case qname? Look at the mf application using the ispf editor, but turn caps off. This will leave lower-case as lower-case.
_________________
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: Wed Oct 14, 2009 2:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
On z/OS, whenever you type lower-case, the editor folds it to UPPER-CASE. Is the queue name literally all caps?
|
Oooo.....good thought! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Oct 14, 2009 2:35 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
|
| Back to top |
|
|
| zhanghz |
| Posted: Wed Oct 14, 2009 5:06 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
Yes, I tried CSQ4BVJR job (executing put sample program CSQ4BVK1), got 2085. |
|
| Back to top |
|
|
|
|
