Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Statements and commands for UDSMON

&pagelevel(3)&pagelevel

A distinction is made between UDSMON statements for starting and UDSMON commands during execution.

UDSMON statements for starting

Statement                                                  

Meaning

CONFNAME=confname

Allocates configuration

HELP

Lists all UDSMON statements

MASK={S | C | ALL | CS | DC |
      DT | D}

Assigns output mask(s)

At the defined interval, UDSMON displays:
S : the STATUS mask
C : the COUNTER mask
ALL : all masks in turn
CS : the COUNTER mask and the STATUS mask alternately
DC : the CONNECT mask
DT : the TRANSACTION mask
D : the TRANSACTION mask and the CONNECT mask alternately

Default value : S

MEDIUM={T,n |
        L,n[,D] |
        F,n[,D] |
        S,n}

Assigns output device and time interval

T : output to data display terminal
L : output to printer
F : output to a file
S : transfer to SM2
Default value :
T in interactive mode
L in batch mode

n : time interval, in seconds, between queries (n=5..999); for output to printer: between queries (n=1..999)
Default value : 10

D : specifies that UDS-D operation is to be evaluated.
With output to a file, an extra label and, at the set intervals, an extra data record are written.
With output to a printer, the information from the masks DC (CONNECT) and DT (TRANSACTION) is added.

DISPLAY={DEPRECATED |
          EXPENSIVE |
         MESSAGES |
         DBCOUNTERS}

Output to intermediate file (cf. corresponding command during operation, see table 27)
The command is noted and executed at startup.

REBASE-COUNTER=NEW

Requests a logical zero point exclusively for the session counters of the counter mask

RUNTIME=n

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)
The time specified here should be greater than the time interval for the allocated output media.

START

Starts UDSMON
Data collection commences.

END

Terminates UDSMON
No data is collected.

Table 26: UDSMON statement for starting

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

INFORM-PROGRAM
 MSG='ADD MEDIUM= {T,n |

                   L,n[,D] |
                   F,n[,D] |
                   S,n}'

Assigns output device and time interval

T : output to data display terminal
L : output to printer
F : output to a file
S : transfer to SM2
Default value :
T in interactive mode
L in batch mode

n : time interval, in seconds, between queries (n=5..999); for output to printer: between queries (n=1..999)
Default value : 10

D : specifies that UDS-D operation is to be evaluated.
With output to a file, an extra label and, at the set intervals, an extra data record are written.
With output to a printer, the information from the masks DC (CONNECT) and DT (TRANSACTION) is added.

INFORM-PROGRAM
 MSG='DISPLAY'

Lists devices and time intervals currently set

INFORM-PROGRAM
 MSG='DISPLAY CP-SIZE'

Lists number and size of common pools

INFORM-PROGRAM
 MSG='DISPLAY DB-IO-COUNTER'

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

INFORM-PROGRAM
 MSG='DISPLAY DEPRECATED'

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.

INFORM-PROGRAM
 MSG='DISPLAY EXPENSIVE'

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
and per transaction, separated according to UTM and TIAM applications

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 MESSAGES'


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.
In the case of consecutive commands in a monitor run with explicit allocation of the intermediate files, messages which have been added since the previous DISPLAY MESSAGES command are supplemented. Messages which are overwritten in the buffer and can therefore no longer be listed are tagged with a separate flag. The date change is displayed.

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.

INFORM-PROGRAM
 MSG='DISPLAY REX'

Displays total number of transactions opened using READY EXCLUSIVE or READY PROTECTED

INFORM-PROGRAM
 MSG='DISPLAY SATURATION'

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)

INFORM-PROGRAM
 MSG='DISPLAY TASK'

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:

  • whether this termination has been completed successfully and the internal UDS resources can be reused (RELEASED),

  • whether termination has not yet been fully completed (PENDING) or

  • whether the relevant internal UDS resource is locked permanently because of a serious error (BLOCKED).

INFORM-PROGRAM
 MSG='END'

Terminates the monitor

INFORM-PROGRAM
 MSG='FINISH MEDIUM={T |
                     L[,D] |

                     F[,D] |
                     S}'

Terminates output on an output device

T : output to data display terminal
L : output to printer
F : output to a file
S : transfer to SM2
D : Only output for UDS-D operation is terminated. With output to a printer, the information from the masks DC (CONNECT) and DT (TRANSACTION) is omitted. With output to a file, the UDS-D record is omitted.

INFORM-PROGRAM
 MSG='HELP'

Lists input options

INFORM-PROGRAM
 MSG='MASK={S | C | ALL | CS |
           DC | DT | D}'

Assigns output mask(s)
At the defined interval, UDSMON displays:

S : the STATUS mask
C : the COUNTER mask
ALL : all masks in turn
CS : the COUNTER mask and the STATUS mask alternately
DC : the CONNECT mask
DT : the TRANSACTION mask
D : the TRANSACTION mask and the CONNECT mask alternately
Default value : S

INFORM-PROGRAM
 MSG='REBASE-COUNTER=NEW'

Rebasing of the counters of the COUNTER mask, i.e. requesting a logical zero point exclusively for the session counters of the COUNTER mask
The next time the counters are collected, the current statuses of the COUNTER mask will be stored ("rebasing" or "snapshot" of the current counter statuses), and from then all counter statuses are specified with reference to this stored status (logical zero point).

Rebasing can be used for the following in the case of extremely long DBH sessions:
- to display comparable session counters, for example on a daily or weekly basis
- to facilitate recognition of a change to counter statuses
- to prevent problems in comparative interpretation when individual counters overrun

Rebasing always refers to a single monitor instance. It is not possible to return to a previous rebasing.
The values for a rebasing remain valid as long as the corresponding DBH session or the UDS monitor continues to run.

The following events invalidate rebasing:
- Restart of the DBH session
When the DBH session restarts, the DBH’s counters once more begin with 0.
- Restart of the UDS monitor
As the rebasing data is located locally in the monitor memory, it is lost when the monitor restarts.

INFORM-PROGRAM
 MSG='REBASE-COUNTER=OFF'

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.

Table 27: UDSMON commands during operation