Hi,

Seen something like it and started to use pre- and postnschedulecmd for a
client because of it. At this client it looked like it took to long to stop
and start the services (non oracle).

Regard,

Karel

-----Oorspronkelijk bericht-----
Van: Bill Boyer [mailto:bill.boyer AT VERIZON DOT NET]
Verzonden: donderdag 25 september 2003 16:33
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: 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." - ??