A fix is available
Closed as program error.
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.
This fix is included in 8.0.1 fix pack 3 This APAR is superceded by JR39543
ODBC Operator conitnues to run even after logging a FATAL error message.
ODBC Operator job continues to execute even after logging a FATAL error.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
12 October 2021