Scheduler messages

SCHD0001I: The Scheduler Service has started.
Explanation: The Scheduler Service is started.
User Response: No user action is required.

SCHD0002I: The Scheduler Service has stopped.
Explanation: The Scheduler Service has stopped and no longer scheduling tasks.
User Response: No user action is required.

SCHD0003E: An error occured while starting the scheduler service: {0}.
Explanation: An unexpected error occurred. See the FFDC logs and the associated exception for details.
User Response: See the server log files for detailed exception data.

SCHD0004E: Scheduler {0} specified an invalid security role string.
Explanation: The security role configured on the specified Scheduler resource does not exist.
User Response: Verify the security role attribute for the specified scheduler has been specified correctly.

SCHD0005I: Error initializing Scheduler PMI.
Explanation: The Scheduler PMI module could not be registered with the PMI service.
User Response: Verify that the application server product is installed correctly, and check the logs for further details. This error affects only performance data gathering.

SCHD0006E: Task with task ID {0} could not be found in the persistent store.
Explanation: An operation on the specified task id was attempted, however, the task is not present in the database. Possible causes include: the task was automatically removed from the database upon task completion, the task was deleted with a call to Scheduler.cancel(...) or Scheduler.purge(...), or the task never existed
User Response: See the server log files for possible exceptions or validate that the task was scheduled properly.

SCHD0007E: Error while accessing the persistent store: {0}.
Explanation: The datastore used by this scheduler instance could not be reached.
User Response: See the server log files for detailed exception data.

SCHD0008I: Feature not currently supported.
Explanation: This feature is not currently enabled in this version.
User Response: No user action is necessary.

SCHD0009I: The Scheduler Service is not enabled.
Explanation: A scheduler instance cannot be used on this server while the scheduler service is disabled.
User Response: See the documentation for information about enabling the Scheduler service.

SCHD0010E: An error occured while firing a task.
Explanation: An exception was thrown while attempting to run a task.
User Response: See the log files for failure details.

SCHD0011I: {0} must be specified for task type {1}.
Explanation: The task of the specified type requires that this property is set.
User Response: Verify that this property is set when creating a new schedule.

SCHD0012I: {0} is not currently supported.
Explanation: The specified function or feature is not yet implmented or tested in this release.
User Response: Verify that the specified function is available in the InfoCenter for this version of the product. If it is, contact IBM product support for help.

SCHD0013E: The following error occurred while accessing the UserCalendar with JNDI Name {0} and specifier {1} : {2}.
Explanation: The UserCalendar session bean specified by this task could not be contacted.
User Response: Verify that the session bean is available.

SCHD0014E: An error occured while publishing a notification: {0}
Explanation: The Notification Sink session bean specified by this task could not be contacted.
User Response: Verify that the session bean is available.

SCHD0015E: User does not have authority to use this scheduler instance.
Explanation: The user associated with the calling thread does not fit the security role that is specified in the configuration for this scheduler instance.
User Response: See the InfoCenter documentation for a detailed explaination of security.

SCHD0016E: The user does not have authority to perform the requested action.
Explanation: The user associated with the calling thread does not have permission to modify a task which was created by another user.
User Response: See the InfoCenter documentation for a detailed explaination of security.

SCHD0017E: The {0} attribute must be specified when creating a {1}.
Explanation: When creating or scheduling objects, this attribute is required.
User Response: Provide the missing attribute and try again.

SCHD0018E: Work Manager with JNDI name {0} could not be found.
Explanation: A WorkManager was specified on a Scheduler resource, however, the WorkManager with the specified JNDI name is not present.
User Response: Verify that the specified work manager exists in the global name space. If it does not exist, create it or alter the Scheduler resource to use the default WorkManager.

SCHD0019E: Data source with JNDI name {0} could not be found.
Explanation: A Data source was specified on a Scheduler resource, however the Datasource with the specified JNDI name is not present.
User Response: Verify that the specified Data source exists in the global name space. If it does not exist create it or alter the Scheduler resource to use an alternate JNDI name.

SCHD0020I: Invalid scheduler configuration: {0}.
Explanation: The specified configuration information is invalid or missing.
User Response: Verify that the Scheduler resource configuration attributes are present and valid. Use the administration console to verify the Scheduler resources.

SCHD0021I: Exception trace information follows: {0}.
Explanation: An unexpected exception has occurred.
User Response: Check for other messages that contain exceptions further in the log.

