RE: Time limits in RPG

This problem should go away if you only has one INVITE active and it is
the last record format that you are displaying.

For example: 
If you have 3 record formats: FMT1, FMT2 and FMT3 and all of them have
INVITE keywords,
You'll need to use indicator to control the invite keyword in each
format.  Make sure the only last format's (last write) INVITE is *on.

Write FMT1;
Write FMT2;
Write FMT3;  // make sure only this INVITE is *on 
Read  MYDSPF

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche
Sent: Tuesday, November 14, 2006 9:13 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Time limits in RPG

One other thing to watch for in the first version using WAITRCD and ithe
INVITE keyword. Using this works great from my testing, except it
removes the keyboard buffer. I had to stop using it because one user
kept getting impatient and pressing the enter key repeatedly after each
screen. It took a while to figure out why the program only failed for
her. RPG doesn't like to get a screen read event passed to it in the
middle of the processing logic. we were sending data to a remote system
in real time with the logic so after a certain screen there may be a 1
or 2 second delay.