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


  1.  Home
  2. MIDRANGE-L
  3. February 2013

Re: Retrieving request message (the calling command)

Hi Buck,

I've not worked with those exits before but I need to have this work within the application rather that an external system configuration. I'll have a look at them for an education anyway.

Tim
On 2/27/2013 7:41 PM, Buck Calabro wrote:
On 2/27/2013 1:16 PM, Tim Bronski wrote:

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.
Have a look at the Command Analyzer Exit points, QIBM_QCA_RTV_COMMAND
and QIBM_QCA_CHG_COMMAND. They won't work for the CALL command, but if
you are invoking this via a user written command, perhaps this will give
you what you're looking for?
--buck


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.