David, > We did note that TSM v.4.2.3.3 server patch was released on Friday though. > Does anybody know if there are any problems of mysterious or unexplained > crashing that existed within the 4.2.3.2 code set?
On Tuesday 15th Jan (when we went to 4.2.3.3) we had exactly the same problems, which I mentioned here btw. On Monday 27th Jan I wrote (here): >> AIX 4.3.3.0, TSM 4.2.3.2. Since we'r running this level, server crashes >> at least once every day. > > Tivoli wrote me: > >> ======================================================= >> ACTION TAKEN: >> I have reviewed the status update. This trace back appears to >> match IC35420 which is currently scheduled to be included in the >> 4.2.3.4. The current estimate for availability of 4.2.3.3 is end >> of the month. This is only an estimate and is subject to >> revision if necessary. >> ======================================================= > > Last Friday 4.2.3.3 became available: > > ****************************************************************************** > ** > * > * $$4233 Fixes delivered in patch 4.2.3.3 > * > ****************************************************************************** > ** > ....... > IC35420 TSM SERVER CORE DUMPS WHEN EBUSY IS RETURNED AFTER AN ATTEMPT > TO UNSET CONDITION VARIABLE IN PKDESTROYCONDITION() > ....... > > Cheers, > Henk ten Have (asap to TSM 4.2.3.3) Well, 'asap' was the same day. Since we'r running 4.2.3.3 the core dumps are gone. Cheers, Henk (not that I heard anything from Tivoli sofar, but that's another issue)
