g] On Behalf Of Peter Cheney
Sent: Sunday, February 10, 2013 2:36 PM
To: Jon Wells; U2 Users List
Subject: Re: [U2] Record locks (Unidata 7.2)
In the example below what happens to the lock?
Does it release if the write is not executed?
If not shouldn't you have a RELEASE statement at the end
-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jon Wells
Sent: Saturday, 9 February 2013 3:57
To: U2 Users List
Subject: Re: [U2] Record locks (Unidata 7.2)
I should add that (in our test account) I switched to the READU statement alo
ehalf Of Jon Wells
Sent: Saturday, 9 February 2013 3:57
To: U2 Users List
Subject: Re: [U2] Record locks (Unidata 7.2)
I should add that (in our test account) I switched to the READU statement along
with a LOCKED clause ->
READU STU.REC FROM STU.FILE, STU.ID LOCKED
CRT STU.ID:" REC
, Bob
Sent: Thursday, February 07, 2013 3:56 PM
To: U2 Users List
Subject: Re: [U2] Record locks (Unidata 7.2)
In an active user session where users are obtaining a lock for a length
of time, you're right. There are lots of times, though, that lock
intervention is not a benefit. It all depe
On second thought this won't do either since it hasn't got an ELSE clause.
ERR = ''
LOOP
TRY_AGAIN = 0
READU STU.REC FROM STU.FILE, STU.ID LOCKED
CRT STU.ID:" RECORD IS LOCKED - (Q)uit or Enter"
INPUT REPLY:
IF REPLY # 'Q' THEN TRY_AGAIN = 1 ELSE ABORT
END ELSE STU.REC = ''
UNTI
Oh no, you don't have to add a label and you don't have to use GOTO.
TRY_AGAIN = 1
LOOP WHILE TRY_AGAIN
READU STU.REC FROM STU.FILE, STU.ID LOCKED
CRT STU.ID:" RECORD IS LOCKED"
SLEEP 2
END THEN
STU.REC<48> = INST.CRED
STU.REC<49> = INET.CRED
WRITE STU.REC ON STU.FILE, S
TU.ID
END
SKIP:
John
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Woodward, Bob
Sent: Friday, February 08, 2013 1:10 PM
To: Jon Wells; U2 Users List
Subject: Re: [U2] Record locks (Unidata 7.2)
You should have writt
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jon Wells
Sent: Friday, February 08, 2013 9:57 AM
To: U2 Users List
Subject: Re: [U2] Record locks (Unidata 7.2)
I should add that (in our test account) I switched to the READU statement along
with a LOCKED clause ->
READU STU.REC FROM STU.FI
ginal Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jon Wells
Sent: Friday, February 08, 2013 9:57 AM
To: U2 Users List
Subject: Re: [U2] Record locks (Unidata 7.2)
I should add that (in our test account) I switched to the
understand how Unidata shops handle locks.
Thank you,
Jon Wells
From: Tony Gravagno <3xk547...@sneakemail.com>
To: u2-users@listserver.u2ug.org
Sent: Friday, February 8, 2013 2:30 AM
Subject: Re: [U2] Record locks (Unidata 7.2)
I think people unde
tand how Unidata shops handle locks.
Thank you,
Jon Wells
From: Tony Gravagno <3xk547...@sneakemail.com>
To: u2-users@listserver.u2ug.org
Sent: Friday, February 8, 2013 2:30 AM
Subject: Re: [U2] Record locks (Unidata 7.2)
I think people understand exactly
We don't really have the luxury to rewrite the entire system.
But we can fix one program a day
-Original Message-
From: Wols Lists
To: u2-users
Sent: Fri, Feb 8, 2013 1:22 am
Subject: Re: [U2] Record locks (Unidata 7.2)
On 08/02/13 07:30, Tony Gravagno wrote:
>
On 08/02/13 07:30, Tony Gravagno wrote:
> I think people understand exactly what you're saying, but disagree.
> Most applications don't use the more rigorous coding for having a
> Locked clause that provides additional information to the user,
> retries, etc. That's not "wrong", it's just not neces
I think people understand exactly what you're saying, but disagree.
Most applications don't use the more rigorous coding for having a
Locked clause that provides additional information to the user,
retries, etc. That's not "wrong", it's just not necessary ...
depending on the site.
That said, when
Then you're misunderstanding what I'm saying.
-Original Message-
From: Kevin King
To: U2 Users List
Sent: Thu, Feb 7, 2013 6:48 pm
Subject: Re: [U2] Record locks (Unidata 7.2)
+1. Well stated.
On Thursday, February 7, 2013, Woodward, Bob wrote:
> In an active
rsday, February 07, 2013 3:41 PM
> To: u2-users@listserver.u2ug.org
> Subject: Re: [U2] Record locks (Unidata 7.2)
>
> I wouldn't however *recommend* this approach to locking as the user can
> never tell if their terminal is waiting on a lock, or just "hung" in
> some
cking system of READU.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Thursday, February 07, 2013 3:41 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Record locks (Unidata 7.2)
I wouldn'
DU without a
LOCKED clause
-Original Message-
From: Woodward, Bob
To: U2 Users List
Sent: Thu, Feb 7, 2013 2:43 pm
Subject: Re: [U2] Record locks (Unidata 7.2)
You're exactly right. The only time you REALLY need the LOCKED clause
if there is some need to change that a
-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Anthonys
Lists
Sent: Thursday, February 07, 2013 2:21 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Record locks (Unidata 7.2)
On 07/02/2013 20:46, Jon Wells wrote:
> What I'm wondering is; what can I put into the &#
On 07/02/2013 20:46, Jon Wells wrote:
What I'm wondering is; what can I put into the 'Xxx what to do if locked'
section whereby it waits until the record lock clears, once it clears, set my
own lock, read the record, alter the record, and then write the record (which
would release my lock)?
tever reason.
Cheers
Peter
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Woodward, Bob
Sent: Friday, 8 February 2013 7:02
To: Jon Wells; U2 Users List
Subject: Re: [U2] Record locks (Unidata 7.2)
With the LOCKED c
mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jon Wells
Sent: Thursday, February 07, 2013 12:47 PM
To: U2 Users List
Subject: Re: [U2] Record locks (Unidata 7.2)
What I'm wondering is; what can I put into the 'Xxx what to do if locked'
section whereby it waits until the
>
>
> From: "Woodward, Bob"
> To: U2 Users List
> Sent: Thursday, February 7, 2013 12:35 PM
> Subject: Re: [U2] Record locks (Unidata 7.2)
>
> Sorry Mecki but I think you have the LOCKED in the wrong place. At
> least in my
you,
Jon Wells
From: "Woodward, Bob"
To: U2 Users List
Sent: Thursday, February 7, 2013 12:35 PM
Subject: Re: [U2] Record locks (Unidata 7.2)
Sorry Mecki but I think you have the LOCKED in the wrong place. At
least in my version of Unidata. It comes before the
m ECL in Unidata will get him that.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Mecki
Foerthmann
Sent: Thursday, February 07, 2013 12:27 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Record locks (Unidat
Perhaps we should apply a little Systems Analysis 101 here - ask some
questions. I'm not convinced that the original request completely
described the need.
What is the logical scenario (batch update, transaction entry, file
maintenance, etc.)?
Once a lock is removed, do you want your copy of t
The READU statement has a LOCKED clause that is true if a record is locked.
You can put all your locking ha logic in there.
READU record FROM filevariable,itemID THEN
code if record exists and isn't locked (optional)
LOCKED
code to handle locked record condition (optional)
END ELSE
code i
: U2-Users@listserver.u2ug.org
Subject: [U2] Record locks (Unidata 7.2)
Hi all,
I have not looked at the world of record locks since my R83 Pick days. I'm
hoping to add the ability for the program I'm working on to:
* Check if a record is locked
* Wait until the lock
o: U2-Users@listserver.u2ug.org
Subject: [U2] Record locks (Unidata 7.2)
Hi all,
I have not looked at the world of record locks since my R83 Pick days. I'm
hoping to add the ability for the program I'm working on to:
* Check if a record is locked
* Wait until the
Recte! I created me an infinite looop thingie.
The DOLOOP = 0 should be INSIDE the Loop structure... obviously
Bonk bonk on the head !
-Original Message-
From: Wjhonson
To: jwaytwells ; u2-users
Sent: Wed, Feb 6, 2013 1:57 pm
Subject: Re: [U2] Record locks (Unidata 7.2)
You
CRT 'HELP ME! HELP ME!'
-Original Message-
From: Jon Wells
To: U2-Users
Sent: Wed, Feb 6, 2013 1:53 pm
Subject: [U2] Record locks (Unidata 7.2)
Hi all,
I have not looked at the world of record locks since my R83 Pick days. I'm
hoping to add the ability for
Hi all,
I have not looked at the world of record locks since my R83 Pick days. I'm
hoping to add the ability for the program I'm working on to:
* Check if a record is locked
* Wait until the lock is removed
* Once the lock is removed, or if the record is not locked:
32 matches
Mail list logo
