|
Bradley, Which V4R3 API was changed in an incompatible fashion? In looking at the Memo the Users I didn't see any mention of this; and I also don't recall any change of this type (though it's always possible either the change slipped through or the change was viewed as a fix rather than a change/enhancement) being discussed for V4R3. I can assure you that IBM goes to great pains at times to maintain compatibility with previous releases in terms of programming interfaces. Thanks, Bruce > >Well, after further looking, the source from MC was old and I had hardcoded >the size of the data instead of using the parameter passed back in the >EntrySize parameter. This has been fixed in the meantime and I will be >posting the newer version on my AS/400 shareware site. > >The reason I thought IBM did something is because they DID change an API >from V4R2 to V4R3 for another one of my tools (SCNMSGF). Half of the data >was pushed over one byte. This could not be fixed without having two >version of the software. > >Bradley V. Stone >BVS/Tools >http://www.bvstools.com > +--- | 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.