Re: TDP & ADSM

Paul,

Since the schedule is a "command" type schedule and it
calls a batch file to run the actual commands,
the exit value of the cmd file is what is returned to
the scheduler status on the server.

On the TSM Server side, to be sure of the actual status
of the backup, you should query the server activity log
for the backup completion records that are logged by
TDP for Exchange itself.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com


Paul Dowie <DOWIE AT CLEAR.CO DOT NZ>@VM.MARIST.EDU> on 12/21/2000 05:06:16 AM

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

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
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 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:\backup.cmd.

My backup works fine, and all my log files are as expected. However the
guys
at the OS390 end get an error message for all my Exchange backups, but
everything works fine ?, the backup does not fail and completes about 2
hours after this message.

Scheduled Start: 20.12.2000 21:15:00
    Actual Start: 20.12.2000 21:15:21
   Schedule Name: WGTNEX_DLYFUL
       Node Name: WGTNEX
          Status: Failed

Because nothing fails I don't get any error messages, so can anyone point
me
in the right direction ?

Any help appreciated,

Paul Dowie
Systems Engineer
CLEAR Communications Ltd
64 9 912 4591
dowie AT clear.co DOT nz