> This resulted in that drive to be skipped without *any*
> message, warning or error. If the drive would have been
> in a DOMAIN statement, an error would have been issued.
> There is an APAR for this behaviour, but that is closed
> as a suggestion because IBM finds it too much trouble to
> fix.
This mischaracterizes the situation, as it tells only half the story.
The APAR you refer to is IC35953. The reason it was closed SUG is due to
the extent of the code changes required to fix it; it is not as trivial as
it sounds. Such code changes are beyond the scope of an APAR fix (not
every problem can be fixed within an APAR) -- believe me, we tried.
However, this APAR is still on the "to do" list, and has certainly not
been closed and forgotten.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Jurjen Oskam <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/06/2003 23:54
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: [tsm] Perl TSM daily reporting script.
On Thu, Nov 06, 2003 at 06:37:15PM +0000, Patrick Audley wrote:
> David> Patrick, Looks nice. But I hope you aren't going to rely
> David> on the schedule completion status to tell you whether a
> David> backup has been successful. You really need to mine the
> David> last backup dates of q filespace f=d (or the equiv select).
>
> Ah... no I hadn't realized that :) I'm actually quite new to TSM
> and this is exactly the feedback that I was hoping to get. I've added
> that to the todo list.
Yes, I've been bitten by this. A Windows 2000 client ran the Client
Acceptor under the LocalSystem account. One day, the Windows administrator
changed a drive to exclude LocalSystem from having access. The TSM client
didn't use a DOMAIN statement.
This resulted in that drive to be skipped without *any* message, warning
or
error. If the drive would have been in a DOMAIN statement, an error would
have
been issued.
There is an APAR for this behaviour, but that is closed as a suggestion
because IBM finds it too much trouble to fix.
--
Jurjen Oskam
PGP Key available at http://www.stupendous.org/
