RE: File update after abnormal program termination

>From: "Fisher, Don" <Dfisher@roomstoreeast.com>
>Date: Thu, 21 Feb 2002 16:51:05 -0500
>
>Thanks for the example, Barbara.  I've read about this before and seem to
>remember that this only works if the job ends in a *CNTRLD instead of
>*IMMED.
>
>Is that correct or will this work regardless of how the job ends.

It will work for *IMMED or *CNTRLD.  The cancel handler fires when
the procedure is canceled for any reason.  Here's the ways I can think
of for a procedure to get cancelled.
- sys-request 2
- end job, subsystem, pwrdwnsys, immediate or controlled
- unhandled exception
- escape message sent to caller (say A calls B, B enables cancel
  handler, B calls C.  Then C sends an escape message to A, cancelling
  B.  B's cancel handler fires.)
- exit with F3 from a debugger session (this is how I usually test
  cancel handlers)
- ending the activation group from an active procedure (COBOL STOP
  operation or call to CEETREC (end normal) or CEE4ABN (end abnormal).

Barbara Morris