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



The CD layout is in the Security Reference manual appendix F.

-----Original Message-----
From: Monnier, Gary
Sent: Wednesday, February 27, 2013 11:18 AM
To: Midrange Systems Technical Discussion
Subject: RE: Retrieving request message (the calling command)

Tim,

Are the CL programs compiled to explicitly log commands or is it left up to the job? If the program isn't set to log CL commands and neither is the job you won't see them.

Have you started journaling? In QAUDJRN you will find journal code T entry type CD. These entries contain the commands that have been executed. The CD layout is in the Security

If the command was run from a CL program that does not log commands the command with parameters value will be blank. The first portion of the journal entry specific data will tell you the command name regardless.

Will this give you what you are looking for?


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tim Bronski
Sent: Wednesday, February 27, 2013 10:47 AM
To: Midrange Systems Technical Discussion
Subject: Re: Retrieving request message (the calling command)

Gary,

Yes I've tried that but retrieving the *LAST request message will give me the call of the CLP that the commands are used in. Commands in a compiled CLP don't appear to have an associated request message.
(Assuming I'm using the apis correctly).

On 2/27/2013 7:23 PM, Monnier, Gary wrote:
Tim,

Have you tried the QMHRTVRQ (Retrieve Request Message) api?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tim Bronski
Sent: Wednesday, February 27, 2013 1:41 AM
To: Midrange Systems Technical Discussion
Subject: Retrieving request message (the calling command)

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?

--
Need secure FTP? Forget PASE...get your FREE sFTP here
www.arpeggiosoftware.com
--
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.


--
Need secure FTP? Forget PASE...get your FREE sFTP here www.arpeggiosoftware.com
--
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.


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.