SCHD0022E: Invalid calendar specified.
Explanation: The Calendar specified is not a valid type.
User Response: Verify that the Calendar specified implements the UserCalendar and associated interfaces.

SCHD0023E: Invalid notification bean specified.
Explanation: The notification specified is not a valid type.
User Response: Verify that the specifed notification implements the NotificationSink and associated interfaces.

SCHD0024E: Task {0} could not execute after {1} attempts. The task will be suspended.
Explanation: The TaskInfo object used to create the task stated that if a task were to fail, it would be retried a specified number of times, then suspended if still unsuccessful.
User Response: The task must be manually resumed by calling the method resume(...) on the Scheduler instance where the task exists. If this is not the desired behavior, see the InfoCenter documentation for information on the various modes of operation.

SCHD0025E: Maximum number of attempts has occured for task {0}.
Explanation: The TaskInfo object used to create the task stated that if a task were to fail, it would be retried a specified number of times. If still unsuccessful, the failure is ignored and the scheduler database updated.
User Response: The transaction in which a task is run and how a failure is handled can be controlled at the time of task creation by calling various methods on the TaskInfo interface. The InfoCenter documentation contains details about the different modes of operation.

SCHD0026E: Scheduler instance {0} failed to initialize because the following error occurred: {1}
Explanation: The specified scheduler could not be initialized and is unable to poll for scheduled tasks.
User Response: Verify that the Scheduler resource is configured correctly and that the associated database is active.

SCHD0027E: Message key {0} was not found in any searched resource bundles.
Explanation: A key was passed into the Messages class to resolve to a string, but a properties file for the locale could not be found and the appropriate message could not be retrieved.
User Response: Determine why the message catalog could not be found.

SCHD0028I: Scheduler service cannot be disabled.
Explanation: The Scheduler service has been disabled in the configuration, but will continue to run because because of service dependencies.
User Response: Re-enable the scheduler service in the configuration to avoid receiving this message in the future.

SCHD0029W: Scheduler service disabled due to previous errors.
Explanation: The Scheduler service experienced an error during initialization. The service is inaccessible on the given server. The root error should have been logged previously.
User Response: Try to resolve the previously logged errors. If unable to do so, please contact IBM support.

SCHD0030E: Scheduler service could not resolve the {0} service.
Explanation: The Scheduler service could not resolve the specified service, which is required for the Scheduler service. Look through the log to see if the specified service started successfully.
User Response: If you wish to use the Scheduler service, correct the problem with the specified service. If you are unable to correct the problem, contact IBM support.

SCHD0031I: The Scheduler Service is starting.
Explanation: The Scheduler Service is starting.
User Response: No user action is required.

SCHD0032I: The Scheduler {0} is initializing.
Explanation: The specified Scheduler instance is initializing.
User Response: No user action is required.

SCHD0033I: The Scheduler {0} has initialized.
Explanation: The specified Scheduler instance has initialized and is ready to accept requests.
User Response: No user action is required.

SCHD0034I: The Scheduler {0} is stopping.
Explanation: The specified Scheduler instance and daemon are stopping.
User Response: No user action is required.

SCHD0035I: The Scheduler {0} has stopped.
Explanation: The specified Scheduler instance and daemon have stopped.
User Response: No user action is required.

SCHD0036I: The Scheduler Service is initializing.
Explanation: The Scheduler Service is initialized.
User Response: No user action is required.

SCHD0037I: The Scheduler Service has been initialized.
Explanation: The Scheduler Service has been initialized.
User Response: No user action is required.

SCHD0038I: The Scheduler Daemon for instance {0} has started.
Explanation: The Scheduler Daemon has started for the specified Scheduler instance.
User Response: No user action is required.

SCHD0039I: The Scheduler Daemon for instance {0} has been stopped.
Explanation: The Scheduler Service has stopped for the specified Scheduler instance.
User Response: No user action is required.

SCHD0040I: The Scheduler Service is stopping.
Explanation: The Scheduler Service is stopping.
User Response: No user action is required.

SCHD0041E: The Data source JNDI Name attribute for scheduler resource {0} ({1})is missing. The scheduler resource is not created.
Explanation: A scheduler resource requires a datasource JNDI name, however the data source JNDI Name attribute in the configuration information for the specified scheduler resource is blank or null.
User Response: Use the WebSphere administration console to configure a data source JNDI name for the specified scheduler resource.

