The best way to avoid this problem is to use one of the following:
1. Use Exec and Pass directives with mapping:
Pass /doc/* qsys.lib/html.lib/*
Exec /cgi-bin/* qsys.lib/html.lib/*
2. Put the CGI programs in a separate library:
Exec /qsys.lib/htmlcgi.lib/*
Pass /qsys.lib/htmldoc.lib/html.file/*
Symptom
Error 500: Bad script request -- script ’/qsys.lib/qsyscgi.lib/progname.pgm’
not found or not executable
Cause: Incorrect match of Exec rule.
This message can appear for the following reasons:
vThe script does not exist.
vThere is a problem with the script, for example, a send error or function check.
vThe user QTMHHTTP does not have authority to run this program.
Solution: See Description of “Forbidden - Path not valid for this server”.
Symptom
A browser request that runs a CGI program runs longer than expected. The
browser keeps waiting for a response.
Cause: The CGI application that was running has taken a function check.
Solution: Look at the QSYSOPR message queue for a message that requires a reply
sent from the CGI program that was running. Note the statement where the
program is failing. Use the procedure described under “Symptom: Error 500”.
Chapter10. Troubleshooting your CGI programs 143