Re: Need to create a program that uses QSECOFR as adopted authority

On 26-Jul-2016 09:35 -0500, Bryan Dietz wrote:

On 25-Jul-2016 18:21 -0500, CRPence wrote:

And if the issue did originate per both no prior request to Delete
Program (DLTPGM) and an existing program had been replaced, the
Create CL Program (CRTCLPGM) request logged a msg CPI2119 "AUT and
USRPRF parameter values were ignored." and msg CPI2121 "Replaced
object &1 type *&4 was moved to &5." to inform of the effect.

Rather than deleting [or moving or renaming] the existing program
and then re-creating anew the program, just to establish the
desired user name for adopted authority, <<SNIP>>

CHGPGM The_Pgm USRPRF(*OWNER)

if on a newish version add this to the beginning of the program
(after the DCL and before program statements)

DCLPRCOPT USRPRF(*OWNER)

Notable; though I personally choose to place that as the first declarative immediately after the PGM statement, and before any other DCL or DCLF.

However FWIW, just to be sure\clear, that Declare Processing Options (DCLPRCOPT) specification is no different than explicitly having coded that parameter keyword and special value on the compile\create command. Thus for an existing program being replaced, again, either first DLTPGM [or RNMOBJ or MOVOBJ] of the existing program to avoid the issue diagnosed by CPI2119 or use the CHGPGM which serves more directly as corrective to an existing program object.