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


  • Subject: RE: DDS Timeout
  • From: Chris Bipes <rpg@xxxxxxxxxxxxxxx>
  • Date: Tue, 23 Nov 1999 14:08:07 -0800

We create a data queue for each display.  id dqlib with hold a data queue
for dev dsp01 named, yes you guessed, dsp01.  It is easy to get the job name
from the program status data structure and read that data queue.  If you
only want one data queue, use a keyed data queue with the job number as the
key.  But then you cannot attach your display file to the data queue if it
is keyed.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

*Note to Recruiters
Neither I, nor anyone that I know of, is interested in any new and/or
exciting positions. Please do not contact me.


-----Original Message-----
From: Scott Klement [mailto:infosys@klements.com]
Sent: Tuesday, November 23, 1999 12:47 PM
To: RPG400-L@midrange.com
Subject: Re: DDS Timeout


The ability to "time out" on a screen isn't actually a feature of RPG
but is rather a feature of the display files.  The same concepts for
timeouts will work in RPG III or CL or (afaik) any HLL.

To change the WAITRCD parameter, you can do:
     CHGDSPF FILE(xxx) WAITRCD(xxx)
 or  OVRDSPF FILE(xxx) WAITRCD(xxx)

These are CL commands, so you can do them from a seperate CL program,
or you can use QCMDEXC (or whatever else you prefer) to do them in
your RPG.

The more versatile way of doing it is to use data queues, INSTEAD of
the WAITRCD parameter.   This works very well, and allows you to
adjust the timeout value on-the-fly.

If you're running several copies of the same program, and want to keep
each data queue seperate, the easiest way is to put the data queue in
the QTEMP library (QTEMP is different for every job)

Your program would do something like this:
        1) Create a data queue in QTEMP for this job.
        2) OVRDSPF FILE(xxx) DTAQ(QTEMP/xxx)
        3) Open the display file
        4) Write a record to the display file with FRCDTA and INVITE
              DDS keywords.
        5) Wait for an entry to appear on the data queue, with a
              timeout value.
        6) If an entry appears before the timeout, read the screen,
              and process the input.
        7) And so on...

Or did you mean that you want the program to control multiple
terminals and to be able to determine which of the terminals
pressed enter?

If you need more info, just reply and ask questions...  I could even
give you example code if you need it.

HTH


"Richard Hartman" <r_hartman@hotmail.com> wrote:
> I was searching through the Midrange Archives looking for informatio
>  on
> RPG's "Timeout" feature. When I found Pete Hall's thread, dated Sat,
>  13 Dec
> 1997, with the title "DDS Timeout", where he describes how to use a
>  data
> queue to change the WAITRCD parameter.
>
> I would like to find out how to change the WAITRCD parameter, but I
>  weary
> about using the data queue method described. If multiple users were
>  running
> the program that use's the data queue, and one of them timed out, ho
>  can
> you tell which program timed out?
>
> If anybody has any information about the above questions, or any
>  information
> at all about the "Timeout" feature with RPG IV, it would be greatly
> apreciated.
>
> Richard Hartman
> Email:  richard.hartman@brctsg.com
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
> +---
> ¦ This is the RPG/400 Mailing List!
> ¦ To submit a new message, send your mail to RPG400-L@midrange.com.
> ¦ To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> ¦ To unsubscribe from this list send email to
>  RPG400-L-UNSUB@midrange.com.
> ¦ Questions should be directed to the list owner/operator:
>  david@midrange.com
> +---
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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.