×
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.
However, other scoping rules apply. The next scoping rule is that
subprocedures can not be called from outside of their *PGM.
This isn't completely true Bob. It is perfectly possible to have a
conventional *PGM object act as a SRVPGM - with the advantage (?) that the
normal LR rules etc. can be applied.
I worked with a UK business partner some years ago to implement a system
based on this notion. Admittedly you cannot simply call the exported
procedures in the "conventional" way since the *PGM requires activation
before its subprocedures can be called.
The method is simply to call the *PGM and have it hand back one or more
procedure pointers to its subprocedure(s). They can then be called with no
problems. The procedures do not need the EXPORT keyword - actually they
don't in a *SRVPGM either if it called by procedure pointer.
Jon Paris
Partner400
www.Partner400.com
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
