RE: MIDRANGE-L Digest, Vol 5, Issue 1682

By adverse effects I mean when having to upgrade the vendor software,
apply PTFs, etc.  This will mean additional changes that have to be
maintained when file structures, etc change.  Also it can cause issues
with disk space, performance, etc.  I also dislike having the same
constrinats with using PF triggers etc.  When they use CRTDUPOBJ en
masse, the triggers also get copied to the duplicate objects & cause
programs to fail due to CLRPFM, etc.  Which is also a good argument for
using CPYF to create the temporary files on the fly, that way triggers,
etc are included in the dup obj.

Granted the performance hit may not seem like much but when the software
package you are using (due to our implementation anyway..)  The vendor
supplied files are replicated across hundreds of libraries.  That tends
to consume a lot of disk space.... 


Thanks,
Tommy Holden


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Wednesday, September 06, 2006 8:50 AM
To: Midrange Systems Technical Discussion
Subject: RE: MIDRANGE-L Digest, Vol 5, Issue 1682

"Since adding indexes can sometimes have adverse effects on some base
code"

Huh?

Since when, what adverse effect?

If you add lots of indexes on a volatile file, you could see a
performance hit due to index maintenance.  But other than that, I'm not
aware of any "adverse effects" indexes might have on base code.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Holden Tommy
Sent: Wednesday, September 06, 2006 9:27 AM
To: Midrange Systems Technical Discussion
Subject: RE: MIDRANGE-L Digest, Vol 5, Issue 1682


If only I could...in our shop our main software package is a 3rd party
software & the mandate is to not change or customize the base product
unless it's just a "have-to" case.  Since adding indexes can sometimes
have adverse effects on some base code it's just not always a viable
solution (not arguing at all..In fact I support index usage
whole-heartedly...) unfortunately some of us have to march to the beat
of someone else's drum =(


Thanks,
Tommy Holden