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



Hi Joel,

Thanks, you got it in one.  I put the log files in a directory off the root
and it now starts fine.  It's interesting that it was able to create the
file in QSYS.LIB, and add a member, before it failed.  That and the fact
that the conversion program didn't flag it as a problem led me to believe it
would work; presumably the manual would've told me otherwise, but the error
message sure doesn't.

OTOH, the new *ADMIN instance is a whole lot better in V5R1 than V4R5, IMO.

Thanks again!

Peter Dow
Dow Software Services, Inc.
909 793-9050 voice
909 522-3214 cellular
909 793-4480 fax

> ----- Original Message -----
> From: "Joel R. Cochran" <jrc@masi-brac.com>
> Sent: Monday, August 26, 2002 6:06 AM
> Subject: RE: [WEB400] HTTP Server pba HTP8420 error when starting
>
>
> > Peter,
> >
> > I ran into some similar problems trying to convert a Classic server to
> pbA.
> > I eventually gave up trying to get the covnersion to work and created
the
> > new config by hand.  You can use the converted statements as a guide
> though
> > until you are comfortable with pbA.
> >
> > I think the real problem here is that you are trying to use a DB2 type
> file
> > for logging purposes...
> >
> > /QSYS.LIB/QUSRSYS.LIB/LPHERRLOG.FILE/HTTPDLOG.MBR
> >
> > Instead, try something like this...
> >
> > ErrorLog logs/basic_error_log
>
>
>




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.