RE: Sending Status message with QMHSNDPM blanks whole screen

RSTDSP = *YES, call stack entry is *EXT, and call stack counter set to
zero. 

The status messages are being sent during the final interactive
processing of the program (updating work files, posting the order, etc.)
before it ends and returns to the calling program.  When the status
message is displayed, the entire screen is blanked out, the status
message is displayed on line 24 and the display is locked while the
program runs.  After program finishes and we return to the calling
program, the calling programs display file is shown.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Monnier
Sent: Thursday, July 20, 2006 3:04 PM
To: Midrange Systems Technical Discussion
Subject: RE: Sending Status message with QMHSNDPM blanks whole screen

Dave,

Check to see if the display file has RSTDSP(*YES).  If not, change it to
*YES and try sending the status message again.  Also try having the call
stack entry = *EXT and the call stack counter set to 0.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Murvin
Sent: Thursday, July 20, 2006 1:10 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Sending Status message with QMHSNDPM blanks whole screen


I am trying to send status messages to a program display using the
QMHSNDPM API.  When I send the status message, it blanks the whole
screen and displays on line 24.  

 

I tried sending it to *EXT call stack entry and a call stack entry of 0
and 1.  No help.  The existing program has a message subfile on line 24.
Status messages seem to work okay as long as I am on a command line.

 

What am I missing?  Is there a better way to send a status message to
the message subfile?

 

Thanks

 

Dave Murvin