🚀 go-pugleaf

>>Hi,
>>    Am I wrong or does moving a minidisk with VMSECURE change the
>>"last updated" date you see when you do a MDSKSCAN or run the VMRMUA
>>report?  If so, how do I work around this?  I want to clean old minidisks
>>off a couple of volumes.  Thanks.  T.S.
>
>I believe that date is simply the latest file update timestamp
>encountered for that minidisk; ie. moving the minidisk will
>not change the timestamp.  We run our Clearvol process (front
>end to VMSECURE) to clear entire volumes without worrying about
>changing any data or timestamps within minidisks.
>


Well, that depends.  Here is what I see (VMSECURE 4.0, CMS5):

   1) look at the FILE timestamps on a disk
   2) do a VMSECURE MDSKSCAN for the disk
   3) move the disk, same device-type, same size
   4) repeat steps 1 & 2 above, neither the FILE timestamps nor the
      last update timestamp reported by MDSKSCAN show any change.
   5) move the disk to a different device-type (3380->3370)
   6) repeat steps 1 & 2 above, the FILE timestamps are preserved, but
      MDSKSCAN indicates that the disk was updated TODAY.

I believe that this is because MDSKSCAN takes its info from a timestamp in
the CMS file system's directory on the mdisk, not from file timestamps,
from a directory timestamp.

I also believe that VMSECURE will use DDR to move a disk when DDR is a
viable option (same device architecture, same size).  Otherwise it will
use COPYFILE (or alternative).  With DDR, the entire disk image, including
the file system directory is moved intact, with no change.  With COPYFILE,
only the data is kept intact, the physical structure of the file system
will changed, and the file system directory will be re-written (more than once)
and will contain today's filestamp.

Jim Colten