IBM Support

IT15736: HL7 TRAILING DELIMITERS NOT SUPPRESSED WHEN EXPECTED

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 serializing HL7 messages using DFDL, any separators for
    'potentially trailing' (see spec) elements should be suppressed
    and should not appear in the output. However such separators
    are not being suppressed if a 'potentially trailing' simple
    element is missing from the infoset but is followed by another
    'potentially trailing' element which is in the infoset but is
    empty.
    
    In the example below, all elements after TXA.19 are
    'potentially trailing'. TXA.20 is simple and missing. TXA.24 is
    empty.
    
    <TXA.19.DocumentAvailabilityStatus>AV</TXA.19.DocumentAvailabili
    tyStatus>
    <TXA.24.FolderAssignment>
      <CWE.1></CWE.1>
    </TXA.24.FolderAssignment>
    
    This causes ',,,|AV||' to be output instead of the expected
    '...|AV'.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of IBM Integration Bus v9.0 and v10.0 using DFDL schemas
    for HL7 and setting HL7 fields to empty string.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When serializing HL7 messages using DFDL, any separators for
    'potentially trailing' (see DFDL 1.0 spec) elements should be
    suppressed and should not appear in the output. However such
    separators are not being suppressed if a 'potentially trailing'
    simple element is missing from the infoset but is followed by
    another 'potentially trailing' element which is in the infoset
    but is empty.
    
    This is shown in the example below which uses a TXA segment. All
    the elements after TXA.19 are 'potentially trailing'. TXA.20 is
    simple and missing. TXA.24 is empty.
    
    <TXA.19.DocumentAvailabilityStatus>AV</TXA.19.DocumentAvailabili
    tyStatus>
    <TXA.24.FolderAssignment>
      <CWE.1></CWE.1>
    </TXA.24.FolderAssignment>
    
    This causes '...|AV||' to be output instead of the expected
    '...|AV'.
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT15736

  • 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

    2016-06-15

  • Closed date

    2016-08-18

  • Last modified date

    2016-08-18

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

    IT15725

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

Fix information

  • Fixed component name

    INTEGRATION BUS

  • Fixed component ID

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"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":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020