PH10333: DURING EXTENSION OF CLUSTERS JOBS ABENDED WITH RC=12 AND EXISTI NG ENDPOINTS ARE NOT FOUND

9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• During extension of clusters jobs abended with RC=12 in wsgrid
  uti¦ity. The indeed existing end points are not found. Before
  the abends serverindex.xml was updated.
  This occurs because the endpoints
  are becoming deregistered at the point of the problem.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Java Batch                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Adding servers to an existing job       *
  *                      scheduler cluster while it is running   *
  *                      prevents submitting new jobs.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When adding a server to an existing cluster hosting the Java
  Batch Job Scheduler, it results in the endpoint servers
  hosting batch applications to be de-registered from the job
  scheduler.  This prevents new jobs from being submitted,
  effectively preventing any new work from occuring. Restarting
  the endpoint servers resolves this issue.
  

Problem conclusion

• A code update has been made to properly handle expansion of a
  job scheduler cluster while it is running.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.5.0 and 8.5.5.16.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• 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

• R900 PSY

     UP