Viewing jobs for a data mining run

ID

Automatically assigned unique ID of the job. IDs of deleted runs are not re-used.

Name

The name of each job, including a descriptor followed by the number of the run. The jobs included in the run differ for MGPS and LR runs, as follows.

An MGPS run includes the following jobs:

• extract—Extracts data from the source database. The run ID follows the job name.
• mgps—Applies MGPS to the extracted data to produce scores. The run ID and 0 follow the job name.
• rgps—For runs that include RGPS computations, applies RGPS to the extracted data to produce scores. The run ID and 0 follow the job name.
• Post_Process—Creates unique value tables for the drugs and events that appear in the run results (for use by the results table) and adds column indexes to the output table. There is only one post-process job. The run ID and 0 follow the job name.

A logistic regression run includes the following jobs:

• LR_extract—Extracts data from the source database. The run ID follows the job name.
• LR—Calculates logistic regression scores. The run ID and 0 follow the job name. Click the name of this job to download the log files. These include the tab-delimited  lr_coefficients.log file, which contains alpha values computed for every event in an Extended LR run; and, if selected as a run option, the coefficients and standard errors for each predictor+response combination; and the lr.log file, which lists the most common values found for run covariates and summarizes convergence for each response.
• LR_Post_Process—Creates unique value tables for the drugs and events that appear in the run results (for use by the results table) and adds column indexes to the output table. There is only one post-process job. The run ID and 0 follow the job name.

Description

The text, Part of Run, followed by the run ID.

Server

The value, Any, appears if the next available listener can perform the job. If multiple listeners are in use and the MGPS or logistic regression run is submitted externally using a run definition file, a listener can be specified to perform each job and the unique ID of the listener appears.

Created

Server date and time when the extraction or base job was created. For a run that is scheduled and may be queued for processing after other runs, the creation of the extraction or base job may be substantially later than the creation date of the run itself.

Start Date

Server date and time when the job was started.

Note: Once an extraction completes, there is internal preparation of the extraction for the mgps or LR job. If you submit two runs, it is possible for the extraction job of the second run to start before the mgps or LR job of the first run.

End Date

Server date and time when the job ended.

Runnable

The value remains NO for each job until the preceding job is complete; then the value becomes YES.

Status

The column remains empty until the job has completed or failed. If the job completes successfully, the status is Completed. If the run is canceled when the job is being performed, the status is Canceled. An error message (and red background) appears if the job failed.