PQ85242: NODE FEDERATION ALLOWS DUPLICATE NODES TO BE FEDERATED

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Customer is running a Network Deployment environment with one
base server running in it.  This server was successully
federated.  They then created a new server via the Customization
Dialog.  When they ran BBOWADDN to federate this server, the job
ran fine but they then noticed that the serverindex tags for the
first base server had been removed from serverindex.xml and the
tags for the second (new) server are there.  We found that these
lines were deleted because, when using the dialogs to create the
second base server, the customer used the same node name as was
used when the first base server was created.  The customization
dialog defaults to the node name that was last entered into this
field.  The customer would like to be notified when the node
name being used already exists in the Deployment Manager, so
they can decide whether to proceed as is or change the node name
to a nonexistent one.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Server tags deleted from an existing    *
*                      serverindex.xml after running addnode   *
*                      and replaced with the new server from   *
*                      addNode. Pre existing servers in the    *
*                      node may not start, once the new        *
*                      node is added.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The addNode.sh shell script and BBOWADDN job need to check
and make sure a Node with a matching name does not already
exist in a given Cell.  If so the job should fail with the
message:
ADMU0033E: The node <nodeName> already has been added to the
           cell.
Problem conclusion
The underlying code of addNode.sh and BBOWADDN has been
modified to check the new node against the current cell's
nodes.

APAR PQ85242 is associated with SERVICE LEVEL W502005 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ85242
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-02-26
Closed date 2004-03-26
Last modified date 2004-04-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ86666    UP04/03/31 P F403

  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


Current web document: swg1PQ85242.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ85242
IBM Group: Software Group
Modified date: Apr 3, 2004