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



Just a guess, but with Gerald's change working I have to wonder if your
SNDPGMMSG is being called in a sub-procedure (which would introduce a new
call stack entry) and the message subfile is looking at a different call
stack (typically associated with the *pgm and one removed from your
specified designation).

On Tue, Oct 5, 2021 at 4:04 PM Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
wrote:

I don't know what I am talking about, but.
I tested, and "*":2 (current stack minus 2) seems to work.



On Tue, Oct 5, 2021 at 1:25 PM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I've got thisd call to QMHSNDPM (prototype as SNDPGMMSG) in an RPG
program:

CLR CALLP SNDPGMMSG ('CPF9897':'QCPFMSG *LIBL':
C %EDITC(COUNTER:'1') + 'records updated.':
C 38:'*COMP':'*':1:MSGKEY:ERRORCODE)

(I've tried it with '*EXT':0 and '*':1)

and it sends the message to the joblog (either way), but not to the
message line of the terminal.

But I have this in a CL program:

SNDPGMMSG MSGID(CPF9897) MSGF(QCPFMSG) MSGDTA(FOO) +
MSGTYPE(*COMP)

and it works just fine.

Anybody know what I'm doing wrong?

--
JHHL
--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

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

--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

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




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.