> First of all I do not know Andy's position at Tivoli.
> And read what is written in the README:
> "This is not officially supported by IBM, but IBM support people
> do participate in the discussions, along with other users."
> So IMHO here Andy is just a colleague. More skilled in ADSM/TSM,
> closer to the developers, but just a colleague.
I am a developer who works on the TSM client (Windows B/A client
and ODBC driver).
The statements in the README file are there mainly to avoid confusion
as to what ADSM-L is and what it is not. Otherwise a user new to the
group might be led to believe that ADSM-L is the place to get support
from IBM. The README statement is intended to make it clear that this
is not the *official* support channel. Our participation, like that of
anyone else, is voluntary. But that does not absolve us of our
obligation to post in a responsible manner when we do participate.
With regard to the APAR in question, I intercepted the APAR when it
came to development and changed the description from a documentation
error (as it was originally opened) to a code error (which it properly
is). So I am fairly close enough to the problem to be able to speak to
it knowledgeably. The problem has since been fixed, and we are
planning a patch to include a fix for this problem. Currently we are
targeting the patch for sometime between now and the end of October,
although that is subject to change.
> If something shows up on the web-site or in docs on media that would
> be official.
The information stating that the problem is fixed will be in the
README file that accompanies the fixing client code. Until then, if
you require something more official, please open up a problem record
with IBM support (your official channel), and ask to be placed on the
"interested parties" list for APAR IC31844. The support folks will do
this for you, and notify you when a fix is available.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
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.
Zlatko Krastev/ACIT <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10/22/2001 07:28
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: FW: v4.2.1 TSM Clients
First of all I do not know Andy's position at Tivoli.
And read what is written in the README:
"This is not officially supported by IBM, but IBM support people
do participate in the discussions, along with other users."
So IMHO here Andy is just a colleague. More skilled in ADSM/TSM, closer to
the developers, but just a colleague.
If something shows up on the web-site or in docs on media that would be
official.
Zlatko Krastev
IT Consultant
"Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> on 19.10.2001 17:57:48
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: FW: v4.2.1 TSM Clients
Andrew Raibeck answered "I am almost certain that this change in behavior
is
not deliberate. The APAR is going to be handled as a code defect"
Isn't that you'r Tivoli official answer?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 19, 2001 12:29
To: [EMAIL PROTECTED]
Subject: Re: FW: v4.2.1 TSM Clients
This was already discussed in the list. Look for the thread "Windows
client
behavior change at 4.2.1.0" and answer of Andrew Raibeck from 9.10.2001.
But it is possible that Andy and this Bob are just having different
PERSONAL opinions. We still do not have answer from any Tivoli official,
do
we?
Zlatko Krastev
IT Consultant
"Subash, Chandra" <[EMAIL PROTECTED]> on 18.10.2001 07:41:31
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: FW: v4.2.1 TSM Clients
i HAVE GOT THIS EMAIL FROM ONE OF MY FRIENDS. GUYS WHAT DO YOU THINK IS IT
TRUE ?
Hi Guys
According to Tivoli Support they have made an alteration to way client
v4.2.1 reports Result code 4 to the server. Earlier version clients would
allow for a certain number of files to fail during the backup and still
report to the server that the Schedule was successful. However version
4.2.1
has been altered so that a result code of failed will be reported to the
server even if 1 file fails during a backup.
ntcmachine had been failing on some WINNT system files which I have added
exceptions for under direction of Tivoli support and now backups of this
machine seem to be successful.
Bob from Tivoli suggested that if we are worried about seeing failed
result
codes on the daily report that there may be a way to generate a report
listing statistics of how many files or how much data had been backed up
from each machine to provide a more accurate picture as to whether the
backups were successful.
**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee,
you
are notified that no part of the e-mail or any attachment may be
disclosed,
copied or distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by
return e-mail, and delete this message. Koninklijke Luchtvaart
Maatschappij
NV (KLM), its subsidiaries and/or its employees shall not be liable for
the
incorrect or incomplete transmission of this e-mail or any attachments,
nor
responsible for any delay in receipt.
**********************************************************************
