Re: To Date or Not to Date... that is the question

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