CA IDMS

Re:Re: [IDMSVENDOR-L] Access to Lock Data Used in PMRM?

  • 1.  Re:Re: [IDMSVENDOR-L] Access to Lock Data Used in PMRM?

    Posted 03-09-2010 02:19 PM
    hen perhaps the real question becomes:=20 =20 does Ms Kline need this
    formation real time as it happens, or can=20 daily reports suffice=20 =20
    the latter, then certainly the log can be interrogated and all=20
    cessary information can be retrieved=20 if the former - good luck - even
    you sat all day executing lockmon=20 you MIGHT see stalls building, but
    ny deadlocks could come and go=20 between two hits of the ENTER key=20 =20
    ris=20
    The information transmitted is intended only for the person or entity to
    ich it is addressed and may contain CONFIDENTIAL material. If you receive
    is material/information in error, please contact the sender and delete or
    stroy the material/information.
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: Access to Lock Data Used in PMRM?
    "The best you can do is pray that it is not a keep longterm that causes the
    problem.

    Have you used LOCKMON when the problem happens. W LTERM should show the
    long term locks.
    A RELEASE ALL will let it go, but you till need to find out where it
    happens and when, in order to issue the release at the correct time.

    Since a longterm lock is held by the lterm, it can be very difficult to
    find out what program it comes from.
    An implicit lock, or a keep (without longterm) only lasts for the length of
    the run-unit so those are much easier to find, if they cause trouble you
    will be able to see the executing program and the many locks held by that
    program.

    The keep longterm exclusive is especially problematic as it is usually used
    for protecting data from being updated in between run-units, otherwise an
    obtain keep exclusive would be just as good.
    If something unexpected happens between the two run-units and the user
    starts on something completely different, the release may not happen, or at
    least not for a while.

    Tommy Petersen
    110 Cokesbury Rd
    Room 542H
    Lebanon, NJ 08833

    Phone:
    Internal 200 - 3699
    External (908) 236-3699
    Fax: (908) 236-3692




    Cynthia Kline
    <cakask@AOL.COM>
    Sent by: IDMS To
    Public Discussion IDMS-L@LISTSERV.IUASSN.COM
    Forum cc
    <IDMS-L@LISTSERV.
    IUASSN.COM> Subject
    Re: [IDMSVENDOR-L] Access to Lock
    Data Used in PMRM?
    03/11/2010 01:29
    PM


    Please respond to
    IDMS Public
    Discussion Forum
    <IDMS-L@LISTSERV.
    IUASSN.COM>






    I don't know - as I wrote it is in TSTLCK95 - and this looks like rather
    old code (don't know whether it was custom?)
    (and in something like ADDPOITM, then I really don't ""get it"")

    Question - how long do locks hold?

    Meaning - like an implicit lock vs an explicit lock vs a KEEP
    LONGTERM ( and perhaps a KEEP LONGTERM xx UPDGRADE EXCLUSIVE'




    If the KEEP LONGTERM UPGRADE EXCLUSIVE is the problem - should a RELEASE
    ALL make it let go?

    (Because it appears the locks involved in the stalls seem awfully
    persistent.)

    Thanks!!
    Cindy Kline
    ASK
    440-829-9275