IBM Support

IT16718: MQSIMIGRATECOMPONENTS CAN LOSE FLOW LEVEL ATTRIBUTES IF A MESSAGE FLOW USES DEPLOYABLE SUBFLOWS

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

  • The mqsimigratecomponents command can lose message flow level
    attributes, such as additional instances, deploy information,
    monitoring settings etc, if a message flow uses deployable
    subflows.
    

Local fix

  • There is no workaround to this problem. The APAR fix will need
    to be applied and the same broker be back migrated to the
    previous release and then forward migrated to V10.0 again.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10.0 using the
    mqsimigratecomponents command to migrate previous product
    version message flows that contain references to deployable
    subflows.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The mqsimigratecomponents command is used to migrate previous
    versions of the product to v10.0. As part of this processing,
    message flows are migrated from the internal configuration
    tables to the file system. If a message flow references
    deployable subflows (.subflow files) then there will be two
    representations of the message flow:
    1) The original (parent) message flow that still contains the
    subflow nodes.
    2) An inlined message flow where all of the subflow nodes have
    been resolved.
    In IBM Integration Bus v10.0 option 2 is no longer needed.  As
    such the mqsimigratecomponents command will merge the flow level
    attributes.
    
    A defect exists such that this process ends too early resulting
    in flow level attributes such as additional instances, deploy
    information, monitoring settings etc being lost.  Which settings
    are lost is dependent on what order they were serialised in the
    flow XML.
    
    This could be visible to the user when they try to view the flow
    level attributes using mqsilist, mqsireportproperties or through
    the webui.
    

Problem conclusion

  • The product has been corrected to copy all flow level attributes
    when merging a parent flow and an inlined message flow on
    migration.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.7
    
    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

    IT16718

  • 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

    2016-08-23

  • Closed date

    2016-11-23

  • Last modified date

    2016-11-23

  • 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

  • RA00 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":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020