SCHD0042E: The Work Manager JNDI name for scheduler resource {0} ({1}) is missing. The scheduler resource is not created.
Explanation: A scheduler resource requires a work manager JNDI name, however, the Work Manager JNDI name in the configuration information for the specified scheduler resource is missing. This can occur for the following reasons: The Work Manager attribute for the specified scheduler resource is blank or not configured, the configured Work Manager's JNDI name attribute is blank or null, or the configured Work Manager cannot be found in the configuration information.
User Response: Use the WebSphere Application Server administration console to verify a Work Manager is configured for the specified scheduler resource. Also, verify the configured Work Manager's configuration contains a valid JNDI name attribute.

SCHD0043E: The JNDI name for scheduler resource {0} is missing. The scheduler resource is not created.
Explanation: A scheduler resource requires a JNDI name, however, the JNDI name in the configuration information for the specified scheduler resource is blank or null.
User Response: Use the WebSphere Application Server administration console to configure a JNDI name for the specified scheduler resource.

SCHD0044W: The Poll Interval attribute value of {0} seconds for the scheduler resource {1} is not within the valid range. The valid range is {2} to {3}. The scheduler resource is created using a poll interval of {4} seconds.
Explanation: The configured poll interval value is not in the specified range, however, the scheduler resource is created with the specified poll interval. The poll interval value specifies the length of time in seconds the scheduler polls the database for tasks.
User Response: Use the WebSphere Application Server administration console to configure the poll interval value for the specified scheduler resource.

SCHD0045E: An exception occurred retrieving the Data source Alias configuration information for scheduler resource {0}.
Explanation: An exception occurred while retrieving the Data source Alias configuration information.
User Response: Use the Websphere Application Server administration console to verify the Data source Alias is configured correctly.

SCHD0046E: The table {0} in datasource {1} used by scheduler resource {2} ({3}) is missing or is not accessible.
Explanation: The specified table cannot be found in the configured database for the specifed scheduler resource. The possible causes are: An incorrect datasource JNDI name has been configured, an incorrect table prefix has been configureed, or the scheduler tables have not been created in the database.
User Response: Use the WebSphere Application Server administration console to verify the data source JNDI name and the table prefix configuration. To create the scheduler database tables, see the "Creating the database for scheduler" article in the WebSphere Application Server InfoCenter.

SCHD0047E: The TaskInfo class {0} must have a registered implementation.
Explanation: The specified TaskInfo class type cannot be used because it is not of a registered type.
User Response: Modify the application to use a TaskInfo class that has a registered implementation and submit the create request again.

SCHD0048E: The task attribute NumberOfRepeats must be non-zero number.
Explanation: The NumberOfRepeats attribute must not be zero.
User Response: Set the NumberOfRepeats attribute to a value other than zero and submit the request again.

SCHD0049E: The start-by time must be greater than the start time for non-repeating tasks.
Explanation: Creating a new task using a start-by time less than the start time for a non-repeating task is an invalid operation.
User Response: Modify the StartByTime, the StartTime, StartTimeInterval, or the NumberOfRepeats and submit the request again.

SCHD0050E: The task attribute InitialState has an invalid value of {0}. Valid values are TaskStatus.SCHEDULED ({1}) and TaskStatus.SUSPENDED ({2}).
Explanation: The specified InitialState value is not valid at this time. The valid values are SCHEDULED or SUSPENDED.
User Response: Set the InitialState value to either SCHEDULED or SUSPENDED and submit the request again.

SCHD0051E: The task (taskId={0}) has been cancelled or is complete. Cancelled or completed tasks cannot be resumed.
Explanation: The specified task has already run or has been cancelled and cannot be resumed.
User Response: No user action required.

SCHD0052E: The task (taskId={0}) has a current state of {1}, however the task must have the state of TaskStatus.COMPLETE ({2}) or TaskStatus.CANCELLED ({3}) before it can be purged.
Explanation: Attempt was made to purge the task, however, the task is not in the correct state to be purged. The task must be in COMPLETE state or it must be CANCELLED.
User Response: Allow the task to run before purging or cancel the task first and then submit the purge request again.

SCHD0053E: The task (taskId={0}) cannot be suspended because it has been cancelled or is already completed.
Explanation: The specified task has already run or has been cancelled and cannot be suspended.
User Response: No user action is required.

SCHD0054E: TaskInfo object {0} could not be created because the following error occurred: {1}.
Explanation: The TaskInfo object could not be created because an error occurred.
User Response: See the user action for the message that contains the cause of the error.

