DTP Debug Activity
Introduction¶
DTP Debug Activity is used to partially execute a DTP without changing partition data.
To launch a DTP in debug mode, it is necessary to select an activity and enter the run parameters via the Activity Debug Window
When a DTP is debugged, the following options must be considered:
- Debugging executes the selected activity and all lower-level activities (or loops).
- When there is a loop, the system derives the level of the loop from the lowest level, MIN(level), of all the activities belonging to the loop.
- Loading operations are not run.
- If there are parameters (AW or reporting) to be set up, a dedicated window will pop up to enter the required values and run the data processing. The audit window displays the name assigned to the target dataset at runtime.
- It is not possible to use datasets partitioned by Business Cycle & Entity in case of multi-organization process.
-
For the operation field:
-
if no operation is selected and the field is left blank, debugging performs all operations of the task.
-
if an operation is selected, debugging performs that data processing up to and including that operation; subsequent operations will not be performed.
IMPORTANT: In the event that the selected operation is part of a loop of several operations, debugging executes the loop to which this operation belongs only up to the selected operation.
Debugging of activities belonging to a loop¶
If the selected activity does not belong to the loop but to a higher level than the loop, the system runs the loop, including all activities belonging to it.
Example 1
Activity list
| CODE ACTIVITY | LEVEL ACTIVITY | LOOP |
|---|---|---|
| ACT_001 | 0 | |
| ACT_002 | 1 | MY_LOOP_1 |
| ACT_003 | 2 | |
| ACT_004 | 3 | MY_LOOP_1 |
| ACT_005 | 3 |
The selected activity is ACT_003 which has level 2,
Debug launch.
The loop MY_LOOP_1 has level 1 (because it takes it from the lowest level of the activities belonging to the loop).
The system runs all activities or loops with a level lower than the level of the selected activity (including also both activities of loop MY_LOOP_1):
then ACT_001, loop MY_LOOP_1 (ACT_002, ACT_004), ACT_003.
If the selected activity belongs to a loop, the system performs the following actions:
- retrieves the loop level to which the selected activity belongs
- determines the out-of-loop activities to be performed and runs them
- performs all activities in the loop at a lower level than the selected activity in the loop.
Example 2
Activity list
| CODE ACTIVITY | LEVEL ACTIVITY | LOOP |
|---|---|---|
| ACT_001 | 0 | LOOP_X |
| ACT_002 | 1 | LOOP_Z |
| ACT_003 | 2 | LOOP_X |
| ACT_004 | 2 | LOOP_Y |
| ACT_005 | 3 | LOOP_Y |
| ACT_006 | 4 | LOOP_Z |
| ACT_007 | 5 | LOOP_Y |
| ACT_008 | 6 |
Debugging operations belonging to a loop¶
If an operation is selected in the debug run window and the selected operation is part of a loop of several operations, debugging loops the operations up to and including that selected operation.
Subsequent operations are not performed.
Example 3
Activity list
| CODE ACTIVITY | LEVEL ACTIVITY | LOOP |
|---|---|---|
| ACT_001 | 0 | |
| ACT_002 | 2 | |
| ACT_003 | 3 | |
| ACT_004 | 3 |
Task list of activity ACT_02:
| CODE OP | LOOP |
|---|---|
| OP_001 | |
| OP_002 | LOOP_X |
| OP_003 | LOOP_X |
| OP_004 | LOOP_X |
| OP_005 |
The selected activity is ACT_002 which has level 2.
Debug is launched by selecting operation OP_003.
OP_003 is part of LOOP_X, a loop of several operations since OP_002, OP_003 and OP_004 all have LOOP_X associated with them and are consecutive.
Since operation OP_003 was selected in the debug launch window, the system runs the LOOP_X loop, but only for operations OP_002 and OP_003.
-
then OP_001, LOOP_X (OP_002, OP_003) are executed
-
operation OP_004 is not executed even if it belongs to LOOP_X because it is subsequent to the operation selected in the debug window.
- OP_005 is not run for the same reason.