 Have you ever thought that a few actions were redundant? Think again! Let’s investigate some actions that have an impact on the dependencies in different ways and understand which one to use based on the situation. Release dependencies This action causes the temporary removal of all predecessor’s dependencies of the selected entity. If the entity is a job, its execution starts instantaneously (it goes in EXEC status). If it’s a job stream, its status is related to the status of the jobs inside. This action modifies the dependency structure only on the current instance and is meant to be used only during this monitoring phase. Whenever the entity is rerun, all dependency structures are restored. This action can be performed by the Release dependencies button on the monitoring action bar. If the user wants to release a single or a subset of dependencies, they can perform it in the Dependencies panel.   The same behavior happens when this action is performed on a job. Delete dependencies This action causes the permanent removal of the selected predecessor’s dependencies of the interested entity. If the entity is a job, its execution starts instantaneously (it goes in EXEC status). If it’s a job stream, its status is related to the status of the jobs inside. This action modifies a dependency on the plan, so whenever the entity is run again using the rerun action, the full dependency structure is not restored. This action can only be performed in the Dependencies panel. The scenario is the same shown for the Release action   The same behavior happens when this action is performed on a job. Cancel When the Cancel action is performed, the entity changes its external status in Canceled and all the successor’s dependencies are released immediately. A job’s internal status remains the same, apart from the EXEC internal status, that continues to run until it reaches a final status. If a Cancel action is performed on a job stream, its jobs are immediately put in Canceled status. The job stream internal status becomes CANCL P until all the running jobs inside reach a final status. After that, it becomes CANCL. The successors, both for jobs and job streams, have the dependency on the particular entity satisfied. Predecessors and successors are executed parallelly if the action cancel is performed on an entity located on the center point of a dependencies series. 4   Description: JOB_C final status depends on its own execution but the dependencies have been released.   Description: This is a scenario where JS_B has no running job during cancel action. Cancel pending This action is useful to avoid the parallel execution of predecessors and successors with respect to the canceled entity. The Cancel pending action postpone the cancel until all predecessor’s dependencies are satisfied. This includes also the completion of job processes inside a job stream. The status, both for job and job stream, remains the same until the cancel option is performed. It is possible to check that the cancel pending action has been taken care of by the Property panel. When the operation is completed, the final status is Canceled for both job and job stream. The internal status, instead, is CANCL for the job stream, but for the job, there are two possibilities: - If the Cancel action is performed during the job execution, the internal status is the job final one. - If the Cancel action is performed when the job has not started, the internal status is the same status the job has before the Cancel action.  Description: This scenario is common for job streams without executing jobs inside, in that case also all the jobs are canceled. Cancel pending status is only visible inside the entity’s property.  Description: JOB_B final status depends on its own execution, but the dependencies have been released. Kill If the job plug-in allows the Kill action, it can be performed only on a job entity in EXEC status. It immediately forces the final status to ABEND and stop the processes.. All successors are maintained and their dependencies are evaluated considering the final status of this job.   Description: If the dependency is simple or conditional to a final status different from ABEND.  Description: If the dependency is conditional to ABEND.
0 Comments
Your comment will be posted after it is approved.
Leave a Reply. |
Archives
October 2025
Categories
All
|
RSS Feed