|
Thanks for your perspective, Jon. When Ian Jarman introduced Open I/ O, did you get the impression that it was only an RPG language feature, or that IBM would be opening up its I/O architecture?
While an RPG program may have no idea beyond the display file I/O buffer, the system-level routines that are subsequently evoked by display file writes and reads, do. If Open I/O is more of an architecture than a language feature, then extended display file meta data could be included in the Open I/O interface - just a speculative thought.
In an earlier comment I inquired about whether the use of Open I/O might source code changes, and some speculated that it would - that it's intended for new types of applications, rather than a next generation of screen scraping - which may be fine. Personally, I prefer the idea of implementing Open I/O through additional keywords on the "F" spec, rather than something like an external trigger, because that would give the programmer more flexibility in using it for specific purposes, rather than globally - like triggers.
I like to think that Open I/O is more of an architecture, and that IBM will be opening it's remarkably streamlined interface for more purposes than the traditional ones.
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.