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



Steve,

After calling CL-B, call API QMHMOVPM (Move program messages).  This will
move all the program messages that have been sent to CL-A to the caller of
CL-A.  A couple of years ago there was an article in one of the magazines
describing a way to wrap the parameters in a command.  If you are interested
I could mail you the source of the command.

Joep Beckeringh

----- Original Message -----
From: "Steve Wolkis" <pthswolkis@hotmail.com>
To: <rpg400-l@midrange.com>
Sent: Monday, February 25, 2002 6:43 PM
Subject: retreiving message previously sent to program messageq


> Hi
>
> I have a CL (lets call it CL-A) that calls another CL (lets call it CL-B -
> which is proprietary, and I don't have source code for).
>
> If I run CL-B as a stand alone, if invalid information is entered in one
of
> the prompts, when enter is pressed the CL will use a SNDPGMMSG command,
and
> on the program status line, it will show a message showing something like
> "outq not valid", or whatever the problem was.
> (I can tell SNDPGMMSG was used by looking at job log)
>
> When I now run CL-A, which calls CL-B, if the same invalid information is
> entered, you do not see the message in the program status line.
>
> I've looked on the boards, and looked into
> using RCVMSG with *PRV, but that works the opposite way (CL-B could pass
> info back to CL-A).. and I can't modify CL-B.
>
> Is there any way CL-A could re-display what CL-B previously output to the
> program messageq.
>
> Thanks





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.