You are probably seeing APAR IC35203. This is fixed in client version
5.1.6.0 and up.

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.




Mike Angels <sysprogm AT VIRGILIO DOT IT>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/25/2003 14:57
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        R: POSTSCHEDULECMD failed, but event was
successful


Hi Bill,

I saw the same behavior on schedules of type=command.
I launched a backup script and even if the script exits with a return code
of 8 (exit 8) the event is showed as COMPLETED instead
of FAILED.
The current versions are:
  TSM Server 5.1.6.0 on AIX 4.3.3
  TSM Client 5.1 on AIX 4.3.3

I think that with the version 4 of TSM the event used to be considered
FAILED when the launched command exited with a return code
of 8.

Regards,

Mike Angels


-----Messaggio originale-----
Da:     Bill Boyer [SMTP:bill.boyer AT VERIZON DOT NET]
Inviato:        giovedi 25 settembre 2003 16.33
A:      ADSM-L AT VM.MARIST DOT EDU
Oggetto:        POSTSCHEDULECMD failed, but event was successful

TSM Client 5.1.6.7 on Windows2000 SP4
TSM Server 5.1.7.1 on AIX 4.3.3

I have coded a PRE and POSTSCHEDULCMD that stops some Oracle services,
backups up and then restarts the services. My POSTSCHEDULECMD keeps track
of
the highest return code and then EXIT %MAXCC%. Testing with this today, my
POSTSCHEDULECMD did and EXIT 2, and you see that in the DSMSCHED.LOG file.
The problem is that the event itself didn't Fail.

Executing Operating System command or script:
   c:\progra~1\tivoli\tsm\scripts\orastart.cmd
09/24/2003 22:17:10 Finished command.  Return code is: 2
09/24/2003 22:17:10 ANS1903W The POSTCHEDULECMD command failed.
09/24/2003 22:17:10 Scheduled event '@166' completed successfully.
09/24/2003 22:17:10 Sending results for scheduled event '@166'.
09/24/2003 22:17:10 Results sent to server for scheduled event '@166'.


According to the TSM Client doc:

For Windows NT, 2000, XP systems: If the postschedulecmd command does not
complete with return code 0, the client will report that the scheduled
event
completed with return code 8 (unless the scheduled operation encounters a
more severe error yielding a higher return code).

Why didn't my schedule event finish with Fail?? Anyone seen this behavior?


Bill Boyer
"Some days you are the bug, some days you are the windshield." - ??