RE: Display window causing a blank screen

["Monnier, Gary" <Gary.Monnier@xxxxxxxxx>]

Mark,

Does the window have the ASSUME keyword in it?

Also, try writing COET0012 to the screen before calling the window
program.

And a silly question but needs to be asked...

Was COET0012 compiled with RSTDSP(*YES)?

Gary

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of J M Plank
Sent: Friday, June 03, 2011 9:54 AM
To: Midrange Systems Technical Discussion
Subject: Re: Display window causing a blank screen

Thanks Gary.  I can't believe I missed that.  I added the OVERLAY to
COETOO12, but still have the blank screen.  I then took out the KEEP
(agree
it shouldn't be needed - not sure why the vendor had it there), and
still
have the blank screen.

I checked the object, and am using the one I thought I was.

Mark Plank

On Fri, Jun 3, 2011 at 12:25 PM, Monnier, Gary
<Gary.Monnier@xxxxxxxxx>wrote:

> Try adding the OVERLAY keyword to COET0012.  You should not need the
> KEEP keyword in it.