JR39089: Teradata API Stage throws "Transaction ABORTed due to deadlock" as Info type and as a result,the DataStage job does not abort

IBM InfoSphere Information Server, Version 8.5 Fix Pack 2

APAR status

• Closed as new function.

Error description

• "Error : 2631: Transaction ABORTed due to deadlock" should be
  treated as "FATAL" and the Job should abort accordingly.
  

Local fix

Problem summary

• TD API stage throws
  "Transaction ABORTed due to deadlock" as Info type and resulting
  datastage job does not abort.
  When deadlock abend occurs in Teradata transaction, which is
  executed by Teradata API stage, this abend is not propagated
  back into DataStage and DataStage job keeps running. This is
  causing process problems.
  Providing a Patch for "Error : 2631: Transaction ABORTed due to
  deadlock" should be treated as "FATAL", so that TD-API will
  treat it as FATAL instead of Info/Warning.
  

Problem conclusion

• TD API stage throws "Transaction ABORTed due
  to deadlock" as Info type and resulting datastage job does not
  abort.
  When deadlock abend occurs in Teradata transaction, which is
  executed by Teradata API stage, this abend is not propagated
  back into DataStage and DataStage job keeps running. This is
  causing process problems.
  Providing a Patch for "Error : 2631: Transaction ABORTed due to
  deadlock" should be treated as "FATAL", so that TD-API will
  treat it as FATAL instead of Info/Warning.
  

Temporary fix

Comments

APAR Information

• 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

• R752 PSY

     UP