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 firstname.lastname@example.org.
We based our service programs on Scott's ILE concepts presentation.
We have multiple service programs split by business area, one source member to one service program, each has a static signature, new procedures get added to the end.
One binding directory holds all the *SRVPGMs.
In the presentation it says "A program calls subprocedures in a service program by number" and "Always add new procedures to the end so that the existing numbers won't change"
When you have multiple modules bound together to make one service program, do you have to be careful to insert the new procedures into the binder source in the correct position, and always bind the modules on the CRTSRVPGM in the same sequence, and always have separate signatures in the binder source so you don't have to re-bind the callers?
I've got another question regarding service program deployment into a production environment.
For *PGM changes we use QLIRNMO, so it moves the existing version of the program into QRPLOBJ, so we can install fixes without the user's needing to log off.
We don't hold any source on production machines, just wondered how other people install service programs?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2023 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.