SCHD0055E: The NotificationSink object for task (taskId={0}) cannot be retreived because the following error occurred: {1}.
Explanation: An error occurred that prevented the NotificationSink object to be retreived from the task information. See the message that contains the cause of the error.
User Response: See the user action for the message that contains the cause of the error.

SCHD0056W: The task information for task ID {0} cannot be inserted into the database because the task already exists.
Explanation: The task with specified task ID cannot be inserted into the database because the task already exists in the database. This can occur when another Scheduler inserts the same task into the database table.
User Response: No user action is required.

SCHD0057W: The task information for task ID {0} 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.
Explanation: The task with the specified task ID cannot be updated in the database because it was already updated.
User Response: No user action required.

SCHD0058W: The task information for task ID {0} cannot be updated in the database because the task record is lock by another process.
Explanation: The task with the specified task ID cannot be updated in the database because the task record is locked by another process. This can occur when another Scheduler is updating the same task record.
User Response: No user action is required.

SCHD0059W: The task information for task ID {0} cannot be removed from the database because the task does not exist or the task information has already been removed by another Scheduler.
Explanation: The task with the specified task ID cannot be removed from the database because it does not exist.
User Response: No user action is required.

SCHD0060W: The task information for task ID {0} cannot be removed from the database because the task record is locked by another process.
Explanation: The task with the specified task ID cannot be removed from the database because the task record is locked by another process. This can occur when another Scheduler is updating or removing the same task record.
User Response: No user action is required.

SCHD0061E: The task information for task ID {0} and owner token {1} was not found in the database.
Explanation: The task with the specified task ID and owner token is not in the database.
User Response: Specify another task ID and try the request again.

SCHD0062E: The task version field value of {0} for task ID {1} is not supported by this level of the Scheduler. The supported task versions are {2}. This task will not run.
Explanation: The Scheduler is attempting to execute the specified task, however, the version of the task record is not supported by this scheduler. This can occur when a task is created on a later version of WebSphere Application Server product and then run on eariler version of WebSphere Application Server product.
User Response: Make sure the version of WebSphere Application Server product is at the same or later version than the version of WebSphere Application Server product that created the task.

SCHD0063E: A task with ID {0} failed to run on Scheduler {1} ({2}) because of an exception: {3}.
Explanation: The Scheduled task failed to run due to an unexpected error and was rolled-back. See the service log for the detailed exception stack trace.
User Response: See the message that contains the cause of the error. The task will continue execute until the problem is resolved or the task is cancelled.

SCHD0064E: An error occurred while attempting to commit the transaction by the scheduler {0} ({1}). The transaction is rolled back. The following error occurred: {2}.
Explanation: The scheduler tried to commit the transaction, but an error occurred. The transaction is rolled back. See the message that contains the cause of the error.
User Response: See the message that contains the cause of the error.

SCHD0065E: The following error occurred while scheduler {0} ({1}) attempted to roll back the transaction: {2}.
Explanation: The scheduler tried to roll back the transaction, but an error occurred. See the message that contains the cause of the error.
User Response: See the message that contains the cause of the error.

SCHD0066E: The following error occurred in scheduler {0} ({1}) while applying the default User Calendar to the current time: {2}.
Explanation: An error occurred attempting to calculate the next fire time using the default User Calendar.
User Response: See the message that contains the cause of the error.

SCHD0067E: An error occurred while calculating the next fire time or the start by interval. See the previous error message for the cause of the error.
Explanation: An error occurred while calculating the next fire time or the start by interval. The previous message contains the cause of the error.
User Response: See the previous message for the cause of the error.

SCHD0068E: The task failed to execute because an error occurred. See the previous messages for the cause of the error.
Explanation: The scheduler attempted to execute the task, but an error occurred preventing the task from executing.
User Response: See the previous messages for the cause of the error.

SCHD0069W: The Scheduler {0} ({1}) was unable to execute the task for task ID {2} because a task collision occurred. Task collisions occur when another Scheduler updates or executes the same task. The cause of the collision is: {3}.
Explanation: Another scheduler executed or updated the task prior to this scheduler updating or executing the task. The task was executed or updated by another scheduler. This can occur when the two or more schedulers compete for the same tasks.
User Response: See the WebSphere Application Server InfoCenter for information on reducing task collisions.

