ca.portal.admin

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

Discussion created by ca.portal.admin on Mar 10, 2010
Cynthia,
What release are you running? R17 gives you lots of information on the log
bout these types of abends. I thought that we had these messages at R16 as
ell, but don't remember for sure.
In the first example below (a deadlock), program D472OJ06 abended due to a lock
eld by program D472OJ04.
In the second example (a stall), program D479HC01 abended due to a lock held by
rogram D479HG01.
The codes following ""R:LTXNLOCK"" are interpreted as Dan Miley explained in his
arlier note.
------------------------------
C001000 V26 T15 T:000265316 AP472O10 P:D472OJ04 C:DEAD WAITING ON R:LTXNLOCK
3F22008 00017B49
C001000 V26 T15 T:000265317 AP472O10 P:D472OJ06 C:DEAD WAITING ON R:LTXNLOCK
3F22008 00017B48
C001002 V26 T15 T:000265317 AP472O10 P:D472OJ06 C:DEAD DEADLOCKED ON R:LTXNLOCK
3F22008 00017B48
------------------------------
C001007 V24 T1057384 TASK:AP479H01 PROG:D479HC01 WAITING FOR LTXNLOCK 03E90008
78E5301
C001008 V24 T1057384 TXNID:48566301 PROG:D479HC01 SUBSCHEMA:A479HU00 MODE:X
C001009 V24 T1057384 TSKID:1057387 TASK:AP479H01 PROG:D479HG01 HOLDS LTXNLOCK
3E90008 778E5301
C001010 V24 T1057384 TXNID:48566303 PROG:D479HG01 SUBSCHEMA:A479HR00 MODE:S
C001003 V24 T1057384 TASK:ADS2 PROG:ADSOMAIN(D479HC01) STALLED WAITING FOR
TXNLOCK 03E90008 778E5301

Outcomes