Output from KDCINF

Output is listed by type. The display shows all properties (LIST!= KDCNAMES). 

When you enter KDCINF ALL,LIST=KDCALL, with the exception of information about load modules and shared objects, all the items listed in the following section are output in succession.

type=CON

The output depends on whether a short or a long host name is assigned to a CON object. In the case of a long host name, the information on a CON object is output in two screen lines.

CON  PRONAM    LPAP  BCAMAPPL  STA     CONNECT    CTIME     LETTERS   CONB
con  proname   lpap  applname  ON|OFF  Y|N|W  A   minutes   number    number
CON  PRONAM    LPAP  BCAMAPPL  STA     CONNECT    CTIME     LETTERS   CONB
con  long.processor.name  
               lpap  applname  ON|OFF  Y|N|W  A   minutes   number    number

Explanation of the output

CON	The name for the logical connections to the partner application lpap created with KC_CREATE_OBJECT for the object type KC_CON or generated with the KDCDEF control statement CON.
PRONAM	Name of the computer on which the partner application runs.
LPAP	Logical name of the partner application for which the logical connection was generated.
BCAMAPPL	Name of the local UTM application (BCAMAPPL name) via which the connection to the partner application is established.
STA	Status of the partner application: ON: The partner application is not disabled. A connection can be established with it, or a connection already exists. OFF: The partner application is disabled. A connection cannot be established.
CONNECT	Several items of information are supplied here. 1st column: The partner application is connected to the application at this time (Y) or not (N), or UTM is attempting to establish a connection (W = waiting for a connection). 2nd column: openUTM will establish the connection to the partner application automatically (A) when the application starts, or UTM will not attempt to establish an automatic connection when the application starts (no output).
CTIME	Duration of connection time in minutes.
LETTERS	Number of messages that have been exchanged via the connection since the application started, i.e. the number sent or received by the local application. Every time the application starts, the counter is reset to 0.
CONB	Indicates how often the connection has failed since the application started. The CONB counter is reset to 0 every time the application starts.

type=KSET

The output illustrated below is only produced if a value <= 255 is specified in the MAX statement for the KEYVALUE operand during KDCDEF generation, i.e. if the application does not permit key codes with a number > 255.

KSET:kset

	0	1	2	3	4	5	6	.	.	.	18	19
0		x			x
20				x		x	x
40			x								x
60
80	x
100
120 . . .
240

Explanation of the output

KSET	Name of the key set

In the first line of the output, all key codes between 1 and 19 in the key set are displayed. Line two contains all key codes with numbers between 20 and 39 etc.

The last line displays key codes with numbers between 240 and 259.

The output illustrated here signifies that key set kset contains key codes 1, 4, 23, 25, 26, 42, 58 and 80.

type=LOAD-MODULE (BS2000 systems)

LOAD-MODULE         lmodname
VERSION (GENERATED) generated element version
VERSION (PREVIOUS)  previous element version
VERSION (CURRENT)   current element version
LIBRARY             name of program library
LOAD MODE           STATIC| STARTUP| ONCALL| POOL| POOL/STARTUP| POOL/ONCALL
CHANGEABLE          YES| NO
AUTOLINK            YES| NO
PROGRAM LIST
program1            program2
program3            program4

Explanation of the output

LOAD-MODULE
		Name of the load module up to 32 characters in length.
VERSION (GENERATED)
		Generated version of the load module
VERSION (PREVIOUS)
		Preceding version of the load module
VERSION (CURRENT)
		Currently loaded version of the load module
LIBRARY		Name for the program library of up to 54 characters loaded from the load module
LOAD MODE		Load mode for the load module; the following modes are possible:
	STATIC	Load mode for the load module; the following modes are possible:
	STARTUP	The load module is loaded dynamically as an independent unit whenever the application starts.
	ONCALL	The load module is loaded dynamically as an independent unit when a program unit or VORGANG exit assigned to the load module(s) is called for the first time.
	POOL	The load module is loaded into the common memory pool whenever the application starts. The load module does not contain a private slice.
	POOL/STARTUP
		The public slice of the load module is loaded into the common memory pool when the application starts. The private slice belonging to the load module is then loaded into the local process memory.
	POOL/ONCALL
		The public slice of the load module is loaded into the common memory pool when the application starts. The private slice belonging to the load module is loaded into the local process memory when the first program unit assigned to this load module is called.
CHANGEABLE
		Display showing whether or not the load module can be replaced during live operation.
AUTOLINK		Indicates whether the load module was loaded with the BLS autolink function.
PROGRAM LIST
		List of names of all program units and data areas (AREAs) assigned to the load module. The list also contains the names of all deleted objects.

type=LPAP

 LPAP    KSET          STATUS     OUT-Q   IDLETIME    MASTER        BUNDLE
 lpap    kset         ON|OFF   Q number    seconds    master         M|Y|N

Explanation of the output

LPAP	Logical name of the partner application in the local application (name of the LPAP partner)
KSET	Key set assigned to the partner application. The key set defines access rights to the partner application for the local application.
STA	Status of the partner application: 1st column: ON The partner application is not disabled. A connection can be established or a connection already exists. OFF The partner application is disabled. No connection can be established. 2nd column: Q (QUIET) No more dialog jobs will be accepted for the partner application.
OUT-Q	Number of messages in the message queue that still have to be sent to the partner application.
IDLETIME	Time until the disconnection of an unused connection (session) between the partner application and the local application.
MASTER	If the LPAP partner forms part of an LU6.1-LPAP bundle then the name of the master LU6.1-LPAP of the bundle is displayed
BUNDLE	Specifies whether the LPAP partner belongs to an LU6.1-LPAP bundle. M The LPAP partner is the master LU6.1 LPAP of an LPAP bundle. Y The LPAP partner is a slave LU6.1 LPAP of an LPAP bundle. N The LPAP partner does not belong to an LU6.1-LPAP bundle.

type=LSES

The output depends on whether a short or a long host name is assigned to a LSES object. In the case of a long host name, the information on a LSES object is output in two screen lines.

LSES    RSES    LPAP    CON      PRONAM    BCAMAPPL  AG/USER
lses    rses    lpap    con      proname   applname  user
 
LSES     PRONAM   CON      BCAMAPPL RSES     LPAP    AG/USER
lses     long.processor.name
                  con      applname rses     lpap    user

Explanation of the output

LSES	Name of the LU6.1 session in the local application
RSES	Name of the session in the partner application
LPAP	Logical name of the partner application for which the session is generated.
CON, PRONAM, BCAMAPPL
	Uniquely identifies the logical connection which was established for the session. con is the name created with KC_CREATE_OBJECT for the object type KC_CON or generated with the KDCDEF control statement CON for the logical connections to partner application lpap. proname is the name of the computer on which the partner application lpap is running. applname is the name of the local UTM application (BCAMAPPL name), via which the connection to the partner application was established.
