“Empty” fields shouldn’t contain junk values – they should be null if null is allowed or blank or zero.
Somehow you can get corrupt values
columns have been added and the LVLCHK is set to NO
RPG program uses internal field definition which is incorrect
Finding them … what does the junk look like?
Thanks for the Update Phil,
The programs are developed in COBOL and the field’s appears filled with ++++++++++++ sign.
Do revert if you find anything which would help prevent these Junk values.
I’m certainly not a COBOL pert — you might want to repost this with the keyword COBOL/400
Here would be my questions before proceeding
1. ++++ In both both numeric and char fields?
2. Is your application intentinally putting this in the fields?
3. Do the files have this as a default value?
4. Does your application need the ++++++++++ in these fields?
5. Can you do some “post” processing of these files prior to sending them to Oracle?
Scan and entire file (actually 1 member) – DSPPFM – find ++++ this would allow you to scan one file at a time.
I think a CL program + COBOL or RPG could be written which
1. Driving by a file containing the names of files
for each file
2. Overrides the file to an internally defined long record file
3. reads each record in file
4. if record contains +++ writes filename, record #, starting position to an error file or error report
or changes it to spaces(?)