IBM Support

IT25584: DFDL PIF FILES REQUIRED EVEN WHEN NOT PARSING A DFDL MESSAGE.

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

  • If a message is received by a flow that has an RFH2 header that
    describes the format as 'dfdl' then the flow will fail if it
    cannot find a PIF file to create the parser with even when the
    input message is not parsed by the flow, such as when it is
    immediately converted to a BLOB message.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus version 10 or App Connect
    Enterprise version 11 using BLOB messages.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a ResetContentDescriptor node is used to mark an incoming
    DFDL message as a BLOB message the DFDL parser is invoked even
    though no parsing of the message is required. The DFDL parser
    will fail is no PIF files can be found but as the message is not
    being parsed the DFDL schema is not needed and may not be
    defined.
    

Problem conclusion

  • The code was changed so that the DFDL Parser will not throw an
    exception if PIF files cannot be found and the environment
    variable 'MQSI_DFDL_IGNORE_NO_PIF_FILE_ERROR' is set. This
    allows the broker to carry on in the case described above where
    the message does not need to be parsed.
    In other cases, where the message does need to be parsed, such
    as if it needs to be converted to something other than a BLOB
    message, then the parser will still fail and throw an exception.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.17
    v11.0      11.0.0.6
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25584

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-12

  • Closed date

    2019-09-30

  • Last modified date

    2019-09-30

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0530

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 September 2019