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



This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Looks like non-subfile windows with overlay to me.see below code from IBM
site.

*** Note:  But when  I asked about "overlay" I did assume(ass of u + ME)
subfile window, sorry,  I use subfiles even on my selection windows(Opt 1by
cust,2 by Cust name,3by order, etc.) with mouse button select or key board.
This also allows me to add options to windows by just adding new record to a
control file instead of program change. Example: Have subfile windows with
sort selections for other window subfile views .Control file not only use to
display posible sort selections but also controls SQL sorting, LF create ,if
need be first time, and record selections for subfile window views. Only
have to add a record to control file.

http://publib.boulder.ibm.com/pubs/html/as400/v5r1/ic2924/index.htm
<http://publib.boulder.ibm.com/pubs/html/as400/v5r1/ic2924/index.htm>


2.4.14.1.1 DDS Full-Screen Display and Window Definitions

The following DDS defines the initial display and two windows used in the
scenario:


A*------------------------------------------------------------------------*
     A* DISPLAY FILE - DEMOFM

A*------------------------------------------------------------------------*

A*------------------------------------------------------------------------*
     A* FILE LEVEL KEYWORDS

A*------------------------------------------------------------------------*
     A                                      DSPSIZ(24 80 *DS3)
     A                                      HELP
     A*

A*------------------------------------------------------------------------*
     A* RECORDS USED IN DEFINING INITIAL DISPLAY

A*------------------------------------------------------------------------*
     A          R INITIAL
     A                                      CA03(03)
     A                                      CA04(04)
     A                                      CA06(06)
     A                                      CA07(07)
     A                                      CA12(12)
     A                                      CLRL(*ALL)
     A                                  3 28'NONWINDOW DISPLAY RECORD'
     A                                  6  1'FLD #1:'
     A            FLD48         30A  B  6  9
     A                                  6 43'FLD #2:'
     A            FLD49         15A  B  6 51
     A                                 10  1'FLD #3:'
     A            FLD50         30A  B 10  9
     A                                 10 43'FLD #4:'
     A            FLD51         15A  B 10 51
     A                                 23  1'F3=Xxxx'
     A                                 23 13'F4=Xxxxxxxx'
     A                                 23 29'F6=Xxxxx Xxxxx'
     A                                 23 48'F7=Xxxx'
     A                                 23 59'F12=CANCEL'
     A*

A*------------------------------------------------------------------------*
     A* RECORDS USED IN DEFINING WINDOW1

A*------------------------------------------------------------------------*
     A          R WINDOW1                   WINDOW(7 3 11 33)
     A N01                                             WDWBORDER((*COLOR
GRN))
     A  01                                              WDWBORDER((*COLOR
RED))
     A                                              2 13'WINDOW #1'
     A                                              4  2'CUSTOMER NO.'
     A            FLD1           6A  O  4 15
     A                                             4 22':'
     A*
     A          R REC2WIN1                  WINDOW(WINDOW1)
     A                                                   OVERLAY
     A                                                   CA12(12)
     A                                          10  2'F12=CANCEL'
     A*
     A          R REC3WIN1                  WINDOW(WINDOW1)
     A                                                    OVERLAY
     A                                             6  2'NAME:'
     A            FLD2          24A  B  6  8
     A                                              7  2'ADDRESS:'
     A            FLD3          21A  B  7 11
     A                                              8  2'PHONE:'
     A            FLD4          23A  B  8  9
     A*

A*------------------------------------------------------------------------*
     A* RECORDS USED IN DEFINING WINDOW2

A*------------------------------------------------------------------------*
     A          R WINDOW2                   WINDOW(9 25 11 32)
     A*
     A                                             2 12'WINDOW #2'
     A            FLD5          22A  O  4  6
     A            FLD6          25A  O  5  4
     A            FLD7          25A  O  6  4
     A            FLD8          25A  O  7  4
     A*
     A          R REC2WIN2                  WINDOW(WINDOW2)
     A                                                  OVERLAY
     A                                                   CA12(12)
     A                                            10  8'Xxxxxxx :'
     A            FLD9                     6A  B 10 18
     A*

