Collecting documentation for the APAR

The documentation that you submit for an APAR must include all the material you need to perform problem determination. Some documentation is common to all CICS® VR problems, and some is specific to particular types of problems.

Ensure the documentation that you send reflects the problem that you describe. If the problem has ambiguous symptoms, show the sequence of events that lead up to the failure. Tracing is valuable here, but you might be able to provide details that the trace cannot give. Annotate your documentation. Highlight important data in the documentation you send.

If you send too little documentation, or if it is unreadable, the change team will return the APAR marked "insufficient documentation". Prepare your documentation carefully and send everything that is relevant to the problem.

Here is a list of the documentation and supporting material you might be asked to submit for an APAR. These are guidelines; you must find out from your Support Center representative precisely which documentation to send for your specific problem.