× 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 Ken,
Yes they are our own commands, all processed with a single CPP. For logging purposes I want to capture the original command string used. I could rebuild it within the CPP but that's a maintenance nightmare. I had myself convinced that I'd done this previously but I've been deluded before! It doesn't seem like it should be that hard to do.

Tim

On 2/27/2013 5:25 PM, Ken Sims wrote:
Hi Tim -

On Wed, 27 Feb 2013 10:40:31 +0100, Tim Bronski
<tim.bronski@xxxxxxxxx> wrote:

I'm trying to retrieve the actual command string of the the command that
was used to invoke my program - the CPP. Using QMHRCVPM or RCVMSG I can
retrieve the request message with the command string in the message data
but ONLY if the command is entered on a command line. If the command was
invoked from a CLP there's nothing there. I've looked up and down the
stack. Its obviously around somewhere and I could have sworn I've done
this before. Anyone know what the difference is between the way a
command is processed in these two scenarios and where I might find my
command?
Without LOGCLPGM(*YES) active, I suspect that's going to be
impossible.

My first question has to be ... what are you trying to actually
accomplish? If it's your command, there *may* be a better way to do
whatever it is that you're trying to do than retrieving the command
string.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.


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.