AG/USER
	Name of the job submitter for whom the session is reserved. user indicates who started the job-submitting service. If the job-submitting service is running in the local application then the user ID or LTERM partner which started the service is entered against user. If the job-submitting service is running in the partner application (the local application is processing the job) or if asynchronous messages are transferred to the session, the local session name (LSES name) is issued for user, i.e. the outputs for LSES and AG/USER are identical.

type=LTAC

 LTAC LOCK    STATUS    RTAC   CODE    LPAP  ACCESSWAIT   REPLYWAIT USED   D
 ltac number  ON|OFF    rtac   I|P|T   lpap  seconds      seconds   number D

Explanation of the output

LTAC		Local TAC name for the service program in the partner application
LOCK		Lock code assigned to the remote service in the local application (access protection); a number between 1 and 4000.
STATUS		The transaction code LTAC is disabled (OFF) or not disabled (ON).
RTAC		Name of the transaction code/service program in the partner application
CODE		Indicates which code type is used internally by UTM for the RTAC name.
	I	Integer code type
	P	PRINTABLE-STRING code type
	T	T61 string code type
LPAP		Logical name of the partner application in the local application (name of the LPAP partner).
ACCESSWAIT
		Length of time openUTM waits for a session to be occupied (can include the time to establish a connection) when the remote service program starts;  time shown in seconds.  If the LTAC is an asynchronous TAC then a wait time != 0 signifies that the job is always entered in the message queue for the partner application.  The time is defined for KDCDEF generation and can be adjusted by administration (e.g. with the KDCAPPL TAC).
REPLYWAIT		Maximum length of time which UTM waits for a response from the remote service. The time is defined for KDCDEF generation and can be adjusted by administration (e.g. KDCAPPL TAC).
USED		Number of jobs issued to this LTAC since the application started.  The counter is reset to 0 every time the application starts.
D		Specifies whether the LTAC has been deletetd via dynamic administration or not (no entry).

type=LTERM

LTERM  PTERM  USER  KSET LOCK  USAGE      STATUS   OUT-Q    INCNT    SECCNT   D
lterm  pterm  user  kset lock  D|O         ON|OFF  number   number   number   D
                               B|M|S|
                               P|G|A

Explanation of the output

LTERM	Name of the LTERM partner; logical name of the assigned client/printer.
PTERM	Name of the client or printer (PTERM name) to which this LTERM partner is assigned.
USER	User ID of the user currently connected to the application through this LTERM partner. If there is currently no connection, then user_curr contains blanks. If a connection exists: If no user has as yet been signed on at a terminal, user_curr also contains blanks. In applications with MULTI-SIGNON=YES: If a genuine user ID with RESTART=YES is signed on to an LTERM partner of a client of the type UPIC/APPLI/SOCKET, user_curr contains that user ID, otherwise it contains the connection user (user_gen). In applications with MULTI-SIGNON=NO: If a genuine user ID is signed on to an LTERM partner of a client of the type UPIC/APPLI/SOCKET, user_curr contains that user ID, otherwise it contains the connection user (user_gen).
KSET	Key set assigned to the LTERM partner (access rights).
LOCK	Lock code assigned to the LTERM partner (access protection).
USAGE	Type of LTERM partner 1st value: D: A client is assigned to the LTERM partner or O: A printer is assigned to the LTERM partner 2nd value: B: A printer bundle is assigned to the LTERM partner. M: The LTERM is a master LTERM of an LTERM bundle. S: The LTERM is a slave LTERM of an LTERM bundle. 3rd value: P: The LTERM partner belongs to an LTERM pool G: The LTERM is the primary LTERM of an LTERM group. A: The LTERM is an alias LTERM of an LTERM group.
STATUS	The LTERM partner is disabled (OFF) or not disabled (ON).
OUT-Q	Number of messages that still have to be output for the LTERM partner.
STATUS	Number of messages entered via this LTERM partner; if a printer is connected to the LTERM partner, the number of print job confirmations is entered here. The INCNT counter is reset to 0 every time the application starts.
SECCNT	Number of security violations on this LTERM partner since the start of the application (e.g. unauthorized codes entered). The SECCNT counter is reset to 0 every time the application starts.
D	Indicates whether the LTERM partner was deleted by dynamic administration (D) or not (no entry).

type=MUX (BS2000 systems)

MUX   PRONAM   BCAMAPPL  STATUS   CONNECT  MAXSES  ACTCON  MAXCON 
mux1  proname  applname  ON       Y   A    number  number  number 
                         OFF      N
                                  W

Explanation of the output

MUX	Name of the multiplex connection
PRONAM	Name of the processor on which the message router runs.
BCAMAPPL	Name of the local application (BCAMAPPL name) through which the multiplex connection is established.
STATUS	The multiplex connection is disabled (OFF) or not disabled (ON).
CONNECT	Here, several items of information are provided. 1st value: The multiplex connection is connected to the application (Y) or the multiplex connection is not connected to the application (N) or openUTM is attempting to establish a connection to the multiplex connection (W = waiting for connection) 2nd value: When the application starts, openUTM automatically tries to establish a connection to the multiplex connection (A) or not (no entry)
MAXSES	Number of terminals that can be connected to the application at the same time using this multiplex connection.
ACTCON	Number of terminals that are at present connected to the application using this multiplex connection.
MAXCON	Maximum number of terminals that were connected to the application at the same time using this MUX connection. The MAXCON counter is reset to 0 every time the application starts.

MUX,OPTION=MONITORING (BS2000 systems)

MUX    PRONAM    BCAMAPPL   LETTERS  INCNT   WAIT    SHORT   RTRYO   RTRYI
mux1   proname   applname   number   number  number  number  number  number

Explanation of the output

MUX	Name of the multiplex connection.
PRONAM	Name of the processor on which the message router is running.
BCAMAPPL	Name of the local application (BCAMAPPL name) via which connection to the multiplex connection is established.
LETTERS	Number of the input and output messages for this multiplex connection since the application started. The counter is reset to 0 every time the application starts.
INCNT	Number of input messages received through this multiplex connection. The INCNT counter is reset to 0 every time the application starts.
WAIT	Number of requests since the application started that were passed from BCAM to the multiplex connection requiring the resending of a message which it was previously not possible to accept because of a BCAM shortage (WAIT FOR GO) from BCAM.
SHORT	Number of BCAM shortages for this multiplex connection since the start of the application.
RTRYO	Number of tries to send an output message again since the start of the application (retry out).
RTRYI	Number of tries to read an input message again since the start of the application (retry in).

