Rational Developer for System z
PL/I for Windows, Version 8.0, Programming Guide

Testing and debugging your programs

Testing your programs
General debugging tips
PL/I debugging techniques
Using compile-time options for debugging
Using footprints for debugging
Using dumps for debugging
Formatted PL/I dumps--PLIDUMP
SNAP dumps for trace information
Using error and condition handling for debugging
Error and condition handling terminology
Error handling concepts
System facilities
Language facilities
ON-units for qualified and unqualified conditions
Conditions used for testing and debugging
Common programming errors
Logical errors in your source programs
Invalid use of PL/I
Calling uninitialized entry variables
Loops and other unforeseen errors
Tips for dealing with loops
Unexpected input/output data
Unexpected program termination
Other unexpected program results
Compiler or library subroutine failure
System failure
Poor performance

Effective design and coding practices help you create quality programs and should be followed by thorough testing of those programs. You should give adequate attention to the testing phase of development so that:

The process of testing usually uncovers bugs, a generic term that encompasses anything that your program does that you did not expect it to do. The process of removing these bugs from your program is called debugging.

While this chapter does not attempt to provide an exhaustive coverage of testing and debugging, it does provide useful tips and techniques to help you produce top-quality, error-free PL/I programs. Both general and PL/I-specific testing and debugging information follow.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)