Re: CGI-Script is not executable

We've noticed that we're seeing this "USER DEF" issue on non-CGI objects as well. In those cases, we don't find out as quickly since the program runs. It only comes up with the dev tries to deploy again. We've been using our deploy CLLE for a couple years under 7.1 without issue, until we moved to 7.3.

I've sent this to IBM. If they confirm the current behavior is intended, I'll change my deploy to manually adjust the authorities.

Thanks



-----Original Message-----
From: Mark S Waterbury [mailto:mark.s.waterbury@xxxxxxxxxxxxx]
Sent: Thursday, September 21, 2017 1:38 PM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] 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