|
You can't see the forest through the trees. Here we thought you were trying to find out what the user was entering to see how they were using your application and how either program changes or training would make for a better transaction. STRCPYSCN SRCDEV(*REQUESTER) OUTDEV(*NONE) OUTFILE(ROB/CPYSCN) Gave a nice "audit". The only thing missing might be if they hit F<something> and your screen allows any Fkey and then your program checks an aid byte or something to determine what Fkey was pressed. But I'd start out with that to see if it would work for you versus the "trees" you are looking at. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.