A fix is available
APAR status
Closed as program error.
Error description
Db2 connector job using Write mode as "User defined SQL" aborts when a DB2 warning is encountered with property of "Fail on Error" is set to 'YES'.
Local fix
Work around is to set the DB2 Connector property "Fail on error = NO" in the Before/After SQL.
Problem summary
Problem Summary: DB2 Connector job using Write mode as "User defined SQL" aborting when a DB2 Warning is encountered. Problem Description: DB2 connector job using Write mode as "User defined SQL" aborts when a DB2 warning is encountered and Fail on Error = YES.Setting Fail on Error = NO, is not a viable solution as it may ignore valid errors also.
Problem conclusion
The Fail on Error property now has the following values: - 'Yes' is now called 'Fail on errors and warnings' - 'No' is now called 'Ignore errors and warnings' - The new value is 'Fail on errors only, ignore warnings' To ignore warnings but not errors: Set the Fail on Error property to 'Fail on errors only, ignore warnings'
Temporary fix
Comments
APAR Information
APAR number
JR38582
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-01-04
Closed date
2011-03-22
Last modified date
2011-11-22
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