commands – job enable/disable/bypass
Enable/disable/bypass a job.
Usage
job (enable|disable|bypass) name
where
| enable | job. Enabled jobs are executed according their schedules and/or conditions. |
| disable | job. Disabled cannot be executed, and any conditions which reference them will always return false. |
| bypass | job. Bypassed are not executed, and always have a job result of success. Any conditions which reference them will return true, if they expect a success result. |
| name | of job to enable, disable or bypass. |
execute on name
in order to enable a job, it must be completely defined and ready to execute/schedule.
this value can be overridden by the system job-mode property.
Examples
Enable a job
BeyondCron % job enable /examples/server/backup
BeyondCron % job list $$
Job Type Mode Description -------------- ------- ------- ------------------- /examples/server/backup Command Enabled Business day backup
Disable a job
BeyondCron % job disable /examples/server/backup
BeyondCron % job list $$
Job Type Mode Description ----------------------- ------- -------- ------------------- /examples/server/backup Command Disabled Business day backup
Bypass a job
BeyondCron % job bypass /examples/server/backup
BeyondCron % job list $$
Job Type Mode Description ----------------------- ------- ------ ------------------- /examples/server/backup Command Bypass Business day backup
Attempt enable an incompletely defined job
BeyondCron % job enable /examples/server/reboot
Job has no start action
See also
- job add
- job calendar
- job changes
- job command
- job condition
- job content
- job copy
- job delay
- job delete
- job description
- job diff
- job email
- job history
- job host
- job image
- job input
- job list
- job message
- job output
- job property
- job schedule
- job show
- job sql
- job start/kill
- job status
- job subject
- job timezone
- job trigger
- job url
- job user
- job variables
- system properties