Status of Submitted Jobs

After you submit the job, you can view its status in the Submitted Batch Jobs window by selecting the Job Status button in the Submission of Module window. You can also reach the window by choosing Action, and thenBatch Jobs from any Oracle Clinical window or by choosing Admin, then PSUB/Report Jobs, and Batch Jobs from the main navigator tree. You cannot update fields in the Submitted Batch Jobs window.

For more information, see the following tasks:

• Viewing Job Status
  
• Understanding Log and Output File Names
  
• Stopping Jobs
  

Viewing Job Status

In this window you can view various aspects of your job, such as its current execution status, log and output file names, failure text if the job failed, as well as various timestamps. The execution status of each job changes as the job moves from entered, to started, and then to success.

If you are viewing this form while the job is executing, click Auto Refresh button on the navigation bar to have Oracle Clinical automatically update the status display. A second click turns off the auto refresh.

Understanding Log and Output File Names

The names of the files are structured as follows: the unique batch job ID for the job is prefixed with an L for the log file, and with an O for the output file; for example, a batch job with a batch job ID of 12345 would have an output file name of RXC_LOG:O12345.OUT, and a log file name of RXC_LOG:L12345.LOG.

If you want to print the output or log file, click the Print Output or Print Log button on the navigation bar. If you want to see the files onscreen without printing them, you click View Output or View Log. If there are multiple files, a dialog box appears and you can select the one you want. For convenience, the output file is included in the log file dialogs.

Note:

These buttons are unavailable if the selected row is a job that ran when an older version of Oracle Clinical—before 5.0—was installed. You can no longer view or print these output and log files.

Output and log files are not deleted from the client automatically, but you may delete them manually if you want. You can also edit the files that you bring up to view.

• PSUB job: As of Release 5.0, log and output files are saved only temporarily to a file system directory, then are immediately uploaded to the database where the View and Print buttons access them. The temporary directory is specified in the PSUB_LOGS_DIR value of the OCL_STATE reference codelist.

  The PSUB_LOGS_DIR value is fetched from the ocl_state ref codelist. A Username-specific directory is created on the database server when a user submits a PSUB job for the first time and is used for all subsequent jobs submitted by that particular user. The Job ID is specific to every job run.

• Report job: Log and output files are placed in the Report Server Directory on the server that is defined in the Oracle Accounts of Oracle Clinical. (Navigate to Admin, then Users, then Oracle Accounts.)

Name	Description
Job Id	Unique system-generated ID for the batch job submission
Module Name	Name of the module that is being executed
Execution Status	Status of the batch job ENTERED = You have requested submission of the job. SUBMITTED = Job has been submitted to the batch queue. SUBMIT_TO_RS = Job has been submitted to the server queue SUBMIT_FAILED = Job failed submission to the batch queue. STARTED = Job is currently executing. SUCCESS = Job has completed successfully. FAILURE = Job has completed unsuccessfully. STOPPED = Job has been stopped by the Stop button. STOP_FAILED = Job has not responded to the Stop button.
Study	Name of the study.
Parameter Set Name	Parameter Set Name that was loaded for this job.
Temporary Output Loc	Name of the directory where the output file was generated before being written to the database table BATCH_JOB_LOBS.
Failure Text	Text the job generates to give information about why it failed
Temporary Log Loc	Name of the directory where the log file was generated before being written to the database table BATCH_JOB_LOBS.
Mode of Execution	Type of scheduling that ran this job BATCH_IMMEDIATE = run in batch mode as soon as possible BATCH_SCHEDULED = run repetitively at a specified day and time
Module Type	Type of module executed in batch: REPORT, 3GL, DCL, PLSQL
Server Queue	Name of the server queue to which you sent the job
Print Queue	Name of the print queue to which you sent the job
Job Request Time	Date and time you clicked the Submit Job button
Job Submission Time	Date and time the job was actually submitted
Scheduled Time	Date and Time the job was scheduled.
Job Start Time	Date and time the job started
Job Completion Time	Date and time the job completed
Format	File format of the output file: ASCII, PDF, or POSTSCRIPT
Report ID/Process ID	The internal identification of the processed report (processed on the Report Server) or PSUB Job (processed on the PSUB Server).
Job Name	Name of the job processed on the Report Server. It is shown on the Report Queue Manager as well.
RS Scheduler	Report Server computer that owns the server queue
Schedule String	Time that you specified for the job start time.
Command Line	Command Line sent to the server.

Stopping Jobs

You can stop a job, even if it is in a job set, by clicking the Stop button. A stopped job has a status of STOPPED; if the job doesn't respond to the action, its status is STOP_FAILED. You can stop only your own jobs. Oracle Clinical does not delete log and output files associated with PSUB jobs; the system deletes log files from reports jobs when you stop the job.