Job Run Details

If supervision is active on multiple Nodes, clicking on New Run will require a Node to be selected.

The following actions can be triggered:

• Run

  To launch a new run from the entered values.

• Nested SAP Jobs

  To display the "Nested SAP jobs" window for SAP_XBP2 Uprocs. Refer to the Dollar Universe Manager for SAP Solutions User Guide.

• Sub-process

  To display the "Sub-processes" window for SAP_PCHAIN Uprocs. Refer to the Dollar Universe Manager for SAP Solutions User Guide.

Depending on the mode, “New Job Run” or “Display / Update” or “Rerun”, certain sections and fields are or are not displayed.

Default values may be defined in Launch Default Settings.

The General section is described below. For the other sections, follow these links:

• Context
• Run-book
• Notes
• Exceptions
• Previous Launches
• Provoked Launches
• Depending Jobs
• Functional Data
• Variables
• Job Log
• History Trace
• Resource Log

General

All the fields in this section are displayed only in Update, Display, and Rerun modes.

• From Task / From MU and Session or Uproc

  (New Run only) Radio button that determines whether job details are extracted of an existing task record or must be created manually.

• Task

  Displays the task; its components are displayed in MU, Session and Uproc fields. This field is only available if From Task has been selected.

  In New Run mode, if the task is of type Watching, the launch created will submit the Uproc / session without waiting for the resource.

• Task MU

  (Display / Update only) Displays the original task’s management unit.

• Specific Task

  If this task is a specific task (optional or provoked) the field will be completed, if not it is empty.

• MU

  Job management unit. Click on the arrow and select the required target MU.

• Session

  (Optional): Click on the arrow and select the required session.

• Version

  The version of the session selected displays in this field.

• Uproc

  If a session has been selected, the session header Uproc will display here by default, but you can change the first Uproc executed (not necessarily the header). To select a Uproc, click on the arrow and select the required Uproc.

• Version

  The version of the Uproc selected displays in this field.

For the Update / Display / Rerun actions the following fields will also be displayed:

• Launch N°

  Launch number

• Status

  Launch or execution status

• Uproc N°

  Uproc execution number

• Session N°

  Session execution number

Context

• Node / Cluster

  Displays the logical Node or cluster name for which the DUAS has been installed.

• Printer

  (New Run) Displays the printer identifier (environment variable) that can be used in the script to direct output.

• Batch queue

  The batch queue (physical or generic) where the job will be submitted. Click on the arrow and select the required queue.

  On OpenVMS, jobs are launched on a DQM batch queue and are then submitted to the VMS Queue Manager when the job has the status “running” in DQM. Therefore the user must select a DQM batch queue from the list that corresponds to an existing VMS Batch Queue (i.e. SYS$BATCH).

  On OpenVMS, only the job priority level is applied to the VMS Queue Manager. Only jobs that have the status “running” are displayed by the VMS Queue Manager.

• Entry N°

  (Display / Rerun) The batch queue entry counter.

• Priority

  Sets the job’s queuing priority (100 by default, range: 1 to 255).

• Submission account

  The submission user account which must exist at the system level. If the DUAS is on Windows, a Windows Service with the same name must also exist. To select a user, click on the arrow and select a submission account.

• Information

  Displays the Uproc default Information value. This field is modifiable for this launch.

• Severity

  Displays the Uproc default Severity value. This field is modifiable for this launch.

• Time Spent

  (Display / Update / Rerun) Execution duration and comparison with average execution time. These statistics are calculated from the third run. When the average is lower than 1 second, it is set to 1 second. If the job lasts 1 second or less, duration is set to 1 second. For example:

  • If average is 10 s and the current job duration is 0.5 s , the display is "< 1 s" and 12,5% of average.
  • If average is 0 s and current duration 0 s, the display is "< 1 s" and 100% of average
  • If average is 0 s and current duration 2 s, the display is " 2 s" and 200% of average

• Actions / Exceptions

  (Display / Update / Rerun) List of actions / past or future exceptions that apply to the launch / execution.

• Start Date

  The start of the job’s launch window. Execution may be delayed by unsatisfied conditions. Default is current system time.

• End Date

  Default is Start Date + 10 minutes. If the Launcher hasn’t successfully launched this job before the end of the launch window (Unsatisfied condition, Launch engine stopped or busy) the job will be set to “Time Overrun” status except in the case of a “Forced Launch” (Refer to section "Functional Data").

  The End Date value cannot be identical to the one displayed in the Job Run list.

• Except from to

  (New Run / Update) Input the definition of an exclusion window within the job’s launch window.

