Re: SQL's TIMESTAMP_FORMAT causes MCH3601 -- MIDRANGE-L

Subject: Re: SQL's TIMESTAMP_FORMAT causes MCH3601
From: Dan <dan27649@xxxxxxxxx>
Date: Thu, 26 Jan 2017 16:30:57 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

No, for three reasons:
1) The the date and time values are generated by IBM's DSPJRN.
2) As we saw in the problem you diagnosed for me a few days ago, I was
getting data mapping errors, which is what I would have expected if we had
bad data today.
3) Finally, the exact same query using the exact same data completed
successfully the second time I ran the query, in the same interactive SQL
session.

- Dan

On Thu, Jan 26, 2017 at 4:22 PM, Arco Simonse <arco400@xxxxxxxxx> wrote:

Have you analyzed whether the contents of jodate and jotime in your
selection are valid date and time representations?

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