[mod.computers.vax] Process BugChecks and the Accounting Log

nagy%bsndbg.hepnet@LBL.ARPA.UUCP (02/20/87)

>>Why is a process terminated when trying to:
>>
>>                 $ TYPE SYS$SYSDEVICE:[000000]QUORUM.DAT
>>
>>on a common system disk that is used as a quorum disk in the cluster.
     
>What I suspect you are seeing is a exec mode bugcheck caused by RMS
>when you try to type the file.  A way to confirm this theory would be
>set the sysgen parameter BUGCHECKFATAL to 1 and see if the system
>crashes when the file is typed.  (Not recommended for a busy cluster)
     
Executive-mode BugChecks cause processes to "crash" and disappear from
the system.  Kernel-mode BugChecks, of course, cause the system to
disappear from itself.

There is an easier way to find out what happened to BugCheck'ed processes.
Rather than crashing the system, go look at the process termination
record in the accounting log.  You will find that this record contains
the process termination status, which (for failing and BugCheck'ed
processes) indicates why the process terminated.  The command to do
this is something like:

	$ ACCOUNTING /FULL /TYPE=PROCESS /SINCE=xxxxx

to only look at the accounting records since time "xxxx" (TODAY is 
usually good enough).