ADSM-L

Re: exchange backup

2004-06-02 01:40:50
Subject: Re: exchange backup
From: "Pan, Sanjoy" <Sanjoy.Pan AT SAVVIS DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 2 Jun 2004 14:39:42 +0900
Sorry for the typo. 
c:\program files\tivoli\tsm\TDPexchange\excfull.cmd .The contents are as
stated below.
 
@ECHO OFF
set exc_dir="C:\Program Files\Tivoli\TSM\TDPExchange"
cd /d %exc_dir%
echo Current date is: >> excfull.log
date /t < NUL >> excfull.log
echo Current time is: >> excfull.log
time /t < NUL >> excfull.log time /t < NUL >> excfull.log
tdpexcc backup * full /tsmoptfile=dsm.opt>>excfull.log

Thanks & best regards,
Sanjoy K Pan



-----Original Message-----
From: Steve Schaub [mailto:Steve.Schaub AT HAWORTH DOT COM] 
Sent: Wednesday, June 02, 2004 3:05 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: exchange backup

Isnt it supposed to be "excfull.cmd"?

Steve Schaub
Systems Engineer, Operations & Storage
Haworth, Inc
616-393-1457 (desk)
616-886-8821 (cell)
Steve.Schaub AT Haworth DOT com 

-----Original Message-----
From: Richard Sims [mailto:rbs AT BU DOT EDU] 
Sent: Tuesday, June 01, 2004 7:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: exchange backup


>  I am getting the error as stated below while taking the exchange 
>backup through TSM scheduler.
...
>Executing Operating System command or script:
>c:\program files\tivoli\tsm\TDPexchange\exefull.cmd
>06/01/2004 10:56:25 Finished command.  Return code is: 1
...

>From my notes in ADSM QuickFacts:

Executing Operating System command or   Message in client schedule log,
 script:                                referring to a command being run
per
                                        either the PRESchedulecmd,
                                        PRENschedulecmd,
POSTSchedulecmd, or
                                        POSTNschedulecmd option; or by
the
                                        DEFine SCHedule ACTion=Command
spec
                                        where OBJects="___" specifies
the
                                        command name.

I don't recognize "exefull.cmd", which may be some local command. Check
that it exists: if it does, check its internals for conditions which may
cause it to exit with a bad value which fouls the schedule.

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

<Prev in Thread] Current Thread [Next in Thread>