ajsstart
- Organization of this page
Format
ajsstart [-c|-o|-t] [-F service-name] [-s {none|EXEC}] [-w] [-R] [-D]
Description
Starts the scheduler service for JP1/AJS3 and executes any jobnet registered for execution.
Execution privileges
In Windows: Administrators privilege
In UNIX: Superuser privilege
Arguments
-c
Forcibly cancels the execution registration of all jobnets and starts ("cold-starts") the scheduler service.
The following situations require a cold start:
-
When the database table structure in the JP1/AJS3 scheduler has been modified
-
When you cannot start a scheduler service
When you cold-start a scheduler service, you must re-register the jobnet for execution after the scheduler service is started.
Cold-starting a scheduler service deletes all execution results for all the previous generations for all jobnets. We recommend that you store any necessary log information before attempting to perform cold start.
You cannot specify this option together with the -R or -D option.
If none of the -c, -R, and -D options are specified, the scheduler service is started in warm-start mode.
-o
Does not execute a jobnet which is scheduled to execute on the day when you start the scheduler service, if its scheduled time for starting execution is prior to the time when you start the scheduler service.
If you omit this option, the system automatically executes a jobnet when you start the scheduler service, even if its scheduled time for starting execution is prior to the time when you start the scheduler service.
If you specify this option together with the -R option, this option is disabled.
-t
Does not execute a jobnet scheduled for planned execution or fixed execution for the day.
If you specify this option together with the -R option, this option is disabled.
-F service-name
Specify the name of the target scheduler service.
You can specify a character string of 1 to 30 bytes.
If you omit this option, the system assumes the default scheduler service name.
-s{none|EXEC}
Specify whether you want to suppress the execution of a jobnet or job, or cancel suppression.
-
none
Cancels the suppression of execution for a jobnet or job.
-
EXEC
Suppresses the execution of a jobnet or job. Once the system has completed the execution of the jobnet or job currently being executed, it will not start any subsequent jobnet or job.
-w
Terminates the command once the scheduler service is started.
-R
Continues the execution of any jobnet or job which was running when the scheduler service was previously stopped. (A hot start is performed.)
- Jobnet
-
Continues execution with the status when the scheduler service was stopped.
This option also executes any jobnet that has passed the scheduled start time after the scheduler service is started.
- Job
-
Obtains the job status when the scheduler service was stopped, and continues execution with that status.
You cannot specify this option together with the -c or -D option.
If none of the -c, -R, and -D options are specified, the scheduler service is started in warm-start mode.
-D
Starts the scheduler service in disaster recovery mode. For details on disaster recovery mode, see 6.2.1 Temporarily changing the start mode of JP1/AJS3 in the JP1/Automatic Job Management System 3 Administration Guide.
You cannot specify this option with the -c, -R, or -s option.
If none of the -c, -R, and -D options are specified, the scheduler service is started in warm-start mode.
Notes
-
Before executing this command, you must start JP1/AJS3.
For UNIX, use the jajs_spmd command to start the JP1/AJS3 process.
For Windows, use the Service dialog box or the Service window to start the JP1/AJS3 service.
-
If you move the system date or time backward, cold-start the entire JP1/AJS3 system.
-
If you use the ajslocaldate command to change the local date and time of a scheduler service, cold-start the scheduler service.
-
This command terminates abnormally if a scheduler service is already started.
-
If none of the -c, -R, and -D options are specified, the scheduler service is started in warm-start mode.
-
When you have to cold start a scheduler service if a failure occurs, we recommend that you collect necessary log information beforehand. For how to collect log information, see 1.3 Data to be collected when a problem occurs in the manual JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/Automatic Job Management System 3 Troubleshooting.
-
The scheduler service will not start if the environment settings# are invalid.
- #
-
The environment settings for the scheduler service.
-
If you want to cold start the scheduler service which uses the ISAM database, ensure that no process is accessing the database (you have not used any JP1/AJS3 command after logging off JP1/AJS3 - View) before attempting the cold start. If any process is accessing the database, the system fails to erase registered information so that it cannot start the service, resulting in abnormal end with the KAVS0218-E The database is still being accessed, so the cold start of the scheduler service (scheduler-service-name) ended abnormally. error message output to the Windows event log or Syslog.
-
If you perform a hot start with the -R option specified or a warm start for the scheduler service and cannot acquire the status of a job, the job might have been placed in Unknown end status and then terminated. For details about the conditions when the job status cannot be acquired, see the Job (Unix job, PC job, flexible job, HTTP connection job, action job, custom job) column in Table 6-3 Jobnet and job statuses when a hot-start is performed (-hot) or Table 6-4 Jobnet and job statuses when a warm-start is performed (-warm) in 6.2.1(3) Jobnet and job statuses for each start mode in the JP1/Automatic Job Management System 3 Administration Guide.
-
When you use this command to start the scheduler service, the value of the OVERSCHEDULE environment setting parameter has no effect. Instead, execution follows ajsstart command operation. The following table shows the relationship between the OVERSCHEDULE environment setting parameter and the ajsstart command options.
Table 3‒25: Relationship between the OVERSCHEDULE environment setting parameter and ajsstart command options OVERSCHEDULE setting
ajsstart command options
The OVERSCHEDULE environment setting parameter is set to exec.
The -t and -o options are not specified.
The OVERSCHEDULE environment setting parameter is set to skip.
The -o option is specified.
The OVERSCHEDULE environment setting parameter is set to plan.
The -t option is specified.
-
You cannot execute this command together with any of the following commands on the same logical host:
ajsprofalter command
ajsembdbstart command
ajsembdbstop command
jajs_hstd command
jajs_hstd_stop command
jajs_spmd command (if the -n value is not jajs_schd)
jajs_spmd_status command
jajs_spmd_stop command (if the -n value is not jajs_schd)
jajs_start command (UNIX only)
jajs_start.cluster command (UNIX only)
jajs_stop command (UNIX only)
jajs_stop.cluster command (UNIX only)
-
You cannot execute this command together with any of the following commands if the same scheduler service is specified:
ajsstart command
ajsstop command
jajs_spmd command (if the -n value is jajs_schd)
jajs_spmd_stop command (if the -n value is jajs_schd)
Return values
0 |
Normal end |
Multiple of 4 within the range from 4 to 124 |
Abnormal end |
Example 1
The following command cold-starts a scheduler service AJSROOT1:
ajsstart -F AJSROOT1 -c
Example 2
The following command warm-starts a scheduler service AJSROOT1:
ajsstart -F AJSROOT1
Example 3
The following command hot-starts a scheduler service AJSROOT1:
ajsstart -F AJSROOT1 -R
Example 4
The following command disaster-recovery-starts a scheduler service AJSROOT1:
ajsstart -F AJSROOT1 -D