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. Debuggers are available for most browsers. I personally use Google CHROME which has built-in debugger under TOOLS -> DEVELOPER TOOLS. Open your preferred debugger and then access your web page. Look at the network data. In the case of CHROME you click on the NETWORK tab to display various items that make up that web page. Right mouse click on the item you think is your execution (probably only one in your case). Select OPEN IN NEW TAB to display the source transmitted. Closing the debugger is the RED X in the right of the debugger box. If you can't use the debugger, then try directing STDOUT and STDERR to disk. Look at those disk files after running your REXX. Jon Perryman. ----- Original Message ----- > From: jan de decker <[email protected]> > > When trying to invoke the same compiled program from HTML the browser > stays connecting and eventually times out. > > An interpreted Rexx in the same directory runs as CGI. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
