Fixes are available
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
Typically the WebSphere Scheduler service requires only one instance being active in a cluster of servers. However, WebSphere for z/OS servers are normally configured with multiple servants and the scheduler poll daemon does not restrict itself to operating in only one Servant region. This can lead to multiple servants attempting to run the same task. One of the possible symptoms can be the following warning: com.ibm.websphere.scheduler.TaskPending: SCHD0057W: The task information for task ID 1664701 for scheduler MyScheduler (MyScheduler) cannot be updated in the database because the task has already been run by another Scheduler, the task information was changed, or the task was cancelled.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0, V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: All Servants attempts to fire the * * same task within a z/OS server * * resulting in SCHD0057W * **************************************************************** * RECOMMENDATION: * **************************************************************** The scheduler service will be started on all servers in the cluster. A lease is required for the scheduler service to start processing the tasks and for ensuring that only one scheduler instance will fire the task. Typically the server that comes up first will obtain the lease. WebSphere z/OS platform supports multiple servants for Workload Managament (WLM) and it was found that all of these servants within a z/OS server were able to obtain the leases. This was possible because the scheduler uses the server name for the lease owner name and all of these servant shared the same name and hence they were all able to obtain the lease and also can fire the tasks. This can result in the following messages in a multi servant zOS environment: com.ibm.websphere.scheduler.TaskPending: SCHD0057W: The task information for task ID 1664701 for scheduler MyScheduler (MyScheduler) cannot be updated in the database because the task has already been run by another Scheduler, the task information was changed, or the task was cancelled. Now with this APAR, the lease owner name has been made unique to uniquely identify each servant and thereby ensuring only one servant will obtain the lease at any point of time.
Problem conclusion
The WebSphere scheduler component has been updated such that the scheduler poll daemon is active on only on servant in a z/OS server envrionment. APAR PM58610 is currently targeted for inclusion in WebSphere Application Server Fix Packs 7.0.0.25, 8.0.0.5, and 8.5.0.1. Sysroute APAR PM65489 will be used to deliver this fix in WebSphere Application Server V6.1 Fix Pack 6.1.0.45. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM58610
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-20
Closed date
2012-05-24
Last modified date
2012-11-02
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
R700 PSY UK81738
UP12/10/04 P F210
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
28 October 2021