Doug,
I tried this last (on AIX) at 3.7.3.1 and I thought it had aborted;
in fact it hadn't (despite the message implying it was in difficulty).
I repeated and it did run to completion. In the meanwhile I sent the
core dump to IBM (PMR 13528) and they were sure that (a) the dump
showed there was nothing wrong and (b) it was probably a performance
problem on a busy system (a dedicated *SM server ... hmmm). I would
run it again, ignore the message and don't waste your time with a PMR.
It does take some time ...
Regards, Sheelagh
--
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>Date: Fri, 6 Oct 2000 11:17:16 -0700
>From: Doug Thorneycroft <[EMAIL PROTECTED]>
>Subject: Is This a serious problem? DSMSERV UNLOADDB Fails
>To: [EMAIL PROTECTED]
>
>The Admin Guide for TSM V3.7 for WindowsNT (Pg. 425 in the first Edition
>(September 1999))
>actually recommends occasionally unloading and reloading the database.
>We are preparing to move our server to new hardware, so before we put our new
>server into service,
>I decided to play a little and try this out. We've been running ADSM for almost
>4 years, and have
>never tried an unload/reload so I thought I' give it a shot to see if it really
>makes a difference.
>
>It didn't work.
>
>WindowsNT Ver 4, SP6
>TSM Server Ver 3.7.3.0
>
>Have tried the unload several times, each runs for awhile, the displays the
>following messages:
>
>ANR9999D sminit.c(436): SM Failed to Initialize - Time Out.
>ANR9999D mmsshr.c(283): Timed out waiting for session manager initialization.
>
<snipped>
Sheelagh Treweek
Oxford University Computing Services
Email: [EMAIL PROTECTED]
Phone: +44 (0)1865 273205 Fax:-273275
