Synopsis
jobschctljob [project name/] job net name/job name control [-sys subsystem-number](*1)
[-sys subsystem-number] is the option of Systemwalker Operation Manager EE.
Description
The jobschctljob command controls (cancel/rerun/pause/continue/disable/enable) jobs.
Options
project name
Specifies the project name where the jobs to be controlled are stored. If there is only one project having jobs registered among the projects accessible for operation by the user of executing the jobschctljob command, this option can be omitted.
job net name
Specifies the job net name where the jobs to be controlled are stored.
job name
Specifies the job name to be controlled.
control
Specify one of the following six control items:
For information about the relationship between the status and operations of the jobs being controlled, and the relationship between the status and operations of the parent job net, refer to the "Operating Scheduled Jobs" in the Systemwalker Operation Manager Operetion Guide.
Cancels the job.
Restarts the job that was canceled or terminated abnormally.
Pauses the job.
Cancels the paused status of the job.
Disables the job.
Enables the disabled job.
-sys subsystem-number
In the system with multiple subsystems, this option is used to specify the subsystem that you want to operate. Specify the target subsystem number using a range of 0 to 9. If omitted, the default is subsystem 0.
Command Location
Windows | Systemwalker Operation Manager installation directory\MpWalker.JM\bin |
Solaris | /usr/bin |
Cautions
Controlling jobs is only available for the jobs that belong to the job net with "Job Execution Control" attribute or "PowerAIM" ([UNIX]) attribute.
When controlling the job, the job name must be specified and if the job name is omitted, the job cannot be controlled.
Child job nets cannot be controlled.
Linked job nets cannot be controlled.
If there are multiple jobs with the same job name specified within the job net, this command fails.
This command simply requests the server to operate on the job, and so the fact that the command has finished executing does not guarantee that job operation on the server has completed. For this reason, after this command has finished executing, check the status of the job by entering the "jobschprint -p" command.
