Dependency Condition

This topic describes the dependency condition definition. Default values may be defined. Refer to section Uproc Default Settings

General Section

This section is specific to the dependency condition.

• Conditioned Uproc

  Contains the name of the current Uproc. It is empty and inaccessible during creation.

• Expected Uproc

  Contains the name of the conditioning Uproc, (meaning the pre-requisite Uproc event). The conditioning Uproc must be memorized. Refer to section: Events. Enter the Uproc name or click the button to select a Uproc from the list.

• If planned

  Check this box so that the condition is only examined by the launcher if it is scheduled / executed, taking into account user / session / MU and processing date elements. If the event is not present and if the launch is not scheduled, the condition is ignored (avoids waiting for a job that will not take place). Refer to the Reference Guide for full description.

• Conditioning Uproc status

  Defines the required status of the expected Uproc in the Job Event list. Possible values are "Completed"(default), "Aborted", "Ended" (Completed or Aborted) or "Absent" (neither Completed, nor Aborted nor Running).

• User account

  Any or Same specifies whether the Submission Account of the conditioning Uproc event should be identical to that of the conditioned Uproc.

• Proposition properties

  Expected or excluded: To be true, the defined condition can be expected (i.e. present in the Job Event list) or excluded (i.e. absent from the Job Event list).

• Fatal condition

  If a fatal condition is not verified during the condition check, the launch will simply be abandoned, whereas non-fatal (default) conditions will wait for the condition to become true.

Session Section

Inter-Session control can be used both with "non-simultaneity" and "dependency" conditions and with completion instructions.

The following choices are exclusive:

• Any Session

  The targeted event will be taken into account regardless of the Session.

  Default value

• Same Session

  The targeted event must refer to the same Session as the Uproc being monitored.

• Same Session and execution

  The targeted event must refer to the same execution of the Session (same Session execution number) as the Uproc being monitored.

• Specific Session

  The targeted event must refer to the selected Session. To select the Session, enter the Session name or click the button to select it from the list.

Management Unit Section

Inter-MU checking is used with "non-simultaneity", "dependency" and "resource" types of conditions (if the element !UG! is used in the resource definition) as well as with completion instructions.

There are four exclusive choices, as follows:

• Same MU

  Equivalent to a definition of an inter-Management Unit control on a blank ({  }) HDP expression. The targeted event(s) refer to the same Management Unit as the Uproc being monitored.

  Default option

• Specific MU

  The targeted event(s) must refer to a specific Management Unit. To define the Management Unit, enter the Management Unit name or click the button to select it from a list.

• MU Type

  The targeted event(s) must refer to a Management Unit of the type selected. To select the Management Unit type, enter the Management Unit type or click the button to select it from a list.

• HDP

  The targeted event(s) must refer to a Management Unit corresponding to the HDP expression entered. To enter an HDP expression, select the Management Unit types from one or both of the lists. The left-hand list represents the first character of the HDP; the right-hand list represents the second. Enter the Management Unit Type codes or click the button to select them from a list. Refer to the Dollar Universe Reference Guide for a detailed explanation of HDP (Hierarchical Data Processing).

All required – One is enough: States whether the validity of the condition should be true for all Management Units targeted by the criteria (HDP expression or the Management Unit type) or if only one Management Unit needs to correspond to the criteria.

Processing Date Section

The processing date is used with the "non-simultaneity", "dependency" and "resource" types of conditions (if the element !DTRAIT! is used in the resource definition) as well as with the completion instructions.

Possible values are:

• Completion instruction: Same, Specific value, Offset, Any
• Dependency condition: Same, Specific value, Offset
• Non-simultaneity condition: Same, Any
• Resource condition: Same, Specific value, Offset, Any

You may therefore choose only one of the following:

• Same

  The targeted event must have the same processing date as the Uproc being defined.

  Default value

• Specific value

  The targeted event must have a processing date corresponding to a specific value:

  • For day, enter the number of the day in the month
  • For week, enter the number of the week in the year
  • For month, enter the number of the month in the year
  • For year, enter the year

• Offset

  Defines the number of units (day / week / month / year) to shift the processing date of the targeted event.

  If the offset is in days, the type of day is taken into account: working, holiday, closed or calendar, depending on the calendar linked to the Management Unit of the targeted event.

• Any

  The processing date of the targeted event is not taken into account.