Hans,
Yes, SFS does keep date of last reference internally. LISTFILE * * fm
(ALLDATES on the directory in question will show you the date of last
reference for each file. Look at the LREF-DT column. I don't think SFS
keeps the date that a directory was last accessed, but if someone
accesses a directory without looking at or changing any files, does it
matter?
Dennis O'Brien
We are Borg of America. You will be assimilated. Resistance is futile.
________________________________
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Hans Rempel
Sent: Wednesday, October 08, 2008 13:04
To: [email protected]
Subject: Re: [IBMVM] SFS files last accessed or updated
Thanks Dennis and others who have replied. I do use the audit files for
links to minidisks but I saw no reference to SFS access. Thanks for the
tip on CPIGNORE DIRLINK.
I was hoping the SFS did keep this information internally but maybe not.
I just downloaded the SFSTOOLS but I'm not sure there is anything there
to assist me. I really like the SFSULIST tool. Thanks again Kris for all
your contributions to the VM download page.
Bruce. I was not able to find the DIRLIST stage at Marist site. Would
you have the URL for their downloads.
Thanks again all for your thoughts on this subject.
Hans
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of O'Brien, Dennis L
Sent: October 8, 2008 3:18 PM
To: [email protected]
Subject: Re: SFS files last accessed or updated
Hans,
For SFS, take a look at the ALLDATES option of LISTFILE. You're correct
that there's no date of last access for minidisk files. You could scan
your VM:Secure audit files to look for links to the minidisk. That
won't tell you what files were accessed, but it will tell you that
someone is either using the minidisk or has an old link in their PROFILE
EXEC. We scan our audit files every day, and keep a link history that
shows requester, target, month, and year. That summary data is kept for
a year. The link history for our largest system takes just over 5
cylinders. If you set up something like that, you could initially
populate it with whatever audit information you keep, then update it
daily going forward.
Once you decide what can be removed, if it's entire userids I recommend
placing them on hold for at least a month before deleting them. Hold
will prevent anyone from linking the minidisk. If you have VM:Secure
set up to manage SFS, it will also disable the filespaces. If someone
then discovers that they can't access something they need, it's trivial
to reactivate the userid. If you decide to remove individual minidisks,
create rules preventing anyone from linking. Make sure you check for
directory links if you have CPIGNORE DIRLINK in VMXRPI CONFIG. You can
manually disable filespaces, but not individual directories. Leave the
rules or disable in place for awhile before you actually delete the
resource.
Dennis O'Brien
We are Borg of America. You will be assimilated. Resistance is futile.
________________________________
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Hans Rempel
Sent: Wednesday, October 08, 2008 11:31
To: [email protected]
Subject: [IBMVM] SFS files last accessed or updated
We are starting a major cleanup of old very old userids so I wish to see
if I can review SFS directory entries to see when they were last
referenced. We have VMSECURE installed and we know when the userid was
last accessed but we do not know if the data is being accessed by other
userids.
For mdisks I'm using system centre utilities VMRMUA to show date last
time file was updated since I believe that is the best we can do with a
mdisk.
Hans Rempel
