No, I had one user who would press enter a few times instead of just once.
The job was reading and writing to DDM files so processing took 2 or 3
seconds. While it was processing her enter key strokes would get fed in to
the program, in the wrong locations, and it would fail. Took a while to
find this problem, because no one else had problems with the program. And
when she was demonstrating for you, She worked slower and it wouldn't
happen.




From:
"Wilt, Charles" <WiltC@xxxxxxxxxx>
To:
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Date:
08/14/2008 01:16 PM
Subject:
RE: Auto advancing display screen



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [
mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Bob P. Roche
Sent: Thursday, August 14, 2008 1:40 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Auto advancing display screen

There is a way to make the screen "auto refresh" but be careful, It is
on
a timer that you set and removes the keyboard buffer. Function keys and
the enter key when pressed at the wrong time will cause program errors.


If by "removes the keyboard buffer" you mean that data typed onto the
screen by a user is lost, then
you are incorrect.

You can set things up so that the screen gets refreshed without losing
anything the user had already
typed.

http://systeminetwork.com/article/display-file-magic-multiple-device-support-part-i


"Following INVITE is the PUTOVR (Put with Explicit Override) keyword.
PUTOVR is not necessary for
effecting a time-out, but using it is often desirable so that when your
device times out you don't
lose any input you've already typed. PUTOVR works in conjunction with the
OVRDTA (Override Data) and
OVRATR (Override Attribute) keywords. You typically use these keywords to
reduce the amount of data
sent to a display when the record format you're writing is already on the
display. When PUTOVR is in
effect, the system sends to the display only those fields for which OVRDTA
is also in effect. OVRATR
works in a similar fashion for display attributes. In the example, you can
see that indicator 11
conditions OVRDTA. I can therefore write the record with indicator 11 set
off so that the system sends
no data to the display when I write the record again after the time-out
and anything already typed on
the display remains there."


HTH,

Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307
wiltc@xxxxxxxxxx




This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to
read, print, retain, copy or disseminate this communication without the
consent of the sender and that doing so is prohibited and may be unlawful.
Please reply to the message immediately by informing the sender that the
message was misdirected. After replying, please delete and otherwise
erase it and any attachments from your computer system. Your assistance
in correcting this error is appreciated.

This thread ...

Follow-Ups:
Replies:

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

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