Re: Extpgm() or Extproc()?

Hi Tom,

You have to remember that PR=Prototype. It's used to 'call something'. PI=Procedure Interface. It's used to receive parameters.

So having EXTPGM instead of EXTPROC on the prototype has a big affect -- but you'll never notice it if you don't use the prototype to call something. I.e. if you coded EXTPGM (when it's actually a module, and not a program) and tried to use the prototype to call the routine, then you'd get an error, since the *PGM wouldn't be found on disk.

However, since it's called via CALLPRC, and not called via the prototype, there's no side effect.



qsrvbas@xxxxxxxxxxxx wrote:

That is, the PR-spec had EXTPGM( XYZRPG ) rather than being a *NOMAIN module with EXTPROC( XYZRPG ).

It's not so much that I think that's wrong, in a compile/bind sense. It all apparently compiled and was bound exactly as the developer told it to be (regardless of intent). It's more that the "mechanism" isn't clear. I'm not sure that it would have ever crossed my mind even to try to do things that way.