• Subject: RE: Problems with Error 500
  • From: "Christopher A. Libby" <clibby@xxxxxxxxxxxxxxxxxxxxxx>
  • Date: Fri, 23 Mar 2001 13:26:57 -0500
  • Importance: Normal

>  >> Hello all - I've been working on a couple sample RPG-CGI
> programs.  I'm
> running into a problem with Internal Server Errors.
>
>
> Christopher, your problem is in the $WrStout subroutine.  It
> should be Eval
> WrtDta = %TrimR(WrtDta) + NewLine - without the %Trim the Newline gets
> added and immediately dropped.  Another comment - the constant calling of
> the API will slow your program down and is not necessary.  Your
> entire page
> could be done with a single call.

Thanks for the help.

> Studying your code leaves me with some other questions though.  It appears
> <snip>
> use varying length fields and CALLP.
>
> Just curious.

<blank stare>Uhmmm...I just copied it off a web page??? :>   I'm rather new
to using RPG as a CGI.  I guess I should have thought of only using one API
call, but I've done a lot of work in Active Server Pages (brainless
programming).

One question I have for you would be this - what happens if my web page
exceeds 1024 bytes?  Do I need to constantly watch the length of WrtDta,
then call the API when it's around 1024 bytes?

-Chris




Maine Public Service Company
www.mainepublicservice.com


+---
| This is the WEB400 Mailing List!
| To submit a new message, send your mail to WEB400@midrange.com.
| To subscribe to this list send email to WEB400-SUB@midrange.com.
| To unsubscribe from this list send email to WEB400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.