> the fact that the domdsm.log contains nothing about the failed operation
> means maybe that it has been rejected before starting using the command
line
> with means in return that it can be a problem between the node and the
> server ??

Mike,

You are correct.  If "domdsm.log" and "dsm_month.log"
do not have an indication that the batch file was run,
then you need to look at the how the scheduler
instance has been defined, i.e. you will need to
examine the parameters that it uses. In addition,
you will need to look at the definition of the
schedule itself.

By the way.. I thought I'd mention a common
problem that we see in this area... and that is
if the OBJECT paramater of the COMMAND type schedule
definition references a directory that contains spaces
in the path... this can cause a problem if the
definition is not correct.
What is the "OBJECTS" option in the
schedule definition set to?  If it contains
spaces, it should look something like this:

OBJECTS='"C:\Program Files\Tivoli\TSM\domino\domino.cmd"'

Notice the usage of single and double quotes.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

Leave everything a little better than you found it.
Smile a lot: it costs nothing and is beyond price.