Re: Add libraries to QSYSLIBL or QUSRLIBL

Charles,

In stead of adding the libraries to a library list, copy the commands of those 
tools (if there are any) to QGPL and reference the "product library" parameter 
on the command to the original library.

In that case you use the product library slot in the job's library list 
(maximum 2). Beware, those libraries are not "transferred" to a batch job when 
submitting such a job.

Unless you want to use all three utilities in one programme at once.

Just a thought.

Regards,
Carel Teijgeler.

*********** REPLY SEPARATOR  ***********

On 28-1-04 at 13:55 CWilt@xxxxxxxxxxxx wrote:

>We've recently purchased a set of tools that should prove useful for all 
>users. FYI: the tools are for converting/emailing spool files.
>
>My initial thought was that since the tools were for all users, we should 
>simply add the (3) libraries to the QUSRLIBL system value.
>
>But there is a minor concern about going over the 25 library limit for the 
>user library list.  (Yes, I'm aware that this can be increased >but that's 
>another can o'worms ;-)
>
>So I started thinking about adding them instead to the QSYSLIBL. 
>Currently, our QSYSLIBL is still using the default IBM provided QSYS, QSYS2, 
>QHLPSYS, and QUSRSYS.
>
>But I'm wondering how appropriate that would be.  Are there any gotcha's if I 
>do this?
>
>Thinking about this led me to wonder if there are any guidelines for what 
>belongs in QSYSLIBL vs. QUSRLIBL.  
>
>At my last position, I added a "Company's system library" to the QSYSLIBL. It 
>had some modified versions of IBM QSYS objects for >the most part.  So it made 
>sense to put it in the QSYSLIBL.  But I'm curious as to what you all put in 
>there.