Re: IBM i "Open I/O" Architecture

Mark,

I was going to say something similar to what you have asked, as it seems like a better approach, and would not require any changes to existing code!

But Jon then said it had to come out of Toronto, and quickly, which probably means no to OVR* commands being changed, and is why I didn't bother... :(


----- Original Message ----- From: "Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, October 21, 2009 2:39 PM
Subject: Re: IBM i "Open I/O" Architecture

Hi, Jon:

Why is this idea being presented as only an RPG IV enhancement?

I think it would be far better to provide this capability in the "base"
OS, namely, via a mechanism such as the "override" commands, so that you
could do something like this:

OVRDBF FILE(MYFILE) PGM(MYLIB/MYPGM)

This would then tell the system to call the named program for all
file-related activity for this file (open, read, write, close, etc.).
Of course, a suitable parameter list structure would need to be defined
for such an "exit" program, but conceptually this should be able to work
similar to triggers. This would work in a manner similar to RPG's
SPECIAL files, but would work for all opcodes, including EXFMT.

I think this facility should be supported on all of the OVRxxx commands
(OVRDBF, OVRDSPF, OVRPRTF, etc.) -- so that it would be possible to
"redirect" any existing file to another device (or the web).

This kind of approach would enable such an enhancement to work with any
supported language or compiler.

What do you all think?

Thanks,

Mark S. Waterbury

> Jon Paris wrote:

Might I suggest we more this to the RPG400 list where the RPG
developers are more likely to see it.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.