× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thank you!
Another project has me today but will do asap.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Friday, July 10, 2015 12:23 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: message text from message subfile does not appear in window

Try this...

D QMHSNDPM PR ExtPgm('QMHSNDPM')
D MsgID 7A Const
D MsgFile 20A Const
D MsgData 60A Const options(*varsize)
D MsgDtaLen 10I 0 Const
D MsgType 10A Const
D CallStkEnt 10A Const
D CallStkCnt 10I 0 Const
D MsgKey 4A
D ErrorCD 10I 0 Const
D LengthCallStackEntry...
D 10I 0
D QualifiedCallStackEntry...
D 20A
D ModuleName 10A Overlay(QualifiedCallStackEntry:1)
D ProgramName 10A Overlay(QualifiedCallStackEntry:11)
D DspProgramWaitTime...
D 10I 0

CallStkEnt = '*PGMNAME';
CallStkCnt = 0;
ModuleName = '*NONE'; // Sends the message to the program's message queue ProgramName = PGMQ; LengthCallStackEntry = %len(trimr(QualifiedCallStackEntry));
DspProgramWaitTime = 0;

QMHSNDPM(MsgID: MsgFile: MsgData: %len(MsgData): MsgType: CallStkEnt: CallStkCnt: MsgKey: ErrorCD:
LengthCallStackEntry: QualifiedCallStackEntry: DspProgramWaitTime);



Gary Monnier


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Friday, July 10, 2015 11:02 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: message text from message subfile does not appear in window

Thanks Gary,
For the 6th parm for QMHSNDPM, (*pgmq or Call stack entry), I use *PROC (positions 1-10) of the Program Status Data Structure (SDS).
Because I can see the message text in my job log, I've been thinking this particular parm is ok ?
The following are the prototype and call from my program:
D QMHSNDPM PR ExtPgm('QMHSNDPM')
D MsgID 7A Const
D MsgFile 20A Const
D MsgData 60A Const options(*varsize)
D MsgDtaLen 10I 0 Const
D MsgType 10A Const
D CallStkEnt 10A Const
D CallStkCnt 10I 0 Const
D MsgKey 4A
D ErrorCD 10I 0 Const
QMHSNDPM(MsgID: MsgFile: MsgData: %len(MsgData): MsgType: PGMQ: 1: MsgKey: ErrorCD);


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Friday, July 10, 2015 11:26 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: message text from message subfile does not appear in window

Gary,

Where is QMHSNDPM sending the message? More specifically, what is your call stack entry setting?

If you are using * in the call stack entry, your call stack counter might be off.

You may want to try using *PGMNAME for the call stack entry. This will require optional parameter group 1 be used.

Thanks,
Gary Monnier


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Thursday, July 09, 2015 2:00 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: message text from message subfile does not appear in window

I have an RPGLE program that displays a window where the user is to be able to update a file we use to store parameters which control a local application.

The subfile for parameter records currently works as expected.

My problem is when the program detects an invalid value and calls QMHSNDPM to send error text to the message subfile, the message does >not< appear on the screen.

I see the error text in the job log, and don't see device errors so I guess I have an error with screen IO:

WRITE "window rec"
EXFMT "subfile control rec"
WRITE "message control rec"

The "message subfile rec" specifies SFLMSGRCD(17) which I selected because I want messages to show on line 17 of the window, just below text for F keys and above the bottom window border.

Thanks for any suggestions!
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.