IBM Support

IT37675: ATTACHING WLM POLICY ON A STOPPED FLOW PREVENT THE FLOW FROM GETTING STARTED UP AS PART OF APPLICATION STARTUP.

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

  • While the application is in stopped state, if a property change
    is made to the message flow like attaching a wlm policy causes
    the message flow's run state to get updated with a wrong value.
    mqsiattachpolicy <Integration_node> -e <Integration_server> -w
    300 -t WorkloadManagement -k <Application> -m <Messageflow> -l
    <wlmpolicy>
    Then if the application is restarted, then this message flow
    remain in the stopped state.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10.0 using wlm policy.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    While the application is in stopped state, if a property change
    is made to the message flow like attaching a wlm policy causes
    the message flow's run state to get updated with a wrong value.
    For example, if the application is started after running the
    following command then the message flow remain in the stopped
    state.
    mqsiattachpolicy <Integration_node> -e <Integration_server> -w
    300 -t WorkloadManagement -k <Application> -m <Messageflow> -l
    <wlmpolicy>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT37675

  • 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

    2021-07-18

  • Closed date

    2022-04-21

  • Last modified date

    2022-04-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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
22 April 2022