> We are running ADSM on a VM server.
> We received the following messages for the first time this past weekend.

>  ANR9999D SSUTIL(793): LOCK ACQUISITION (SIXLOCK) FAILED FOR SS UNIVERSE LOCK.
>  ANR2033E UPDATE DEVCLASS: COMMAND FAILED - LOCK CONFLICT.
>  ANR9999D SSUTIL(793): LOCK ACQUISITION (SIXLOCK) FAILED FOR SS UNIVERSE LOCK.
>  ANR2033E UPDATE DEVCLASS: COMMAND FAILED - LOCK CONFLICT.
>  ANR9999D SSUTIL(793): LOCK ACQUISITION (SIXLOCK) FAILED FOR SS UNIVERSE LOCK.
>  ANR2033E UPDATE DEVCLASS: COMMAND FAILED - LOCK CONFLICT.
>  ANR9999D SSUTIL(793): LOCK ACQUISITION (SIXLOCK) FAILED FOR SS UNIVERSE LOCK.

> At the time, two things were going on:
> 1) QUERY CONTENT of each tape in our library was running to collect 
> information
> 2) an UPDATE DEVCLASS command was being issued.

> Anybody familiar with this problem?    Does IBM know about it?

The QUERY CONTENT and UPDATE DEVCLASS commands each require that the server
lock on a resource known as the SS UNIVERSE LOCK.  UPDATE DEVCLASS was
unable to lock on this resource because the lock was already held by the
QUERY CONTENT command.  Issue the UPDATE DEVCLASS command at a later time.

Dave Cannon
ADSM Development