what is the "bound program access - built in number" mentioned in the mi
functional reference manual?


I am curious how procedures like "_lbcpynv" and "ceedod" are implemented in
the rpg compiler as inline instead of procedure calls.

In RPGLE there are an entire series of built in functions which, I assume,
execute as inline functions.  Also, a lot of the "CEE" procedures like
CEEDOD ( get operational descriptor info ) CEEHDLR ( register a user written
condition handler ) are not invocation stack calls, but are implemented

Recently, while writing some rpg code to do data pointer like operations, I
noticed that the RPG compiler bombs when the procedure prototype of the
_LBCPYNV instruction is not correct.  It is the same compiler type of crash
that I would see when QPRCRTPG is called with an MI stmt with an incorrect
operand template value.

That indicates to me that the _LBCPYNV proc is also implemented as an inline
in the RPGLE compiler. And the RPGLE compiler is simply inserting the
contents of _LBCPYNV into the instruction stream without regard to the
actual code. More like a macro insertion of w-code or MI-code than anything

So the question is, is it possible to compile and bind a user written
procedure, somehow tag it with a "built in number", then have the RPGLE
compiler implement that procedure as a "built in", that is INLINE call.


-Steve Richter

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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

This mailing list archive is Copyright 1997-2021 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.