How to release lock on a record in RPG/400

Ben Rubenstein

11255 pts.

Tags:

RPG

RPG/400

What type of opcodes should I use to release the lock on a record?

Asked: July 29, 2008 10:32 AM Last updated: May 19, 2017 11:40 AM

Answer Wiki

Last updated: August 22, 2013 5:06 PM GMT

Ben Rubenstein11,255 pts.
History
Contributors
- Ordered by most recent
- Ben Rubenstein11,255 pts.
- Gilly40023,730 pts.

Thanks. We'll let you know when a new response is added.

Hi,

The following opcodes should release locks on records.

CLOSE
EXCEPT
REL
UNLOCK
UPDATE

Regards,

Martin Gilbert.

=======================================================

The problem with the lists above and in the Discussion below is that some of the op-codes are from RPG IV and not RPG/400.

For RPG/400, the corrections are EXCPT, UNLCK, UPDAT and COMIT.

Tom

Discuss This Question: 10 Replies

Birddon Jul 29, 2008 2:39 PM GMT

It used to be a standard interview question, Name 7 ways to release a record lock in RPG. READ (READE READP) CHAIN CLOSE UNLOCK UPDATE EXCEPT (for the file) SETLL (SETGT SETLT)

45 pointsBadges:

report
Gilly400 Jul 30, 2008 9:44 AM GMT

Hi, The READ, CHAIN and SETLL don't necessarily unlock records, especially not if you're using commitment control. Regards, Martin Gilbert.

23,730 pointsBadges:

report
GAC Jul 30, 2008 5:10 PM GMT

... if you are using commitment and want to release the record(s) use COMMIT ... But I have experienced that it does not work under some circumstances. :-o

300 pointsBadges:

report
Yorkshireman Oct 6, 2011 7:23 AM GMT

You need to look in the manual relevant to the language you are using. The issue of when a lock is created, or not, is dealt with fully, precisely, and definitively by the IBM authors who write these things. Check the DB2 programming and the RPG or RPGLE manuals

6,085 pointsBadges:

report
UARTJ May 3, 2017 2:51 PM GMT

Does WRITE lock up that record?

170 pointsBadges:

report
jpanzenhagen May 4, 2017 1:17 PM GMT

WRITE does not put a lock on a record.

95 pointsBadges:

report
ToddN2000 May 4, 2017 1:19 PM GMT

A WRITE will not lock a record. A CHAIN locks a record... I have run across many old programs, old like RPGII and RPGIII, that used a CHAIN to validate data with a file. If that is all you are doing and you get locks on this record, it is better to use the opcode (not sure when this came out, but use CHAIN(N). This does the chain but with a no lock option.

100,095 pointsBadges:

report
GregManzo May 4, 2017 11:31 PM GMT

If you are only validating the key exists, then CHAIN(N) or SETLL both work - SETLL is marginally faster but you don't get the contents of the record.
A WRITE will lock the new record *if* you are using commit control - and if you aren't then why not? If you are serious about data integrity then you should be making a 'commitment' to your database. :-) but be aware of the differences between an ODP record lock and a commit lock.

2,315 pointsBadges:

report
WoodEngineer May 5, 2017 4:38 PM GMT

Are you asking about a record locked by your program or a lock created by another program?

7,900 pointsBadges:

report
TheRealRaven May 19, 2017 11:40 AM GMT

Without knowing the circumstances of the lock, there's no good way to answer. WoodEngineer is on a good track there.

23,285 pointsBadges:

report