Kelly J. Lipp wrote:
>
> You could have a distinct include/exclude file on each system that excluded
> everything you don't want and includes only those things you do.  Sort of a
> pain because you have to modify each client's options file.
>
> Kelly
>
> -----Original Message-----
> From:   Steve Watson [SMTP:swatson AT KODAK DOT COM]
> Sent:   Saturday, March 07, 1998 8:20 AM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        Variables in schedules
>
> I have a situtation where I would like to run many systems out of one
> schedule but on each
> system the object name is slightly different.  Is there a way that I could
> set a variable in a pre script
> that would cause the schedule to backup a different file system on each
> system
>
> example:
>
> schedule 1 backups two system: system1 and system2.  On system 1 we want to
> backup the filesystem
> /var/adm/system1/logs and on system2 we want to backup
> /var/adm/system2/logs.  Could I specify
> the object as /var/adm/$variable/logs and have both backed up from the same
> schedule rather
> than have two schedules...
>
> Thank you in advance
>
> Steve
>
> From Lotus Notes user: Stephen T. Watson
Steve,

Another approach (since I am assuming you are backing things up at the
filesystem level using a V2 client), is schedule a COMMAND (script) that
runs on each client.  The script would build the appropriate filesystem
path in $variable and then do a dsmc incr $variable.  Your
include/exclude list could then be generic (like the script) to simply
include /var/adsm/.../* <mgmtclass>

David Hendrix
dmhendri AT fedex DOT com

--
As soon as we started programming, we found to our surprise that it
As soon as we started programming, we found to our surprise that it
wasn't as easy to get programs right as we had thought.  Debugging had
to be discovered.  I can remember the exact instant when I realized
that a large part of my life from then on was going to be spent in
finding mistakes in my own programs.
                -- Maurice Wilkes discovers debugging, 1949