Re: Display File I/O Buffer

[Bruce Vining <bvining@xxxxxxxxxxxxxxx>]

Vern,

The second approach I refered to earlier is similiar to Open Access in that
data, indicators, and status information is exchanged. The application data
however is not formatted exactly like the IO buffer (as it would be when
using Open Access). It's also a different approach from Open Access in that
no change for HANDLER (or even recompile of the WORKSTN program for that
matter) is needed. It is, however, only applicable to WORKSTN while Open
Access is much more generic in nature.

Bruce

On Fri, Apr 8, 2011 at 6:00 PM, Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:

> Bruce
>
> Would the second approach be basically what Open Access for RPG is
> doing? It does provide all the data, with indicators and some status stuff.
>
> Again, not for the faint of heart - I'm glad I only had to deal with
> DISK files in the handler I wrote!
>
> But having said that, I suggest Jason take a look at OAR.
>
> Vern
>
> On 4/8/2011 4:24 PM, Bruce Vining wrote:
> > There are several ways to intercept the 5250 I/O buffer. Some provide the
> > raw 5250 data stream, others provide the application data (generally)
> > without the the 5250 orders. I would not consider any of them for the
> faint
> > of heart. I have worked with all of the various interfaces at one time or
> > another. If you would like to pursue this you can contact me offline. You
> > certainly do not need any product other than the i operating system.
> >
> > Bruce Vining
> >
> > On Fri, Apr 8, 2011 at 1:09 PM, Jason Abreu<
> > jason.abreu@xxxxxxxxxxxxxxxxxxxx>  wrote:
> >
> > > Has anybody tried to intercept the display file I/O buffer?  I am
> > > interested in the process.  I know it's accomplished by IBM products,
> > > such as WebFacing, but was wondering if it was possible outside of a
> > > specific product offering.
> > >
> > > Thanks,
> > >
> > > --
> > > Jason Abreu
> > > Abreu Innovations, Inc.
> > > jason.abreu@xxxxxxxxxxxxxxxxxxxx
> > > http://www.abreuinnovations.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.
> --
> 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.