IBM Support

IT36307: IT IS NOT POSSIBLE TO ARCHIVE FAILED MESSAGES IN THE EMAILINPUT NODE.

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 new function.

Error description

  • If a message fails processing in the Email Input Node, either
    because the Email Input node itself was unable to deserialise
    the message from the email server or because the downstream
    processing of the message has resulted in an exception being
    thrown back to the Email Input Node, then the message is
    deleted from the server.
    
    This means that it is not possible to
    either analyse a failed message to see what caused the problem,
    or to replay a failed message at a later time.
    
    This APAR
    introduces a mechanism to archive failed messages in a BACKUP
    folder on an IMAP server.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of App Connect version 11 or 12 using the EmailInput
    Node
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">If a message
    fails processing in the Email Input Node, either </span><span
    style="background-color:rgb(255, 255, 255)">because the Email
    Input node itself was unable to deserialise </span><span
    style="background-color:rgb(255, 255, 255)">the message from the
    email server or because the downstream     </span><span
    style="background-color:rgb(255, 255, 255)">processing of the
    message has resulted in an exception being </span><span
    style="background-color:rgb(255, 255, 255)">thrown back to the
    Email Input Node, then the message is </span><span
    style="background-color:rgb(255, 255, 255)">deleted from the
    server.                                       </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">This means
    that it is not possible to </span><span
    style="background-color:rgb(255, 255, 255)">either analyse a
    failed message to see what caused the problem, </span><span
    style="background-color:rgb(255, 255, 255)">or to replay a
    failed message at a later time.                 </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">This APAR
    </span><span style="background-color:rgb(255, 255,
    255)">introduces a mechanism to archive failed messages in a
    BACKUP </span><span style="background-color:rgb(255, 255,
    255)">folder on an IMAP server.          </span>
    

Problem conclusion

  • This APAR introduces the environment variable
    MQSI_ARCHIVE_FAILED_EMAILS. When set to any non-null value this
    causes email which can not be processed to be move into a BACKUP
    folder on the IMAP server. If no BACKUP folder exists then an
    attempt will be made to create it if the Integration Server
    userid has sufficient permissions to do so. Note that this
    variable must be set in the Integration Servers profile
    environment prior to starting the Integration Server.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.17
    
    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

    IT36307

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-03-22

  • Closed date

    2022-03-02

  • Last modified date

    2022-03-02

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
03 March 2022