In processes taking many steps to prune data I usually have a "delreason" field: if empty, the record is not deleted,
if it gets deleted I fill it with a string making it easy to identify the process step which deleted.

Easy to track even afterwards and quite fast: deletion writes more than the deleted flag, but not much,
finding bugs is speeded up tremendously.

>Thanks for the warnings about debugging when SELECTing a cursor back into itself.
>My case is rather simple, as I'm simply pruning the same cursor (one or more times).
>In retrospect, I could have accumulated the selection criteria (which are handled thru macro substitution anyway) and done them all at once. But, I think it reads a little better the way that it is.

>
>>>Can I do a SELECT phrase from a cursor where the INTO goes back into the same named cursor?