Starting and stopping data recording

Data recording can be started in two steps:

• First you must start KDCMON.

• Then activate data recording for the UTM applications to be checked.

KDCMON is an independent subsystem in the BS2000 system and is included in BS2000 basic configuration. KDCMON must be installed and loaded by the system administrator. See also section "KDCMON subsystem".

Starting KDCMON

Before starting KDCMON, you must create a file in which KDCMON is to write the recorded data. To do this, issue the following commands:

• For recording to disk files:

  /SET-FILE-LINK LINK-NAME=KDCMON,FILE-NAME=kdcmonfile -
  /     ,ACCESS-METHOD=UPAM 
  /MODIFY-FILE-ATTRIBUTES FILE-NAME=kdcmonfile        -
  /     ,SUPPORT=*PUBLIC-DISK(SPACE=*RELATIVE         -
  /      (PRIMARY-ALLOCATION=xxx,SECONDARY-ALLOCATION=yyy))
  

  xxx and yyy must be multiples of 12 (otherwise DMS error).

• For recording to tape files:

  /SET-FILE-LINK LINK-NAME=KDCMON,FILE-NAME=kdcmonfile -

  /     ,ACCESS-METHOD=BTAM

  /MODIFY-FILE-ATTRIBUTES FILE-NAME=kdcmonfile  -

  / ,SUPPORT=*TAPE(VOLUME=xxxxxxx,DEVICE-TYPE=type)

The block size and record length must not be specified for the file.

You can then start KDCMON under the ID $TSOS. The program for starting KDCMON is provided in the file SYSPRG.KDCMON.nnn:

/START-EXECUTABLE-PROGRAM FROM-FILE=$userid.SYSPRG.KDCMON.nnn

The version identifier nnn stands for the BS2000 version in which KDCMON is running. See also section "KDCMON subsystem".

You can also start KDCMON using the SDF command START-KDCMON, see section "Starting UTM tools via separate SDF commands".

 

The KDCMON program expects the following control parameters:

BUFPAG=size
	Specifies the size of the buffer in KDCMON in units of 4 KB. Permitted values: 1 to 7 Default value: 2 (= recommended value)
BUFFER=number
	Specifies the number of buffers in KDCMON. Permitted values: 2 to 128 Default value: 4 (= recommended value)
{TIME= mmm | START | BREAK}
	Determines the runtime of KDCMON. The specification of one of TIME=mmm, START or BREAK terminates the input of the control parameters.
TIME=mmm	Runtime of KDCMON in minutes. After the specified time has elapsed, KDCMON terminates. Minimum value: 1 Maximum value: 150
START	KDCMON runs for 30 minutes. Corresponds to the specification TIME=30. Default value: START
BREAK	KDCMON runs until RESUME is entered.

CAUTION!

KDCMON can run for a maximum of 150 minutes; otherwise, the evaluation tool KDCEVAL cannot evaluate the data.

The buffers have the same meaning in KDCMON as in COSMOS.

The program SYSPRG.KDCMON.nnn must not be terminated during data entry, as otherwise the KDCMON subsystem will no longer be available and must be unloaded.

Stopping KDCMON

KDCMON terminates after the predefined time set in the parameters TIME=mmm and START, or after RESUME is entered with BREAK. However, the KDCMON subsystem remains loaded and can be unloaded using the DSSM command

/STOP-SUBSYSTEM KDCMON

if data entry is not running at this time. If you want to unload KDCMON when data entry has not concluded in one of the UTM applications, you must specify:

/STOP-SUBSYSTEM KDCMON,FORCED=YES

 

Activating and deactivating data recording

After KDCMON has been started successfully, you can record data from all UTM applications running on the respective system.

KDCMON also records BCAM wait times: If KDCMON is activated for input messages, BCAM records the wait time spent by these messages in the BCAM transport system before they are picked up by openUTM. For connections with intense dialog, the wait times are recorded for all input messages. For other connections, a statistical selection is made in high-load situations. openUTM transfers this wait time for each message from BCAM and writes it in the KDCMON records. From this data, KDCEVAL determines the maximum, minimum, and mean value (specified in seconds). These values are output in the WAIT list (see "WAIT: WAITING TIMES").

Using UTM administration functions, you can define the UTM applications from which data is recorded by KDCMON.
Data entry, including the entry of BCAM wait times, can be activated and deactivated using the administration command:

KDCDIAG KDCMON={ ON | OFF }

This administration function is also available on the KDCADMI program interface and via the graphical administration tools WinAdmin/WebAdmin.

You can activate and deactivate data entry for an application during a KDCMON run several times. Up to 10 data acquisition time intervals are possible.

The UTM administrator can use the following command:

KDCINF SYSPARM

at any time to determine whether or not data is being recorded.

If openUTM detects that the KDCMON function is not available when it attempts to activate it, then the following message is output to the default destination SYSLOG:

K080 KDCMON is not active

Possible cause:
The KDCMON subsystem was not started or was not installed under $TSOS.

If openUTM detects that the KDCMON function is not available any more while it is acquiring data, then openUTM deactivates the collection of data and informs the user of this fact with message K080.

openUTM logs the activation and deactivation of the BCAM wait time with UTM message K146; the default destination of the UTM message is SYSLOG. UTM message K146 is also output by openUTM if an error occurs when reading the BCAM wait times. As diagnostic documentation, openUTM creates a UTM dump with the dump error code ASIS70, UMES02, or WAIT61. The application then continues to run without recording the BCAM wait time.