× 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.



thanks for that Dave... i'm certainly going to look into that.
Ultimately need the data cleansed and the bleeding to stop but this could
be a good way to cope in the meantime.

Jay

On Tue, Oct 22, 2019 at 11:19 AM <dlclark@xxxxxxxxxxxxxxxx> wrote:

"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
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331





*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.

*********************************************************************************************
--
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.