Making initial checks

There are some initial checks that we can make that may provide answers to common problems that you may have.

Use the information and general advice given in the subtopics to help you to carry out the initial checks for the platform and rectify the problem.

Tips for system administrators

Check the error logs for messages for the operating system:
Check the contents of qm.ini for any configuration changes or errors. For more information on changing configuration information, see:
If the application development teams are reporting something unexpected, we use trace to investigate the problems. For information about using trace, see Use trace.

Tips for application developers

Check the return codes from the MQI calls in the applications. For a list of reason codes, see API reason codes. Use the information provided in the return code to determine the cause of the problem. Follow the steps in the Programmer response sections of the reason code to resolve the problem.
If we are unsure whether the application is working as expected, for example, we are not unsure of the parameters being passed into the MQI or out of the MQI, we can use trace to collect information about all the inputs and outputs of our MQI calls. For more information about using trace, see Use trace. For more information about handling errors in MQI applications, see Handling program errors.

Making initial checks on UNIX, Linux, and Windows
Before you start problem determination in detail on UNIX, Linux, and Windows, consider whether there is an obvious cause of the problem, or an area of investigation that is likely to give useful results. This approach to diagnosis can often save a lot of work by highlighting a simple error, or by narrowing down the range of possibilities.
Making initial checks on IBM i
Before you start problem determination in detail on IBM i, consider whether there is an obvious cause of the problem, or an area of investigation that is likely to give useful results. This approach to diagnosis can often save a lot of work by highlighting a simple error, or by narrowing down the range of possibilities.
Making initial checks on z/OS
Before you start problem determination in detail on z/OS, consider whether there is an obvious cause of the problem, or an area of investigation that is likely to give useful results. This approach to diagnosis can often save a lot of work by highlighting a simple error, or by narrowing down the range of possibilities.

Parent topic: IBM MQ Troubleshooting and support