A fix is available
APAR status
Closed as program error.
Error description
Job continues running after ODBC fatal error, even with JR29782 installed (fix was working until recently). . The error is intermittent. Consecutive job runs with ODBC error show one job terminating with status of FAILED after fatal error while another job completes with status OK. Problem observed in parallel job with 2-node configuration. . It appears that APT_MSG(Fatal,..... ) may not abort the operator under some scenarios.
Local fix
This fix is included in 8.0.1 fix pack 3 This APAR is superceded by JR39543
Problem summary
ODBC Operator conitnues to run even after logging a FATAL error message.
Problem conclusion
ODBC Operator job continues to execute even after logging a FATAL error.
Temporary fix
Comments
APAR Information
APAR number
JR33966
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-11
Closed date
2011-09-13
Last modified date
2011-09-13
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
R753 PSY
UP
R800 PSY
UP
R801 PSY
UP
R802 PSY
UP
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.0.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021