WORK IN PROGRESS
Scheduler Menu (menu button in the top of JOC)
...WORK IN PROGRESS
Job Menu
For each job in the Jobs tab you can call a menu of some functions
- via right click in the left tree view of the jobs.
- via the Job menu button in the left list view of the jobs.
- via the Job menu button in the right detail view of a job which you get when you have click on a job.
These functions areshow log
It shows the job log in a new window viahttp://<scheduler host>:<scheduler port>/show_log?joh1. <jobname>
show configuration
It shows the job configuration in a new window.
This function is only active for jobs which has its configuration in the ./config/live/ folder.
If the job is configured directly in the ./config/scheduler.xml then this function is inactive.
Underlying command: <http://www.sos-berlin.com/doc/en/scheduler.doc/xml/show_job.xml show_job job="jobname" what="source"/>
show description
If the job has a description in its configuration then this function is active and shows it in a new window.
show dependencies
...WORK IN PROGRESS
show start times
...WORK IN PROGRESS
start task immediately
Hereby you start a task of a (standalone) job immediately independent if the job is _stop_ped or not.
This function is inactive for order jobs. Order jobs can only be started by an order.
Underlying command: <http://www.sos-berlin.com/doc/en/scheduler.doc/xml/start_job.xml start_job job="jobname"/>
start task after
Here you get a dialog for a later job start. You can enter a start time in ISO format "yyyy-mm-dd HH:MMSS" or "now".
The run time of the job is deactivated.
Relative times - "now + HH:MMSS" and "now + SECONDS" - are allowed.
Underlying command: <http://www.sos-berlin.com/doc/en/scheduler.doc/xml/start_job.xml start_job job="jobname" at="..."/>
start task parametrized
Here you get a dialog for a later job start and for parameter settings. See start task after.
Underlying command: <http://www.sos-berlin.com/doc/en/scheduler.doc/xml/start_job.xml start_job job="jobname" at="..."><params><param name="..." value="..."/>...</params></start_job>
set run time
...WORK IN PROGRESS
stop
You can configure a job to stop automatically after an error occurs.
Here you can stop a job manually.
If you stop a job while a task is running then this task continues to run normally.
Stopped jobs cannot start a new task due to its run time or an order until you unstop it.
But you can start a stopped job manually via the start task immediately function.
Underlying command: <http://www.sos-berlin.com/doc/en/scheduler.doc/xml/modify_job.xml modify_job job="jobname" cmd="stop"/>
unstop
This function is only active for a _stop_ped job to unstop it.
Underlying command: <http://www.sos-berlin.com/doc/en/scheduler.doc/xml/modify_job.xml modify_job job="jobname" cmd="unstop"/>
reread
This function is obsolete and removed in the next release.
end tasks
The end tasks, suspend tasks and continue tasks has only an effect on API jobs.
They have no effect on shell jobs.
The end tasks function close all running tasks of the API job after the current process step.
Underlying command: <http://www.sos-berlin.com/doc/en/scheduler.doc/xml/modify_job.xml modify_job job="jobname" cmd="end"/>
suspend tasks
This function suspends all running tasks of the API job after the current process step.
The tasks are still alive.
Underlying command: <http://www.sos-berlin.com/doc/en/scheduler.doc/xml/modify_job.xml modify_job job="jobname" cmd="suspend"/>
continue tasks
This function continues all suspended tasks and the next process step is called.
Underlying command: <http://www.sos-berlin.com/doc/en/scheduler.doc/xml/modify_job.xml modify_job job="jobname" cmd="continue"/>
Task Menu
If a task of a job is running and you have clicked on the job then you see in the right detail view of the job the running tasks with a task menu button which contains the following functions
show log
It shows the task log in a new window via
http://<scheduler host>:<scheduler port>/show_log?task<task_id>
end
This function has only an effect on API jobs.
They have no effect on shell jobs.
It close the task of the API job after the current process step.
Underlying command: <code><kill_task joh1. "jobname" id"task-id"/>
kill immediately
This function kills the task immediately from the process list. The job stops when it is configured to stop on error.
Underlying command: <code><kill_task joh1. "jobname" id"task-id" immediately="yes"/>