It has already been acknowledged that this is indeed a program bug. The
APAR, IC31844, was erroneously opened as a documentation problem (i.e. the
change in behavior was not documented). This is not the case, though, and
the problem has since been changed do "program error" vs. "doc error".

The problem is fixed in the latest patch, 4.2.1.15, now available on the
usual FTP site.

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.





Steven P Roder <tkssteve AT REXX.ACSU.BUFFALO DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/26/2001 10:02
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: FW: v4.2.1 TSM Clients



> Guys
>
> Is there a patch for this issue ?

Yes, is there?  I read through that APAR, and one cannot conceivably visit
hundreds, possibly thousands of clients, and exclude all files that may
fail.  This behavior, in my opinion, is a bug.  If I upgraded to this
code, close to 100% of my client schedules would show up as failed.

This may be a nice feature to add, but not as a failed schedule.  Perhaps
some other completion status could be set, or inquired (via q event).
Calling the backup a failure does not seem correct, IMHO.