Hello Robert,

We are facing problems too with the "new" Expire Inventory.
Before to upgrade to 3.1.2.14, our DB was 53GB with 92% used and +/- 62
millions objects
The problem is that we never turn the "new" E-I out
Now (4 weeks later), the 53GB DB is 67% used with about 50 millions objects.
During each aborted run of the "new" E-I, some free cartridges where
returned to scratch.
Daily, we schedule a reclamation process (recl=85% in place of rec=100%)
that reclaims many cartridges.

What is your RECLAMATION value for your cartridge storage pools?

Best regards

Francis.


-----Message d'origine-----
De : Robert Bunt <rmbunt AT NYSEG DOT COM>
De : Robert Bunt <rmbunt AT NYSEG DOT COM>
À : ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
Date : lundi 19 avr. 1999 18:52
Objet : Expire and reclaim after 3.1.2.20 Upgrade


>We have just upgraded our ADSM/MVS server to 3.1.2.20 over this past
>weekend.  Following the normal process checks, the EXPIRE INVENTORY
>command was executed.  This ran for approximately 36 hours and issued
>a successfully completion message.  This is only set to run once a week
>by schedule.
>
>Today, we ran the follow up to the upgrade which was the execution of the
AUDIT
>RECLAIM Utility.  The message was returned that no items were identified
>as needing to be processed.  The RECLAIM_ANALYSIS table was empty.
>
>I had expected that (at the very least) the growing number of backup copies
>found in the inventory would be reduced to the VEREXISTS parameter as
>set up in the copygroup.  The large number of tapes that had grown to hold
the
>non-expiring inventory are still present and do not appear to be going away
>anytime soon.
>
>Did I miss something?  Should one or both of these utilities reduce the
>inventory
>back to what is specified in the respective management class copy groups?
>