× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Straight from: http://www.redbooks.ibm.com/redbooks/pdfs/sg245402.pdf
Section 3.5.2 "Replacing the *ENTRY PLIST.

What I didn't see covered was a couple of suggestions as to how to store
the prototypes.
There are three school of thoughts.
1 - Hardcode it into every program that calls this subprogram. Take these
programmers and relegate them to working only on debugging 10,000 line
matching record programs that use every possible indicator out there -
including the halt indicators. These (expletive deleted) wouldn't be
likely to use your prototypes anyway. (see funny url at bottom)
2 - Store the prototype in a separate member and do a
/copy qprotosrc,... where ... is the name of the subprogram
3 - Use "compiler directives in the source for the called program. The
callING program may have
/define prototypesonly
/copy qrpglesrc,... where ... is the name of the subprogram
/undefine prototypesonly

and the callED program may have
/if not defined prototypesonly
... H specs, F specs, etc
/endif
Now the D specs for the prototype. (just the PR part, not the PI part)
/if defined prototypesonly
/eof ... the eof causes it to skip the rest of the source
/endif

To help transition people, I often code *ENTRY PLIST way off to the right
in the comment section of the prototype.

Now, for some light Friday reading...
http://members.iinet.com.au/~bofh/index.html

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.