True, and I should have mentioned that possibility. But I only do that for files that are outside of the current ?FLIB?. And then I'll put those in a CL so that qualification (Test or Production) can be determined more easily.

* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



ed stevens wrote:
An OVRDBF before the // FILE statement can be used to qualify the library in the 36EE.

message: 3
date: Fri, 11 Jan 2008 07:47:49 -0600
from: Jerry Adams <jerry@xxxxxxxxxxxxxxx>
subject: Re: QTEMP not in library list

There are some places where one cannot qualify the library, such as the 36EE (although it does have the FLIB command). In a test environment (single LPAR, multiple libraries - test/production) using the library list is pretty much a "must have" for many situations. But I can still do explicit overrides because I know if I am running in a test -vs- production mode. But the programs (CALL's) I usually leave to the library list. Only the tables, data areas, etc., get qualified. Naturally, there are always exceptions to the rule .-)

* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Jeff Crosby wrote:
Crispin,

You took the words right out of my mouth. If the library is always
explicitly coded, why have the library list at all?




____________________________________________________________________________________
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ


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.