FIELD NAME OR TERM |
|
DESCRIPTION |
indicator |
|
specifies whether or not the failure of a request job should cause subsequent jobs in the request to be prevented from running. |
indicator |
|
If the override options indicator is set, this indicator specifies whether or not a user can direct the job output to an email address. |
indicator |
|
If the override options indicator is set, this indicator specifies whether or not a user can direct the job output to a facsimile machine. |
indicator |
|
If the override options indicator is set, this indicator specifies whether or not a user can direct the job output to a printer. |
indicator |
|
set by an IT specialist, an indicator showing whether a user is permitted to set up standing requests. |
|
in this system, a job scheduled to run at a future time within a request, rather than immediately on the user's PC. |
|
|
a mode indicating a job is to run as a batch job. |
|
|
provide a mechanism for running request jobs in batch mode. A job must be assigned to an active batch queue by the system before it can run. Only one job at a time can be running in a batch queue, but several jobs can run concurrently using different queues. |
|
|
the act of cancelling a submitted request (using the Cancel Request button and saving). The status reverts to PLANNED. |
|
|
the total time allocated by the computer processor to run the job . |
|
(in JBS) |
|
are similar to query criteria. They are values used for comparison in extracting particular data from the database for reporting. |
Alias Instance - Job Request Schedule |
|
the date of an event, such as census day, which is used in specifying the schedule for a job. |
(in JBS) |
|
is a commonly used value supplied as a parameter by the system. A default parameter value can generally be overridden by a user. |
Delete Output indicator |
|
when set this indicator causes the system to delete the output file after it has been sent to its specified destinations. |
|
a job which requires the successful completion of one or more other jobs before it can run. See also Mandatory, Prerequisite Job. |
|
|
a unique number identifying a destination or set of destinations within each output number for a job in a request. |
|
- Batch Queue |
|
represents the latest time a request job can be assigned to a queue. The end time must fall within at least one of the queue's run window intervals. |
|
the date and time at which the entry was made in the run log. |
|
(executable job) |
|
see Job Execution Name |
|
a mode applying only to jobs run under the Oracle Reports facility, where the job runs immediately on the user's PC. |
|
|
see Run Window Interval |
|
|
the name or names by which existing executable jobs are known in Callista. |
|
|
the name of the module (set of programming instructions) executed when a job is run. |
|
(job number) |
|
see Job Sequence Number |
|
a destination or set of destinations (printer, fax, email) to which an output is directed. |
|
|
a term used to define an output destination at the time a job is defined. |
|
|
each job is assigned a priority (1-9) which is a major determinant in deciding the order in which the job runs in relation to other jobs which have also reached their scheduled time. Priority 1 is the highest priority. |
|
|
see Request |
|
|
a particular instance of the running of a job. |
|
|
a particular instance of the running of job, identified so that output from that run can be reproduced. |
|
|
reflects the stage a job has reached in its running. Possible statuses are WAIT, SCHEDULED, RUNNING, COMPLETE, FAILED, ABORTED, CANCELLED. |
|
(job number) |
|
a number identifying a job (or occurrence of a job) within a request. Jobs in a request will run in the sequence shown by these numbers, if the Sequence indicator is set. |
|
see System Job Type |
|
|
the date on which the job was last run. |
|
(JBS) |
|
the code of the location of a printer or facsimile machine recorded as the output destination of a job. |
indicator |
|
see Mandatory |
indicator |
|
When two jobs have a dependent relationship, the mandatory indicator signifies whether or not they must be included in the same request. |
|
the maximum number of jobs that may be run concurrently in the specified run mode at any time during the relevant run window. This can effectively limit the number of active batch queues in use. |
|
(of Job) |
|
the title of a job to be displayed on menus. |
(Job Output) |
|
see Job Output Option |
(in JBS) |
|
information produced as the result of running a job. |
|
the name of the output produced from a job, which for reports is specified in the Maintain Job Details form and for other jobs is pre-determined within the executable job. |
|
|
a number, unique within a job, which identifies a file created as output from that job. |
|
indicator |
|
an indicator which specifies whether or not, at request time, an end-user is:
The indicator works in conjunction with the Allow Print/Fax/Email indicators. |
(in JBS) |
|
a value influencing the way a computer program, routine or command will work, and/or the data it will access. In the JBS subsystem, parameters are entered by a user before a job runs. |
(in JBS) |
|
the form into which parameters are entered before a job is run. |
(in JBS) |
|
allows a user to change their own default printer and displays an indicator showing whether the user is permitted to set up standing requests. |
|
a job whose successful completion is required before a dependent job can run. See also Mandatory, Dependent Job. |
|
|
see Job Priority |
|
|
the priority for a job set by a user (where the user has been granted this privilege) which overrides the default job priority. |
|
|
the unique code assigned to a batch queue. |
|
|
a job producing a report, run using the Oracle Reports facility. Report jobs are the only ones that can be run in immediate mode, but they may also be run in batch mode. |
|
|
a request is the method by which a user can schedule and submit jobs to run in batch mode. |
|
|
a job that is included in a request and run in batch mode. |
|
|
a system generated unique number identifying an individual request. |
|
|
the stipulation of specific date(s) and time(s) within the specified run window after which the jobs in a particular request can run. |
|
|
reflects the stage a request has reached. Possible values are PLANNED, WAIT, SCHEDULED, COMPLETE, CANCELLED. |
|
|
the identification of the current user. |
|
|
a previous destination to which an output file can be redirected for a further copy of its contents. |
|
|
where an output file has been retained, a copy of its contents can be re-sent to a previous destination (printer, fax or email). |
|
indicator |
|
specifies whether or not a job can be restarted after a system crash. |
indicator |
|
an indicator which shows whether or not database security restrictions will be enforced when a report job is run. |
|
a record of the outcome for jobs that have completed. |
|
|
see System Run Mode |
|
|
is assigned to both batch jobs and batch queues and defines a set of times (intervals) during which jobs may be run, and batch queues are active. |
|
|
a run window interval is a period of time within a run window defined by a start day/time and an end day/time. |
|
|
the date and time at which, or as soon as possible after which, a job is required to run. |
|
|
used in this documentation to mean the specification of either a request schedule or a standing request. |
|
(in JBS) |
|
access to particular menus, forms, data or jobs granted to individuals or security roles. |
(in JBS) |
|
the ability to create or change security restrictions/access. |
|
the Callista identification of the person to whom the (email) job output will be sent. |
|
(job number) |
|
see Job Sequence Number |
indicator |
|
specifies whether or not the jobs within a request are to run in order of job sequence number. Jobs not run in sequence will generally run according to their priority. If job dependencies exist the system will ensure that pre-requisite and dependent jobs are run in the appropriate order. |
Short Title (of Job) |
|
the title of a job to be used in zoom lists. |
|
is a request automatically scheduled to run on a regular basis - for example, on the last day of each month - rather than on specific dates nominated beforehand. |
|
|
the days, day of the month, events, or other time markers which are used to trigger the automatic scheduling of a standing request. |
|
indicator |
|
specifies whether or not the request is one that is automatically scheduled on a regular basis. |
|
is the set of dates marking the period during which a request is to be run automatically at regular intervals. The period can be open-ended. |
|
- Batch Queue |
|
represents the earliest time a request job can be assigned to a queue. The start time must fall within at least one of the queue's run window intervals. |
|
the act of submitting a PLANNED request (using the Submit Request button and saving) so the system can schedule and run its constituent jobs. |
|
|
see Job |
|
|
see Job Priority |
|
|
specifies the type of job. The current types are STORED DATABASE PROCEDURE, PRO C PROGRAM, ORACLE REPORT and UNIX SHELL SCRIPT. |
|
|
the currently available types are TEXT and POSTSCRIPT. |
|
|
indicates the level of activity of a batch queue. The possible statuses are ACTIVE, INACTIVE and SUSPENDED. |
|
|
the available run modes are IMMEDIATE and BATCH. Report jobs can run in either mode, but other jobs run only in batch. |
|
indicator |
|
indicates that the job updates the database. This indicator is for information only. |
Last Modified on 30 September 1999