Take a look at the client manual. In the chapter on "Automating Tasks",
there is a discussion on return codes from the command line client, which
also encompasses the scheduler. Perhaps that discussion, along with what
you know about your PRE/POSTSCHEDULECMD commands will help explain the
situation.

If that doesn't help, then please elaborate on what you mean by "failed"?
How do you know it failed? It would help to see the dsmsched.log and
dsmerror.log files that show the failure, and if you could point out how
you know the command failed (if it isn't obvious from log files).

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.eyebm DOT com (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.




Markus Klein <markus.klein AT VITERRA DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/14/2003 22:24
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        PRESCHEDULECMD failed after upgrading from TSM 4.1.x to 
5.1.x



After an upgrade from TSM BA CLient 4.1.x to 5.1.x on SUN Solaris 8 my
PrescheduleCMD failed with exiting the BA Client Session.
I don't change anything else.


Here's the the PRE.. CMD Line in the dsm.sys

PreScheduleCmd    " /etc/init.d/gis tsmstop"
PostScheduleCmd   " /etc/init.d/gis tsmstart"

I try to change the quotation marks into single marks. Nothing happens.


Anyone who can help?

I think the masking of the Command Line is the Problem, but why???



Best regards

Markus Klein

CC CompuNet Essen
Systemadministrator