2. The program to be canceled shall not be in the active state or contain a program in the active state. If a program in the active state is explicitly or implicitly referenced in a CANCEL statement, the referenced program is not canceled.

3. No action is taken when a CANCEL statement is executed referencing a program that has not been called in this run unit or has been called and is at present canceled. Control is transferred to the next executable statement following the explicit CANCEL statement.

4. The contents of data items in external data records described by a program are not changed when that program is canceled.

5. The CANCEL statement has no effect on a program with the RESIDENT clause specified in its PROGRAM-ID paragraph.

6. The ALL clause affects all programs in the non-active state as described in rule 2.

7. The CLIENT clause affects the client called program (with CALL CLIENT statement) when running in ApplicationServer mode.

8. The CANCEL statement doesn’t have any effect on programs called through CALL THREAD. Threads are automatically cancelled by the Framework when they terminate.

9. The CANCEL statement doesn’t have any effect on native libraries (e.g. DLLs). Call the C$UNLOAD_NATIVE library routine in order to cancel a native library.

10. You can install a hook class for the CANCEL statement via the iscobol.call_cancel.hook configuration property.