| Author |
Message
|
| exerk |
 Posted: Mon Dec 28, 2009 2:38 pm Post subject: Re: Auto-defined clus-sdr channel is not coming up |
 |
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| akm.mohan wrote: |
...But here I don't see the channel called TO.QMT2, even by issuing the dis chs(*) or (TO.QMT2).
If I define manually, it works fine...
Please help me to find out why its not coming up automatically or in other way..why auto definition is not working in this senario.
(clusterqueue defbind is set to notfixed)
Thanks in advance. |
1. Are you sure that you have correctly altered each FR to define each as an FR?
2. Have you correctly defined the required CLUSSDR/CLUSRCVR objects in each of the FR's?
3. Were both FR's cluster channels running correctly before you proceeded further?
4. Have you defined cluster instances of the same queue in each of the FR queue managers?
5. Are both cluster queue instances set to DEFBIND(NOTFIXED) ?
As a rule of thumb, never proceed past #3 until both FR's are 'talking' to each other properly - if you have to manually define a CLUSSDR to the other FR, I'd say your cluster isn't working properly, so scrap it and start again.
_________________
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 |
|
 |
| zonko |
| Posted: Mon Dec 28, 2009 11:27 pm Post subject: |
|
|
Voyager
Joined: 04 Nov 2009
Posts: 78
|
| Quote: |
Please help me to find out why its not coming up automatically or in other way..why auto definition is not working in this senario.
|
When a PR joins a cluster, it creates an auto CLUSSDR to the full repos qmgr that it is not connected to by a manual CLUSSDR.
This will not happen if:
EITHER
you have not defined it properly
OR
full connectivity has not been established |
|
| Back to top |
|
|
| akm.mohan |
| Posted: Tue Dec 29, 2009 6:50 am Post subject: Auto-defined clus-sdr channel is not coming up |
|
|
Apprentice
Joined: 07 Oct 2008
Posts: 41
|
Thanks fexerk and zonko for your imm reply.
So Yes for all of your questions becaz they were communicating each other sice long time(years). But something was messed up to caz this issue.
Since some one has created the cluster, to be clear I am giving you the channel names and types here. Please have a look and tell me if we missed something in that..
QMGR: QMGR1(PR)
dis chs(TO.*)
2 : dis chs(TO.*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.QMGR1) CHLTYPE(CLUSRCVR)
CONNAME(180.12.19.120) CURRENT
RQMNAME(MQT1) STATUS(RUNNING)
SUBSTATE(RECEIVE) XMITQ( )
AMQ8417: Display Channel Status details.
CHANNEL(TO.QMGR1) CHLTYPE(CLUSRCVR)
CONNAME(129.16.14.170) CURRENT
RQMNAME(MQT2) STATUS(RUNNING)
SUBSTATE(RECEIVE) XMITQ( )
QMGR: MQT1
cluster qmgr name : MQGR1
channel name: TO.QMGR1
Disposition: MQT1
channel type: CLUSSDRA
cluster qmgr name : QMT1
channel name: TO.QMT1
Disposition: MQT1
channel type: CLUSRCVR
cluster qmgr name : MQT2
channel name: TO.QMT2
Disposition: MQT1
channel type: CLUSSDR
QMGR: QMT2
cluster qmgr name : QMGR1
channel name: TO.QMGR1
Disposition: MQT2
channel type: CLUSSDRA
cluster qmgr name : QMT1
channel name: TO.QMT1
Disposition: MQT2
channel type: CLUSSDRB
cluster qmgr name : QMT2
channel name: TO.QMT2
Disposition: MQT2
channel type: CLUSRCVR
Thanks,
Krishna |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Dec 29, 2009 7:55 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Please post the channel definitions rather than their status as that will give us more information, especially as things like:
| Quote: |
QMGR: MQT1
cluster qmgr name : MQGR1
channel name: TO.QMGR1
Disposition: MQT1
channel type: CLUSSDRA
cluster qmgr name : QMT1
channel name: TO.QMT1
Disposition: MQT1
channel type: CLUSRCVR
cluster qmgr name : MQT2
channel name: TO.QMT2
Disposition: MQT1
channel type: CLUSSDR
QMGR: QMT2
cluster qmgr name : QMGR1
channel name: TO.QMGR1
Disposition: MQT2
channel type: CLUSSDRA
cluster qmgr name : QMT1
channel name: TO.QMT1
Disposition: MQT2
channel type: CLUSSDRB
cluster qmgr name : QMT2
channel name: TO.QMT2
Disposition: MQT2
channel type: CLUSRCVR |
caught my eye...unless they're typo's of course?
_________________
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 |
|
|
| akm.mohan |
| Posted: Tue Dec 29, 2009 8:09 am Post subject: |
|
|
Apprentice
Joined: 07 Oct 2008
Posts: 41
|
They are not typo ..
from unix server: QMGR1
dis chl(TO.*)
6 : dis chl(TO.*)
AMQ8414: Display Channel details.
CHANNEL(TO.MQT1) CHLTYPE(CLUSSDR)
AMQ8414: Display Channel details.
CHANNEL(TO.MQT2) CHLTYPE(CLUSSDR)
AMQ8414: Display Channel details.
CHANNEL(TO.QMGR1) CHLTYPE(CLUSRCVR)
From MainFrames: I mentioned in my last reply. Those are not status of channels.. those are definitions only...not typo ..here MQT1 and MQT2 are FRs.. or To be clear to us, Please use these qmgrs and tell me which chanenls do I need to create in which qmgrs...So As per your channels list I can check here, whether they were created properly or not.
Thanks,
Krishna. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Dec 29, 2009 9:38 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| From MainFrames: I mentioned in my last reply. Those are not status of channels.. |
Did you do a tcp ping from sender end to receiver end? Was it successful?
Did you perform an MQ PING from a non-started Sender channel to validate the definitions on both ends? Was it successful?
Is the mainframe end brand new? Is the qmgr on the m/f brand new? Is their CHIN address space started? Any error messages on the m/f syslog in the CHIN address space?
_________________
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 |
|
|
| mvic |
| Posted: Tue Dec 29, 2009 9:53 am Post subject: Re: Auto-defined clus-sdr channel is not coming up |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| akm.mohan wrote: |
| Whenever I put the messages by issuing the amqsreq script from QMGR1, I can see the response time from only QMT1 not from QMT2. |
Please tell me why you expected different results from this. |
|
| Back to top |
|
|
| akm.mohan |
| Posted: Tue Dec 29, 2009 10:57 am Post subject: Auto-defined clus-sdr channel is not coming up |
|
|
Apprentice
Joined: 07 Oct 2008
Posts: 41
|
Is the mainframe end brand new? Is the qmgr on the m/f brand new?
MainFrame QMGr is not a brand new qmgr...
Please tell me why you expected different results from this.
becaz these three are in one cluster they can access the cluster queue from any queue manager. QMGR1 to QMT1 , all the channels are up and running fine so all the transactions are going to MQT1. But here if we would like to send the messages to MQT2, its failing becaz of that cluster snder channel is not defining automatically MQT2 is also FR.
PING is not successful: |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Dec 29, 2009 11:05 am Post subject: Re: Auto-defined clus-sdr channel is not coming up |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| akm.mohan wrote: |
| ...PING is not successful: |
Then there is something wrong in the cluster. As requested earlier, please post the channel definitions of all three queue managers.
_________________
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 |
|
|
| akm.mohan |
| Posted: Tue Dec 29, 2009 12:16 pm Post subject: |
|
|
Apprentice
Joined: 07 Oct 2008
Posts: 41
|
here are the channel definitions:
QMGR1:
dis chl(TO.MQT1)
5 : dis chl(TO.MQT1)
AMQ8414: Display Channel details.
CHANNEL(TO.MQT1) CHLTYPE(CLUSSDR)
ALTDATE(2009-12-24) ALTTIME(14.26.50)
BATCHHB(0) BATCHINT(0)
BATCHSZ(50) CLUSNL( )
CLUSTER(AUTOCLUS) CLWLPRTY(0)
CLWLRANK(0) CLWLWGHT(50)
COMPHDR(NONE) COMPMSG(NONE)
CONNAME(110.10.15.140(1415)) CONVERT(NO)
DESCR( ) DISCINT(0)
HBINT(300) KAINT(AUTO)
LOCLADDR( ) LONGRTY(999999999)
LONGTMR(600) MAXMSGL(4194304)
MCANAME( ) MCATYPE(THREAD)
MCAUSER( ) MODENAME( )
MONCHL(QMGR) MSGDATA( )
MSGEXIT( ) NPMSPEED(FAST)
PASSWORD( ) RCVDATA( )
RCVEXIT( ) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SEQWRAP(999999999)
SHORTRTY(10) SHORTTMR(60)
SSLCIPH( ) SSLPEER( )
STATCHL(QMGR) TPNAME( )
TRPTYPE(TCP) USERID( )
dis chl(TO.QMGR1)
6 : dis chl(TO. QMGR1)
AMQ8414: Display Channel details.
CHANNEL(TO. QMGR1) CHLTYPE(CLUSRCVR)
ALTDATE(2008-12-24) ALTTIME(14.26.50)
BATCHHB(0) BATCHINT(0)
BATCHSZ(50) CLUSNL( )
CLUSTER(AUTOCLUS) CLWLPRTY(0)
CLWLRANK(0) CLWLWGHT(50)
COMPHDR(NONE) COMPMSG(NONE)
CONNAME(180.12.19.120) CONVERT(NO)
DESCR( ) DISCINT(0)
HBINT(300) KAINT(AUTO)
LOCLADDR( ) LONGRTY(999999999)
LONGTMR(1200) MAXMSGL(4194304)
MCANAME( ) MCATYPE(THREAD)
MCAUSER( ) MODENAME( )
MONCHL(QMGR) MRDATA( )
MREXIT( ) MRRTY(10)
MRTMR(1000) MSGDATA( )
MSGEXIT( ) NETPRTY(0)
NPMSPEED(FAST) PUTAUT(DEF)
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SEQWRAP(999999999) SHORTRTY(10)
SHORTTMR(60) SSLCAUTH(REQUIRED)
SSLCIPH( ) SSLPEER( )
STATCHL(QMGR) TPNAME( )
TRPTYPE(TCP)
dis chs(TO.QMGR1)
7 : dis chs(TO.QMGR1)
AMQ8417: Display Channel Status details.
CHANNEL(TO.QMGR1) CHLTYPE(CLUSRCVR)
CONNAME(180.12.19.120) CURRENT
RQMNAME(MQT1) STATUS(RUNNING)
SUBSTATE(RECEIVE) XMITQ( )
AMQ8417: Display Channel Status details.
CHANNEL(TO.QMGR1) CHLTYPE(CLUSRCVR)
CONNAME(180.12.19.120) CURRENT
RQMNAME(MQT2) STATUS(RUNNING)
SUBSTATE(RECEIVE) XMITQ( )
QMT1:
Cluster qmgr name: QMGR1
Channel name: TO.QMGR1
Disposition: MQT1
Channel definition type: CLUSSDRA
Cluster name: AUTOCLUS
Queue manager identifier: QMGR1_2008-12-12
Repository management: N
Suspended: Y
Cluster workload rank 0
Cluster workload priority 0
Cluster workload weight 50
Cluster time 2008-12-24 14.29.11
Transport type T
Connection name: 180.12.19.120
Status: RUN
Network priority 0
MCA type THREAD
Cluster qmgr name: QMT1
Channel name: TO.QMT1
Disposition: QMT1
Channel definition type: CLUSRCVR
Cluster name: AUTOCLUS
Queue manager identifier: QMT1_2008-12-12
Repository management: Y
Suspended: N
Cluster workload rank 0
Cluster workload priority 0
Cluster workload weight 50
Cluster time 2008-12-24 14.29.11
Transport type T
Connection name: 110.10.15.140
Status: RUN
Network priority 0
MCA type THREAD
Cluster qmgr name: QMT2
Channel name: TO.QMT2
Disposition: QMT1
Channel definition type: CLUSSDRB
Cluster name: AUTOCLUS
Queue manager identifier: QMT2_2008-12-12
Repository management: Y
Suspended: N
Cluster workload rank 0
Cluster workload priority 0
Cluster workload weight 50
Cluster time 2008-12-24 14.29.11
Transport type T
Connection name: 129.16.14.170
Status: RUN
Network priority 0
MCA type THREAD
Cluster qmgr name: QMGR1
Channel name: TO.QMGR1
Disposition: QMT2
Channel definition type: CLUSSDRA
Cluster name: AUTOCLUS
Queue manager identifier: QMGR1_2008-12-12
Repository management: N
Suspended: Y
Cluster workload rank 0
Cluster workload priority 0
Cluster workload weight 50
Cluster time 2008-12-24 14.29.11
Transport type T
Connection name: 180.12.19.120
Status: RUN
Network priority 0
MCA type THREAD
Cluster qmgr name: QMT1
Channel name: TO.QMT1
Disposition: QMT2
Channel definition type: CLUSDRB
Cluster name: AUTOCLUS
Queue manager identifier: QMT1_2008-12-12
Repository management: Y
Suspended: N
Cluster workload rank 0
Cluster workload priority 0
Cluster workload weight 50
Cluster time 2008-12-24 14.29.11
Transport type T
Connection name: 110.10.15.140
Status: INACT
Network priority 0
MCA type THREAD
Cluster qmgr name: QMT2
Channel name: TO.QMT2
Disposition: QMT2
Channel definition type: CLUSRCVR
Cluster name: AUTOCLUS
Queue manager identifier: QMT2_2008-12-12
Repository management: Y
Suspended: N
Cluster workload rank 0
Cluster workload priority 0
Cluster workload weight 50
Cluster time 2008-12-24 14.29.11
Transport type T
Connection name: 129.16.14.170
Status: RUN
Network priority 0
MCA type THREAD |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Dec 29, 2009 12:55 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
QMT1:
Cluster qmgr name: QMGR1
Channel name: TO.QMGR1
Disposition: MQT1
Channel definition type: CLUSSDRA
Cluster name: AUTOCLUS
Queue manager identifier: QMGR1_2008-12-12
Repository management: N
Suspended: Y |
_________________
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 |
|
|
| mvic |
| Posted: Tue Dec 29, 2009 12:59 pm Post subject: Re: Auto-defined clus-sdr channel is not coming up |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| There seems to be a problem wth typos here. QMGR1 thinks its full repository is contacted via channel TO.MQT1. Nowhere else in your dumps is there a definition of a CLUSRCVR named TO.MQT1. |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Dec 29, 2009 1:09 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| bruce2359 wrote: |
Repository management: N
Suspended: Y |
A good spot bruce2359, but I think we are looking at something even more odd here. A qmgr that is suspended can introduce messages to the cluster; not aware that that is a problem.
However, these defs do not show a proper cluster: QMGR1 thinks its full repository is contacted via channel TO.MQT1. What you highlight here is what QMT1 (CLUSRCVR name TO.QMT1) thinks about QMGR1. I would almost say it's irrelevant what TO.QMT1 thinks of QMGR1, but am not quite confident enough to do so.
I don't think we know enough of the application scenario either... what qmgr is the putting app on, and where in the cluster are the queues of that name.
akm.mohan, have you checked the error logs on all systems for a historical view of what might have happened? Also you mentioned someone changed things - are they available to explain what change they made? |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Dec 29, 2009 1:16 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Have things changed in the z world? General question because I didn't think that z/OS QMID's look like QMGR1_2008-12-12...
I still think akm.mohan should scrap the cluster (if possible) and start from scratch, after all it's only three queue managers and the practice is always useful 
_________________
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 |
|
|
| bruce2359 |
| Posted: Tue Dec 29, 2009 1:39 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Yep.
QMID is an internally generated unique name that consists of the queue manager name plus the time the queue manager was created.
For z/OS, the time is expressed as 16 hex digits, for example
RTPH.BDA2D50C17934846.
_________________
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 |
|
|
|
|
