Fixes are available
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
This fix is to address WSGrid PJM Subjobs in restartable state after Scheduler goes down may not be able to be restarted issue.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 Parallel Job Manager Batch * * functionality. * **************************************************************** * PROBLEM DESCRIPTION: WSGrid Parallel Job Manager subjobs * * that are in executing status when the * * Scheduler goes down are not able to * * be restarted. * **************************************************************** * RECOMMENDATION: * **************************************************************** The endpoint uses a proxy scheduler lock in order to monitor the status of the scheduler that submitted the job. If the scheduler goes down, the job is cancelled on the endpoint. The proxy scheduler lock is specific to a scheduler servant region and is passed along to the endpoint in the xJCL. Since a subjob's restart does not originate from the scheduler, but instead from the endpoint, the modified xJCL, with the "old" lock name was being used to restart the subjob. This caused the subjob to believe the scheduler was down and to go back into the restartable state.
Problem conclusion
Since only the Top Level job needs to be notified if the Scheduler server goes down and subsequently cancels all subjobs, the code was modified to remove the proxy scheduler lock from the xJCL of all subjobs. APAR PI28397 is currently targeted for inclusion in Fix Pack 8.5.5.5 of WebSphere Application Server V8.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI28397
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-24
Closed date
2015-01-16
Last modified date
2015-01-16
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
R850 PSY
UP
Document Information
Modified date:
28 April 2022