Fixes are available
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.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
Invalid job status in jmc just after changing security role of job scheduler.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere Batch Function * * within IBM WebSphere Application Server * * V8.5. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server must be * * restarted to pick up Job Scheduler * * Security role to user or group * * mapping changes. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a Security role to user or group mapping occurs for the Batch Job Scheduler, the scheduler application is stopped, updated with the new roles, and then restarted. Upon restart, any new batch jobs recieved by the scheduler were being left in Submitted state, even though they were being processed.
Problem conclusion
An update was implemented so that the Job Scheduler application is dynamically re-initialized after any Security role to user/group mapping occurs. Jobs are processed, status information updated, and there is no longer a need to recycle the WebSphere Application Server. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.4. Please refer to the Recommended Updates page for delivery information: http://www-01.ibm.com/support/docview.wss?uid=swg27036319
Temporary fix
Comments
APAR Information
APAR number
PI24811
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-08-28
Closed date
2014-10-29
Last modified date
2014-10-29
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 APP S
Fixed component ID
5724J0800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022