PJ39741: FILE IMPORT WITH LOAD IS MARKED AS SUCCESSFUL EVEN IF THE FILE TO BE LOADED IS MISSING

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

  • When running a File Import operator with 'LOAD' option in a
    control flow, the execution status of the flow shows success
    even if the file to be loaded does not exist.
    
    The log file may also show the following message:
    
    Call ADMIN_CMD: SQL2036N: The path for the file or device
    "xxxxxx" is not valid.
    
    Subsequently, no data will be loaded to DB2.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * SQW users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When a FileImport operator with 'LOAD' option runs in a      *
    * control                                                      *
    * flow, if the file to loaded does not exist, the execution of *
    * this operator will still mark the execution status as        *
    * success.                                                     *
    *                                                              *
    * In the log file, it has the message like this:               *
    *                                                              *
    * Call ADMIN_CMD: SQL2036N: The path for the file or device    *
    * "xxxxxx" is not valid.                                       *
    *                                                              *
    * Subsequently, no data is loaded to DB2.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * The interim fix was delivered through SQW interim fix        *
    * package 'SQW-9.7.3.v20111212'.                               *
    *                                                              *
    * Please upgrade to ISW 9.7.7 to pickup the full fixes of this *
    * problem as well as other fixes.                              *
    ****************************************************************
    

Problem conclusion

  • The logic for checking the error code from DB2 LOAD utility
    needs to be improved.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ39741

  • Reported component name

    DWE SQL WHSE TO

  • Reported component ID

    5724DWESQ

  • Reported release

    973

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-08

  • Closed date

    2012-10-23

  • Last modified date

    2012-10-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

    DWE SQL WHSE TO

  • Fixed component ID

    5724DWESQ

Applicable component levels

  • R973 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Warehouse
DWE - SQL Warehousing Tool

Software version:

973

Reference #:

PJ39741

Modified date:

2012-10-23

Translate my page

Machine Translation

Content navigation