IBM Support

PM26178: WEBSPHERE V7.X Z/OS - UPDATE TO ROUTINGTABLE CODE TO HANDLE MAKING THE DMGR MOBILE ON Z/OS

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A "mobile" Deployment Manager is one that is capable of
    being started on different MVS images in the Sysplex.
    This provides higher availability because it allows you
    to maintain a DMGR instance even when MVS images are taken
    out of service for planned maintenance. It's a relatively
    simple thing to accomplish, and is considered a
    "best practice" when configuring a network deployment
    configuration that spans multiple MVS images in a Sysplex.
    .
    At the heart of this is z/OS Sysplex Distributor.
    That's what allows the DMGR to be started in different
    places and still be located by a TCP request.
    .
    WebSphere z/OS V7 introduced new functionality that
    at the present time modifies slightly the process to make
    the DMGR "mobile".  The  RoutingTable code and IPC Ports
    make the process difficult.  Tech DOC WP101140
    was updated.
    

Local fix

  • .
    See update in Tech Doc WP101140
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 on z/OS                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: For Mobile DeploymentManager on z/OS    *
    *                      as described in Tech DOC WP101140,      *
    *                      after the DeploymentManager             *
    *                      has been moved to the alternate         *
    *                      system, node status may not be          *
    *                      correct.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The code does not take into account that the DeploymentManager
    could be running on an alternate
    system from where it is configured to be running.   Because of
    this, the wrong(local) connector type is used to connect to
    nodeagent and status could be wrong.
    

Problem conclusion

  • The code has been modified to check the running system in
    determining connector type.
    
    APAR PM26178 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.19 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM26178

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-08

  • Closed date

    2011-01-24

  • Last modified date

    2011-10-04

  • 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

  • R700 PSY UK71280

       UP11/09/10 P F109

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM26178

Modified date: 04 October 2011