×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I will be running this command today. Thanks for reminding me it existed. I also forgot that SAVSECDTA is part of the SAVSYS until I read the help text. We run the SAVSECDTA every day and last night it ran 1945-2101 so I agree this is the culprit besides running the SAVSYS on a tape drive going bad.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Monday, April 22, 2013 7:01 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Long SAVSYS
On 22 Apr 2013 17:59, Steinmetz, Paul wrote:
<<SNIP>> SAVSYS includes a SAVSECDTA.
I agree with Pete, it is probably one or more user profiles.
DSPOBJD OBJ(QSYS/*ALL) OBJTYPE(*USRPRF)
Profiles taking more than 999,999 could be your culprits.
<<SNIP>>
Probably better and even much easier to use the Print Profile
Internals (PRTPRFINT) CL command instead. That command was created
specifically to assist one to quickly diagnose /large/ amounts of
authorities for a specific user or all users. The command offers
reporting by selection from all users, to include those users which
exceed a certain percentage of their limit; i.e. issuing the request:
PRTPRFINT SELECT(*PCTFULL) PCTFULL(some_percent_full_value). I provided
a link to the docs in a prior reply.
midrange.com
