× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



If I read your question, to capture screen data, let's also document the
simplest method of data capture of a screen into a file.

The minimum code to insert would be the following, which I use for test
programs, and a record and playback of batch&SOA functions. Simple
create a structure based on the screen format, and push the structure
into a file.

FCUDPAscreenCF E Workstn
F Include(ipGPainq3 )
F Prefix( painq3 )
D ScreenFields...
D E DS EXTNAME(cudpascreen:ipgpainq3 )
D Prefix( painq3 )

Exfmt ipGpainq3 ;

exxRecordFlds( ScreenFields ) ;


If all you are going to do is "maybe" review this output "only " if
there is a problem, capture the data now, and don't worry about parsing
it out until it is time to analyze it. At that time, you can use the
structure again to parse the fields back onto a report or screen, after
you select your records.

Obviously, you will want to include user, time and date in the collected
data, and getting that onto the output file can be done with a trigger
pgms, or journaling the collection file, or what I do - pass the
structure to another program whose purpose is to write to the output
file while adding the user-time-date-stamps.

This other pgm has a single parm - 1760 bytes which will handle any
screen structure
The prototype for my writer is

D exxRecordFlds...
D PR
D EXTPGM('CUGPAWRITE')
D ParmList 1760 Varying CONST

(This is stripped-down code to demonstrate the simplest example)

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.