IBM Support

IC84063: WEBSPHERE MQ FTE V7 CAN NOT HANDLE MORE THEN 16 CHARACTERS IN THE ENCODING NAMES. BFGDB0003E SQL -302

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If for example, the name of the encoding used for the
    destination file or the name of source encoding is longer than
    16 characters, this will causes a SQL -302 error seen in the
    BFGDB0003 message output below:
    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.64.82]
    
    In addition to the BFGDB0003 message output to the log there
    will also be a message present on the reject queue for the
    logger and the WMQFTE_ReasonForRejection custom property will
    be set to the same error message.
    

Local fix

  • None <br/>
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere MQ File Transfer Edition Version 7.0.4
    using a custom encoding
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    If an encoding with a name longer than 16 character was being
    used, the database logger would fail to process audit messages
    which contained information on the encoding used with error
    BFGDB0003E. The audit message would be placed to the database
    logger reject queue.
    
    The reason for the failure is that the column used for the
    encoding name within the database has a size limit of 16
    characters. Attempting to insert a record with an encoding
    name of more than 16 characters would subsequently fail.
    

Problem conclusion

  • The database logger code has been altered to truncate any
    encoding name longer than 16 characters, to 16 characters in
    length. This ensures that the data can be inserted into the
    TRANSFER_ITEM database table and the message will no longer be
    sent to the reject queue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Platform           v7.0
    --------           --------------------
    Multiplatforms     7.0.4.3
    
    Platform           v7.5
    --------           --------------------
    Multiplatforms     7.5.0.1
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC84063

  • 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-06-11

  • Closed date

    2012-08-14

  • Last modified date

    2012-08-14

  • 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:
14 August 2012