× 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.



My 4.4.0 ISQL returns dates to me in *MDY format despite the job's DATFMT.
This is causing some confusion among some auditors who want to see 4 digit
years like we told them we're using.

ISQL seems to disregard both the job date format and the DATFMT parameter on
STRSQL.  It returns dates like 01/18/00 no matter what the date format is.
I suspect it uses QDATFMT but I can't change the date format on my machine
to test it out.

QMQRY respects the job date format (sort of) - it uses the full 4 digit CCYY
instead of the expected YY, but that's okay.

Timestamp fields are always displayed in timestamp format
CCYY-MM-DD-hh.mm.ss.millis

I could not find any PTF's or APARs on this; the closest being SF54193 -
CHAR(date) uses job format instead of SQL date format.  

Does anyone with a system QDATFMT other than MDY see *ISO dates in their
QDATFMT?

Buck Calabro
Commsoft; Albany, NY
"Nothing is so firmly believed as
 that which we least know" -- Michel Montaigne
Visit the Midrange archives at http://www.midrange.com and the FAQ at
http:faq.midrange.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.