|
I found IBM's response to my issue from our system's manager for anyone at V5.2 that might run into this issue also. <snip> It sounds like you are running into the fact that SQL and DDS create different field format IDs for timestamp fields before R530. This is a problem that has been around since the integration of SQL onto the system that has only been discovered recently. Unfortunately, although we've fixed the problem at R530 we currently do not plan to provide a fix for earlier versions. Essentially, you will only encounter the problem if you try to replace a table which was previously built with DDS with the same table created by SQL, or vice versa. The workarounds discussed in the email you included will take care of the problem. </snip> Thanks, Matt
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.