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 your platform and rectify the problem.

Procedure

• Carry out the initial checks for your platform:
  • Making initial checks on UNIX, Linux, and Windows
  • Making initial checks on z/OS
  • Making initial checks on IBM i

Tips for system administrators

• Check the error logs for messages for your operating system:
  • Error logs on UNIX, Linux, and Windows
  • Error logs on IBM i
  • Diagnostic information produced on IBM MQ for z/OS
• Check the contents of qm.ini for any configuration changes or errors. For more information on changing configuration information, see:
  • Change configuration information on UNIX, Linux, and Windows
  • Change configuration information on IBM i
  • Customizing your queue managers on z/OS
• If our 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 our 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 you are unsure whether our application is working as expected, for example, you 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 your MQI calls. For more information about using trace, see Use trace. For more information about handling errors in MQI applications, see Handling program errors.