Re: 3270 screen capture

[Alison Herman <alison@xxxxxxxxxxxxxxxx>]

I have been looking at that code this morning trying to figure out what
to modify etc...  Thanks for the help.


eric.delong@pmsi-services.com wrote:
> 
>      Alison, that util in MC captures a display screen and passes is
>      through a data queue to a receiving program. As written, it
>      captures 1920 bytes (24x80) so it would need to be modified to
>      capture (27x132). Onve you receive the data, you could parse it for
>      whatever you're looking for.
> 
>      Just an option.
> 
>      Eric DeLong
> 
> ______________________________ Reply Separator 
>_________________________________
> Subject: Re: 3270 screen capture
> Author:  <MIDRANGE-L@midrange.com > at INET_WACO
> Date:    10/15/98 9:12 AM
> 
> Want we need to do is capture the data on the screen, parse it out into
> fields to populate an AS/400 database.  The 3270 is using an SNA
> connection and can be started from either a PC or dummy terminal.
> 
> Thanks for info so far, I'm checking it all out.
> Alison
> 
> 
> bvining@VNET.IBM.COM wrote:
> >
> > I'm not sure what sense of screen capture you are looking for, but an
> > application program can appear as a 3270 device to another system using
> > the 3270 device emulation APIs.  For SNA communications the SNA Upline
> > Facility Programming manual describes the programming interfaces.  For
> > BSC the S/38 3270 Emulation Reference manual describes the interfaces.
> >
> > For maximum fun one could also use the standard 3270 emulation commands
> > and capture the screens by way of the Virtual Terminal APIs found in
> > the System API Reference (and running the 3270 session from a virtual
> > 5250 session).
> >
> > Bruce Vining
> >
> > >
> > >Hi All!
> > >
> > >Does any one know how to do a screen capture on an AS/400 running a 3270
> > >emulation session to another system?
> > >
> > >Thanks in advance.
> > >Alison
> > >
> >
> > +---
> > | 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
> +---
+---
| 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
+---