|
Think of signatures as file level identifiers for service programs. In your binder language, you can set it up so that it will have more than one signature. There are great examples in the online books to do this. In a nutshell, after you have added new subprocedures, do the following: 1. Make a copy of all the binder language statements in a group. On one of them (the one you are not adding the new subprocedures to), change it to read PGMLVL(*PRV). 2. On the other list, add your new subprocedures. Here's an example of binder language that will produce 2 signatures so that the programs that use the old subprocedures will not have to be recompiled. STRPGMEXP EXPORT SYMBOL(SP1) EXPORT SYMBOL(SP2) EXPORT SYMBOL(NEWSP) ENDPGMEXP STRPGMEXP PGMLVL(*PRV) EXPORT SYMBOL(SP1) EXPORT SYMBOL(SP2) ENDPGMEXP Hope this helps... Bradley V. Stone -----Original Message----- From: Wayne Achenbaum [mailto:wache@slomins.com] Sent: Monday, March 15, 1999 4:41 PM To: MIDRANGE-L@midrange.com Subject: Service programs no binder language signatures??? I have general question regarding modifying and adding code to a service program. My question is this. If I for example add additional sub-procedures to a given service program, do I have to rebind this service pgm to any of the *pgm objects that are currently bound to this service pgm and don't even use the new sub_procedures? The service program visibly has a different signature than the signature seen in the service pgm detail on a display pgm of the pgms previously bound to this service pgm. Can anyone tell me if the signatures mean anything when not using binder language. If so what are the ramifications of not rebinding the service pgm in question. TIA Wayne Achenbaum +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.