10.1.1 Job Editor Terminology

The following table provides a list of terms used to define the concepts of the job editors.

Table 10-1 Job Editors List of Terms

Term Definition
dispatcher Daemon process that polls the job metadata for new jobs to be executed.
job Set of input parameters you identify within a job editor for a Oracle Financial Services algorithm, such as datasets, patterns, and date ranges.
jobeditors Tools within the Scenario Manager used to create jobs.
jobstatus code

Three-letter abbreviation for the status of a job:

  • ERR: The system places a job in this status if the job’s aborted during the run due to error.
  • FIN:The system places the job in this status when the job runs successfully without errors.
  • IGN:You,the user, places a job in this status to tell the dispatcher to ignore and not process the job. This type of job contains a cleancopy of the setup parameters for a job and is never intended to be executed. Also used for job templates.
  • NEW: You,the user, place a job in this status to indicate to the dispatcher that a new job is available for processing. When creating a new job, this is the default status.
  • RES:You,the user, place a job in this status after you have corrected a failure due to errors. This RES indicates to the dispatcher that the job should be restarted.
  • RUN: The system places the job in this status while the job is running.
run Audit trail the system creates when the Oracle Financial Services algorithm processes,such as the start and end times, the status, or the associated job. A runis created when the dispatcher processes a job. A job can have multiple runs. Refer looping.
salient entity Dataset attribute that is set up in the job editor to perform a special function during a job run, such as directing the job to run in multiple iterations.