Re: Long SAVSYS -- MIDRANGE-L

Subject: Re: Long SAVSYS
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Mon, 22 Apr 2013 19:01:11 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Long SAVSYS , Bakutis, Becky

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.