Re: Running API's as QSECOFR

It turns out it was my mistake. I was adopting authority, but the USRPRF
parameter of the CHGPGM was *USER, when it should have been *OWNER. I know
the difference, but missed the attribute when scratching my head. Thank
you for the responses on this issue.


___________________________________
Darren Strong
Dekko





From: Darren Strong <darren@xxxxxxxxx>
To: "midrange-l " <midrange-l@xxxxxxxxxxxx>
Date: 10/26/2017 12:03 PM
Subject: Running API's as QSECOFR
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



For a compliance project, I must run the QUSLOBJ and QCDRCMDI apis as
someone with *ALLOBJ. So, I created by program to use adopted authority,
and made its owner QSECOFR. However, it appeared that the QCDRCMDI api
was returning ?????? for the "created by user" field. This makes me
assume that the API is not running with the adopted authority of the
program calling it. So, is tried using the QSYGETPH and QWTSETP apis to
switch my user profile, however, even running with adopt QSECOFR, the
api's can't change the current profile to QSECOFR because it says it needs

*USE authority to the profile.

I might be able to submit a job as user QSECOFR, but I was hoping to run
this directly, because a Lotus Notes process will be calling it, and if
another job is submitted, the Notes process won't know when the process is

complete.



___________________________________
Darren Strong
Dekko