Many days ago I asked for (and received, thank you) help about
'dsmc select' and 'dsmc expire' with the '-filelist' option. Here
there has been installed a 'Vault' like a HMC that moves files and
email messages that have not been used in some time out of the file
server and exchange server (can you tell we're using Microsoft)
to a different location. The 'Vault' server leaves behind 'stub'
files and the hooks in the OS allow for users to open the stub and
receive the file as if the file were still local to the file server.

This behavior is causing the TSM server some problems.  The OS
hooks do set the 'O' or 'Offline' flag when a file is moved and a
stub remains.

Attached (if the list server lets me do attachments) is the program
I mentioned that I would pass on once I'd finished writing it. The
name is 'dsmpmj' for 'DSM - Poor Man's Journal' since the program
also does the journalling feature of the B/A client.

The program reads yesterday's file, scans the local filesystem,
and then compares the two lists. Anything that existed yesterday,
but is not there today goes into the EXPIRELIST.  Anything that
has a timestamp newer than the timestamp of the YESTERDAY file goes
into BACKUPLIST. If any part of the lines in EXCLUDELIST match the
local files, the files are excluded. That means if BACKUPLIST has
a line '.sys' this will match the file 'c:\user\intricate.system',
the latter file not making it to BACKUPLIST.

The way to run this is:

dsmpmj -y YESTERDAY -b BACKUPLIST -e EXPIRELIST -x EXCLUDELIST

There is also a -r REFERENCEFILE that can be used the first time
the program is called to give dsmpmj a place to start for it's
backup timestamp (i.e. four days ago).

Once you have run dsmpmj feed the two generated files to dsmc:

c:\> dsmpmj -y yesterday -b backup -e expire -x excludes
c:\> dsmc expire -filelist=expire
c:\> dsmc sel -filelist=backup

That's about it. I hope it works for other people.

Mike

dsmpmj.c
Description: Text document