Re: TDP & ADSM

Another fix is to have the schedule run d:\runbackup.cmd, which contains one line: start d:\backup.cmd This will let runbackup.cmd finish, showing successful completion of the schedule, while letting the backup run for as long as it needs to. Since you already have to check elsewhere to see if

TDP & ADSM

> We are running ADSM 3.1.0.7, TDP 1.1.1.01 and OS390 Adsm 3.7.0. > I have 2 schedules set up, 1 for NT and 1 for Exchange, these use seperate > folders,seperate management classes, seperate node names and seperate dsm > files. > The ADSM server schedules my exchange backups by pulling the local >

Re: TDP & ADSM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: TDP & ADSM Hi, We are running ADSM 3.1.0.7, TDP 1.1.1.01 and OS390 Adsm 3.7.0. I have 2 s

TDP & ADSM

Hi, We are running ADSM 3.1.0.7, TDP 1.1.1.01 and OS390 Adsm 3.7.0. I have 2 schedules set up, 1 for NT and 1 for Exchange, these use seperate folders,seperate management classes, seperate node names and seperate dsm files. The ADSM server schedules my exchange backups by pulling the local d:\bac