Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
rdms:webapp:processes [2025/08/13 11:38] – periodic edit giuliordms:webapp:processes [2025/08/20 07:41] (current) – fixed punctuation + small text change giulio
Line 39: Line 39:
 The RDMS process ID (highlighted in red) is visible for every delayed rule, which allows you to correlate a job with its respective delayed rule. For example, in the screenshots above, you can see that the process ID is the same for both the delayed rule and for the related job presented in the section above.  The RDMS process ID (highlighted in red) is visible for every delayed rule, which allows you to correlate a job with its respective delayed rule. For example, in the screenshots above, you can see that the process ID is the same for both the delayed rule and for the related job presented in the section above. 
  
-Moreover, you can see displayed here as an example what the delayed rule for the creation of a tar archive looks like. You will notice that below the first line (''ID:''), a **Priority** of 9 is assigned to this rule. The RDMS assigns **priority 9** to all the delayed rules that **should be executed first**, **priority 5** to delayed rules that have **medium priority**, and finally **priority 1** to all the rules that should be **queued last** (i.e. checksum calculations).+The example we show above is a delayed rule linked to the creation of a tar archive (data bundling). You will notice that below the first line (''ID:''), a **Priority** of 9 is assigned to this rule. The RDMS assigns **priority 9** to all the delayed rules that **should be executed first**, **priority 5** to delayed rules that have **medium priority**, and finally **priority 1** to all the rules that should be **queued last** (i.e. checksum calculations).
  
 {{ :rdms:webapp:rdms_procces_8.png?direct&850 |}} {{ :rdms:webapp:rdms_procces_8.png?direct&850 |}}