Re: Programs that didn't need to be written - ScreenSaver5250

Thank you guys for your replies.

Having said the below, is there now a process in OS400 that puts a device into screen saver mode, somehow locks a screen?
Thats what I was really asking.


My response to replies is as follows.

I have been way way back on S/3 CCP,  used INVITE INPUT to allow the user to enter data into a display.
Then one did a READ operation to get the entered data.

As for auto refreshing, surely only a write operation is needed.
But I think I see now, the issue is how long to wait between auto refreshes.

Again INVITE and WAITRCD seems to me to apply to MRT programmimg.
I never programmed MRT on S38 AS400 nor Sys i, but I did on S/3.
I never needed to do auto refresh, but I almost always coded F5-Refesh.

Having read the document in the link below I see it applies to the waitrcd() parameter.  I never used waitrcd.
I suppose I always used the default wait time.


From the manual
----
Maximum record wait time (WAITRCD)
Specifies the number of seconds the program waits for the completion of a read-from-invited-devices
operation to a _*multiple device file*_ in a high-level language program. Refer to the high-level language
reference manual to determine when a file is treated as a multiple device file. The program performing
the read operation waits for the input form all invited devices currently accessing the file. If a record is
not returned from any of the invited program devices in the specified amount of time, a notify message is
sent to the program. This parameter has no effect on an input operation directed to a single device.
*NOMAX
There is no limit on the time the system waits for the completion of the operation.
*IMMED
The program does not wait. If a record is not available when the read-from-invited-devices
operation is done, a notify message is sent to the program.
integer
Specify the maximum number of seconds that the program waits. Valid values range from 1
through 32767 seconds
----

Frank



On 16/08/2022 1:24 pm, Charles Wilt wrote:

Not sure where you've been...but INVITE has long been a key part of an
auto-refreshing screen.

Further down in the docs..

On a read operation from invited devices operation to a display file, only
data from devices with an outstanding invite operation are considered. The
input operation waits for data from any of the invited devices. (See the
WAITRCD parameter on the Create Display File (CRTDSPF) and Change Display
File (CHGDSPF) commands.) If none of the invited devices responds before
the wait time ends, a notify message is sent and no data is returned. All
invited devices remain invited.

Also see this IBM article
https://www.ibm.com/support/pages/ile-rpg-example-screen-auto-refresh-and-alarm-usage

Charles

On Mon, Aug 15, 2022 at 4:40 PM Frank Kolmann <Frank.Kolmann@xxxxxxxxx>
wrote:

Quite confused. Not sure how INVITE would work as a screen saver.

I was never aware that OS400 disconnected inactive jobs.

INVITE is used with ACQ op-code for multiple device coding. I rarely
used MRT programs,
INVITE is used with UDDS to get input from the device, also rarely used.

From the manual
-----
INVITE (Invite) keyword for display files
Use this file- or record-level keyword to invite the device for a later
read. To send an invite to a specific
device, your program sends an output operation to the device with the
INVITE keyword in effect. If the
record format used has output-capable fields, the data is sent to the
device before the device is invited.
This keyword has no parameters.
INVITE must be used if the display file can have multiple _acquired_
devices and your program does read
from invited devices operations.
-----

Frank

On 15/08/2022 11:41 am, Chris Pando wrote:

I use this program to keep the system from thinking my job is inactive,

and

disconnecting me. A recursive implementation of quicksort, it uses the
INVITE keyword to update the screen every n seconds. It also uses a
Fisher-Yates shuffle, with the bindable procedure CEERAN0.

http://www.brilligware.com/cp1329.html

Chris Pando
chris@xxxxxxxxx
www.brilligware.com - Home to MineSweeper5250

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com