This tip is based on "Murach's CICS for the COBOL Programmer." If you would like to purchase a copy of the book, click here.
There's an old saying that if you write a line of code then you will have a bug. Everyone who has ever coded knows the frustrations of programming errors. This tip is a checklist for how to check a CICS program for errors. It provides a comprehensive list of things that must be checked when testing a CICS program.
What to check for on the screen
- Are all the headings and captions placed correctly?
- Are the user instructions displayed properly?
- Is there any garbage on the screen?
- Are all words spelled correctly?
- Is the cursor in the correct initial location?
- Does the cursor move correctly from field to field?
What to check for as you enter valid data
- Are all the program screens displayed in the correct sequence?
- Do all the attention keys work correctly?
- Are the user messages always correct?
- Are the functions of all attention keys indicated?
- Does the program properly acknowledge the receipt of valid data?
- Are work fields properly cleared after each valid transaction?
- Are control totals accumulated properly?
- Are files updated properly?
What to check for as you enter invalid data
- Does each case of invalid data for each field yield an appropriate error message?
- Do look-up routines work properly?
- Is the field in error highlighted?
- Is the cursor positioned at the field in error?
- When you correct the error, do the error message and highlighting go away?
- Does the program post transactions even though errors are detected?
- Does the program detect all possible cross-validation errors?
- Does the program properly detect and highlight multiple entry errors?