1) As far as I know, that's a design flaw and you can't fix it.
2) If the script was started by an ADMIN client, it keeps running even if
the admin logs off.
To kill those you can do Q SESSION, and CANCEL the number of the admin
session.

But if the script was started by a scheduled admin command???
I've wondered about that myself, don't know!

> -----Original Message-----
> From: Orville Lantto [SMTP:olantto AT DTREND DOT COM]
> Sent: Wednesday, January 12, 2000 12:13 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Admin Schedule Events and Script Cancelation
>
> Two issues:
>
> 1)  Why is the querying of admin schedule events unable to see events
> prior to the most recent change to that schedule?  How might I get around
> this?
>
> 2)  How can an entire script execution be canceled?