×
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.
My problem now with service programs is that I don't see why I would put
exported procedures anywhere else!
If I create an exported procedure it's surely to be able to call it from
more than one program, so why have we been putting everything in modules?
Answers, please.
We DO have an application that recompiles all the necessary objects when a
module is modified. Trouble is, more and more programs are binding the same
procedures and the application seems to want to compile the whole machine
when one of our more popular modules is modified!
As for adding parameters, is this not a an idea ? :
Calling procedure
/COPY QRPGLESRC,DSPEC_P1
WPARM1 = IPARM1
WPARM2 = IPARM2
/COPY QRPGLESRC, CALL_P1
*************************************
QRPGLESRC/DSPEC_P1
D WPARM1 S LIKE(REF_PARM1)
D WPARM2 S LIKE(REF_PARM2)
*************************************
QRPGLESRC/CALL_P1
CALLP ( WPARM1 : WPARM2 )
*************************************
I haven't tried this, maybe someone will see a flaw right away and save me
some time.
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: ILE question : parmameters, modules and service programs, (continued)
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.
midrange.com
