Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Description of UDS/SQL monitor output to data display terminal

&pagelevel(3)&pagelevel

The masks output on the data display terminal by the UDS/SQL monitor (UDS monitor masks STATUS and COUNTER and UDS-D monitor masks TRANSACTION and CONNECT) are described below.

Description of the UDS/SQL monitor mask: STATUS

 UDS/SQL-MONITOR 2.9 * DB-CONFNAME: EXAMPLES                     DATE: 2019-01-29
 STATUS              * INTERV. SEC: 030 TSKCON: 002 TAACT: 0002  TIME: 13:49:46 
 *********************
      TA     DML     SQLTA SQLDML RDMLO RDMLI LRDDB PRDDB LWRDB PWRDB PRDRL PWRRL
 IV:  000000 0000000 00000 000000 00000 00000 00000 00000 00000 00000 00000 00000
 PROGRAM  TSN  RUN-ID   MO ST DB-NAME  CALLS   DML  RDML  LRDDB PRDDB LWRDB PWRDB
 IQS      3VKT 00000004 SR IO VERSAND  FTC4R   0006 0000  00012 00005 00000 00000
 IQS      3VMT 00000005 SU US KUNDEN   READY   0001 0000  00000 00000 00000 00000
 --------------------------------------------------------------------------------
 LTG                                                         TAST

In the two header lines the UDS/SQL monitor outputs information on the database configuration, current date, output frequency and time:

DB-CONFNAME : confname

name of the DB configuration

DATE : yyyy-mm-dd

current date (year, month, day)

INTERV. SEC: nnn

time interval in seconds for mask output

TSKCON:

number of user tasks connected to UDS/SQL

TAACT:

number of active transactions at the end of an interval

TIME : hh:mm:ss

time (hour, minute, second)

The subsequent lines contain information on the internal counter values of the last output interval and on the transactions currently active.

Information on a maximum of 16 active transactions is displayed in this mask, sorted in increasing order of transaction identifier. In the event of more than 16 active transactions, the 16 oldest are output.

IV (interval):

TA

number of transactions

DML   

number of CODASYL statements and SQL statements

SQLTA


number of SQL transactions

SQLDML


number of SQL statements


For UDS-D:

RDMLO


number of DML statements sent to remote partner configurations for processing


For UDS-D:

RDMLI


number of DML statements received from remote partner configurations for processing

LRDDB


number of logical read calls (READ) to the databases

PRDDB


number of physical read calls (READ) to the databases

LWRDB


number of logical write calls (WRITE) to the databases

PWRDB


number of physical write calls (WRITE) to the databases

PRDRL


number of physical read calls (READ) to the RLOG file

PWRRL


number of physical write calls (WRITE) to the RLOG file; if duplicate RLOG files are maintained, the calls are counted only once

For each active transaction, the following information is provided on the program(s) started: 

PROGRAM


progname
In timesharing mode: name of the application program
In transaction mode: database key (openUTM)

For UDS-D:

If progname is followed by an ‘*‘, it designates a secondary subtransaction, i.e. the application program was started in another configuration.

TSN

tsn
In timesharing mode: task serial number under which the program progname runs;
In transaction mode: task serial number of the last openUTM task used in the transaction.

RUN-ID


transaction-id

Internal transaction identifier assigned by UDS/SQL. Transactions are numbered consecutively within a session.

MO

open mode of the transaction

SR       SHARED RETRIEVAL
SU       SHARED UPDATE
PR       PROTECTED RETRIEVAL
PU       PROTECTED UPDATE
ER       EXCLUSIVE RETRIEVAL
EU       EXCLUSIVE UPDATE

ST

current transaction status

AR=AREA
The transaction is in the process of executing a READY statement in a realm queue; it is currently unable to access a requested realm.

CA=IN CANC
The CANCEL request is being processed or

CA=TO CANC
a CANCEL request for the transaction is pending

CC=CONNEC
Control of the transaction resides in the connection module

DH=DBH
DML is being processed by the DBH

IO=INPUT/OUTPUT
The transaction is waiting for the end of an asynchronous input or output operation

LO=LOCK
The transaction is waiting for a page lockout to be canceled

SM=SEMAPHOR
The transaction is waiting for a code lock to be canceled

SP=STOP
The transaction is in the STOP state or

SP=TOSTOP
a STOP request is pending

ST=SERVERTASK
The transaction is waiting for a free server task

US=USER
DML with the user

DB-NAME


dbname 
Name of the database being processed by the current DML statement

CALLS


Short function names for DML and SQL statements (see DAL command DISPLAY SQL "Displaying information on an SQL conversation (DISPLAY SQL)" and section “Function codes of the DML statements”).

DML

serial number of DML statement of the transaction:

