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

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.

Easily enough done by customizing the QSTRUPJD Job Description (JOBD) or perhaps instead, doing what Rob explains in a followup. And of course, then also adding that customization to the System Change Management [script] to be repeated after maintenance and upgrades. Noting: that maintenance has at least a theoretical chance of overlaying such a customization, if even any greater chance than other means of customization that could accomplish the same effect, a dependence on the startup processing effecting an automatic run of the scripted changes could [though I expect with almost zero chance] present a conundrum.

Of course consider that the startup is tempered in authority, purposely, to ensure prevention of running in a god-like mode, such that Trojans or other negative effects from running with excessive privileges might be avoided. That is to suggest, what the QPGMR profile is going to perform in the startup should be well-planned, and probably is best tested before [rather than after blindly] having added new work to be performed in what is effectively the user-defined-portion of the IPL.

The startup job also has the options of performing a switch-user or submitting the job as another user [to which QPGMR is authorized] as necessary, so as to perform any specific requests under an alternate user profile. Or again as Rob noted in another followup reply, the controlling subsystem could be modified to have [some] additional AutoStart Job Entry (AJE) added to the controlling Subsystem Description (SBSD) [or similar customizations, but to a different SBSD that is automatically started], using the Add Autostart Job Entry (ADDAJE).