Testing Exits

Exits should be well tested with a variety of different input parameters before they are put into production. For exits that need AOCQRY task globals, you can call AOCQRY to set up the globals without evaluating the flag exits, and then invoke the exit on its own for testing purposes. This method saves the overhead of calling AOCQRY every time you run the exit.

Attention:

If you have a syntax error or a no-value-condition in your exit it can cause parts of SA z/OS to abend, resulting in severe disruption of your automation.