In this case, the 4.2.2.6 probably had the expiration fix first, because
the customer(s) reporting the problem were at the 4.2 level and not the 5.1
level.  We just got the 4.2.2.6 code a couple of days ago and plan to
install it Sunday in an attempt to correct some expiration problems that we
were seeing at the 4.2.2.4 level.

At 04:50 PM 6/26/2002 -0400, you wrote:

We are currently running into some expiration issues on our current server
of 4.2.1.7.  It is not deleting files due to some archive files we have.
Therefore, Support said to run an expire with "expire inv q=n w=n
skipdirs=yes du=60" every hour till we get the database down to a managable
percentage, currently at 87.4 (total 59.3 GB).  They also said for us to
upgrade to 4.2.2.6, instead of 5.1.1. They said that 5.1.1 has known issues
that are not fixed but 4.2.2.6 is fixed.  Please, can anyone tell me why
5.1.1. is lower than 4.2.2.6 or at least that is what some are being led to
believe?