ca.portal.admin

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

Discussion created by ca.portal.admin on Mar 9, 2010
Maybe I'm reading this wrong but I don't think that PMRM statistics are
necessary to achieve what was desired. I thought the OP wanted to know
which program was holding a record. We trap the logs and write reports on
what programs are stalling or deadlocking on what records. For example from
the CV log:

DC001000 V9 T12 T:000238126 CPSBP419 P:CPSBP419 C:DEAD WAITING ON R:LTXNLOCK
000A0008 58C48109

Then you have to break out the codes following the LTXNLOCK as follows:
000A - page group
00 - indicates that a dbkey follows
08 - the dbkey's radix
58C48109 - is the dbkey in hex

Then, taking the 58C48109 - you can translate back to binary, then do a
generic Find to get the record name. The above assumes that you can
determine the subschema name from the program name (which we can). Of
course, I am oversimplifying things a bit, but it is doable.

But, the above should plant the germ of an idea in the OP's mind for an
alternative to PMRM if all that is desired is the offending program for
deadlocks and stalls.

Outcomes