Debugging a CA Culprit Report

Debugging a CA Culprit Report

A CA Culprit report is debugged by using a combination of standard debugging techniques and the informational, warning, error, and statistical messages provided by CA Culprit. The following procedural sequence, recommended for finding errors in CA Culprit coding, uses standard and CA Culprit techniques:

1. Desk check the code.
2. Review CA Culprit listings, messages, and error codes, including buffer dumps.

   Refer to the CA Culprit for CA IDMS Messages and Codes Guide, for detailed information.

3. Use procedure module CULLUS48.
4. Print unsorted listings of data and walk through program logic with the data (play computer).
5. Print information beyond that required for the report.
6. Force buffer dumps.

This appendix presents a summary of CA Culprit capabilities that can be useful in debugging.

This section contains the following topics:

Reviewing CA Culprit Listings and Messages

Using CULLUS48

Printing Additional Report Information