I lived with this problem for months, in one way or another from 3.1.2.20
thru 3.1.2.50.  Here it was caused by an admin using the GUI to to a q node
or q fi.  At that point, expiration and all subsequent sessions would
hang.  The only cure was to restart ADSM.  The only safeguard was to
threaten bodily harm to careless GUI users.  The problem is mostly fixed in
3.1.2.50 and I haven't seen it at all in 3.1.2.55.


At 10:57 AM 4/14/2000 +0100, you wrote:

AIX 4.3 server, ADSM 3.1.2.40

Yesterday, an expiration process was started off. Today, I find it is
still running ( without having made any further progress ) and after I try
to cancel this process, it just says :
'     219 Expiration           ANR0819I Cancel in progress'
This doesn't look good.
Anyone else seen this happening ?
Any suggestions on how to fix it ?

Steven Bridge ( Systems group - UCL EISD Information Systems )

Fred Johanson
System Administrator, ADSM
S.E.A.
University of Chicago
773-702-8464