Circular logging keeps all restart data in a ring of log files. Logging
fills the first file in the ring, then moves on to the next, and so on, until
all the files are full. It then goes back to the first file in the ring and
starts again. This continues as long as the product is in use, and has the
advantage that you never run out of log files.
WebSphere MQ starts with these primary log files, but if the log fills, it
allocates secondary log files. It does this dynamically and removes them
when the demand for log space reduces.
If MQ
can keep track of all your units of work within the 15 logfiles, then you will
never see more than 15, but there will always be 15. If you have a long running
unit of work that spans the 15, then the QM will start using up the
secondarys.
Make
your log files as big as possible. (What are you going to do the first time you
run out of log space; curse yourself for not making the logs bigger!) Even if
you make them as big as MQ will allow, you will only use up about 4 GIG. Most
servers have that much disk to spare easily.
-----Original Message-----
From: G. Edward Pius [mailto:[EMAIL PROTECTED]
Sent: Friday, July 16, 2004 4:56 PM
To: [EMAIL PROTECTED]
Subject: Log QuestionHello,
This may be a really dumb question. So bear with me for a while.
I am specifying circular logs when creating a queue manager. The number of files is 15 (never mind the secondary). Does this mean that the log files will never exceed 15 in number at all or does this mean that the log files per day will never exceed 15 in number.
Edward Pius
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all copies.
