RE: recs with invalid data

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>Alternatively, write a 2 line Update Primary program to read all
>records & update them and compile IGNDECERR(*YES).

It hasn't been my experience that IGNDECERR(*YES) will "fix" the invalid
data when updating the record, so I decided to test it out.  I found a few
surprises.

If I define a file via SQL, I cannot use CPYF to put invalid decimal data in
it!

If I use DFU, I can specify the record number, field exit, F23 (not enter)
and delete the record.

I built a file with a 5 char alpha field and inserted several records:
"BAD"
"12345"
")(*&^"
"....."

I then did a CPYF to a file with a 5 zoned numeric field to cause decimal
data errors.  Here's what it looked like:
*...+
BAD
CCC44
21400

12345
FFFFF
12345

)(*&¢
54554
DDC0A

.....
44444
BBBBB

I ran this small program over it:
     FDDEN    UP  E                    DISK
     IDDENR       01
     ODDENR   D        01
     O                         FIELD1

and got this:
*...+
21400
FFFFF
21400

12345
FFFFF
12345

12345
FFFFF
12345

12345
FFFFF
12345

I don't think this is what was expected.  This is at V4R5.  Is there a
difference at another CPF level?
  --buck