>        I've just started archiving using schedule type of archive and I am
>wondering if there is a way to specify all local hard drives in the objects
>field. I've discovered that I cannot use a wildcard drive specification and
>that I need to use "-subdir=yes". I'm working on archiving WinTel boxes.
>Sure, I can specify all local drives in the Objects field my concerns with
>this method  are two. 1: If another hard drive letter is defined in the
>future and I am not informed (A normal occurrence!) the new drive will not
>be archived and 2: If I just define a generic objects="C: D: E: F: G: H :I
>..." in the schedule I may end up archiving CD/DVDROM drives, etc.
>
>        So my question is this: Is there a way to specify all local drives
>in the objects field in an archive schedule and if not, will I be required
>to use a different schedule for each set of boxes with different number of
>logical drives. Also, if I set a generic, all inclusive drives specification
>will I end up archiving CD/DVDROMs? Any solutions and/or suggestions. I've
>searched the ADSM.ORG and found no answer.

Al - I don't think there's an inherent way to do it,
     but here's a "trick" method I thought of, inciting TSM to generate
the list of local hard drives for you...

1. Create ad hoc options file mydsm.opt
   containing simply:  DOMAIN ALL-LOCAL
2. setenv DSM_CONFIG  mydsm.opt
   (Using the environment variable approach is more flexible than -OPTFILE,
    in that the former works with all commands and the latter with just some)
3. Do 'dsmc q opt' (or 'dsmc show opt' in earlier TSM) and harvest the
   DomainList of local hard drives/file systems.
4. Use the list in your Archive operation.

You could probably play with PRESchedulecmd to use this kind of approach.

    Richard Sims,  http://people.bu.edu/rbs

      "Think different."   -- Apple