We have been seeing the server hangs, or something very like them,
as described by Jim (4140) and Henk (4216) - since July at 4140.
We have had a PMR open since then and have not made any progress
towards a resolution.  The latest suggestion I have had is to
upgrade to either 4144 or (wait for it) 4212 to fix the problem.
This latest suggestion was this week, and after all the problems
have been aired with 421x on this list.  The finger is being
pointed at 'library sharing' code (which we do not use and have
library sharing option set to no).

I would urge anyone experiencing server problems that require a
restart to resolve, to report the problems to IBM/Tivoli. They
may not get the focus required to diagnose and fix otherwise.

Thanks to all for the information about 421x.

I opened a PMR about the licensing problems still persisting at 4216
and was told today that it will be fixed at 4127, which is being built,
and that it had been accidentally omitted from 4216.

Regards, Sheelagh
--
Sheelagh Treweek
Sheelagh Treweek
Oxford University Computing Services
Email: sheelagh.treweek AT oucs.ox.ac DOT uk
Phone: +44 (0)1865 273205 Fax:-273275



X-Accept-Language: en
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Date: Wed, 31 Oct 2001 09:44:24 -0500
From: Jim Kirkman <jmk AT EMAIL.UNC DOT EDU>
Subject: Re: TSM 4.2.1.6 AIX 4.3.3.0
To: ADSM-L AT VM.MARIST DOT EDU

We have seen this exact same scenario with 4.1.4 on OS390 2.10. Backups, q proc,
and expiration working, DB backup and dr move cmds invoked but never ran, admin
sessions 'frozen' and processes cancelling but never going away. It's only
happened once, but then we've only been at 4.1.4 for about a month. I ended up
'bouncing' the server after expiration ended.

FWIW

Henk ten Have wrote:

>    I wrote:
>
> > If any bad comes out of this, just let me know too.....
>
>    Well, it didn't take 24 hours. This morning my server was "frozen". Simple
>    queries like q mo, q vol, q libvol or q dr never give any result.
>    q se (which worked) showed a lot of "frozen" admin session, wait time
>    zero, but never ending.
>    q proc (which also worked) showed backup stg processes which didn't
>    do anything for a long time (probably finished, but never ending).
>    The funny thing was that backup's still worked (backup's to diskpools).
>    So finally I had to halt the server and did a restart.
>    The activitylog and the dsmserv.err didn't show anything weird.
>
>    Cheers,
>    Henk (still not amused)

--
Jim Kirkman
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884