topic %DIRECT-E-OPENIN, error opening DKB100:[000000] in Operating System - OpenVMS

%DIRECT-E-OPENIN, error opening DKB100:[000000]

Dennis_153 — Mon, 11 Apr 2005 14:34:43 GMT

OpenVMS v7.1 I'm looking for a way to make this directory available again.

DIR DKB100:[000000] returns %DIRECT-E-OPENIN, error opening DKB100:[000000]*.*;* as input
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file

Specifying any other valid directory on the disk works correctly. Dir to other disks on the system (dra0:, dkc0:) works correctly.

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Uwe Zessin — Mon, 11 Apr 2005 14:55:54 GMT

It is possible that you are trying this from a non-privileged user, although the error message looks a bit strange. On OpenVMS V7.3-2 I get:

$ dir dsa0:[000000]
%DIRECT-E-OPENIN, error opening DSA0:[000000]*.*;* as input
-RMS-E-PRV, insufficient privilege or file protection violation
$

This, by the way, is the default behaviour as a non-privileged user is usually not supposed to be able to peek into the master file directory.

See if you can change the directory protection from a sufficiently privileged user:
$ set file /protection=W:RE DKB00:[000000]000000.DIR;1

If that does not work, it might be that you disk structure is corrupted and making the directory available again can require somewhat more work or is impossible.

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Hein van den Heuvel — Mon, 11 Apr 2005 15:18:47 GMT

I suspect that the BACKLINK for the Master File Directory (MFD) is broken after a careless rename by an over-privveliged individual.

You can verify with DUMP/HEAD/BLOC=COU=0 /IDENT=4 DKB100

You can fix this with DFU (freeware):

DFU> SET 000000.DIR/BAK=(4,4,0)

Good luck!

Hein.

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Jeffery D. Urmann — Mon, 11 Apr 2005 15:33:11 GMT

Dennis,

Could you report the results of the following:

$ Show Device /Full DKB100:

When you say that you can view other directories on this disk, do you mean e.g.

$ Dir DKB100:[DirName]
or
$ Dir DKB100:[000000]DirName.Dir

Try this as well:
$ Dir DKB100:[0,0]

