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
Occasionally, when endpoint server servant region is cancelled, the Job Management Console shows a job that was submitted to that endpoint remaining in submitted state.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Compute Grid version 8.0 on z/OS * **************************************************************** * PROBLEM DESCRIPTION: Occasionally, when endpoint server * * servant region is cancelled, the Job * * Management Console shows jobs that * * were submitted to that endpoint * * remaining in submitted state. * **************************************************************** * RECOMMENDATION: * **************************************************************** The job scheduler dispatch process was completed successfully and the job was marked as owned by the endpoint. However, on the endpoint server, there is a timing window where the servant region was cancelled after it picked up the job but before the record keeping was updated. Because of this, the control region did not know about this job so no clean up was done for this job when the servant region was down.
Problem conclusion
Currently, when about to execute a job (calling the BatchJobController.submitJob()),the endpoint server adds the job to the control region job cache. However, if the endpoint servant region is canceled at any point before the job is added to the job cache, no status update will be sent out. The runtime code has been updated to add the jobid to the control region job cache as soon as the runtime gets the job submission. This way, if the servant region goes down before it processes the job submission, the control region will have a record of this job and it will cancel the job and send update status to the 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
PI13410
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-11
Closed date
2014-06-04
Last modified date
2014-07-21
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:
27 April 2022