A*------------------------------------------------------------------------*

But I'm not a super coder so please explain the following more:

KEEP-Use this record-level keyword to keep the display from being deleted
when the display file is closed. The entire display is kept if any of the
records on the display have KEEP specified. The default causes the entire
display to be deleted when the file is closed.

In addition, the name of the first, uppermost record on the display that has
the KEEP attribute is saved by the OS/400 program for possible use by
subsequent programs. The name kept can be used by a subsequent program that
does not specify a record name on its first input operation. This keyword
enables you to leave data on the display for review after your program ends,
or use that data as input for subsequent programs.

USRRSTDSP-Use this record-level keyword on a window record to specify that
the application will manage the display. Window records are not
automatically removed. If this keyword is not specified, the system saves
and restores the underlying display when a window record is displayed.
The following example shows how to specify the USRRSTDSP keyword.

|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+.
...8
     A          R APPRCD
     A            FIELD1        10A  O  5 40
     A            FIELD2         5S 0B  6 45
     A          R WINDOW1                   WINDOW(6 15 9 30)
     A  25                                                USRRSTDSP
     A            FIELD1         5A  B  2  2
     A            FIELD2        20S  B  8  5
     A

In this example, suppose APPRCD is already on the display. If indicator 25
is set on when WINDOW1 is written to the display, the system does not save
the underlying display (which contains APPRCD). When the user exits WINDOW1,
the application must restore the underlying display, possibly by rewriting
APPRCD to the display. Note: With USRRSTDSP, there is no limit on the number
of windows. The limit is 12 without using the USRRSTDSP keyword.

Is it because the two work hand and hand??

Just trying to understand and learn more. Could you provide an example
Carel? Hope this wasn't to much for post

Thanks

Bill Hopkins

 <mailto:Bhopkins@saurerinc.com> Bhopkins@saurerinc.com





----------------------------------------------------------------------------
---

-----Original Message-----
From: Teijgeler [ mailto:coteijgeler@chello.nl
<mailto:coteijgeler@chello.nl> ]
Sent: Wednesday, August 21, 2002 3:33 PM
To: rpg400-l@midrange.com
Subject: Re: Keep background screen on display when using window keyword


John,

ASSUME is not needed on a full screen display.
In the window display put in the DDS keywords KEEP and USRRSTDSP. Windows do
not need OVERLAY, unless it contains a SFL, but then that keyword should not
be in the record format, that defines the window.

Hopes this helps.

Regards,
Carel Teijgeler.

*********** REPLY SEPARATOR  ***********

On 21-8-02 at 14:40 JMBauman@wardtrucking.com wrote:

>I have a problem with loosing my initial screen when I display several
>sequential windows on top of the initial display.  Here is the program
>flow:
>
>pgmA displays a full screen
>pgmA calls pgmB
>pgmB displays a window.  the user makes a selection and pgmB ends,
>returning to pgmA
>pgmA calls pgmC based on a parm received from pgmB
>pgmC displays window
>
>When pgmC displays it's window, the screen that pgmA displayed initially,
>goes away.  I am using the RSTDSP=*yes on the screen in pgmA, and I am
>using the ASSUME keyword in all 3 display files.
>
>I have used windows in other applications and have had no trouble.  Is my
>problem coming from the fact that 2 displays are being written over the 1st
>display without any "rewrite" of the 1st display in between them?
>
>Any suggestions would be appreciated.
>
>Thanks,
>John
>
>_______________________________________________
>This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
>To post a message email: RPG400-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
<http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>
>or email: RPG400-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/rpg400-l
<http://archive.midrange.com/rpg400-l> .




_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
<http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l
<http://archive.midrange.com/rpg400-l> .




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.