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



On 19 Jul 2013 14:27, Scott Klement wrote:
<<SNIP>>

In CL, I would either use RTVSYSVAL QDATE -- in which case, I'm
always very careful not to make any assumptions about what the date
format will be. (That's another thing I've been bit with far too many
times.. people assume that QDATE will be in MMDDYY order, and then it
gets run on a system with DDMMYY or YYMMDD and the program goes
haywire...)

Yet another reason to use QDATETIME vs QDATE if retrieving either or both of the date and time from system values. For QDATETIME the format of the value is fixed\static vs variable according to DATFMT and DATSEP [or TIMSEP] of the job, thus one can depend consistently on the "format of the field is YYYYMMDDHHNNSSXXXXXX where YYYY is the year, MM is the month, DD is the day, HH is the hours, NN is the minutes, SS is the seconds, and XXXXXX is the microseconds."

Easiest way to make sure the date format is consistent is to use
CVTDAT FROMFMT(*SYSVAL), to convert my QDATE field to a known format.

<<SNIP>>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.