type=OSI-ASSOCIATIONS

ASSOC-ID  OSI-LPAP  OSI-CON   CONTWIN  CON-STATE  CONTIME   REQ-CALLS  IND-CALLS
assoc-id  osi-lpap  osi-con   Y|N      CONNECTED| minutes   number     number
                                       WAIT-GO|
                                       STOP

Explanation of the output

ASSOC-ID		ID assigned to the association when it was established. This is only unique while the association remains established. If the association is terminated, the ID is released and can be assigned to another established association.
OSI-LPAP		Logical name of the partner application (name of the OSI-LPAP partner) for which the association was generated.
OSI-CON		The OSI-CON name generated with the KDCDEF control statement for the logical connection to the partner application osi-lpap. If no connection is established, blanks are output at this point.
CONTWIN		Indicates whether the local application for this association is the contention winner or the contention loser.
CON-STATE		Indicates the status of the association.
	CONNECTED	The association is established.
	WAIT-GO	The association is being established. It is waiting for a “GO” from OSS.
	STOP	The association is being established. The OSS call a_assrs has run up to “STOP”.
CONTIME		Indicates the length of time in minutes for which the connection has existed.
REQ-CALLS		Number of request/response presentation calls to OSS since the association was established.
IND-CALLS		Number of indication/confirmation presentation calls to OSS since the association was established.

type=OSI-CON

The output depends on whether a short or a long host name is assigned to an OSI-CON object. In the case of a long host name, the information on an OSI-CON object is output in two screen lines.

OSI-CON   N-SEL    T-SEL      ACC-PNT      OSI-LPAP  ACTIVE
osi-con   proname  applname   access-point osi-lpap  Y|N
OSI-CON   N-SEL    T-SEL      ACC-PNT      OSI-LPAP  ACTIVE
osi-con   long.processor.name
                   applname   access-point osi-lpap  Y|N

Explanation of the output

OSI-CON	Name of the logical connection to the partner application osi-lpap .
OSI-LPAP	Logical name of the partner application in the local application (name of the OSI-LPAP partner) for which the connection was generated.
T-SEL	Application name of the partner application in the local system (transport selector).
N-SEL	Logical name of the computer on which the partner application is running (network selector).
ACC-PNT	Name of the local access point via which the connection osi-con is established.
ACTIVE	Y Connection osi-con can be used, i.e. messages for the specified OSI-LPAP partner are sent through and received by this connection. N The osi-con connection cannot be used. It is reserved as a replacement connection.

type=OSI-LPAP

OSI-LPAP KSET STA    Q OUT-Q  IDLET   OSI-CON ASSOC  CONN   AUTOC  BU
osi-lpap kset ON|OFF Q number seconds osi-con number number number M|S

Explanation of the output

OSI-LPAP	Logical name of the partner application in the local application (name of the OSI-LPAP partner).
KSET	Key set assigned to the OSI-PAP partner. The key set defines access rights to the partner application for the local application.
STATUS	Status of the partner application: ON The OSI-LPAP partner is not disabled. A connection to the partner application can be established or a connection already exists. OFF The OSI-LPAP partner is disabled. A connection cannot be established to the partner application.
Q (Quiet):	No more dialog jobs will be accepted for the OSI-LPAP partner.
OUT-Q	Number of messages in the message queue which still have to be sent to the partner application.
IDLETIME	Time to monitor the idle state of sessions between the partner application and the local application.
OSI-CON	The OSI-CsON name generated with the KDCDEF control statement for the logical connection to the partner application.
ASSOC	Maximum number of parallel connections (associations) to the OSI-LPAP partner that can exist at the same time. The number is defined during KDCDEF generation in the OSI-LPAP statement.
CONNECT	Number of connections to the OSI-LPAP partner existing at the present time or currently being set up.
AUTOCON	Number of connections to the OSI-LPAP partner which UTM should establish automatically when the application starts.
BU (bundle)	Specifies whether the OSI-LPAP partner belongs to an OSI-LPAP bundle. M The OSI-LPAP partner is the master LPAP of the OSI-LPAP bundle. S The OSI-LPAP partner is a slave LPAP of the OSI-LPAP bundle.

type=PAGEPOOL

PAGEPOOL INFORMATION
percent % PAGES FOR GSSB                 percent % PAGES FOR LSSB
percent % PAGES FOR TLS                  percent % PAGES FOR ULS
percent % PAGES FOR DIALOG SERVICES      percent % PAGES FOR TAC-CLASSES
percent % PAGES FOR FPUT-MANAGEMENT      percent % PAGES FOR ASYN MESSAGES
percent % PAGES FOR MSGTAC MESSAGES      percent % PAGES FOR LPUT
percent % PAGES FOR PHYS. MESSAGES       percent % PAGES FOR RESET MESSAGES
percent % PAGES FOR OSI TP LOG RECORDS   percent % OTHER PAGES
percent % FREE PAGES

Explanation of the output

PAGES FOR GSSB

Number of pages, in percent, which are utilized for GSSBs.

PAGES FOR LSSB

Number of pages, in percent, which are utilized for LSSBs.

PAGES FOR TLS

Number of pages, in percent, which are utilized for TLS areas.

PAGES FOR ULS

Number of pages, in percent, which are utilized for ULS areas.

PAGES FOR DIALOG SERVICES

Number of pages, in percent, which are utilized for service contexts by users.

PAGES FOR TAC-CLASSES

Number of pages, in percent, which are utilized for dialog input messages, and which are temporarily stored in TAC Class Queues.

PAGES FOR FPUT-MANAGEMENT

Number of pages, in percent, which are utilized for managing asynchronous messages.

PAGES FOR ASYN MESSAGES

Number of pages, in percent, which are utilized for asynchronous messages.

PAGES FOR MSGTAC MESSAGES

Number of pages, in percent, which are utilized for MSGTAC messages.

PAGES FOR LPUT

Number of pages, in percent, which are utilized for temporarily stored LPUT records. 

PAGES FOR PHYS. MESSAGES

Number of pages, in percent, which are utilized for output messages and which need to be temporarily stored because they can only be transferred to the transport system in sections owing to their length.

PAGES FOR RESET MESSAGES

Number of pages, in percent, which are utilized for reset messages.

PAGES FOR OSI TP LOG RECORDS

Number of pages, in percent, which are utilized for OSI TP log records.

OTHER PAGES

Number of other utilized pages, in percent.

FREE PAGES

Number of free pages, in percent.

