Gert van der Kooij <gert@invalid.nl> wrote in message news:<MPG.1a4293bd8cd7df8f9896b7@news.xs4all.nl>...[color=blue]
> In article <9a73b58d.0312102256.5a36403@posting.google.com>,
>
Join Bytes! says...[color=green]
> > Per the manual, when USEREXIT is set to ON and a log file becomes
> > full,
> > it is automatically archived using the exit program.
> >
> > So far so good. It then says that the log files are not deleted.
> > Instead, when a new log file is required and one is not available, an
> > archived log file is renamed and used again.
> >
> > I don't understand this. When will a new file which is required be
> > *not
> > available*? The number of log files determined by 'logprimary' are
> > pre-allocated when the database is initialized. So, is the manual
> > talking
> > about "logsecond" here?
> >
> > TIA
> > Raquel.
> >[/color]
>
> What it means is that the logfile doesn't exist when needed. Instead
> of formatting a new logfile DB2 renames an old one.
>
> For example:
> Db2 is logging to S0000008.LOG and S0000001.LOG has been archived
> already. Some time before S0000008.LOG is full (if I do remember
> right when starting to write to S0000008.LOG) DB2 checks if
> S0000009.LOG already exists and if not, renames S0000001.LOG to
> S0000009.LOG.[/color]
Thank you so much Gert for replying to all my mails in such immaculate
detail. Really appreciate it.
Raquel.
