>My errorhandler decides when certain conditions are fatal and it
>calls a procedure which SHOULD kill the app. However, I am caught in the midst of other procedures and valids.
>
>While my PROCEDURE killitnow does accomplish its clean-up tasks, its final QUIT command is ignored due to other calling code wanting to finish execution.
>
>Is there a way to break this cycle so this procedure can accomplish its tasks and ignore the completion of those tasks that called it in the first place.
>
>As always, any help is greatly appreciated

You can use the CANCEL command to stop the procedure that was executng before the erro occured.