PQ84602: WITH W502000, UPDATING SERVER SHORTNAME RESULTED IN TWO SYMBOLICLINKS PER APP SERVER INSTEAD OF A SYMBOLIC LINK REPLACEMENT.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Customer created a cluster using the admin console.
The servers were created using an existing app server model and
saved.  In the HFS they saw links pointing to
cellname.nodename.BBOS00x.  Then they updated the server
shortname for each of the newly created app servers such that
the server shortname matched the server name.  In the past, this
caused the symbolic link ending BBOS00x to be replaced by one
ending in the server short name; however they ended up with two
links per app server, one cellname.nodename.BBOS00x and one
cellname.nodename.servershortname.
The existence of the extra symbolic link prevents the
successful creation of additional cluster servers (or perhaps
even standalone servers).  They have to manually delete the
cell/node.BBOS000x link in order to successfully create any
more cluster servers; otherwise, one can end up with a very
corrupted HFS.
Another concern is that they see the following message:
ADMS0016I: Configuration synchronization failed.  This message
came out in the zOS system log and the Nodeagent jeslog.
They would like to see something stronger than an information
message in this circumstance, and secondly, they would like to
see a message in the admin console since that is where the
work is being done.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: When you change an Servers short name   *
*                      (On the Administrative Console ->       *
*                       Application Server -> <server name>    *
*                       -> Short Name)                         *
*                      The correct symlink is generated        *
*                      but the old one remains.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When you change the shortname of your server
a new symlink is created, ie: (CELLSHORT.NODESHORT.NEWSERVSHORT)
the previously used one remains
(CELLSHORT.NODESHORT.OLDSERVSHORT)
Problem conclusion
The Transformer was modified to clean up the old symlinks
correctly.

APAR PQ84602 is associated with SERVICE LEVEL W502004 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ84602
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-12
Closed date 2004-03-10
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 UQ86037    UP04/03/17 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: swg1PQ84602.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 #: PQ84602
IBM Group: Software Group
Modified date: Apr 3, 2004