Not a good idea.
Some applications make a copy of a file and put it into QTEMP and then do 
an OVRDBF for a particular application to go to QTEMP.  If, however, you 
put QTEMP in the system library list this same file may be used for 
regular production applications (granted, still in the same job).
I know of some things which would spiral downward rather quickly if 
someone did this.
If it is put into the library list I've only seen it at the very end of 
the user library list.
If you're trying to test one particular task, and you don't want to modify 
the code with any overrides, then just have that one job temporarily put 
it at the top of it's user library list.  If you're trying to qtemp an 
object normally in a system library like QSYS or QUSRSYS, then you're just 
screwed.  Figure out an alternative.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.