Contents of the Manage Job Queues Screen
Use the fields and options to configure the Manage Job Queues screen.
Job Queues
Use this block to select a job queue, specify whether jobs should be run sequentially or in parallel (Oracle DBMS only), and view the activity of the attached job servers.
Identification
Use this group box to specify a job queue ID.
Field | Description |
---|---|
Job Queue ID |
When creating a new queue, use this field to enter an identification code for this job queue. To use existing queues, use this field to search for and select a queue ID. |
Process Sequentially |
Select this check box to enable sequential job processing for this queue. Note: Jobs in a user-defined queue run simultaneously on different threads unless it is set up as a sequential queue. Jobs in a sequential queue run sequentially, one after the other.
|
Use Parallel SQL |
Select this option to enable parallel query and parallel DML. This option is available only if you are using Oracle DBMS. For other DBMS such as MS SQL Server, this option does not display. Parallel query is a technique the DBMS uses to improve performance by breaking down tasks into smaller subtasks and executing them in parallel. Parallel DML complements parallel query by providing both querying and updating capabilities for DSS databases, thus, speeding up large DML operations against large database objects. Parallel execution can be enabled at 3 different levels:
Jobs must be submitted through the Process Server. Oracle automatically performs the SQL statements that involve SELECT operations in parallel mode. Certain hardware requirements must be met. Requirements include:
|
Attached Servers
Use this table window to view all the job servers attached to this job queue.
Field | Description |
---|---|
Server |
This field displays the servers associated with this job queue ID. |
Queue Active |
This field displays Y if this job server is active. Otherwise, this field displays N. |
Scheduled Jobs
Use this table window to view and modify the details of scheduled jobs.
Field | Description |
---|---|
Job |
This field displays the job ID of each job that has been submitted to the queue. |
Description |
This field displays the description of the job ID in the Job field. Job descriptions are set up in the Manage Jobs screen. |
Status |
This field displays the current status of the job. They are as follows:
You can change the status of a job by selecting one of the options from this drop-down list box. To execute a job, select Scheduled and enter the scheduled date and time in the Start Date and Start Time fields, respectively. If you change the status from Scheduled to Hold, Costpoint automatically clears the data in the Start Date and Start Time fields after you save this job queue. If you change the status from Hold to Scheduled and you have not entered a start date or time, Costpoint automatically enters the current date and time in the Start Date and Start Time fields you save this job queue. Note: Costpoint automatically changes the job status to
Aborted if the application fails as a result of server failure. Any jobs with a status of
Executing will be set to
Aborted when a server is brought up after failure.
|
Start Date |
Enter, or click to select, the scheduled date on which to execute this job on the job server. If you selected Start Time/Date from the Execution Option field in the Submit Job to Queue screen, Costpoint automatically displays that date in this field. You can edit this default data. If you enter data in the Start Time field, entry in this field is required. |
Start Time |
Enter the scheduled time at which to execute this job on the job server. Use the standard hh:mm:ss AM/PM format, where: hh = hour, mm = minute, and ss = second. If you selected Start Time/Date from the Execution Option field on the Submit Job to Queue screen, Costpoint automatically displays that time in this field. You can edit this default data. If you enter data in the Start Date field, entry in this field is required. |
Priority |
This field displays the default priority level for this job. The priority level can be any number from 1 (highest) to 99 (lowest). The job server determines which jobs to process first based on this priority level. |
Recur Every |
If this is to be a recurring job, use this field to enter the number of hours, days, weeks, or months to on which this job must recur after it has been initially executed on the job server. If you enter data the Recurring Timeframe field, entry in this field is required. |
Recurring Timeframe |
Select the frequency of recurrence (Hours, Days, Weeks, or Months) for this job. If you enter data in the Recur Every field, entry in this field is required. |
End Date |
Use this field to enter, or click to select, the date on which this recurring job should end. This field is only available for recurring jobs. If you enter data in the End Time field, entry in this field is required. |
End Time |
Enter the scheduled time at which to end the recurring job on the job server. Use the standard hh:mm:ss AM/PM format, where hh = hour, mm = minute, and ss = second. This field is only available for recurring jobs. If you enter data in the End Date field, entry in this field is required. |
Submitting User |
This field displays the ID code of the user who submitted the job to the queue. |
Submitted Date/Time |
This field displays the date and time that the job was submitted to the queue. |
Cancel Job |
Click Cancel Job to cancel the selected job in the table window. |
Subtask
Subtask | Description |
---|---|
Scheduled Job Steps | Click this link to open the Scheduled Job Steps subtask and view the status of all operations that are scheduled within the selected job. |
- Related Topics:
- Scheduled Job Steps Subtask
Use this subtask to view the status of all operations that are scheduled within the current job. In the circumstance that a job has failed or been cancelled, you can review the details of completed versus failed operations to fully analyze the job status.