This report contains data of the SESAM/SQL database system.
Report output
The REPORT SESAM_SQL statement is used to request the output of the SESAM SQL report.
The SESAM SQL report can only be output if
SESAM/SQL has been prepared for data to be sent to SM2 (see "SESAM-SQL Monitored data for the SESAM/SQL database system")
the SM2 administrator has activated the monitoring process using the
START-MEASUREMENT-PROGRAM TYPE=*SESAM-SQL statement.
Overflow screens may be requested for this report.
The monitored data output is sorted under the category DB CONF.
HOST0001 SM2 SESAM SQL CYCLE: 30 S <date> <time>
DB CONF | UPDTA | RETTA | RESTA | PLGEN | RDSYS | WRSYS | RDUSR | WRUSR
| (1/S) | (1/S) | (1/S) | (1/S) | (1/S) | (1/S) | (1/S) | (1/S)
--------+-------+-------+-------+-------+-------+-------+-------+------
SESAMEW | 2.4 | 2.4 | 4.8 | 1.4 | 70.3 | 10.0 |3837.2 | 7.4
Monitoring information
DB CONF | Name of the DB configuration |
UPDTA (1/S) | Number of update transactions per second |
RETTA (1/S) | Number of retrieval transactions per second |
RESTA (1/S) | Number of reset transactions per second |
PLGEN (1/S) | Number of SQL plan generations per second |
RDSYS (1/S) | Number of logical read accesses to the system data buffer |
WRSYS (1/S) | Number of logical write accesses to the system data buffer |
RDUSR (1/S) | Number of logical read accesses to the user data buffer |
WRUSR (1/S) | Number of logical write accesses to the user data buffer |
The monitored data is supplied by SESAM/SQL asynchronously to SM2 and applies for one or more cycles which are defined by SESAM/SQL and need not match the SM2 cycle. Here differences can exist in the duration of the cycles, and time displacements can also exist between the SESAM/SQL and SM2 cycles. The duration of one or more SESAM/SQL cycles is used to standardize the monitored data to one second. The data is therefore exact, but it only matches the SM2 cycle to a certain degree.