When should I use ABEXIT NO verses ABEXIT SNAP?
Article ID: 13655
Updated On:
Products
Issue/Introduction
Abend handling for Easytrieve.
What is the difference between ABEXIT NO, and ABEXIT SNAP?
Environment
Resolution
ABEXIT indicates the level of control exercised over program interrupt codes 1 to 11. SNAP prints a formatted dump of CA Easytrieve Report Generator storage areas along with an error analysis report. NOSNAP prints only an error analysis report. NO inhibits CA Easytrieve Report Generator interception of program interrupts.
It is advisable that the ABEXIT value in the site options table be set to NO, and to use the PARM ABEXIT(SNAP or NOSNAP) during development as a debugging aid. Before moving the CA Easytrieve Report Generator program into production, remove the PARM ABEXIT override. This will reduce overhead for production applications.
Additional Information
You can reduce the turnaround time for a support issue by enabling these debugging aids for any documentation sent to CA Technologies.
Additional Considerations:
Generally, parameters that are useful for debugging are not the best choice when executing your program. They can add unnecessary overhead to the execution of production programs. For example, a snap dump (produced with ABEXIT SNAP) is ideal for debugging a S0C7 data exception ABEND. However, ABEXIT NO is a better choice to debug actual source code problems. The default values provided in the Options File are ideal for testing purposes.
Feedback
