Re: CPYAUDJRNE question

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Log level?

Might it be like one of those things where you do WRKOBJ *ALL/MYOBJ and it
doesn't find it but if you do a DSPOBJD MYLIB/MYOBJ it tells you that you
do not have authority to it?  And yes, I know that you're talking IFS
instead but hopefully you get my drift.

On Wed, Aug 21, 2024 at 10:31 AM DEnglander--- via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> I am using the CPYAUDJRNE command to create a QTEMP file of T-AF entries,
> which are Authority Failures.
>
> When I look at the information in the QTEMP file, it references a specific
> job name for each entry. When I look at that job's joblog, I do not see
> any failures, nor do I see where it is using the path that is associated
> with the entry. For example, the path entry contains '/www' in it [field
> AFPNM in QSYS/QASYAFJ5], but nowhere in the associated joblog do I see any
> reference to that path, nor any authority failures. There are references
> to other IFS paths [that are not in the QTEMP for the job] in the
> associated job in the CL with no authority issues.
>
> I do see where the Username associated with the job is not in the list of
> Users who have authority to /www. Could that be it? It's not clear why I
> getting the Audit Journal entry for a job that doesn't use the IFS folder.
>
> The job does use a Java routine, could that be it?
>
> Thank you,
>
> Doug
>
>
>
> "CONFIDENTIALITY NOTICE:  This e-mail transmission (and/or the attachments
> accompanying it) contain confidential information belonging to the sender.
> The information is intended only for the use of the intended recipient.  If
> you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or the taking of any action in reliance
> on the contents of the information is strictly prohibited.  Any
> unauthorized interception of this transmission is illegal under the law.
> If you have received this transmission in error, please promptly notify the
> sender by reply e-mail, and then destroy all copies of the transmission."
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.