RE: Doohickey to visually show relationships between files

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

>The hit comes from access path maintenance....

But, if you need in access path to enforce, say, the relationship from
Order Detail to Order Header, you'll need an index on Order Header by
Order Number. Chances are you already have that, so is there really a
hit for index maintenance, since that index is already there?

-Walden 


------------
Walden H Leverich III
President & CEO
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
 
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Thursday, July 01, 2004 7:45 PM
To: Midrange Systems Technical Discussion
Subject: RE: Doohickey to visually show relationships between files

db

The hit comes from access path maintenance - that is separate from what
the 
system does that is the same as the RPG code did - but the system may 
handle that stuff better, so maybe there's a tradeoff?

About the "could" - isn't that the face-saving word of the hour from IBM

all the time?   ;-)

Vern

At 12:20 PM 7/1/2004, you wrote:
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx / Vern Hamberg
> >
> > But putting RI into things has implications for performance and
> > changes in
> > applications. RI will generate messages you need to handle, it'll
> > actually
> > DO things you used to do in code, etc. And every constraint is
actually
> > maintained as an additional access path, so performance could have a
hit.
> >
> > ;-)
> > Vern
>
>Knowledge will come with practical experience, I'm sure, but I wonder
why
>performance would suffer if you're letting the system handle the stuff
you
>would otherwise do in RPG (or other) code.  If anything, I would think
>performance would be better.
>
>I did see that you qualified that with "could".
>
>db


--
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.