I`ve heard of issues when using [000000].

Enjoy,

--Jeff

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Dennis_153 — Mon, 11 Apr 2005 15:37:51 GMT

You may be on to something. How does this look?

$ DUMP/HEAD/BLOC=COU=0 /IDENT=4 DKB100:
Dump of file _RALFA1$DKB100:[PKDATA.VALIDATION]000000.DIR;1 on 11-APR-2005 16:31:51.48
File ID (4,4,0) End of file block 16 / Allocated 18
File Header
Header area
Identification area offset: 40
Map area offset: 100
Access control area offset: 255
Reserved area offset: 255
Extension segment number: 0
Structure level and version: 2, 1
File identification: (4,4,0)
Extension file identification: (0,0,0)
VAX-11 RMS attributes
Record type: Variable
File organization: Sequential
Record attributes: Non-spanned
Record size: 512
Highest block: 18
End of file block: 17
End of file byte: 0
Bucket size: 0
Fixed control area size: 0
Maximum record size: 512
Default extension size: 0
Global buffer count: 0
Directory version limit: 0
File characteristics: Contiguous, Directory
Map area words in use: 2
Access mode: 0
File owner UIC: [RLIV]
File prot: S:RWED, O:RWED, G:RE, W:RWED
Back link file identification: (2520,1,0)
Journal control flags:
Active recovery units: None
Highest block written: 18
Identification area
File name: 000000.DIR;1
Revision number: 3
Creation date: 5-JUN-1999 06:18:03.84
Revision date: 7-JAN-2005 15:34:32.96
Expiration date:
Backup date:

Map area
Retrieval pointers
Count: 18 LBN: 1188828
Checksum: 55957

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Dennis_153 — Mon, 11 Apr 2005 15:45:11 GMT

dir dkb100:[operator] works fine. dir dkb100:[0,0] does not, same as posted error.

$ Show Device /Full DKB100:
Disk RALFA1$DKB100:, device type RZ29B, is online, mounted, file-oriented device, shareable, available to cluster, error logging is enabled.

Error count 0
Operations completed 173095289
Owner process ""
Owner UIC [RLIV]
Owner process ID 00000000
Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 139
Default buffer size 512
Total blocks 8380080
Sectors per track 113
Total cylinders 3708
Tracks per cylinder 20
Volume label "CALS2" Relative volume number 0
Cluster size 9
Transaction count 131
Free blocks 5885595
Maximum files allowed 419004
Extend quantity 5
Mount count 1
Mount status System
Cache name "_RALFA1$DKC0:XQPCACHE"
Extent cache size 64
Maximum blocks in extent cache 588559
File ID cache size 64
Blocks currently in extent cache 316557
Quota cache size 0
Maximum buffers in FCP cache 5519
Volume owner UIC [RLIV]
Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD
Volume Status: subject to mount verification, file high-water marking, write-
back caching enabled.

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Hein van den Heuvel — Mon, 11 Apr 2005 15:52:11 GMT

You may be on to something. How does this look?

$ DUMP/HEAD/BLOC=COU=0 /IDENT=4 DKB100:
Dump of file _RALFA1$DKB100:[PKDATA.VALIDATION]000000.DIR;1 on 11-APR-2005 16:31:51.48
File ID (4,4,0)
:
File owner UIC: [RLIV]
File prot: S:RWED, O:RWED, G:RE, W:RWED
Back link file identification: (2520,1,0)

That looks broken.
You need to review skills/priv for "RLIV".

Bad owner, pad priv, bad backlink for 000000.DIR

Fix with DFU and you'll be all set

(AND/DISK/REPAI may well catch this also. Dunno).

hein.

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Dennis_153 — Mon, 11 Apr 2005 19:06:20 GMT

Can DFU be used on an active disk? What version of DFU are you using? How do you specify the device that the SET will act upon?

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Hein van den Heuvel — Mon, 11 Apr 2005 22:18:58 GMT

DFU is your friend. No VMS system manager shoudl be without. Trust me.
Just get it, use it and be happy.
Mind you, It's not like you have much choice at this point!
Actually, there are little programs out there specifically to fix this problem, but since DFU can do, and yes on a active disk, just go that route. Help within dfu will explain details.

Regards,
Hein.

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Ian Miller. — Tue, 12 Apr 2005 03:18:12 GMT

I think for VMS V7.1 you need DFU V2.7A on Freeware V5
http://h71000.www7.hp.com/freeware/freeware50/dfu027a/

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Ian Miller. — Tue, 12 Apr 2005 03:28:26 GMT

in DFU V2.7A I think you have to do
DFU VERIFY/FIX/LOCK/DIR DKB100:

as the SET command previously mentioned is not there. The author of DFU is the Wizard of ODS and it is truely indespensble.

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Jan van den Ende — Tue, 12 Apr 2005 08:02:31 GMT

Hi,

we have hit one of my favorite wooden horses again!

It is some time back, but I have _WITNWSSED_ this situation getting created!

And the easiest way to do it is by using the [000000.xyz...] directory syntax.

I see it time and again, and quite often there is no real harm, but if the target file spec of a BACKUP or RENAME command contains [000000.dirname], then you may well create a REAL [000000] directory _IN_ the MFD (000000.DIR <> (4,4,0) )
A similar command again creates the subject of this thread!

Let us all solemny promise now to NEVER again use that syntax, and educate anyone seen doing it!!

Proost.

Have one on me.

Jan

Re: %DIRECT-E-OPENIN, error opening DKB100:[000000]

Dennis_153 — Thu, 14 Apr 2005 15:52:59 GMT

DFU 2.7A did the trick. DFU VERIFY/FIX/LOCK/DIR DKB100: and about five seconds was all it needed. I'm not sure how it occurred, but it looks like a privileged user was messing around were they shouldn't.

Thanks for the assistance. I had a cpu fan fail on the same system today. It took about 5 minutes to fix, but it gave me an oppertunity to run the fix on a quiet disk.