Home

 

Preliminary checks

 

Before you start problem determination in detail, it is worth considering the facts to see if there is an obvious cause of the problem, or a likely area in which to start your investigation. This approach to debugging can often save a lot of work by highlighting a simple error, or by narrowing down the range of possibilities.

The cause of your problem could be in:

• WebSphere MQ

• The network

• The application

The sections that follow raise some fundamental questions that we need to consider. As you work through the questions, make a note of anything that might be relevant to the problem. Even if your observations do not suggest a cause immediately, they could be useful later if you have to carry out a systematic problem determination exercise.

• Has WebSphere MQ run successfully before?
  

• Are there any error messages?
  

• Does the Windows Application Event Log show any WebSphere MQ errors? (Windows only)
  

• Are there any return codes explaining the problem?
  

• Can you reproduce the problem?
  

• Have any changes been made since the last successful run?
  

• Has the application run successfully before?
  

• Problems with commands
  

• Does the problem affect specific parts of the network?
  

• Does the problem occur at specific times of the day?
  

• Is the problem intermittent?
  

• Have you applied any service updates?
  

 

Parent topic:

Problem determination

fa14830_

 

Home