This screen is normally restricted to a system administrator for the purpose of creating and managing job queues in Costpoint web.
This screen is similar to the Monitor Job Status screen (Administration » Transactions » Job Management) because it provides information on the status of a specific queue, the attached server, and the jobs that the queue contains. With functional rights to this screen, however, a system administrator can also create new queues, change the status of existing queues, and update any jobs waiting for execution on the job server.
The two blocks in this screen, Identification and Scheduled Jobs, display simultaneously, and you can use them as follows:
Use the fields in the Identification block to select the job queue, to specify whether jobs should be run sequentially or in parallel, and to view the activity of the attached job servers.
Use the fields in the Scheduled Jobs table window block to view the details of scheduled jobs and to make selective edits.
You cannot enter new jobs in this screen. You can update or delete jobs previously sent to the queue if Aborted, Hold, or Scheduled displays in the Status field. When a job is being executed through the job server, the Status field displays Executing and you cannot edit that job.
After you update or delete jobs in this screen, save the screen to retain your changes.
If the job has not executed successfully (as a result of application server failure), the Status field in this screen will display Aborted.
|
|
The system 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. |
You must first create a job in the Jobs screen (Administration » Maintain » Job Management). You must also submit a job to the queue via the Submit Job to Queue screen (Administration » Transactions » Job Management) before it will display in this screen.
If you send a job to the queue and its status is Scheduled, the scheduled time and scheduled date determine when the job is executed on the job server.
What steps should I follow to submit a job to the job server?
Selection Parameters
Create and save the screen selection parameters to be used in the individual computation, process, or report application(s).
Job Groups (Optional)
If you want to organize your jobs into groups (for organizational purposes only), you should first create job groups in the Job Groups screen (Administration\Maintain\Job Management).
Jobs
Set up the details of the specific job in the Jobs screen (Administration\Maintain\Job Management), including the name, description, and how the job should behave if an application task fails.
You must also enter one or more application tasks to be executed in the job as well as the parameter ID for each specific task.
Submit Job to Queue
Use the Submit Job to Queue screen (Administration\Transactions\Job Management) to select the timing parameters and specify the queue.
Click on the Submit to Queue button.
Which screens can I use to monitor and report on my jobs?
Job Report screen
Run the job report from this screen to review the jobs you have created in Costpoint web. This report lists the parameter ID(s) and sequential application(s) associated with each job.
Monitor Job Status screen
Use the Monitor Job Status screen (Administration\Transactions\Job Management) to view the job information and the status of jobs scheduled for a specific job queue.
|
|
Note: You can only make edits to submitted jobs in this screen. |
Update Job Queue List Status screen
Use the Update Job Queue List Status screen (Administration\Transactions\Job Management) to make a queue active or inactive on the job server and to allow a new queue to be recognized when the job server is already running.
Process and Report Status Inquiry screen
Use the Process and Report Status Inquiry screen (Administration\Review\Job Management) to view job status by application.
Print/Purge Job History
Use the Print/Purge Job History screen (Administration\Utilities\Job Management) to print and/or purge the history of jobs that have been previously executed on the job server.
Which job screens are normally the responsibility of a system administrator?
Job Queues
The system administrator will normally create the job queues for jobs to run in and can manage them all from the Job Queues screen (Administration\Maintain\Job Management) based on the display of queue status and specific job information.
Start/Stop Job Server
The system administrator will normally manage the job server operation from this screen (Administration\Transactions\Job Management) via the Start, Stop, and Reset buttons and the Daily Shutdown Time and Daily Restart Time fields.
Job queue activation/deactivation can also be controlled from this screen.
Use the fields in this block to select the job queue, to specify whether jobs should be run sequentially or in parallel (Oracle DBMS only), and to view the activity of the attached job servers.
For a new queue, enter up to 12 alphanumeric characters to specify a unique queue ID.
For existing queues, use Query to search for and select a queue ID.
For existing queues called up using Query, this non-editable check box displays whether this queue has been enabled to process jobs sequentially.
If you are adding a new queue, select this check box to enable sequential job processing for this queue.
|
|
Jobs in a user-defined queue will run simultaneously (on different threads), unless it is set up as a "sequential queue." Jobs in a sequential queue will be run sequentially (one after the other). |
This option is available only if you are using Oracle DBMS. For other DBMS like MS SQL Server, this option and this check box do not display.
This is a technique the backend DBMS uses to improve performance by breaking down tasks into multiple smaller subtasks and executing them in parallel.
Parallel execution can be enabled at 3 different levels: At the session level (connection time), at the table or index level (creation time) or at the statement level (statement execution).
Performance gain varies according to the type of SQL operation. It is significant in decision support systems (DSS), data warehousing operations or batch processing.
Jobs must be submitted via the Process Server. Oracle automatically performs the SQL statements that involve SELECT operations in parallel mode.
Certain hardware requirements must be met. Requirements include:
Symmetric multiprocessors (SMP)
Clusters or massively parallel systems
Sufficient I/O bandwidth
Underutilized CPU.
Attach the queue to a server in the Start/Stop Job Server (Administration » Transactions » Job Management) application.
Two fields in this block list the selected server and whether or not it is active.
Use the fields in this table window block to view the details of scheduled jobs and to make selective edits.
This non-editable field displays the job ID of each job that has been submitted to the queue.
This non-editable field displays the description of the job ID that displays in the Job field.
The description for this job was set up with the job in the Jobs screen (Administration » Maintain » Job Management).
When using Parallel Query (Oracle DBMS only), you should assign jobs suitable for parallel processing such as decision support systems (DSS), data warehousing operations or batch processing.
Status *
The current status of the job (Scheduled, Hold, Executing, or Aborted) displays in this field.
To execute a job, select Scheduled in this field and enter the scheduled date and time.
If the status is Aborted, the job was submitted but was not executed successfully. You cannot change the status of an Aborted job, but you can delete the entry.
If the status is Executing, the job server is currently executing this job. You cannot change the status in this circumstance.
If the status is Scheduled, the job is executed as soon as it reaches the top of the entry list and a server is available.
If the status is Hold, the job is not executed until you change the status to Scheduled.
If you change the Status field from Scheduled to Hold, the system automatically clears data from the Start Date and Start Time fields after the record is saved.
If you change the Status field from Hold to Scheduled and you have not entered a start date or time, the system automatically displays the current date and time as a default in the Start Date and Start Time fields after the record is saved.
Enter, or use Calendar Lookup to select, the scheduled date on which to execute this job on the job server.
If you selected the Start Time/Date execution option from the Execution Option drop-down box in the Submit Job to Queue screen (Administration » Transactions » Job Management), the system automatically displays that date in this field, where it can be edited, if desired.
If you enter data in this field OR in the Start Time field, entry in both fields is required.
If you change the Status field from Scheduled to Hold, the system automatically clears data from the Start Date and Start Time fields after the record is saved.
If you change the Status field from Hold to Scheduled and you have not entered a start date or time, the system automatically displays the current date and time as a default in the Start Date and Start Time fields after the record is saved.
Enter the scheduled time at which to execute this job on the job server.
If you selected the Start Time/Date execution option from the Execution Option drop-down box in the Submit Job to Queue screen (Administration » Transactions » Job Management), the system automatically displays that time in this field, where it can be edited, if desired.
Use the standard hh:mm:ss AM/PM format, where hh = hour, mm = minute, and ss = second.
If you enter data in this field OR in the Start Date field, entry in both fields is required.
If you change the Status field from Scheduled to Hold, the system automatically clears data from the Start Date and Start Time fields after the record is saved.
If you change the Status field from Hold to Scheduled and you have not entered a start date or time, the system automatically displays the current date and time as a default in the Start Date and Start Time fields after the record is saved.
If this is to be a recurring job, enter the number (of hours, days, weeks, or months), as appropriate, to specify when this job should recur after it has been initially executed on the job server.
Choose the frequency of recurrence in the drop-down box to the right of this field. Select Hours, Days, Weeks, or Months.
If you enter data in this field OR in the Recurring Timeframe field, entry in both fields is required.
Select the frequency of recurrence from these drop-down box options: Hours, Days, Weeks, or Months, as applicable.
If you enter data in this field OR in the Recur Every field, entry in both fields is required.
Enter, or use Calendar Lookup to select, the date at which the recurring job should end. This field is only available for recurring jobs.
If you enter data in this field OR in the End Time field, entry in both fields is required.
Enter the scheduled time at which to end the recurring job on the job server. This field is only available for recurring jobs.
If you enter data in this field OR in the End Date field, entry in both fields is required.
Use the standard hh:mm:ss AM/PM format, where hh = hour, mm = minute, and ss = second.
This non-editable field displays the user ID of the user who submitted the job to the queue.
This non-editable field displays the date and time that the job was submitted to the queue.
* A red asterisk denotes a required field.
This screen accesses data from the following tables: JOB_QUEUE (Job Queue) and JOB_SCHEDULE (Job Schedule).
