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.
I agree with the others that Binder Language is the answer. But these days few people bother with multiple signatures and take the same approach that IBM use - namely a hared-coded signature that never changes. Unless and until you need to force a change to catch any programs that were not rebound after you needed to change the signature for whatever reason.
THE critical thing - regardless of multiple signatures or a single one is the ORDER of the names in the Binder Language is what controls the slot order in the program - and that is the only order that matters.
When adding a new procedure ALWAYS add it to the end of the list - don't be tempted to place it alphabetically. Add it to the end of the list and all will be well.
You might find these useful:
When Barbara Morris teaches this topic she uses comments in the binder source like this - a model I have adopted and encourage all my clients to do so.
/* Binder Language for UTILS */
/* Signature value remains the same */
/* Add EXPORT SYMBOL line for each new procedure added */
/* The order of the EXPORTS must never change */
/* New Exports must be added to the END of the list */
/* Never remove an Export entry from the list */
On Sep 20, 2022, at 6:08 AM, Rich Loeber <rich@xxxxxxxxx> wrote:
I'm a newbie to service programs. If I have an existing service program that is in use, how do I add a new module to it? Do I have to rebuild it from scratch? If so, does that mean that I have to rebind all current programs that are using the service program?
Kisco Systems LLC
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
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.