RE: Sending Status message with QMHSNDPM blanks whole screen

You could do the following:

When program B is getting ready to do the processing and return to program A

1. Capture to current screen in a 1920 byte field
2. Change the last 80 bytes to contain the status smessage
3. Write a screen containing the changed field.

It requires little bit of UDDS but is not to bad.

Albert

----- Original Message -----
From: "Dave Murvin" <Dave.Murvin@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: RE: Sending Status message with QMHSNDPM blanks whole screen
Date: Fri, 21 Jul 2006 13:19:17 -0700

I think you are making it too complex. Just put your messages into the
message subfile. The format gets executed no matter what or should be
and costs next to nothing. The nice thing about Message Subfiles is

that

you can write the message anywhere and when you write the format, they
get loaded. Once of the nicest things about green screens.

Thanks for the suggestions.

There must be something in my specific program (a big ugly legacy
program) or display file that is causing my problems, because my
existing service program to send status messages works in other places.

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

By the way, program B makes extensive use of message subfiles for normal
edits and processing where the screens are redisplayed for the user.

Thanks

Dave Murvin

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