Conference bulova::docnotes

1225.0. "BADNAMEORDER, Bad advice (crosspost from VMSNotes)" by POMPY::LESLIE ([email protected] as of Feb 14) Mon Feb 03 1997 07:04

    This morning I did a directory of pcsi-related files in sys$library.
    
    POMPY::leslie � dir sys$library:pcsi$*
    
    Directory SYS$COMMON:[SYSLIB]
    
    PCSI$MOTIFSHR.EXE;2
                                  172/174           12-NOV-1996 09:15:04.00
    PCSI$MOTIFSHR.EXE;1
                                  173/174           10-DEC-1996 14:20:23.48
    PCSI$SHR.EXE;2                916/918           12-NOV-1996 09:14:45.00
    PCSI$SHR.EXE;1                914/915           10-DEC-1996 14:20:24.31
    PCSI$MOTIFSHR.EXE;1
                                  173/174           10-DEC-1996 14:20:23.48
    PCSI$SHR.EXE;1                914/915           10-DEC-1996 14:20:24.31
                   
    Total of 6 files, 3262/3270 blocks.
    
    Now the above is visibly up the spout, because PCSI$SHR.EXE;1 appears
    twice, so I did an $ana/disk/repair dsa0:
    
    which gave me the message
    
    %ANALDISK-W-BAD_NAMEORDER, filename ordering incorrect in VBN 82
            of directory SYS0.SYSCOMMON.SYSLIB (874,48,1)
            Filenames are PCSI$SHR.EXE
                      and MTHDEF.FOR
    
    
    Hmm. I thought...
    
    
    
    POMPY::leslie � Help/message  BAD_NAMEORDER

BAD_NAMEORDER,  filename ordering incorrect in VBN 'virtual-block- number' 
of directory 'file-id' 

Filenames are 'file-id' and 'file-id'
    
Facility:     ANALDISK, Analyze/Disk_Structure Utility
    
Explanation:  The Analyze/Disk_Structure utility detected two files that
are out of alphabetical order.
    
User Action:  Do a SET FILE/NODIRECTORY on the directory file in which the
files are located; then delete the directory file. Last, run
ANALYZE/DISK/REPAIR to rename all the files from the bad directory into the
SYSLOST.DIR;1 directory.
    
    
    This is plainly a bit dangerous as advice to the inexperienced system
    manager. If I had followed these instructions for sys$library i may
    have never moved again. Worse would have been sysexe.dir!
    
    I would suggest that this 'help' text be revisited and thus this note
    will be posted in DOCNOTES as well.
    
    In the meantime, this is VAX OpenVMS 7.1 and I'd love to know what
    caused it. (I fixed it with judicious rename/copying.)
    
    /andy