Page History

...

• has information about processes being executed by JobScheduler and other high level information of JobScheduler operation.
• is subject to log rotation which creates a new log file with a new timestamp by the house keeping job sos/housekeeping/scheduler_rotate_log  
• is stored on the file system (the default location is ${SCHEDULER_DATA}/logs/).

Anchor
job job

3. Job Log: job.<job_chain_name>,<job_name>.log

A Job Log is created:

• during start of JobScheduler for each job. Any job start will append an existing Job Log.

• when a job is added to a scheduling environment while the JobScheduler is running.
• with the file name job.<job_chain_name>,<job_name>.log where
  • <job_chain_name> is the name of the job chain that the job is executed for, i.e. the <job_chain_name> part of a <job_chain_name>.job_chain.xml job chain file.
  • <job_name> is the name of the job, i.e. the <job_name> part in a <job_name>.job.xml job file.

...

• is stored on the file system (the default location is ${SCHEDULER_DATA}/logs/).

Anchor
task task

4. Task Log: task.<job_chain_location>,<job_chain_name>,<job_name>.log

The Task Log is created:

• during execution of individual tasks (processes) for jobs. Any job start with a subsequent task will overwrite an existing Task Log.
• with the file name task.<job_chain_location>,<job_chain_name>,<job_name>.log where
  • <job_chain_location> is the folder name where the job chain is located.
  • <job_chain_name> is the name of the job chain that the job is executed for, i.e. the <job_chain_name> part of a <job_chain_name>.job_chain.xml job chain file.
  • <job_name> is the name of the job, i.e. the <job_name> part in a <job_name>.job.xml job file.

...

• contains all information about the execution of job instances, e.g. parameters, output to stdout and stderr of the script or application that is executed..
• is stored in the file system and - after execution - is saved to the database.

Anchor
order order

5. Order Log: order.<job_chain_location>,<job_chain_name>,<order_id>.log

The Order Log is created:

...

In Addition to being read from the file System, a number of JobScheduler log files can be viewed by JOC Cockpit users:

• The debug and main
and debug
• logs for a JobScheduler Master (scheduler.log and scheduler-<yyyy-mm-dd-hhmmss>.<scheduler-id>.log
and scheduler.log
• respectively) can be downloaded from the JOC Cockpit's Dashboard view by JOC Cockpit users with permissions to view the JobScheduler Status widget in the Dashboard.
• Log files for individual Orders, Jobs and Tasks can be read in the relevant JOC Cockpit view by users with the necessary permissions. Permissions are described in detail in the Authentication and Authorization - Permissions for the JOC Cockpit Web Service article.

Note that log files can only be accessed in this way via the JOC Cockpit when the JobScheduler Master in question does not have the status unreachable.

...