SirFile: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
[[Model 204]] database files and warning users of the need for file reorganizations.. | [[Model 204]] database files and warning users of the need for file reorganizations.. | ||
SirFile is part of the [[ULSPF | UL/SPF]] family of products from [[Sirius Software]]. As with all UL/SPF products, SirFile requires the installation of the [[Sirius Mods]], with a version equal to or higher than the SirFile version. | <var class="product">SirFile</var> is part of the [[ULSPF | UL/SPF]] family of products from [[Sirius Software]]. As with all UL/SPF products, <var class="product">SirFile</var> requires the installation of the [[Sirius Mods]], with a version equal to or higher than the <var class="product">SirFile</var> version. | ||
==Overview== | ==Overview== | ||
SirFile requires only a single screen of setup information to determine "thresholds," after | <var class="product">SirFile</var> requires only a single screen of setup information to determine "thresholds," after | ||
which it automatically performs a pass through the online database files, checking to see | which it automatically performs a pass through the online database files, checking to see | ||
if any file has exceeded a threshold. The process that evaluates files is called the | if any file has exceeded a threshold. The process that evaluates files is called the | ||
| Line 21: | Line 21: | ||
</ul> | </ul> | ||
During the initial database load, all files added to the SirFile database are compared to | During the initial database load, all files added to the <var class="product">SirFile</var> database are compared to | ||
the system default thresholds. After the initial load, the user may override the system | the system default thresholds. After the initial load, the user may override the system | ||
default thresholds with file-specific thresholds for files that require higher or lower levels | default thresholds with file-specific thresholds for files that require higher or lower levels | ||
of monitoring. | of monitoring. | ||
If any file table is above a threshold, SirFile flags the file with a warning, causing it to be | If any file table is above a threshold, <var class="product">SirFile</var> flags the file with a warning, causing it to be | ||
highlighted in SirFile. Once SirFile has stored at least one sample snapshot of a file, it | highlighted in <var class="product">SirFile</var>. Once <var class="product">SirFile</var> has stored at least one sample snapshot of a file, it | ||
begins calculating the date at which each table will fill — assuming any table is showing | begins calculating the date at which each table will fill — assuming any table is showing | ||
growth. If the predicted fill date falls within a user-settable number of days, SirFile posts | growth. If the predicted fill date falls within a user-settable number of days, <var class="product">SirFile</var> posts | ||
a prediction to the file, and the file is highlighted in the SirFile screens. When a | a prediction to the file, and the file is highlighted in the <var class="product">SirFile</var> screens. When a | ||
prediction or warning is posted using a periodic refresh, a message can also be sent to | prediction or warning is posted using a periodic refresh, a message can also be sent to | ||
the audit trail, as well as to a list of user IDs. | the audit trail, as well as to a list of user IDs. | ||
| Line 36: | Line 36: | ||
The file parameters that are evaluated for table-full status are ARETRIES, BFULLP, | The file parameters that are evaluated for table-full status are ARETRIES, BFULLP, | ||
CRETRIES, CFULLP, DFULLP, EXTNADD, OVFLADD, EOVFLADD, and SPILLADD. | CRETRIES, CFULLP, DFULLP, EXTNADD, OVFLADD, EOVFLADD, and SPILLADD. | ||
The database refresh portion of SirFile is quite efficient, however it is the most expensive | The database refresh portion of <var class="product">SirFile</var> is quite efficient, however it is the most expensive | ||
operation in SirFile. Therefore, several options are provided for determining when to | operation in <var class="product">SirFile</var>. Therefore, several options are provided for determining when to | ||
perform a refresh, and for determining when to calculate CFULLP, generally the most | perform a refresh, and for determining when to calculate CFULLP, generally the most | ||
expensive of the refresh calculations. | expensive of the refresh calculations. | ||
Revision as of 23:57, 29 October 2012
SirFile is a comprehensive facility for monitoring the physical storage utilization of Model 204 database files and warning users of the need for file reorganizations..
SirFile is part of the UL/SPF family of products from Sirius Software. As with all UL/SPF products, SirFile requires the installation of the Sirius Mods, with a version equal to or higher than the SirFile version.
Overview
SirFile requires only a single screen of setup information to determine "thresholds," after which it automatically performs a pass through the online database files, checking to see if any file has exceeded a threshold. The process that evaluates files is called the refresh process. The refresh process performs two types of checks:
- It compares the current state of each file against the threshold settings to see if any file statistic is above the critical value for that statistic.
- It maintains a database of table usage information which it uses to determine rate of growth and to predict when thresholds will be exceeded.
During the initial database load, all files added to the SirFile database are compared to the system default thresholds. After the initial load, the user may override the system default thresholds with file-specific thresholds for files that require higher or lower levels of monitoring.
If any file table is above a threshold, SirFile flags the file with a warning, causing it to be highlighted in SirFile. Once SirFile has stored at least one sample snapshot of a file, it begins calculating the date at which each table will fill — assuming any table is showing growth. If the predicted fill date falls within a user-settable number of days, SirFile posts a prediction to the file, and the file is highlighted in the SirFile screens. When a prediction or warning is posted using a periodic refresh, a message can also be sent to the audit trail, as well as to a list of user IDs.
The file parameters that are evaluated for table-full status are ARETRIES, BFULLP, CRETRIES, CFULLP, DFULLP, EXTNADD, OVFLADD, EOVFLADD, and SPILLADD. The database refresh portion of SirFile is quite efficient, however it is the most expensive operation in SirFile. Therefore, several options are provided for determining when to perform a refresh, and for determining when to calculate CFULLP, generally the most expensive of the refresh calculations.
See also
All Sirius UL/SPF documentation is a available for download in PDF format at http://sirius-software.com/maint/manlist