IBM Support

IT34275: ATTACHMENTS PROPAGATED OUT OF EMAILINPUT NODE MAY GET CORRUPTED.

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 you directly propagate an email with an attachment, received
    by the EmailInput node, to an EmailOutput node, the attachment
    is seen corrupted at the receiving end.
    

Local fix

  • Using the following ESQL to explicitly set the attachment
    through the LocalEnvironment override makes it work.
    
    
    
    
    
    declare bl blob InputRoot.MIME.Parts.Part[2].Data.BLOB.BLOB;
    
    
    
     declare ctype Character
    InputRoot.MIME.Parts.Part[2].\"Content-Type\";
    
    
     set
    OutputLocalEnvironment.Destination.Email.Attachment.Content=
    bl;
    
    
     set
    OutputLocalEnvironment.Destination.Email.Attachment.ContentType=
    ctype;
    
    
     set OutputLocalEnvironment.Destination.Destination.Em
    ail.Attachment.ContentEncoding='Base64';
    
    
     -- Email Text
    
    
    
    Set OutputRoot.XMLNSC.MSG = 'Test Msg';
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All Users of IBM App Connect Enterprise 11.0 and IBM Integration
    Bus 10.0 using EmailInput node.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">If an email
    with an attachment is directly propagate as received by the
    EmailInput node, to an EmailOutput node, then the attachment
    gets</span><span style="background-color:rgb(255, 255, 255)">
    corrupted at the receiving end.
    
    This issue occurs because EmailInput node does not retain base64
    form of attachments, for example, PDF documents..</span>
    

Problem conclusion

  • The product has been modified to propagate the email binary
    attachments  in base64 form to the message tree to avoid
    corruption of its contents while sending them out.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.24
    v11.0      11.0.0.12
    
    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

    IT34275

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-18

  • Closed date

    2021-03-25

  • Last modified date

    2021-03-25

  • 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

    5724J0540

Applicable component levels

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

Document Information

Modified date:
26 March 2021