|
I thought that since the existing display has a message subfile on line 24 that it might be interfering with the status messages. I am just trying to send a *STATUS message to the *EXT message queue. The existing display is RSTDSP = *YES. I am calling the QMHSNDPM API via a prototyped subprocedure in a service program. I use the message subfile for normal error messages, but did not want to be manually executing a format with the message subfile just to see the status. This same subprocedure and service program work as desired when I call a program from the command line. The status message is displayed on line 24 while the program is loading data, then the programs subfile is displayed. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan G. Campin Sent: Thursday, July 20, 2006 4:03 PM To: midrange-l@xxxxxxxxxxxx Subject: RE: 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.
You do not say what you are trying to do this in. If it RPG, sending a status message has nothing to do with a message subfile. To put a message in a message subfile, the message has to be sent to the program message queue associated with that level of the program and then a write must be done to the subfile and then it pulls out the messages from program message queue. If you just want to display a message on a status line, are you sending the message as a message type *STATUS to the *EXT message queue?
As an Amazon Associate we earn from qualifying purchases.
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.