LogPrimary

[Raquel]

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.

[Gert van der Kooij]

In article <9a*************************@posting.google.com> ,
ra****************@yahoo.com says...

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.

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.

[Raquel]

Gert van der Kooij <ge**@invalid.nl> wrote in message news:<MP************************@news.xs4all.nl>.. .

In article <9a*************************@posting.google.com> ,
ra****************@yahoo.com says...

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.

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.

Thank you so much Gert for replying to all my mails in such immaculate
detail. Really appreciate it.

Raquel.