RE: Sending Status message with QMHSNDPM blanks whole screen-RESOLVED

I have found the problem.  

The display file in program B has 14 formats, including stand alone
screens, screens with subfiles, and the message subfile.  One of these
formats was being used to blank out messages that were left over from
one of the previous displays in this display file (evidently enabling
the SFLCLR was not always removing the messages under some
circumstances).  It was coded to write a blank line to line 24 and was
written to the display during the ClearMessages subroutine.  When I
removed this format from the display file and substituted writing a
blank status message, all the status messages are now displayed on line
24 without blanking out the rest of the display.

Thanks for your suggestions.

Dave Murvin

I have an order selection screen with display width of 132 (program A)
that calls the order entry program with display width of 80 (program

B).

The send status message calls are all in program B.  When I select an
order for processing in program A, program A calls program B.  The
status message "Loading work files" generated by program B is

displayed

at the bottom of the display of program A (this is before any display
files are executed in program B) just like I expected.

When I am finished changing order information in program B, I press F6
to accept the changes and return to program A.   After pressing F6,
program B still has a lot of work to do and this is where I wanted to
send the status messages to let the users know what was going on in
program B.  After pressing F6, the display of program B is locked

while

it does its thing.  I thought the status messages generated by program

B

would display at the bottom of the last screen displayed by program B.
What actually happens is that the entire screen is blanked out and the
status messages are displayed at the bottom of the blank screen.

After

program B is finished with its work, it returns to program A.

I will continue to play around with this, but I think the users will
just have to get used to it or I will have to take out the status
messages.  Status messages are being sent to *EXT message queue with a
message type of *STATUS.  Both display files are RSTDSP(*YES).