× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.