×
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.
I think the memory taken up by program instructions is common among all jobs using the program or service program, while temporary storage is allocated for each job. I can see how late binding to each module that is now a service program will lower the temporary storage allocated to a job until all modules have been bound and called. So if modules are never used in a particular job then that job will use less storage under this model than under the monolithic program model. For 600 jobs, this can add up to less contention for memory and so less paging and better performance. This would be countered by the added time for the late binding to occur as each module is called.
Apologies for abusing the word module here, but it seems that module and procedure would be interchangeable for this discussion.
Regards,
Kevin Wright | IBM i Developer, LPC
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
