Re: CGI-Script is not executable

Justin,

It would be  best to change the object owner of the new version of the program, in the 'test" library, ("from library"), to the correct production object owner, before invoking QLIRNMO.  It would also be a good idea to change all *PGMs in the "production" library to the "production object owner.   Or, at least, retrieve the current "owner" of the object about to be replaced, e.g. using RTVOBJD, and then use that to issue  a CHGOBJOWN to ensure the new object is  owned by the same profile as the previous version.

Whenever you promote objects using this CL procedure, the owners must "match" and then everything should work okay.

I also noticed that you used *PUBLIC *EXCLUDE (in an earlier e-mail),  so you may need  to ensure that QTMHTTP and/or QTMHTTP1 has at least *USE authority to these program objects. Or, just change them to be *PUBLIC *USE ... (why do they need to be *PUBLIC *EXCLUDE?).

I hope that helps,

Mark S. Waterbury

> On 9/21/2017 2:23 PM, Justin Taylor wrote:

Reminder: A CHGOBJOWN makes this error go away.

Mark S. Waterbury:
Here is the deploy code:
CHGVAR VAR(&FROMOBJ) VALUE(&OBJECT *CAT &TESTLIB)
CHGVAR VAR(&TOOBJ) VALUE(&OBJECT *CAT &PRODLIB)
CHGVAR VAR(&REPLACE) VALUE('2')
CALL PGM(QSYS/QLIRNMO) PARM(&FROMOBJ &OBJTYPE &TOOBJ +
&REPLACE &ERROR)

Objects are owned by the dev who compiled.


Henrik Rützou:
Changing it to *PUBLIC *USE (with the other dev as owner) works. When I change the owner to me, it works even with *PUBLIC *EXCLUDE. I'm puzzled as to why authority changes make a difference. There are no AF entries in QAUDJRN, so it shouldn't be due to authority failures.

The user names I posted for the CGI jobs were based on the actual jobs, not belief. If you think I should check the config for the user, please let me know what entry to look at.