User Guide > Objects > Alphabetical Listing > Runtime Tab

Runtime Tab

The Runtime tab is an object class-specific tab which is available in every executable object in AE. It can be used to specify parameters for a task's runtime behavior.

The Runtime tab is structured as follows:

Description

Field/Control

Description

Definition for ENDED_OK

 

Return code <= 

Maximum return code for a task's normal end.

A task ends normally (Status "ENDED_OK") if its return code lies below or is equal to the specified maximum return code.

Else execute

You can execute an object if the task does not end with a return code that lies within the ENDED_OK area.

Note that this object will not be processed if the task is terminated by using the script statement :EXIT.

End status for forecast

Selection list for the end status that this task should return when you make a forecast calculation.

Estimated runtime (ERT) 

 

Current ERT = 

Displays the task's next estimated runtime (ERT).

You can enter the estimated runtime here. This value applies until the ERT calculation is made after the task's next execution.

Format: "hours:minutes:seconds".

Use default (UC_CLIENT_SETTINGS)

Selecting this option has the effect that the calculation method that the administrator specified in the variable UC_CLIENT_SETTINGS using the key "ERT_METHOD" is used to calculate the estimated runtime.

Fixed value

A fixed value is entered as the estimated runtime.
Format: "seconds"

Dyn. method

Selection list for the dynamic method that is used to calculate the estimated runtime from the actual runtime.
Possible selections:

  • Adaptive: This method calculates the ERT proactively by considering various factors and runtime parameters such as the start time and the task's agent.
  • Linear regression: This method puts emphasis on runtime increases or decreases. You can also define the number of previous runs that should be considered, or define a correction factor in percent.
  • Average: This means that the average value will be retrieved from the real runtimes. You can also define the number of previous runs that should be considered, or define a correction factor in percent that will be added to the calculated average value.
  • Maximum value: The highest value from the list of real runtimes is used as the estimated runtime.

from the last ... runs

Number of past runs that are considered for the ERT calculation. Allowed values: 0 to 25.  

+ ... %

Value in percent for an upward ERT correction.

Differences > ... % are ignored

You can ignore possible huge differences to of actual runtimes.

Upper limit (in percent) for actual runtimes that should be included in estimated runtime calculation.

but do use ... runs at least

Number of past runs that should be considered regardless of differences. Allowed value: 0 to 25.  

Show Chart

Button that can be clicked in order to update the estimated runtime according to the current settings. A diagram displays in a separate window; it shows the last 25 ERT/RRT runs. Windows that are already open are updated.

Reset Values

Button that can be used to delete the real and estimated runtimes.
A security query displays, confirm it and all saved runtimes are cleared.

Maximum runtime (MRT)

 

None

The maximum runtime is not monitored.

Fixed value

The maximum runtime is monitored.

The allowed time is entered as a fixed value in the format "hours:minutes:seconds". An action as an ELSE condition must be specified which reacts when maximum runtime is exceeded.

ERT

The maximum runtime is monitored.

The valid estimated runtime (ERT) at the time of the task's activation is used as the maximum runtime. An action as an ELSE condition must be specified which reacts when maximum runtime is exceeded. 

+ ... %

A correction in percent can be specified for ERT for the maximum runtime. The determined value is added to the estimated runtime.

Curr. date + day(s)
Time

The maximum runtime is monitored.

A number of days and time of day are set for when the task must be finished. The starting point for the calculation of the date is the real date of the task. An action as an ELSE condition must be specified which reacts when maximum runtime is exceeded.

TimeZone

Selection of a TimeZone object.

Minimum runtime (SRT)

 

None

The minimum runtime is not monitored.

Fixed value

The minimum runtime is monitored.

The allowed time is entered as a fixed value in the format "hours:minutes:seconds". You must specify an action (ELSE condition) that applies if the maximum runtime has been exceeded.

ERT

The minimum runtime is monitored.

The valid estimated runtime at the time of the task's activation is used as its maximum runtime. You must specify an action (ELSE condition) that applies if the maximum runtime has been exceeded.

- ... %

When you select the ERT, you can also specify a correction value in percent for the maximum runtime. The value you determine is added to the estimated runtime.

Else

 

Cancel / Quit

If you activate this check box is activated, the task is canceled or quit if the runtime has been exceeded. Only available if the maximum runtime is monitored.

Execute

If you activate this check box, you determine that the task is executed. You can directly select the executable object. If the runtime is exceeded or not reached, the specified task is executed. Only available if the runtime is monitored.

Comments

A different type of runtime monitoring can be used for tasks that have been activated in a workflow or using a Schedule object. You can define it in the properties of the relevant object  (Runtime tab). The setting that are defined within the context of a workflow or schedule overrule the settings that have been defined in the task itself.

You can also assume these setting for runtime monitoring in the workflow or schedule. This is the default setting.

The quality of the ERT calculation is dependent on the available data. In case of a reorganization of the databaseA database is an organized collection of data including relevant data structures. there could be not enough datasets available. The calculation might be wrong in this case.

A lot of statistical data will be read from the object for the ERT calculation. Therefore this function should be only activated for individual objects, not client-wide.

 

See also:

Runtime Evaluation
Runtime Monitoring