We are using compiled REXX program's with the "old" HTTP Server
(not the Apache based one) without problem's
I can suggest to try with
"F httpserv",APPL=DEBUG -V " or -VV option and/or check the HTTP "logs"
directory for the actual logs, "cgi-error*" or "httpd_errors*"
On 29.01.2014 16:3
On 1/29/2014 10:46 AM, Miklos Szigetvari wrote:
We are using compiled REXX program's with the "old" HTTP Server
(not the Apache based one) without problem's
I can suggest to try with
"F httpserv",APPL=DEBUG -V " or -VV option and/or check the HTTP "logs"
directory for the actual logs, "cgi-
Since the CGI stays connected, then it may be looping. Look in SDSF and see if
one of HTTP processes is using CPU.
Although the browser has not displayed anything, it may have received some
data. Look at this data to see if it contains OMVS error messages or something
that indicates a problem.
The IBM http server should be set up with a surrogate user id to limit
access
to resources. We use the default PUBLIC surrogate id in our shop. So you
could have security issues if you are set up similarly as the surrogate id
should not be uid(0). You can also turn trace on in your CGI scri
