RE: Private Authority

Chris,

Per the quote below from the Performance Tools manual, the results may
be overstated in your Advisor report.  This would depend on whether the
private authorities were cached in memory or not, the tools do not
differentiate.

"Collection Services counts each authority lookup. The advisor function
and
the redbook, AS/400 Performance Management V3R6/V3R7, SG24-4735,
provide CPU utilization estimates based on the number of lookups per
second and the processor rating. Because of this caching capability, the
counts are incremented as if they were not cached. Therefore, beginning
with V3R7, the effect on the CPU utilization counts could be much less
than the advisor message and the redbook would indicate."


An authority lookup will occur if you have restricted access to your
files.  Specifically if an object has private authorities which are more
restrictive than public authorities, the system will need to check that
the user is not specifically restricted.  Thus if you have public
authority of *use but have granted some users or groups *exclude
authority, the system will need to check that the user is not excluded
either individually or as a group member.  This would occur even if the
user is a member of the group which has access to the object.

The easiest way to avoid authority lookups would be to have fairly
restrictive public authority and rely upon the object's primary group or
have a group profile own the object.

Regards,
Andy Nolen-Parkhouse