|
Gary L Peskin wrote: > You say that "To get clean compiles ...". What happens if you just > change all of the STRPGMEXP commands, except the current one, to specify > PGMLVL(*PRV). Why doesn't this result in a clean compile? > > Gary > I do that, but it is not enough because the new set of exports is placed at the end of the source member by RTVBNDSRC instead of at the beginning where the compiler requires it. Also, it alphabetizes the exports rather than adding the new exports at the end. While this will compile OK, it causes mismatches when programs compiled under an earlier signature try to call a procedure which used to be the first export, for example, and now gets a completely different procedure just because RTVBNDSRC moved a new one into export position one. Programs using the service program go by the position of the exports and not the name or size of parameters, etc. I understand how to fix the problem, by moving the new source from the bottom of the source member to the top and by reorganizing the exports to put the new ones at the end. But if you have to do all that there is no point to using the RTVBNDSRC command. It's easier to do it by hand. My question is am I doing something wrong or is RTVBNDSRC really that badly written? Or has a PTF been issued to address this problem that I don't know about? -- Nelson Smith "Standards are Wonderful....cause there's so many to choose from!" ncsmith@gate.net +--- | 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-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.