---------------------------- Top of message ----------------------------
>>--> 12-18-02  08:59  S.SHEPPARD     (SHS)    Re: Cleanup Backupgroups

We also just went from 4.2.0 to 4.2.3 on OS/390 2.10.  Ran Cleanup on
both of our servers.  It ran for maybe 10 minutes and finished with no
errors reported.  If you are finding that it is not finishing in 5 or 6
hours, I would guess that there probably is some cleanup going on though.

Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
-----------------------------------------------------------------------`


---------------------------- Top of message ----------------------------
>>--> 12-18-02  08:57  ..NETMAIL     ()     Re: Cleanup Backupgroups
Date: Wed, 18 Dec 2002 16:53:17 +0000
From: "John Naylor" <john.naylor AT SCOTTISH-SOUTHERN.CO DOT UK>
Subject: Re: Cleanup Backupgroups and Expiration Processing
To: ADSM-L AT VM.MARIST DOT EDU
_________________________________Top_of_Message_________________________________

Are you sure that you need to run cleanup backupgroups.
I did not think this problem impacted os390 TSM servers.
I am on 4.2.2 and I do not think I kave a problem with this.






Cinda Mullen <cmullen AT ascensionhealth DOT org> on 12/18/2002 04:36:26 PM

Please respond to "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>

To:   adsm-l AT vm.marist DOT edu
cc:    (bcc: John Naylor/HAV/SSE)
Subject:  Cleanup Backupgroups and Expiration Processing



TSMers...

We are running OS390 2.10 with a 4.2.3 TSM Server.

We upgraded to 4.2.3 in November and have been running cleanup
backupgroups off and on since that time to try to get the system object
issue resolved.  (Sure wish there was a duration parameter for the
cleanup so, we could stop it automatically instead of having to babysit
it on the weekends:)

Some days we skip the running of cleanup backupgroups and run expiration
processing to try to catch up on expiration for all the other things.

It just seems like we are going in circles, run cleanup...stop it...run
expiration...etc. and nothing ever gets caught up.

How is everyone else doing this?  IBM could give us no idea as to how
long the cleanup backupgroups might take to get all the way through.
I'm guessing we've ran it at least 20 days for 5-6 hours each day and we
don't know how much longer we will have to run it.

And, we are not getting all the way through expiration processing like
we used to do because we used to run it daily and now it is just once or
twice a week.

Anyway, was just curious as to how everyone has handled this monster and
how long it finally took to get everything cleaned up.

Thanks in advance for any input.

Cinda Mullen
Ascension Health ISD


-----------------------------------------------------------------------`