|
Hello, On Mon, 29 Aug 2005, Jeff Young wrote: [SNIP]
The only way to get the service program to create is to specify Export on the procedure in Module 2.
Correct. The "EXPORT" is another way of saying "This can be used from outside this module." Without export, you're saying "This CANNOT be called from outside this module."
Make sense? [SNIP]
I could use Binder language and specify the specific procedures to export, but would prefer not to.
Binder Language tells the system which procedures are exported from a *SRVPGM, The EXPORT keyword tells which procedures are exported from a module (which is a prerequisite to being exported from a *SRVPGM)
Frankly, IBM should never have made it possible to build service programs without specifying binder language. It should be required.
Service programs that don't have binder language are an absolute nightmare to maintain. You have to recompile every program that calls them whenever you make any changes to the public interface!
Binder language is extremely simple -- it's really nothing more than a list of what's being exported from the service program. Just a list of procedures, that's it.
So, why don't you want to use it? It takes seconds to write. It'll make maintenance much simpler. AND it solves the problem that you've asked about today. Why would you not want to use it?!
As an Amazon Associate we earn from qualifying purchases.
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
