That is what I was trying to explain you in my prior post. My apologies
beforehand if it wasn't clear, as my native language is Spanish and
sometimes I don't express myself very clearly in English (my wife would be
of the opinion that I don't express myself clearly in ANY language :-) )
Ok. To the point. If you transform your DATE SQL parameter to receive an
ISO date, it won't matter your date *JOB format. It will always show the
correct date.
For example. If your view could have the following DATE statement:
SELECT DATE
('20' ||
SUBSTR(ODCDAT, 5, 2) || '-' ||
SUBSTR(ODCDAT, 1, 2) || '-' ||
SUBSTR(ODCDAT, 3, 2)
) AS CREATE_DATE FROM MYFILE
I will leave you as an exercise the use of CASE with ODCEN for using the
correct century...
HTH,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: SQL list *OUTFILE of DSPOBJD by date, (continued)
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.