| Nieves,
I suppose your 'problem' is the expected behaviour with VMS alias
directories : a normal VMS system disk always contains such directories
that are physical the same, but with different names.
eg. dir system_disk:[vms$common] = dir system_disk:[sys0.syscommon]
you can check if a file is an alias for another file if they have the
same file-id :
$ dir/FILE sys$sysdevice:[000000]VMS$COMMON.DIR,-
sys$sysdevice:[SYS*]SYSCOMMON.DIR /WID=FILE=50/NOHEAD/NOTRAIL
SYS$SYSDEVICE:[000000]VMS$COMMON.DIR;1 (11,1,0)
SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR;1 (11,1,0)
SYS$SYSDEVICE:[SYS1]SYSCOMMON.DIR;1 (11,1,0)
SYS$SYSDEVICE:[SYS10]SYSCOMMON.DIR;1 (11,1,0)
SYS$SYSDEVICE:[SYS11]SYSCOMMON.DIR;1 (11,1,0)
SYS$SYSDEVICE:[SYS12]SYSCOMMON.DIR;1 (11,1,0)
SYS$SYSDEVICE:[SYSE]SYSCOMMON.DIR;1 (11,1,0)
As you can see all these files (and their subdrectories) are physically the
same directories
If the disk is not a system disk, or not concerning the *common*
directory, it's possible that the customer or an application created
such alias directories with the DCL command
$ set file a.dir/enter=b.dir
For backup, this means that if you do a
backup/ignore=interlock system_disk:[000000...],
you will backup twice the same directory.
To prevent this, use
backup/IMAGE
or if this is not possible,
backup/exclude=system_disk:[sys*.syscommon...]*.*;*
Bart
|