SmartMode uses the FOCUS database management system to administer and maintain its databases. This system is provided as a part of the SmartMode software. |
In this section: Files Created During Installation Example: Determining a Disk Size Estimate for the Usage Monitoring Database |
The SmartMode Usage Monitor, Governor, and System Administrator Facility require certain files and databases, which are created during installation using the SMINSTAL FOCEXEC. The following table lists and describes these files.
Database |
Description |
SMCNTRL FOCUS SMCNTRL MASTER |
Tracks which data sources are monitored, governed and have rules applied. This is the main monitoring and governing control database. It is updated every time the administrator either turns on or off Global Monitoring or individual object monitoring or governing. |
SMRPCS FOCUS SMRPCS MASTER |
Contains information on any stored procedure or focexec execution if RPC monitoring is enabled. |
SMQUERY FOCUS SMQUERY MASTER |
Contains the analysis of the query. This is the main record created for each request that is monitored or governed. |
SMFROMS FOCUS SMFROMS MASTER |
Contains information about the data source being queried or reported from, most importantly the name. |
SMCOLMNS FOCUS SMCOLMNS MASTER |
Contains information about the fields or columns accessed in a data source. |
SMRELTNS FOCUS SMRELTNS MASTER |
Contains information about relational clauses using WHERE or IF syntax such as the field names, operators, and connectors. |
SMFNCTNS FOCUS SMFNCTNS MASTER |
Contains information about functions used. |
SMBYS FOCUS SMBYS MASTER |
Contains information about field names and sort order used with BY. |
SMREQSTS FOCUS SMREQSTS MASTER |
Contains the actual query that was monitored. |
SMGOVEND FOCUS SMGOVEND MASTER |
Contains governing results information only used with the SmartMode product. |
SMPRMTRS FOCUS SMPRMTRS MASTER |
This database contains all shift parameters and thresholds. |
SMKBASE FOCUS SMKBASE MASTER |
This is the database that is updated during the Build Rules process. It contains information on all rule files created for the data objects. |
SMPRL FOCUS SMPRL MASTER |
This database is updated during the Build Rules process or the Custom Rule Wizard and contains all rule syntax statements generated by the data induction process or the Custom Rule Wizard. |
GKESET FOCEXEC |
Contains server configuration information. |
You can control access to the SmartMode system databases using the FOCUS DBA facility, as described in the FOCUS for Mainframe documentation set.
The size of your tables will vary from one implementation to another. The following are major factors to consider:
This example assumes that you have a large SmartMode implementation, with 5000 tables monitored. Use the following table as a guideline.
Table Name |
Total Rows |
Row Size in bytes |
Table Size (KB) |
Notes |
SMCONTROL |
5000 |
145 |
1137 |
One row per monitored data source. |
SMRPCS |
900000 |
1956 |
3008497 |
One row per monitored Store Procedure. |
SMQUERY |
300000 |
1232 |
631641 |
One row per monitored request. |
SMFROMS |
750000 |
711 |
911316 |
One row for each data source used in a request. |
SMCOLUMNS |
1000000 |
232 |
396484 |
One row per column used in a request. |
SMRELATIONS |
250000 |
366 |
156372 |
One row per relational test used in a request. |
SMFUNCTIONS |
150000 |
221 |
56653 |
One row per function used in a request. |
SMBYS |
100000 |
182 |
31104 |
One row per BY, Order By or Group By used in a request. |
SMREQUESTS |
500000 |
120 |
102539 |
1:n rows per request. |
SMGOVERN |
150000 |
146 |
37427 |
One row per Governed request. |
SMPARAMETERS |
50 |
97 |
8 |
One row per defined shift. |
SMKBASE |
10000 |
219 |
3846 |
1:n rows per knowledge base. Where n is the number of active shifts defined when the knowledge base was created. |
SMPRL |
250000 |
141 |
60242 |
1:n rows per knowledge base. Where n is the number of PRL statements created during the data induction process. |
For every data object under SmartMode/Site Analyzer control, one record of SMCNTRL is used: 145 bytes.
For every FOCEXEC executed, one record of SMRPCS is used: 1956 bytes.
For every query monitored, at least one SMQUERY, SMFROMS, SMCOLMNS, and SMREQSTS record is stored: 1232+ 711 + 232 + 120 = 2295 bytes.
For example: SELECT * FROM CAR;
Add a sort (adds record to SMBYS): 2295 + 182 = 2477 bytes
Add a relational clause (adds record to SMRELTNS): 2477 + 366 = 2843 bytes
If governing is active, a record is added to SMGOVEND: 2843 + 146 = 2989 bytes
For example:
SELECT E.NAME, E.ADDRESS, E.JOBTITLE, J.JOBDESCRIPTION, J.PAY
FROM EMPLOYEE E, JOBS J
WHERE E.JOBTITLE = J.JOBTITLE
AND J.PAY < 50000
ORDER BY J.JOBTITLE, J.PAY
Requires:
1 SMQUERY (1* 978) 1232
5 SMCOLMNS (5 * 232) 1160
2 SMFROMS (2 * 711) 1422
2 SMBYS (2 * 182) 364
2 SMRELTNS (2 * 366) 732
5 SMREQSTS (5 * 120) 600
--------
5510 bytes of storage
A suggestion on how to calculate average query monitoring storage needs is to average the least complex query in the system with the most complex and multiply that by how many queries will be monitored in a day, month, or year. That will produce an estimate of space requirements.
Additionally, if rules are built and governing is on there will be recorded shifts in SMPRMTRS, built rules statistics in SMKBASE (one for every data object and every shift), and rule syntax in SMPRL (depends on complexity of data rules or custom rules).
* The Formula for KB: Rows * Size * 1.75 / 1024 = KB.
† SmartMode uses this table. It must be allocated but the size can be reduced if you are not using SmartMode.
Information Builders |