ADSM-L

Re: MOVE DRMEDIA locked up our server

1997-03-13 12:19:25
Subject: Re: MOVE DRMEDIA locked up our server
From: "Prather, Wanda" <PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU>
Date: Thu, 13 Mar 1997 12:19:25 -0500
Thanks for the info -
Please clarify, do you mean it will be available for PTF 12, or some
future release of the server?

>----------
>From:  Greg Van Hise[SMTP:vanhise AT VNET.IBM DOT COM]
>Sent:  Wednesday, March 12, 1997 11:10 AM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       MOVE DRMEDIA locked up our server
>
>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>