Job Runs

This function is designed to allow the operator to display past and present activity simultaneously. It proposes the functions required to control operations processes. This feature is not limited to a single Node but can also be used to supervise a Node View (multiple Dollar Universe Nodes).

Actions

• Filters

  When the document is opened, the filter bar is displayed and the default filter is loaded. The number of days displayed by default is defined in Administration> User Preferences> General Settings> Production> Job run Default Time Filter. The user can change the filter in the current document: This will only be applied to the current document and it will be discarded once it is closed.

• Group By

  Consolidate information in the Job runs document so as to make it more readable. Refer to section: Job Runs – Group by.

  It is recommended to limit the display to 60,000 job runs if the Group By option is selected.

• New Run

  Creates a new run of an existing job. Refer to section: Job Run Details. Used for a watcher task, this action does not create a launch with the Watching status. It creates a launch as for a scheduled task: the Uproc or session is submitted directly to the launcher.

• Display

  All details of a job run. Sections actually displayed will vary with the status of the job. Refer to section: Job Run Details.

• Session Execution Graph

  Displays the selected Session in the Job Chain editor in monitoring mode as a PERT graph (refer to section: Job Chains Editor). This is possible only if the Session header already exists in the Job runs (not purged) and was executed less than a day before. All monitoring and navigation actions are possible.

• Update

  The user can change the details of Launches that have not yet started running (disabled, launch wait, event wait). Refer to section: Job Run Details.

• Actions

  Shows available actions for the executions / launches. The user can select several jobs by using Shift or Ctrl.

  • Actions > Delete

    Purges records from the Job run list regardless of their status. Another way to automatically delete job runs is to set up the online purge. This action displays a confirmation window.

  • Actions > Cancel

    Kills running jobs or jobs with Watching status. This action displays a confirmation window. On OS/400, the job is canceled immediately but it can take up to 30 seconds to update the job status in Dollar Universe.

  • Actions > Hold

    Disables job runs in “Launch Wait” or “Event Wait” status. The release option activates the job executions in the Hold status.

  • Actions > Force Completion

    For a job in Launch Wait, Event Wait, Time Overrun, Refused, Deactivated or Aborted status; forces the job status to Completed (executing completion instructions).

    This action systematically generates an exception for this launch.

  • Actions > Bypass Conditions

    For a job in Launch Wait or Event Wait; modifies the launch by defining the option “Launch without condition check.”

  • Actions > Skip Execution

    For a job in Launch Wait, Event Wait, will not execute the Uproc script.

    This action systematically generates an exception for this launch.

  • Actions > Re-Run

    Jobs that have completed or aborted can be recovered with the same or different parameters. Refer to section "Job Run Details".

  • Actions > Acknowledge / Unacknowledge

    For a job in Aborted, Refused or Time Overrun status, the user can indicate that job run is under his / her control by selecting this job run and clicking Acknowledge. The user can cancel this action by clicking Unacknowledge. An alert appears in the Actions column; it corresponds to the “Acknowledgement” filter. This action is purely informational and will not appear in the intervention history.

  • Actions > Respond

    For a job that is running on OS/400 and in message wait (MSGWAIT status), the icon is displayed in the action column (it can take up to a minute for the icon to be displayed).
    On this line, select the option Reply Message to display the message (Message window) and respond in the Response window. Then, click on the Send button to send the response to the program.
    

• Open Notes

  Enables you to enter a note about the execution selected. “Run Notes” displays the notes already entered. The notes are signed and stamped as such:

  Uproc = [Uproc job run number>]

  [<user> - <Date> <Time>]

  Text

  “Enter New Note”: Enter a new note in addition to the others. Click on Save to memorize it. These notes are also visible in the execution details. Refer to section: "Notes".

• Show Runbooks

  Displays document execution details opened to the "Run-book".

• Trace

  Groups access to Engines traces and run logs:

  • Trace > Job Log

    Displays the Job Log. Refer to section: "Job Log".

  • Trace > History Trace

    Displays the History Trace. Refer to section: History Trace.

  • Trace > Resource Log

    Opens the log file associated with this script resource execution. If more script resources are associated with this job run, the logs are concatenated.

Columns

• Uproc

  This field contains the Uproc code.

• Status

  • Aborted: The job ended in error or canceled.
  • Completed: Normal successful completion.
  • Completion in progress: The job’s processing has finished and Dollar Universe is carrying out the completion instructions.
  • Disabled: The job (in Launch Wait status) was either held by the operator or the task is simulated.
  • Event Wait: Uproc conditions have not yet been satisfied and the launch window is still valid.
  • Watching: The watcher task has started and is monitoring the arrival of its resource.
  • Launch Wait: The job is scheduled for a time in the future.
  • Pending: The job has been submitted and is waiting to run in a batch queue.
  • Refused: An unsatisfied fatal condition was encountered during the condition check.
  • Running: Job execution in progress.
  • Started: The launch has been submitted (transitional status).
  • Time Overrun: The Launcher could not submit the Uproc before the end of the launch window (conditions not satisfied, Launcher absent or watching task that did not submit any job). The launch will not be submitted without operator intervention.

