You are welcome!

No, the syntax is not quite as you have stated; you also need to have an
'=' between the option name and value. For example, if you code

   SUBDIR YES

in the options file, the command line equivalent would be

   -SUBDIR=YES

In the case of your specific option, you can use something like this:

   -PRESCHEDULECMD="cmd.exe /c d:\Oracle\database\idevhotbackup.cmd"

When adding this to a schedule definition, specify the OPTIONS parameter
with the option in single quotes, like this:

   OPTIONS='-PRESCHEDULECMD="cmd.exe /c
d:\Oracle\database\idevhotbackup.cmd"'

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 12/20/2004
15:05:24:

> Andy,
>
> Thanks VERY much for that info.
>
> I assume the syntax in the command line is the same as in the OPT file
> plus leading dash:
>
> -PRESCHEDULECMD 'cmd.exe /c "d:\Oracle\database\idevhotbackup.cmd" '
>
> Is that correct?
>
> Thanks again.
>
> Tab
>
>
>
>
>
>
>
>
> The problem is that OPTFILE is not a valid option in the schedule
> definition. You can, however, include the PRESCHEDULECMD option in the
> schedule definition.
>
> 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.