Re: Green screen timeout handling

Hi, Thank you Don and Reeve.

Yes, this program is being updated in order to do that. The original open
is implicit, so I added the invite at the record level, not the file
level. Maybe I should try that.

The other changes consist of getting the timeout seconds parameter from a
table, and then I do this:

1. Close the display file with *CLOSE theFile*
2. Call *QCMDEXC *with a *OVRSPF FILE(theFile) WAITRCD(30)* command string
which is dynamically built within the program.
3. Reopen the file with *OPEN theFile*.

Then, as I saw in an example posted out there in some web page, yes, you
first WRITE the record format and just immediately READ it. Then you test
the %STATUS return value or else you can also test the Major and Minor
return codes in the feedback I/O data structure that you declare at the
file's "F" sheet.

This is the code of my local procedure in the program. I first try to
retrieve a value for the timeout seconds to wait:

waitRecord = getWaitRecord();
IF waitRecord > 0;
saveFields();
*ovrDspf(waitRecord);*
restoreFields();
ENDIF;

Then, the *ovrDspf()* function is like this:

DCL-PROC ovrDspf;
DCL-PI ovrDspf;
parm_in_wait_time int(10);
END-PI;

//*** Close the display file to issue the override command ***//
CLOSE SCREENF;

//*** Setup timer for WAITRCD and use it with the OVRDSPF ***//
//*** command. ***//
commandString = 'OVRDSPF FILE(SCREENF) WAITRCD(' +
%char(waitRecord) + ')' +
' OVRSCOPE(*JOB)';
commandLength = %len(%trim(commandString));

MONITOR;
QCMDEXC(%trim(commandString): commandLength);
ON-ERROR;
ENDMON;
OPEN SCREENF;
END-PROC;


Then come the WRITE and READ opcodes. All of that is very clearly made but
no luck. I think I'll try writing a small copy of the program and call it
from the original one.

Any other suggestions are welcome.

Really appreciate your assistance.
Thanks again.