|
I said:
NOTE: You can't try to fool the system by specifying PUTOVR at the file level and OVRATR and OVRDTA on another field conditioned with the same error indicator (i.e., 53) into which you would write "OVER" or "UNDER" and expect that to be sent to the workstation along with the error. When the documentation says ERRMSG and ERRMSGID are the only things processed they mean it.
Pseudo code: do until exit WRITE screen READ screen check for errors if over-limit set on indicator controlling OVER/UNDER write screen set on indicator controlling error message endif enddo
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists
http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.