×
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.
Kent
This must be CGI (Net.data?) since it has a scriptaliasmatch to a
program in a library. One of our products does the same thing.
The 404-not found is probably related not to any IFS stuff, rather, to
the program. Could the authority to the library or program have changed?
Of course, in your case, it seems the program might not have been
specified in the address of the browser, hence the next paragraph.
When I asked about the URL, I was wondering what address was used in the
browser? You have to have something (the program name) following the
http://host:port/ewalibcgitp for it to be able to substitute something
for the $1.
Instance jobs - these are regular 400 jobs. They have a job log. There
is information there, in addition to the HTTP error logs in the IFS. The
instance jobs will probably be in subsystem QHTTPSVR - do a WRKSBSJOB
QHTTPSVR and look for jobs with names that are the same as the name of
your server instance. One or more of these will have CGI as part of the
text in the function column. Look at the job log there. That is actually
my first look for trouble-shooting. Now if there is no CGI job, then the
error logs are all you have. I've not done this, but you can set verbose
logging when you start the instance, I believe.
HTH
Vern
On 8/5/2010 11:51 AM, Hohlen, Kent wrote:
Vern,
<In addition to the instance logs under /www there might be job logs for
the instance jobs...
Our server isn't configured to dump the logs in /www. They go to a
different directory.
<As to the match, what URL did you use? If you only specified
"/ewalibcgitp/" then it would not have a program name to substitute.
I'm not sure what you are saying here or how I should respond. The way
it was configured and the way we are using it hasn't changed for years.
So I think this is not the issue.
We have done some further testing and it appears that the server job
can't get to the IFS. We have our CSS, javascript& logos in a
directory on the IFS and Firebug shows a 404 error - not found. We
haven't changed anything with authority butm we still opened these
directories up to everyone and didn't make a difference.
Thank,
Kent
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.
midrange.com
