| Panel |
|---|
On This Page: Related Pages: |
spfru is one of the main processes within the SERVICEOptimizer system. It is responsible for a major part of the business as usual processing, as well as for some of the tidying process.
...
DB Name | System Parameter | Similar to sp_dbtidy option |
|---|---|---|
fru_tidy_enabled | If set to “YES” then the FRU will tidy jobs. If set to “NO” no tidying will be performed regardless of the setting of other parameters in this table. |
|
fru_tidy_ jobs_ days_before | Unlike the sp_dbtidy “-e” parameter, the date can only be specified as a number of days in the past. Integer: range sp083.glob_days_before to (unlimited). It also excludes the day specified so if the value is set to 7 then it tidies day 8 backwards. Installed as FRU memory horizon start. | -e |
fru_tidy_unfinished_ jobs | If set to “YES” then tidy job of any dispatch status otherwise just Cleared jobs. Installed as “NO” | -j |
fru_tidy_ intray_ days_before | Unlike “-i” the date can only be specified as a number of days in the past. Integer: range sp083.glob_days_before to (unlimited). It excludes the day specified so if the value is set to 7 then it tidies day 8 backwards. A value of 0 means do not tidy intray jobs. Installed as 0 | -i |
fru_tidy_ commit_count | This specifies the number of jobs that are tidied before a database commit is performed. This parameter should be used to limit the amount of database resource used during the tidy operation. Integer: range 1 to (unlimited). Installed as 500. | -c |
Scheduling Tidy in spfru
The schedule is formed by specifying up to 3 tasks per day and provides the following information:
...
A default schedule is set up when upgrading the database using dbinstall. It has a FRU_NO which corresponds to the ROOT resp_unit_no that can be found in sp056_responsibility_units.
Some Useful Tips
The following system (sp083_system_parameters) or FRU (sp213_scheduler_parameters) parameters need to be specified to activate FRU tidying:
...