RE: blank records in file

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Sad to say but there are still many applications that rely on traditional
5250 programs to prevent duplicate records.
Chain to file, if record does not exist, assume add, otherwise assume
update.
But do not use unique keys.  Have you ever heard of SSA's BPCS?  Their
item master allows duplicate keys.  They leave it strictly up to their
Item Master Maintenance program to prevent duplicate keys.  But we've had
some cases of duplicate keys.  Probably something we've done here with the
merging and separation of companies databases all the time, using some
homegrown program.

I am a big fan of controlling whatever you can with the database.  Be it:
Referential Integrity, constraints, triggers or a combination of all
three.  Lock it down so that you can't even mess it up with UPDDTA or
WRKDBF

<snip>
However, I think it's much more likely that someone did something wrong on
the iSeries. Also, don't you have a unique key on that file? Wouldn't the
second blank record have violated the unique key constraint?

-Walden
<endsnip>



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