SCHD0070E: The Task Store is not available.
Explanation: The Task Store object for this scheduler is null.
User Response: See previously listed error messages to determine the cause.

SCHD0071E: Scheduler resource {0} has JNDI name attribute value of {1} which is the same as the value of the data source JNDI name attribute. The scheduler resource is not created.
Explanation: The JNDI name of the scheduler resource is the same as the scheduler resource data source JNDI name attribute.
User Response: Use the WebSphere Application Server administration console to modify either the datasource JNDI name or the JNDI name of the scheduler resource.

SCHD0072E: Scheduler resource {0} has a JNDI name attribute value of {1}, which is the same as the value of the work manager JNDI name attribute. The scheduler resource is not created.
Explanation: The JNDI name of the specifed scheduler resource is the same as the work manager JNDI name attribute.
User Response: Use the WebSphere Application Server administration console to modify either the work manager JNDI name in the Work Manager resource or modify the JNDI name of the scheduler resource.

SCHD0073E: The Scheduler implementation class attribute is missing for scheduler {0} ({1}). The scheduler resource will not be created.
Explanation: The scheduler implementation class for the specified scheduler resource is missing. An implementation class is required.
User Response: Specify a valid scheduler implementation class.

SCHD0074E: The Scheduler {0} ({1}) was not able to acquire a read lock for the AsynchScope because the following error occurred: {2}
Explanation: An error occurred which prevented the specified scheduler from acquring a read lock for the AsynchScope.
User Response: See the message that contains the cause of the error.

SCHD0075E: The following error occurred in scheduler resource {0} ({1}) while cancelling task for task id {2}: {3}
Explanation: An unexpected error occurred while the specified scheduler resource was cancelling the specified task.
User Response: See the message that contains the cause of the error. The server log files may contain additional failure details.

SCHD0076E: Scheduler resource {0} ({1}) was unable to fire a notification event of {2} for task with task id {3} because the following error occurred: {4}
Explanation: An unexpected error occurred while the specified scheduler resource was firing the specified notification event for the specified task.
User Response: See the message that contains the cause of the error. The server log files may contain additional failure details.

SCHD0077I: The Scheduler Service is starting the Schedulers.
Explanation: The Scheduler Service has initialized and is starting each configured Scheduler instance.
User Response: No user action required.

SCHD0078I: The Scheduler Service has completed starting the Schedulers.
Explanation: The Scheduler Service has initialized and has started each configured Scheduler instance.
User Response: No user action required.

SCHD0079E: The Scheduler {0} ({1}) was unable to reschedule failed task {2} due to an unexpected error: {3}.
Explanation: The Scheduler attempted to re-execute a task that previously failed due to an error.
User Response: See previous messages and the included exception for further information. Once the error is resolved, the Scheduler will attempt to re-execute the failed task.

SCHD0080E: The Scheduler was unable to create the task handler EJB home object due to an unexpected error: {0}.
Explanation: The Scheduler attempted to create an instance of the defined task hander EJB home, but failed to do so because of an unexcepted error.
User Response: See previous messages and the included exception for further information. Once the error is resolved, the Scheduler will attempt to re-execute the failed task.

SCHD0081E: The Scheduler was unable to create the task handler EJB home for JNDI name {0} due to an unexpected error: {1}.
Explanation: The Scheduler attempted to create an instance of the defined task hander EJB home, but failed to do so because of an unexcepted error.
User Response: See the message that contains the cause of the error. The server log files may contain additional failure details.

SCHD0082E: Unable to determine the configuration location for resource URI {0}. The URI resolved to object name {1} with location properties {2}.
Explanation: The Scheduler attempted to find the server, node or cell name from the URI. The URI does not contain the expected key field names server or node or cell.
User Response: Correct the URI and try your request again.

SCHD0083E: Unable to find the scheduler configuration for resource URI {0}.
Explanation: The Scheduler attempted to find the configuration described in the message but could not locate it.
User Response: Correct the URI and try your request again.

SCHD0084W: The lease manager tables in datasource {0} used by scheduler resource {1} ({2}) are missing, are not accessible, or are not configured correctly. The scheduler function will run normally without these tables, however multiple schedulers using the same task tables may experience a high rate of task collisions which may impact overall performance.
Explanation: The Scheduler attempted to find the lease manager tables and they are missing. The lease manager tables must reside in the specified datasource and have names that begin with the configured table prefix and end with "LMGR" and "LMPR".
User Response: See the WebSphere Application Server InfoCenter for information on creating scheduler tables.

