× 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.



rpg400-l-request@xxxxxxxxxxxx wrote:

>   2. CPF4737 and INVITE Keyword (Andy Hautamaki)
>
>I have the following on my display file;
>
>INVITE keyword.
>
>I have setup the display file to have a waitrcd of 600.
>
>In my RPG module I have setup the display file with the following;
>
>MAXDEV(*FILE)
>INFDS(DS010)
>
> D DS010           DS
> D  @@STAT           *STATUS
>
>Then I'm checking for this after each write and read to the display file;
>
>if @@stat = 1331;
>
>My problem is if  press {Enter} twice very quickly  the module gets a 
>CPF4737.
>
>I've tried a exfmt(e) instead of a write and read but when I do that I can't 
>get the timeout. @@stat = 1331.
>
>How do I allow for tracking for the waitrcd on the display file being 
>reached as well as handling the quick multiple entries?

Andy:

I'm not certain what all goes on in your code, but you might try one thing -- 
turn off keyboard buffering before doing any display I/O.

Review the Set Keyboard Buffering (QWSSETWS) API in the Workstation Support API 
group. Turn buffering off at the beginning, do your DSPF processing, and turn 
it back on at the end.

Or better... Call the Query Keyboard Buffering (QWSQRYWS) API at the beginning 
to determine the current state and reset it at the end if necessary.

Just a guess from what you've supplied.

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.