PM47120: THIS APAR IS TO SHIP FIXES FOR WCG V8 FIX PACK 2

8.0.0.2: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 2
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.3: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 3
8.0.0.4: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 4
8.0.0.5: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 5

APAR status

• Closed as program error.

Error description

• This APAR is to ship fixes for WCG V8 Fix Pack 2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere Compute Grid V8          *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR is to ship cumulative fixes   *
  *                      for WebSphere Compute Grid V8 Fix       *
  *                      Pack 2                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR contains fixes for the following problems:
  - Welcome page does not display Compute Grid when installed
  - Job Scheduler setup through an admin agent
  - Native wsgrid and long xJCL fixes (PMR 33761,004,000)
  - NPE occurs when creating a profile without default app and
  admin console
  - Invalid endpoint was listed after deleting a server or
  cluster
  - Admin agent erroneously listed as scheduler target
  - JMC welcome splash page contains incorrect links
  - Job Scheduler panel JDBC providers shows none when they exist
  - NPE in DefaultBatchJobStepBean.setupLogHandler
  - Parallel job intermittently remains in executing state
  - Exception during showdown in BatchSensorComponent
  - Errors in fail over scenario when using local tran mode
  - Valid JobLevelUserData is reset in mixed setp
  - WSGRID client genenerate non-unique correlator
  - SQLException while using oracle backend
  - ClassCastException while using oracle backend
  - Duplicate key exception in Scheduler SR
  - Handle  runtime exception UnsupportedOperationException when
  using Blob.free
  - Handle default transaction mode differences between versions
  - Record not correctly skipped during batch update
  - Resolve issues that occur when number of job log
  subdirectories exceeds 64K
  - PJM top level job waits forever
  - PJM failure with single JVM
  - Cursor holdable JDBC reader did not work with type 2 drivers
  

Problem conclusion

• The reported issues have been resolved in WebSphere Compute
  Grid Fixpack 2.
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?uid=swg27022998
  

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

  WXD COMPUTE GRI

• Fixed component ID

  5725C9301

Applicable component levels

• R800 PSY

     UP