Fixes are available
APAR status
Closed as program error.
Error description
DB Common Connector: If the update batch has errors( e.g incorrect string rep for date, null value for not nullable column ) as well as warnings ( no row found for update), then the logic processes the diag messages incorrectly and loses the first row in the batch.
Local fix
Use an array size of 1
Problem summary
IF THE UPDATE BATCH HAS ERRORS AS WELL AS WARNINGS, THEN THE DB2 CONNECTOR LOGIC PROCESSES THE DIAG MESSAGES INCORRECTLY AND LOSES THE FIRST ROW
Problem conclusion
In the Update then Insert mode DB2 Connector processes batch status incorrectly and loses the first record in the batch. This is because if the update batch has errors as well warnings, then DB2 CLI does not return the diag messages sorted on row number. Modified DB2 Connector code for Update then Insert mode, to get all diag messages for the update batch before processing records for insert.This patch also contains the fix for APAR JR40919 -THE DB2 CC STAGE DOES NOT REJECT ROWS WITH AN INVALID DATE. INSTEAD, THE ROW IS INSERTED WITH THE DETAILS FROM THE PREVIOUS ROW.
Temporary fix
Comments
APAR Information
APAR number
JR41273
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-21
Closed date
2011-12-06
Last modified date
2012-03-23
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
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.5","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021