ca.portal.admin

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

Discussion created by ca.portal.admin on Mar 9, 2010
hen perhaps the real question becomes:
oes Ms Kline need this information real time as it happens, or can
ily reports suffice
f the latter, then certainly the log can be interrogated and all
cessary information can be retrieved
the former - good luck - even if you sat all day executing lockmon
u MIGHT see stalls building, but many deadlocks could come and go
tween two hits of the ENTER key
hris
"
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?
"Cindy,

Your OPER W DB display does not show any user/task currently locked out
that I see (maybe you have a bad example). If you look in release 17.0
CA-IDMS System Tasks and Operator Commands Guide under DCMT DISPLAY
TRANSACTION there is a table for the STATUS (STA) field values: The
table shows the possible STATUS field values and their meanings:
Code Position 1 (Controlling module)
Position 2 (Wait status of transaction)
Position 3 (Progress of transaction).

These status field values apply to OPER W DB also. So I would expect to
see some values in the status field ( STA ) below if a transaction (your
OPER W DB shows only a 3rd position value and no user IDMSPROG or
SUSCHEMA) was waiting on something like a K in position 2 for IDMSLMGR -
Waiting for db-key lock held by another transaction. So my display shows
M111PSDC program waiting on DBKEY lock that is held by NSFDUPKG program
( I pieced this together so it might not be completely accurate).

TASK ID ORIG IDMSPROG SUBSCHEM PRI STA V# PAGEREAD PAGEWRIT
CALLIDMS
0000000010 DBDC M111PSDC UUFESS00 100 IKH 35 00000000 00000000
00000003
0000000009 DBDC NSFDUPKG UUF0SS48 100 H 54 00000000 00000000
00000003
0000000008 DBDC RHDCLGSD IDMSNWK9 253 A 56 00000000 00000000
00000003
0000000007 DBDC RHDCRUAL IDMSSECS 253 A 95 00000000 00000000
00000022
0000000007 DBDC RHDCRUAL IDMSSECS 253 A 95 00003700 00000000
00011688
0000000006 DBDC RHDCRUAL IDMSNWK8 253 A 54 00000000 00000000
00000003

Hope this helps,
Steve

Outcomes