home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: Warning: bug check messages
- Date: 23 Jan 1993 00:52:21 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 33
- Distribution: world
- Message-ID: <1jq4s5INNhrv@gap.caltech.edu>
- References: <1993Jan22.160529.1@woods.ulowell.edu>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <1993Jan22.160529.1@woods.ulowell.edu>, welchb@woods.ulowell.edu writes:
- >
- > We are running VMS 5.5-2 on a VAX 6610. When a privileged user,
- >inside mail, says
- >
- >Mail>show forwarding/user=*
- >
- >we get the correct response listing the approximately 30 users who have
- >set forwarding. But the execution of the instruction causes bug check
- >mail messages from VAXsimPLUS; apparently it has something to do with
- >generating stuff coming across the network.
-
- Could you be a bit more explicit about the bug check messages? What do they
- actually say, etc.?
-
- > We reported this as a hardware problem; after dialing in they
- >asked us to call it in as a software problem. Software has never seen
- >this. The only way they could solve it would be to change a sysgen
- >parameter which allows a crash to occur from non-fatal errors; we find
- >this to be unacceptable on our busy machine.
-
- I.e., they'd set SYSGEN parameter BUGCHECKFATAL to 1, which would turn the
- continuable bugcheck you're getting into a fatal bugcheck. Since BUGCHECKFATAL
- is a dynamic parameter, you could, of course, set it to 1 and issue the
- problematic command next time you want to shut down your VAX.
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-