OVNPM 1.5.2 - Performance Agent for NonStop Server Monitoring Guide

OVNPM Monitoring Configuration 21

2-4 Monitoring User Application

A user application is a set of instances belong domain PROCESS, PROGRAM, APPLIFILE, APPLIDEF, USERDEF

and BASE24DEF. To monitor user application, its components (that is instances) must be found and added in the

USERCFG file. In OVNPM version 1.2, this operation must be done manually.

• Step 1: Get Instances Related Processes

In the first step, we must locate the subvolume or the directory that contains the executable belonging the

application. This subvolume will give the program and their processes. This will give PROGRAM,

PROCESS, and APPLIDEF instances.

• Step 2: Get Instances Related to Data Files

The second step involves using navigator to get the data file opened by those processes. This will give

instances belong to FILESIZE, DISKFILE and APPLIFILE.

• Step 3: Get USERDEF and BASE24 instances

The third step is the definition of your USERDEF and BASE24 counter.

USERDEF required cooperation with your development team to get the list of the USERDEF counter and the

processes that bumps them. BASE24 counter needs BASE24 documentation to get the list of the counters.

A user application is a set of instances belong domain PROCESS, PROGRAM, APPLIFILE, APPLIDEF, USERDEF,

BASE24DEF, FILESIZE and DISKFILE. To monitor user application, its components (that is instances) must be found

and added in the USERCFG file.

OVNPM provides the sv_discover_* functions to perform application discovery.

2-4-1 Discovery Steps

Step 1: Get Instances Related Processes

In the first step, we must locate the subvolume or the directory that contains the executable belonging

the application. This subvolume will give the program and their processes. This will give PROGRAM,

PROCESS, and APPLIDEF instances.

Step 2: Get Instances Related to Data Files

The second step involves using navigator to get the data file opened by those processes. This will give

instances belong to FILESIZE, DISKFILE and APPLIFILE.

Step 3: Get USERDEF and BASE24 instances

The third step is the definition of your USERDEF and BASE24 counter.

USERDEF required cooperation with your development team to get the list of the USERDEF counter and

the processes that bumps them. BASE24 counter needs BASE24 documentation to get the list of the

counters.

USERDEF Example

In following example, we show how to add a USERDEF counter belonging to process $VQ0A. We use the

Meascom output to define USEDEF in OVNPM configuration files. We consider that measurement of $VQ0A

USERDEF counters is already running.

$DATA07 THDOQA 30> meascom

MEASURE Performance Monitor - T9086G09 - (02APR01) - \NODE

1+ add measurement udmameas

2+ list userdef $VQ0A

Process 1,416 ($VQ0A) Pri 158 Device Name $SMF

Program $DATA07.THDOQA.UDM

Userid 144,1 Creatorid 144,1 Ancestor 1,160 ($Y8VD)

Local System \NODE From 9 Apr 2004, 7:39:54 For 7.3 Minutes

ITERATION 1.09 Accum 0