For UDS-D:

  • progname *:

    serial DML number of a secondary subtransaction (application program in another configuration)

  • progname without *:

    serial DML number of a purely local transaction or, if RDML counter allocated,
    serial DML number of a primary subtransaction


RDML

For UDS-D:
serial number of the remote DML statement sent to another configuration (remote DML)

LRDDB


number of logical read calls (READ) to the databases

PRDDB


number of physical read calls (READ) to the databases

LWRDB


number of logical write calls (WRITE) to the databases

PWRDB


number of physical write calls (WRITE) to the databases

Description of the UDS/SQL monitor mask: COUNTER

 UDS/SQL-MONITOR 2.9 *   DB-CONFNAME : EXAMPLES              DATE    : 2019-01-28
 COUNTER             *   MACHINE TYPE:  S190-40              TIME    : 13:13:16
 *********************   MAIN MEMORY : 001232 MB             INTERVAL: 030 SEC
                    SESSION    INTERVAL                       SESSION    INTERVAL
 SQL CONVERSATIONS  0000000000 00000000  LOGICAL  READ DB     0000000140 00000010
 TRANSACTIONS       0000000005 00000000  PHYSICAL READ DB     0000000074 00000005
 SQL TRANSACTIONS   0000000000 00000000  PHYSICAL READ RLOG   0000000000 00000000
 UPDATE TRANSACT.   0000000000 00000000  LOGICAL  WRITE DB    0000000000 00000000
 REMOTE UPD. TRANS. 0000000000 00000000  PHYSICAL WRITE DB    0000000000 00000000
 DML CALLS          0000000049 00000005  PHYSICAL WRITE RLOG  0000000004 00000000
 SQL CALLS          0000000000 00000000  PHYSICAL WRITE ALOG  0000000000 00000000
 RDML OUT           0000000000 00000000
 RDML IN            0000000000 00000000  DATA   DEADLOCKS     0000000000 00000000
                                         GLOBAL DEADLOCKS     0000000000 00000000
 ITC ST --> US      0000000049 00000005  LOCK WAITS           0000000000 00000000
 ITC US --> ST      0000000049 00000005
 REQUEST ST --> ST  0000000022 00000005  PPP OK                   100.0%   ---.-%
 ITC ST--> ST       0000000000 00000000  AVG TRANSACTION TIME   000.700s 000.300s
 PP TRANSACTION     DEF  0004  ACT 0002  PP SQL               DEF  0004 ACT  0000
 PP SEC. TRANSACT.  DEF  0001  ACT 0000  PP SERVERTASK        DEF  0001 FREE 0001
 SEC. TRANSACT. OUT            ACT 0000  PP 2KB/4KB/8KB-BUFFERSIZE 0001/0001/0000
 --------------------------------------------------------------------------------
 LTG                                                         TAST

The three header lines contain information on the database configuration, current date and time, output frequency and hardware used.

DB-CONFNAME : confname

name of the database configuration

DATE : yyyy-mm-dd

current date (year, month, day)

MACHINE TYPE : XXXXXXXX

name of the system (up to eight characters), e.g. "S190-40"

TIME : hh:mm:ss

time (hour, minute, second)

MAIN MEMORY : nnnn.n MB

size in Mbytes of usable main memory

INTERVAL: nnn

time interval in seconds for mask output 

The subsequent lines list information on internal counter values since the start of the session and during the last output interval:

SQL CONVERSATIONS

number of SQL conversations processed 

TRANSACTIONS

number of CODASYL and SQL transactions

SQL TRANSACTIONS

number of SQL transactions

UPDATE TRANSACT.

number of update CODASYL and SQL transactions

REMOTE UPD. TRANS.

number of transactions with update in a remote partner configuration

DML CALLS

number of CODASYL statements and SQL statements

SQL CALLS

number of SQL statements


For UDS-D:

RDML OUT

number of DML statements sent to remote partner configurations for processing (remote DML)


For UDS-D:

RDML IN

number of DML statements received from remote partner configurations for processing

ITC ST --> US

number of performed inter-task communications (ITC) from the server task (ST) to the user (US)

ITC US --> ST

number of performed inter-task communications (ITC) from the user (US) to the server task (ST)

REQUESTS ST --> ST

sum of all requests from server task (ST) to server task

ITC ST --> ST

number of performed inter-task communications (ITC) from server task (ST) to server task

LOGICAL READ DB

number of logical read calls to the databases (READ) 

PHYSICAL READ DB

number of physical read calls to the databases (READ)

PHYSICAL READ RLOG

number of physical read calls to the RLOG file

LOGICAL WRITE DB

number of logical write calls to the databases (WRITE)

PHYSICAL WRITE DB

number of physical write calls to the databases (WRITE)

PHYSICAL WRITE RLOG

number of physical write calls to the RLOG file; with duplicate RLOG backup, calls are counted only once

PHYSICAL WRITE ALOG

number of physical write calls to the ALOG file

