An event procedure may CALL another procedure which may contain ACCEPT
statements, which, in turn, may contain embedded procedures. Although this is handled
in the same fashion as nested PERFORMs and is perfectly legal, doing this
poses the danger of going from one ACCEPT to another uncontrollably. When the
limit of 10 nested accepts is reached, the program starts overwriting memory. It
is possible to warn the user when the limit is reached by giving this
configuration variable a zero ("0") value. This gives users the opportunity to continue
at their own risk. Giving WARNING_ON_RECURSIVE_ACCEPTS a non-zero value suppresses the warning.
To avoid overwriting memory, you may choose to re-code affected programs to
terminate the ACCEPT and perform the CALL after you exit from the ACCEPT. You
may also use CHAIN or CALL PROGRAM instead of the regular CALL, if applicable.