Re: Update file definition with a LOT of records - best approach?

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Good idea to have a primary key on the physical file.  You'll have no need
to ensure that your unique's stay unique like one person warned you of.

If you decide to create a read old / write new HLL program to copy the
data from the old into the new then you could drop the K in the F spec and
that might help blocking.  Using a primary file (if you are using RPG)
will help the system do the blocking automatically for you.

However, if the bulk of your access to this file is by the primary key,
then this might not be a bad time to sort it.  Therefore you might want to
read it by key and write it to the new file.  This should help your
performance (in the long run - a penalty might be incurred during the
conversion).  Or read the old data by the logical which is most important
to your business - performance wise, (provided the select/omit are not
prohibitive).

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin