home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!usenet.ins.cwru.edu!agate!ucbvax!lrw.com!leichter
- From: leichter@lrw.com (Jerry Leichter)
- Newsgroups: comp.os.vms
- Subject: Re: SYSDUMP.DMP File Question...
- Message-ID: <9301080512.AA12581@uu3.psi.com>
- Date: 8 Jan 93 03:50:14 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 43
-
- I just wanted to correct a small, very common error:
-
- The crash-dump file must be on the system disk.
-
- The crash dump file is opened early in startup, way before you can mount any
- disks, so it must, indeed, be on the system disk.
-
- You can, however,
- have the system write its crash-dump to the pagefile, but I believe
- that pagefile must be on the system disk to be used as a crash-dump
- area.
-
- The dump can go only to the primary pagefile. The primary pagefile must be
- on the system disk, since it is opened at about the same time the crash dump
- file is located, very early during system boot.
-
- Note that in recent versions of (VMS V5.2 or later? I'm not sure) you don't
- need to have a primary pagefile.
-
- This is done by setting SAVEDUMP to 1.
-
- No; SAVEDUMP does something very different.
-
- If a crash takes place, there was no SYSDUMP.DMP file when the system booted,
- but there is a primary page file, then the dump will be taken to the primary
- pagefile. (Note: NOT there was no USEFUL SYSDUMP.DMP file - a 0-block
- SYSDUMP.DMP file will prevent dumping to the pagefile.) SAVEDUMP is not
- checked.
-
- SAVEDUMP is checked AT THE NEXT BOOT. If, at that time, it is 0, the dump
- in the pagefile is ignored and system just starts using the pagefile. If,
- however, it is 1, the parts of the pagefile that contain the dump are marked
- off-limits, preserving the dump. (You normally free them up for use in paging
- by using ANALYZE/CRASH/COPY to copy the information to a more convenient
- location. You can also use ANALYZE/CRASH/RELEASE to simply discard the dump.)
-
- Note, BTW, that because the dump is ALWAYS taken, and it is the value of
- SAVEDUMP defined at the NEXT boot that matters, you can run with SAVEDUMP=0,
- effectively ignoring the dumps, and then at some point after a crash do an
- interactive boot, set SAVEDUMP to 1, and analyze the dump.
-
- -- Jerry
-
-