ADSM-L

MOVE DRMEDIA locked up our server

1997-03-12 11:10:14
Subject: MOVE DRMEDIA locked up our server
From: Greg Van Hise <vanhise AT VNET.IBM DOT COM>
Date: Wed, 12 Mar 1997 08:10:14 PST
Scotty,

Please refer to APAR IC16433 which will be available with
the next server PTF.  This APAR removes a lockout exposure
that exists with MOVE DRMEDIA.

My guess is the transaction waiting for a lock in your case
is associated with one of the following commands:
  - define/update/delete stgpool
  - define/update/delete devclass
  - vary on/off
  - update volhistory
If this is true, the bypass until the APAR is available
is to avoid executing the above commands at the same time
as MOVE DRMEDIA.

Hope this helps, Greg

> This afternoon we were moving some DRM  volumes from our 3494, using a
> procedure we've successfully used before, and managed to lock up parts
> of the ADSM server.

> Lock hash table contents (slots=256):
> slot -> 0:
> LockDesc: Type=34000, NameSpace=0, SummMode=sLock, Key=''
>   Holder: Tid=0:83467872, Mode=sLock
>   Holder: Tid=0:83459850, Mode=sLock
>   Waiter: Tid=0:83467910, Mode=sixLock
>   Waiter: Tid=0:83467919, Mode=sLock
>   Waiter: Tid=0:83468124, Mode=sixLock
>   Waiter: Tid=0:83468904, Mode=sLock
>   Waiter: Tid=0:83469119, Mode=sLock
>   Waiter: Tid=0:83469841, Mode=sixLock
<Prev in Thread] Current Thread [Next in Thread>