Can't you use the call stake entry parameter to specify it?
Alternatively right after the call to B from A do a receive message and then
a send message:
Like:
RCVMSG MSGTYPE(*COMP) MSGDTA(&MSGDTA) MSGID(&MSGID) +
MSGF(&MSGF) MSGFLIB(&MSGFLIB)
SNDPGMMSG MSGID(&MSGID) MSGF(&MSGFLIB/&MSGF) +
MSGDTA(&MSGDTA) TOPGMQ(*PRV) MSGTYPE(*COMP)
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John
R. Smith, Jr.
Sent: Tuesday, March 24, 2015 11:07 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Sending a message in CL
Since both programs are CLLE, both of these options would be much more
involved. There aren't screens in either program. I just want the messages
displayed on the bottom of the screen when the program completes like the
messages you get back when you compile a program from PDM.
I was asked for more details on my current command. Here it is. Again, it
works if program B (where this command exists) is called directly from the
command line but not when program B is called from program A.
SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGDTA(&MSG)
TOPGMQ(*PRV) MSGTYPE(*COMP)
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth
Martin
Sent: Tuesday, March 24, 2015 11:56 AM
To: Midrange Systems Technical Discussion
Subject: Re: Sending a message in CL
If I am understanding this correctly, I might consider sending the messages
from Program B to a data queue. Then, perhaps at program A's LR time or
even upon a F-key request, run a procedure that reads the data queue and
provides the log you are looking for, at the time that you want it.
A second choice would be for Program B to populate a log file that can be
viewed, archived, cleared, or whatever you and the user want done.
On 3/24/2015 10:32 AM, John R. Smith, Jr. wrote:
I have program A that repeatedly calls program B with different
parameters (both are CLLE). Program B does its task based on the
parameter and then needs to send a message that will show up at the
bottom of the screen when program A is complete so we can see what all
happened by scrolling through the messages.
I tried having Program B do a SNDPGMMSG *PRV *COMP and if I call
program B from the command line, it works. However, when program B is
called from program A, the messages never show when program A is
complete. Can anyone tell me which command and parms need to be used
to have program B send the message all the way back?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
