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

Subject: Re: DB2 zoned data issue with SQL
From: Luis Rodriguez <luisro58@xxxxxxxxx>
Date: Fri, 18 Oct 2019 16:07:07 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: DB2 zoned data issue with SQL , Jay Vaughn

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.