In the case of UTM cluster applications, GSSB and ULS areas are stored in the global page pool of the UTM cluster application. As KDCINF PAGEPOOL only displays the utilization of the local page pool, the values for GSSB and ULS are always zero in UTM cluster applications.

type=POOL

The output depends on whether a short or a long host name is assigned to a LTERM pool object. In the case of a long host name, the information on a LTERM pool object is output in two screen lines.

POOL     PRONAM   BCAMAPPL PTYPE STATIONS STA=ON ACTCON MAXCON KSET     LOCK
ltprefix proname  applname ptype number   number number number kset     lock
POOL     PRONAM   BCAMAPPL PTYPE STATIONS STA=ON ACTCON MAXCON KSET     LOCK
ltprefix long.processor.name
                  applname ptype number   number number number kset     lock

Explanation of the output

POOL	LTERM prefix of the LTERM pool. The names of the LTERM partners assigned to the pool comprise ltprefix and a serial number between 1 and the maximum number of clients allowed to connect to the LTERM pool at the same time.
PRONAM	Only clients located on computer proname can establish connections to the application using the LTERM pool. In the case of applications on Unix, Linux or Windows systems, blanks are entered for proname if the LTERM pool is defined for locally connected clients.
BCAMAPPL	Name of the local application (BCAMAPPL name) through which the connections to this LTERM pool were established (see KDCDEF statement TPOOL operand BCAMAPPL).
PTYPE	Physical type of client allowed to connect to the application through this LTERM pool.
STATIONS	Maximum number of clients allowed to connect to the application at the same time using this LTERM pool.
STA=ON	Number of clients currently allowed in the LTERM pool.
ACTCON	Number of clients connected to the application at the present time through this pool.
MAXCON	Maximum number of clients connected to the application during the current application run using this LTERM pool. The counter is reset to 0 every time the application starts.
KSET	Key set assigned to the LTERM pool, and therefore to all clients connected to the application by this LTERM pool (access rights).
LOCK	Lock code assigned to the LTERM pool (access protection).

type=PROG

For KDCINF PROG,L=KDCALL,CONT=programname

Output for UTM applications on BS2000 systems

PROGRAM	LOAD-MODULE	L-MODE	CHN	D
program1 program2	load module1 load module2	load mode load mode	YES | NO YES | NO	D

Output for UTM applications on Unix, Linux and Windows systems

PROGRAM	SHARED-OBJECT	L-MODE	CHN	D
program1 program2	shared object1 shared object2	load mode load mode	YES | NO YES | NO	D

Explanation of the output

PROGRAM

Name of the program unit as specified during generation in the PROGRAM statement; up to 32 characters in length.

LOAD-MODULE

Name of the load module on BS2000 systems to which this program unit is assigned; up to 32 characters in length.

SHARED-OBJECT

Name of the shared object/DLL on Unix, Linux and Windows systems to which this program unit is assigned; up to 32 characters in length.

L-MODE

Load mode of the load module/shared object/DLL to which this program unit is assigned. Key to terms:

STATIC
The load module/shared object/DLL is incorporated as a static element in the application program.

STARTUP
The load module/shared object/DLL is loaded dynamically as an independent unit whenever the application is started.

ONCALL
The load module/shared object/DLL is loaded as an independent unit whenever a program unit or VORGANG exit assigned to the load module/shared/DLL is called for the first time. 

Only on BS2000 systems:

POOL
The load module is loaded into the common memory pool whenever the application starts. The load module does not contain a private slice.

POOL/STARTUP
The public slice of the load module is loaded into the common memory pool whenever the application starts. The private slice belonging to the load module is then loaded into the local process memory.

POOL/ONCALL
The public slice of the load module is loaded into the common memory pool whenever the application starts. The private slice belonging to the load module is loaded into the local process memory when the first program unit assigned to this load module is called.

CHANGEABLE

Displays whether or not the load module/shared object/DLL to which this program unit is assigned can be exchanged.

D

Indicates whether the program was deleted from the configuration by means of system administration functions (D) or not (no entry).

type=PTERM

The output depends on whether a short or a long host name is assigned to a PTERM object. In the case of a long host name, the information on a PTERM object is output in two screen lines.

PTERM  PRONAM  LTERM  BCAMAPPL PTYP  STA     CONNECT      CTIME   LETTERS CONB   D 
pterm  proname lterm  applname ptype ON|OFF  Y|N|W A|P M  minutes number  number D
                                              T|E
pterm  long.processor.name
               lterm  applname ptype ON|OFF  Y|N|W A|P M  minutes number  number D
                                              T|E

Explanation of the output

