• Subject: Re: Problems with Error 500
  • From: Jon.Paris@xxxxxx
  • Date: Fri, 23 Mar 2001 18:10:11 +0100

 >> 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.

Studying your code leaves me with some other questions though.  It appears
that you used one of my examples as a base for some of your code (there is
an accidental spelling error in the API error structure that indicates its
ancestry <grin>) but you've changed much of the rest of the stuff and I'm
curious as to why.  For example you've changed all the 10I binaries to 9B -
I wonder why when 9B is inefficient as all getout and offers zero
advantages.  You also use CALLB instead of the cleaner CALLP with the
resulting loss of ability to pass parameters that do not exactly match.
Also use of a fixed length field to build the HTML string forces you to use
the SCANR and constantly do %Trimming neither of which are needed if you
use varying length fields and CALLP.

Just curious.

| 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 ...


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.