Consistent return codes was a Share requirement for years so that production
processes could actually be coded and have a determinable consistent result.
You may not like the implementation, but it is what was asked for.

Paul D. Seay, Jr.
Technical Specialist
Northrop Grumman Information Technology
757-688-8180


-----Original Message-----
From: Richard Sims [mailto:rbs AT BU DOT EDU]
Sent: Monday, January 27, 2003 8:02 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: 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?

Give IBM (formerly Tivoli) some credit here...  Customers have been
clamoring for years for useful return codes, and this is an example of how
they can be useful.  Acting on the return codes is optional, after all.

  Richard Sims, BU