IBM Support

JR57836: Teradata Connector continues to execute "AfterSQL" even after job failureabort.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Teradata Connector to stop executing "AfterSQL" in job failure
    and on enabling CC_TDCC_SKIP_AFTERSQL_ON_FAILURE.
    

Local fix

Problem summary

  • After SQL was getting executed even when the job has aborted.
    

Problem conclusion

  • A New environment variable"CC_TDCC_SKIP_AFTERSQL_ON_FAILURE" is
    added. On setting it to true(Case Insensitive) AfterSQL
    statement will not get executed when job fails.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR57836

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    B31

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-27

  • Closed date

    2017-09-27

  • Last modified date

    2017-09-27

  • 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

  • RB30 PSY

       UP

  • RB31 PSY

       UP

  • RB50 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.3","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 September 2017