I have my application logging set on most detailed.  WAA builds application
logs, the current one is named WAA10408.LOG.  WAA seems to start a new log
file when the present one grows too large.  How is the file naming and start
a new log functioning accomplished?
Bruce Anderson

Hi Bruce,

There is one log in a month:

    WAA1YYMM.LOG


Bruce Anderson wrote:

> I have my application logging set on most detailed.  WAA builds application
> logs, the current one is named WAA10408.LOG.  WAA seems to start a new log
> file when the present one grows too large.  How is the file naming and start
> a new log functioning accomplished?
> Bruce Anderson
> 
> 

Regards
   Andreas Herdt
   [Alaska Research & Development]

Bruce,

> I have my application logging set on most detailed.  WAA builds application
> logs, the current one is named WAA10408.LOG.  WAA seems to start a new log
> file when the present one grows too large.  How is the file naming and start
> a new log functioning accomplished?
> Bruce Anderson

Further to Andreas message, the logs change as follows:

1.  If WAA is started, it opens a log for the current month, creating a new
one if necessary.

2.  If WAA is running and a request arrives (or another event, such as
shutdown occurs), WAA checks to see if the currently open log is the
correct log for the current month.  In other words, if it recieves a
request at five past midnight on the first of the month, it knows the
current log is the wrong one. In this case, it places a continuation
message in the log, closes it and opens the new log.  The continuation
message looks like this:

[01/06/2004 09:05:09]*** STARTING NEW LOG: WAA10406.LOG

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

He's dead Jim.