We had problem to identify application process locking a record.

Before any program change, is there any VMS utility show the process
locking the record ?

Also how to identify the process locking the record through ANALYZE
/SYSTEM ?

Thanks for any input in advance,

Terence.

AMDS is nice to display interprocess lock

Terence Wong wrote:
> We had problem to identify application process locking a record.
> 
> Before any program change, is there any VMS utility show the process
> locking the record ?
> 
> Also how to identify the process locking the record through ANALYZE
> /SYSTEM ?
> 
> Thanks for any input in advance,
> 
> Terence.

Hoff Hoffman wrote:
>   Me?  I'd install Avaibility Manager or AMDS, and be done with it.

Is there a solution for VAX ?

In article <87af9e83.0503010744.618ca5b8@posting.google.com>, tlywong@gmail.com (Terence Wong) writes:
:We had problem to identify application process locking a record.

  OpenVMS version?

:Before any program change, is there any VMS utility show the process
:locking the record ?

  AMDS or its more current version, Availability Manager, make this 
  easy -- current versions are licensed with OpenVMS, are easily
  installed, and make finding a blocking lock blindingly easy.

  When I have this situation, I tend to code the applications to play
  more nicely with the record locks, where the application detects a
  long hold time for itself, and backs off the lock.  Where I do not
  need the record lock, I do not acquire it.  Both are obvious, of
  course, and are certainly not the only way to go after what is
  usually a coding or design problem within the application -- I have
  had my share of these errors over the years; errors I've either
  committed, or that I have found and resolved.

:Also how to identify the process locking the record through ANALYZE
:/SYSTEM ?

  Current SDA versions are better at this.  Older releases are somewhat
  of an "adventure" when tracing the lock trees around a cluster.  On
  the current versions, SHOW LOCK is pretty easy to use and to follow
  around.  On older releases, again, it'll be more of an "adventure" --
  you will want to look at the lock resource name documentation, if you
  take this SDA tactic, too -- you'll need to know what the RMS lock 
  names look like, and how the locks are structured.  IIRC, this is in
  the internals and data structures manual.

  Me?  I'd install Avaibility Manager or AMDS, and be done with it.
  Look for which process is holding a lock that is blocking others,
  and work out from there -- the IDSM can still be useful here, too,
  though simpler cluster configurations and stand-along can potentially
  be easy to resolve without knowledge of the specific resource names.


 ---------------------------- #include <rtfaq.h> -----------------------------
    For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq
 --------------------------- pure personal opinion ---------------------------
        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com

JF Mezei wrote:
> Hoff Hoffman wrote:
> 
>>  Me?  I'd install Avaibility Manager or AMDS, and be done with it.
> 
> 
> Is there a solution for VAX ?

I submitted RMS_LOCKS to freeware.  It's on the freeware distribution 
prior to the current one, V6 possibly.  Also downloadable from the HP 
web site I believe.

As I've mentioned before, much could be done on the user interface side. 
  It was something that fell out of a project I was working on, so not 
much time was spent on it.

Since I don't have a cluster, it wasn't tested in that environment.

Dave

A much similar question is being discussed in the OpenVMS ITRC Forum:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=824830

Over there two alternative programs, both called rms_tools.c where
offered up.
Dave's solution is in done Basic. Cool!

:-).

Hein.

Hein wrote:
> 
> A much similar question is being discussed in the OpenVMS ITRC Forum:
> 
> http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=824830

For those who keep javascript disabled, the rms_tools.c from Mr Hein van
den Heuvel
is at:

> http://forums1.itrc.hp.com/service/forums/getattachment.do?attachmentId=213571&ext=.c

JF Mezei wrote:
> Hein wrote:
> 
>>A much similar question is being discussed in the OpenVMS ITRC Forum:
>>
>>http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=824830
> 
> 
> For those who keep javascript disabled, the rms_tools.c from Mr Hein van
> den Heuvel
> is at:
> 
> 
>>http://forums1.itrc.hp.com/service/forums/getattachment.do?attachmentId=213571&ext=.c

David Sneldon (probably misspelled, my appologies) also has/had a 
utility, in C I believe.  I think his user interface allowed for input 
of a filespec.  I never saw it, just remember the discussion from 
several years ago.

Dave

JF Mezei wrote:
> Hoff Hoffman wrote:
> >   Me?  I'd install Avaibility Manager or AMDS, and be done with it.
>
> Is there a solution for VAX ?
This one worked for me (vax only, I don't think it made it to alpha)
http://www.decus.org/encompass/libcatalog/description_html/v00484.html
Phil