• Processing Date

  The processing date is formatted according to the functional period of the Uproc. For a Uproc whose functional period is Day, the processing date would be same as the start date. However, the processing date can be changed as required, for example, to run a job now on behalf of yesterday.

• Step

  (Display / Rerun) The step number is incremented from within the execution script with the uxset step command. In Rerun mode the step number can be set for recovery if the S_NUMJALON variable is managed in the script.

• Action Origin

  (Display) Indicates the origin of action taken on the execution or the launch: either Calculator or Operator.

• Operation

  (Display)

  • Relaunched: Indicates that the execution has been re-run.
  • Modified: Means that the event has been updated.

Run-book

Displays the list of run-books that coincide with the selected execution

Select a Run-book and click Display:

• If the Run-book is internal, the message is displayed immediately.
• If the Run-book is an external URL, it will open in the navigator by default.
• If the Run-book is a file, open the file using the appropriate application.

Notes

Update / Display / Rerun modes

Displays the notes on a job entered by the operator. The notes are signed and stamped as such:

[<user> - <Date> <time>]

Note text

Exceptions

Update / Display / Rerun modes

Job list exceptions.

The columns of this list are described in the "Exceptions" object

Previous Launches

Display / Rerun modes

Lists the execution attempts associated with the same launch. Each launch is subject to a line identified by a Uproc number, launch date and time and its origin. The status associated with the launch can be displayed by clicking the Load status button.

Select a line and click Open history trace to display more information about this launch.

Provoked Launches

Display mode

This section list the jobs provoked by the selected watcher task when the resource arrived. Each job corresponds to a file arrival.

• Session – Uproc – Task MU

  Identify the provoked launch.

• Uproc Number – Session Number

  Launch number and session execution number of the provoked launch (enables you to make the distinction between several concurrent launches on the same Uproc).

• Status

  Status of the provoked launch or job run.

• Start Date - End Date

  Start en end dates of the provoked launch.

Select a launch / a job run in the list and click:

• Open History Trace to open the history trace of the provoked launch, refer to section History Trace

• Provoked Run Log to open the job log of the provoked job, refer to section Job Log.

Depending Jobs

Display / Rerun modes

This document displays the list of launches expecting the event corresponding to the selected execution.

• Node

  Node of the launch that expects this event

• Session – Uproc – MU

  Identity of the selected execution.

• Launch # –Session #

  Launch number and Session counter of the conditioned launch (enables you to make the distinction between several concurrent launches on the same Uproc).

• Processing date

  Processing date of the launch in event wait.

Functional Data

New Run / Update modes:

• Forced launch at end of window

  Causes a job to run at the end of the launch window even if its prerequisites are not satisfied.

• Automatic restart

  (V5 only) automatically restarts a job that was running when the system crashed.

• Bypass condition check

  Causes the job to be submitted without checking its prerequisite conditions.

• Central monitoring

  (V5 only) sends monitoring information to a central monitoring Node.

Variables

In Dollar Universe, variables and their default values are defined at the Uproc level. Their values can be changed when the scheduled Task is created, when a manual launch is created or when a job is re-run.

To change the value of a variable: Select the variable line, click Update and the Value field becomes editable (in case of a password variable, the value is not displayed). Enter the new variable value and type Enter.

Job Log

The Job Log stores the standard and error output of the job.

In Dollar Universe, the Job Log systematically contains the job’s identification information, variables values (except for the password variables) and parameter values.

• Click Edit to display the Job Log in the default editor.
• Click Save As… to save the Job Log to a new file. A standard file browser is displayed.

On OS/400, all the job spools are copied in the job log.

On OpenVMS, if a job is in “running” status, the job log cannot be displayed.

History Trace

This section provides Launcher-generated information: Condition check time, batch queue submission time and entry number, start of execution time, messages, variables, steps, completion status, events deleted, next Uprocs launched in the session.

The display language is Dollar Universe (not UVC). To change it, go to the Administration mode > Nodes > DUAS Node > Node Settings > General settings > Language, and select FR or EN. This change is only taken into account when the Dollar Universe node is restarted.

The contents of the history trace are described in the Reference Guide.

• Click Edit to display the history trace in the default editor.
• Click Save As… to save the history trace to a new file. A standard file browser is displayed.

Resource Log

This section displays the log file for SCRIPT type resources used to condition Uprocs (if resources of such type were monitored by the EEP server during the Uproc condition check). If several resources were monitored, their logs are concatenated in this log file.

• Click Edit to display the log in the default editor.
• Click Save as … to register the log in a new file. A standard file browser appears.