Fixes are available
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 number
JR40538
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-01
Closed date
2011-09-13
Last modified date
2012-03-27
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
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021