The APAR was opened on November 10. I don't control the web site, but I would imagine that there is some delay between the time the APAR is opened and when it gets propagated to the external web site. What that delay is, I don't know. But my original post on the thread included the full text of the APAR.
If your TSM server is running under a heavy load with lots of lock contention, then the risk of the LOCKCYCLE02 crash is pretty high. If you are willing to risk and tolerate the crash, then you can stay at 5.2.3.4. Just be certain that you are backing up your db regularly, and of course, db/log mirroring and log roll forward mode is always recommended. Otherwise go back to 5.2.3.3, then when 5.2.3.5 is available, go there. 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 11/17/2004 08:29:43: > I've been searching IBM's Web for IC43445... And no hits, we just updated two > AIX TSM servers to 5.2.3.4... Are we screwed? > > Thanks > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of > Andrew Raibeck > Sent: Wednesday, November 17, 2004 8:49 AM > To: [EMAIL PROTECTED] > Subject: Re: TSM server 5.2.3.4 removed from ftp site > > > > Would you expect 5.2.3.5 to have a fix for IC43445? > > Yes! > > 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.
