JR51005: Connectors on a server canvas are not honoring the scale part of a timestamp field in a target context

APAR status

• Closed as program error.

Error description

• Problem:
  Connectors on  a server canvas are not honoring the scale part
  of a timestamp field in a target context.
  
  Details:
  Here in Server connector framework, Microseconds resolution is
  hardcoded. So we are always seeing 6 fraction digits
  irrespective of scale and other properties.
  
  Resolution:
  To handle microseconds correctly, we have an environment
  variable CC_SE_TIMESTAMP_FF which does:
  
  1. When the environment variable is not added, the jobs would
  behave the same way as they are behaving today.
     This is to ensure that any of the customers who are using the
  Connectors on Server canvas and are comfortable with the
     hard coded microseconds that is coming in their data.
  2. When the environment variable is added and its value is set
  to MICROSECONDS, it would be same behavior as (1).
  3. When the environment variable is added with a value of SCALE,
  then it is expected that the scale is mentioned in the
     timestamp fields in the schema and whatever scale is
  mentioned the microsecond resolution would be set to that.
  4. When the environment variable is added and its value is set
  to NONE, then the behavior would be same as DS_NO_FF (
     or SCALE with the scale in the timestamp fields being set to
  0)
  

Local fix

• Change the table DDL for date to use timestamp(0) instead. For
  example,
  
  CREATE TABLE TEST.DATE_INSERT_TEST(c1 timestamp(0));
  

Problem summary

• Connectors on  a server canvas are not honoring the scale part
  of a timestamp field in a target context. In Server connector
  framework, Microseconds resolution is hardcoded. So we are
  always seeing 6 fraction digits irrespective of scale and other
  properties.
  

Problem conclusion

• To handle microseconds correctly, we have an environment
  variable CC_SE_TIMESTAMP_FF which does:
  
  1. When the environment variable is not added, the jobs would
  behave the same way as they are behaving today. This is to
  ensure that any of the customers who are using the Connectors on
  Server canvas and are comfortable with the hard coded
  microseconds that is coming in their data.
  2. When the environment variable is added and its value is set
  to MICROSECONDS, it would be same behavior as (1).
  3. When the environment variable is added with a value of SCALE,
  then it is expected that the scale is mentioned in the timestamp
  fields in the schema and whatever scale is mentioned the
  microsecond resolution would be set to that.
  4. When the environment variable is added and its value is set
  to NONE, then the behavior would be same as DS_NO_FF (or SCALE
  with the scale in the timestamp fields being set to 0)
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R910 PSY

     UP

• R912 PSY

     UP