I don't think that future maintenance argument holds any water.
UNIQUE
R ABR
MYKEY 5A
MYDATA 10A
K MYKEY
If I change the size of MYKEY to 11A and then run a CHGPF against it I had
no problems. ALTER TABLE also worked great (and much faster).
I also find that obscure "if you need to do something temporarily that
would violate the unique key requirement" without a lot of merit as,
having suffered through a few mergers and stuff where having the unique
key enforced would surely have helped.
Again, (from "The Outlaw Josey Wales") "if any of you just has to", you
could always use the CHGPF to remove the key.
At least no one said the "well, on release ... on CPF on the S/38 it was
recommended to not have any keys on the physical because...".
Our packaged application uses no unique keys as all updates are supposed
to come from their standard maintenance programs and you should never
perform mergers and stuff.
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.