Re: CGI-Script is not executable

Hi, Justin,

Please describe the exact  process, step-by-step, and the commands used, to "move" these objects into "production." What  if a program by the same name already exists in the target library?  How does your  procedure handle that situation?

Also, what is the "object owner" of these programs?   ("Best practice" is to have all "production" objects owned by a single "application owner" profile.)

All the  best,

Mark S. Waterbury

> On 9/20/2017 3:06 PM, Justin Taylor wrote:

All of my CGI apps are RPGLE objects. Each source member has a compile script that contains the compile commands. The object is created in a test library associated with a test Apache server. We deploy into production by moving the object into a production library associated with a production Apache server.

For me, this works perfectly. Every over dev has problems. They run the compile script and get the object in the test library. The app runs fine. When the object is moved into the production library (regardless of who does it), the app does not run. It gives a "Script is not executable" message. I know the URL is correct because I have the page loaded before the object is updated. We move the object and I click refresh in my browser. If we change the owner of the production object, the app begins working. Changing the owner back has no effect.

We first saw this at IBMi 7.1, and it's still an issue at 7.3.


I don't even know where to go from here. Any suggestions?