×
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.
You can trap that the error occurred and look for the proper error code
for a time out code.
I found this on another site.
After the READ, check the *STATUS field from the display file information
data structure (RPG) or %STATUS (RPGLE). If the value is 01331, then the
WAIT time expired and control returned. If it is NOT 01331, then the user
caused control to return by pressing a function key.
From:
Luke Gerhardt <lgerhardt@xxxxxxxxx>
To:
rpg400-l@xxxxxxxxxxxx
Date:
08/05/2010 02:26 PM
Subject:
Re: Refreshing a kiosk screen
Sent by:
<rpg400-l-bounces@xxxxxxxxxxxx>
I have never used the *pssr either. Perhaps that's an optional way to
see if your screen timed out or if you received user input?
On 8/5/2010 2:45 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
date: Thu, 5 Aug 2010 19:45:07 +0100
from: "John McKay"<jmckay@xxxxxxxxxxxxxxxx>
subject: Re: Refreshing a kiosk screen
I have an example somewhere too.
If memory serves, I did not have to use the *pssr.
Read / write was used, not exfmt, in the program and the waitrcd was
set on
the compiled dds. This was compiled along the lines of a ICF dds file.
INVITE was used in the DDS.
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
