|
>The slow rate of adoption, it could be argued, >is a testament to how good that old, legacy >stuff really is. 6 character upper case variables All variables are global 256 byte character fields 9 decimal place numeric fields Short array names 9999 record length 9999 array elements 254 subroutine maximum 50 files No Date/Time datatype No parameter validation Admittedly, only local storage is an ILE benefit, but I would think that the slow adoption rate of simple RPG IV has little to do with the "goodness" of RPG III. Maybe I'm too narrowly focused on individual programs rather than an entire application? I can't imagine cost-justifying an application re-write *solely* to convert to ILE technology, whether the legacy application is good or not. But if "...the higher ups are talking about doing a rewrite of our system...", then I find it difficult to justify deliberately using hobbled technology when we've already paid for the good stuff. I personally have implemented new ILE modules/programs/service programs that are modifications of existing OPM programs. Thusly creating a mixed environment for this application. My mods are somewhat isolated, and I was able to roll them out as a unit, not disturbing the overall application. Do you think this is unusual? I mean, do you think it would be very difficult to gradually deploy ILE portions as modifications are made to legacy applications in your company? Your note is definitely food for thought. Buck +--- | 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.