ADSM-L

Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server

2002-08-15 15:20:34
Subject: Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server
From: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 15 Aug 2002 15:15:19 -0400
That was my question, what will it do?  What are the plus and
minuses of changing it?  What resources is it for?

Don't have much log pin problem on this server.

David Longo

>>> xjolliff AT TI DOT COM 08/15/02 09:42AM >>>
Just be aware of what lengthening the RESOURCETIMEOUT will do, especially if
you are susceptible to "logpinned" conditions due to slow, long-running
sessions.




-----Original Message-----
From: David Longo [mailto:David.Longo AT HEALTH-FIRST DOT ORG] 
Sent: Thursday, August 15, 2002 8:17 AM
To: ADSM-L AT VM.MARIST DOT EDU 
Subject: Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server


Richard,
I have 4.2.1.10 server.  Checked and my RESOURCETIMEOUT  is
set to 10.  Looked at manuals and see this is a new option with 4.2.
There is only a small paragraph about this.  What RESOURCES is this
talking about and what are the implications of changing?

It's probably not tape mounts as I can have a process waiting on a tape
that's being used by another process for well over 10 minutes. (No problem
with that, just know it doesn't apply to tape mounts.)

David Longo

>>> richard.menides AT SPCORP DOT COM 08/15/02 08:47AM >>>
I had the same problem after upgrading from 3.74 tp 5.11 on AIX 4.3. The fix
is to change the resource time out in the TSM server's dsmserv.opt file to
60 the default is 10. Hope this helps you out.

Senior TSM consultant

Richard Menides

-----Original Message-----
From: Gerhard Rentschler [mailto:g.rentschler AT RUS.UNI-STUTTGART DOT DE] 
Sent: Thursday, August 15, 2002 7:38 AM
To: ADSM-L AT VM.MARIST DOT EDU 
Subject: Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server


Hello,
this is obviously a known problem. See the discussion a few days earlier
with subject " Expiration problem with TSM 5.1.1.1 on AIX 4.3.3".
I opened PMR 88563,070,724 on July 31st. First I was advised to upgrade to
5.1.1.2. This didn't change anything. Then I had to supply diagnostic
information. According to the web interface to Tivoli problem management the
problem was closed on August 6th without any further information. I haven't
got any new information since  this day.
Best regards
Gerhard

---
Gerhard Rentschler            email:g.rentschler AT rus.uni-stuttgart DOT de 
Regional Computing Center     tel.   ++49/711/685 5806
University of Stuttgart       fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> MC Matt Cooper (2838)
> Sent: Thursday, August 15, 2002 1:22 PM
> To: ADSM-L AT VM.MARIST DOT EDU 
> Subject: Re: ANR9999 message Lock acquisition - TSM 4.2.1.15 server
>
>
> 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-----
> Fren: 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 
> Dmne: 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

***************************************************************
 This message and any attachments is solely for the intended recipient. If
you are not the intended recipient, disclosure, copying, use, or
distribution of the information included in this message is prohibited --
please immediately and permanently delete this message.


"MMS <health-first.org>" made the following
 annotations on 08/15/2002 09:17:52 AM
----------------------------------------------------------------------------
--
This message is for the named person's use only.  It may contain
confidential, proprietary, or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.  If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify the
sender.  You must not, directly or indirectly, use, disclose, distribute,
print, or copy any part of this message if you are not the intended
recipient.  Health First reserves the right to monitor all e-mail
communications through its networks.  Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where the
message states such views or opinions are on behalf of a particular entity;
and (2) the sender is authorized by the entity to give such views or
opinions.

============================================================================
==


"MMS <health-first.org>" made the following
 annotations on 08/15/2002 03:16:39 PM
------------------------------------------------------------------------------
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or 
privilege is waived or lost by any mistransmission.  If you receive this 
message in error, please immediately delete it and all copies of it from your 
system, destroy any hard copies of it, and notify the sender.  You must not, 
directly or indirectly, use, disclose, distribute, print, or copy any part of 
this message if you are not the intended recipient.  Health First reserves the 
right to monitor all e-mail communications through its networks.  Any views or 
opinions expressed in this message are solely those of the individual sender, 
except (1) where the message states such views or opinions are on behalf of a 
particular entity;  and (2) the sender is authorized by the entity to give such 
views or opinions.

==============================================================================