PK82690: FAILURE TO CREATE A CLUSTER WITH TWO CLUSTER MEMBERS THAT HAVE THE SAME NAME BUT DIFFERENT SHORT NAMES IN TWO DIFFERENT NODES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The customer attempted to create a cluster with two cluster
  members that have the same name (server_specific_name), but
  different short names in two different nodes, but the server
  failed on start with BBOM0057W message and DC3 abend.  The
  server_specific_uuid in was.env of the cluster members has more
  than the 40-chars limit (the failed server_specific_uuid has 80
  chars - to be exact).
  Here's the symptom:
  IEF403I DVSR99CS - STARTED - TIME=14.53.33
  +BBOM0057W DEFAULT VALUE OF ENVIRONMENT VARIABLE
  server_specific_uuid
  USED. LENGTH MUST NOT EXCEED 40 CHARACTERS.
  .
  +CEE0374C CONDITION=CEE3250C TOKEN=00040CB2 61C3C5C5 00000000
            WHILE RUNNING PROGRAM UNKNOWN
            AT THE TIME OF INTERRUPT
            ...
  BPXP018I THREAD 32B71A6000000000, IN PROCESS 51055530, ENDED
  WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04DC3000, AND REASON
  CODE 04010001.
  IEF450I DVSR99CS DVSR99CS - ABEND=SDC3 U0000 REASON=04010001
          TIME=14.53.34
  IEF404I DVSR99CS - ENDED - TIME=14.53.34
  $HASP395 DVSR99CS ENDED
  .
  and the server_specific_uuid in was.env of the cluster members
  had a value greater than 40-chars limit (80 chars - to be
  exact):
  server_specific_uuid=C3127481E00AC98B0000016C0000045A0AE8480DC31
  274CA91AB45870000016C0000045A0AE8480D
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere Application Server    *
  *                 V7.0                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Failure to start a cluster member       *
  *                      when two cluster members have the       *
  *                      same name but are in different nodes.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When two cluster members have the same name on different
  nodes, the cluster members cannot be started.
  During cluster creation, the configuration save operation
  generates the server_specific_uuid property incorrectly by
  concatenating the individual cluster member uuid's together
  since they have the same name.  This causes the startup
  failure since the server_specific_uuid is limited to 40
  characters.
  The following message is seen in the cluster member's log at
  startup:
  BBOM0057W DEFAULT VALUE OF ENVIRONMENT VARIABLE
  server_specific_uuid USED.   LENGTH MUST NOT EXCEED 40
  CHARACTERS.
  

Problem conclusion

• The code has been fixed to properly generate the
  server_specific_uuid when more than one cluster member has the
  same name.   This problem exists only on z/OS.
  
  APAR PK82690 is currently targeted for inclusion in Service
  Level (Fix Pack) 7.0.0.3 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 is sysrouted FROM one or more of the following:

  PK74800

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• BBGUBINF BBOUBINF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R700 PSY UK45160

     UP09/04/06 P F904

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.