I've seen this so many times it's becoming routine although our server is
at 2.1.0.9 on an AIX playform. When I reported the problem to ADSM, the
only thing I got back was to go to ptf12. I decided not to push the issue
since we will be going to ptf13 this coming weekend. Then if the problem
re-occurs, I will be escalating the issue pretty quickly.

At 10:24 AM 8/4/97 -0500, you wrote:
>We are running ADSM V2R1Level 0.10/0.10 on MVS platform. Recently, We
>have received the following ADSM mesages regarding ADSM database dead
>lock.
>
>IGD104I TSDP.ADSM.SERV1.HIST1                        RETAINED,
>DDNAME=SYS0021
>ANR5220I Deleting CARTRIDGE 792987 from Storage Pool TAPEMIGRATIONPOOL.
>
>ANR1341I Scratch volume 792987 has been deleted from storage pool
>
>TAPEMIGRATIONPOOL.
>
>ANR0390W A server database deadlock situation has been encountered: lock
>
>request for transaction 0:75661734 will be denied to resolve the
>deadlock.
>ANR9999D ICUTIL(1369): Lock acquisition (sLock) failed for
>icvhVolumeType 5.
>ANR4513E A database lock conflict was encountered in processing
>sequential
>volume history information.
>
>ANR4510E Server could not write sequential volume history information to
>
>'TSDP.ADSM.SERV1.HIST1'.
>
>ANR5220I Deleting CARTRIDGE 758460 from Storage Pool TAPEMIGRATIONPOOL.
>
>ANR1341I Scratch volume 758460 has been deleted from storage pool
>
>TAPEMIGRATIONPOOL
>
>I searched the IBM info and could not find any current APAR apply to
>this situation. Any one of you ever seen this with your ADSM server?
>
>Thanks..........Khiem
>
>