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

Subject: RE: DB2 zoned data issue with SQL
From: Rob Berendt <rob@xxxxxxxxx>
Date: Fri, 18 Oct 2019 21:02:12 +0000
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>

If your trigger program is reading the file that's an issue. It should be passed the datastructure directly. However, if your trusting the DS to be valid you'll run into the same issue.
Funny thing is, you could clean up your data, redefine your tables with DDL, and might still have a garbage DS in the trigger IF it is the program writing the trigger that's corrupting the data because a before trigger gets called prior to DB checking integrity (I think).

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.