Re: 3rd party app failed to start on IPL, because QPGMR password was set to *NONE

On 06-Jul-2016 14:42 -0500, Rob Berendt wrote:

On 06-Jul-2016 13:44 -0500, Steinmetz, Paul wrote:

Response from the 3rd party vendor:
The profile starting the software must have a password and be
capable of signing on - or the java will not start.

[…]

This issue only occurs during IPLs, which default to QPGMR running
the QSTRUP job.

I would really like to change QSTRUP to run as a different user,
would solve this and many other issues related to QPGMR having
insufficient authority to run a process.

Take this third party app out of startup.
Create its own Autostart Job Entry ADDAJE in the subsystem with a
job description assigned to an appropriate user profile.

CRTJOBD THIRDPARTY USER(QSECOFR) RQSDTA(put call or whatever here)

Except the USER can not be QSECOFR, i.e. QSECOFR does not qualify as "an appropriate user profile". However the USER can be a User Profile (USRPRF) that is defined with a User Class (USRCLS) and Special Authorities (SPCAUT) similar to or matching the system-supplied *SECOFR; see msg CPD1617

ADDAJE QCTL JOB(THIRDPARTY) JOBD(THIRDPARTY)

And to be clear, that request assumes *LIBL/QCTL [of the job making the request] matches the Controlling Subsystem Description as defined by the System Value QCTLSBSD.