Sub-Tasks (ttspt2535m000)

Use this session to maintain the sub-tasks of a data upgrade task.

The rows in this session are sorted on the data range fields.

The session shows at least one sub-task; this is the sub-task with the minimal values of the data range indicators. This sub-task is automatically created during the initialization of the task. The displayed to-values depend on the presence of other sub-tasks.

You can add and delete sub-tasks, but restrictions are applicable as shown in the table below. When you add a sub-task, the Data Range of Sub-Task (ttspt2835m000) dialog is started. A next sequence number is generated for the sub-task.

The sub-task with the minimal data range indicator values can never be deleted.

This table shows the restrictions for adding and deleting sub-tasks:

Task real run statusSub-task real run statusSub-task real run status predecessorDelete sub-task allowedAdd sub-task allowed
anyvery first sequenceanyno-
Released, Completedanyanynono
Running with Failuresn/an/ayesyes
Partially Completedn/an/ayesyes
Ready for Retryn/an/ayesyes
Initialized, FailedInitializedInitializedyesyes
Initialized, FailedInitializedRunningnono
Initialized, FailedInitializedFailed *)yesyes
Initialized, FailedInitializedCompleted, Releasednono
Initialized, FailedRunninganynon/a
Initialized, FailedFailed *)Initializedyesn/a
Initialized, FailedFailed *)Runningnon/a
Initialized, FailedFailed *)Failed *)yesn/a
Initialized, FailedFailed *)Completed, Releasednon/a
Initialized, FailedCompleted, Releasedn/anon/a

 

*) Failed means status equals Failed, OR status equals Running while NO application lock has been set. The displayed values of the fld1, fld2, and fld3 fields are formatted according the data type of the corresponding data range field.

 

Sub-Task

The sequence number of the sub-task.

From

The first value in the data range of field 1 for the sub-task.

From

The first value in the data range of field 2 for the sub-task.

From

The first value in the data range of field 3 for the sub-task.

To

The last value in the data range of field 1 for the sub-task.

To

The last value in the data range of field 2 for the sub-task.

To

The last value in the data range of field 3 for the sub-task.

Real Run Status

The Real status of the sub-task.

Allowed values

InitializedThe characteristics of the UDLL sub-task have been retrieved and are stored in the other fields of the record.
RunningThe UDLL sub-task is running.
FailedThe UDLL sub-task finished with errors, or aborted. If one sub-task has the Failed status, the task gets the Failed status.
CompletedThe UDLL sub-task finished correctly, but the same upgrade step may be present for other companies for which the tables are logically linked. When all sub-tasks of a task have the Completed status, the task gets the Completed status.
ReleasedThe UDLL sub-task succeeded. When all sub-tasks of a task have the Released status, the task gets the Released status.

 

Server Number

The actual server (bshell) where the sub-task was executed last time.

Number of Restarts

The number of times the sub-task was started before it succeeded.

Attention Needed

If this check box is selected, the sub-task requires additional actions, although it may have succeeded.

Logfiles Present
Result Description
First Start Date
Last Start Date
Last Failure Date
Completion Date
Release Date
Simulation Run Status

The Simulation status of the Upgrade Step.

Allowed values

See Run Status.

Server Number
Number of Restarts
Attention Needed
Logfiles Present
Result Description
First Start Date
Last Start Date
Last Failure Date
Completion Date
Release Date

 

Data Range of Sub-Task

Starts a dialog where you can update the data range to be handled by the selected sub-task.

Restore Sub-Tasks from Upgrade Program

Restores the original sub-tasks from the upgrade program. All changes you made to the sub-tasks are reversed and all sub-tasks you added are removed.