SCHD0073E=SCHD0073E: The Scheduler implementation class attribute is missing for scheduler {0} ({1}). The scheduler resource will not be created. The scheduler implementation class for the specified scheduler resource is missing. An implementation class is required. Specify a valid scheduler implementation class. SCHD0033I=SCHD0033I: The Scheduler {0} has initialized. The specified Scheduler instance has initialized and is ready to accept requests. No user action is required. SCHD0137E=SCHD0137E: Unable to create EJB instance for {0}: {1} There was an error when attempting to create the specified EJB instance. See the nested exception for details on the cause of the problem. Verify that the EJB, Application, Host and Port are available. If no longer available, cancel or suspend the task. SCHD0136W=SCHD0136W: The lease manager tables are missing for scheduler {0} ({1}) which will reduce performance in a clustered environment. The lease manager tables are required to reduce the contention between redundant or clustered schedulers. If the tables are absent, there will be a large amount of collisions. Use the supplied DDL files to create the lease manager tables or use the createTables operation on the WASSchedulerCfgHelper MBean or administrative console to add the new tables. See the information center for details. SCHD0140I=SCHD0140I: EJB information: Host: {0}, Port: {1}, J2EE component: {2} This message displays information about an EJB's remote destination, which includes the remote host, port and Java Platform, Enterprise Edition component that the EJB is a member of. No user action is required. SCHD0072E=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. The JNDI name of the specifed scheduler resource is the same as the work manager JNDI name attribute. Use the administrative console to modify either the work manager JNDI name in the Work Manager resource or modify the JNDI name of the scheduler resource. SCHD0308E=SCHD0308E: No chained exception available A message with a chained exception was generated, but there was no chained exception. Review the message details and stack trace for the root exception. SCHD0100I=SCHD0100I: Scheduler tables verified successfully. The Scheduler tables were verified in the database. No user action required. SCHD0032I=SCHD0032I: The Scheduler {0} is initializing. The specified Scheduler instance is initializing. No user action is required. SCHD0068E=SCHD0068E: The task failed to execute because an error occurred. See the previous messages for the cause of the error. The scheduler attempted to run the task, but an error occurred preventing the task from running. See the previous messages for the cause of the error. SCHD0135W=SCHD0135W: Value out of range for custom property {0} for scheduler {1} ({2}). Valid values include: {3}. A custom property was set for the specified scheduler, but the value is not valid. This property will be ignored. Update the custom property value to be valid. SCHD0071E=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. The JNDI name of the scheduler resource is the same as the scheduler resource data source JNDI name attribute. Use the administrative console to modify either the data source JNDI name or the JNDI name of the scheduler resource. SCHD0307E=SCHD0307E: The lease for resource {0} is disabled. The lease has been disabled. Operations on a lease are only available when the lease has been acquired. The lease must be enabled prior before the lease can be acquired or renewed. SCHD0031I=SCHD0031I: The Scheduler Service is starting. The Scheduler Service is starting. No user action is required. SCHD0067E=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. An error occurred while calculating the next fire time or the start by interval. The previous message contains the cause of the error. See the previous message for the cause of the error. SCHD0070E=SCHD0070E: The Task Store is not available. The Task Store object for this scheduler is null. See previously listed error messages to determine the cause. SCHD0134I=SCHD0134I: Scheduler {0} ({1}) has lost its lease and will no longer run tasks on this application server. Tasks will now run on server {2}. The scheduler uses a lease to allow clustered scheduler servers to avoid contention. Only one scheduler instance per server may hold the lease at one time. All tasks will run on the scheduler instance who holds the lease. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . SCHD0306E=SCHD0306E: The lease for component {0} has expired. No other operations are permitted until the lease is reaquired. The component has lost the lease because it has expired. Operations on a lease are only available when the lease has been acquired. 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. SCHD0066E=SCHD0066E: The following error occurred in scheduler {0} ({1}) while applying the default User Calendar to the current time: {2}. An error occurred attempting to calculate the next fire time using the default User Calendar. See the message that contains the cause of the error. SCHD0026E=SCHD0026E: Scheduler instance {0} failed to initialize because the following error occurred: {1} The specified scheduler could not be initialized and is unable to poll for scheduled tasks. Verify that the Scheduler resource is configured correctly and that the associated database is active. SCHD0133I=SCHD0133I: Scheduler {0} ({1}) has acquired the lease and will run all tasks on this application server. The scheduler uses a lease to allow clustered scheduler servers to avoid contention. Only one scheduler instance per server may hold the lease at one time. All tasks will run on the scheduler instance who holds the lease. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . SCHEDULER_DISABLED=SCHD0029W: Scheduler service disabled due to previous errors. The Scheduler service experienced an error during initialization. The service is inaccessible on the given server. The root error should have been logged previously. Try to resolve the previously logged errors. If unable to do so, contact IBM support. SCHD0305E=SCHD0305E: The lease for component {0} was cancelled. No Other operations are permitted until the lease is reaquired. The lease has been cancelled. Operations on a lease are only available when the lease has been acquired. Attempt to acquire a lease before running the operation. SCHD0065E=SCHD0065E: The following error occurred while scheduler {0} ({1}) attempted to roll back the transaction: {2}. The scheduler tried to roll back the transaction, but an error occurred. See the message that contains the cause of the error. See the message that contains the cause of the error. SCHD0129E=SCHD0129E: The {0} MBean for for scheduler {1} could not be started: {2} An unexpected error occurred while starting the specified MBean. Review the error, solve the problem and retry the operation. SCHD0132W=SCHD0132W: Task {0} for scheduler {1} ({2}) has exceeded the failure threshold limit and has been deactivated. The scheduled task has failed multiple times consecutively and will no longer run on this application server. Review other related error messages to determine what the problem is. Once the problem is resolve, either suspend and resume the task using the scheduler API methods, or restart this scheduler daemon. SCHD0304E=SCHD0304E: No database connections could be obtained in the required time for operation: {0} and resource: {1}. A connection to the database could not be obtained before the connection manager timed-out. Increase the number of connections or continue to retry the operation until a connection can be retrieved. SCHD0064E=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}. 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. See the message that contains the cause of the error. SCHD0128E=SCHD0128E: The daemon for scheduler {0} could not be started: {1} An unexpected error occurred. See the FFDC logs and the associated exception for details. See the server log files for detailed exception data. SCHD0131W=SCHD0131W: Task {0} on thread {1} for scheduler {2} ({3}) has been running for {4} milliseconds and may be hung. The scheduled task has been running for a long period of time. If this behavior is by design, then no further action is necessary. When the thread completes, a WSVR0606W message is logged. If the task is running longer than expected, then the task and thread should be examined to determine if is running properly. If the task is hung, the thread should be interrupted or the application server ended and the task should be suspended or cancelled until the problem can be resolved. SCHD0059W=SCHD0059W: The task information for task ID {0} for scheduler {1} ({2}) cannot be removed from the database because the task does not exist or the task information has already been removed by another Scheduler. The task with the specified task ID cannot be removed from the database because it does not exist. No user action is required. SCHD0303E=SCHD0303E: The database connection required for operation: {0} and resource: {1} is stale. The operation could not complete because the database connection is stale. Examine database logs and other messages to determine if there is a configuration problem and retry the operation. SCHD0099E=SCHD0099E: Exception occurred while deserializing object {0}: {1} An unexpected error occurred. See the FFDC logs and the associated exception for details. See the server log files for detailed exception data. SCHD0063E=SCHD0063E: A task with ID {0} failed to run on Scheduler {1} ({2}) because of an exception: {3}. 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. See the message that contains the cause of the error. The task will continue to run until the problem is resolved or the task is cancelled. SCHD0127E=SCHD0127E: Access Denied. A task cannot be modified from a different application than it was created with. An application attempted to modify or change a task created by another application. 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. SCHD0130W=SCHD0130W: Failed to {0} the scheduler tables because of an error: {1} The scheduler tables cannot be created, dropped or verified because of the specified error. 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. SCHD0019E=SCHD0019E: Data source with JNDI name {0} could not be found. A data source was specified on a Scheduler resource, however the data source with the specified JNDI name is not present. 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. SCHD0058W=SCHD0058W: The task information for task ID {0} for scheduler {1} ({2}) cannot be updated in the database because the task record is lock by another process. 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. No user action is required. SCHD0302E=SCHD0302E: The lease owner: {0} is not the current owner of the lease for resource {1}. Operation: {2} was unable to complete. The lease has not been acquired. Operations on a lease are only available when the lease has been acquired. Attempt to acquire a lease before running the operation. SCHD0098E=SCHD0098E: Could not determine the task operation for method {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . SCHD0062E=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. The Scheduler is attempting to run 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 the Application Server and then run on an earlier version of the Application Server. Make sure the version of the Application Server product is at the same or later version than the version of the Application Server that created the task. SCHD0126E=SCHD0126E: The scheduler service singleton has not been set. The instance API method was called before the scheduler service was initialized. Check the startup time values specified for the component. SCHD0018E=SCHD0018E: Work Manager with JNDI name {0} could not be found. A WorkManager was specified on a Scheduler resource, however, the WorkManager with the specified JNDI name is not present. 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. SCHD0057W=SCHD0057W: The task information for task ID {0} for scheduler {1} ({2}) 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. The task with the specified task ID cannot be updated in the database because it was already updated. No user action required. ERR_MISSING_KEY=SCHD0027E: Message key {0} was not found in any searched resource bundles. 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. Determine why the message catalog could not be found. ERR_NO_SERVICE=SCHD0030E: Scheduler service could not resolve the {0} service. 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. 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. SCHD0301E=SCHD0301E: The lease for resource {0} does not exist. Operation: {1} was unable to complete. The lease for the specified resource does not exist. Operations on a lease are only available when the lease has been acquired. Attempt to acquire a lease before running the operation. SCHD0097E=SCHD0097E: The task operation {0} is not supported by task type {1}. The supplier of the specified task type has indicated that the specified task operation is not allowed. Change your application so it does not call the specified operation. SCHD0061E=SCHD0061E: The task information for task ID {0} and owner token {1} was not found in the database. The task with the specified task ID and owner token is not in the database. Specify another task ID and try the request again. SCHD0021I=SCHD0021I: Exception trace information follows: {0}. An unexpected exception has occurred. Check for other messages that contain exceptions further in the log. SCHD0125E=SCHD0125E: Unexpected exception while processing the {0} operation: {1} An unexpected exception occurred while processing the specified operation. Review the error, solve the problem and retry the operation. SCHD0060W=SCHD0060W: The task information for task ID {0} for scheduler {1} ({2}) cannot be removed from the database because the task record is locked by another process. 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. No user action is required. SCHD0017E=SCHD0017E: The {0} attribute must be specified when creating a {1}. When creating or scheduling objects, this attribute is required. Provide the missing attribute and try again. SCHD0056W=SCHD0056W: The task information for task ID {0} for scheduler {1} ({2}) cannot be inserted into the database because the task already exists. 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. No user action is required. SCHD0300E=SCHD0300E: Error during Database operation, localized message is {0}, Vendor Error Code is {1}, ANSI-92 SQLState is {2}, cause: {3} A database operation threw an SQLException. Review the cause or chained SQLException and documentation for the database or database driver throwing the exception to resolve the problem. SCHD0096E=SCHD0096E: The current user is not in the appropriate role to use the {0} method. The current user is not in a role that has authority to run 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. 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 administrative console. Please see the information center for more information. SCHD0020I=SCHD0020I: Invalid scheduler configuration: {0}. The specified configuration information is not valid or missing. Verify that the configuration attributes for the Scheduler resource are present and valid. Use the administrative console to verify the Scheduler resource. SCHD0124E=SCHD0124E: Unable to initialize {0} due to error: {1} The specified object could not be initialized. Review the error, solve the problem and retry the operation. SCHD0095E=SCHD0095E: The SQL statement for statement key {0} cannot be found for table key {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . SCHD0123E=SCHD0123E: The {0} field or attribute is invalid. Valid values include: {1} The specified field or attribute is not valid. Correct the field or attribute value with a value in the proper format or range. SCHD0055E=SCHD0055E: The NotificationSink object for task ID {0} for scheduler {1} ({2}) cannot be retreived because the following error occurred: {3}. 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. See the user action for the message that contains the cause of the error. SCHD0119E=SCHD0119E: Invalid numeric value specified: {0}. The specified value is not numeric. Correct the method or object call to specify a number. SCHD0094E=SCHD0094E: End index of {0} is smaller than beginning index of {1}. The specified end index value is less than the specified beginning index value. Modify the index values so the beginning index is smaller than the end index and submit the request again. SCHD0122E=SCHD0122E: The {0} attribute must also be specified if the {1} is set while creating a {2}. A dependent attribute was not set or was null. Set the attribute and retry the operation. SCHD0054E=SCHD0054E: TaskInfo object {0} could not be created because the following error occurred: {1}. The TaskInfo object could not be created because an error occurred. See the user action for the message that contains the cause of the error. SCHD0118E=SCHD0118E: Unable to acquire lock for {0}. The Scheduler uses synchronization locks to maintain consistency. The thread waiting for the lock either timed-out or was interrupted. Try running the operation again. If the application server is shutting down at the time of the error, then no action is necessary. SCHD0014E=SCHD0014E: An error occured while publishing a notification: {0} The Notification Sink session bean specified by this task could not be contacted. Verify that the session bean is available. SCHD0093E=SCHD0093E: End index of {0} cannot be negative. The specified end index value is less than 0. Modify the end index value so it is equal or greater than 0 and submit the request again. SCHEDULER_CANNOT_BE_DISABLED=SCHD0028I: Scheduler service cannot be disabled. The Scheduler service has been disabled in the configuration, but will continue to run because because of service dependencies. Re-enable the scheduler service in the configuration to avoid receiving this message in the future. SCHD0089I=SCHD0089I: Table {0} cannot be dropped because it does not exist in the database. The specified table cannot be dropped because it does not exist in the database. No user action required. SCHD0121E=SCHD0121E: The LeaseManager database is not correctly configured. The LeaseManager tables are missing or the database is inaccessible. Create the missing LeaseManager tables using the instructions found under the Scheduler topic in the information center 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. SCHD0053E=SCHD0053E: The task (taskId={0}) cannot be suspended because it has been cancelled or is already completed. The specified task has already run or has been canceled and cannot be suspended. No user action is required. SCHD0117E=SCHD0117E: Unexpected tokens detected for term: {0}. The specified CRON calendar interval string term is formatted incorrectly and has too many tokens. Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. SCHD0049E=SCHD0049E: The start-by time must be greater than the start time for non-repeating tasks. Creating a new task using a start-by time less than the start time for a non-repeating task is not a valid operation. Modify the StartByTime, the StartTime, StartTimeInterval, or the NumberOfRepeats and submit the request again. SCHD0013E=SCHD0013E: The following error occurred while accessing the UserCalendar with JNDI Name {0} and specifier {1} : {2}. The UserCalendar session bean specified by this task could not be contacted. Verify that the session bean is available. SCHD0009I=SCHD0009I: The Scheduler Service is not enabled. A scheduler instance cannot be used on this server while the scheduler service is disabled. See the documentation found under the Scheduler topic in the information center about enabling the Scheduler service. SCHD0092E=SCHD0092E: Beginning index of {0} cannot be negative. The specified beginning index value is less than 0. Modify the beginning index value so it is equal or greater than 0 and submit the request again. SCHD0088I=SCHD0088I: Index {0} created successfully. The specified index was created in the database. No user action required. SCHD0120E=SCHD0120E: Invalid term detected: {0}. The SIMPLE calendar interval string supports the following terms: seconds, minutes, hours, days, weeks, months and years. An incorrect term was specified. Correct the SIMPLE calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. SCHD0052E=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. 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. Allow the task to run before purging or cancel the task first and then submit the purge request again. SCHD0116E=SCHD0116E: Invalid range format string specified: {0}. Valid range format is: <low>-<high> The CRON calendar interval string allows terms with range values. The specified range is not of the correct syntax. Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. SCHD0048E=SCHD0048E: The task attribute NumberOfRepeats must be non-zero number. The NumberOfRepeats attribute must not be zero. Set the NumberOfRepeats attribute to a value other than zero and submit the request again. SCHD0091E=SCHD0091E: Beginning index of {0} is larger than the end index of {1}. The specified beginning index value is larger than the specified end index value. Modify the index values so the beginning index is smaller than the end index and submit the request again. SCHD0087I=SCHD0087I: Scheduler tables created successfully. The Scheduler tables were created in the database. No user action required. SCHD0051E=SCHD0051E: The task (taskId={0}) has been cancelled or is complete. Cancelled or completed tasks cannot be resumed. The specified task has already run or has been cancelled and cannot be resumed. No user action required. SCHD0115E=SCHD0115E: Unable to parse CRON term {0}: {1}. The specified CRON calendar interval string has an incorrect term at the specified position. Positions are from 1 to 6. Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. SCHD0047E=SCHD0047E: The TaskInfo class {0} must have a registered implementation. The specified TaskInfo class type cannot be used because it is not of a registered type. Modify the application to use a TaskInfo class that has a registered implementation and submit the create request again. SCHD0007E=SCHD0007E: Error while accessing the persistent store: {0}. The data store used by this scheduler instance could not be reached. See the server log files for detailed exception data. SCHD0090I=SCHD0090I: Scheduler tables dropped successfully. The Scheduler tables were dropped from the database. No user action required. SCHD0086I=SCHD0086I: Table {0} cannot be created because it already exists in the database. The specified table already exists in the database. No user action required. SCHD0050E=SCHD0050E: The task attribute InitialState has an invalid value of {0}. Valid values are TaskStatus.SCHEDULED ({1}) and TaskStatus.SUSPENDED ({2}). The specified InitialState value is not valid at this time. The valid values are SCHEDULED or SUSPENDED. Set the InitialState value to either SCHEDULED or SUSPENDED and submit the request again. SCHD0114E=SCHD0114E: Invalid repeat value of {0} for term {1}. The value must be between 1 and {2}. 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. Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. SCHD0046E=SCHD0046E: The table {0} in datasource {1} used by scheduler resource {2} ({3}) is missing or is not accessible. The specified table cannot be found in the configured database for the specified scheduler resource. The possible causes are: An incorrect data source JNDI name has been configured, an incorrect table prefix has been configured, or the scheduler tables have not been created in the database. Use the administrative 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 information center. SCHD0085E=SCHD0085E: Unable to find datasource JNDI name {0}. The following configuration files were searched: {1}. The Scheduler was unable to find the data source for the specified JNDI name in the message. Verify that the specified data source 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 information center for more information about creating data sources and modifying scheduler configurations. SCHD0113E=SCHD0113E: Term value '?' is invalid for the specified term. The '?' token is only valid for terms DayOfMonth or DayOfWeek. The CRON calendar interval string requires that either the DayOfMonth or DayOfWeek is specified, but not both. Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. SCHD0045E=SCHD0045E: An exception occurred retrieving the Data source Alias configuration information for scheduler resource {0}. An exception occurred while retrieving the authentication alias for the data source configuration information. Use the administrative console to verify the authentication alias for the data source is configured correctly. SCHD0084W=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. The Scheduler attempted to find the lease manager tables and they are missing. The lease manager tables must reside in the specified data source and have names that begin with the configured table prefix and end with "LMGR" and "LMPR". See the information center for information on creating scheduler tables. SCHD0109E=SCHD0109E: Invalid value detected. The value for field {0} must be a valid non-null value. The specified field or argument must not be null. Change the method or object call to set the appropriate argument or verify that the field value is properly set. SCHD0044W=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. 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. Use the administrative console to configure the poll interval value for the specified scheduler resource. SCHD0112E=SCHD0112E: The DayOfMonth or DayOfWeek term must be specified, but not both. The CRON calendar interval string requires that either the DayOfMonth or DayOfWeek is specified, but not both. Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. SCHD0108E=SCHD0108E: Unable to de-serialize a home handle due to error: {0} The Scheduler is attempting to read a HomeHandle object from an input stream, but the Home is unavailable. 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. SCHD0083E=SCHD0083E: Unable to find the scheduler configuration for resource URI {0}. The Scheduler attempted to find the configuration described in the message but could not locate it. Correct the URI and try your request again. SCHD0111E=SCHD0111E: Incorrect number of terms specified. The CRON calendar interval string requires 6 terms: second minute HourOfDay DayOfMonth Month DayOfWeek Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. SCHD0079E=SCHD0079E: The Scheduler {0} ({1}) was unable to reschedule failed task {2} due to an unexpected error: {3}. The Scheduler attempted to re-run a task that previously failed due to an error. See previous messages and the included exception for further information. Once the error is resolved, the Scheduler will attempt to re-run the failed task. SCHD0043E=SCHD0043E: The JNDI name for scheduler resource {0} is missing. The scheduler resource is not created. A scheduler resource requires a JNDI name, however, the JNDI name in the configuration information for the specified scheduler resource is blank or null. Use the administrative console to configure a JNDI name for the specified scheduler resource. SCHD0039I=SCHD0039I: The Scheduler Daemon for instance {0} has been stopped. The Scheduler Service has stopped for the specified Scheduler instance. No user action is required. SCHD0107E=SCHD0107E: A byte array read field {0} with an unexpected type of {1}. The Scheduler is attempting to read an object from an input stream, but the object's type number was unexpected. 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. SCHD0003E=SCHD0003E: An error occured while starting the scheduler service: {0}. An unexpected error occurred. See the FFDC logs and the associated exception for details. See the server log files for detailed exception data. SCHD0082E=SCHD0082E: Unable to determine the configuration location for resource URI {0}. The URI resolved to object name {1} with location properties {2}. 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. Correct the URI and try your request again. SCHD0078I=SCHD0078I: The Scheduler Service has completed starting the Schedulers. The Scheduler Service has initialized and has started each configured Scheduler instance. No user action required. SCHD0110E=SCHD0110E: The DayOfWeek term must be between 1 and 7. The DayOfWeek term for the CRON calendar interval string is not in the correct range. Update the DayOfWeek term in the calendar interval string to use a number between 1 and 7. SCHD0042E=SCHD0042E: The Work Manager JNDI name for scheduler resource {0} ({1}) is missing. The scheduler resource is not created. 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. Use the administrative 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. SCHD0038I=SCHD0038I: The Scheduler Daemon for instance {0} has started. The Scheduler Daemon has started for the specified Scheduler instance. No user action is required. SCHD0002I=SCHD0002I: The Scheduler Service has stopped. The Scheduler Service has stopped and is no longer scheduling tasks. No user action is required. SCHD0106E=SCHD0106E: A byte array expected field with id {0} but read id {1}. The Scheduler is attempting to read an object from an input stream, but a field is incorrect or out of order. 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. SCHD0081E=SCHD0081E: The Scheduler was unable to create the task handler EJB home for JNDI name {0} due to an unexpected error: {1}. The Scheduler attempted to create an instance of the defined task hander EJB home, but failed to do so because of an unexcepted error. See the message that contains the cause of the error. The server log files may contain additional failure details. SCHD0077I=SCHD0077I: The Scheduler Service is starting the Schedulers. The Scheduler Service has initialized and is starting each configured Scheduler instance. No user action required. SCHD0041E=SCHD0041E: The Data source JNDI Name attribute for scheduler resource {0} ({1})is missing. The scheduler resource is not created. A scheduler resource requires a data source JNDI name, however the data source JNDI Name attribute in the configuration information for the specified scheduler resource is blank or null. Use the administrative console to configure a data source JNDI name for the specified scheduler resource. SCHD0037I=SCHD0037I: The Scheduler Service has been initialized. The Scheduler Service has been initialized. No user action is required. SCHD0001I=SCHD0001I: The Scheduler Service has started. The Scheduler Service is started. No user action is required. SCHD0105E=SCHD0105E: A byte array expected field {0} with version {1} but read version {2}. The Scheduler is attempting to read an object from an input stream, but the object's version number was unexpected. 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. SCHD0080E=SCHD0080E: The Scheduler was unable to create the task handler EJB home object due to an unexpected error: {0}. The Scheduler attempted to create an instance of the defined task hander EJB home, but failed to do so because of an unexcepted error. See previous messages and the included exception for further information. Once the error is resolved, the Scheduler will attempt to re-run the failed task. SCHD0040I=SCHD0040I: The Scheduler Service is stopping. The Scheduler Service is stopping. No user action is required. SCHD0076E=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} An unexpected error occurred while the specified scheduler resource was firing the specified notification event for the specified task. See the message that contains the cause of the error. The server log files may contain additional failure details. SCHD0036I=SCHD0036I: The Scheduler Service is initializing. The Scheduler Service is initialized. No user action is required. SCHD0104E=SCHD0104E: The Scheduler poll daemon {0} ({1}) failed to load tasks from the database due to an exception: {2} 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. Review the error and resolve the problem. The daemon will continue to attempt to poll the database. SCHD0103W=SCHD0103W: The Scheduler {0} ({1}) was unable to run task {2} because the application or module is unavailable: {3}. The Scheduler is attempting to run a task, but the application or module that the task was created with is not available. Start or install the application, module or component. SCHD0075E=SCHD0075E: The following error occurred in scheduler resource {0} ({1}) while cancelling task for task id {2}: {3} An unexpected error occurred while the specified scheduler resource was cancelling the specified task. See the message that contains the cause of the error. The server log files may contain additional failure details. SCHD0035I=SCHD0035I: The Scheduler {0} has stopped. The specified Scheduler instance and daemon have stopped. No user action is required. SCHD0139E=SCHD0139E: Unable to invoke the {0} EJB: {1} There was an error when attempting to invoke a method using the specified EJB. See the nested exception for details on the cause of the problem. Review the details from the nested exception stack to determine the cause of the error. SCHD0074E=SCHD0074E: The Scheduler {0} ({1}) was not able to acquire a read lock for the AsynchScope because the following error occurred: {2} An error occurred which prevented the specified scheduler from acquiring a read lock for the AsynchScope. See the message that contains the cause of the error. SCHD0102I=SCHD0102I: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . SCHD0034I=SCHD0034I: The Scheduler {0} is stopping. The specified Scheduler instance and daemon are stopping. No user action is required. SCHD0138E=SCHD0138E: Unable to retrieve {0} from a javax.ejb.HomeHandle. There was an error when attempting to retrieve the EJBHome instance from a HomeHandle. See the nested exception for details on the cause of the problem. Verify that the EJB and Application are available. If no longer available, cancel or suspend the task. SCHD0069W=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}. Another scheduler ran or updated the task prior to this scheduler updating or running the task. The task was run or updated by another scheduler. This can occur when the two or more schedulers compete for the same tasks. See the information center for information on reducing task collisions.