IBM Support

PH20251: INSTALL MULTIPLE COMPONENTS STEP DOES NOT RESPECT MAXIMUM NUMBEROF CONCURRENT COMPONENTS OR PROCESSES SETTINGS

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

  • When using the "Install Multiple Components" step in an
    application process, the application process ignores the maximum
    number of concurrent components as well as the maximum number of
    concurrent processes settings.
    
    Reproduction Steps:
    1. Create 2 identical components with a tag "tag" and a
    component process "comp process":
    Start > Wait 5 seconds > Set Status: Failure > Finish
    2. Create an application "app" with an app process: "app
    process":
    Start > Install Multiple Components > Finish
    set the configuration of install multiple components to use the
    tag "tag" and have 1 concurrent component and 1 concurrent
    process allowed, check the "Fail Fast" setting
    3. Run the application process
    Both components start at the same time and run concurrently. In
    a working case, the "Fail Fast" checkbox would cause the second
    component not to start.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When using the "Install Multiple Components" step in an      *
    * application process, the application process ignores the     *
    * maximum                                                      *
    * number of concurrent components as well as the maximum       *
    * number of                                                    *
    * concurrent processes settings.                               *
    *                                                              *
    * Reproduction Steps:                                          *
    * 1. Create 2 identical components with a tag "tag" and a      *
    * component process "comp process":                            *
    * Start > Wait 5 seconds > Set Status: Failure > Finish        *
    * 2. Create an application "app" with an app process: "app     *
    * process":                                                    *
    * Start > Install Multiple Components > Finish                 *
    * set the configuration of install multiple components to use  *
    * the                                                          *
    * tag "tag" and have 1 concurrent component and 1 concurrent   *
    * process allowed, check the "Fail Fast" setting               *
    * 3. Run the application process                               *
    * Both components start at the same time and run concurrently. *
    * In                                                           *
    * a working case, the "Fail Fast" checkbox would cause the     *
    * second                                                       *
    * component not to start.                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fixed in version 7.1.0.1                                     *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 7.1.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH20251

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    703

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-12-12

  • Closed date

    2020-07-23

  • Last modified date

    2020-07-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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 July 2020