Then you're misunderstanding what I'm saying.

 

 

 

-----Original Message-----
From: Kevin King <ke...@precisonline.com>
To: U2 Users List <u2-users@listserver.u2ug.org>
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 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 depends on the need of the
> application and many situations where I would highly recommend using the
> default locking system of READU.
>
>
> -----Original Message-----
> From: u2-users-boun...@listserver.u2ug.org <javascript:;>
> [mailto:u2-users-boun...@listserver.u2ug.org <javascript:;>] On Behalf Of
> Wjhonson
> Sent: Thursday, February 07, 2013 3:41 PM
> To: u2-users@listserver.u2ug.org <javascript:;>
> 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 other odd manner, or perhaps processing a batch of something.
>
> So it's rather a nasty trick to play on the user, to just use READU
> without a LOCKED clause
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Woodward, Bob <bob_woodw...@k2sports.com <javascript:;>>
> To: U2 Users List <u2-users@listserver.u2ug.org <javascript:;>>
> 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 approach.  That was what I
> attempted to show in my first response.  I guess I was a bit terse in
> that one, though.
>
> BobW
>
> -----Original Message-----
> From: u2-users-boun...@listserver.u2ug.org <javascript:;>
> [mailto:u2-users-boun...@listserver.u2ug.org <javascript:;>] On Behalf Of
> Anthonys
> Lists
> Sent: Thursday, February 07, 2013 2:21 PM
> To: u2-users@listserver.u2ug.org <javascript:;>
> 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 '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)?
>
> Somebody will correct me if I'm wrong, but I thought that was exactly
> what READU did!
>
> If you don't provide a LOCKED clause, READU will "hang" and wait until
> the lock clears, then read and lock the record.
>
> As I say, check the docu and make sure I'm right ... I've never had to
> bother much with locks ...
>
> Cheers,
> Wol
> >
> >
> > Thank you,
> >
> > Jon Wells
> >
> >
>
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org <javascript:;>
> http://listserver.u2ug.org/mailman/listinfo/u2-users
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org <javascript:;>
> http://listserver.u2ug.org/mailman/listinfo/u2-users
>
>
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org <javascript:;>
> http://listserver.u2ug.org/mailman/listinfo/u2-users
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org <javascript:;>
> http://listserver.u2ug.org/mailman/listinfo/u2-users
>
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

 
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to