You hit the nail on the head. Proper design is critical. These guys are
building indexes on the fly. To make matters worse, their implementation of
the DataMirror software for replication to other platforms depends on (wait
for it)...............................
Relative
Record
Numbers
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Thursday, December 01, 2016 10:34 AM
To: Midrange Systems Technical Discussion
Subject: Re: IBM i and Java
I suppose you can look at it like this. Suppose you're an all RPG shop.
But you've got this old timer working there who refuses to put any key(s)
on a PF because he remembers something from the System/32 about rebuilding
a PF and the difficulties involved if the PF has a key on it.
He also seriously limits you from building any indexes on any tables
because he remembers an old John Sears lecture about performance and how
index maintenance can inhibit performance.
So instead his solution is that you write all your RPG with no indexes.
You have to write it by reading in the entire table and doing sorting in
RPG. Any chaining is strictly limited to chaining by relative record
number only.
This is basically what you are doing when you ignore SQL index advice and
you start doing a bunch of "order by" or "where" clauses without building
the proper indexes. It can be done, but it's going to hurt.
Rob Berendt
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.