A distinction is made between UDSMON statements for starting and UDSMON commands during execution.
UDSMON statements for starting
Statement | Meaning |
| Allocates configuration |
| Lists all UDSMON statements |
| Assigns output mask(s) At the defined interval, UDSMON displays: Default value : S |
| Assigns output device and time interval T : output to data display terminal n : time interval, in seconds, between queries (n=5..999); for output to printer: between queries (n=1..999) D : specifies that UDS-D operation is to be evaluated. |
| Output to intermediate file (cf. corresponding command during operation, see table 27) |
| Requests a logical zero point exclusively for the session counters of the counter mask |
| Specifies the time after which UDSMON is to terminate automatically. This statement can be used particularly in batch mode, e.g. to obtain output to printer after a specified time. n : runtime in seconds (n = 60..86400) |
| Starts UDSMON |
| Terminates UDSMON |
UDSMON commands during execution
Execution of UDSMON can be interrupted to list or modify the specified devices, masks or time intervals.
Interruption is initiated by means of:
EM, DUE
followed by the command INFORM-PROGRAM MSG = ... [, JOB-ID=*OWN'].
Command | Meaning |
| Assigns output device and time interval T : output to data display terminal n : time interval, in seconds, between queries (n=5..999); for output to printer: between queries (n=1..999) D : specifies that UDS-D operation is to be evaluated. |
| Lists devices and time intervals currently set |
| Lists number and size of common pools |
| Lists all database I/Os that have occurred since starting the DBH and in the last time interval. The database I/Os are arranged in categories (2-Kbyte, 4-Kbyte, 8-Kbyte, and exclusive I/Os) and further subdivided into logical and physical read/write I/Os per category |
| List of applications with properties which contain a potential risk (limited address space utilization, obsolete loading technique, subschema validation missing) The list is written to the intermediate file (see section “DISPLAY output of the UDS monitor to intermediate files”) and displayed by the monitor by means of a SHOW-FILE command. |
| List of applications with the greatest resource utilization with regard to transaction duration, number of DMLs per transaction, number of logical inputs/outputs per DML The list is written to the intermediate file (see section “DISPLAY output of the UDS monitor to intermediate files”) and displayed by the monitor by means of a SHOW-FILE command. |
| Edited list of buffered DBH messages The list is written to the intermediate file (see section “DISPLAY output of the UDS monitor to intermediate files”) and displayed by the monitor by means of a SHOW-FILE command. |
INFORM-PROGRAM MSG='DISPLAY DBCOUNTERS' | Displays the number of DMLs and I/Os per database since starting the DBH and while database is online. The list is written to the intermediate file (see section “DISPLAY output of the UDS monitor to intermediate files”) and displayed by the monitor by means of a SHOW-FILE command. |
| Displays total number of transactions opened using READY EXCLUSIVE or READY PROTECTED |
| List of the greatest saturation of central system resources in the DBH session to date (e.g. number of parallel transactions, utilization of non-extensible memory pools) |
| Lists all the user tasks associated with UDS/SQL and the number of DMLs already processed in these tasks In the case of the processed DMLs, in contrast to comparable values of the counter mask, for diagnostic reasons requests of the COBOL runtime system which ensure correct transaction processing in the case of a task switch are also counted. For applications which were terminated asynchronously, e.g. as a result of timeouts in UTM applications, the following is also output:
|
| Terminates the monitor |
| Terminates output on an output device T : output to data display terminal |
| Lists input options |
| Assigns output mask(s) S : the STATUS mask |
| Rebasing of the counters of the COUNTER mask, i.e. requesting a logical zero point exclusively for the session counters of the COUNTER mask Rebasing can be used for the following in the case of extremely long DBH sessions: Rebasing always refers to a single monitor instance. It is not possible to return to a previous rebasing. The following events invalidate rebasing: |
| The counter statuses of the COUNTER mask which are used for rebasing are set to 0. As a result, the session counters in the COUNTER mask are once more displayed as absolute values with reference to the start of the DBH session. |