It would help to know:

- What your batch file looks like
- What the output looks like when the batch file is invoked manually
- What the output looks like when the batch file is invoked via
PRESCHEDULECMD

While I do know know enough at this time to say for sure, I doubt that the
use of PRESCHEDULECMD itself has anything to do with the output generated
by ntbackup; rather, it is probably due to some difference between the
environment in which the batch file is run.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-02-23
10:22:43:

> Good Afternoon.
> I'm running with Win2K servers with TSM 5.2.2 and AIX 5.2 TSM 5.2.2
server.
> I have a batch file I'm running that runs NTBACKUP and the
> preschedulecmd does a great job.
> The question/problem I have is the log file(NTBACKUP log) that is
> generated is very different than if the batch is run outside of the
> preschedulecmd.
> Normally I have a full log that NTBACKUP produces(run from a
> scheduled task or on a command line) but when run with the
> "preschedulecmd" inside the dsm.opt file I have minimal to no real
output.
> In the DSM.OPT file I have the following for the preschedulecmd.
>
-------------------------------------------------------------------------------------
> preschedulecmd d:\NTBACKUP\SYSTEMSTATE_Backup.bat
>
--------------------------------------------------------------------------------------
>
> Do I need to add anything different?  I've read the manuals and it
> appears you only need to have quotes if there are "blanks" in the
command.
>
> Have a Great Day,
> Eric Jones
> > *  eric.j.jones AT lmco DOT com
> > *:   607-751-4133
> Cell : 607-972-7621