Re: Why did this RENAME lose my files?

On Jun 27, 9:23 am, AEF <spamsink2...@xxxxxxxxx> wrote:
On Jun 27, 9:01 am, Jan-Erik Söderholm <jan-erik.soderh...@xxxxxxxxx>
wrote:

AEF wrote:
[...]

What dir

> $ DIR FTDAYBCK.JOU;*

say before the REName ?

It looked normal. But it seems to me that DIR/SECURITY would be
useful. Fortunately,I was able to reproduce the problem. I'm running
VMS V6.2 with all mandatory ECO kits installed and a few optional
ones.

DCL> DIR /SECURITY FTDAYBCK.JOU

Directory SYS$SYSDEVICE:[FELDMAN]

FTDAYBCK.JOU;4 1/9 27-JUN-2008
15:18:05.45 [1,1] (RD,RWD,,)
FTDAYBCK.JOU;3 1/9 27-JUN-2008
15:17:54.16 [1,1] (RD,RWD,,)
FTDAYBCK.JOU;2 1/9 27-JUN-2008
15:17:38.83 [1,1] (RD,RWD,,)
FTDAYBCK.JOU;1 1/9 27-JUN-2008
14:54:17.82 [1,1] (RD,RWD,,)

Total of 4 files, 4/36 blocks.
DCL> RENAME FTDAYBCK.JOU;* .JOU_SAVE
DCL> RENAME FTDAYBCK.JOU;* .JOU_SAVE
DCL> RENAME FTDAYBCK.JOU;* .JOU_SAVE
%RENAME-E-OPENIN, error opening SYS$SYSDEVICE:[FELDMAN]FTDAYBCK.JOU;4
as input
-RMS-F-REENT, file could not be renamed and recovery failed; file has
been lost
-SYSTEM-F-NOPRIV, insufficient privilege or object protection
violation
%RENAME-E-OPENIN, error opening SYS$SYSDEVICE:[FELDMAN]FTDAYBCK.JOU;3
as input
-RMS-F-REENT, file could not be renamed and recovery failed; file has
been lost
-SYSTEM-F-NOPRIV, insufficient privilege or object protection
violation
%RENAME-E-OPENIN, error opening SYS$SYSDEVICE:[FELDMAN]FTDAYBCK.JOU;2
as input
-RMS-F-REENT, file could not be renamed and recovery failed; file has
been lost
-SYSTEM-F-NOPRIV, insufficient privilege or object protection
violation
%RENAME-E-OPENOUT, error opening SYS$SYSDEVICE:
[FELDMAN]FTDAYBCK.JOU_SAVE;1 as output
-RMS-E-ENT, ACP enter function failed
-SYSTEM-W-DUPFILENAME, duplicate file name
DCL> HELP/MESS RMS-F-REENT
%DCL-I-IGNQUAL, qualifiers appearing before this item were ignored
\MESS\
%MSGHLP-F-NOTFOUND, message not found in Help Message database
DCL>

I had READALL enabled by not BYPASS and I ran this from the SYSTEM
account.

AEF

AEF,

I concur with Mike. READALL allows the directory to be read, not
written. I suspect that a DIRECTORY/SECURITY on the directories
involved will clarify.

ANALYZE will recover the files, they have not been deleted (although I
will not vouch for the version numbers, verify that the dates are in
correct sequence).

- Bob Gezelter, http://www.rlgsc.com
.

Relevant Pages