Re: Green screen timeout handling

I don't remember the exact details, but you can attach a data queue to the display file, then after writing the display format with invite, sit on a data queue receive for whatever timeout period you want.  If the dtaq times out, you get no data and display your message.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 7/3/2021 3:13 PM, Javier Sanchez wrote:

Hi everyone,

I have been boxing around with a very simple and dumb stuff that has to do
with when you send your output to your display file in an RPGLE program,
you are required to wait, say, 30 seconds for the user to type in only two
small fields of information from a customer who's on the phone. If the
user gets longer than that amount of time, they will be notified that they
are taking too long a period of fair enough time to do so as it is critical
information being taken on the phone line.

I have tried many things, like, adding the INVITE keyword on the record
format, and then to issue first a WRITE and then a READ(E) opcode, so that
I can then, either: (1) test the %STATUS opcode whether it returned 01331
value, or probably the feedback I/O area structure for that file in
particular. The latter should show me a value of major return code of 03
and a minor return code of 10.

But when I execute it, it simply doesn't run the timer and it just sits
there infinitely, so my timer is being ignored. While running this
program, I first close the display file. Then I use the QCMDEXC API to run
a OVRDSPF with a parameter like WAITRCD(30) which is run-time built using a
parameter variable, and then reopen the display file before I issue the
WRITE and READ opcodes.

What could I be possibly missing?

Thanks