The following figure shows an example of the Job Database
interface:

You can use the Job Search area to view basic information about a
job and to search for specific jobs. Isight
displays the jobs in the Job List area in the middle of the Job
Database interface.
If you have a long list of jobs, you can organize the jobs by time
or model name in the View by area on the left
side of the Job Database interface (see Sorting the Job List).
You can use the control buttons on the right of the Job
Database interface to stop jobs, to delete jobs, and to export
and to import jobs. For more information, see Stopping Running Jobs, Deleting Jobs, and Exporting and Importing Jobs.
You can use the tabs at the bottom of the Job
Database interface to see an overview of the job, the job
size, and the run summary.
The Job Search Area
The Job Search area at the top of the Job Database
interface allows you to view basic information about a job and to search
for specific jobs.
For more information on searching for jobs, see Searching for a Job in the Database.
The following information and options are available:
Job Name |
Typically, the Runtime Gateway
assigns a name to the job using the model name and the date and time
of the execution. |
User |
For SIMULIA Execution Engine
users, the name of the user who submitted the job. For other users, All
users is the only option. |
Model Name |
A text string specified by you or
by Isight
(see Saving a Model in the Design Gateway). |
Job completion status |
The state of the model
when execution finished. The following status options are available: |
OK |
The model executed successfully. |
Failed |
The model failed because of some problem
with the model itself. |
Cancelled |
The model was cancelled by you. |
System Failed |
The model failed because of
a software system failure. This status can indicate that some part of
the infrastructure has become unusable (e.g., a database has gone down),
or it can indicate a programming error; report these errors to your system
administrator for analysis. |
Jobs started on or after and Jobs
started on or before |
You can specify a date using any of
the predefined time periods (e.g., today, last week, etc.) by clicking
the corresponding list. You can also click the button to access a calendar that allows you to choose
a specific day. Finally, you can use a locally accepted date format.
For more details, place your cursor in the corresponding text box and
review the information that appears. |
Expiration date before |
Job expiration dates can be specified for individual models and component execution runs (see Setting the Execution Options). You can specify a date using any of
the predefined time periods (e.g., today, last week, etc.) by clicking
the corresponding list. You can also click the button to access a calendar that allows you to choose
a specific day. Finally, you can use a locally accepted date format.
For more details, place your cursor in the corresponding text box and
review the information that appears. |

The Job List

The Job Overview
The Job Overview tab at the bottom of the Job Database interface displays
some of the same information as the columns in the Job List. This tab
is useful for viewing large strings of information that are difficult
to view in the Job List.
For more information, see Viewing Job Information.
The following information is available: the name of the job, the job
ID (which is defined by Isight),
the model name, the model version, the name of the user that saved the
job, the random seed, the job results expiration date, and the job’s execution status. You can change the results expiration date for this job by clicking the button.
The job ID starts with "LOCAL_" if the job was run using standalone Isight. The following figure shows an example of the Job Overview
tab:


The Job Sizing Overview
The Job Sizing tab at the bottom of the Job Database interface displays
information about the size of the model. The following information is
available: the start and end date of the job and the duration (length)
of the job. In addition, the size in the database, the size of the managed
files, and the total size are shown for the selected model.
For more information, see View Job Size Information.
The following figure shows an example of the Job Sizing
tab:


The Run Summary
The Run Summary tab at the bottom of the Job Database interface shows
the model hierarchy (left side) and a small table (right side). The hierarchy
breaks down the jobs in a model based on the components in the model
and the model’s structure. It allows you to gain some insight into
the structure and size of the model that corresponds to the selected
job without having to load it into the Runtime Gateway.
For more information, see View the Run Summary.
The following figure shows an example of the Run Summary
tab:

When you select a job on the left side of the tab, the table on the
right side displays the following information for the selected job:
Count |
This column displays the number of workitems that finished
with the displayed combination of EvalType, Completion
Code, and Status. This value gives
you the ability to see the ratio of database lookup runs, approximation
runs, and exact evaluations for any given component. |
Eval Type |
This column displays the evaluation type of the
corresponding portion of the model. The following values may be displayed: |
|
Exact |
The component was (will be) executed using
exact analysis. No approximations are used in the analysis. |
|
Approximation Update |
The evaluation was made
for the purposes of updating an approximation model. It is an exact analysis. |
|
Database Rerun |
The evaluation was made by
lookup in the simulation process flow database (the analysis was not
run). This type of lookup restores the values associated with a prior
workitem—both inputs and outputs. |
|
Approximate |
The evaluation was made using
an approximation. |
|
Database lookup |
The evaluation was made by
database lookup in the results database. The analysis was not run. For
more information on database lookup, see Setting Local Results Database Preferences. |
Normal |
Any subflows or components with active
approximations are evaluated using those approximations. This evaluation
is the usual mode of operation. This value is used only to indicate how
an evaluation is to be done; it will never be the result of an evaluation. |
Completion Code |
This column displays whether or not the corresponding
portion of the model completed successfully or failed for some reason
(e.g., OK, Failed, Cancelled,
or System Failure). |
Status |
This column displays the execution status of the corresponding
portion of the model. |
|