|
Hi Folks, Does anyone know how to make access & error logging from the http server work using LogFormat DDS. I was doing it on V4R2 but when we went to V4R4 it stopped working. These are the directives that I used. # locations for your access and error logs LogFormat DDS AccessLog QUSRSYS.LIB/WWWACCESS ErrorLog QUSRSYS.LIB/WWWERROR # LogTime LocalTime this did not become a problem until we loaded V4R4. When I first encountered the problem I deleted QUSRSYS/WWWACCESS and QUSRSYS/WWWERROR thinking that the next server start would recreate them in the proper format. This did not happen. The files were never recreated on server startup. The error I got was TCP7411 Additional Message Information Message ID . . . . . . : TCP7411 Severity . . . . . . . : 10 Message type . . . . . : Information Date sent . . . . . . : 12/16/99 Time sent . . . . . . : 01:40:56 Message . . . . : A mismatch exists between log file /QUSRSYS.LIB/WWWERROR.FILE.Q0991216 and log format. Cause . . . . . : The type of file that exists for log file /QUSRSYS.LIB/WWWERROR.FILE.Q0991216 and the format specified on the LogFormat directive are not compatible. The directives are located on the Work with HTTP Configuration (WRKHTTPCFG) command. IBM can't seem to answer this. The reason I want to use dds is because I already have some reporting functions using these files. Any Ideas? THANKS IN ADVANCE Michael P. Gibbons MARYWOOD UNIVERSITY 2300 Adams Ave. Scranton, PA 18509 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-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 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.