SCHD0085E: Unable to find datasource JNDI name {0}. The following configuration files were searched: {1}.
Explanation: The Scheduler was unable to find the datasource for the specified JNDI name in the message.
User Response: Verify that the specified datasource exists in the configuration and it exists at the same or higher scope than the scheduler configuration.. If it does not exist, create it or alter the Scheduler resource to use an existing datasource. See the WebSphere Application Server InfoCenter for more information about creating datasources and modifying scheduler configurations.

SCHD0086I: Table {0} cannot be created because it already exists in the database.
Explanation: The specified table already exists in the database.
User Response: No user action required.

SCHD0087I: Scheduler tables created successfully.
Explanation: The Scheduler tables were created in the database.
User Response: No user action required.

SCHD0088I: Index {0} created successfully.
Explanation: The specified index was created in the database.
User Response: No user action required.

SCHD0089I: Table {0} cannot be dropped because it does not exist in the database.
Explanation: The specified table cannot be dropped because it does not exist in the database.
User Response: No user action required.

SCHD0090I: Scheduler tables dropped successfully.
Explanation: The Scheduler tables were dropped from the database.
User Response: No user action required.

SCHD0091E: Beginning index of {0} is larger than the end index of {1}.
Explanation: The specified beginning index value is larger than the specified end index value.
User Response: Modify the index values so the beginning index is smaller than the end index and submit the request again.

SCHD0092E: Beginning index of {0} cannot be negative.
Explanation: The specified beginning index value is less than 0.
User Response: Modify the beginning index value so it is equal or greater than 0 and submit the request again.

SCHD0093E: End index of {0} cannot be negative.
Explanation: The specified end index value is less than 0.
User Response: Modify the end index value so it is equal or greater than 0 and submit the request again.

SCHD0094E: End index of {0} is smaller than beginning index of {1}.
Explanation: The specified end index value is less than the specified beginning index value.
User Response: Modify the index values so the beginning index is smaller than the end index and submit the request again.

SCHD0095E: The SQL statement for statement key {0} cannot be found for table key {1}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

SCHD0096E: The current user is not in the appropriate role to use the {0} method.
Explanation: The current user is not in a role that has authority to execute the specified method. All Scheduler API and Mbean methods are protected by role-based security. In general, to modify scheduler tasks or scheduler runtime attributes the user must be in a operator or higher role. To view tasks or scheduler runtime attributes the user must be in a monitor or higher role.
User Response: Either login with a user id which is in the appropriate role or add this user to the appropriate role. Adding users to roles is performed using the Administration Console. Please see the InfoCenter for more information.

SCHD0097E: The task operation {0} is not supported by task type {1}.
Explanation: The supplier of the specified task type has indicated that the specified task operation is not allowed.
User Response: Change your application so it does not call the specified operation.

SCHD0098E: Could not determine the task operation for method {0}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

SCHD0099E: Exception occurred while deserializing object {0}: {1}
Explanation: An unexpected error occurred. See the FFDC logs and the associated exception for details.
User Response: See the server log files for detailed exception data.

SCHD0100I: Scheduler tables verified successfully.
Explanation: The Scheduler tables were verified in the database.
User Response: No user action required.

SCHD0102I: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

SCHD0103W: The Scheduler {0} ({1}) was unable to run task {2} because the application or module is unavailable: {3}.
Explanation: The Scheduler is attempting to run a task, but the application or module that the task was created with is not available.
User Response: Start or install the application, module or component.

SCHD0104E: The Scheduler poll daemon {0} ({1}) failed to load tasks from the database due to an exception: {2}
Explanation: The Scheduler is attempting to load tasks from the database, but was unable to complete due to an unexpected exception. Some tasks will fail to run until the problem is resolved.
User Response: Review the error and resolve the problem. The daemon will continue to attempt to poll the database.

SCHD0105E: A byte array expected field {0} with version {1} but read version {2}.
Explanation: The Scheduler is attempting to read an object from an input stream, but the object's version number was unexpected.
User Response: This error is typically caused by a mismatch in product versions or an unexpected product error. Verify that the version of the Scheduler that logged this error is compatible with the version of the Scheduler that created the task.

SCHD0106E: A byte array expected field with id {0} but read id {1}.
Explanation: The Scheduler is attempting to read an object from an input stream, but a field is incorrect or out of order.
User Response: This error is typically caused by a mismatch in product versions or an unexpected product error. Verify that the version of the Scheduler that logged this error is compatible with the version of the Scheduler that created the task.

