Re: Imbedded SQL UPDATE

Well you know what the say about assuming....

Try commenting out the SQL update and see if you still get the record lock.

If so, how are you doing the SQL update, as a searched update, or a
positioned update (using a cursor)?

Some code might be useful.

Charles


On Tue, Apr 28, 2009 at 6:40 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx>
wrote:

Thanks, Martin,

I just added <with nc> at the end of the UPDATE clause. I'm still getting

the message that the record is blocked by the job.

I've been through the entire application looking for possible record

locks but haven't found any. While debugging, I can change the key value
when the SQL UPDATE is executed. This forces it to fail, then the READE that
occurs later works. This is my reason for assuming that the SQL UPDATE does
not release the record.

-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Hillier, Martin
Envoyé : mardi 28 avril 2009 12:04
À : RPG programming on the IBM i / System i
Objet : RE: Imbedded SQL UPDATE

Hi David,

Is commitment control locking the record?

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: 28 April 2009 10:58
To: RPG programming on the IBM i / System i
Subject: Imbedded SQL UPDATE

Hi,

After an UPDATE on a file by SQL, a subsequent READE is
failing because of a record lock.

Why doesn't the SQL UPDATE let go afterwards as a an RPG
UPDATE would do?

David FOXWELL
Service Informatique
Tél : 03 90 23 91 63
david.foxwell@xxxxxxxxx<mailto:david.foxwe@xxxxxxxxx>

P Pensez à l'environnement avant d'imprimer ce message

--
This is the RPG programming on the IBM i / System i
(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 message (including any attachments) is only for the use
of the person(s) for whom it is intended. It may contain
Mattel confidential and/or trade secret information. If you
are not the intended recipient, you should not copy,
distribute or use this information for any purpose, and you
should delete this message and inform the sender immediately.
--
This is the RPG programming on the IBM i / System i
(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 IBM i / System i (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 IBM i / System i (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.