Better yet,
Create your own startup pgm that calls the IBM one. Compile it to adopt
autority of it's owner and make sure than that owner is QSECOFR. This
way, if a PTF or a version change or whaterver changes the IBM startup
pgm, you wont be affected.
"Paul Nelson" <nelsonp@xxxxxxxxxxxxx> 2008-01-19 17:34 >>>
Sign on as QSECOFR or some profile with *SECOFR authority.
Before you compile the program, delete it. Make sure it's not the one
in
QSYS.
Use option 14 and press F4.
Change the replace program parameter to *NO and then press F10.
Change *USER to *OWNER and press enter to compile the program.
Now, when QSTRUP runs, it will adopt QSECOFR's authority. I have been
doing
this for years, and have never had an authority issue when a batch
program
like this runs.
Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bonnie Lokenvitz
Sent: Saturday, January 19, 2008 4:19 PM
To: Midrange Systems Technical Discussion
Subject: IOSYSCFG special authority needed
On a 520 at V5R3 we have a modified QSTRUP program compiled by QSECOFR
and its USER parameter is equal to *OWNER.
When the system is IPL'ed, we get the error CPF222E (*IOSYSCFG special
authority is required.). The program is attempting to vary on *NWS
servers.
The QSTRUPJD user is QPGMR which appears to be the default shipped.
What do I need to do to eliminate the error and get the network
servers
varied on at start up?
Thank you (again),
Bonnie Lokenvitz
midrange.com
