The Scheduled event is the backup, which was successful.
The Pre-Post Schedule calls a script that runs outside the backup.
The only time I have seen a failed TSM event due to failure of a Post schedule
command was when the post schedule command hung due to a problem
unrelated to TSM. The scheduled event was waiting for it's return code to
continued,
and finally reached it's commtimeout, which caused a report of failed.
On Thursday, September 13, 2001 9:14 AM, Rushforth, Tim
[SMTP:[EMAIL PROTECTED]] wrote:
> Does anyone know what the status of a scheduled event should be if the Pre
> or Post command fails with a non zero return code?
>
> On tests with the 4.2.0 and 4.12.12 win32 clients, the scheduled event
> completes successfully even if the Prescheduled command fails with a return
> code of 1.
>
> I'm wondering if this is working as designed or if the client should show
> the event as failing if a pre or post command fails.
>
>
> Thanks,
>
> Tim Rushforth
> City of Winnipeg
