BARBE@sdr.slb.COM.UUCP (06/22/87)
One thing that I successfully did after getting:
SYSBOOT-W-DMPFRG, SYSDUMP.DMP is too fragmented to be used
At that time (VMS 4.2) it prevented booting the system and DEC
Telephone Support Center told me to BACKUP and RESTORE, which I
didn't want to risk doing...
I don't know if this problem still occurs with VMS 4.5 or later.
1) I ran to a working system, dumped SYS$SYSTEM:SYSBOOT.EXE, located the
SYSDUMP.DMP file name string that was not part of a diagnostic message
(for VMS 4.5 SYSBOOT.EXE is dated 2-SEP-1986 15:15, the string starts at
01b9 in VBN 21).
2) Made a conversational boot. When I got SYSBOOT>, switched the terminal
into console mode (^P or whatever), examined all lower addresses looking
for SYSDUMP.DMP, starting at 01b9, then 03b9 and found it at 61b9.
3) Changed SYSD into KYSD with DEP 61b9 43595344.
Then continued SYSBOOT which did not complain about the fragmented file
since it didn't find it. Then under VMS I deleted the faulty file.
The above technique is worth trying 1) when the official solution is
ridiculously long compared to what you need, AND 2) you know what you are
doing.