May have found somehting thanks to the debug view ... When i try to run the program from the browser, i get the following records added to the debug file in my development library:
 
WrtSection: Failed when calling QtmhWrStout. Msgid = CPF3C17. Message data:            
WrtJobDbg: 236625/QTMHHTTP/CGIDEV2APA                                                  
WrtSection: Section TOP not found.                                                     
WrtSection: Section TABSTR not found.                                                  
WrtSection: Section TABROW not found.                                                  
WrtSection: Section TABROW not found.                                                  
WrtSection: Section TABROW not found.                                                  
WrtSection: Section TABEND not found.                                                  
WrtSection: Section FORM not found. 
 
Im rather new to RPG ILE and have looked at the code but cannot see why this is failing. I have not modified the test cgi (firstcgi.pgm) src in any way - it is as CGIDEV2 installation restores and modifys it.
 
I can see in the src for firstcgi the statement - /copy CGIDEVPSS/qrpglesrc,prototypeb which contains the Wrtsection prototype
 
Any ideas what the Debug file is pointing to?
 
Stuart
 
 


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: 27 February 2006 14:37
To: [email protected]
Subject: Re: [Easy400Group] Problems with Firstcgi pgm using CGIDEV2


Check your CGIDEBUG file for errors.  The path should be something like YOURCGILIB/CGIDEBUG.  If the error is occurring in CGIDEV2, (ie. path to your HTML is wrong, section name is wrong...) you should see some sort of message in CGIDEBUG.  If there are no messages there, you should set up your CGI application to log the job number your CGI application is using to CGIDEBUG.   Simply add the following code to the top of your CGI program somewhere and recompile:

callp     wrtjobdbg(*on)

After running the CGI program again, go to the last record in CGIDEBUG.  You should (hopefully) see a job number and you can view the logs for that job for clues as to what the problem is.




"stuart5170" <[EMAIL PROTECTED]>
Sent by: [email protected]

02/27/2006 06:54 AM

Please respond to
[email protected]

To
[email protected]
cc
Subject
[Easy400Group] Problems with Firstcgi pgm using CGIDEV2





 Hi

  I have been given the job of setting up CGIDEV2 on our iseries
for development.
  So far, everything has been fine. I initially set up a server
instance which processed Cgi fine (created a test pgm hellothere
found In a tutorial sample)
  Ive now installed CGIDEV2 and got that web instance up and
running. The demo pages all work fine.
  Ive run the  SETCGILIB process and have a development library.
Ive created the firstcgi module and then compiled program FIRSTCGI.

  When I try to run this from a web browser -
http://1.1.1.1:8014/cgidevpssp/firstcgi

  I get the 'http 500 - internal server error'

  Im not sure what could be the issue here, the http directives
seem ok.

  I moved my hellothere test cgi pgm to the development library
(CGIDEVPSSP) and this runs
fine :http://1.1.1.1:8014/cgidevpssp/hellothere

  Could anyone point me in the direction of where I should be
looking to resolve this?

Thank you
Stuart






Yahoo! Groups Links

<*> To visit your group on the web, go to:
   http://groups.yahoo.com/group/Easy400Group/

<*> To unsubscribe from this group, send an email to:
   [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
   http://docs.yahoo.com/info/terms/







SPONSORED LINKS
How to format a computer hard drive Cobol programmer Iseries 400
How to format a computer


YAHOO! GROUPS LINKS






****************************************************************************

This email may contain confidential material.

If you were not an intended recipient,

Please notify the sender and delete all copies.

We may monitor email to and from our network.


****************************************************************************



Reply via email to