Jobs

The Jobs function enables users to start reports and jobs and monitor their progress.

Start Job

When you select the Start Job option, a list of available and allowed reports is shown. An example is shown below.

You can apply filters for the application, queue, and job type. In the Job name field, you can enter a search string (case-insensitive) so that only jobs with that string in the name are displayed.

Use the filters to find a specific job.

To start a job, double-click it in the list.

AmtReport

The following window appears for the AmtReport type:

You can set the following Start Job options:

• Queue: The job queue to place the report in. See also: Job Queue Priority.
• Run As: The batch controller retrieves the specified user from LoginAccounts and uses the specified credentials to start the job. The job then runs under those credentials.
• Printer: The printer to use if no printer is set in the report.
• Request file: If the report requires user input, this file can be used to provide the input in advance.
• Backup directory: If set, a copy of the print file is saved in this directory.
• Report parameter: Parameters to pass to the report.
• Global parameter: Global parameters to pass to the report.
• Don't print: If selected, only the print file is created and nothing is printed physically.
• Recover from crash point: If selected, the job recovers from a crash point if possible.

At least a queue and a printer must be selected. When you click OK, the report is placed in the selected queue.

Script/Batch/Executable

For other job types (script, batch, or executable), you can set the following fields:

• Queue: The job queue to place the job in. See also: Job Queue Priority.
• Start date/time: The date and time to start the job.
• Run as: The batch controller retrieves the specified user from LoginAccounts and uses the specified credentials to start the job. The job then runs under those credentials. If the account is not found or is disabled, the job fails to start.
• Command line (script) parameter: An optional parameter to send to the script. It can be read in the ComScript job interface parameter ScriptParameter.
• Restart at: An optional parameter to send to the script to indicate from which point the script should be started. It can be read in the ComScript job interface parameter RestartAt. To use this parameter, add a custom restart mechanism to the script.

When you click OK, the job is placed in the selected queue for execution at the specified date and time.

Job Management

In this option, users can view and control the progress of started jobs. There are three tabs: Completed Jobs, Running Jobs, and Queued Jobs.

Completed Jobs

This tab contains a list of all completed jobs in the environment. You can apply filters for application, type, name, and a date/time window. Right-click a job in the list to view the details of the completed job. By selecting Extra Options, you can access additional filter options. By clicking the Batch controllers link, you can pause or resume running batch controllers and rebuild job schedules.

Running Jobs

This tab contains a list of all running jobs in the environment. You can apply filters for application, type, name, and queue. Right-click a job to do one of the following: view the details of the running job, stop the job gracefully, kill the job, or interrupt the job and send a value from 0 to 3. The sent value is available inside a report in the system item SI-REPORTRESULT in the interrupt routine of the report.

Queued Jobs

This tab contains a list of all queued jobs that have not started running yet. You can apply filters for the application, type, queue, and name of the queued job. Right-click a queued job to view its details, remove it from the queue, or force it to run now.