ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » MQ Explorer with Tandem MQ

Post new topic  Reply to topic
 MQ Explorer with Tandem MQ « View previous topic :: View next topic » 
Author Message
AndyMQ
PostPosted: Wed Feb 01, 2006 7:19 am    Post subject: MQ Explorer with Tandem MQ Reply with quote

Apprentice

Joined: 22 Apr 2004
Posts: 33
Location: Scotland

Does anyone use MQ Explorer to access MQ on a Tandem? Specifically, we use 5.3 MQ Explorer on Windows and have recently applied CSD03 EFIX1 on our 5.1 MQ and it's stopped working properly.
Tandem queue managers have been stopped and started only. We didn't do a dltmqm and crtmqm as part of the upgrade.
MQ Explorer is connecting via the svrconn channel as principal mqm and we can display the channels. When we try to display the queues it fails with a timeout.
The system.admin.command queue hasn't changed.
We also access MQ 5.3 on Unix and that part still works a treat.
Nothing appears in EMS and there are no FFSTs produced. Anyone got any ideas? A bit baffled by it all. IBM are on the case, but thought I'd run in past the gurus on this site too.
Any help greatly appreciated.
Back to top
View user's profile Send private message
mvic
PostPosted: Wed Feb 01, 2006 7:50 am    Post subject: Re: MQ Explorer with Tandem MQ Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

AndyMQ wrote:
Specifically, we use 5.3 MQ Explorer on Windows and have recently applied CSD03 EFIX1 on our 5.1 MQ and it's stopped working properly.

If application of a CSD broke something, you should raise a PMR. Are you sure it was the CSD that broke this? (Was there anything else that was done administratively to MQ?)
Back to top
View user's profile Send private message
AndyMQ
PostPosted: Wed Feb 01, 2006 8:00 am    Post subject: Reply with quote

Apprentice

Joined: 22 Apr 2004
Posts: 33
Location: Scotland

Have raised a PMR.
We were running with CSD02 with version 5.1 and all we did was run the CSD03 upgrade + the C3EFIX1. No other changes took place, which was what baffled us.
Initial suggestion from IBM is to increase a timeout parameter for MQ Explorer in the registry. That kinda makes sense to a degree as we have over 300 queues in one queue manager. However, the other queue manager only has around 100.
Currently waiting for our desktop team to do the registry update. To be continued...
Back to top
View user's profile Send private message
hankknowles
PostPosted: Thu Feb 02, 2006 7:11 am    Post subject: Reply with quote

Centurion

Joined: 18 Aug 2003
Posts: 114

I would think that maybe there is higher efix available we are @ csd03 and the efix is c3efix3.

I use MQJexplorer myself on my PC much less troublesome!
Back to top
View user's profile Send private message
AndyMQ
PostPosted: Thu Feb 02, 2006 7:30 am    Post subject: Reply with quote

Apprentice

Joined: 22 Apr 2004
Posts: 33
Location: Scotland

We went for efix1 as it was the latest at that time and it was the one our auditors were most interested in, specifically because it allowed you to better secure the Pathway environment (mqpathsec param). We've rolled out this change to all systems, with our dev box being the last to go. It's only our dev folks who use MQ Explorer, so it's only come to light now.
The security param wasn't seen as being an issue on dev, so we simply upgraded MQ having stopped all qmanagers. This seems to be the problem. We organised a copy of MQ Explorer on our own PCs and saw the same problem, i.e. display channels took quite a while but returned info. Display queues however simply timed out.
We created a new queue manager and were able to access it without any problems which suggested that perhaps there were too many queues in the dev qmgrs.
Did a saveqmgr and added the same queues into our test chap, and again, no problems.
So, the solution is to delete and re-create all queue managers if you are using MQ Explorer, despite the fact that the qmgrs themselves are working away like little sweeties.
That was the easy bit. The tricky bit is breaking it to the developers that they have to recreate their qmgrs ('cos they've done some seriously weird stuff in there!).
Thanks for the hints/suggestions.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » MQ Explorer with Tandem MQ
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.