IBM Support

IT30930: SUPPORT FOR IBM MANUFACTURING PACK NODES ON IBM APP CONNECT ENTERPRISE 11.0.0.6

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

  • This APAR fixes the following issues.
    - A manufacturing pack input node fails to receive any messages
    following a restart of the message flow.
    - Messages received by the manufacturing input node contain an
    incorrectly initialised properties folder.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of the IBM Manufacturing Pack on ACE v11
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    This APAR contains fixes for 2 distinct problems
    1) If a message flow containing a manufacturing input node was
    stopped (mqsistopmsgflow) and then restarted (mqsistartmsgflow),
    the message flow was not restarted correctly and would not
    processes any input messages. The application needed to be
    redeployed or the integration server restarted in order for the
    message flow to resume processing messages.
    2) The 'Properties' folder of an input message received by
    manufacturing input node was not populated with the correct
    defaults for the Encoding and CodedCharSetId properties. These
    properties should be populated with defaults from the
    Integration Server.
    

Problem conclusion

  • 1) When the Manufacturing Input Node was running and then
    stopped, it failed to update it's internal state to stopped. A
    subsequent start request then took no action as it believed the
    Input Node was already running running when in-fact it was not.
    The solution was to correctly change the internal state to
    stopped when the message flow is stopped.
    2) The node framework, upon which the manufacturing pack nodes
    are built, was incorrectly initializing the Properties folder
    for each message received. This logic was changed to extract the
    correct defaults from the Integration Server when building the
    Properties folder.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.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

    IT30930

  • 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

    2019-11-13

  • Closed date

    2020-01-21

  • Last modified date

    2020-01-21

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 January 2020