× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



what i usually use is :

First - QTEMP
2 to n My libraries (files, pgm ....)
last - QGPL

Because i often use work files in QTEMP, and i am not sure of what is in
QGPL so i put it on last.

----- Original Message ----- 
From: "Dennis Nel" <dvnel.za@xxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, September 08, 2005 2:38 PM
Subject: Sequence of libraries in Library List


> When setting up a new JOBD what is the "best" sequence for the libraries
on
> the library list?
>  In particular I am refering to libraries like QGPL and QTEMP. Should the
be
> at the top of the LIBL or towards the bottom?
>  In the following example in which sequence would be best?
>  We have our runtime objects (*pgm, *DSPF, *PRTF) in library RTLIB .
> Our database (*PF, *LF) in library DBLIB, and other objects (*Dtaara,
*dtaq)
> in SELIB.
>  should the *LIBL look like, QGPL, SELIB, RTLIB, DBLIB, QTEMP?
>


----------------------------------------------------------------------------
----


> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.