Re: Database server jobs and SQL tuning

Al,

I seem to remember reading the same thing, in one of Mike Dawson's security 
handbook things.

As I recall it, the reason for not hard-coding libraries was that the users 
authority to each of the libraries in the library list is resolved at start 
of job and kept for use throughout the job whereas qualified references 
have the authority resolved for the library and object each time they are 
referred to.

I don't know if this is still the case or even if what I remember is/was 
the correct interpretation, but I was certainly taught the same as you, 
albeit in the school of experience not the classroom.

Of course maintaining hard-coded references teaches us that even if it was 
quicker performance wise who wants the maintenance and management penalty ? ;)

Cheers
Evan Harris

>John Earl also challenged what I thought I had learned in IBM school.  I did
>not remember which programming class this was in, so I dug into notes on
>several but did not find the specific reference.  I did find many references
>to how security can impact performance, so it should be used wisely.
>
>In IBM's CL class S 6020 introduction page 1-61 I was told not to qualify
>libraries in CL ... it is asking for trouble ... I think it is here that I
>learned the topic you ask if I have documented

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---