×
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.
There are two uses for binder language:
1) To control the signature of your service programs. This is critical
if you intend to be able to make changes without re-binding all callers.
Everyone should be using binder language for this reason.
2) To control which procedures are exported from the service program.
(This is primarily useful when you have multiple *modules in your
service program.)
This has been discussed several times in the past, I think you'll find
it useful to search/read the archives. (I've primarily seen this
discussed on the RPG400-L list. Not so much on Midrange-L)
On 12/14/2010 7:11 AM, David FOXWELL wrote:
On the commande CRTSRVPGM our default settings are EXPORT(*SRCFILE).
I know that using a *SRCFILE will enable me to restrict the use of
certain subprocedures, but why wouldn't I just make the subprocedures
non exportable in the module, ie leave off the EXPORT keyword? Is the
idea so that more than one service program can be made from the same
module?
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
