home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!uwm.edu!linac!att!ucbvax!IPG.PH.KCL.AC.UK!SYSMGR
- From: SYSMGR@IPG.PH.KCL.AC.UK
- Newsgroups: comp.os.vms
- Subject: re: re.2: extending INDEXF.SYS (new idea!)
- Message-ID: <27A0322A_001750A8.00963CCFDBE03840$626_3@UK.AC.KCL.PH.IPG>
- Date: 18 Nov 92 12:43:16 GMT
- Article-I.D.: UK.27A0322A_001750A8.00963CCFDBE03840$626_3
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 27
-
- > Wolfgang J. Moeller writes:
- >
- > |It occurred to me that there is a VMS utility for extending files,
- > |which *has* that important check built-in:
- > |
- > | $ MCR SYSGEN CREATE disk:[000000]INDEXF.SYS/size=<newsize>
- >
- >
- > If this does work, you had better check to see if
- > the INDEXF.SYS file has not been marked NOBACKUP!!
- >
-
- Well spotted!
-
- Also, you want to check the results with ANALYZE/DISK. At the very least,
- it will report that the backup index file header is bad. /REPAIR will fix
- that. Also, SYSGEN CREATE is unlike $EXTEND in that it makes the used size of
- the file equal to the allocated space. You may find that there are umpteen
- thousand 'bad file headers' to be repaired. (This may in turn depend on the
- status of /HIGHWATER on the target disk)
-
- It's still a neat idea, though.
-
- Nigel Arnot
-
- NRA%ipg.ph.kcl.ac.uk@nsfnet-relay.ac.uk (internet)
- NRA%uk.ac.kcl.ph.ipg@ukacrl.bitnet (bitnet)
-