IBM Support

IT40323: MONITORING EVENTS ARE NOT REMOVED FROM NODES IN 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

  • If a monitoring profile is detached from a message flow or
    application using the /detach-monitoring-profile admin REST API
    endpoint, or using the equivalent mqsichangeflowmonitoring
    command, then monitoring events attached to nodes inside
    subflows are not removed.
    
    Similarly if a monitoring profile is attached to a message flow
    or application using the /attach-monitoring-profile admin REST
    API endpoint, or using the equivalent mqsichangeflowmonitoring
    command, then monitoring events attached to nodes inside
    subflows are not removed if they are not present in the new
    monitoring profile. Events that are present in both the old and
    new monitoring profile will, however, be updated to the new
    profile correctly.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of monitoring profiles applied to subflows in IBM App
    Connect Enterprise
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <div><div>If a monitoring profile is detached from a message
    flow or application using the /detach-monitoring-profile admin
    REST API endpoint, or using the equivalent
    mqsichangeflowmonitoring command, then monitoring events
    attached to nodes inside subflows are not removed.</div>
    <div>Similarly if a monitoring profile is attached to a message
    flow or application using the /attach-monitoring-profile admin
    REST API endpoint, or using the equivalent
    mqsichangeflowmonitoring command, then monitoring events
    attached to nodes inside subflows are not removed if they are
    not present in the new monitoring profile. Events that are
    present in both the old and new monitoring profile will,
    however, be updated to the new profile correctly.</div></div>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT40323

  • 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

    2022-03-17

  • Closed date

    2022-10-25

  • Last modified date

    2022-10-25

  • 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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
26 October 2022