IBM Support

IC81973: MQ FTE: BFGDB0003E EXCEPTION OCCURS WHEN RUNNING WMQ FTE 7.0.4.1 DATABASE LOGGER AGAINST DB2 ON Z/OS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are running the WebSphere MQ File Transfer Edition 7.0.4.1
    database logger against DB2 in z/OS. When using DB2 Connect you
    see the following error:
    .
    MQDataSource  I   BFGDB9999E:
    The database logger has placed a message on the reject queue:
    SYSTEM.FTE.DATABASELOGGER.REJECT, on queue manager: x.
    Check the queue for more information.
    .
    DatabaseLogge W   BFGDB0003E: A problem occurred with
    the database. The database driver reported the
    following details: SQL State ■26501, Error Code ■-514,
    Message ■DB2 SQL Error: SQLCODE=-514, SQLSTATE=26501,
    SQLERRMC=SQL_CURLH200C1, DRIVER=3.63.75
    .
    The 514 errors continue until the Database Logger is stopped.
    .
    A check of the Reject Queue shows:
    WMQFTE_ReasonForRejection BFGDB0003E: A problem occurred with
    the database. The database driver reported the following
    details: SQL State ■22001, Error Code ■-302,
    Message ■DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001,
    SQLERRMC=null, DRIVER=3.63.75
    

Local fix

Problem summary

  • In some conditions the database logger would attempt to INSERT a
    record into a DB2 database running on z/OS, and would fail with
    SQLCODE -302.  This occurred because IBM WebSphere MQ File
    Transfer Edition would only specify the database schema to use
    on the first transaction.  DB2 for z/OS requires the schema to
    be specified on every transaction, and will not assume the
    previous used schema should be used again.
    
    USERS AFFECTED:
    All users of the database logger using a DB2 database on z/OS
    
    PLATFORMS AFFECTED:
    All
    

Problem conclusion

  • The code has been altered to ensure that the database logger
    will specify the database schema to be used for every
    transaction for a DB2 on z/OS database.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 7.0.4.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC81973

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-12

  • Closed date

    2012-04-10

  • Last modified date

    2012-07-20

  • 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

    WMQ FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R704 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
20 July 2012