SCHD0107E: A byte array read field {0} with an unexpected type of {1}.
Explanation: The Scheduler is attempting to read an object from an input stream, but the object's type number was unexpected.
User Response: This error is typically caused by a mismatch in product versions or an unexpected product error. Verify that the version of the Scheduler that logged this error is compatible with the version of the Scheduler that created the task.

SCHD0108E: Unable to de-serialize a home handle due to error: {0}
Explanation: The Scheduler is attempting to read a HomeHandle object from an input stream, but the Home is unavailable.
User Response: This error is typically caused when the application, module or EJB is not available. Review the full error to determine the cause of the problem.

SCHD0109E: Invalid value detected. The value for field {0} must be a valid non-null value.
Explanation: The specified field or argument must not be null.
User Response: Change the method or object call to set the appropriate argument or verify that the field value is properly set.

SCHD0110E: The DayOfWeek term must be between 1 and 7.
Explanation: The DayOfWeek term for the CRON calendar interval string is not in the correct range.
User Response: Update the DayOfWeek term in the calendar interval string to use a number between 1 and 7.

SCHD0111E: Incorrect number of terms specified.
Explanation: The CRON calendar interval string requires 6 terms: second minute HourOfDay DayOfMonth Month DayOfWeek
User Response: Correct the CRON calendar interval string to use the correct terms. See the javadoc for class com.ibm.websphere.scheduler.UserCalendar for details.

SCHD0112E: The DayOfMonth or DayOfWeek term must be specified, but not both.
Explanation: The CRON calendar interval string requires that either the DayOfMonth or DayOfWeek is specified, but not both.
User Response: Correct the CRON calendar interval string to use the correct terms. See the javadoc for class com.ibm.websphere.scheduler.UserCalendar for details.

SCHD0113E: Term value '?' is invalid for the specified term. The '?' token is only valid for terms DayOfMonth or DayOfWeek.
Explanation: The CRON calendar interval string requires that either the DayOfMonth or DayOfWeek is specified, but not both.
User Response: Correct the CRON calendar interval string to use the correct terms. See the javadoc for class com.ibm.websphere.scheduler.UserCalendar for details.

SCHD0114E: Invalid repeat value of {0} for term {1}. The value must be between 1 and {2}.
Explanation: The CRON calendar interval string allows terms with repeat values. Each repeating term type has a lower limit of 1 and an upper limit based on the term position.
User Response: Correct the CRON calendar interval string to use the correct terms. See the javadoc for class com.ibm.websphere.scheduler.UserCalendar for details.

SCHD0115E: Unable to parse CRON term {0}: {1}.
Explanation: The specified CRON calendar interval string has an incorrect term at the specified position. Positions are from 1 to 6.
User Response: Correct the CRON calendar interval string to use the correct terms. See the javadoc for class com.ibm.websphere.scheduler.UserCalendar for details.

SCHD0116E: Invalid range format string specified: {0}. Valid range format is: -
Explanation: The CRON calendar interval string allows terms with range values. The specified range is not of the correct syntax.
User Response: Correct the CRON calendar interval string to use the correct terms. See the javadoc for class com.ibm.websphere.scheduler.UserCalendar for details.

SCHD0117E: Unexpected tokens detected for term: {0}.
Explanation: The specified CRON calendar interval string term is formatted incorrectly and has too many tokens.
User Response: Correct the CRON calendar interval string to use the correct terms. See the javadoc for class com.ibm.websphere.scheduler.UserCalendar for details.

SCHD0118E: Unable to acquire lock for {0}.
Explanation: The Scheduler uses synchronization locks to maintain consistency. The thread waiting for the lock either timed-out or was interrupted.
User Response: Try running the operation again. If the application server is shutting down at the time of the error, then no action is necessary.

SCHD0119E: Invalid numeric value specified: {0}.
Explanation: The specified value is not numeric.
User Response: Correct the method or object call to specify a number.

SCHD0120E: Invalid term detected: {0}.
Explanation: The SIMPLE calendar interval string supports the following terms: seconds, minutes, hours, days, weeks, months and years. An incorrect term was specified.
User Response: Correct the SIMPLE calendar interval string to use the correct terms. See the javadoc for class com.ibm.websphere.scheduler.UserCalendar for details.

