| When NSCHED exits voluntarily (for example, when someone issues a
$ SCHED STOP command, or NSCHED encounters a fatal error and decides
to "kill" itself), it will try to append an entry to its event log before
exiting. So either the error is untrappable, NSCHED can't write to the
log (quota?, i/o error?) or something is doing STOP/ID on the NSCHED
process.
If you have image accounting enabled ( $ set accounting... ) you should
always see the time the image exited and the exit status, since VMS is
very careful about writing accounting records. This will give you the
exact time and the exit status. In the case of a STOP/ID, the
status won't be that useful - probably either 0 or the completion status
of the last image executed by the process, but the exact time may give
a hint. You might also try giving the account NSCHED runs under
EXQUOTA as a default privilege (if it doesn't have it already) to
see if this makes the problem go away.
|