IBM Support

PH31840: MOVEABLE DMGR FAILS TO CREATE VIPARANGE DVIPA ON 2ND LPAR

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 a DVIPA defined by a VIPARANGE for the moveable DMGR
    (instead of a sysplex distributed DVIPA), the DMGR needs to
    bind to the DVIPA to create the DVIPA.  Setting the end points,
    com.ibm.CORBA.LocalHost, and com.ibm.CORBA.BootstrapHost to the
    DVIPA hostname and setting
    com.ibm.websphere.network.useMultiHome to false allows the DMGR
    to create the DVIPA on the system configured on
    (server_configured_system_name), but not on the other LPAR.
    
    On the failing LPAR, the DMGR CR fails to start with:
    BBOO0220E: DCSV9403E: Received an illegal configuration
    argument. Parameter MulticastInterface, value: <dvip_address>.
    Exception is java.lang.Exception: Network Interface
    <dvip_address> was not found in local machine network interface
    list. Make sure that the NetworkInterface property is properly
    configured!
    

Local fix

  • use TCPIP PORT BIND definition to cause DMGR to bind to the
    DVIPA address in the VIPARANGE
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 for z/OS                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      deployment manager fails to create      *
    *                      VIPARANGE DVIPA when started on a       *
    *                      system that it is not configured for.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using a DVIPA defined by a VIPARANGE for the moveable
    deployment manager (instead of a sysplex distributed DVIPA),
    the deployment manager needs to bind to the DVIPA to create
    the DVIPA.  Setting the end points, com.ibm.CORBA.LocalHost,
    and com.ibm.CORBA.BootstrapHost to the DVIPA hostname and
    setting com.ibm.websphere.network.useMultiHome to false allows
    the deployment manager to create the DVIPA on the system
    configured on (server_configured_system_name), but not on
    another LPAR.
    On the failing LPAR, the deployment manager controller region
    fails to start with:
    BBOO0220E: DCSV9403E: Received an illegal configuration
    argument. Parameter MulticastInterface, value: <dvip_address>.
    Exception is java.lang.Exception: Network Interface
    <dvip_address> was not found in local machine network interface
    list. Make sure that the NetworkInterface property is properly
    configured!
    

Problem conclusion

  • When the WebSphere variable
    private_deployment_manager_always_on_configured_system is
    set to 1 in a deployment manager, the code will act as if the
    deployment manager is running on the configured system even
    if it is not running on the configured system.
    The default for
    private_deployment_manager_always_on_configured_system is 0.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.20 and 9.0.5.8. For more information, see 'Recommended
    Updates for
    WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH31840

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-11-18

  • Closed date

    2021-01-30

  • Last modified date

    2021-01-30

  • 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":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
31 January 2021