|
The average raw user wouldn't use QTEMP as a query output. Query defaults to *CURRENT. Which, if your shop has the default of QGPL, results in a lot of files being created in QGPL and left there forever. Then you get the issue where company A (who has their own datafile library) is using the data from a file in QGPL from company B (who has a different file library). And I tried changing a bunch of these problem children's default current library to their library (named after their user profile). The problem is that the current library appears before any USRLIBL libraries and we were running into the exact problem of using the wrong library. So if you want to stick a library above USRLIBL for inserting test files or versions of programs, then run a command created with PRDLIB(yourLibrary). For a sample of how this works do a DSPLIBL - before executing the command STRPDM - after executing the command STRPDM but while you are still at the menu - after backing out of the menu presented by STRPDM You could use CHGCURLIB but that could get you into a sticky situation for objects created on the fly. Rob Berendt
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.