×
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.
The describe scenario, although it may be subject to a similar
concern for the Date/Time/Timestamp Date Separator issue, is actually at
least in part, a direct consequence of there being no support in SQL to
effect the DATFMT(*EUR) in an SQL TABLE.
FWiW, the original "working as designed" response to the noted PMR
[before an APAR was even opened] was due to a misinterpretation, by the
support person on the call, of the initial developer response; i.e. it
was never _the_ response, neither before nor after any pressure to fix
it :-) Since the DATE data type had already been /corrected/ for the
same issue, it was just a matter of extending the same change to more
data types -- as described in the Info APAR II14134. It is unfortunate
that I did not think to investigate the TIME and TIMESTAMP when the
first issue came up for DATE [very odd, because I typically would have;
probably because I passed on providing a fix], because then they could
have all been done on the first pass instead of with a second set of PTFs.
Regards, Chuck
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.
midrange.com
