> Do you see any reason why TSM V5.2.3 would not be safe to install? No, none at all.
See an older posting of mine at http://msgs.adsm.org/cgi-bin/get/adsm0301/1009.html for info on what the different numbers in our version numbering scheme mean. 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. "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 08/03/2004 09:05:21: > I'm back from class and I've installed TSM V5.2.3 on another 2003 > Windows server and the results have been positive. I've done some test > restores on a 2000 server that I installed this same version on with > good results. > > The Unix admins don't really want me to install this TSM V5.2.3 since > they would prefer what they call a maintenance level, like TSM V5.2.3.X. > Do you see any reason why TSM V5.2.3 would not be safe to install? > > Melinda Cooper > Senior Information Center Analyst > Work - 425.783.4467 > Pager - 425.438.5981 > > > -----Original Message----- > From: Andrew Raibeck [mailto:[EMAIL PROTECTED] > Sent: Friday, July 23, 2004 1:38 PM > To: [EMAIL PROTECTED] > Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003 > > Just to close the loop with the rest of this list on this: > > The doc that Melinda and Leif sent me both showed "invalid verb > received" > messages, which suggested IC40841. The current APAR description isn't an > exact match, but from what I knew about the fix for that APAR, it seemed > worth a shot. > > There were two facets of this APAR to fix. The first facet, which is the > pertinent one here, is fixed in 5.2.3.0 (even if the README file doesn't > mention IC40841). The second facet (regarding a "successful backup" > message even if the file system processing stopped prematurely), will be > fixed in an upcoming interim fix, at which time IC40841 will be shown as > "fixed". > > It is my understanding that 5.2.3.0 resolved the problem for Leif (at > least initial testing looked promising). If and when Melinda reads this > message, perhaps she can indicate her current status as well. But I > think > this will resolve her problem, too. > > So for anyone who experiences similar symptoms to those discussed > earlier > in this thread: try 5.2.3.0. > > 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.
