8.5.1 Starting the scheduler service
Use the jajs_spmd or ajsstart command to start only the scheduler service. You can use command options to restrict the execution status of jobnets and jobs when the scheduler service starts.
-
Cold start
Execution registration for all jobnets is forcibly canceled when the scheduler service starts.
If the table structure of the JP1/AJS3 scheduler database has changed, you need to perform a cold start.
-
Warm start
The status when scheduler service was stopped is inherited when the scheduler service starts. However, the status of jobnets and jobs that were in Now running status when the scheduler service stopped changes to an end status.
-
Hot start
The status when scheduler service stopped is inherited when the scheduler service starts. The execution of jobnets and jobs that were in Now running status when the scheduler service stopped continues.
For details about the jajs_spmd command, see jajs_spmd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
To use advanced options, instead of the options above, to start the scheduler service, use the ajsstart command. For details about the ajsstart command, see ajsstart in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
- Cautionary notes
-
-
When cold start is specified, all execution results are disabled because execution information for all jobnets registered for execution is deleted before the scheduler service starts. In addition, you will need to re-register the jobnets after the scheduler service is cold-started.
-
Cold-start processing waits for JP1/AJS3 - View to terminate. If you specify a cold start, make sure that the connection with JP1/AJS3 - View is closed.
-