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.
