If DSPSIZ(*DS3 *DS4) is not the cause, then KEEP will not be either, I
think.

Perhaps it is in the programme itself. Perhaps the problem WINDOW DSPF is
closed after the first call and opened on a next call without another DSPF
been refreshed on the screen.

As you do not give us the complete source of both the DSPFS (omitting the
CF-lines), but including the ones required for the WINDOW and the DSPSIZ.
and code snippets of handling the EXFMT of the second WINDOW DSPF we all
are just stabbing in the dark. The code snippets provided are irrelevant.

And in the WINDOW DSPF you do not need OVERLAY, unless it is a SFLCTL.(But
that is not the problem either.)

Have you signed off an on again, because you may have working with an older
copy of the problem objects?

Regards,
Carel Teijgeler

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

On 3-6-2011 at 12:04 J M Plank wrote:

The new display window works when called from "format 1", but not from
"format 2", so I was looking in the wrong places for the problem.

The format displayed when the window program is called and displays
correctly has:
A R COETOO1A
A N18 CF01
<lots of similar records snipped>
A 87 CF09
A RTNCSRLOC(&CSRREC &CSRFLD)
A BLINK
A 69 ALARM
A CSRLOC(CROW CCOL)
A OVERLAY

This is the format displayed when the window program is called and blanks
out the screen has:
A R COETOO12
A N56 CF02
<lots of similar records snipped>
A CF10
A KEEP
A RTNCSRLOC(&CSRREC &CSRFLD)
A BLINK
A 69 ALARM
A CSRLOC(CROW CCOL)

I took the KEEP keyword out of COETOO12 and still had the blank screen (as
expected) on the called window. I added the KEEP to COETOO1A and the
windows still display correctly with the COETOO1A display still visible
behind the window.

Does this give anyone any ideas?



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].