Re: Message Waiting Indicator

[Booth Martin <booth@xxxxxxxxxxxx>]

For a kiosk application I suggest:

****

*** Special notes concerning the auto-refresh feature. The goal is to * 
* have the screen be auto-refreshing on a user-selected time period. * * 
At the same time, we need the user to be able to interrupt the * * cycle 
at will. * * 1-The *DSPF must have the INVITE keyword, and if there is 
to be a* * subfile then INVITE must be conditioned with an indicator. * 
* That indicator must be off when clearing and filling the * * subfile. 
Tip: Use a unique indicator. * * 2-Look at the F-spec. You need "workstn 
maxdev(*file)" * * 3-The RPGLE program must use WRITE/READ combinations. 
* * --->Do not use EXFMT. <----------------------------- !!!!! * * 4-The 
conditioning indicator must be on when doing a WRITE/READ. * * 
5-Remember the rulz: Always WRITE the record and READ the file. * * 
6-Use a MONITOR/ON_ERROR/ENDMON block on all WRITE/READ pairs. * * 7- 
wCmd = 'OVRDSPF FILE(DQMON10D) WAITRCD(' * * + %char(%int(wMinutes * 
60)) + ')'; is what makes it work.* * 8-When the screen times out, MUST 
set off conditioning indicator * * and then WRITE the screen again, so 
that the INVITE keyword * * is not active. * An example is: 
http://www.martinvt.com/SQL_-simple-/Dataque_Monitor/dataque_monitor.html **

****

On 7/8/2020 6:20 AM, Rob Berendt wrote:
> I am curious as to whether or not this screen was waiting on input.  Most people use EXEFMT to display screens.  This is because they write some stuff out, then read some input from the user.  However if you are only display kiosk information and are not waiting for user input then forego EXEFMT and just WRITE the screen as is your wont.
>
> Rob Berendt