IBM Support

PH40934: PH40934:PROVIDE OPTION FOR AEM DEPLOY TO NOT START ANOTHER SERVER IF ONLY 1 IS RUNNING

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

  • PH40934:PROVIDE OPTION FOR AEM DEPLOY TO NOT START ANOTHER
    SERVER IF ONLY 1 IS RUNNING
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WAS ND edition- Virtual              *
    *                  Enterprise/IM Component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: PROVIDE OPTION FOR AEM DEPLOY TO NOT    *
    *                      START ANOTHER SERVER IF ONLY 1 IS       *
    *                      RUNNING                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When rolling out a new edition of an application, if only one
    server instance is running, Application Edition Manager will
    start another instance thereby ensuring that application upgrade
    is interrup-free. However, in some instances, user may prefer
    not to start another instance; to support that we added a system
    property 'appedition.rollout.maintainRunState' which can be set
    to 'false' thus disabling the start of another server. We also
    provided a Admin task rollout command property 'maintainRunState
    false' in case the user does not want to set the global system
    property.
    

Problem conclusion

  • Code changes were made to add a system property
    'appedition.rollout.maintainRunState' which can be set to
    'false; thus disabling the start of another server. If the user
    doea not want to set a global property, they can alternatively
    set Admin task rollout command property 'maintainRunState false'
    to prevent starting a new server for the specific rollout.
    
    The fix for this APAR is currently targeted for inclusion in fix
    packs 9.0.5.10 and 8.5.5.21.  Please refer to the Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH40934

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-28

  • Closed date

    2021-11-16

  • Last modified date

    2021-11-16

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900"}]

Document Information

Modified date:
17 November 2021