Uh oh,   I just went from 4.1.5  to 5.1.1 Monday, z/OS 1.1.   This morning I
am looking at my EXPIRATION process was hung and a backup of local tape to
the copytape is hung and it all started with very similar message..
Matt
ANR0538I A resource waiter has been aborted.

ANR0538I A resource waiter has been aborted.

ANR1224E BACKUP STGPOOL: Process 23 terminated - lock conflict.

ANR0538I A resource waiter has been aborted.

ANR0538I A resource waiter has been aborted.

ANR9999D IMFS(3566): ThreadId<656> Lock conflict error in obtaining sLock
for   
ANR9999D node 499, filespace 35

ANR0986I Process 23 for BACKUP STORAGE POOL running in the BACKGROUND
processed 
ANR0986I 3603 items for a total of 970,174,464 bytes with a completion state
of 
ANR0986I FAILURE at 06:06:44.

ANR9999D IMFS(3566): ThreadId<662> Lock conflict error in obtaining sLock
for   
ANR9999D node 499, filespace 35


-----Original Message-----
From: Nilsson Niklas [mailto:ninil AT WMDATA DOT COM]
Sent: Thursday, August 15, 2002 2:25 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: SV: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

Good morning...

Im testing 4.2.2.9 (testfix) on OS/390 but still I've got these locks...
Going to take it up with support.

Regards Niklas

-----Ursprungligt meddelande-----
Från: Brian L. Nick [mailto:BRIAN.NICK AT PHOENIXWM DOT COM]
Skickat: den 14 augusti 2002 16:16
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

Good morning,

 We are running TSM 4.2.1.15 on OS/390 2.10 and are having several issues.
One of these is poor performance since upgrading from 4.2.2.0 to 4.2.1.15.
Also we are receiving the following error message after issuing an update
storage pool command:


ANR9999D SSUTIL(943): ThreadId<15401> Lock acquisition (ixLock) failed for
SS
universe lock.
ANR2753I (DAILY_APL_MIGRATION_AVOID):ANR2033E UPDATE STGPOOL:
ANR2753I (DAILY_APL_MIGRATION_AVOID):Command failed - lock conflict.

 This condition seems to occur when we are in a heavy backup period, which
since upgrading to 4.2.1.15 is very often. I need to test 4.2.2.0 before
upgrading to that release, we applied the 4.2.1.15 fix level at the
recommendation of Tivoli even thought 4.2.2.0 was available.  Is anyone
running 4.2.2.0 on OS/390 2.10 and if so have you run into any gotcha's?

 Thanks for  any input.

 - Brian



Brian L. Nick
Systems Technician - Storage Solutions
The Phoenix Companies Inc.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  Brian.Nick AT phoenixwm DOT com
PHONE:   (860)403-2281