These screens are normally used by a system administrator for the purpose of monitoring the overall workload on the application server and viewing the status details of the jobs. Other users may also benefit from access to these screens, however, since the application functionality enables status monitoring of each job submitted to the server, including reports, processes, and other jobs.
All data is display-only, which can be filtered by user, application, starting and ending dates, job status, and execution method.
These screens consist of a primary block and two subtask links, Costpoint Web Jobs and Open Client Server Process Applications. You can access two additional subtask links, Restartable Job Details and Scheduled Job History, from the Costpoint Web Jobs subtask/table window.
Use the primary block to enter your filter selections for data display, including user, application, starting and ending dates, job status, and execution method.
Use the Costpoint Web Jobs table window subtask to view the details of each Costpoint web job, including the application, submitting user ID, status, execution methods, start and end date/time, detailed status, progress, company, cancelled by user ID, report name and status, action name, and whether the job is restartable.
Use the Open Client Server Process Applications subtask to view the details of any client/server applications currently locked, including the application name and ID, the user ID, start date/time, company, and user's seat assignment.
The system automatically opens the Costpoint Web Jobs subtask when you access the application. Within this table window, two additional subtask links are available for jobs with a "Failed" or "User Cancelled" status:
Use the Restartable Job Details subtask to view the job sequence, step type, description, and start and end date/time details for each restartable job that failed or was cancelled by the user.
Use the Scheduled Job History subtask to view the status of all operations that are scheduled within the current job. The execution method must be "Process Server." If the current job is not submitted through the job server, this subtask will not display any information.
Note: Alternately, you can view some of the data from these screens, usually with less detailed information, using the following:
|
All users can monitor these screens whenever there is a need to view the details of the job server workload.
System administrators can purge status information stored in the W_APP_STATUS_INFO table whenever desired.
Since a new row is added to this table for each action and report executed on the server, this table can quickly become very large. |
These screens can be used to view the execution status of any job submitted to the server. These are the only screens in the current release of Costpoint web in which there is functionality for users to check on the status of jobs submitted asynchronously.
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 screen (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 screen
Set up the details of the specific job in the Jobs screen (Administration\Maintain\Job Management), including the name, description, and desired behavior of the job 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 screen
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 pushbutton.
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. |
If your system administrator has granted you rights, you can also use the Process and Report Status Inquiry screen (Administration\Review\Job Management) to view job status details by application.
Update Job Queue List Status screen
Use the Update Job Queue List Status screen (Administration\Transactions\Job Management) to activate or deactivate a queue on the job server, and to allow a new queue to be recognized when the job server is already running.
Print/Purge Job History screen
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 screen
The system administrator will normally create the job queues for jobs to run in and can manage all job queues from this screen (Administration\Maintain\Job Management) based on the display of queue status and specific job information.
Start/Stop Job Server screen
The system administrator will normally manage the job server operation from this screen (Administration\Transactions\Job Management) via the Start, Stop, and Reset pushbuttons and the Daily Shutdown Time and Daily Restart Time fields.
Job queue activation/deactivation can also be controlled from this screen.
Process and Report Status Inquiry screen
The system administrator will normally use the Process and Report Status Inquiry screen (Administration\Review\Job Management) to view job status details by application.
What is the difference between "synchronous" and "asynchronous" processing?
In Costpoint client/server, most functions are implemented synchronously, in which steps are performed in a specific order and only after the previous step has successfully completed. This means that you cannot execute another process or report on a real-time basis if another long-running process or report is currently in process (except in Report Preview mode). The solution for this limitation in Costpoint client/server is to schedule the execution of longer-running processes and reports on a process server.
In Costpoint web, for most functions you can choose either a synchronous mode of execution (the default) or an asynchronous (batch mode). In a batch (asynchronous) mode, applications are unlocked almost immediately after submission of a report or process. This means that you can submit a request for another report or process (including closing the application and shutting down the PC) before the current job is complete.
The functionality in these application screens enables users to view the execution status of all jobs in Costpoint web, whether they were submitted synchronously or asynchronously.
Note: Some reports can only be executed synchronously in Costpoint web, as in a posting report, which must be successfully generated before the application will allow you to post. Executing such a report asynchronously adds little value, since you must still keep the application open and wait for the report to finish before posting. Action/report locking rules still apply. For example, if you begin a single user process or report asynchronously, you cannot initiate another process until the first one completes, even though the application is unlocked. |
Please refer to the following technical topics for more specific information:
Actions
Application Locking
Asynchronous Processing
Job Server vs. Process Server
Use the fields in the primary block to enter your filter selections for data display, including user, application, starting and ending dates, job status, and execution method.
Enter, or use Lookup to select, the user by which you want to filter the inquiry data.
Lookup at this field displays the user ID.
Your Costpoint web user login ID displays in this field by default, and can be changed as desired.
Leave this field blank if you do not want a filter for it.
Enter, or use Lookup to select, the application ID by which you want to filter the inquiry data.
Lookup at this field displays the application ID and application name.
Leave this field blank if you do not want a filter for it.
This field is blank by default.
Enter, or use Calendar Lookup to select, a starting date by which you want to filter the inquiry data.
Leave this field blank if you do not want a filter for it.
This field is blank by default.
Enter, or use Calendar Lookup to select, an ending date by which you want to filter the inquiry data.
Leave this field blank if you do not want a filter for it.
This field is blank by default.
Select the job status from the drop-down box, by which you want to filter the inquiry data.
Your choices are: "All," "Active," "Completed, " "Failed," "Cancel Requested," or "User Cancelled."
"All" displays in this field by default, and blanks are not accepted.
Select the execution method from the drop-down box, by which you want to filter the inquiry data.
Your choices are: "All," "Asynchronous," "Process Server," and "Synchronous."
Note: Although "API" and "Asynchronous API" also display in the drop-down box, these choices are not available in the current Costpoint web release. |
"All" displays in this field by default, and blanks are not accepted.
Please refer to the FAQ in this topic for more information on synchronous and asynchronous processing.
* A red asterisk denotes a required field.
Click on this subtask link to open the Costpoint Web Jobs subtask.
Click on this subtask link to open the Open Client Server Process Applications subtask.
This screen accesses and displays data from the W_APP_STATUS_INFO (Web Application Status Information) table.