Unfortunately I don't think we can determine why your script is failing,
at least not without more information. I don't believe that the change in
TSM release is responsible for the script failure, as nothing has changed
in the way the script is launched.
What does your script look like? You should look at any commands that rely
on certain environment settings that may not exist when running the
scheduler (for example, PATH settings, program-specific environment
variables, commands that will only run under a certain NT account, etc.).
Also, if the script has more than one command in it, try to narrow it down
to which exact command is failing. For example, if your script looked like
this:
========================================
@echo off
dir e:\tsm\baclient\*.opt
dir e:\xsm\baclient\*.opt
========================================
Then you could put some "echo" statements around it, like this:
========================================
@echo off
@echo Issuing first dir command >> e:\tsm\baclient\myscript.out
dir e:\tsm\baclient\*.opt
@echo RC = %errorlevel% >> e:\tsm\baclient\myscript.out
@echo Issuing second dir command >> e:\tsm\baclient\myscript.out
dir e:\xsm\baclient\*.opt
@echo RC = %errorlevel% >> e:\tsm\baclient\myscript.out
========================================
In my rigged example, there is no directory "e:\xsm", so the second dir
command should fail. Here is what myscript.out looks like after the
schedule runs:
========================================
Issuing first dir command
RC = 0
Issuing second dir command
RC = 1
========================================
This way, I can narrow the problem down.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Lawrence Clark <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07/23/2002 08:10
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: pre and post sched on NT TSM 5.1.1
Well, yes, the preschedcmd fails....That's the question. It did not fail
under the previous release, and when run apart from the backup by
running the script by ilself, then doing the backup without the
preschedcmd in the dsm.opt, it runs successfully.
So the question is why does it fail when initiated vis the preschedscm
parm.
>>> [EMAIL PROTECTED] 07/22/02 05:35PM >>>
The first error message below tells you what is happening - the pre
command
failed - the schedule is not executed. This is new with 5.11 - if the
preschedulecmd fails, the schedule doesn't run.
Tim Rushforth
City of Winnipeg
-----Original Message-----
From: Lawrence Clark [mailto:[EMAIL PROTECTED]]
Sent: July 22, 2002 2:49 PM
To: [EMAIL PROTECTED]
Subject: pre and post sched on NT TSM 5.1.1
We noticed after upgradeing the TSM client on NT that those servers
with
pre and post sched commands were not backing up. Anyone else
experience
this?
DSM.OPT entries:
preschedulecmd e:\adsmbackup\cinfoadsmprebackup.bat
postschedulecmd e:\adsmbackup\cinfoadsmpostbackup.bat
ERROR LOG ENTRIES:
07/17/2002 06:55:27 ANS1902E The PRESCHEDULECMD command failed. The
scheduled event will not be executed.
