Andy,
Glad you're on this discussion. I work for IBM and my colleagues and I were
told months ago from level2 TSM support that reporting a backup as failed (in
the TSM activity) as a result of an rc=4 (files open or not found) was a "bug"
in 4.2.x and would be fixed.

Andrew Raibeck wrote:

> You don't qualify what you mean by "failed", but if you simply mean that
> the return code from dsmc was 4, then this is a new 5.1 feature, not a
> bug. See the "Automating Tasks" chapter in the 5.1 client manual for
> information on return codes from the command line client and their
> meanings. If you have any other questions on this, let me know.
>
> 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.eyebm DOT com (change eye to i to reply)
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> Thomas Denier <Thomas.Denier AT MAIL.TJU DOT EDU>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 01/27/2003 14:47
> Please respond to "ADSM: Dist Stor Manager"
>
>         To:     ADSM-L AT VM.MARIST DOT EDU
>         cc:
>         Subject:        Backup fails when files fail
>
> We have an HP-UX TSM client running 5.1.1.0 code. It connects to a 4.2.3.3
> server running under OS/390. A 'dsmc incremental' command on the HP-UX
> system failed with an exit status of 4, apparently because three files
> failed with ANS1228E and ANS4045E (file not found) messages. I remember
> reading about this kind of behavior in Version 4 clients. Has Tivoli
> managed to resurrect this bug in Version 5?