On Monday, 12/03/2007 at 11:55 EST, "Schuh, Richard" <[EMAIL PROTECTED]> wrote: > I was thinking that the SRVRFTPO CONFIG version of TIMESTAMP might > actually apply to the FTPSERVE LOG file. I already use TERM TIMPSTMP ON > for the console messages, so the question still stands. Is the > documentation wrong (TIMESTAMP ON does not appear to be the default, as > stated), or is there a program bug? Which do I report?
Without digging through code, I would guess that the FTP TIMESTAMP ON applies only to *messages*, not the, ummm, "e-musings" and trace output of the server. If there's a bug, it's that those e-musings are being displayed. > While on the subject of the log files, they would be much handier if > they were made date-specific. If the file type were the current date, > perhaps Rexx date(S) format, instead of that totally uninformative > "LOG", it would make life much easier for me and, I suspect, for many > others. This applies to all of those perpetually growing log files that > seem assume that they have an infinitely large disk to use and try to > use every bit of it. Again, use the exits we have provided if you want to build a real, live audit trail of what the server is doing. Then you can use SCIF to capture output of your choice and store it the way you want. Alan Altmark z/VM Development IBM Endicott
