Analyzing problems

 

This chapter suggests reasons for problems you might have with WebSphere MQ for iSeries, to help you in problem determination. You usually start with a symptom, or set of symptoms, and trace them back to their cause.

Do not confuse problem determination with problem solving although the process of problem determination often enables you to solve a problem. For example, if you find that the cause of the problem is an error in an application program, we can solve the problem by correcting the error.

However, you might not always be able to solve a problem after determining its cause. For example:

• A performance problem might be caused by a limitation of your hardware.

• The cause of the problem might be in the WebSphere MQ for iSeries code. If this happens, we need to contact your IBM support center for a solution.

This chapter is divided into the following sections:

• Preliminary checks

• Problem characteristics

• Determining problems with WebSphere MQ applications

• Obtaining diagnostic information

• Error logs

• Dead-letter queues

• First-failure support technology (FFST)

• Performance considerations