RE: CRTDUPOBJ an ILE program

Scott asked:

>How about we change our philosophy to be the "top-level 
>ILE program" instead of merely the "top-level program"?

The thing is there might not be a top level ILE program yet.  Say I have a
payroll application with a dozen programs in it.  I'm working on a mod to
the tax section of one of them, and I convert it to RPG IV so I can use some
new BIFs.  Normally, I'd just compile the thing in the DAG so it fits with
all the other OPM programs in the app.  But I'm a wise guy, and decide to
put a subprocedure in there.  I CAN make it *CALLER, but should I?  It'll
run in the DAG just like the OPM version, so it's no big deal, I guess...

Time passes and I change two other programs in that application.  As it
turns out, they can share some tax calculation code, so I put that into a
service program.  Do I make that *CALLER?  It'll run in the DAG, but it'll
be unpleasant to deal with service programs in the DAG.  Or will it?  I
guess that's where my out-of-date thinking might lie.  So, for a
randomly-mixed shop, perhaps all *CALLER is adequate advice?  When they move
the entire application to ILE, they can identify the top level for payroll
and make that *NEW.  Nothing else needs to change, I guess.
  --buck