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?
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. Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Sunday, December 02, 2007 7:05 PM To: [email protected] Subject: Re: FTP Append (Update) On Friday, 11/30/2007 at 06:45 EST, "Schuh, Richard" <[EMAIL PROTECTED]> wrote: > There is no SRVRFTP CONFIG file, so everything about FTP is vanilla. > The manual says that the default is TIMESTAMP ON. I have 30,000 lines of > empirical evidence that this is not so. Do I report this as a program > bug or is it a documentation problem? TIMESTAMP applies to actual FTP server messages, not to anonymous, uh, "e-drivel" the server puts on the console. I'd use CP TERMINAL TIMESTAMP ON instead. Alan Altmark z/VM Development IBM Endicott
