Re: DB2 zoned data issue with SQL

Interesting option B Luis. I’m on this project to begin with because I had to write a trigger pgm *after that actually gets off loaded to batch for processing. Long story I’m not going to get into.
What will one more trigger pgm *before hurt!? Jk.

The solution is to going to be to determine those culprit pgms and modernize them!!

Thanks for the input.

Jay

Sent from my iPhone

On Oct 18, 2019, at 4:07 PM, Luis Rodriguez <luisro58@xxxxxxxxx> wrote:

Jay,


As I see it you could either:


a) Recreate the table using SQL. A table created with SQL simply does not
allow invalid data to be written. Your COBOL programs would send an error.
That would help you to fix the error(s) at its origin.


b) Not sure about this one but, what happens if you create a BEFORE INSERT
trigger? You could check and fix the zoned field's integrity BEFORE it gets
written to the table.



Regards,

Luis
Luis Rodriguez

--

On Fri, 18 Oct 2019 at 15:17, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:

So our database has data output to it daily by older cobol/rpg pgms.
The system has been around FOREVER.

Getting more into sql and have discovered an issue with some data columns
that have "invalid" data values in the zoned data fields.

This does NOT play well with sql. When sql issues an insert using data
from this source, it errors and from my pretty extensive research in the
past, there is no way to "handlle, massage, or prepare" the column values
prior within the same sql statement.

The fix to clean the data is simply a 3 line coded pgm such as...

h alwnull(*inputonly) fixnbr(*zoned)
f filename up e k disk
c update rcdfmt

Thats IT! all rows are processed and re-initialized correctly for the
zoned data columns.

We are at a point with SQL development that we really need to get to the
bottom of this and get it fixed.
Has anyone dealt with this before and what was the actual cause and
solution?

TIA

Jay
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com