RE: Calling a Procedure from Another Program

["Bob Cozzi" <bob@xxxxxxxxxxxx>]

> > > > EXPORT (which I recommend be placed on all subprocedures) ...

> > Why do you recommend this?


Because 10 times out of 10 RPG programmers who create a subprocedure and evolve
them to a service program go through the following learning experience:

Create a new subprocedure in a *PGM's mainline source/module.
Call it from the main program body; it works fine.
Move the subprocedure to a secondary source mbr.
Compiler the original source mbr (now sans the subproc) and the new source mbr.
Bind... 
"Compiler failed in bind phase, see joblog for details."  
Huh?
Look at joblog.
What does "Unresolved external reference" mean?
What do you mean I don't have MySubProc defined--it is right there!
This ILE stuff sucks!


Had the programmer simply put the EXPORT keyword on the P spec, out of habit,
and then removed it only when necessary (out of 1200 subprocedures or so that
I've written, I have not used EXPORT on about 5 of them), they wouldn't have
this issue.


-Bob Cozzi