RE: Creating a physical AND Logical file

That's why we use the EXTFILE keyword if we need QTEMP, and don't depend 
on OVRDBF's being issued higher up the callstack.

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----



"Holden Tommy" <Tommy.Holden@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/01/2007 17:14
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Creating a physical AND Logical file






My 2 coppers...

There are times when it may be necessary to allow temporary objects
inserted first in the LIBL.  Since all programs would have to be
modified & hard coded to QTEMP (or any other intermediary library for
that matter) it just makes more sense to leave the programs where they
point to the first library with the object.  I prefer not hardcoding at
all (and this can be done...so why make life harder...).  Can YOU
guarantee that a programmer will not forget to override to QTEMP when
they should be??? And if they did...how long would it take to discover
that error & then patch the data that got inadvertently got
updated/deleted/added to the actual production files??


Thanks,
Tommy Holden