---------------------------- Top of message ----------------------------
>>--> 11-21-02 14:07 S.SHEPPARD (SHS) Re: Cleanup backupgroups,
Matt: I second Bill's comment about the clarity of the history of this
problem. I have also been running the 4.2.2.0 OS/390 server for 6+
months but I see no apparent problems with system objects. I'll run
the cleanup when I go to 4.2.3 in a couple of weeks, but I believe that
the OS/390 4.2.2.0 server probably just doesn't have this problem. You
should be able to verify that with support.
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
-----------------------------------------------------------------------`
---------------------------- Top of message ----------------------------
>>--> 11-21-02 11:44 ..NETMAIL () Re: Cleanup backupgroups,
Date: Thu, 21 Nov 2002 14:41:19 -0500
From: "William F. Colwell" <bcolwell AT DRAPER DOT COM>
Subject: Re: Cleanup backupgroups, system objects
To: ADSM-L AT VM.MARIST DOT EDU
_________________________________Top_of_Message_________________________________
Matt - I recently did the same server upgrade and got the same
result doing cleanup backupgroups -- 0 anything deleted.
I have never been clear on the history of the problem, that is
what server levels caused it. So I have to wonder if the cleanup
command still has a bug in it for the OS/390 server, in that it didn't
find any problems. I am thinking of calling in a problem to IBM/tiv.
My server level history is -
4.2.1.9 (for quite a while)
4.2.2.10 (a month?)
4.2.2.12 (a month?)
4.2.3.1 (starting 11/16)
Just before going to 4.2.2.12 I suppressed all system object backups
because of severe performance problems.
Bill
At 01:41 PM 11/21/2002, you wrote:
>We assumed we had the dreaded "system objects" problem because we
>were running 4.2.2.0, we have a bunch of Windows clients, and our
>database was growing at a rate that we didn't like.
>
>So a couple of days ago, we upgraded to 4.2.3, and ran CLEANUP BACKUPGROUPS.
>It didn't seem to accomplish anything. It finshed fairly quickly,
>compared to some of the reports I've read here, and finished with the
>message:
>
>ANR4730I CLEANUP BACKUPGROUPS evaluated 28729 groups and deleted 0
>orphan groups with 0 group
>members deleted with completion state 'FINISHED'.
>
>
>Somebody on this list suggested using the command
>QUERY OCC * "SYSTEM OBJECT"
>
>to get an idea of how bad the problem was. I tried that, before and
>after the upgrade, and got the same result: zip
>
>tsm: UKCCSERVER1>QUERY OCC * "SYSTEM OBJECT"
>ANR2034E QUERY OCCUPANCY: No match found using this criteria.
>ANS8001I Return code 11.
>
>
>This doesn't seem to make sense to me, because if I pick a client at
>random and issue a query occ for that client, I see some system
>object filespaces.
>.
>.
>
>.
>The pieces just don't seem to be fitting together. What am I missing?
>--
>
>
>Matt Simpson -- OS/390 Support
>219 McVey Hall -- (859) 257-2900 x300
>University Of Kentucky, Lexington, KY 40506
><mailto:msimpson AT uky DOT edu>
>mainframe -- An obsolete device still used by thousands of obsolete
>companies serving billions of obsolete customers and making huge obsolete
>profits for their obsolete shareholders. And this year's run twice as fast
>as last year's.
----------
Bill Colwell
C. S. Draper Lab
Cambridge Ma.
-----------------------------------------------------------------------`
|
