RE: window display clearing display first

Thanks much

Sorry I didn't get back. I have been out of town since wednesday night.

This would seem to be one of the very very few times that I have found
something on the i did not work as documented, or at least I haven't been
able to find the right document yet, or can't quite understand the nuance
of the document. There certainly doesn't seem to be any reference in the
documentation on the difference between how the screen behaves when the
program ends with lr on or lr off.
There are noclear, noerase and scr1 formats in both programs window1 and
window2. (the program is a generic screen handler). I have not tried
putting the keep in format scr1. Am hoping all the formats in all
programs will not need to be changed to make this work.

I believe paragraph 3 says that if programA displays format1 and format 2
and both formats had keep specifiedy, then calls programB whose first
operation is a -read- to a file and not a format, then it will get the
fields from format1 not format2 because format1 was specified first. the
words first and uppermost would seem to be possibly ambiguous, or the
record to be kept must be both the first and uppermost to work without
specifying a record format on the read. This probably comes from the s34
days when -reads- used record codes to determine what format was being
read.

any IBM'er who wrote the code out there? Maybe he has passed on by now
or possibly living in the jungle far away from computers.

will test another idea tomorrow or probably just be sure all programs work
without turning on LR.


Jim Horn

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

message: 4
date: Wed, 9 Apr 2008 15:01:08 -0500
from: "Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx>
subject: RE: window display clearing display first

Uummm. After a bit more testing, seems like it will work as long as the
KEEP keyword is on the very first record format of window2 program
display file. Below is IBM doc on KEEP (Couldn't quite understand the
3rd paragraph where it talks about KEEP keyword on uppermost record)

--IBM Doc on KEEP
---------------------------------------------------------------
KEEP (Keep) keyword for display files
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 i5/OS(tm) operating system 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.

This keyword has no parameters.

This keyword cannot be specified with the following keywords:
ALWROL
CLRL
SLNO

A warning message appears at file creation time if the KEEP keyword is
specified on a record with the DSPMOD keyword. At run time, the KEEP
keyword is ignored when the display mode changes.

Option and response indicators are not valid for this keyword.

I'm assuming NOCLEAR and SCR1 record formats in your example below
belongs to display file of window2 program.

Try add KEEP keyword to both the NOCLEAR and SCR1 record formats.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
JDHorn@xxxxxxxxxxxxxx
Sent: Tuesday, April 08, 2008 4:55 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: window display clearing display first

I have an issue with a window clearing the display
old oe system calls window1
window1 requests fax info
calls window2 to find customer fax numbers
returns to window1 with lr on
calls window3 to display error message
when window3 displays, it first clears the display

if I return from window3 and call another window program the display
is still cleared.
the background will not return until window1 is redisplayed
if window2 does not turn on LR, everything works just fine.

all of the display files have records with assume and keep keywords in
them.
all the record formats displayed use the overlay keyword.

I tested this in a number of different ways and it seems to be a
universal truth.

Is this normal behavior? Is there a way to make this work with LR on?

typical beginning of a screen member

R NOCLEAR TEXT('Prevent Initial Clear')
ASSUME
OVERLAY
1 2'X'

R NOERASE TEXT('Prevent Screen Erase')
KEEP

R SCR1

WINDOW(3 4 20 72)
OVERLAY
RTNCSRLOC(&XXRCD &XXFLD )
MOUBTN(*ULD CF24)


Jim Horn