Jobs are identified by a unique ID (generated by Isight when the job is submitted) and a readable job name that you can provide or Isight can generate. A job is created when a model and job control information are submitted to the SIMULIA Execution Engine for execution or run locally in the Runtime Gateway. Jobs progress through a series of states as they execute, until they reach the Done state. You can use the Configure and Run interface to set execution options (such as a customized job name, log level, and the root component’s initial parameter values) before you run a job. For more information, see Setting Execution Options and Running a Job. Jobs that are submitted to the SIMULIA Execution Engine are automatically saved for later analysis. Jobs run locally in the Runtime Gateway can be saved to the job database if the appropriate preference setting is enabled (see Setting Local Results Database Preferences). If you run a job locally and have the local database disabled, you have an option to automatically save the job results to a zipped results file (*.zrf) that you can later open in the Runtime Gateway. You can pause a job (see Pausing Job Execution), and you can remove old jobs from your system’s memory (see Removing Jobs from Memory). You can use the Job Database interface to search for previously executed jobs, sort and open jobs, control job execution, import and export jobs, and view job information. For information, see Using the Job Database Interface. If you are connected to a SIMULIA Execution Engine, you can set access permissions to the jobs that are stored in the SIMULIA Execution Engine database. You can set default permissions, which are automatically applied to each job when it is run, or you can set permissions on a job-by-job basis. For information on setting default permissions, see Setting Default Permissions. For information on setting permissions on a job-by-job basis, see Setting Permissions for a Specific Job. | |||||||