IBM Support

PI41552: TIMEOUTNOTIFICATION NODE DEPLOYED WITH BLANK UNIQUEIDENTIFIER CAN PROCESS REQUESTS FROM OTHER TIMEOUTNOTIFICATION NODES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a TimeoutNotification Node is deployed with a blank
    uniqueIdentifier then it can process timeout requests from other
    TimeoutNotification nodes.
    
    The toolkit will stop flows from being deployed that have an
    empty uniqueIdentifier set but you can still override the
    property via overrides (e.g mqsiapplybaroverride).
    
    This APAR will change the runtime to throw an error if a the
    TimeoutNotification node has an empty uniqueIdentifier.
    

Local fix

  • Do not override the TimeoutNotification Node
    with an empty uniqueIdentifier.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker version 8 and IBM
    Integration Bus version 9 and 10 using the TimeoutNotification
    node.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The TimeoutNotification node must have a unique identifier. If a
    a TimeoutNotification node is deployed with a blank unique
    identifier then it can process timeouts from other timeout
    nodes.
    
    The toolkit will stop flows from being deployed that have an
    empty uniqueIdentifier set but you can still override the
    property via overrides (e.g mqsiapplybaroverride).
    
    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

  • The product now throws an exception if a TimeoutNotification
    Node is deployed with a
    blank unique identifier.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.7
    v9.0       9.0.0.6
    v10.0      10.0.0.2
    
    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

    PI41552

  • Reported component name

    WEB MB Z/OS

  • Reported component ID

    5697P4400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-21

  • Closed date

    2015-09-13

  • Last modified date

    2016-03-16

  • 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

    WEB MB Z/OS

  • Fixed component ID

    5697P4400

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 March 2016