PI14202: WSGRID RETURNED FALSE POSITIVE.

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.0.0.5: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 5
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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

• Compute grid environment experienced a loss of the database
  connection the LRS resulting in jobs not running properly which
  resulted in us having to cycle the environment to bring things
  back up. During that time, a job was submitted and WSGrid
  returned an exit status of 0 (successful) which is a false
  positive. WSGrid should not report an exit status of zero when
  it encounters this kind of failure.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Compute Grid version 8.0          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Java WSGrid client returns an exit      *
  *                      code of zero even though the job        *
  *                      execution encountered a failure.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The JobSchedulerBus was stopped when the server was restarted.
  WSGrid client does not catch this type of error and returns
  zero as a successful exit status.
  

Problem conclusion

• The java WSGrid client has been updated to catch all type of
  exceptions and set the appropriate return code.  The fix for
  this APAR is currently targeted for inclusion in fixpack
  8.0.0.5. 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