I talked to IBM Q & A/Usage/Installation & Configuration Support this
morning about this phenomenon.  He told me that since we are coming from
3.1.1.3 to 3.1.2.20 we should not see a protracted Expire Inventory because
the problem with not expiring properly occurred after the 3.1.1.3 release.
Your experience is most interesting. I will forward your  e-mail to the  IBM
support person and let's see The response. Please keep me informed as to
your experience in upgrading from server 3.1.1.3 to 3.1.2.20.
John

John Morlier
Manager of Technical Services and Operations Support
, Integrated Product Data Environment

Avondale Industries, Inc.
IPDE Technology Division

%   Voice: (504) 436-5213
*  Fax:  (504) 437-5534
):    Email:  jmmorlier AT avondale DOT com <kgmyers AT avondale DOT com>


        -----Original Message-----
        From:   Lambelet,Rene,VEVEY,FC-SIL/INF.
[SMTP:Rene.Lambelet AT NESTLE DOT COM]
        Sent:   Tuesday, April 20, 1999 10:01
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: Expire after 3.1.2.20 Upgrade

        Hello dears,

        we upgraded our adsm server yesterday from 3.1.1.3 to 3.1.2.20,
OS/390 2.4.

        Expire processing still running after more than 8h30 elapsed, more
than
        2'000'000 objets inspected, more than 1'000'000 backup objects
deleted! I
        hope I still get backups in my database...

        Will tell you tomorrow the definitive results of this first expire
after the
        upgrade (normal expire time, db size...).

        IBM, please make a note in the installation readme's, about this
long expire
        processing!

        Question: did we got the expire problem even if we never install
3.1.2 and
        went directly from 3.1.1.3 to 3.1.2.20? It seems that the answer is
        positive.

        Regards,

        Rene Lambelet
        Nestec SA - 55, Av. Nestle - CH-1800 Vevey
        Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
        E-Mail: rene.lambelet AT nestle DOT com



        > -----Original Message-----
        > From: Robert  Bunt [SMTP:rmbunt AT NYSEG DOT COM]
        > Sent: Tuesday, April 20, 1999 3:07 PM
        > To:   ADSM-L AT VM.MARIST DOT EDU
        > Subject:      Re: Expire and reclaim after 3.1.2.20 Upgrade
        >
        > John:
        >       I tried to answer the questions as you asked them. Please
see the
        > notes
        >       immediately following
        > your queries.  One additional note I misquoted the person that was
in over
        > the
        >       weekend about the 36 hours clock time to
        > run the EXPIRE INVENTORY.  He corrected me this morning and it
should have
        > been
        >       6 Hours.  He gave
        > me the wrong start time when we spoke.  I did not want to scare
you any
        > more
        >       than necessary.
        >
        >       The reason for my original question is that we have been
amassing
        > far more
        >       copies of datasets
        > without expiring the older versions.  My mailbox backup in Notes
is only
        >       supposed to have 20 Versions at all
        > times.  I checked yesterday and found that I have 30.  The EXPIRE
        > INVENTORY only
        >       appears to have
        > changed the Deactivation Date for the 10 oldest Versions to the
day when
        > we ran
        >       the command.  I thought that
        > some process would start cleaning out all of the un-needed
versions and
        > would
        >       start reclaim processing in
        > my tape pool.
        >
        >                                               Bob Bunt
        >                                               rmbunt AT nyseg DOT com
        >
        >
        >
        >