DMD_PROCESS_INTERVAL
Process Management Configuration
Summary
This attribute defines the times during the day when the Deadline Manager checks the iProcess database for expired deadlines.
Applies To
The attribute can be set for the DLMGR process.
Permissible Values
The attribute value must be an integer in the range -1439 to +720, representing a processing interval, in minutes, calculated relative to midnight local time on the server where the DLMGR process is running.
If this value is:
| • | zero or less than zero, the processing interval is interpreted as an absolute interval. An absolute interval is used to process deadlines once per day at a set time. A value of zero means exactly midnight. |
| • | greater than zero, the processing interval is interpreted as a repeating interval. A repeating interval is used to process deadlines at regular intervals and at set times throughout the day, on each day. If an interval crosses the midnight boundary, the calculation is reset to start from midnight again (so that deadlines are processed at the same times each day). |
Default Value
This attribute is not defined on a newly installed iProcess Engine node. In this case, the default value is:
|
Machine ID |
Process |
Instance |
Value |
|
0 |
ALL |
0 |
1 |
The attribute only appears in the output of the SHOW_ALL_ATTRIBUTES command if you have explicitly assigned a value to it using the SET_ATTRIBUTE command. The default setting is not displayed.
Notes
The following table shows some example settings and the intervals they represent.
|
Value |
Type |
Deadlines will be processed at |
|
-720 |
Absolute |
Noon, every day. |
|
60 |
Repeating |
1am, 2am, 3am...and every hour thereafter. |
|
0 |
Absolute |
Midnight, every day. |
|
360 |
Repeating |
6am, 12pm, 6pm, 12am every day |
|
300 |
Repeating |
5am, 10am, 3pm, 8pm every day. Note: Processing on the second day does NOT start at 1am (8pm + 5 hrs) |