DATA DEADLOCKS

number of data deadlocks

GLOBAL DEADLOCKS

number of task deadlocks during openUTM operation and interconfiguration deadlocks (if UDS-D is used)

LOCK-WAITS

number of lock waits

PPP OK

number of successful attempted accesses via probable position pointer (PPP) in percent

AVG TRANSACTION TIME

average transaction times in seconds, e.g. 0.099 sec 

The following lines provide information on the DBH load parameters, as defined (DEF) on starting the DBH, and the extent to which the requested resources are being used (FREE/ACT):

PP TRANSACTION DEF

maximum possible number of simultaneously active transactions = value in PP TRANSACTION

For UDS-D:
primary and secondary subtransactions and local transactions

PP TRANSACTION ACT

number of active transactions

For UDS-D:
primary and secondary subtransactions and local transactions currently being processed by this DBH

PP SEC. TRANSACT. DEF

For UDS-D:
maximum possible number of secondary subtransactions that can be processed by this DBH (value m in PP TRANSACTION)

PP SEC. TRANSACT. ACT

For UDS-D:
number of active secondary subtransactions (STTs) currently being processed by this DBH

SEC. TRANSACT. OUT ACT

For UDS-D:
number of active secondary subtransactions (STTs) if the application program is in its own configuration

PP SQL DEF

number of SQL conversations defined with PP SQL

PP SQL ACT

number of active SQL conversations

PP SERVERTASK DEF

number of server tasks defined with PP SERVERTASK

PP SERVERTASK FREE

number of free server tasks

PP 2KB/4KB/8KB-BUFFER-SIZE

size of system buffer pools in Mbytes; as specified for PP 2KB-BUFFER-SIZE, PP 4KB-BUFFER-SIZE and PP 8KB-BUFFER-SIZE, respectively.

Description of the UDS-D monitor mask: TRANSACTION

 UDS/SQL-MONITOR 2.9 * DB-CONFNAME: EXAMPLES                     DATE: 2019-01-29
 UDS-D   TRANSACTION * INTERVAL   : 030 SEC     PARTNER: 0002    TIME: 14:03:27
 *********************
 IV:  TA     DML     SQLTA SQLDML       LRDDB PRDDB  LWRDB PWRDB  PRDRL PWRRL
      000045 0000612 00000 000000       01024 00000  00260 00000  00000 00040
 SUM:           STT-OUT          STT-IN           RDML-OUT         RDML-IN
            SESSION  INTERV  SESSION  INTERV   SESSION  INTERV  SESSION  INTERV
            00000390 000022  00000620 000022   00005455 000306  00008646 000302
 CONFNAM
 BEISP02    00000390 000022  00000620 000022   00005455 000306  00008646 000302
 BEISP01    00000000 000000  00000000 000000   00000000 000000  00000000 000000
 --------------------------------------------------------------------------------
 LTG                                                         TAST

In the two header lines the UDS/SQL monitor outputs information on the database configuration, current date, output frequency, number of partner configurations, and time:

DB-CONFNAME : confname

name of the home DB configuration

DATE : yyyy-mm-dd

current date, specified as year, month, day

INTERVAL: nnn

time interval in seconds for mask output

PARTNER

number of partner configurations known to this configuration

TIME: hh-mm-ss

time, specified as hour, minute, second

The following lines contain information on the internal counter values of the last output interval.

Information on a maximum of 13 partners is displayed in this mask.

First there is a list of the partners in which or by which DML statements were processed in the most recent output interval, followed by a list of all other known partners.

IV (interval):

TA

number of transactions

DML

number of CODASYL statements and SQL statements

SQLTA

number of SQL transactions

SQLDML

number of SQL statements

LRDDB

number of logical read calls (READ) to the databases

PRDDB

number of physical read calls (READ) to the databases

LWRDB

number of logical write calls (WRITE) to the databases

PWRDB

number of physical write calls (WRITE) to the databases

PRDRL

number of physical read calls (READ) to the RLOG file

PWRRL

number of physical write calls (WRITE) to the RLOG file; with duplicate RLOG backup, calls are counted only once

The following lines contain information concerning the sum of all partner configurations.
The counter values since the start of the session and during the last interval are output.

STT-OUT



total number of secondary subtransactions sent to remote partner configurations for processing

STT-IN



total number of secondary subtransactions sent from remote partner configurations for processing

RDML-OUT


number of DML statements sent to remote partner configurations for processing (remote DML)

RDML-IN



number of DML statements received from remote partner configurations for processing

The following lines contain information on the attached partner configurations:

CONFNAM



name of the partner configuration

STT-OUT



total number of secondary subtransactions sent to this partner configuration for processing

STT-IN



total number of secondary subtransactions received from this partner configuration for processing

RDML-OUT



number of DML statements sent to this partner configuration (remote DML)

