ca.portal.admin

Re:Access to Lock Data Used in PMRM?

Discussion created by ca.portal.admin on Mar 9, 2010
Hi, =20

I have been looking at a bunch of DEADLOCK and STALL issues in some CAS code. =20 =20 I have a couple programs that are stalling quite often. One in partiuclar appears,based on the last command displayed in the Log (using ADS TRACE), that the next command that SHOULD be executed is a OBTAIN OWNER - which SHOULD get the PURCHASE-ORDER (owner of an activity
junction record). =20
I am assuming that another program is locking the record (and it seems like this data stays locked for quite a long time - stalls leading to aborts)=20

They do not have PMRM which I would think would help identify what program might be holding onto the record the stall program is not getting (the example below is from a presentation on dealing with Deadlocks.)=20 Is there some other way to see this data (which programs are holding a
lock) - be it the Network (IDMSNWKA) or some kind of journal report?=20 =20 From a presentation on Deadlocks: (My apologies to the author for not knowing who wrote it) PMRM - Active User Task Detail PM-R16.0 TECHDC99 Computer Associates Intl. V545 04.112
CMD--> 02 Active User Task Detail
Task Task Current Waited_On Dbkey
Number Code Program Dbkey Holder
109414 ADS2 DBCRUPD 680037: 13 VL500006
109887 ADS2 DBCRUPD 680021: 13 VL500035
109923 ADS2 DBCRUPD 680022: 1 VL500025
109917 ADS2 DBCRUPD 680039: 13 VL500003
109797 ADS2 DBCRUPD 680019: 11 VL500018
109700 ADS2 DBCRUPD
109827 ADS2 DBCRUPD 680047: 1 VL500024



The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Access to Lock Data Used in PMRM?
"The OPER task code could be of use to determine the program name holding
locks, using the WATCH DB command within OPER, and the WATCH ACTIVE
TASKS command within OPER will show the LTERM and USER ID.

Regards,

John Collins
SAIC

Outcomes