UDS SQL report

This report contains data of the UDS/SQL database system.

Report output

The REPORT UDS_SQL statement is used to request the output of the UDS SQL report.

The UDS SQL report can only be output if

• UDS/SQL has been prepared for data to be sent to SM2 (see "Monitored data for the UDS/SQL database system")

• the SM2 administrator has activated the monitoring process using the
  START-MEASUREMENT-PROGRAM TYPE=*UDS-SQL statement.

Overflow screens may be requested for this report.
The monitored data output is sorted under the category DB CONF.

 HOST0001 SM2 UDS SQL             CYCLE:   30 S                   <date>  <time>

  DB CONF        |  DML  |  TA   | UPDTA | LREAD | PREAD | PWRIT | LCKWT | DLOCK
                 | (1/S) | (1/S) | (1/S) | (1/S) | (1/S) | (1/S) | (1/S) | (1/S)
 ----------------+-------+-------+-------+-------+-------+-------+-------+------
 Q1254KON        | 229.2 |  11.4 |  10.4 |1676.4 | 366.2 | 185.2 |  21.6 |   9.1

Monitoring information

DB CONF	Name of the DB configuration
DML (1/S)	Number of CODASYL and SQL statements per second
TA (1/S)	Number of transactions per second
UPDTA (1/S)	Number of update transactions per second
LREAD (1/S)	Number of logical read accesses to the databases per second
PREAD (1/S)	Number of physical read accesses to the databases per second
PWRIT (1/S)	Number of physical write accesses to the databases per second
LCKWT (1/S)	Number of wait states for locks per second
DLOCK (1/S)	Number of data deadlocks per second

The monitored data is supplied by UDS/SQL asynchronously to SM2 and applies for one or more cycles which are defined by UDS/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 UDS/SQL and SM2 cycles. The duration of one or more UDS/SQL cycles is used to standardize the monitored data to one second. The values are therefore exact, but they only match the SM2 cycle to a certain degree.