|
RE: Re: Performance Question - Authority check rate exceeded guideli >John, >> At 10:54 AM 11/19/97 -0500, you wrote: >> I have a system where the performance tools Advisor function is informing me >> <SNIP> > One source of excessive authority checks can be when a job has to > continually re-resolve itself to an object, especially a program. A typical > example could be a where program A calls utility program B, and B returns > with LR on (or B is a OPM CL that closes completely). > I have also heard (but havn't verified this myself) that if a program name > is a variable in an RPG program (as opposed to a declared literal), the OS > is forced to resolve to that object each time it is called. The alleged > reason is that a variable name can be changed, so the authority checking is > forced. >jte No On a variable name call, It is only resolved the 1st time. OS/400 checks to see on each subsequent call if the variable has changed. If it has not, OS/400 doesn't resolve it again. This was changed a loooooong time ago. It used to be that way on the SYS/38 but was changed I think on one of the first releases of OS/400. John Carr +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.