Mark,

There are a few different ways you can do this.
As you eluded to...
I think the easiest is to use the "original" nodename
for the scheduled event and then have the batch or command
file that does the backups specify an "alternate" options file
(with the "/ADSMOPTFile" option) on the backup command.

Alternatively you can have another instance of the
scheduler running as the alternate node and create the
scheduled event for that node specifically.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM ADSM Agent Development
hoobler AT us.ibm DOT com



"Remeta, Mark" <MRemeta AT SELIGMANDATA DOT COM> on 04/12/99 02:24:43 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Del Hoobler/Endicott/IBM)
Subject:  Re: Exchange Agent Question





Dell, If I was to setup the scenario you mentioned below, how would it be
done.
Add another node to the database with a different name than the original.
Then create a scheduled event to occur once a month. The question I have is
here. Do I create the event using the original nodename and then just use a
different option's file with a line in it like NODEName <newnodename> ? If
I
create an event using the new node name (which is not the actual name of
the
node) wouldn't the scheduled action fail because it couldn't connect to the
bogus node name?

Thanks in advance,
Mark