RE: OVRDBF in ILE (was: diff btw Procedures and Routines)

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>all of my new RPG IV is ILE, either *NEW or *CALLER,
>and I try to encourage the other programmers to do
>the same.  I have H-spec /COPY members to make it easy.

What criteria do you use to determine if the AG should be *NEW or *CALLER?

>With one or two exceptions, all of the SHARE(*YES)
>is related to OPNQRYFs.  But we do have a lot of
>that.  For example, a lot of my service programs
>use our item master file.  There are also a lot of
>OPNQRYFs over the item master.  If I didn't protect
>the files in my service programs from sharing, it
>could cause a lot of "unpredictable results".

Perfect example of a mixed environment!  I'm pretty sure that if the OPNQRYF
is issued by OPM you need to OPNSCOPE(*JOB) in order to see the open in ILE.
That's regardless of OVRDBF SHARE(*YES).  So in this case, the ILE solution
would be to put the CL in the same AG as the ILE parent, and have the
service program in it's own AG.  I need to test it to be certain, but I'm
pretty sure I've encountered this.

Thanks for the explanation.  I've had my mind broadened!  (now I'm all the
way to 5mm!)
  --buck