Posted: Wed Feb 22, 2006 3:50 am Post subject: Re: Applying CSDs to MQ Client platforms
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
zpat wrote:
Having recently applied CSD 11 to our (Windows) queue managers, I was thinking it would make sense to do the same on the MQ client platforms.
It does make sense.
zpat wrote:
How important is it to apply MQ client maintenance? Does it really make a difference to application reliability?
It can make a lot of difference when there are bugs in the client.
zpat wrote:
What about Java MQ applications (JMS) - how does the MQ client component of these apps get upgraded?
The CSD installer upgrades the jar files that are in the standard location (<install_root>/java/lib usually). Your java applications may have chosen to use a jar file that is somewhere else entirely - and that location will have to be found out. It's probably best to switch it to use the standard location, rather than upgrading the jar files it's using.
zpat wrote:
I suspect some of our JMS apps are incorporating MQ java classes that are way out of date. What should I look for to find out?
Look for com.ibm.mq.jar on the file system. That will find all instances of the jar file that the application has not packaged in their own JAR.
zpat wrote:
Finally is there an easy way to display the current MQ version and CSD on a Windows MQ client platform?
There's a client verison of the mqver command, but I've forgotten what it is. It might be dmpmqver or dspmqver... Try doing a search here for mqver. _________________ I am *not* the model of the modern major general.
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