IBM Support

JR39543: ODBC OPERATOR DOES NOT ABORT EVEN AFTER THROWING A FATAL ERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ODBC Operator does not abort when design schema columns does not
    match with target table schema and "Drop Unmatched Fields" is
    not specified.
    
    Note: This APAR supercedes APAR JR33966.
    

Local fix

  • downgrade fatal with message handler
    

Problem summary

  • ODBC Operator does not abort even after logging a fatal error of
    input field not found in the target table and drop option is not
    specified.
    

Problem conclusion

  • Code has been corrected to abort the job when a FATAL error like
    input field does not match in the target table.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR39543

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-09

  • Closed date

    2011-06-29

  • Last modified date

    2011-11-23

  • 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

  • R810 PSY

       UP

  • R850 PSY

       UP

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

Document Information

Modified date:
07 October 2021