RDML-IN



number of DML statements received from this partner configuration for processing

Description of the UDS-D monitor mask: CONNECT

 UDS/SQL-MONITOR 2.9 * DB-CONFNAME: EXAMPLES                     DATE: 2019-01-29
 UDS-D   CONNECT     * INTERVAL   : 030 SEC     PARTNER: 0002    TIME: 12:13:24
 *********************
 IV:  TA     DML     SQLTA SQLDML RDMLO RDMLI LRDDB PRDDB LWRDB PWRDB PRDRL PWRRL
      000047 0000657 00000 000000 00333 00322 01103 00000 00286 00000 00000 00044
 
 SUM:          CONNECT-OUT            CONNECT-IN        DISCON    GLOB-DEADLOCKS
          REQUEST REJECT ACTIVE  REQUEST REJECT ACTIVE  SESS      SESS
          0000005 000000 000002  0000007 000000 000000  000000    00000000000000
 CONFNAM
 BEISP02  0000005 000000 000002  0000007 000000 000000  000000
 BEISP01  0000000 000000 000000  0000000 000000 000000  000000
 --------------------------------------------------------------------------------
 LTG                                                         TAST

In the two header lines the UDS/SQL monitor outputs information on the database configuration, current date, output frequency, number of partner configurations, and time:

DB-CONFNAME : confname

name of the home DB configuration

DATE : yyyy-mm-dd

current date, specified as year, month, day

INTERVAL: nnn

time interval in seconds for mask output

PARTNER

number of partner configurations known to this configuration

TIME: hh-mm-ss

time, specified as hour, minute, second

The next lines contain information on the internal counter values of the last output interval.

Information on a maximum of 13 partners is displayed in this mask.

First there is a list of the partners to which there are currently active connections, followed by a list of all other known partners.

IV (interval):

TA

number of transactions

DML

number of CODASYL statements and SQL statements

SQLTA


number of SQL transactions

SQLDML


number of SQL statements

RDMLO


number of DML statements sent to remote configurations for processing

RDMLI


number of DML statements received from remote application programs for processing

LRDDB


number of logical read calls (READ) to the databases

PRDDB


number of physical read calls (READ) to the databases

LWRDB


number of logical write calls (WRITE) to the databases

PWRDB


number of physical write calls (WRITE) to the databases

PRDRL


number of physical read calls (READ) to the RLOG file

PWRRL


number of physical write calls (WRITE) to the RLOG file; with duplicate RLOG backup, calls are counted only once

The next lines contain information relating to the sum of all partner configurations. The counter values since the start of the session are output.

CONNECT-OUT

REQUEST
total number of connection requests issued to remote partner configurations in the course of the session

CONNECT-OUT

REJECT
total number of connection requests rejected by remote partner configurations

CONNECT-OUT

ACTIVE
total number of currently active connections to remote partner configurations requested by the home configuration

CONNECT-IN

REQUEST
total number of connection requests issued by remote partner configurations to the home configuration in the course of the session 

CONNECT-IN

REJECT
total number of connection requests from remote partner configurations rejected by the home configuration

CONNECT-IN

ACTIVE
total number of currently active connections to the home configuration requested by remote partner configurations

DISCON SESS

total number of connections to remote partner configurations cleared down by application programs of the local configuration in the course of the session due to errors. Reasons for disconnection:

  • CHECKTIME monitoring by the user

  • errors reported by DCAM

GLOB-DEADLOCKS SESS

total number of task deadlocks detected by the lock manager of the home configuration, i.e. task deadlocks that occur during openUTM operation and interconfiguration deadlocks when UDS-D is used.
There is assumed to be an interconfiguration deadlock when interconfiguration contention situations between distributed transactions are not resolved within a specified time. This time can be set with PP DEADTIME.

The following lines contain information on the attached partner configurations. The counter values since starting the DBH are output.

CONFNAM

name of the partner configuration

CONNECT-OUT

REQUEST
total number of connection requests issued to this partner configuration in the course of the session

CONNECT-OUT

REJECT
total number of connection requests rejected by this partner configuration in the course of the session

CONNECT-OUT

ACTIVE
total number of active connections to this partner.

A connection can be made to this partner configuration from any application program and from the UDS-D task of the home configuration. The home/remote UDS-D task connection is counted only in CONNECT-IN ACTIVE. 

CONNECT-IN

REQUEST
total number of connection requests issued by this partner configuration in the course of the session

CONNECT-IN

REJECT
total number of connection requests from this partner configuration rejected by the home configuration

CONNECT-IN

ACTIVE
total number of currently active connections from this partner configuration to the home configuration.

A connection can be made from this partner configuration from any application program and from the remote UDS-D task.

DISCON SESS

total number of connections to this partner configuration cleared down in the course of the session due to errors

Powered by Atlassian Confluence and Scroll Viewport.