× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



>I haven't configured the Original server for sometime, but I think there
was a place you had to specify "%%EBCDIC/EBCDIC%%" or something like
that.  Sorry I can't be more help there.

I am pretty sure that is for specifying what translation table should be
used to get it from one format to another - EBCDIC to ASCII for instance.

>I'v never had any trouble debugging in Apache: it works the same for me
as it did under Classic.  The only trick is finding the correct job. 

I am the only one using this http server and I watch the job come and go
right before my eyes, weird.

Aaron Bartell


-----Original Message-----
From: Joel Cochran [mailto:jrc@xxxxxxxxxx]
Sent: Tuesday, August 12, 2003 3:24 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] IBM Original HTTP Server translating content


Aaron,

I haven't configured the Original server for sometime, but I think there
was a place you had to specify "%%EBCDIC/EBCDIC%%" or something like
that.  Sorry I can't be more help there.

I'v never had any trouble debugging in Apache: it works the same for me
as it did under Classic.  The only trick is finding the correct job.  If
your traffic isn't too bad, you can just end all the jobs accept one. 
When I'm debugging during heavy traffic times, I just watch for the job
that stops and starts the most and 98% of the time I can get in on that
job.

Just to review the process for anyone who may not know:

1.  Find the job under QHTTPSVR subsystem.  There are some pre-start
jobs(terminology?) that you can skip over.  A good place to start is
with the first job whose "function" is listed as QZSRCGI (should be the
fourth one), although this is subject to change over the life of the
server instance.

2.  STRSRVJOB on that job.

3.  STRDBG on the program you want.  Naturally you usually want to
UPDPRD(*YES) and set a break point.  

4.  Initiate the CGI program through the appropriate browser call.

The debugger should open the next time the program runs ON THAT JOB.  If
the web page finishes processing normally then either the break point is
set wrong or that request went to another job in the subsystem.  Again,
this is the tricky part!

Also good to remember is that you only have so long to spend in debug
before the HTTP request times out.  You can keep debugging when this
happens, but you won't get to see any of the HTML output in your browser
if you let the job time out!

When you are done debugging, be sure to ENDDBG and ENDSRVJOB so as not
to disrupt any of your web clients, not that I've ever done such a
thing... :-)

Joel
http://www.rpgnext.com


On Tue, 2003-08-12 at 15:54, Bartell, Aaron L. (TC) wrote:
> Hi,
> 
> I am working with the IBM Original HTTP Server and IBM Apache.  From my
RPG
> program I am reading from standard input and writing the result of the
read
> to a file in the IFS.  When the program gets called via the IBM Original
> HTTP Server the query string doesn't get translated from the query string
> (for instance, spaces are still %20), but when I run the same program
> through the Apache server it translates the query string for me.
> 
> Is there a parameter I can set in the IBM Original HTTP Server that will
> make the translation happen automatically like the Apache server does?
> 
> Also, the reason that I am using the IBM Original HTTP Server is because I
> can't seem to figure out how to debug my programs with the Apache server,
> and it gives inadequate error messages when something goes wrong.  I can't
> get a service job started on job because the job comes into existence when
> the request comes in and leaves once the request is done.  Is this a
setting
> somewhere that I can change to fix this?
> 
> TIA,
> Aaron Bartell 
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.

_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

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