Fixes are available
8.0.0.4: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 4
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
When a job goes into the restartable state on one endpoint and then the job is restarted on a different endpoint the job does not complete. A null pointer error appears and the job stays in the restartable state.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere Extended Deployment * * Compute * * Grid 8.0 and the batch function * * of WebSphere Application Server 8.5. * **************************************************************** * PROBLEM DESCRIPTION: When a job is dispatched to a * * different endpoint (on restart) than * * it was on the initial execution, the * * persistent user data is lost. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a job is submitted, an endpoint is assigned to that job based on the specifications in the xJCL file. If a job runs into an issue or is stopped/cancelled by the user then the job will go to the restartable state. The problem occurs when a different endpoint is used on restart. The step context that stores the information needed to restart the job was removed before it had a chance to be used, which caused the persistent user data to be null.
Problem conclusion
The loss of information that occurred when a job was restarted on a different endpoint was fixed so that the step context is passed on from endpoint to endpoint. The fix for this APAR is currently targeted for inclusion in fixpack 8.0.0.4. 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 number
PI14380
Reported component name
WXD COMPUTE GRI
Reported component ID
5725C9301
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-25
Closed date
2014-06-11
Last modified date
2014-06-11
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
Document Information
Modified date:
28 April 2022