Schedulers can be created or configured using the administrative
console.
Procedure
- Start the administrative console.
- Select Resources > Schedulers.
- Click New.
- Specify configuration settings.
Fields marked
with an asterisk (*) are required. The settings are described in detail
in the topic "Scheduler settings".
![[z/OS]](../../images/ngzos.gif)
If you do not want the scheduler to attempt to run
any work until the WebSphere Application Server for z/OS server is
open for e-business, click Custom Properties > New to
add the synchWithControlRegion custom property
to the scheduler configuration settings, and set the property to true.
When this property is set to true the Scheduler waits until the WebSphere
Application Server for z/OS server is open for e-business before attempting
to run any work. The default value is false.
Best practice: If you do not require interoperability
with PME Version 5.0 tasks, under Additional Properties, click
Custom
Properties > New. Then specify
disableV50TaskInteroperability in
the
Name field,
true in
the
Value field, and select
java.lang.boolean from
the list of available Type options. When this property is set to
true,
tablespace scans that are only required for PME Version 5.0 tasks
no longer occur.
bprac
- Click OK or Apply to save the changes.
- Save the changes to the configuration repository.
Results
A scheduler is now configured and ready to use for newly
installed applications. If the scheduler JNDI name is not yet visible
to your application, restarting the application or restarting application
server will allow the scheduler to be seen.
When schedulers
are created for the first time, the poll daemon will not automatically
start and must be started manually and will only start automatically
the next time the server is started. To start the poll daemon manually,
refer to the scheduler daemons topic.
Attention: Changes
to existing scheduler configurations will not take affect until after
the application server is restarted.