IBM Support

IT14426: MODULE AND SCHEMA LEVEL REFERENCE VARIABLES NOT BEING RESET AFTER PROPAGATE WITH DELETE IN COMPUTE NODE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a user has a REFERENCE variable declared at the module or
    schema level which points at either OutputRoot,
    OutputLocalEnvironment or OutputExceptionList and performs a
    PROPAGATE without specifying DELETE NONE in a compute node, then
    it is not defined what the REFERENCE variable will be left
    pointing at. After the PROPAGATE the Output trees are deleted
    and the REFERENCE variables should be reset to point at the root
    of the newly created trees. The module and schema level
    reference variables are not being reset and are thus left to
    point at the original syntax element which they were pointing at
    which will now have been reset leading to unexpected results.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V8.0, IBM Integration Bus
    V9.0 and IBM Integration Bus V10.0 performing a PROPAGATE
    without specifying DELETE NONE in a compute node.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a user has a REFERENCE variable declared at the module or
    schema level which points at either OutputRoot,
    OutputLocalEnvironment or OutputExceptionList and performs a
    PROPAGATE without specifying DELETE NONE in a compute node, then
    it is not defined what the REFERENCE variable will be left
    pointing at. After the PROPAGATE the Output trees are deleted
    and the REFERENCE variables should be reset to point at the root
    of the newly created trees. The module and schema level
    reference variables are not being reset and are thus left to
    point at the original syntax element which they were pointing at
    which will now have been reset leading to unexpected results.
    
    
    <i>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</i>
    

Problem conclusion

  • REFERENCE variables are now correctly reset after a PROPAGATE
    with the DELETE DEFAULT option or no delete keyword.
    
    ---------------------------------------------------------------
    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.5
    
    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

    IT14426

  • Reported component name

    WEB MESSAGE BRO

  • Reported component ID

    5724J0520

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-23

  • Closed date

    2016-04-07

  • Last modified date

    2016-04-07

  • 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 MESSAGE BRO

  • Fixed component ID

    5724J0520

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
07 April 2016