The Database Monitoring tools are used to issue specific database operator commands at specified frequencies during user-designated time periods. The monitor tools collect and analyze the output to determine if any problems exist.
Each morning the Control Center monitor scheduling routine reviews all database monitor schedules for databases managed by Control Center, and schedules the day's monitoring activity to be performed.
When a monitoring activity is started, Control Center issues a specific database operator command to the database's operator console, such as a SHOW LOG operator command.
After a brief wait (1 minute) an analyzer routine is executed to review the console response to determine if any further action is required. Upon completion of the analyzer routine, a monitor scheduler routine schedules the monitor for its next run.
Monitor tools issue database operator commands on a periodic basis. The responses to the database operator commands are collected and analyzed to determine if there are any problems or conditions that should be reported.
When a monitor is added, you identify conditions or problems to be flagged. For example, you can add a Database Log Check monitor that will tell you when your database's log has reached or exceeded a certain percentage used.
Notification is done upon the detection of a condition or problem by a monitor. Notification is made in the form of an online message and a note file sent to your virtual reader.
All users who are listed in the Notify-dbstatus field of the database's PARMS file will receive the online and reader file notification. See the description in Authorization/Notification Parameters.
Notification does not repeat each time the monitor runs, unless the detected condition or problem changes. For example, a Database Log Check monitor detects that a database's log has exceeded a threshold of 65 percent full and is now 66 percent full. The Database Log Check monitor would issue notification of this condition upon its detection, but will not continue to notify you unless the condition changes to a different percentage full (67 percent or greater).
If you want the notification message (not the note file) to be reissued each time the monitor runs, then set the Notify-Detect entry field to Y on the monitor scheduling panel. Refer to Figure 173.
| Important: |
|---|
|
The Notify-Detect entry field does not apply to these monitors: the User Activity monitors (Users Active, Users Connected, Users Locking), Database Counters monitor, Reset Counters monitor, or VMDSS monitors. |
Each database monitoring tool has a report generation option. Monitors can log the collected database monitor information each time a monitor runs. All log entries are recorded with the date and time that the monitor ran, along with information obtained in response to a database operator command.
Since you can vary how often a given monitor runs during the day, the reports can be used to show daily database usage and activity trends. For example, you can enable a Database Counters monitor to run at regular intervals (every 15 minutes, for example) throughout the day to get a better understanding of how your database is performing. Figure 157 shows an example of a Database Counters monitor report.
Figure 157. Monitor Report Example
Monitor Name: DBCOUNTERS Date: 04/06/97
Database: SQLDBA Time: 16:00:00
Type: DB COUNTERS DBSSCALL BEGINLUW PAGEREAD
PAGWRITE DIRREAD DIRWRITE
Run Days: MON-SUN
Time: 14:00-16:30
Frequency: 15 Minute
Next Refresh: 04/24/97
Monitor Report Log
Date Time DBSSCALL BEGINLUW PAGEREAD PAGWRITE DIRREAD DIRWRITE
________ ________ ________ ________ ________ ________ ________ ________
04-06-97 14:00:00 124 8 698 636 44 22
04-06-97 14:15:20 62 7 21 32 33 192
04-06-97 14:30:18 76 6 13 0 0 2
04-06-97 14:45:48 10 2 3 0 0 0
04-06-97 15:00:03 0 0 0 0 0 0
04-06-97 15:15:17 10 2 3 0 0 0
04-06-97 15:30:14 0 0 0 0 0 0
04-06-97 15:45:41 21 4 4 0 0 0
04-06-97 16:00:16 0 0 0 0 0 0
04-06-97 16:15:15 0 0 0 0 0 0
04-06-97 16:30:15 0 0 0 0 0 0
04-07-97 14:00:16 0 0 0 0 0 0
04-07-97 14:15:18 0 0 0 0 0 0
04-07-97 14:30:16 308 19 88 26 3 11
04-07-97 14:45:16 0 0 0 0 0 0
04-07-97 15:00:15 171 12 56 16 0 6
.
.
.
V
To create and schedule a monitor for a database, Control Center DBA or Control Center Administrator authority is required. Viewing of monitors, monitor schedules, and monitor reports requires a minimum level of database user authorization.
| Advanced Usage: | Control Center provides a default set of tools that are accessible by User, Operator, or DBA-level authorizations. These defaults can be changed so as to add or delete User, Operator or DBA authorizations to specific tools. For more details on how your Control Center authorization levels can be modified, refer to Appendix E, Authorizations. |
There are four categories of database monitor tools: Special Checks, User Activity, Space Usage, and Counter Monitors. These categories provide a broad range of database monitoring capability from user activity monitoring to space usage reporting.
The basic intent of these monitors is to verify that your database environment is "alive and well". Monitors for this category are the Database Up and Running Check and Database Log Check monitors.
Monitors in this category can be used to monitor and report on the activity of the users in your database. You can, for example, monitor users that are active, but not processing. Monitors in this category are the Users Connected, Users Active, and Users Locking monitors.
Use the monitors in this category to monitor and track your database space utilization. The monitors will notify you when space used thresholds are reached or exceeded. Monitors in this category are the DBSPACE Usage and POOL Usage monitors.
The Database Counter monitor can be used to collect and report on the database counters. All counters, specific counters, or subsets of counters can be monitored. In addition, use the Reset Counters monitor to reset your database counters as required.
The initialization of monitors is done for each database using the panel shown in Figure 158. You can add, delete, modify, view, and list monitors for a database. When adding (Option A) a monitor, you first select a specific monitor type; you are then prompted for additional information that will be used by the monitor.
All information pertaining to a given monitor is stored on the service machine's 191 A-disk and is available for update (Option M) at any time.
Figure 158. Control Center Main Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*---------------------------- Database Monitoring --------------------------* | || Option ===> CTRLID: MSTRSRV1 | | || Database ===> SQLDBA NODE: VMSYSTM1 | | || | | || A ADD Add a NEW database monitor | | || | | || D DELETE Delete a database monitor | | || | | || L LIST List monitors for this database | | || (Delete, Modify, Purge, Report, View) | | || | | || M MODIFY Modify an existing database monitor | | || | | || P PURGE REPORT Purge (refresh) a database monitor report | | || | | || R REPORT DISPLAY Report display for a database monitor | | || S SCHEDULE DISPLAY Display schedule for database monitor(s) | | || V VIEW View (display) a database monitor | | || Enter OPTION, select DATABASE, press ENTER to process | | || | | |*---------------------------------------------------------------SQMONITR----* | | PF: 1 Help 3 End | | | +--------------------------------------------------------------------------------+
Several options are made available on this panel for the convenient management of all monitors pertaining to the same database.
Figure 159. Database Monitor List Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------- Database Monitor List -------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Name Monitor Type Name Monitor Type | | || _ BPSPUSE DBSPACE USAGE _ DB1UPCK UP AND RUNNING CHECK | | || _ CHECKLOG DATABASE LOG CHECK _ DB1CNT1 DB COUNTERS | | || _ DB2CKLOG DATABASE LOG CHECK _ DB3LGCK DATABASE LOG CHECK | | || _ DB1CKPL DBSPACE USAGE _ DB3ULCK USER LOCKING | | || _ DB3UL1 USER LOCKING | | || | | || | | || | | || | | || | | || Select: V = View, M = Modify, D = Delete, | | || R = Report Display, P = Purge Report(refresh) | | || Page 1 of 1 | | || | | |*------------------------------------------------------------SQMMNLST-------* | | PF: 1 Help 3 End | | | | | | | +--------------------------------------------------------------------------------+
| Operational Note: | Modification of a monitor will cause automatic rescheduling to occur. |
Scheduling of all active monitor routines is done each morning by Control Center. Only those monitors that are to be run for the current day are shown on the Monitor Schedule Display panel.
Figure 160. Monitor Schedule Display Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*-------------------------- Monitor Schedule Display -----------------------* | || Command ===> CTRLID: SQLMSTR | | || NODE: WMAVM1 | | || Next *Schedule* Run | | || NBR Date Run ******* EVENT ******* Start Stop Frequency | | || 1 03/16/97 17:08 SQLDBA DBLOGCHK 15:38 19:00 5 MINUTE | | || 2 03/16/97 17:06 SQLDBA DBCOUNTR 09:01 18:00 3 MINUTE | | || 3 03/16/97 21:00 SQLDBA DBULCHK 11:00 24:00 5 HOUR | | || 4 03/16/97 22:00 SQLDBA DBUACHK 22:00 24:00 1 HOUR | | || | | || | | || | | || | | || | | || | | || | | || | | || | | || Page 1 of 1 | | || | | |*---------------------------------------------------------------SQMNS10-----* | | PF: 1 Help 3 End | | | +--------------------------------------------------------------------------------+
If Option A (Add) was selected from the main monitor panel, then the next panel presented will be the monitor selection panel shown in Figure 161. After you have selected a monitor, you will be prompted for conditions to be scanned for, as well as scheduling information.
Figure 161. Monitor Selection Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Selection ===> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor name => | | || | | || Special Check Monitors User Activity Monitors Space Usage Monitors | | || CL DATABASE LOG CHECK UA USERS ACTIVE SD DBSPACE USAGE | | || CU UP & RUNNING CHECK UC USERS CONNECTED SP POOL USAGE | | || UL USER LOCKING | | || | | || DB Counter Monitors VMDSS Feature Monitors | | || CO DB COUNTER(S) CI INTERNAL COUNTER(S) | | || RC RESET COUNTER(S) CP POOL COUNTER(S) | | || | | || | | || | | || | | || Select a MONITOR TYPE, enter MONITOR NAME, press ENTER to Continue | | || | | || | | |*---------------------------------------------------------------SQMMNOP-----* | | PF: 1 Help 3 End (CANCEL) | | | +--------------------------------------------------------------------------------+
The name you indicate in the Monitor Name entry field (refer to Figure 161) will uniquely identify the monitor being added. This is done so that you may select the same monitor type for the same database more than once. Each monitor name entered will be verified to be sure that it does not conflict with other monitor names.
This tool monitors database log usage. The Log Used Percentage entry field shown in Figure 162 is set by you to a level at which you will receive notification if the database's log ever reaches or exceeds it. For example, the log for the SQLDBA database identified in Figure 162 will be checked each time the monitor runs to see if the log percentage used has reached or exceeded 75 percent.
In addition to notifying you that a database log has reached or exceeded a set percent used, the Database Log Check monitor can be instructed to take specific action. For example, if the database's log reaches or exceeds 75 percent used, then the monitor shown in Figure 162 will initiate an SQLEND ARCHIVE. Additionally, if the Schedule Time entry field has been specified, then the Action specified will be scheduled for the time indicated and will not be initiated immediately.
Figure 162. Database Log Check Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => LOGCHECK | | || Monitor Type => DATABASE LOG CHECK | | || | | || Log Used Percentage => 75 Actions occur when percentage is reached | | || | | || Select ACTION to be taken(to SCHEDULE specify a time); | | || SQLEND ARCHIVE => N (Y/N; Full archive, database down) | | || SQLEND UARCHIVE => N (Y/N; User archive, database down) | | || SQLEND LARCHIVE => N (Y/N; Log archive, database down) | | || DVERIFY => N (Y/N; Verify the directory) | | || ARCHIVE => N (Y/N; Full archive, database up) | | || LARCHIVE => N (Y/N; Log archive, database up) | | || SCHEDULED TIME => 22:00 (HH:MM; 00:01 to 24:00, blank for | | || IMMEDIATE execution.) | | || Press ENTER to CONTINUE or PF3 to CANCEL | | || | | |*---------------------------------------------------------------SQMMNCL-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
SHOW LOG is the database operator command used by this monitor. If the report option (Monitor Scheduling Panel) is selected, the results of the command are logged.
This tool (Figure 163) verifies that your database is still up and running. A SHOW LOG database operator command is issued to the database to verify that the database is responding. If the database terminates, is logged off, does not respond, or responds incorrectly, you will be notified.
Figure 163. Database Up and Running Check Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => RUNCHECK | | || Monitor Type => UP AND RUNNING CHECK | | || | | || | | || This monitor verifies that a database is 'up and running'. | | || | | || The monitor will check that the database machine is running | | || DISconnected, and that it responds to an operator command. | | || | | || NOTE: If report option is selected, then a running log of the | | || database's status will be maintained. | | || | | || | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | || | | |*---------------------------------------------------------------SQMMNCU-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
SHOW LOG is the database operator command used by this monitor. If the report option (Monitor Scheduling Panel) is selected, then the status of the database machine is logged.
This tool monitors active database users. This monitor can be instructed to scan for checkpoint active agents or for the database agents in lock, communication, or checkpoint waits. Refer to Figure 164.
Figure 164. Users Active Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => UACTIVE | | || Monitor Type => USERS ACTIVE | | || | | || | | || Select desired scans: | | || | | || Checkpoint Active => N (Y or N; scan for active checkpoint agent) | | || Agent Wait Check => N (Y or N; scan for Lock, communication , or | | || checkpoint waits) | | || | | || NOTE: Scans are optional; if no scans specified, | | || then be sure to specify report option. | | || | | || Select scans to be performed by monitor, | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | |*---------------------------------------------------------------SQMMNUA-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
SHOW ACTIVE is the database operator command used by this monitor. If the report option (see Monitor Scheduling Panel) is selected, the results of the command are logged.
This tool monitors users connected to a database. This monitor can be used to scan for active users not processing, users waiting for agents, or for inactive users (refer to Figure 165).
Figure 165. Users Connected Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => UCONNECT | | || Monitor Type => USERS CONNECTED | | || | | || Select Desired Scan(s): | | || Scan for ACTIVE users that are NOT PROCESSING => N (Y or N) | | || Scan for users that are WAITING for an AGENT => N (Y or N) | | || Scan for users that are INACTIVE => N (Y or N) | | || | | || NOTE: Notification will occur if scan(s) detect users | | || in conditions specified. | | || | | || | | || Select scans to be performed by monitor, | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | || | | |*---------------------------------------------------------------SQMMNUC-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
SHOW USERS is the database operator command used by this monitor. If the report option (see Monitor Scheduling Panel) is selected, the results of the command are logged.
This tool monitors database lock contention. The monitor can be used to scan for lock holders that are not processing, locking due to a checkpoint, or any lock contention at all. Refer to Figure 166.
Figure 166. Users Locking Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => ULOCKING | | || Monitor Type => USER LOCKING User Locking Activity Monitor | | || | | || | | || This monitor scans for user LOCKING contention, | | || NOTIFICATION will occur as specified: | | || | | || Notify when a lock holder is NOT PROCESSING => N (Y or N) | | || Notify when locking is due to a Check Point => N (Y or N) | | || Notify when ANY locking contention detected => N (Y or N) | | || | | || **Report generated by this monitor records locking activity by DBSPACE | | || | | || Select NOTIFICATION conditions desired, | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | |*---------------------------------------------------------------SQMMNUL-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
SHOW SYSTEM is the database operator command used by this monitor. If the report option (see Monitor Scheduling Panel) is selected, the results of the command are logged.
This tool monitors DBSPACE usage. You must specify a DBSPACE number, which you can obtain from using the Object Search and List tool. You can enter several thresholds for header, data, and index pages. Refer to Figure 167. You will be notified if any of the thresholds are reached or exceeded.
Figure 167. DBSPACE Usage Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => DBSPUSE | | || Monitor Type => DBSPACE USAGE Logical Space Monitor | | || | | || DBSPACE Number => ___ (Number of DBSPACE to be monitored; | | || obtained from DBSPACENO col SYSDBSPACES) | | || Header Pages => ____ (Percentage of occupied pages) | | || Header Used => ____ (Percentage of space used) | | || Data Pages => ____ (Percentage of occupied pages) | | || Data Used => ____ (Percentage of space used) | | || Index Pages => ____ (Percentage of occupied pages) | | || Index Used => ____ (Percentage of space used) | | || NOTE: NOTIFICATION occurs if any of the specified values are exceeded. | | || | | || Enter parameter values to be checked by monitor, | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | |*---------------------------------------------------------------SQMMNSD-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
SHOW DBSPACE is the database operator command used by this monitor. If the report option (see Monitor Scheduling Panel) is selected, the results of the command are logged.
Use this tool to monitor pool usage for a database. This monitor will review the amount of space used for the storage pool(s) specified (refer to Figure 168). To have all storage pools monitored leave the POOL Number parameter field blank. The Percent Used parameter field is optional. If specified, the monitor will notify the database's DBAs when the percentage specified is reached or exceeded for any of the storage pools entered. If a SHORT ON STORAGE condition is detected for any storage pool, then the database's DBAs will be notified. Note, any means all the database's storage pools, not just those listed for this monitor. The monitor's report will record the date/time, storage pool number, total pages, number in use, number free, percent used, number of extents, and short-on-storage indicator.
Figure 168. POOL Usage Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => SP | | || Monitor Type => POOL USAGE Pool Usage Monitor | | || | | || POOL Number => ___ (Storpool number to be monitored; | | || leave BLANK to monitor ALL storpools) | | || | | || Percent Used=> ___ (Percent of storpool pages in use) | | || | | || | | || | | || | | || NOTE: NOTIFICATION occurs if any STORPOOL exceeds the specified value | | || | | || Enter parameter values to be checked by monitor, | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | |*---------------------------------------------------------------SQMMNSE-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
SHOW POOL is the database operator command used by this monitor. If the report option (see Monitor Scheduling Panel) is selected, the results of the command are logged.
This monitor can be used to record the changes in a database's internal counter(s). The COUNTER operator command will be issued to the database at the frequency that you designate for this monitor. Refer to Figure 169. The information returned will then be recorded in the monitor's report log, so that you can monitor changes in counter(s) values.
Specify only those counter(s) that you want to monitor, or specify the ALL COUNTERS option to have all the internal database counters monitored. Place ON next to those counter names that you want to have monitored, and OFF next to the counter names that will not be monitored.
This monitor is used for report purposes only and does not perform condition notification; therefore, be sure to specify the report option (see Monitor Scheduling Panel) for this monitor.
| Usage Consideration: | The Reset Counters monitor can be used to set counter values to zero at regular intervals. |
Figure 169. Database Counters Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => COUNTMON | | || Monitor Type => DB COUNTERS | | || | | || ALL COUNTERS => NO (YES/NO for ALL COUNTERS) | | || (Indicate ON or OFF next to each counter) | | || RDSCALL => OFF DBSSCALL => OFF BEGINLUW => OFF | | || ROLLBACK => OFF CHKPOINT => OFF LOCKLMT => OFF | | || ESCALATE => OFF WAITLOCK => OFF DEADLCK => OFF | | || LPAGBUFF => OFF PAGEREAD => OFF PAGWRITE => OFF | | || LDIRBUFF => OFF DIRREAD => OFF DIRWRITE => OFF | | || LOGREAD => OFF LOGWRITE => OFF DASDREAD => OFF | | || DASDWRIT => OFF DASDIO => OFF | | || | | || Specify UP to 8 counter(s) to be monitored (or YES for ALL), | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | |*---------------------------------------------------------------SQMMNCO-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
The COUNTER database operator command is used by this monitor. If the report option (see Monitor Scheduling Panel) is selected, the results of the command are logged.
This tool resets database counter(s) on a regular basis. The report log for this monitor will record the date and time that the counter(s) are reset.
Specify only those counter(s) that you want to reset, or specify the RESET ALL option to have all the internal database counters reset. Place "ON" next to those counter names that you want to have reset, and "OFF" next to the counter names that will not be reset. Refer to Figure 170.
Figure 170. Reset Counters Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Type => RESET COUNTERS | | || Monitor Name => RESETCON | | || | | || Specify ALL or specific counters(ON/OFF) to be reset: | | || RESET ALL => NO | | || RDSCALL => OFF DBSSCALL => OFF BEGINLUW => OFF | | || ROLLBACK => OFF CHKPOINT => OFF LOCKLMT => OFF | | || ESCALATE => OFF WAITLOCK => OFF DEADLCK => OFF | | || LPAGBUFF => OFF PAGEREAD => OFF PAGWRITE => OFF | | || LDIRBUFF => OFF DIRREAD => OFF DIRWRITE => OFF | | || LOGREAD => OFF LOGWRITE => OFF DASDREAD => OFF | | || DASDWRIT => OFF DASDIO => OFF | | || | | || Specify counter(s) to be reset by the monitor, | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | |*---------------------------------------------------------------SQMMNRC-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
The RESET database operator command is used by this monitor. If the report option (see Monitor Scheduling Panel) is selected, then the date and time of the counter reset is logged.
This monitor collects internal information about data spaces usage in a VM/ESA environment.
The COUNTER INTERNAL command will be issued at the frequency that you designate for this monitor. The information captured will be recorded in the monitor's report log, so that you can monitor changes in counter(s) values. Refer to Figure 171.
Figure 171. VMDSS Internal Counters Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => VMDSS | | || Monitor Type => INTERNAL COUNTERS | | || | | || ALL COUNTERS => NO (YES/NO for ALL COUNTERS) | | || (Indicate ON or OFF next to each counter) | | || ESASEG => OFF MAPSEGPG => OFF REQMAPPG => OFF MAPPG => OFF | | || SAVESLD => OFF SAVEMXRN => OFF SAVEBLK => OFF WAITSLD => OFF | | || REFBLOCK => OFF REFBPAGE => OFF REFBSPAN => OFF REFLST => OFF | | || REFLPAGE => OFF DIAG10 => OFF DIAG10PG => OFF SCDIAG10 => OFF | | || SCREF => OFF SCBLKREF => OFF SCSPNREF => OFF SAVEGNRL => OFF | | || SAVECHK0 => OFF SAVECHK1 => OFF | | || | | || Specify UP to 7 counter(s) to be monitored (or YES for ALL), | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | |*---------------------------------------------------------------SQMMNCI-----* | | PF: 1 Help 3 End (Cancel) | | | | | | | +--------------------------------------------------------------------------------+
Specify only those counter(s) that you want to monitor, or specify the ALL COUNTERS option to have all the internal counters monitored. Place "ON" next to those counter names that you want to have monitored, and "OFF" next to the counter names that will not be monitored.
This monitor is used for report purposes only and does not perform condition notification; therefore, be sure to specify the report option for it.
| Usage Consideration: | The Reset Internal Counter command can be used to set values to zero. |
The COUNTER INTERNAL operator command is used by this monitor. If the report option is selected, the results of this command are logged.
This tool monitors the performance of VM Data Spaces Support and the standard database DASD I/O system.
The COUNTER POOL command displays two sets of counters. One is for storage pools using Data Spaces Support, a database directory using Data Spaces Support, and unmapped internal dbspaces. The other set is for pools using the standard database DASD I/O system and a directory using the standard system.
This monitor can be utilized to collect performance information for a single storage pool, the database directory, the unmapped internal dbspaces or all storage pools plus the database directory and unmapped internal dbspaces.
The COUNTER POOL command will be issued at the frequency you designate. The information captured will be recorded in the monitor's report log, so that you can monitor changes in the counter pool values. Refer to Figure 172.
Figure 172. VMDSS Pool Counters Monitor Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------ Database Monitor Addition ------------------------* | || Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Name => DSSPOOL | | || Monitor Type => POOL COUNTERS | | || Counter Pool type => ___ (Enter one of the following to be monitored | | || | | || | | || a Storpool number, or | | || DIR - for database directory, or | | || UNM - for Unmapped internal dbspaces, or | | || * - for all storpools, database directory| | || and unmapped internal dbspaces.) | | || | | || NOTE: Remember to specify the report option. | | || | | || Enter Pool Type(s) to be checked by the monitor | | || then press ENTER to CONTINUE or PF3 to CANCEL | | || | | |*---------------------------------------------------------------SQMMNCI-----* | | PF: 1 Help 3 End (Cancel) | | | | | +--------------------------------------------------------------------------------+
Specify only the counter pool type that you want to monitor; using a Storpool number, DIR (Directory), UNM (Unmapped Internal Dbspaces), or * to have all of the environment monitored (storage pools, the database directory, and unmapped internal dbspaces).
The counter pool monitor is used for report purposes only and does not perform condition notification; therefore, be sure to specify the report option.
| Usage Consideration: | The Reset Pool command can be used to set values to zero. |
The COUNTER POOL operator command is used by this monitor. If the report option is selected, the results of this command are logged.
You can specify or change monitor scheduling information each time you use the Add (A) or Modify (M) options from the Main Monitor panel. After indicating any conditions or thresholds to be scanned for, you will be presented with the panel shown in Figure 173.
The scheduling or rescheduling of a database monitor automatically occurs after the addition of a new monitor, or after the successful modification of an existing monitor.
To deactivate (stop a monitor from running or being scheduled to run), use the Modify (M) option from the Main Monitor panel. On the monitor schedule panel (Figure 173), set the Active entry field to N; the monitor will be deactivated and removed from the schedule and will not be rescheduled to run until the Active entry field is set to Y.
Figure 173. Monitor Scheduling Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy Control Center hh:mm:ss | |*------------------------- Database Monitor Addition -------------------------* | ||Command ==> CTRLID: MSTRSRV1 | | || Database => SQLDBA NODE: VMSYSTM1 | | || Monitor Type => DATABASE LOG CHECK | | || Monitor Name => LOGCHECK | | || Active => Y (YES/NO) | | || | | || Run Days => MON TUE WED THU FRI SAT SUN (MON,TUE,WED,...) | | || Start Time => 06:15 (hh:mm) | | || Stop Time => 24:00 (hh:mm, >= start time) | | || Frequency => 15M (nnt, t=H or M HR/MIN) | | || Notify - Detect => N (YES/NO) | | || | | || Generate Report => Y (YES/NO) | | || Report Reset => SUN (MON,TUE,WED,...) | | || Send Reports To => MSTRUSR/VMSYSTM1 (Userid/Nodeid OR Nickname) | | || Enter all parameters and press PF2 to install MONITOR | | || | | |*--------------------------------------------------------------SQMNTR05-------* | | PF: 1 Help 2 Process (SAVE) 3 End (CANCEL) | | | +--------------------------------------------------------------------------------+