DSPFFD does indeed effectively lie for the length of data types Date, Time, and TimeStamp. The /buffer length/ is accurate for the specific [human-readable] formatting for presentation, not the length for the internal storage for the data type; as seen for Packed and Integer for example.

The respective lengths for Date, Time, and Timestamp data types, are shown with the following SQL SELECT and the resulting report:

select int( length(hex(current date) )/2) as date_len
, int( length(hex(current time) )/2) as time_len
, int( length(hex(current timestamp))/2) as tmsp_len
from qsys2.qsqptabl

....+....1....+....2....+....3....+....4....+.
DATE_LEN TIME_LEN TMSP_LEN
4 3 10
******** End of data ********

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.