|
Since the list is so quiet, I might as well drop an item in that
I've been thinking around for a day or so.
While looking through a bunch of code to locate where a problem
might be found, I noticed that an outer ILE CL module contained a
CALLPRC XYZRPG for an RPG procedure. As I was going through the RPG
code, I also noticed that, as a module, it was actually structured
and apparently intended to be a whole program object.
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.
Is there anybody out there who might be willing to illuminate
potential unexpected side-effects of this structure?
Tom Liotta
--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone 253-872-7788 x313
253-479-1416
Fax 253-872-7904
http://www.powertech.com
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.