Re: DB2 zoned data issue with SQL -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 10/18/2019
03:17:04 PM:

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?

Seems to me this can be handled by using an extended indicator
array. This allows SQL to flag (-2) the invalid data rather than erroring
out.

Sincerely,

Dave Clark

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.