Add timestampPrecisionReporting option to resultset.getDBTimestamp and resultset.getTimestamp to get trailing 6 number places after the decimal as has been done with resultset.getString

In IDz DB2 for z/OS Connections, we return the result of 3 methods to show the timestamp in our tables.
Two of the three entries lack the last zero.
With the timestamp type data in the presentation of the result of the execution of a db2 query if a record contains 0 at the end it is eliminated and the complete data is not presented. 
The customer reports, "It is necessary that the data be presented as is without being cut."

The DB2 team said in an investigation of this problem in a skills case:

The property timestampPrecisionReporting specifies what kind of precision Jcc uses for ResultSet.getString for TimeStamp column. 
When the property value is set to 2, it indicates that trailing zeros are kept up to the defined precision of the column. 

From the details provided and the JDBC trace logs, I see that the resultset.getDBTimestamp(3) is called. 
[jcc][Time:2024-08-10-22:59:31.339][Thread:ForkJoinPool.commonPool-worker-15][ResultSet@5b8d2b2c]getDBTimestamp (3) called.
[jcc][Time:2024-08-10-22:59:31.339][Thread:ForkJoinPool.commonPool-worker-15][ResultSet@5b8d2b2c]getDBTimestamp () returned 2018-06-19 15:10:20.02 

As per the timestampPrecisionReporting property, it applies only to the resultset.getString for the timestamp column and not to getDBTimestamp. 

Sample:
rs.getTimestamp : 2018-04-09 16:06:38.75813
rs.getString : 2018-04-09 16:06:38.758130 
rs.getDBTimeStamp : 2018-04-09 16:06:38.75813 

Hence, you do not see the zero padded at the end when rs.getDBTimeStamp is called.
Please use rs.getString along with setting property timestampPrecisionReporting =2 for getting the timestamp with trailing 0 padding.

We request that you add the timestamp option to the other two methods rs.getDBTimeStamp and rs.getTimeStamp to get the end decimal.