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



I neglected to mention we had looked at that. Our DSPSIZ was different, and
we changed it to match the calling program's DSPSIZ, but we still get the
blank screen.

That did give me an idea on something else to try.

Thanks.
Mark Plank

On Fri, Jun 3, 2011 at 11:12 AM, Jeff Young <cooljeff913@xxxxxxxxx> wrote:

Try looking at the DSPSIZ of the calling pgm DSPF vs the new window.
If the new window does not have a DSPSIZ corresponding to the calling pgm,
it
will blank out the underlying screen.


Jeff Young
Sr. Programmer Analyst






________________________________
From: J M Plank <plank.computer@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Fri, June 3, 2011 10:52:59 AM
Subject: Display window causing a blank screen

A coworker is having problems getting a window to display properly. I know
we are missing something obvious. There is an interactive program with a
display file that can call other programs with windows. The problem is
with
the called program and window. All the existing windows display properly,
but the new window blanks out the screen behind it. I've checked the
archives and Googled this, and had lots of hits - everything I've read we
either have in the code or tried unsuccessfully (which means we are likely
overlooking the obvious).

The calling program has two different record formats used when the windows
are called. Format 1 is used for the calls to existing programs with
windows that display correctly. Format 2 calls the new program which has
the window with the blank screen. The only difference I see between them
is
that format 2 has the KEEP keyword. I've taken it out with the same
result,
and added it to format 1, and the called windows there still display
correctly.

The new window has one field. The existing windows either have subfiles or
multiple fields, but I don't think that has any bearing on the problem.

We've compared the source for two correctly displaying windows to the
source
for the new window and nothing obvious jumps out at us.

All the display files have RSTDSP *YES.

The new display file has the following record format (not called):
A R DUMMY
A ASSUME
A 15 1' '

This is the record format displaying with a blank screen:
A R DISPLAYR
A OVERLAY
A WINDOW(3 6 8 32)
<== (also used WINDOW(*DFT 8 32)
A KEEP
A WDWBORDER((*COLOR RED) (*DSPATR RI)-
A (*CHAR ' '))
A USRRSTDSP
We have the same result with the overlay keyword removed, and with both the
KEEP and USRRSTDSP keywords removed.

This existing window displays correctly, even without the KEEP and
USRRSTDSP
keywords. But the calling program uses Format 1 instead of Format 2.
A R COETCM01
A OVERLAY
A WINDOW(*DFT 11 60)
A WDWBORDER((*COLOR RED) (*DSPATR RI)-
A (*CHAR ' '))

Any ideas of what else we should be looking for?

Thanks.
Mark Plank
Maple Leaf Farms
Milford, IN
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.