RE:

Rob,

I have similar issues.
In QSTRUP, I do a sbmjob using the user that has authority for that job/process.
For QSECOR issues, I created a copy of QSECOFR, IQSECOR, sbmjob jobs under IQSECOFR.
I also had a related issue in AJS where I had to submit as QSECOFR, (AJS won't allow this, had to use ISECOFR)
I still didn't get QSH CMD('clrtmp') to run under QSECOFR in QSTRUP.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, September 18, 2014 8:43 AM
To: midrange-l@xxxxxxxxxxxx
Subject:

Here's the issue,
Startup program runs at IPL.
I want the startup program to set certain items that IBM mucks up upon system restores and whatnot.
One of these items I want changed is the attribute on /QFPNWSSTG.
Startup programs runs under QPGMR. This profile cannot change that attribute.
Calling a program that has adopted authority does not work as the stream file system doesn't recognize adopted authority.
QPGMR cannot submit a job to run under QSECOFR, even if it uses an adopted authority program. USER(QSECOFR) is stopped in it's tracks by SBMJOB.
Check the help on that.
I could try getting a profile handle to QSECOFR. I've not worked with profile handles. I'm under the impression that I need to know the password for QSECOFR in the get profile handle api. And we do change the password, so burying it into code is not desirable.
I am leaning towards submitting the job under some user created user profile that has *ALLOBJ. I just have to ensure that it exists on all lpars, etc.
Any other suggestions?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.