JR40538: Change in nullability behavior of output columns in DB2 Connector introduced with the APAR JR37511

IBM InfoSphere Information Server, Version 8.7 Fix Pack 1
IBM InfoSphere Information Server, Version 8.5 Fix Pack 3

APAR status

• Closed as program error.

Error description

• Fatal error in sparse lookup stage after installation of FP2 on
  8.1
  
  Error:
  Message: Lku,1: Null in field "DATA2 "; the result is
  non-nullable and there is no handle_null to specify a default
  value.
  
  The job ran without any problem in IS8.1 FP1 environment but it
  has error in IS8.1 FP2 environment.
  On Lookup stage (sparse), if reference link's non-key item
  (CHAR) is nullable and if it is set as not-nullable when it is
  passed to output link,
  
  In FP1 env: even if actually it is NULL, padding character space
  (0x20) is added implicitly.
  In FP2 env: error happens.
  

Local fix

Problem summary

• Nullability handling of DB2Connector read/lookup jobs changed
  after applying IS 8.1 Fix Pack 2.
  

Problem conclusion

• Code has been corrected to properly set the nullability. The
  environment variable CC_USE_EXTERNAL_SCHEMA_ON_MISMATCH can eb
  used to get the old behaviour.
  

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

• R810 PSY

     UP

• R850 PSY

     UP