You could try STRCPYSCN into a file, then search the file for the

If there is something specific about a screen that confirms the data entered
was accepted, then this would be a good screen to start from. Find this
screen and work out where the data is relative to it.

I would suggest that everything it 'extracts' is checked and validated
before taking it as accurate.

Alternatively you could look into writing a VB program that accepts the data
and then 'writes the keystrokes' both to the AS400 and the mainframe
application. This of course will be full of potential problems if the PC
data is not validated.

Brendan Bispham

~ We're connected to a mainframe system using the AS/400 which is
~ emulating a 3471 controller.  We do a passthrough session to log onto
~ the mainframe using 3270 sessions.  We do data entry into the remote
~ system, and redundant entry of the same info into our AS/400.  The
~ mainframe system is maintained by the state, and we have no access to
~ ad-hoc reporting with the data (nor directly to the files themselves).
~ That's why we also maintain the same (and a bit more supplemental)
~ information locally.
~ What we want to do is eliminate the redundant entry by somehow
~ monitoring the passthrough session and populate our database from the
~ data gleaned.
~ How should I approach this task?  What facilities on the 400 would I use
~ to accomplish it?  Is there a 3rd party product that could help me get
~ this done?

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
| To subscribe to this list send email to
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].