×
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.
Hi Jerry,
I am curious as to why you say that Scott?
[SNIP]
The only problem (and I know this is why you and your peers recommend
avoiding this) is that when a modification is required to the module then
all the programs using it need to be recompiled (and I know that these
should be in a service program and accessed via prototyped calls).
Well, no... you don't have to recompile. Just re-bind (UPDPGM or
UPDSRVPGM). But yes, that's exactly why I recommend not binding the
same module to more than one program.
Not only does it save you time re-creating things, but it saves time
doing analysis to determine what needs to be re-created. Using a
service program intead of a module also makes your routines available
for use as a web service, stored procedure, or SQL function. Plus it
makes it callable from Java and other non-ILE languages.
I realize that making the change from static binding to reference
binding will take some time and some upheaval, and it won't happen
overnight. All I was trying to tell you is that reference binding (i.e.
SRVPGM instead of MODULE) is the route that I recommend.
I didn't know that you already knew that.
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
