Collecting documentation for the problem

As a general rule, the documentation we need to submit for a problem includes all the material we need yourself to do problem determination. Some of the documentation is common to all WebSphere MQ for z/OS problems, and some is specific to particular types of problem.

Make sure the problem you have described can be seen in the documentation you send. If the problem has ambiguous symptoms, we need to reveal the sequence of events leading to the failure. Tracing is valuable in this respect but we need to provide details that trace cannot give. You are encouraged to annotate your documentation, if your annotation is legible and does not cover up vital information. We can highlight any data in hardcopy you send, using transparent highlighting markers. We can also write notes in the margins, preferably using a red pen so that the notes are not overlooked.

Finally, note that if you send too little documentation, or if it is unreadable, the change team will have to return your problem marked "insufficient documentation". It is, therefore, worthwhile preparing your documentation carefully and sending everything relevant to the problem.

The general documentation is described below. However, these are only guidelines, find out from the IBM support center representative precisely what documentation we need to send for your specific problem.