Troubleshooting › Collect Diagnostic Data › Symbolic Postprocessors

Symbolic Postprocessors

Review all output from the postprocessor for error messages. If any messages are found, locate the message in the CA Application Quality and Testing Tools Symbolic Guide, then review the reason and suggested action(s).

Gather the following documentation:

• All output from the postprocessor
• The listing file used as input to the postprocessor

For all problems, gather:

• The full IBM system SYSUDUMP if an abend has occurred. Although there are other products that, like CA SymDump Batch, produce very neat, easy-to-read, condensed dumps appropriate for debugging user programs, they generally do not contain enough information for our purposes.
• All JCL, JOBLOG information, and messages for the job that ended in error.
• You may occasionally encounter a problem involving a COBOL program purchased from another vendor that is considered proprietary. While you are usually allowed to send the source listing on paper, you may not be permitted to send it on tape. Check. Arrangements can usually be made, including the signing of nondisclosure agreements by CA.