|
Hello,
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 :(
Best Regards
Filip
--
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 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.