Q:
Increasingly lengthy SAVSYS times
Our time required for SAVSYS is growing, and we have not had much success with IBM on getting answers on why and how to fix.
We orginally thought the bulk of the time was with the SAVSECDTA, and then discovered user profiles owning large numbers of objects - most being scanned images. However, the private authority on these objects is not large, so...?
If it is the SAVSECDTA portion that is slowing us down, what can we do?
IBM is saying we should clean up the profiles in question that are unusually large, but how do you do that since someone hsa to own the objects?
Is anyone else having a problem with growing SAVSYS time as a result of the number of objects growing?
Would distributing the ownership of objects between other profiles shorten the amount of time our SAVSECDTA takes? If so, can you do that by selecting a group of objects to change their owners rather than doing them all at once or one at a time?
Any suggestions would be appreciated!
We orginally thought the bulk of the time was with the SAVSECDTA, and then discovered user profiles owning large numbers of objects - most being scanned images. However, the private authority on these objects is not large, so...?
If it is the SAVSECDTA portion that is slowing us down, what can we do?
IBM is saying we should clean up the profiles in question that are unusually large, but how do you do that since someone hsa to own the objects?
Is anyone else having a problem with growing SAVSYS time as a result of the number of objects growing?
Would distributing the ownership of objects between other profiles shorten the amount of time our SAVSECDTA takes? If so, can you do that by selecting a group of objects to change their owners rather than doing them all at once or one at a time?
Any suggestions would be appreciated!
ASKED:
Jan 4 2008 9:17 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
A:
RATE THIS ANSWER
0
Click to Vote:
0
Click to Vote:
- 0
0
Then run some DSPOBJD reports to files, and query them by owner ID.
You should have some figurative profiles on the system - QPGMR is a favourite, and maybe QUSER.
Set up individual profiles to be members of the appropriate group profile - so all users are members of group QUSER.
From your reports, identify objects which are owned by 'wrong' profiles. Use CHGOBJOWN to change the owner to become one of your group profiles.
a simple loop around a dspobjd output file - or a query output from the dspobjd will alter lots at a time.
