Re: Calling a Procedure from Another Program

["Brian Johnson" <brian.johnson.mn@xxxxxxxxx>]

AKA dumb-it-down...


On 5/31/07, Bob Cozzi <bob@xxxxxxxxxxxx> wrote:
> >>>> 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
>
>
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.