>> SYSTST$ dir/file dkb500:[000000]*common.dir,dkb500:[sys0]*common.dir
Directory DKB500:[000000] VMS$COMMON.DIR;1 (12,1,0)
DIRECTORY/FILE_ID only reads the directory file that holds the requested name entry.
The file ID can be garbage and it would still be displayed without warning/error.
Here, the file id actually looks reasonable (see below)
>> %DUMP-E-OPENIN, error opening DKB500:[000000]VMS$COMMON.DIR;1 as input
>> -RMS-E-FNF, file not found
A directory with any other option (date, size,...), or any attempt to open the file like that DUMP command will actually use the file-id to find the primary file header in indexf.sys.
That's when the file-id might be found to be bad, which typically means the that ID is fine, because that's just an offset into INDEXF.SYS, so likely to be used, but that the SEQuence does not match between INDEXF and the directory entry.
So there are 2 things to check now
1) Out of curiosity... what is the file with ID=12.
Use DUMP/HEAD/ID=xx as described before for that.
2) Where is the real VMS$COMMON.DIR
Use
$ DFU SEARCH/FILE for that.
Or in a pinch, use
$ PIPE DUMP/NUMBER/form=non [000000]INDEXF.SYS | SEARCH SYS$PIPE VMS$COMMON
Below some example commands and outputs.
hth,
Hein
$ dir/file/nohead/wid=file=40/notrail sys$sysdevice:[000000]VMS$COMMON
SYS$SYSDEVICE:[000000]VMS$COMMON.DIR;1 (15,1,0)
$ dir/file/nohead/wid=file=40/notrail sys$sysdevice:[SYS0]SYSCOMMON
SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR;1 (15,1,0)
$ write sys$output f$fid_to_name("SYS$SYSDEVICE:","(15,1,0)")
DISK$ALPHASYS:[000000]VMS$COMMON.DIR;1
$ PIPE DUMP /HEAD/BLOCK=COUNT=0 /ID=15 sys$sysdevice: | search sys$pipe identification:,name
File identification: (15,1,0)
Extension file identification: (0,0,0)
Back link file identification: (4,4,0)
File name: VMS$COMMON.DIR;1
$ dfu searc/file=VMS$COMMON.DIR sys$sysdevice:
:
$1$DGA1:[000000]VMS$COMMON.DIR;1
