|
You will need to KEEP keyword to retain your previous display. This keyword needs to be in the executing display file. You may want to use the ASSUME keyword as well. Here's the V4R4 DDS manual description for ASSUME. 3.14 ASSUME (Assume) Keyword Use this record-level keyword to specify that the OS/400 program is to assume that this record is already shown on the display when this file is opened. Such a record would also be defined, with the KEEP keyword, in another display file. That other display file would be closed before this file (in which you are specifying ASSUME) is opened. This keyword has no parameters. Specify the ASSUME keyword for at least one record format within the display file so that the OS/400 program does not erase the display when the file is opened. In addition, specify the OVERLAY keyword with the ASSUME keyword to prevent the OS/400 program from deleting the display when your program sends the first output operation after opening the file. If you use the ASSUME keyword, at least one field in the record must be able to be displayed. If more than one record with the ASSUME keyword exists, they must occupy unique display lines. For the OS/400 program to process the data correctly, your program must specify the record format name containing this keyword. The ASSUME keyword is not needed if the record format you are defining is in a shared file (SHARE(*YES)) parameter specified on the Create Display File (CRTDSPF), Change Display File (CHGDSPF), or Override with Display File (OVRDSPF) command). This keyword cannot be specified with any of the following keywords: +------------------------------------------------------------------------+ ¦ ALWROL ¦ SLNO ¦ ¦ CLRL ¦ USRDFN ¦ ¦ SFL ¦ USRDSPMGT ¦ +------------------------------------------------------------------------+ A warning message is issued at file creation time if the ASSUME keyword is specified on a record with the DSPMOD keyword. At run time, the ASSUME keyword is ignored when the display mode changes. A file with the ASSUME keyword will be opened to the display size of the file with the KEEP keyword. Option indicators are not valid for this keyword. ----- Original Message ----- From: <BillsVilla@aol.com> To: <RPG400-L@midrange.com> Sent: Wednesday, May 24, 2000 9:08 PM Subject: Question regarding SDA WINDOWS clearing the screen when displayed ... > Here's the situation. I have just recently started using the window feature > in SDA and love it. My only problem is that if I have a CL program for a menu > and I call an RPG or even another CL program to control the features of the > window it clears the screen. > > Does anyone know how to fix this so it always "overlays" the menu? At this > time I have rigged it so the RPG program controlling the window does a WRITE > for the menu display and an EXFMT for the window display. I hate doing such > a thing and do not want to continue "wasting" resources if there is a better > way. > > Any help would be greatly appreciated! > > Bill Francis > Abacus Corporation > > PS: I love using DOU/IF's too... (kidding people, just kidding) > > +--- > | 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 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.