|
OK - From the thread on this topic I understand that when you add procedures to a service program and export(*all) the signature changes and calling programs will do the equivalent of a level check. If you list the procedures separately in a bind source and use this on the create service program, this problem goes away. This is the part I don't understand. Say I have a service program with three procedures (Proc1, Proc2, and Proc3) and I create a service program (SrvProg) listing all three in my bind source. Then I use this service program in 50 other programs. Then I decide that Proc4 would be useful so I add it to my service program source, add it to my bind source list and re-create SrvProg with the new bind source. Doesn't SrvProg now have a new signature? Won't my other 50 programs blow up? If not, why not? TIA, Lance +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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-2025 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.