|
*Badly formed data can trigger data mapping error*
Prior to V6R1, if there was badly formed data in decimal or zoned fields
within physical files, it was
dependent on the query implementation and the interface as to whether an
SQL0406 or an SQL0802 data
mapping error would be signalled. In V6R1, there is better detection for
data mapping errors caused by
badly formed decimal and zoned data in non-SQL tables. It will be more
likely that an SQL0406 or
SQL0802 will be seen on V6R1. It will be necessary to correct the badly
formed data within the physical
file to avoid the data mapping error.
As an Amazon Associate we earn from qualifying purchases.
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.