[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

371.0. "VMS V6.2 rename problem on shadowset" by HTSC12::MICKWIDLAM (Water addict, water man) Mon Mar 24 1997 04:54

I have a customer want to rename a file but failed. The action is below:

$RENAME/LO SEPRG1:SERE.EXE SEPRG1:SERE.XXX
%RENAME-E-NOTRENAMED, EDP:[PROD.SERVICE.PROG1]SERE.EXE;1 not renamed
-RENAME-E-NOTSAMEDEV, Cannot RENAME to a different device

The logical SEPRG1 was defined as below:
$SH LOG SEPRG1/FUL
   "SEPRG1" [exec] = "EDP:[PROD.SERVICE.PROG1]" (LNM$SYSTEM_TABLE)

The logical EDP point only to a DSA device
$DEFINE/SYS/TRAN=CONC/EXEC EDP DSA3:

DSA3 comprised two physical device $22$DIA1 and $22$DIA8.

As we don't have a V6.2 machine with shadowset, we cannot simulation this
problem. Is there anyone seen similar case before?

Regards,
Mickwid.

T.R Title User Personal
Name Date Lines

371.1 Ask For Verification From Customer... XDELTA::HOFFMAN Steve, OpenVMS Engineering Mon Mar 24 1997 13:29 35

T.R	Title	User	Personal Name	Date	Lines
371.1	Ask For Verification From Customer...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon Mar 24 1997 13:29`	35
	The error message: :$RENAME/LO SEPRG1:SERE.EXE SEPRG1:SERE.XXX :%RENAME-E-NOTRENAMED, EDP:[PROD.SERVICE.PROG1]SERE.EXE;1 not renamed :-RENAME-E-NOTSAMEDEV, Cannot RENAME to a different device Clearly indicates there is a second device involved -- I would ask the customer for the output from the following commands: $ SHOW LOGICAL SEPRG1 $ SHOW LOGICAL EDP $ SHOW LOGICAL DSA3 Also ask the customer to perform the same operation without the specification of logical names. If stuck, enable "SET WATCH/CLASS=ALL FILE", and watch and see what is accessed when the command fails. Use "SET WATCH/CLASS=NONE FILE" to disable the XQP logging. This (undocumented) command should be typed exactly as shown -- entire FILE and not the filename -- and this command requires privileges. My assumption is that the customer is not telling you something about the current configuration... -- A shadowset device looks and works like a standard volume. You can create a single volume shadowset for testing, but I suspect there is something odd at this customer's site... I would recommend the current shadowing patches, but that is another issue...

   The error message:

:$RENAME/LO SEPRG1:SERE.EXE SEPRG1:SERE.XXX
:%RENAME-E-NOTRENAMED, EDP:[PROD.SERVICE.PROG1]SERE.EXE;1 not renamed
:-RENAME-E-NOTSAMEDEV, Cannot RENAME to a different device

   Clearly indicates there is a second device involved -- I would
   ask the customer for the output from the following commands:

   $ SHOW LOGICAL SEPRG1
   $ SHOW LOGICAL EDP
   $ SHOW LOGICAL DSA3

   Also ask the customer to perform the same operation without the
   specification of logical names.

   If stuck, enable "SET WATCH/CLASS=ALL FILE", and watch and see what
   is accessed when the command fails.  Use "SET WATCH/CLASS=NONE FILE"
   to disable the XQP logging.  This (undocumented) command should be
   typed exactly as shown -- entire FILE and not the filename -- and
   this command requires privileges.

   My assumption is that the customer is not telling you something
   about the current configuration...

	--

   A shadowset device looks and works like a standard volume.  You
   can create a single volume shadowset for testing, but I suspect
   there is something odd at this customer's site...

   I would recommend the current shadowing patches, but that is
   another issue...