SCHD0121E: The LeaseManager database is not correctly configured.
Explanation: The LeaseManager tables are missing or the database is inaccessible.
User Response: Create the missing LeaseManager tables using the instructions in the Scheduler InfoCenter and verify that the Scheduler can communicate correctly with the database. The Scheduler will continue to function without the LeaseManager tables, but performance will be decreased when using redundant or clustered Schedulers.

SCHD0122E: The {0} attribute must also be specified if the {1} is set while creating a {2}.
Explanation: A dependent attribute was not set or was null.
User Response: Set the attribute and retry the operation.

SCHD0123E: The {0} field or attribute is invalid. Valid values include: {1}
Explanation: The specified field or attribute is not valid.
User Response: Correct the field or attribute value with a value in the proper format or range.

SCHD0124E: Unable to initialize {0} due to error: {1}
Explanation: The specified object could not be initialized.
User Response: Review the error, solve the problem and retry the operation.

SCHD0125E: Unexpected exception while processing the {0} operation: {1}
Explanation: An unexpected exception occurred while processing the specified operation.
User Response: Review the error, solve the problem and retry the operation.

SCHD0126E: The scheduler service singleton has not been set.
Explanation: The instance API method was called before the scheduler service was initialized.
User Response: Check the startup time values specified for the component.

SCHD0127E: Access Denied. A task cannot be modified from a different application than it was created with.
Explanation: An application attempted to modify or change a task created by another application.
User Response: Check the task ID and verify that the correct application is being used to access that task, or use the WASScheduler JMX MBean to administer the task.

SCHD0128E: The daemon for scheduler {0} could not be started: {1}
Explanation: An unexpected error occurred. See the FFDC logs and the associated exception for details.
User Response: See the server log files for detailed exception data.

SCHD0129E: The {0} MBean for for scheduler {1} could not be started: {2}
Explanation: An unexpected error occurred while starting the specified MBean.
User Response: Review the error, solve the problem and retry the operation.

SCHD0130W: Failed to {0} the scheduler tables because of an error: {1}
Explanation: The scheduler tables cannot be created, dropped or verified because of the specified error.
User Response: Resolve the error and try the operation again or use the supplied SQL or DDL files to create or drop your tables. See the information center for details.

SCHD0300E: Error during Database operation, localized message is {0}, Vendor Error Code is {1}, ANSI-92 SQLState is {2}, cause: {3}
Explanation: A database operation threw an SQLException.
User Response: Review the cause or chained SQLException and documentation for the database or database driver throwing the exception to resolve the problem.

SCHD0301E: The lease for resource {0} does not exist. Operation: {1} was unable to complete.
Explanation: The lease for the specified resource does not exist. Operations on a lease are only available when the lease has been acquired.
User Response: Attempt to acquire a lease before running the operation.

SCHD0302E: The lease owner: {0} is not the current owner of the lease for resource {1}. Operation: {2} was unable to complete.
Explanation: The lease has not been acquired. Operations on a lease are only available when the lease has been acquired.
User Response: Attempt to acquire a lease before running the operation.

SCHD0303E: The database connection required for operation: {0} and resource: {1} is stale.
Explanation: The operation could not complete because the database connection is stale.
User Response: Examine database logs and other messages to determine if there is a configuration problem and retry the operation.

SCHD0304E: No database connections could be obtained in the required time for operation: {0} and resource: {1}.
Explanation: A connection to the database could not be obtained before the connection manager timed-out.
User Response: Increase the number of connections or continue to retry the operation until a connection can be retrieved.

SCHD0305E: The lease for component {0} was cancelled. No Other operations are permitted until the lease is reaquired.
Explanation: The lease has been cancelled. Operations on a lease are only available when the lease has been acquired.
User Response: Attempt to acquire a lease before running the operation.

SCHD0306E: The lease for component {0} has expired. No other operations are permitted until the lease is reaquired.
Explanation: The component has lost the lease because it has expired. Operations on a lease are only available when the lease has been acquired.
User Response: Attempt to acquire a lease before running the operation. If the lease is already acquired by another owner, then the lease can only be forcibly acquired.

SCHD0307E: The lease for resource {0} is disabled.
Explanation: The lease has been disabled. Operations on a lease are only available when the lease has been acquired.
User Response: The lease must be enabled prior before the lease can be acquired or renewed.

SCHD0308E: No chained exception available
Explanation: A message with a chained exception was generated, but there was no chained exception.
User Response: Review the message details and stack trace for the root exception.