Automatic data validation by using asnclp create qsub with different data type column mapping

Related to the case TS020335936

Scenario:

Consider the following qsub creation: mapping VARCHAR(26) to TIMESTAMP(6)

TRGCOLS EXCLUDE (RECORD_TIME, MES_RECORD_TIME, SITE_CD, D_KEY, CHANGE_TYPE, CHANGE_TIME)
EXPRESSION (
"'MES2'" TARGET SITE_CD,
"current_timestamp" TARGET MES_RECORD_TIME,
"CASE WHEN :D_KEY is NULL THEN ' ' ELSE :D_KEY END" TARGET D_KEY,
"CASE WHEN :CHANGE_TYPE is NULL THEN ' ' ELSE :CHANGE_TYPE END" TARGET CHANGE_TYPE,
"TO_TIMESTAMP(:CHANGE_TIME, 'YYYY-MM-DD-HH24.MI.SS.FF6')" TARGET CHANGE_TIME)

It can be worked with add "VALIDATE NO" on asnclp command.

Customer think, if this can be worked(by adding VALIDATE NO parameter), why it caused the following error?

ASN0999E "The source expression to_timestamp(:CHANGE_TIME,'YYYY-MM-DD-HH24:MI:SS.FF') could not be evaluated because of a DB2 error. Check the correctness of the expression. The Apply program will fail if the source data cannot be transformed correctly or if the transformed data is not compatible with the target column CHANGE_TIME. If the expression is correct for the actual source data, create the target table and rerun the action. Otherwise, correct the expression. Original error message : ASN2022E The action ended in error. An SQL error was encountered. SQL message is “ORA-01840: input value not long enough for date format"." : "" : Error condition "", error code(s): "", "", "".
 

It should be automatic VALIDATED and can be created by using asnclp directly. They requested the new enhancement.