• Actions

  Displays the action / exception that will eventually be applied to a launch / job run:

  • All / No action: Selects all the actions or cancels the selection on all the actions.
  • Alert / Critical Alert: Indicates that an alert with Medium / High criticalness was issued on this job run. The alert was defined in the "Alerting Rules".
  • Acknowledgment: Indicates the user performed an Accepted action on this job run.
  • Note: A note was entered. To display it, select the job then Open Notes in the toolbar.
  • Skipped by User / by Exception: the job execution was not done at the request of the user or by applying an exception.
  • Bypassed by User / by Exception: the condition check was not done at the request of the user, by applying an exception.
  • Held by User / by Exception / by simulated Task: the launch has been suspended at the request of the user, by applying an exception, or because it has been generated by a simulated task.
  • Released by User: the launch has been freed by the user (after having been hold).
  • Killed based on time limit: The execution has been stopped by the engine because the execution time has exceeded the time limit set in the Uproc settings. Refer to section "Time Control Management".
  • Killed by user: The execution has been stopped by the User.
  • Could not submit: The execution could not be submitted; Refer to the History trace or the system trace for more details.
  • Restarted - too short: The execution has been restarted by the engine because its execution time was shorter than the one indicated in the Uproc settings. Refer to section "Time Control Management".
  • Shifted – outage: The execution has been postponed due to maintenance.
  • Force completed: The execution was forced into completed status.
  • Relaunched by user: Indicates the execution was rerun by the user either through UVC or the command line.
  • Script ran– based on time limit: Indicates a Uproc script was run after the set time limit for the execution was exceeded.
  • Message Wait: For a job that is running on OS400 and in message way (MSGWAIT status), this action is displayed. On this line, select the action Respond from the menu to respond to the message.
  • Launched by trigger: Indicates that a job has been triggered by an external system. For sessions, this status is only displayed for the header Uproc.
  • Watcher: Indicates a task of type Watcher, which is waiting for the arrival of its resource.
  • Launched by watcher: Indicates an execution that was submitted by a watcher task on arrival of its resource.

• Start Date

  The date and time of the start of the job’s launch window. By default this date is calculated in function with the day and number days to be displayed (set in Administration mode > User Preferences > General Settings > Job Monitoring > Job Run Default Time Filter).

• End Date

  For Launch Wait, Event Wait and Watching statuses, this is equal to the end of the launch window; during execution this is equal to the current date and time. Otherwise, this is the date and time the job finished executing.

• Session

  The Session ID if the Uproc is run within a Session.

• MU

  The job’s Management Unit

• Task

  Name of the Task

• Task MU

  The Task’s Management Unit. This can differ from a job Management Unit in the cases of a specific MU in the middle of a Session, HDP or a provoked or optional task.

• Processing Date

  Displays the job’s processing date (formatted according to the Uproc's functional period). Note that this is a business date not directly linked to the date of execution.

• Elapsed Time

  Gap between the current date (if the job is executing) or the end date (if it is completed) and its start date.

• % of Average per status

  Displays, in percentages, execution progression (current time - start time) compared to statistics duration. Progress is not displayed for launches with the status: Launch Wait, Time Overrun, Refused, Disabled. In the case of a consolidated view, progress is only displayed if the consolidation affects the Session number. In this case, the progression shown is calculated on the duration of the session statistics.

• Node

  The logical Node name on which the job will or has run.

• Application

  Application linked to the Uproc.

• Queue

  Batch queue, if the length of the batch queue name is greater than 20, the 20th character and the rest of the string is replaced by a "*". With Dollar Universe V5 if the queue manager (DQM) is not used, all JOBS will be displayed with the SYS_BATCH default queue name.

  On OpenVMS, only the job priority level is submitted to the VMS Queue Manager.

  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 a VMS batch queue (i.e. SYS$BATCH).

• Submission account

  User submission account in which the job is executed.

• Launch N°

  Unique numeric launch identifier generated, which is common to all Uproc condition checks.

• Uproc N°

  The Uproc’s execution sequence counter. This execution number is managed internally by Dollar Universe. For purely technical reasons, it identifies each Uproc occurrence.

• Session N°

  The Session's execution sequence counter. This execution number is managed internally by Dollar Universe and identifies the various occurrences of a given Session (this distinction may be used when creating conditions).

• Uproc Version

  The Uproc version number, which is always “000” in production

• Session Version

  The Session version number, which is always “000” in Production and Simulation.

• Information

  The default information value can be set when the Uproc is created and updated in the Uproc script.

• Severity

  The default severity level can be set when the Uproc is created and can be updated in the Uproc script.

• Session Node

  The Node on which the Session started.

• Step

  Displays the step number from which the execution has been restarted. The step number is set from within the Uproc script by the uxset step command. It can be useful for partial recovery (rerun from step number three for example). To know the current step of the execution, open the History Trace.

• MU Time Offset

  Displays the timezone and the time difference between the Management Unit time and the system clock. The time offset for a specific time zone is calculated for the date/time of the beginning of the job.

• Uproc Label

  Displays the Uproc label (on DUAS V6 nodes only)

• Priority

  Priority of the job run in the batch queue. The maximum value is 255.

• Printer

  Not available on Windows or UNIX, defines the output printer for the job run. The printer code is the four character logical name of the dedicated print queue.