RE: Locking records in DB2

Ron,

Nice idea but wrong.  What usually happen is that a user gets into a record 
then runs to get a cup of coffee, so nobody and no process can access then 
record while it is locked.

This read and hold lock till the user finishes his changes is strongly 
discourage now-a-days even for green screen programs.  You certainly don't want 
to code your web apps that way.


HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: java400-l-bounces@xxxxxxxxxxxx
> [mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of RPower@xxxxxxxxxx
> Sent: Wednesday, October 05, 2005 7:36 AM
> To: Java Programming on and around the iSeries / AS400
> Subject: RE: Locking records in DB2
> 
> 
> I'm trying to make sure that if a user decides they are going 
> to open a 
> particular record for edit mode to make changes, that another 
> user can't 
> get into that same record and make changes and overwrite each other.
> 
> Ron Power
> Programmer
> Information Services
> City Of St. John's, NL
> P.O. Box 908
> St. John's, NL
> A1C 5M2
> 709-576-8132
> rpower@xxxxxxxxxx
> http://www.stjohns.ca/
> ______________________________________________________________
> _____________
> Success is going from failure to failure without a loss of 
> enthusiasm. - 
> Sir Winston Churchill
> 
> 
> 
> 
> "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx> 
> Sent by: java400-l-bounces+rpower=stjohns.ca@xxxxxxxxxxxx
> 2005/10/04 03:29 PM
> Please respond to
> Java Programming on and around the iSeries / AS400 
> <java400-l@xxxxxxxxxxxx>
> 
> 
> To
> "Java Programming on and around the iSeries / AS400" 
> <java400-l@xxxxxxxxxxxx>
> cc
> 
> Subject
> RE: Locking records in DB2
> 
> 
> 
> 
> 
> 
> >Do you have a better suggestion than the record lock then in 
> a web app?
> 
> 
> What are you trying to accomplish?
> 
> -Walden
> 
> ------------
> Walden H Leverich III
> Tech Software
> (516) 627-3800 x11
> WaldenL@xxxxxxxxxxxxxxx
> http://www.TechSoftInc.com
> 
> Quiquid latine dictum sit altum viditur.
> (Whatever is said in Latin seems profound.)
> 
> 
> -----Original Message-----
> From: java400-l-bounces@xxxxxxxxxxxx
> [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of RPower@xxxxxxxxxx
> Sent: Tuesday, October 04, 2005 1:52 PM
> To: Java Programming on and around the iSeries / AS400
> Subject: RE: Locking records in DB2
> 
> Do you have a better suggestion than the record lock then in 
> a web app? 
> That's not being sarcastic either, I'm open to suggestions :)
> 
> Ron Power
> Programmer
> Information Services
> City Of St. John's, NL
> P.O. Box 908
> St. John's, NL
> A1C 5M2
> 709-576-8132
> rpower@xxxxxxxxxx
> http://www.stjohns.ca/
> ______________________________________________________________
> __________
> ___
> Success is going from failure to failure without a loss of 
> enthusiasm. -
> 
> Sir Winston Churchill
> 
> 
> 
> 
> "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx> 
> Sent by: java400-l-bounces@xxxxxxxxxxxx
> 2005/10/04 03:15 PM
> Please respond to
> Java Programming on and around the iSeries / AS400 
> <java400-l@xxxxxxxxxxxx>
> 
> 
> To
> "Java Programming on and around the iSeries / AS400" 
> <java400-l@xxxxxxxxxxxx>
> cc
> 
> Subject
> RE: Locking records in DB2
> 
> 
> 
> 
> 
> 
> >Can anyone help me with understanding what I need to do to 
> use Java and
> 
> >SQL to put a record lock on a database file on the iSeries? 
> 
> You WANT to put a record lock on a row? And how long do you intend to
> hold this lock? The suggestion of "...FOR UPDATE" might work w/in the
> servlet or JSP, but once you return to the user there's no guarantee
> that the user will be serviced by the same iSeries job next time.
> 
> Holding a record lock on a web app is not something you 
> usually want to
> do. I guess if you really need to do it, the first thing that comes to
> mind is to hold the lock not in the java program, but in a 
> surrogate job
> you launch specifically for this task. 
> 
> -Walden
> 
> ------------
> Walden H Leverich III
> Tech Software
> (516) 627-3800 x11
> WaldenL@xxxxxxxxxxxxxxx
> http://www.TechSoftInc.com
> 
> Quiquid latine dictum sit altum viditur.
> (Whatever is said in Latin seems profound.)
> 
> 
> -- 
> This is the Java Programming on and around the iSeries / AS400
> (JAVA400-L) 
> mailing list
> To post a message email: JAVA400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
> 
> 
> -- 
> This is the Java Programming on and around the iSeries / AS400
> (JAVA400-L) mailing list
> To post a message email: JAVA400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
> 
> 
> -- 
> This is the Java Programming on and around the iSeries / 
> AS400 (JAVA400-L) 
> mailing list
> To post a message email: JAVA400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
> 
> 
> -- 
> This is the Java Programming on and around the iSeries / 
> AS400 (JAVA400-L) mailing list
> To post a message email: JAVA400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
> 
>