|
Makes sense... -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Darrell A Martin Sent: Friday, January 12, 2007 9:09 AM To: Midrange Systems Technical Discussion Subject: RE: Creating a physical AND Logical file Hi, Dave: I see no reason for putting QTEMP at the *bottom* of a library list, as a general rule, but you pays your money and you takes your choice. For us, the standard (as far as user profiles or job descriptions go) is to put QTEMP at the top of the user portion of the list. The exception is for programmers. In their cases, QTEMP is placed after the profile's development library. This allows a programmer to place a data object with modified data in his/her development library and test, without having to change code that creates and populates the equivalent object in QTEMP. In other words, situations where the existence of the object in the "higher" library is conditional but in QTEMP expected. Darrell Darrell A. Martin - 630-754-2141 Manager, Computer Operations dmartin@xxxxxxxxxxxxx midrange-l-bounces@xxxxxxxxxxxx wrote on 01/12/2007 08:36:10 AM:
Wow! QTEMP is ONLY used by the current job. Objects in that library have to be created BY that job for use by that job ONLY. We ALWAYS have QTEMP at the top of the user portion of the library list. I don't
know of ANY value for QTEMP that would place it at the end of the list... ??? What am I missing here?? Dave
-- 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 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.