Re: DSPF window message question

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 02/11/2019
07:00:41 PM:

I found an option in the DDS of the window and it is set to have the
message line in the window.

The program is using a subroutine to send the messages to the program
message queue. The messages are stored in a MSGF.

When the window is displayed, it does not display the messages.

The messages are displayed when I exit (F3) the window.

I use the *NOMSGLIN keyword and you can have a message subfile in
a window as long as you have enough room for the record format to fit and
the messages are in the call message queue expected by the window. The
following is the message subfile from one of my windows.

A
*------------------------------------------------------------------------*
A* Error Message Subfile and Control for Window *
A
*------------------------------------------------------------------------*
A R SMSFL TEXT('MESSAGE SUBFILE')
A SFL
A SFLMSGRCD(17)
A SFLMSGKEY SFLMSGKEY
A SFLMSGQUE SFLPGMQ
A*
A R SMSFLC TEXT('MESSAGE SUBFILE
CONTROL')
A SFLCTL(SMSFL)
A SFLPAG(1)
A SFLSIZ(2)
A OVERLAY KEEP
A WINDOW(ACSYAW2W)
A SFLDSPCTL
A SFLDSP
A 58 SFLEND
A SFLINZ
A SFLMSGQUE SFLPGMQ
A*

Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331

TIA, Darryl.


On Mon, Feb 11, 2019 at 6:36 PM a4g atl <a4ginatl2@xxxxxxxxx> wrote:

I have not had to do this in a very long time,

I have an old program that had intermittent problems and found the

problem

in a window record format.

I corrected the problem and then added messages for the issues which

cause

the problem.

To my surprise, the window does not provide for displaying the message
subfile on it.

Did I miss something?

Or do I have to use an output field for the message?

TIA

Darryl Freinkel

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link:

https://amazon.midrange.com

*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.

*********************************************************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com