Re: Auditing Program Calls

Hi, Rob and Gord:

I might be able to shed some light on this apparent conundrum.

The CALL command is a special command. It can be used interactively, to invoke a program, from a command line, or it can be used as a request message on a submitted job, etc., and it can also be used in a CL program. However, whether CLP or CLLE, the "CALL" command gets "compiled" into generated code that performs the invocation of the desired program, and the "CALL" command itself is never executed, unlike most CL commands in a CL program. In that respect, CALL in a compiled CL program is more like the DCL command, or those "control flow" commands like IF, ELSE, GOTO etc. --they generate code at "compile-time" to perform some actions at "run-time."

And, of course, the CALL opcode in RPG or the CALL statement in COBOL also generates code and does not use the CL "CALL" command at all.

Hence, I believe that is why you will never see a "CD" audit trail entry in QAUDJRN for those commands when executed from a compiled CL program... unless you did something like concatenate the CALL command in a variable and invoke it via QCMDEXC...

Does t hat "make sense"?

I hope that helps,

Mark S. Waterbury

> On 3/28/2017 3:13 PM, Rob Berendt wrote:

I agree that you should be seeing those 'Y' entries. Based on the "Where
run" shown by me and Mark Waterbury at
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/rzarl/rzarlf10.htm
You may wish to open a Service Request on that.

IDK if TRCJOB would work for you.

I'm not sure why you are doing this. Is this something which may be
addressed by the new 7.3
<snip>
What's new for IBM i 7.3
Read about new or significantly changed information for the Security
reference topic collection.
A new capability that is called Authority Collection has been added to the
base operating system. This
support assists the security administrator and application provider in
securing the objects in an
application with the lowest level of authority that is required to allow
the application to run successfully. The goal of authority collection is
to increase the security of the objects within the application. New CL
commands, Start Authority Collection (STRAUTCOL), End Authority Collection
(ENDAUTCOL), and
Delete Authority Collection (DLTAUTCOL), and a new SQL view,
QSYS2.AUTHORITY_COLLECTION,
are provided in support of this new enhancement
</snip>
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/rzarl/sc415302.pdf?view=kc


Rob Berendt