I am about to do this upgrade on an OS/390 1.3 server platform
(mainframe).  I have read many letters in this bulletin board about the
Expire Inventory not working properly in earlier releases and running long
at 3.1.2.xx releases.  I am at server 3.1.1.3 now, about to go to 3.1.2.20.
I read the Samplib member about the AUDIT RECLAIM process you speak of and
the UPGRADE option that needs to be specified.
1.      Where and when and how often do you specify UPGRADE?
2.      Is it a PARM on the execute card of the ADSM address space JCL?
3.      Do you specify it only the first time you come up under the upgraded
software?
4.      After you have come up successfully, do you remove the UPGRADE
phrase?
5.      It sound like the AUDIT process is performed after you have come up
with UPGRADE specified. Is that correct?
6.      I have read of other users whose first EXPIRE INVENTORY took days to
execute.  It sounds like you expected that.

        I am very interested in your experience upgrading to 3.1.2.20. Do
you have any tips or warnings? We are upgrading all our clients first to
3.1.0.6 before we do the server.  I would be very greatful for any info on
your testing plan and the  confirmations that were done after you upgraded.
I plan on backing up all my ADSM files using DF/DSS ad well as the ADSM
database backup utility before upgrading.
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:   Robert  Bunt [SMTP:rmbunt AT NYSEG DOT COM]
        Sent:   Monday, April 19, 1999 10:51
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        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?