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



Hi,

By destination message queue you mean line with pgmq = 'WRITETOMSGF'; ?
My MSGF in DisplayFile looks like this:

A R MSGSFL SFL
A SFLMSGRCD(22)
A MSGXKY SFLMSGKEY
A PGMQ SFLPGMQ(276)
A*---------------------------------------------------------------------
A R MSGCTL SFLCTL(MSGSFL)
A OVERLAY LOCK BLINK
A KEEP
A 60 SFLDSP
A 61 SFLDSPCTL
A 62 SFLINZ
A N51 SFLEND
A SFLSIZ(0005)
A SFLPAG(0001)
A PGMQ SFLPGMQ(276)

After calling Pgm_SNDSFMSG I have this line:
MeesageFileSCTL.pgmq = 'WRITETOMSGF';
Not sure if this matter but WRITETOMSGF is called from another
procedure inside srvpgm so the flow looks like this:
Pgm A call SRVpgm B, in srvpgm B procedure A calls proc WRITETOMSGF so
after WRITETOMSGF is finished we are again in Proc A in SRVPGM B.
wt., 4 wrz 2018 o 17:22 <dlclark@xxxxxxxxxxxxxxxx> napisał(a):

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 09/04/2018 11:15:10
AM:
I've been using MessageSubfiles many times and so fat I have not had
any problems until today....

I'm Calling srvpgm B from PGM A. In this SrvPgm B I have procedure
WriteToMSGF which writes to message subfile using SNDPGMMSG:

if ErrorHappened;
%subst(msgf:1:8) = 'MSGFILEID';
msgid = 'MSGID';
pgmq = 'WRITETOMSGF';
%subst(msgq:1:7) = '*TOPGMQ';
msgdta = '';
Pgm_SNDSFMSG(msgf : msgid : pgmq : msgq : msgdta);
ENDIF;

Thing is I don't see those messages on my screen and srvpgm B has its
own Display File.
In job log I can see all messages properly and by using F1 on one of
them I can see this:

From program . . . . . . . . . : SNDMSG
From library . . . . . . . . : LANSAFD4
From module . . . . . . . . : SNDMSG
From procedure . . . . . . . : SNDMSG
From statement . . . . . . . : 1900

To program . . . . . . . . . . : PROGRAM1
To library . . . . . . . . . : LANSAFD4
To module . . . . . . . . . : PROGRAM1
To procedure . . . . . . . . : WRITETOMSGF
To statement . . . . . . . . : 79200

PROGRAM1 is name of program which calls my SRVPGM. SNDMSG is name of
CL program which run SNDPGMSG command. Do I have this problem because
srvpgm's don't have their own message queue? How I can solve this
problem? Should I switch to using some API? Please help :(


The service program, itself, doesn't have a message queue but each
service procedure that is called within the service program has its own
message queue. So, I notice that you are specifying a destination message
queue name in the API. This same message queue name would have to be
referenced by your message subfile in order for the message to be seen. Is
this the case?


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





*********************************************************************************************
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 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: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.