| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Not able to add z/OS queue manager to cluster |
« View previous topic :: View next topic » |
| Author |
Message
|
| hughson |
 Posted: Sat May 31, 2014 12:56 pm Post subject: |
 |
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| Prithviraj wrote: |
| Before concluding, do anyone have any other suggestions regarding my problem..? |
Please look in the CHINIT log of your z/OS queue manager and show us the error messages that are there reporting your issue.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sat May 31, 2014 8:04 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
WMQ on z/OS is very, very different from WMQ on Windows/UNIX. If you do not have z/OS skills, you need the assistance of a z/OS-skilled person.
_________________
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 |
|
|
| Prithviraj |
| Posted: Mon Jun 02, 2014 4:17 am Post subject: |
|
|
Apprentice
Joined: 29 May 2014
Posts: 30
|
Hi all,
As you have advised I have gone through the message log and here is the o/p:
+CSQX410I +MR11 CSQXREPO Repository manager started
+CSQX015I +MR11 CSQXSPRI 5 dispatchers started, 0 failed
+CSQX036E +MR11 CSQXSUPR Unable to open SYSTEM.BROKER.DEFAULT.STREAM, 765
MQCC=2 MQRC=2531
+CSQT816E +MR11 CSQXFCTL Unable to open Queued Pub/Sub control queue 852
MQCC=2 MQRC=2085
+CSQT855E +MR11 CSQXFCTL Queued Pub/Sub Daemon failed, reason=00005816
+CSQX037E +MR11 CSQXREPO Unable to get message from 894
SYSTEM.CLUSTER.COMMAND.QUEUE, MQCC=2 MQRC=2016
+CSQX448E +MR11 CSQXREPO Repository manager stopping because of 895
errors. Restart in 600 seconds
+CSQX022I +MR11 CSQXSUPR Channel initiator initialization complete
+CSQX500I +MR11 CSQXRCTL Channel TO.CLUSTER2 started
+CSQX004I +MR11 CSQXSPRM Channel initiator is using 31 MB of local 898
storage, 1803 MB are free
+CSQX251I +MR11 CSQXSTRL Listener started, TRPTYPE=TCP INDIS INDISP=QMGR
+CSQX023I +MR11 CSQXLSTT Listener started, 900
port 1400 address *,
port 1400 address *,
TRPTYPE=TCP INDISP=QMGR
+ CSQU012I CSQUTIL Initialization command handling completed
+CSQX202E +MR11 CSQXRCTL Connection or remote listener unavailable, 989
channel TO.CLUSTER2,
connection (172.16.109.201)
TRPTYPE=TCP RC=00000467 (ETIMEDOUT) reason=00000000
+CSQX501I +MR11 CSQXRCTL Channel TO.CLUSTER2 is no longer active
+CSQX449I +MR11 CSQXREPO Repository manager restarted
+CSQX037E +MR11 CSQXREPO Unable to get message from 398
SYSTEM.CLUSTER.COMMAND.QUEUE, MQCC=2 MQRC=2016
+CSQX448E +MR11 CSQXREPO Repository manager stopping because of400
errors. Restart in 600 seconds
+CSQX534E +MR11 CSQXRESP Channel TO.MR1ads is stopped
+CSQX599E +MR11 CSQXRESP Channel TO.MR1ads ended abnormally
+CSQX534E +MR11 CSQXRESP Channel TO.MR11CH is stopped
+CSQX599E +MR11 CSQXRESP Channel TO.MR11CH ended abnormally
+CSQX449I +MR11 CSQXREPO Repository manager restarted
+CSQX449I +MR11 CSQXREPO Repository manager restarted
+CSQX037E +MR11 CSQXREPO Unable to get message from 398
SYSTEM.CLUSTER.COMMAND.QUEUE, MQCC=2 MQRC=2016
+CSQX448E +MR11 CSQXREPO Repository manager stopping because of 400
errors. Restart in 600 seconds
+CSQX534E +MR11 CSQXRESP Channel TO.MR1ads is stopped
+CSQX599E +MR11 CSQXRESP Channel TO.MR1ads ended abnormally
+CSQX534E +MR11 CSQXRESP Channel TO.MR11CH is stopped
+CSQX599E +MR11 CSQXRESP Channel TO.MR11CH ended abnormally
+CSQX449I +MR11 CSQXREPO Repository manager restarted
+CSQX037E +MR11 CSQXREPO Unable to get message from 686
SYSTEM.CLUSTER.COMMAND.QUEUE, MQCC=2 MQRC=2016
+CSQX448E +MR11 CSQXREPO Repository manager stopping because of 687
errors. Restart in 600 seconds
+CSQX500I +MR11 CSQXRCTL Channel TO.CLUSTER2 started
+CSQX202E +MR11 CSQXRCTL Connection or remote listener unavailable, 713
channel TO.CLUSTER2,
connection (172.16.109.201)
connection (172.16.109.201)
TRPTYPE=TCP RC=00000467 (ETIMEDOUT) reason=00000000
+CSQX501I +MR11 CSQXRCTL Channel TO.CLUSTER2 is no longer active
The interesting thin is that all those channels,mentioned here, were deleted earlier and ip 172.16.109.201 is not present now.
Please tell me what to do or do I need to provide any further information ? |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Jun 02, 2014 4:24 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
you should make SYSTEM.CLUSTER.COMMAND.QUEUE get-enabled.
hopefully you did not screw your cluster up already with trying a lot of stuff.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| hughson |
| Posted: Mon Jun 02, 2014 4:43 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| Prithviraj wrote: |
+CSQX410I +MR11 CSQXREPO Repository manager started
+CSQX037E +MR11 CSQXREPO Unable to get message from
SYSTEM.CLUSTER.COMMAND.QUEUE, MQCC=2 MQRC=2016
+CSQX448E +MR11 CSQXREPO Repository manager stopping because of
errors. Restart in 600 seconds
+CSQX449I +MR11 CSQXREPO Repository manager restarted
+CSQX037E +MR11 CSQXREPO Unable to get message from
SYSTEM.CLUSTER.COMMAND.QUEUE, MQCC=2 MQRC=2016
+CSQX448E +MR11 CSQXREPO Repository manager stopping because of
errors. Restart in 600 seconds |
These messages tell you that the repository task is not running. Your cluster will not work while this is the case. The reason for the repository task stopping originally will be in an older CHINIT log. You should get your Sysadmin to review them to find the original reason. You could reenable the SYSTEM.CLUSTER.COMMAND.QUEUE again, but if the original reason is not fixed it will continue not to work.
| Prithviraj wrote: |
+CSQX500I +MR11 CSQXRCTL Channel TO.CLUSTER2 started
+CSQX202E +MR11 CSQXRCTL Connection or remote listener unavailable, 989
channel TO.CLUSTER2,
connection (172.16.109.201)
TRPTYPE=TCP RC=00000467 (ETIMEDOUT) reason=00000000
+CSQX501I +MR11 CSQXRCTL Channel TO.CLUSTER2 is no longer active
+CSQX534E +MR11 CSQXRESP Channel TO.MR1ads is stopped
+CSQX599E +MR11 CSQXRESP Channel TO.MR1ads ended abnormally
+CSQX534E +MR11 CSQXRESP Channel TO.MR11CH is stopped
+CSQX599E +MR11 CSQXRESP Channel TO.MR11CH ended abnormally
+CSQX534E +MR11 CSQXRESP Channel TO.MR1ads is stopped
+CSQX599E +MR11 CSQXRESP Channel TO.MR1ads ended abnormally
+CSQX534E +MR11 CSQXRESP Channel TO.MR11CH is stopped
+CSQX599E +MR11 CSQXRESP Channel TO.MR11CH ended abnormally
+CSQX500I +MR11 CSQXRCTL Channel TO.CLUSTER2 started
+CSQX202E +MR11 CSQXRCTL Connection or remote listener unavailable, 713
channel TO.CLUSTER2,
connection (172.16.109.201)
connection (172.16.109.201)
TRPTYPE=TCP RC=00000467 (ETIMEDOUT) reason=00000000
+CSQX501I +MR11 CSQXRCTL Channel TO.CLUSTER2 is no longer active |
Nowhere in the messages showing channels starting/stopping do I see the channel you mentioned in your first post? If these are old channels that you deleted already, I guess they weren't deleted following the instructions in the clustering manual for correct deletion? Often the way on test queue managers unfortunately!
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| Prithviraj |
| Posted: Tue Jun 03, 2014 2:19 am Post subject: |
|
|
Apprentice
Joined: 29 May 2014
Posts: 30
|
Dear all,
Please find my analysis,
1) Are channels able to run in both direction ?
In windows full repository
dis chstatus(*)
9 : dis chstatus(*)
AMQ8417: Display Channel Status details.
CHANNEL(WINDZOS.SECOND) CHLTYPE(CLUSSDR)
CONNAME(172.16.109.223(1501)) CURRENT
RQMNAME(SECOND) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
AMQ8417: Display Channel Status details.
CHANNEL(WINDZOS.FIRST) CHLTYPE(CLUSRCVR)
CONNAME(172.16.109.223) CURRENT
RQMNAME(SECOND) STATUS(RUNNING)
SUBSTATE(RECEIVE)
AMQ8417: Display Channel Status details.
CHANNEL(WINDZOS.FIRST) CHLTYPE(CLUSRCVR)
CONNAME(172.16.111.222) CURRENT
RQMNAME(MR11) STATUS(RUNNING)
SUBSTATE(RECEIVE)
In z/OS partial repository
MQM Command ===> DISPLAY CHSTATUS(WINDZOS.*)
-------------- Command Results: RETURN=00000000, REASON=00000000 -------------
CSQM428I +MR11 CHSTATUS(WINDZOS.FIRST ) CHLDISP(PRIVATE ) XMITQ(SYSTEM.
CLUSTER.TRANSMIT.QUEUE ) CONNAME(172.16.109.223
) CURRENT CHLTYPE(CLUSSDR ) STATUS(RUNNING ) SUBSTATE(M
QGET ) STOPREQ(NO ) RQMNAME(FIRST
)
-------------------------------------------------------------------------------
My z/OS cluster-receiver channel is always INACTIVE. As it is partial repository cluster-receiver its corresponding sender channels will be automatically created when needed.
In windows full repository
display clusqmgr(*)
10 : display clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FIRST) CHANNEL(WINDZOS.FIRST)
CLUSTER(WINDZOS)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(SECOND) CHANNEL(WINDZOS.SECOND)
CLUSTER(WINDZOS)
z/OS partial repository is not shown in cluster details .
2) Are the SYSTEM.CLUSTER.* queues enabled?
In z/OS
SYSTEM.CLUSTER.REPOSITORY.QUEUE :
get and put enabled, current depth not 0 and trigtype = none
SYSTEM.CLUSTER.COMMAND.QUEUE:
put enabled and get disabled, current depth not 0 and trigtype = none
SYSTEM.CLUSTER.TRANSMIT.QUEUE
get and put enabled, current depth not 0 and trigtype = first
I think this current depths of these queues might be my issue.
3)Are there are duplicate QMID for queue managers?
No, no queue managers have duplicate QMID.
4)Is the repository queue manager still running ?
CHIN message logs
+CSQX036E +MR11 CSQXSUPR Unable to open SYSTEM.BROKER.DEFAULT.STREAM, 570
MQCC=2 MQRC=2531
+CSQT816E +MR11 CSQXFCTL Unable to open Queued Pub/Sub control queue 573
MQCC=2 MQRC=2085
+CSQT855E +MR11 CSQXFCTL Queued Pub/Sub Daemon failed, reason=00005816
+CSQX037E +MR11 CSQXREPO Unable to get message from 584
SYSTEM.CLUSTER.COMMAND.QUEUE, MQCC=2 MQRC=2016
+CSQX448E +MR11 CSQXREPO Repository manager stopping because of 585
errors. Restart in 600 seconds
This is the present scenario, now please tell me
1)How to clear SYSTEM.CLUSTER.* queues?
As they are system queues, I think it is not possible to clear those.
But if there is a way please share.
2)My CHIN message logs are showing details about channels that really do not
presently exists, all those channels were deleted ones.
It will take 90 days for complete removal of those but still is there any way to forcefully delete them ?
3)Is it because my z/OS cache is full? If yes, how to know it?
4)Is there a way to delete everything from a z/OS queue manager except default objects?
Please help me solving my issue, I badly need this cluster to work |
|
| Back to top |
|
|
| hughson |
| Posted: Tue Jun 03, 2014 4:24 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| Prithviraj wrote: |
2) Are the SYSTEM.CLUSTER.* queues enabled?
In z/OS
SYSTEM.CLUSTER.COMMAND.QUEUE:
put enabled and get disabled, current depth not 0
I think this current depths of these queues might be my issue.
4)Is the repository manager still running ?
CHIN message logs
+CSQX037E +MR11 CSQXREPO Unable to get message from SYSTEM.CLUSTER.COMMAND.QUEUE, MQCC=2 MQRC=2016
+CSQX448E +MR11 CSQXREPO Repository manager stopping because of
errors. Restart in 600 seconds |
As already noted, the repository manager (task) is clearly not running. Those error messages tell you that. Also the fact that the SYSTEM.CLUSTER.COMMAND.QUEUE is GET(DISABLED) tells you that nothing is reading from it.
| Prithviraj wrote: |
| 3)Is it because my z/OS cache is full? If yes, how to know it? |
I doubt your cache is full given that this is a test system and I don't believe you'll have made so many object definitions to fill it up. In order to answer why the repository manager (task) is not running you will have to look back through previous CHINIT logs to see the original error that set your repository task in this retry pattern. Or alternatively you could renable the SYSTEM.CLUSTER.COMMAND.QUEUE for GET and see if it reports the same error again (because the message causing said error is still at the front of the queue).
| Prithviraj wrote: |
1)How to clear SYSTEM.CLUSTER.* queues?
As they are system queues, I think it is not possible to clear those.
But if there is a way please share. |
You can clear queues on z/OS in the same way as you clear queues on distributed. Clearing SYSTEM.CLUSTER queues will mess up your cluster, but if you want to start clean all over again on a test system, you may consider it an appropriate step to take. You should REFRESH the cluster on your z/OS queue manager after throwing away all its knowledge of the cluster though or it is never going to reconnect again.
| Prithviraj wrote: |
| 4)Is there a way to delete everything from a z/OS queue manager except default objects? |
You can cold start a z/OS queue manager by wiping the logs and page sets back to clean again. This will also throw away the default objects, but since they are defined by CSQINP2 samples, then they can be redefined when the cold started queue manager starts up again. Is this z/OS queue manager only used by you? Did someone else set it up for you? Perhaps easier to ask them to clean it for you?
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| Prithviraj |
| Posted: Tue Jun 03, 2014 10:26 pm Post subject: |
|
|
Apprentice
Joined: 29 May 2014
Posts: 30
|
Dear all,
I enabled SYSTEM.CLUSTER.COMMAND.QUEUE and now my clustering is working fine.
I thank hughson, for helping me in figuring out error in clustering and helping me to solve it. I am very thankful to you,hughson.
Now, to all others, I told you all, a hundred times, that I had gone through clustering manuals many times and I am sure that there is no error in my channel definition.
You people, never read my channel definition or my post and anticipated that my channel definitions are wrong and started blaming me for not reading manuals.
I request you to read questions properly before replying to posts...else it will be a waste of everyone time reading those crap and is waste of server space....
Anyways thanks for your replies and I expect your help in future..  |
|
| Back to top |
|
|
| hughson |
| Posted: Wed Jun 04, 2014 1:44 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| Prithviraj wrote: |
Now, to all others, I told you all, a hundred times, that I had gone through clustering manuals many times and I am sure that there is no error in my channel definition.
You people, never read my channel definition or my post and anticipated that my channel definitions are wrong and started blaming me for not reading manuals.
I request you to read questions properly before replying to posts...else it will be a waste of everyone time reading those crap and is waste of server space.... |
Dear Prithviraj,
I don't think this manner of thanking the forum for spending their time for free on your problem is likely to endear you to them for any future questions you may like to expect their help on. Channel definitions are the most common misconfiguration for this type of problem, and even with the detail you provided they cannot tell whether you put in the correct IP address, for example. Only once you provided the requested error messages could any one do more than guess at your problem. Please be more considerate of the experts you wish help from and treat them with more respect. There is a wealth of knowledge and information on this forum and you want to be able to call on it in the future.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 04, 2014 4:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hughson wrote: |
| I don't think this manner of thanking the forum for spending their time for free on your problem is likely to endear you to them for any future questions you may like to expect their help on. |
I also think the use of terms like that on the forum are likely to get future posts moderated. All opinions here are welcome but this is a technical forum for professionals, and posts are expected to reflect that.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Prithviraj |
| Posted: Tue Jun 10, 2014 12:43 am Post subject: |
|
|
Apprentice
Joined: 29 May 2014
Posts: 30
|
Dear hughson,
Sorry for that kind of reply. I won't reply like that .
Thanks everyone for helping me.  |
|
| Back to top |
|
|
| hughson |
| Posted: Tue Jun 10, 2014 6:07 am Post subject: Related Technote |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jun 10, 2014 9:46 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
Prithviraj.
May I suggest that before your next post, please spend a few minutes reading http://www.mqseries.net/phpBB2/viewforum.php?f=37 Read First for All New to WebSphere - Only Moderators Post Here
How To Answer Questions The Helpful Way
How To Ask Questions The Smart Way
Posting guidelines
Common Errors Link
_________________
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 |
|
|
|
|
|
|
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
|
|
|
|
