Task Details

This topic describes all options available to define a task: the Session or Uproc to be executed, its execution management unit, and all its scheduling settings.

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

• Schedule
• Specific Task
• Trigger
• Technical Data
• Resource
• Functional Data
• Variables
• Schedule Preview

Some default values of the displayed information can be modified, refer to section: Task Default Settings. Don't forget to click Save to save your Task.

General

• Task on

  Select Session if you want to schedule a group of Uprocs (Sessions) or Uproc if you want to schedule a single Uproc. If a Session is selected:

  • A Main task (scheduled, provoked, watcher or cyclic) can only be created on the Uproc Session header.
  • A specific task (optional or provoked) can be created on a Uproc Session other than the header, once the main task has been created.

• Task Name

  Task name, independent of Session, Uproc and Management Unit names.

• Label

  Task description.

• MU

  Only available for "non-template" task types, it defines the target Management Unit. In Create mode, enter the Management Unit name or click on the button to select it from the Management Unit list. If the task is a template, no Management Unit is specified. In this case, it is recommended to specify a template name in the Template field. If the template name is a Management Unit name, it will be used as a target when you deploy the task.

• Session

  The Session and its version selected for the task. In Create mode, enter the Session name or click on the button to select it from a list.

• Uproc

  The Uproc and its version selected for the task. In creation mode, enter the Uproc name or click on the button to select it from a list.

  • If a Session is defined for this task, this Uproc list is restricted to the list of the Uprocs contained in the Session.
  • If the selected Uproc (or the selected session header Uproc) contain variables, they are automatically assigned to the task. If the Uproc contains password variables, their values are displayed as stars *******.

• Type

  A task defined for a single Uproc or for a Session using its Uproc header can be of type Scheduled, Provoked, Watcher or Cyclical. A task defined for a Session using a Uproc other than the Session header can only be of type Optional or Provoked (refer to the section Specific Task to create this type of task).

  • A task is scheduled with a set of scheduling rules and/or a set of explicit dates.
  • An optional task concerns a Uproc within a Session that has a scheduling different from the rest of the Session.
  • A provoked task can either be a task that will be triggered on demand (using the uxordre command or a trigger), or a task triggered within a Session with specific submission properties. In both cases, a provoked task doesn’t have any scheduling properties (neither rule nor explicit date).
  • A cyclical task is scheduled (without explicit scheduling rules or dates) by a user-defined number of days, hours and minutes.
  • A watcher task is scheduled with a set of scheduling rules and/or a set of explicit dates and waits for its resource (refer to section Resource).

• Template task

  Check this box to create a Template task. A Template task is not linked to a Management Unit. A template task does not create launches.

• Generate event

  For an optional task, check this box to create the event (Completed status if the Uproc is stored) even if the optional task did not run because of its planning.

• Activation

  The user can choose between:

  • Enabled: The next launch of this task is created in the “Launch wait” status.
  • Simulated: The next launch of this task is created in the “Disabled” status.
  • Disabled: No launch will be created for this task.

  In versions of Dollar Universe prior to V6, a deactivated task generates a deactivated launch if the U_WRITE_HELD<AREA> was validated at N.