RE: Dealing with Record locks in embedded SQL

You're probably right.  However I've found that many RPG developers get 
kind of sloppy and when they get the lock they either really screw up and 
assume that it's the end of the read loop, or, they skip the row and go 
on.  No handling of the lock occurs.

By the way the fastest rpg development may be as bad as the sql solution. 
For example, take the program that I used to create a lock (and just 
paused in via WDSC's debugger).
h option(*nodebugio)
FLOCKER    UP   E             DISK    rename(locker:rlocker)
 /free
  mychar='SISTER';
  update rlocker; 
 /end-free 

Rob Berendt