Skip to end of metadata
Go to start of metadata

This article only applies to the Classic JOC interface

The information provided on this page only applies to the Classic JOC user interface, which is entering retirement:

FEATURE AVAILABILITY ENDING WITH RELEASE 1.11

The JOC Cockpit user interface replaces JOC:

FEATURE AVAILABILITY STARTING FROM RELEASE 1.11

See the JOC Cockpit Article for more information about the JOC Cockpit.

Viewing Job Schedules

Question:

How can a job owner view schedules and output?

Answer:

Using the JobScheduler Information Dashboard

The JobScheduler Information Dashboard (JID) is the most effective way to monitor orders and jobs and to view schedules and log files. Read our, "JobScheduler Dashboard Video", news article for a quick introduction to JID together with links to follow-up information as well as to the video itself.

For detailed information about JID read the Information Dashboard documentation.

Using the JobScheduler Operations Center

The JobScheduler Operations Center (JOC) can be used to show the next start time of a job or of an order.

Output for all jobs can either be gathered in log files that can then be accessed using JOC or in mails that can be configured to be sent by JobScheduler to specific addresses.

Note that we do not support the concept of job owners in the JobScheduler Operations Center: this is used for administrative access, not for end users, therefore all jobs are shown for all allowed hosts.

Individual applications can also provide end users with schedule-relevant information by making an XML request via TCP/IP:

Example Request:
<show_job job="scheduler_cleanup_sos_files"/>
 
Example Response:
<job job="scheduler_rotate_log" state="pending" title="Rotate
  and compress logfiles"
     all_steps="0" all_tasks="0"
     log_file="c:/scheduler/logs/job.scheduler_rotate_log.log"
     order="no" tasks="1" in_period="yes" next_start_time="2005-10-18 01:00:00">
  <tasks count="0"/>
  <queued_tasks length="0"/>
  <log level="info" highest_level="debug3" last_info=""
       mail_on_error="yes"
       mail_on_warning="yes" smtp="localhost"
       mail_from="scheduler@sos-berlin.com"
       mail_to="info@sos-berlin.com"/>
</job>
Write a comment…