IBM Support

JR34669: NOT VALID FOR OPERATION ERROR INSERTING DATA INTO DB2 ON ISERIES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error message:
    
    LdBDetailTableTESTTEST..Xfm.DataToInsert: DSD.BCIPut call to
    SQLExecute failed.
    SQL statement:INSERT INTO J73DISDTA.F554211B(SZEDUS) VALUES (?)
    SQLSTATE=S1000, DBMS.CODE=-7008
    [DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol
    driver][UDB DB2 for iSeries and AS/400]F554211B   in J73DISDTA
    not valid for operation.  3
    
    SZEDUS = "EXPL_DIS  "
    
    When trying to insert data in DB2 database on iSeries.
    
    DS 7.5.2 on Solaris
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Server jobs with ODBC stages to DB2 on iSeries or AS/400 can
    fail on all platforms.
    ****************************************************************
    PROBLEM DESCRIPTION:
    This is for the ecase 122504 fix.  Server jobs with ODBC stage
    to DB2 on iSeries or AS/400 can fail during insert of data.
    Errors similar to the following will be found in job logs.
    
    LdBDetailTableTESTTEST..Xfm.DataToInsert: DSD.BCIPut call to
    SQLExecute failed.
    SQL statement:INSERT INTO J73DISDTA.F554211B(SZEDUS) VALUES (?)
    SQLSTATE=S1000, DBMS.CODE=-7008
    [DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire
    Protocoldriver][UDB DB2 for iSeries and AS/400]
    F554211B in J73DISDTA not valid for operation.
    ****************************************************************
    RECOMMENDATION:
    Apply a patch. Available as part of the release in 8.0.1.2 and
    8.1.
    ****************************************************************
    

Problem conclusion

  • The DataStage server engine sets an initial isolation level of
    SQL_TXN_READ_COMMITTED.  The fix is to apply this patch and
    bypass the SQLSetConnectOption call by setting the environment
    variable DSE_ODBC_ISOLEVEL_NONE to 1.  DSE_ODBC_ISOLEVEL_NONE
    can be set for all of DataStage by adding it to $DSHOME/dsenv,
    on a project basis through the Administrator, or just for a
    particular job with the addition of a Before-job subroutine
    using ExecTCL to run ENV SET DSE_ODBC_ISOLEVEL_NONE=1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR34669

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    752

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-10-26

  • Closed date

    2009-11-03

  • Last modified date

    2009-11-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • SERVER
    

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R752 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":"7.5.2","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 November 2009