RE: Record lock checking in RPG or CL?

AFIAC - if you are doing that check in CL, it's too late... First of
all, you need to do a two-read process. That is, when you initially read
the record, you do it without a record lock. When you get to the point
you are ready to update (which is the only thing that NEEDS a lock) you
read again with the lock, and update the record which releases the lock.


The only problem with this method is if ANOTHER program is not set up to
do the same thing, and locks the record while the user is at lunch... 

Dave 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Phil Kestenbaum
Sent: Monday, November 13, 2006 2:57 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Record lock checking in RPG or CL?

I could monitor for this CPF3156. and post a message to the user. Just
was wondering if there were any drawbacks to this method.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Turnidge, Dave
Sent: Monday, November 13, 2006 3:55 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Record lock checking in RPG or CL?

You've got to put your code where you are reading the record. Don't
think you can do it in a CL if you are reading the record in a follow-on
RPG program...

Dave 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Phil Kestenbaum
Sent: Monday, November 13, 2006 2:47 PM
To: RPG programming on the AS400 / iSeries
Subject: Record lock checking in RPG or CL?

HI,

 

 I have a program that I was not concerned of a record lock situation.
Now it has happened so I have to put in code to prevent the hanging. 

Is there any drawbacks to just to do this in the CL, ?

 

TIA,

Phil


This message contains information proprietary to our company. It is
intended to be read only by the individual or entity named above or
their designee.
Any distribution of this message or the information contained herein
without written permission from our company is strictly prohibited. If
the reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are hereby
notified that you have received this document in error and that any
review, dissemination, distribution, or copying of this message is
strictly prohibited. If you have received this communication in error,
please notify us immediately by e-mail, and delete the original message.


--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.