APAR status
Closed as new function.
Error description
When Job Schedulers and Endpoint servers are available on several LPARs, the Scheduler can select an Endpoint on any LPAR to run the job, not necessarily the one on which it is running (local). If DB2 becomes unavailable on one of the LPARs, it can affect the update of the status table and subsequent job status communication to Schedulers on the other LPAR. An option to select a preference to have the Scheduler disperse jobs to Endpoint servers on the same LPAR (prefer local) would reduce the impact.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * * Java Batch * **************************************************************** * PROBLEM DESCRIPTION: A property to enable preference to * * dispatch batch jobs to servers on the * * same node as the Job Scheduler * **************************************************************** * RECOMMENDATION: * **************************************************************** When Job Schedulers and Endpoint servers are available on several nodes, the Scheduler can select an Endpoint on any node to run the job, not necessarily the one on which it is running (local). If the backend becomes unavailable on one of the nodes, it can affect the update of the status table and subsequent job status communication to Job Schedulers on the other node. An option to select a preference to have the Job Scheduler dispatch jobs to Endpoint servers on the same node (prefer local) would reduce the impact.
Problem conclusion
A new Job Scheduler custom property has been added: PreferLocalDispatch When defined as true, a Job Scheduler will prefer to dispatch jobs to servers hosting the application on the same node as it. If not are available, or there was a problem during the dispatch, it will dispatch to the next available server as before. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.9 and 8.5.5.20. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
Comments
APAR Information
APAR number
PH35447
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-03-17
Closed date
2021-05-26
Last modified date
2021-05-26
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
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900"}]
Document Information
Modified date:
27 May 2021