CA IDMS IUA EIUA

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
    nformation real time as it happens, or can=20 daily reports suffice=20 =20 if
    he latter, then certainly the log can be interrogated and all=20 necessary
    nformation can be retrieved=20 if the former - good luck - even if you sat all
    ay executing lockmon=20 you MIGHT see stalls building, but many deadlocks could
    ome and go=20 between two hits of the ENTER key=20 =20 chris=20

    The information transmitted is intended only for the person or entity to which
    t is addressed and may contain CONFIDENTIAL material. If you receive this
    aterial/information in error, please contact the sender and delete or destroy
    he 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?
    "=20
    I believe their CAS is 1.3 and they are on IDMS R 15 (SP 2 - base); they=
    are planning to go to Release 17 in a few months.=20
    I believe their CAS is 1.3 and they are on IDMS R 15 (SP 2 - base); they=
    are planning to go to Release 17 in a few months.=20

    This is an example of the Stall I am trying to deal with (the dbkey appear=
    s to be a P-O in all the examples I=E2=80=99ve seen) =E2=80=93
    ** This is why I was asking whether there was a way to determine which oth=
    er program has a lock on P-O that is preventing this programs from accessi=
    ng the P-O. (w/o Perfmon)
    DC001007 V1 T67037 TASK:CPRO PROG:CPRDUAPQ WAITING FOR LTXNLOCK 0000000=
    8 3C495315
    DC001008 V1 T67037 TXNID:13763354 PROG:CPRDUAPQ SUBSCHEMA:CPRS3POS MODE=
    :S
    DC001003 V1 T67037 TASK:ADS2 PROG:ADSOMAIN(CPRDUAPQ) USER:U61162 STALLE=
    D WAITING FOR LTXNLOCK 00000008 3C495315
    DC027007 V1 T67037 TASK:ADS2 PROG:ADSOMAIN USER:UMC61162 ABENDED WITH=
    CODE D002

    The problem is that the real life is often more complicated than the =E2=
    =80=9Cideal=E2=80=9D examples. =20
    For example from a CA presentation on Deadlocks the following example =E2=
    =80=93 which looks like the second example you provided:=20
    DC001002 T:20583 ADS2 P:DBCRUPD C:DEAD DEADLOCKED ON R:LTXNLOCK 0000000=
    8 0A60730D
    DC001002 T:20470 ADS2 P:DBCRUPD C:DEAD DEADLOCKED ON R:LTXNLOCK 0000000=
    8 0A60730D=20
    These examples show both programs waiting on the SAME DBKEY. =20
    Unfortunately, many of the deadlocks I am seeing seem more complicated (to=
    me anyway).
    Where the messages show different db records, OR an SR1 or SR8, OR a dbk=
    ey and a page number. =20
    A way I have been explaining the two different records - ( if I am wrong=
    on this, I would really appreciate if someone would correct me) =20
    PROG 1 - will get records A, B, C in that order PROG 2 - will get th=
    e records as in the order C,B,A

    So if =
    and=20
    PROG 1 has A and B locked PROG 2 - has=
    C locked
    then when and whe=
    n =20
    PROG 1 tries to get C it will Stall PROG 2 tri=
    es to get B a deadlock occurs
    (I don't have OLQ or DMLO (or DBOL), so I have written a program to look=
    up the record id's for these dbkeys)
    The dbkey 60583A0E is for a record outside of CASSMONA (and I haven=E2=80=
    =99t seen how the ENC01D31 is called from CPRDAP12) =20
    The 323EB300 is an SR1 in the CAS-CPRAUD-AREA
    DC001000 V1 T11 T:000052006 CPRO P:ENC01D31 C:DEAD WAITING ON R:LTX=
    NLOCK 00000008 60583A0E
    DC001001 V1 T11 TXNID:137607556 RUID:137607556 RUNAME:CPRDAP12 SSC:=
    CPRS3POS
    DC001000 V1 T11 T:000052007 CPRO P:CPRDSUB1 C:DEAD WAITING ON R:LTX=
    NLOCK 00000008 323EB300
    DC001001 V1 T11 TXNID:137607557 RUID:137607557 RUNAME:CPRDAP12 SSC:=
    CPRS3POS
    DC001002 V1 T11 T:000052007 CPRO P:CPRDSUB1 C:DEAD DEADLOCKED ON R:=
    LTXNLOCK 00000008 323EB300
    DC203005 V1 T52007 PROGRAM-ID CPRDAP12 TRANSACTION-ID 137607557 HAS=
    BEEN ROLLED OUT!
    This one appears to be a combination of a SR1 and a page (in CAS-CPRAUD-AR=
    EA). =20
    But if I am reading this correctly 2 different tasks/run-units are basical=
    ly trying to work with the same page =E2=80=93haven=E2=80=99t look at this=
    one enough to know if there is anything I can do about this.
    DC001000 V1 T11 T:000027789 CPRO P:CPRDSUB1 C:DEAD WAITING ON R:LTX=
    NLOCK 00000008 32341F00
    DC001001 V1 T11 TXNID:137570346 RUID:137570346 RUNAME:CPRDAP12 SSC:=
    CPRS3POS
    DC001000 V1 T11 T:000027790 CPRO P:CPRDSUB1 C:DEAD WAITING ON R:LTX=
    NLOCK 00002008 0032341F
    DC001001 V1 T11 TXNID:137570347 RUID:137570347 RUNAME:CPRDAP12 SSC:=
    CPRS3POS
    DC001002 V1 T11 T:000027790 CPRO P:CPRDSUB1 C:DEAD DEADLOCKED ON R:=
    LTXNLOCK 00002008 0032341F
    DC203005 V1 T27790 PROGRAM-ID CPRDAP12 TRANSACTION-ID 137570347 HAS=
    BEEN ROLLED OUT!=20