You are currently browsing peterbroadhurst’s articles.

Here’s a little utility which allows you to match an integer against WMQ constants, or find WMQ bit flags it contains.

You might find it useful if you are looking at output from an application which prints WMQ fields as an integer, or in hex.
Read the rest of this entry »

I came across The Support Authority series of WAS related articles on developerWorks the other day, with their latest article on WAS trace released yesterday.

In this series a group of IBM’s technical support professionals are taking the time to explain the trace, and other RAS (reliability, availability and serviceability) features, of WebSphere Application Server and IBM’s JVM.

If you use WMQ as a messaging provider for WAS, or standalone WMQ JMS applications, I suggest taking a look.

A February post on listeners lead on to some discussion on the operation of channels, and diagnosing issues.
I thought this comment from John merited a post of its own.

There are a number of status indicators and other sources of information available on the operation of WMQ channels – with new ones for WMQ V6.0.

So here’s a summary of some things that you can use in diagnosing channel issues and links to more information. There’s lots out there on this subject, so do add links to other useful docs and sources of information.
Read the rest of this entry »

Most discussions on using SSL with WMQ Java applications (using the WMQ Classes for Java) talk about using the javax.net.ssl.keyStore etc. Java System Properties to specify a certificate store and password.

This works well for most applications.
However, there are a few limitations to this approach:

  • The SSL context is initialised only once – the first time it is used.
    If the path/password is incorrect, the JVM must be terminated before trying again.
  • Debugging is only available through using javax.net.debug system property.
    This produces a large amount of output on the console.
  • Only one certificate store can be used per JVM.
    You might want to use different certificates to connect to different queue managers.

So, this post has the starting point for an alternative.

Read the rest of this entry »

There are often queries about using the WMQ Explorer from a desktop (without a WMQ install), to admin back-end queue managers.

If you have a back-end Windows installation of WMQ, RDC is a good option.
But what about when you’ve got a back-end Linux installation of WMQ?

Well, here’s an option:
Run the WMQ Explorer on the server, but using the X server of your desktop…

Read the rest of this entry »

I saw Dale’s Diagnosing Triggering Problems post, and thought I’d add a checklist I put together.

The idea was to give some help diagnosting common triggering issues when setting up a new triggered queue for an app-team, or diagnosing a queue-depth alert at 2am on a callout.

The Conditions for a Trigger Event section in the APG is the definitive reference, but this checklist is written more from a diagnosis point of view.

The document has a UNIX bias I’m afraid…

Read the rest of this entry »