DB2 stores date values using an internal representation. Any values whose data type is DATE, TIME or TIMESTAMP will be represented by character strings upon retrieval. The character string representation is normally the default format of date/time values associated with the country code of the database, unless overridden by specification of the DATETIME option when the program is precompiled or bound to the database. The CLP is a DB2 application program. My guess is that your default is ISO and the date/time format was changed for the CLP? Perhaps rebinding it would help.
You can always use the CHAR function to change a DATE value to a string representation in any DB2-supported format you wish (ISO, EUR, JIS, USA or LOC). So, using CHAR(DATE_COL, ISO) in the CLP when retrieving dates would cause your CLP dates to be the same as your dates elsewhere (Command Center, JDBC, etc.)
Dig Deeper on IBM DB2 management
Related Q&A from Craig S. Mullins
Our expert suggests that the best way to pass the SAP BW exam is to have hands-on job experience. But that's not all he has to say about ... Continue Reading
To export data from a DB2 table to a flat file, you need to run an export specifying the proper file format. The export utility exports data from a ... Continue Reading
Craig Mullins recommends two specific resources for learning how to create and support Binary Large Objects (BLOB) in DB2. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.