PTERM	Name of the client or printer (PTERM name).
PRONAM	Name of the computer on which the client/printer is located. In UTM applications on Unix, Linux or Windows systems blanks are output for local clients/printers.
LTERM	Name of the LTERM partner (logical name) to which this client/printer is assigned.
BCAMAPPL	Name of the local UTM application (BCAMAPPL name) via which the connection to the client/printer is established.
PTYP	Type of client/printer (for the meaning of the output, see chapter "kc_pterm_str - Clients and printers" (BS2000 systems or Unix, Linux and Windows systems)
STA	The client/printer is disabled (OFF) or not disabled (ON).
CONNECT	Several items of information are provided here. 1st column: Y/N/W: The client/printer is at present connected to the application (Y) or not (N), or UTM is now attempting to establish a connection (W = waiting for connection) T/E: Only output for terminals connected to a UTM application on a BS2000 system by a multiplex connection. T: (timer) The session is in DISCONNECT-PENDING mode; the timer is running, waiting for confirmation that a connection is being established. E: (expired) The session is in DISCONNECT-PENDING mode and the timer waiting for confirmation has run out before confirmation was received. In both cases, the session can be released with KDCPTERM. 2nd column: A: automatic connection is established when the application starts or P: the client is connected to the application by an LTERM pool. If neither of these properties applies, there is no output at this point. 3rd column (only for UTM applications on BS2000 systems): The client is connected to the application by a multiplex connection (M) or not (no entry).
CTIME	Duration of the existing connection in minutes.
LETTERS	Number of input and output messages for the client or output messages to the printer since the application started. The counter is reset to 0 every time the application starts.
CONB	Number of connection failures between client/printer and application since the application started. The CONB counter is reset to 0 every time the application starts. In UTM applications on BS2000 systems, the CONB counter also counts incrementally if a UPIC client first shuts down its connection to the UTM application and then establishes a new connection using the same PTERM name.
D	Indicates whether the client/printer was deleted (D) or not (no entry) from the configuration by means of system administration functions.

type=SHARED-OBJECT (Unix, Linux and Windows systems)

For KDCINF SHARED-OBJECT, L=shared-object-name, CONT=programname

SHARED-OBJECT       shared object name
VERSION (PREVIOUS)  old version
VERSION (CURRENT)   new version
LIBRARY             name of program directory
LOAD MODE           STATIC|STARTUP|ONCALL
CHANGEABLE          YES|NO
PROGRAM LIST
program1            program2
program3            program4

Explanation of the output

SHARED-OBJECT
		Name of the shared object/DLL; up to 32 characters in length
VERSION (PREVIOUS)
		Previous version of the shared object/DLL.
VERSION (CURRENT)
		Currently loaded version of the shared object/DLL.
LIBRARY		Name for the program library of up to 54 characters loaded from the shared object/DLL.
LOAD MODE		Load mode for the shared object/DLL. Key to the terms used:
	STATIC	The shared object/DLL is incorporated as a static element in the application program.
	STARTUP	The shared object/DLL is loaded dynamically as an independent unit whenever the application starts.
	ONCALL	The shared object/DLL is loaded as an independent unit whenever a program unit or VORGANG exit assigned to the same shared object/DLL(s) is called for the first time.
CHANGEABLE
		Displays whether or not the shared object/DLL can be replaced during run time.
PROGRAM LIST
		List of the names of all program units and data areas (AREAs) assigned to the shared object/DLL.

type=STATISTICS

    name   APPLINAME                      version   VERSION OF UTM
yy-mm-dd   GEN APPLICATION DATE           hh:mm:ss  GEN APPLICATION TIME
yy-mm-dd   START APPLICATION DATE         hh:mm:ss  START APPLICATION TIME
yy-mm-dd   CURRENT DATE                   hh:mm:ss   CURRENT TIME
  number   TERMINAL INPUT MESSAGES         number   TERMINAL OUTPUT MESSAGES
  number   CURRENT TASKS                   number   CONNECTED USERS
  number   OPEN DIALOG SERVICES            number   OPEN ASYN SERVICES
 percent % CURRENT LOAD                   percent % MAXIMUM LOAD
  number   DIALOG TAS PER SECOND           number   ASYN TAS PER SECOND
  number   DIALOG STEPS PER SECOND        percent % MAXIMUM POOL SIZE
 percent % ACTUAL POOL SIZE               percent % AVERAGE POOL SIZE
 percent % CACHE HIT RATE                  number   NR CACHE SEARCHES
 percent % CACHE WAITS FOR BUFFER          number   NR CACHE REQUESTS
  number   UNPROCESSED ATACS               number   UNPROCESSED PRINTS
  number   WAITING DPUTS                   number   ABNORMAL TERMINATED SERVS
  number   LOGFILE WRITES                  number   UTM-DEADLOCKS
  number   PERIODIC WRITES                 number   PAGES PER PERIODIC WRITE
 percent % WAITS FOR RESOURCES             number   NR RESOURCE REQUESTS
 percent % MAX WAITS FOR RESOURCES         number   NR RES REQUESTS FOR MAX
 percent % WAITS FOR SYSTEM RES            number   NR SYSTEM RES REQUESTS
 percent % MAX WAITS FOR SYSTEM RES        number   NR SYSTEM RES REQ FOR MAX
 percent % ACTUAL JR                      percent % MAXIMUM JR 
  number   AVG COMPRESS PAGES SAVED

Explanation of the output

APPLINAME

Name of the application that was defined during KDCDEF generation for MAX APPLINAME.

VERSION OF UTM

openUTM version used with correction status

GEN APPLICATION DATE

Date of the generation run of the application

GEN APPLICATION TIME

Time of the generation run of the application

START APPLICATION DATE

Day of the last cold start of the application (UTM-S application);
day of the last start of the application (UTM-F application)

START APPLICATION TIME

Time of the last cold start of the application (UTM-S application);
Time of the last start of the application (UTM-F application)

CURRENT DATE

Current date

CURRENTN TIME

Current time

TERMINAL INPUT MESSAGES

Total number of messages received by the application from clients or partner applications during the last full hour.

TERMINAL OUTPUT MESSAGES

Total number of messages sent by the application to clients, printers or partners during the last full hour.

CURRENT TASKS

Current number of processes in the application.

CONNECTED USERS

Number of users connected to the application at the present time.

OPEN DIALOG SERVICES

Number of dialog services open at the present time.

OPEN ASYN SERVICES

Number of asynchronous services open at the present time.

CURRENT LOAD

Current load of the application during the last completed period of 100 seconds as a percentage.

The value in this field indicates the current load of the processes of the application in processing jobs. If the value is very high, additional processes should be started for the application.

MAXIMUM LOAD

Maximum load of the UTM application since startup or since the last time the value was reset as a percentage.

DIALOG TAS PER SECOND

Number of dialog transactions per second being executed at the present time.

ASYN TAS PER SECOND

Number of asynchronous transactions per second being executed at the present time.

DIALOG STEPS PER SECOND

Number of dialog steps per second being executed at the present time.

MAXIMUM POOL SIZE

Maximum allocation of page pool space in percent. In UTM-S applications, the value is set to 0 when the application is generated for the first time with KDCDEF or updated with KDCDEF/KDCUPD. With UTM-F applications, the value is set to 0 each time the application is started. 

ACTUAL POOL SIZE

Allocation of page pool space in percent at the present time.

AVERAGE POOL SIZE

Average allocation of page pool space in percent. In UTM-S applications, the value is set to 0 when the application is generated for the first time with KDCDEF or updated with KDCDEF/KDCUPD. With UTM-F applications, the value is set to 0 each time the application is started.
For this value to be meaningful, many dialog steps must already have been processed.

CACHE HIT RATE

Hit rate for a page search in cache memory. Figure quoted in percent. CACHE HIT RATE is reset to 0 before every application start.

NR CACHE SEARCHES

Number of search operations for UTM pages in the cache taken into account to calculate the value of CACHE HIT RATE.

CACHE WAITS FOR BUFFER

Buffer calls in cache that have resulted in a wait time. Figure quoted in percent.
CACHE WAITS FOR BUFFER is reset to 0 after every full hour.

NR CACHE REQUESTS

Number of buffer requests taken into account to calculate the value of CACHE WAITS FOR BUFFER.

UNPROCESSED ATACS

Number of messages for asynchronous services currently stored in openUTM that have not been completely processed.

UNPROCESSED PRINTS

Number of messages currently queued for the printers.

WAITING DPUTS

Number of time-driven jobs currently waiting (DPUTs)

ABNORMAL TERMINATED SERVS

Number of abnormally terminated services. In UTM-S applications, the value is set to 0 when the application is generated for the first time with KDCDEF or updated with KDCDEF/KDCUPD. With UTM-F applications, the value is set to 0 each time the application is started.

LOGFILE WRITES

Number of calls written to the user log file (USLOG). The LOGFILE WRITES counter is reset to 0 after every full hour.

UTM-DEADLOCKS

Number of recognized and resolved deadlocks affecting UTM resources. In UTM-S applications, the value is set to 0 when the application is generated for the first time with KDCDEF or updated with KDCDEF/KDCUPD. With UTM-F applications, the value is set to 0 each time the application is started.

PERIODIC WRITES

Number of periodic writes since the last application start.
(Periodic write = backup of all log-related administration data on the UTM application).

PAGES PER PERIODIC WRITE

Average number of UTM pages backed up during a periodic write.
The counter is reset to 0 every time the application starts.

WAITS FOR RESOURCES

This value indicates the average lock conflict rate for the GSSB, ULS and TLS memory areas during the last 100 second interval as an amount per thousand, i.e. the total number of wait situations on lock requests as a ratio of GSSB, ULS and TLS lock requests in the last 100 second interval multiplied by 1000.

A high value for WAITS FOR RESOURCES can have the following causes:

• Processes with excessively long run times or wait times,

• Resource disabled for too long, e.g. frequent PEND KP or PGWT calls to KDCS program units.

If a lock holder enters the status PEND KP then all "Waiters" are informed and all further locks are rejected immediately. I.e. the value of WAITS FOR RESOURCES does not increase as a result.

NR RESOURCE REQUESTS

Number of requests for transaction resources during the last 100 second interval taken into account to calculate the value of WAITS FOR RESOURCES.

MAX WAITS FOR RESOURCES

Maximum conflict rate for user data locks across the application run. The value is specified as a percentage

NR RES REQUESTS FOR MAX

Number of requests for transaction resources in the 100 second interval in which the maximum conflict rate MAX WAITS FOR RESOURCES was reached.

WAITS FOR SYSTEM RES

Average conflict rate in the last 100 second interval for the most heavily loaded system resource. The output in different intervals can refer to different system resources. The value is specified as a percentage.

NR SYSTEM RES REQUESTS

Number of requests for system resources during the last 100 second interval taken into account to calculate the value of WAITS FOR SYSTEM RES. 

MAX WAITS FOR SYSTEM RES

Maximum conflict rate for requests for system resources (system locks) across the application run. The value is specified as a percentage. 

NR SYSTEM RES REQ FOR MAX

Number of requests for system resources in the 100 second interval in which the maximum conflict rate MAX WAITS FOR SYSTEM RES was reached.

ACTUAR JR

Only for distributed processing:
Current number of simultaneously addressed job-receiving services relative to generation value MAXJR, figure quoted in percent.
(MAXJR = maximum number of job-receiving services that can be addressed simultaneously in the local application; this corresponds to the number of simultaneously active APRO calls.)

MAXIMUM JR

Only for distributed processing:
Maximum number of simultaneously addressed remote job-receiving services relative to generation value MAXJR (KDCDEF control statement UTMD). In UTM-S applications, the value is set to 0 when the application is generated for the first time with KDCDEF or updated with KDCDEF/KDCUPD. With UTM-F applications, the value is set to 0 each time the application is started.

The figure is quoted in percent.

AVG COMPRESS PAGES SAVED

Average value for the UTM pages saved per data compression. The writing of data areas in which UTM performs no compression because, for example, the data length is less than one UTM page is not included in this statistics value.

If no statistics value for data compression is available, the string "- - -" is output instead of a numeric value. This is possible in the following situations.

• Data compression is disabled.

• The value was reset, e.g. with KC_MODIFY_OBJECT or by means of WinAdmin or WebAdmin.

• No data compression was performed because the application uses "small" data areas in which it does not make sense to use compression.

If the value output for AVG COMPRESS PAGES SAVED is less than 0.5, for performance reasons data compression should be disabled for this application.

Lifetime of statistical data output for STATISTICS

The following statistical data is updated when the application is started or on each full hour (applies to UTM-F applications as well if MAX STATISTIC-MSG=FULL-HOUR was generated). The following table shows when UTM resets the counter to 0 for a UTM-S application. In UTM-F applications, all counters are reset to 0 at every application start.

You can reset some of the statistical values to 0 through the program interface to administration (see chapter "obj_type=KC_CURR_PAR").

Reset time	Counter(s) reset
At every application start	CACHE HIT RATE PAGES PER PERIODIC WRITE PERIODIC WRITES
For regeneration with KDCDEF and change generation with KDCDEF/KDCUPD	AVERAGE POOL SIZE MAXIMUM JR MAXIMUM POOL SIZE WAITS FOR RESOURCES
When the application starts and after every full hour (also in UTM-F applications if MAX STATISTIC-MSG= FULL-HOUR was generated)	CACHE WAITS FOR BUFFER LOGFILE WRITES UTM_DEADLOCKS ABNORMAL TERMINATED CONVS  TERMINAL INPUT MESSAGES TERMINAL OUTPUT MESSAGES

The following statistical values are written to the system log file SYSLOG at hourly intervals and at every normal termination of the application (message K081) provided that the application has been generated with MAX STATISTICS-MSG=FULL-HOUR:

CACHE HIT RATE
CACHE WAITS FOR BUFFER
CONNECTED USERS
LOGFILE WRITES
TERMINAL INPUT MESSAGES
TERMINAL OUTPUT MESSAGES
UNPROCESSED ATACS 

type=SYSLOG

The information in the output is identical to the output from KDCSLOG INFO (see chapter "KDCSLOG - Administer the SYSLOG file").

type=SYSPARM

appliname   APPLINAME                   version   VERSION OF UTM
   ON|OFF   ACCOUNT                      ON|OFF   CALC FOR ACCOUNTING 
   ON|OFF   SM2                          ON|OFF   KDCMON
   ON|OFF   TESTMODE                    percent % MAX CACHE PAGING RATE
   number   PROGRAM FGG                 seconds   TERMWAIT
   number   USLOG FGG                   seconds   RESWAIT-TA
   number   MAX TASKS                   seconds   RESWAIT-PR
   number   CURRENT TASKS               seconds   CONRTIME
   number   MAXASYN TASKS               seconds   LOGACKWAIT
   number   CURRENT MAXASYN TASKS        number   CURRENT MAX TASKS IN PGWT
  seconds   PTCTIME                     seconds   CONCTIME
  seconds   PGWTTIME                     number   TASKS WAITING IN PGWT
   YES|NO   PROGRAM EXCHANGE IS RUNNING  number   MAX TASKS IN PGWT
   YES|NO   CLUSTER-APPLICATION          PS|DS    CACHE LOCATION
   ON|OFF   DATA COMPRESSION (GEN)

Explanation of the output

APPLINAME	Name of the application defined in MAX APPLINAME during KDCDEF generation.
VERSION OF UTM
	openUTM version used, including the correction status and generation variant of the application (UTM-S or UTM-F).
ACCOUNT	The accounting phase for the accounting function is switched on (ON) or switched off (OFF). Can be switched on and off during runtime (e.g. with KDCAPPL).
CALC FOR ACCOUNTING
	The calculation phase of the accounting function is switched on (ON) or switched off (OFF). Can be switched on during runtime (e.g. with KDCAPPL).
SM2	Data supply to openSM2 is switched on (ON) or switched off (OFF) for the application. Can be switched on and off during runtime (e.g. with KDCAPPL).
KDCMON	The event monitor KDCMON is switched on (ON) or switched off (OFF). Can be switched on and off during runtime (e.g. with KDCDIAG).
TESTMODE	Test mode is switched on (ON) or switched off (OFF). This can be switched on and off during runtime (e.g. with KDCDIAG).
MAX CACHE PAGING RATE
	Current value for CACHE. The pageing rate indicates the maximum number of pages in cache memory (in percent) to be written to KDCFILE when shortages occur. This value can be changed, e.g. with KDCAPPL CACHE.
PROGRAM FGG
	Generation number of the currently loaded application program. For UTM applications on BS2000 systems, the value 0 is always output for PROGRAM FGG. For UTM applications running on Unix, Linux or Windows systems that were not started from the file generation directory PROG, the value 0 is output for PROGRAM FGG.
TERMWAIT	Current value representing the maximum length of time in seconds that can elapse in a multi-step transaction (PEND KP is called in the KDCS program unit) between an output to the terminal and the next entry made by the user (the time the terminal user takes to think).
USLOG FGG	Number of the file generation for the user log file to which the user is writing at the present time.
RESWAIT-TA	Current value representing the maximum time in seconds that the system can wait for another locked resource (GSSB, ULS,TLS).
MAX TASKS	Maximum number of processes allowed in this application (see the chapter "kc_tasks_par_str" data structure, tasks parameter).
RESWAIT-PR	Current value representing the maximum time in seconds that the system can wait for a resource locked by another process (GSSB, ULS, TLS).
CURRENT TASKS
	Number of processes in the application at the present time (see the chapter "kc_tasks_par_str" data structure , curr_tasks parameter).
CONRTIME	Current value representing the time in minutes after a connection failure after which UTM should attempt (cyclically) to re-establish the connection.
MAXASYN TASKS
	Maximum number of processes in the application that can be used at the same time for asynchronous processing (see the chapter "kc_tasks_par_str" data structure, asyntasks parameter).
LOGACKWAIT
	Maximum time in seconds for which UTM applications on BS2000 systems can wait for a printout or transport confirmation message. For UTM applications running on Unix, Linux or Windows systems, this output is irrelevant.
CURRENT MAXASYN TASKS
	Maximum number of processes that can be used at the same time for asynchronous processing (see the chapter "kc_tasks_par_str" data structure, curr_max_asyntasks parameter). This value is adjusted automatically whenever: the value is explicitly changed by means of system administration functions (e.g. by KDCAPPL ASYNTASKS=). the number of processes in the application (CURRENT TASKS) is changed (e.g. by KDCAPPL TASKS=). When the number of CURRENT TASKS is reduced, the number of CURRENT MAXASYN TASKS is also reduced as soon as CURRENT TASKS is < CURRENT MAXASYN TASKS. If the number of CURRENT TASKS is increased at a later point, the value for CURRENT MAXASYN TASKS is increased again automatically by UTM.
CURRENT MAX TASKS IN PGWT
	Maximum number of processes currently in the application that are permitted to accept program units with blocking calls (see the chapter "kc_tasks_par_str" data structure, curr_max_tasks_in_pgwt parameter). This value is changed automatically whenever: the value is explicitly changed by means of system administration functions (e.g. by KDCAPPL TASKS-IN-PGWT=). the number of processes in the application (CURRENT TASKS) is changed by administration (e.g. by KDCAPPL TASKS=). When the number of CURRENT TASKS is reduced, the number of CURRENT MAX TASKS IN PGWT is also reduced as soon as CURRENT TASKS is <= CURRENT MAX TASKS IN PGWT. If the number of CURRENT TASKS is increased at a later point, the value for CURRENT MAX TASKS IN PGWT is increased again automatically by openUTM.
PTCTIME	Only for distributed processing: Maximum time in seconds for which a local job-receiving service can wait in PTC mode (prepare to commit, transaction status P) for confirmation from the job-submitting service. The value 0 signifies that the system can wait for confirmation for an unlimited period of time.
CONCTIME	Only for distributed processing: Time in seconds for monitoring the establishment of a session (LU6.1) or an association (OSI TP). If the session or association is not established within the specified time limit, openUTM terminates the transport connection. This prevents a transport connection from remaining disabled due to failure to establish a session or an association. CONCTIME=0 means that session setup is not monitored in the case of LU6.1 connections (UTM waits indefinitely). In the case of OSI TP connections, UTM waits up to 60 seconds for an association to be set up.
PGWTTIME	Maximum time in seconds that a blocking function call can wait, e.g. the KDCS call PGWT.
TASKS WAITING IN PGWT
	Number of current processes that can be in wait state at the same time due to blocking function calls (e.g. KDCS call PGWT).
PROGRAM EXCHANGE IS RUNNING
	Specifies whether openUTM is currently exchanging a program for the application.
MAX TASKS IN PGWT
	Maximum number of processes in the application that can simultaneously process program units with blocking function calls (e.g. KDCS call PGWT) (see the chapter "kc_tasks_par_str" data structure, tasks_in_pgwt parameter).
CLUSTER-APPLICATION
	Specifies whether the application is a UTM cluster application or a standalone UTM application.
CACHE LOCATION
	Specifies whether the UTM cache lies in the program space (PS) or in one or more data spaces (DS). PS is always displayed for Unix, Linux, and Windows systems.
DATA-COMPRESSION (GEN)
	Specifies whether data compression is permitted (ON) or not (OFF) for the application. The value displayed here matches the generation value for the application (see openUTM manual “Generating Applications”, MAX DATA-COMPRESSION=). If ON is displayed here, data compression can be enabled or disabled using administration facilities, e.g. with KDCAPPL.

 

type=TAC

TAC  LOCK    STAT TCL    IN-Q   USED   ERROR  DBCNT  TACELAP DBELAP TACCPU D
tac  number  ON   number number number number number msec    msec   mcsec  D
             OFF  type
             HLT
             KP

Explanation of the output

TAC	TAC name
LOCK	Lock code which provides access protection for the transaction code; a number between 1 and 4000.
STAT	Status of the transaction code: The TAC is enabled (ON), disabled (OFF), completely disabled (HLT) or blocked (KP). Blocked means that the TAC is disabled, but jobs are accepted for the TAC and placed in the job queue.
TCL	TAC class and type ( D | A | Q ) of the transaction code or TAC queue.
IN-Q	Number of messages that still have to be processed by the program unit started by the TAC name.
USED	Total number of program unit runs processed with this transaction code (only for asynchronous TACs). In UTM-S applications, the value is set to 0 when the application is generated for the first time with KDCDEF or updated with KDCDEF/KDCUPD. With UTM-F applications, the value is set to 0 each time the application is started.
ERROR	Number of program unit runs which were started by this transaction code and abnormally terminated. In UTM-S applications, the value is set to 0 when the application is generated for the first time with KDCDEF or updated with KDCDEF/KDCUPD. With UTM-F applications, the value is set to 0 each time the application is started.
DBCNT	Average number of database calls from program units which were started with this TAC name. With database connections via the XA interface DBNCT is always 0.
TACELAP	Average run time of the program unit which was started with this TAC (elapsed time); figure quoted in milliseconds.
DBELAP	Average time for processing the database calls in the program unit runs. With this TAC; figure quoted in milliseconds. With database connections via the XA interface DBNCT is always 0.
TACCPU	Average CPU time in microseconds used for processing this transaction code in the program unit. This corresponds to the CPU time used by openUTM plus the CPU time used by the database system.
D	Indicates whether the transaction code was deleted (D) or not (no entry) from the configuration by means of system administration functions.

The statistical values output for type = USED, ERROR, DBCNT, TACELAP, DBELAP and TACCPU are reset to 0 every time KDCDEF performs a new generation and every time KDCDEF/KDCUPD generates a change in UTM-S applications. With UTM-F applications, the values are set to 0 each time the application is started. 

type=TAC-PROG

Output for UTM applications on BS2000 systems

TAC       PROGRAM            LOAD-MODULE
tac1      program1           load-module1
tac2      program2           load-module2
tac3      program3           load-module3

Output for UTM applications on Unix, Linux and Windows systems

TAC       PROGRAM            SHARED-OBJECT
tac1      program1           shared-object1
tac2      program2           shared-object2
tac3      program3           shared-object3

Explanation of the output

TAC	Name of the transaction code
PROGRAM	Name of the program unit to which this transaction code is assigned
LOAD-MODULE
	On BS2000 systems: Name of the load module containing the program unit (PROGRAM)
SHARED-OBJECT
	On Unix, Linux and Windows systems: Name of the shared object/DLL containing the program unit (PROGRAM)

type=TACCLASS

TACCLASS  TASKS  WT MSGS   AVG-WAIT-TIME PGWT    PRIO* NR     WAITS
    1     number   number  msec          YES|NO  prio  number number
    :
    8     number   number  msec          YES|NO  prio  number number
    9     number   number  msec          YES|NO  prio  number number
    :
   16     number   number  msec          YES|NO  prio  number number

*prio = ABS | REL | EQ | NO

Explanation of the output

TASKS	Maximum number of processes currently allowed to process jobs for transaction codes in this TAC class.
WT MSGS	Number of messages currently stored in openUTM for transaction codes in this TAC class that have not yet been processed.
AVG-WAIT-TIME
	Average wait time for jobs in this TAC class in milliseconds. The wait time is calculated from the time openUTM accepts the job to the start of actual processing. AVG-WAIT-TIME=0 signifies that all jobs are being processed immediately. Wait times can, for instance, arise if not all processes in the application may process jobs for the TAC class and if openUTM consequently has to store jobs temporarily in the job queue.
PGWT	Specifies whether program units with blocking calls, e.g. the KDCS call PGWT, are allowed to run in this TAC class. If the application was generated with priority control (TAC-PRIORITIES statement), then the column PGWT contains NO for all TAC classes.
PRIO	If the application was generated with priority control, then the column PRIO contains the type of priority defined for the TAC classes (ABS, REL, EQ). If the application was generated without the TAC-PRIORITIES statement, the PRIO column contains NO for all TAC classes.
NR	Number of program unit runs for this TAC class.
WAITS	Number of wait situations taken into account to calculate the value AVG-WAIT-TIME.

type=USER

 USER   KSET   STATUS   OSERV  NR.TACS  CPUTIME   SECCNT   LTERM   D
 user1  kset1  ON|OFF   Y|N    number   msec      number   lterm1  D

Explanation of the output

USER	Name of the user ID
KSET	Key set assigned to this user ID (access rights)
STATUS	User ID is disabled (OFF) or not disabled (ON).
OSERV	Y signifies that the user is currently processing a service and that this service has reached at least one synchronization point. N signifies that the user is not currently processing a service which has not already reached one synchronization point.
NR.TACS	Number of program unit runs entered under this user ID. In UTM-S applications, the value is set to 0 when the application is generated for the first time with KDCDEF or updated with KDCDEF/KDCUPD. With UTM-F applications, the value is set to 0 each time the application is started.
CPUTIME	Number of CPU milliseconds used up by the user for processing these jobs (does not include the CPU time for the database calls). The value is reset to 0 after the user has signed off (KDCOFF) or after the connection has been cleared.
SECCNT	Number of security violations for this user ID (e.g. incorrect password entered) since the start of the application. This number is reset to 0 each time the application is started.
LTERM	The following cases must be distinguished: Applications with MULTI-SIGNON=NO (i.e. multiple sign-ons are not permitted): LTERM or OSI-LPAP partner by means of which a user is signed on with this user ID. Exception: LTERM contains blanks when signing on to start an asynchronous service was via OSI TP. Applications with MULTI-SIGNON=YES (multiple sign-ons permitted): If a user with the user ID is connected to the application via a terminal, LTERM contains the name of the LTERM partner assigned to the terminal. If the user ID is generated with RESTART=YES, LTERM contains the name of the LTERM or OSI-LPAP partner via which a client with this user ID is signed on. Exceptions: Signing on took place by means of OSI TP, and the functional unit “Commit” was selected, or signing on was via OSI TP to start an asynchronous service. In this case, LTERM contains blanks. In all other cases, LTERM contains blanks.
D	Indicates whether the user ID was deleted (D) or not (no entry) from the configuration by means of system administration functions.

The password for the user ID is not output.