|
I have a v3r2 machine available for time sharing. You can get more info at http://www.timeshare400.com . Currently no one is using it so it's turned off. It probably costs about $50 a month just to keep the thing turned on. Keeps the office nice and warm, too... :) But, if someone wants to use it, it's available. You could use it to test your v3r2 compiles, or you could use it to develop your stuff. ----- Original Message ----- From: Richard Jackson <richardjackson@richardjackson.net> To: <MIDRANGE-L@midrange.com> Sent: Friday, September 22, 2000 10:27 AM Subject: RE: API's & Compiling to Prev Release > Be advised that backwards compatibility to V3R2 stops after V4R5 and, > according to the IBM presentation I saw yesterday, will not appear again. > It is now possible to upgrade directly from V3R2 to V4R5 but, never again. > Food for thought. > > Richard Jackson > mailto:richardjackson@richardjackson.net > http://www.richardjacksonltd.com > Voice: 1 (303) 808-8058 > Fax: 1 (303) 663-4325 > > -----Original Message----- > From: owner-midrange-l@midrange.com > [mailto:owner-midrange-l@midrange.com]On Behalf Of dkeck@idt.net > Sent: Thursday, September 21, 2000 6:25 AM > To: midrange-l@midrange.com > Subject: API's & Compiling to Prev Release > > > I am developing on V4R4, compiling to V3R2, and relying on the compiler to > ensure that the code will in fact execute on a V3R2 box. Will this approach > work ? I am particularly concerned about API support ... if I reference an > API, bindable or otherwise, will the compile process let me know if the API > is > not available at the target release ? > -DaveK > > --------------------------------------------- > This message was sent through IDT. > http://www.idt.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 > +--- > > +--- > | 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 > +--- > +--- | 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.