Record already locked to this job? Hans?

Hi,
What makes the "record manager" so much smarter under ILE?
I've seen this error a few times on programs converted to ILE, but ran OK in
RPG400.
RPGIV / ILE / whatever seems to be a lot "smarter" about this than OPM did.

I'm just wondering why.

This kind of thing is an argument used against converting to RPGIV / ILE.
This seems as though it would be a function of the "record manager", not the
"environment".  Is this somehow caused by the new&improved activation group?

My latest example showing this problem is:
C     kholdk        Chain     qlvf020d
C                   If        %found(qlvf020d) And @lotohqty > *Zero
C                   Eval      lbqoh  = lbqoh + @lotohqty
C                   Update    ql020d
C                   Else
**** this goes and chains the same record, generating the error

I added an UnLock(E) following the else.  Really should split the If, but
the unlock was quicker.
I realize this is a legitimate problem, but RPG400 (OPM) didn't care.

This seems to be more of a "midrange-l" question, but after I added a little
RPG code, I changed to rpg400-l.

TIA

AS/Resources, Inc.
William A.(Tony) Corbett
IBM Certified Specialist - AS/400 Developer
http://www.asresources.com
corbett@asresources.com
770-587-4812 (office)
678-935-5006 (mobile)
fax:  404-663-4737