| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSeries Clustering between OS/390 & Sun Solaris |
« View previous topic :: View next topic » |
| Author |
Message
|
| rajesh_avrs |
 Posted: Thu Oct 04, 2001 6:13 pm Post subject: |
 |
|
Apprentice
Joined: 18 May 2001
Posts: 31
|
Hi,
We have two OS/390 systems having MQSeries queue managers. We made a cluster making these two as repositories. Today we were unsuccessfully trying to add a QManager on a Solaris Box to the same cluster. We have defined a cluster sender channel and Cluster receiver channel on Solaris Box.
When we started the cluster sender channel it started fine, we saw the status as 'running'. Surprisingly, the Cluster Receiver channel which is supposed to start automatically didn't start. We tried starting it manually, but it never started. We tried looking at the Error Logs on the Solaris Box and everything looked fine. No error messages. So we tried looking the error log on os/390 side which said "One Repository Command couldn't be processed". We are sure that all the required processes (listeners & channel initiators) on the Solaris side are running.
Anyone has experienced this earlier? Any early suggestions, ideas etc., are greatly appreciated.
_________________
****************
MQSeries is cool
**************** |
|
| Back to top |
|
 |
| bduncan |
| Posted: Fri Oct 05, 2001 11:14 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Rajesh,
a few things:
1. Did you look on the OS/390 to see if it had created a CLUSSDR channel going back to the Solaris box? If so, what is its status? Also, did you check the depth of the SYSTEM.CLUSTER.TRANSMIT.QUEUE? Normally, when a new member of a cluster starts the CLUSSDR channel to the repository, the repository attempts to automatically create a CLUSSDR channel going back (which should start the CLUSRCVR channel you defined on the sun box) and the repository will send some messages via the SYSTEM.CLUSTER.TRANSMIT.QUEUE containing information about the cluster that the new member will need (to create its partial repository, and give it the necessary information to connect to the second full repository).
2. Is the /etc/inetd.conf on the Solaris box set up properly? If it is, you should be able to create a static sender channel on the OS/390 pointing to a static receiver channel on the solaris box. If this is able to start, while the cluster channels are not, then there is probably a problem with the configuration of the cluster objects.
3. Type 'dis clusqmgr(*)' on the solaris box. Do you see all the machines that are in the cluster, just the one repository you connected to, or nothing at all?
With this information we should be able to get a better idea of what your problem is...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
