|
Dennis--Generally, we put QTEMP at the top of our library lists. This allows a job to create work files and have them automatically selected over the files in the permanent libraries.
QGPL is normally system-type files; we place it nearer the bottom of the list.QUSRSYS wasn't in your list, but we place it near QGPL (usually before QGPL); this is user-created system-type files (ie outqs, jobqs, etc.).
Data files "should" be above program libraries, in case a data file slips into the program library by mistake. We normally lump data files, data areas, and data queues in the same library-- these are all objects that can be changed during the course of normal operations, so they can be in the same library.
midrange.com
So for production jobs I'd recommend:
QTEMP
DBLIB
SELIB
RTLIB
QUSRSYS
QGPL
When running 'fixit' type maintenance programs I will usually run
jobs with QTEMP at the bottom of the list to make sure the fix really
hits the permanent database files.
--Paul E Musselman PaulMmn@xxxxxxxxxxxxxxxxxxxx
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?
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.
