I don't know about Universe but UniAdmin displays the time the lock was
set in UD.
On 23/03/2012 06:06, Namacha, N. (Nicholas) wrote:
Is it possible to know for how long a record has been locked in universe?
Kind Regards
Nicholas Namacha
Nedbank Limited Reg No
There is no way of which I know, in Universe natively, to figure out what time
a lock was set.
Years ago, I wrote a job that woke up every five minutes, scoured the lock
table, and updated a lock table history file.
Then at any time, you could query that history to how long a lock had been open
Problem is if a lock was set multiple times within that 5 minute interval, it
could look like
It had been setup for 5 minuteswhen in reality, it could have only been
locked for a couple seconds
This time.
I guess you could always make that five minutes, down to like 10 seconds or
so...
Not possible.
If you have *one* task that is setting and releasing the same lock constantly
than yes.
However that should be recognized as a problem and corrected anyway, except the
slim possibility of a Batch Job Status flag lock itself.
Otherwise, each process will have a unique process id
Not paying much attention to this thread so perhaps I missed
something, but...
That's not a problem, every application has code that does rapid
lock/write/release operations on the same record. George's scenario
was common and perfectly reasonable.
T
(And dude, you really need to do something
Your answer is not related to the main thrust of this thread.
-Original Message-
From: Tony Gravagno 3xk547...@sneakemail.com
To: u2-users u2-users@listserver.u2ug.org
Sent: Fri, Mar 23, 2012 11:11 am
Subject: Re: [U2] Record lock
Not paying much attention to this thread so perhaps
It is not relevant that there is *code* that does locking and releasing of the
same item.
It must be not just *code* but the exact same process ID that is doing this.
This thread is not about exceptions.
It is about how to tell how long a lock has been set for. You will always have
I whole-heartedly disagree...
1) I have numerous processes that lock/update/release the same record
repeatedly running 24x7 - on the sale process id.
2) I don't want code that works 98% of the time - that's unacceptable. I don't
want calls in the middle of the night because it appears
So you would recommend the OP modify their entire system of three thousand
programs
Instead of accept a 98% solution?
Very nice.
-Original Message-
From: Robert Porter ropor...@ochsner.org
To: u2-users u2-users@listserver.u2ug.org
Sent: Fri, Mar 23, 2012 11:44 am
Subject: Re: [U2]
Come on, people! Let's not get into another pissing contest of who
programs the right way and who doesn't. As stated, the original
question was if there is a way to tell how long a lock has been in
place. Nothing else was given so the assumption that the OP was ONLY
looking at locks placed
*sigh*
*putting the pop-corn back up*
On 3/23/2012 3:00 PM, Woodward, Bob wrote:
Come on, people! Let's not get into another pissing contest of who
programs the right way and who doesn't. As stated, the original
question was if there is a way to tell how long a lock has been in
place.
There is not, on Universe natively, any value that tells you how long a lock
has been placed.
I answered that in the first response.
You have to roll your own.
-Original Message-
From: Woodward, Bob bob_woodw...@k2sports.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Fri,
And the answer was -- I ASSumed UDT.OPTIONS 88 was on since we have other
'C' code running. Now, if I had executed THAT other c code, and then
tested this code, it would have worked! But it was not 'on' from Login --
D'Oh!
The weird part is that the C program DOES get called and all variables
13 matches
Mail list logo
