EDEP Processor for Control Sequence Dependency Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Contemporary systems lack a mechanism to track dependencies between control blocks in a control sequence, leading to performance loss and delays when a control block fails, as subsequent dependent blocks are still processed, causing the entire sequence to be re-queued and delayed.
Innovation Solution
A mechanism is introduced where each control block is assigned an error dependency (EDEP) level, allowing the system to identify and abort subsequent control blocks dependent on a failing block, and resume execution when there is no longer a dependency, using an EDEP processor to manage and analyze these levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the system processes control blocks sequentially without dependency tracking, then the execution mechanism remains simple, but processing delays occur when a control block fails and subsequent dependent blocks must be re-queued
Solution Approach 1:
The system performs preliminary action by assigning EDEP levels to control blocks in advance before execution. This pre-marking of dependency levels allows the execution mechanism to quickly identify and skip dependent blocks upon failure without requiring complex real-time dependency analysis, thus improving productivity while keeping the mechanism relatively simple.
Solution Approach 2:
The EDEP level acts as an intermediary indicator that mediates between the control block failure and the execution decision. Instead of directly analyzing complex dependency relationships, the system uses this intermediate EDEP level field to determine whether to skip subsequent blocks, simplifying the execution logic while maintaining dependency awareness.
2Loss of time
If the system continues processing subsequent control blocks after a failure, then execution completeness is maintained, but time is wasted re-processing dependent blocks that should be aborted
Solution Approach 1:
The system implements feedback by monitoring the EDEP levels of subsequent control blocks after a failure occurs. When a block fails, the system uses feedback information about the EDEP levels to determine which subsequent blocks should be skipped and which should still be executed, allowing timely abortion of dependent blocks while maintaining execution completeness for independent blocks.
Solution Approach 2:
The system applies local quality by differentiating the treatment of control blocks based on their individual EDEP levels. Not all subsequent blocks are treated uniformly - only those with EDEP levels indicating dependency on the failed block are skipped, while blocks with lower or equal EDEP levels continue to be executed, optimizing time loss without compromising overall execution completeness.
3Productivity
If the entire control sequence is re-queued after a failure, then all blocks are processed again ensuring completeness, but the system experiences significant delays and reduced efficiency
Solution Approach 1:
The system segments the control sequence into independent units based on EDEP levels. When a failure occurs, only the affected segment (subsequent blocks with higher EDEP levels) is identified and skipped, rather than re-queuing the entire sequence. This segmentation approach maintains processing efficiency by minimizing the scope of re-processing while ensuring completeness through targeted re-execution of only necessary blocks.
Data Source
AI summary
Provided are embodiments for a computer-implemented method, system and computer program product for identifying dependencies in a control sequence. Embodiments include receiving a control block that comprises a first error dependency (EDEP) level, maintaining the first EDEP level, and determining whether the received control block was successfully executed. Embodiments also include receiving a subsequent control block that comprises a second EDEP level, comparing the first EDEP level and the second EDEP level, and providing the subsequent control block for execution based at least in part on the successful execution of the received control block, and on the second EDEP level being less than or equal to the first EDEP level.