|
3. If the user has been pressing keys on the "waiting" screen, the buffered keystrokes are passed to this screen.
The screen that's displayed while you wait on the data queue... does it have the INVITE keyword in the DDS? If so, the keystrokes won't be in the keyboard buffer, they'll be in your program's input buffer, waiting for you to read them.
It should just be a matter of reading the screen to clear them out of the buffer in that case.
If you haven't used the INVITE keyword, then the data is indeed in the keyboard buffer -- and that's harder to deal with. Keep in mind that the keyboard isn't directly attached to the iSeries. It's attached to a terminal or PC that's a separate machine. Since every make of terminal or every PC software can potentially work differently. I know that back in the day some manufacturer's considered it a "feature" to buffer keystrokes even after they were told to clear the buffer, since it enabled an extra type-ahead capability. No idea if that paradigm survived to the current day, however.
You might try sending the clear unit 5250 code (I know, a bit drastic) and see if that helps at all.
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.
midrange.com
