Good summary, Richard, but just to clarify:

If POSTSCHEDULECMD fails, then the schedule will be considered to have
completed successfully with RC 8, assuming the scheduled operation did not
complete with a higher return code. POSTSCHEDULECMD results have no
bearing on whether the file space's last backup times are updated.

If PRESCHEDULECMD fails (has a nonzero return code), then the scheduled
operation does not even run (as you said, the event is flagged as failed).

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.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-06-10
06:43:51:

> On Jun 10, 2005, at 5:23 AM, Matthew Large wrote:
>
> > We run Image backups at the weekend and normal incrementals in the
> > week,
> > and for some time now the filespaces involved in the backup have not
> > updated their last backup/access date/time....
> >
>
> The timestamp will be updated only for unqualified Incremental
> backups which complete without error. A nuance is that as of TSM 5.1:
> If the command specified by the PRESchedulecmd or POSTSchedulecmd
> option ends with a nonzero return code, TSM will consider the command
> to have failed.
>
>    Richard Sims