Velocity Software, Inc. is recognized as a leader in the performance measurement of z/VM and Linux on z. The Velocity Performance Suite consist of a set of tools that enable installations running z/VM to manage Linux and z/VM performance. In addition, many components of server farms can be measured and analyzed. Performance data can be viewed real-time through the use of either 3270 or a browser. The CLOUD Implementation (zPRO) component is designed for full cloud PaaS implementation as well as to extend the capabilities of the z/VM sysprog (system programmer) to the browser world. This feature moves system management to the point-and-click crowd. Archived data and reports can be kept available of long term review and reporting usine zMAP. The zVPS, formally ESALPS, components consist of: zMON (formally ESAMON - real-time display of performance data), zTCP (formally ESATCP - SNMP data collection), zMAP (formally ESAMAP - historical reporting and archiving), zVWS (formally ESAWEB - z/VM based web server), zTUNE (a subscription service), zVIEW (formally SHOWCASE - web based viewing of performance data), zPRO (new to the quality line of Velocity Software Products). Velocity continues to work with other software vendors to ensure smooth interface with or from other products such as VM:Webgateway, CA-Webgateway, EnterpriseWeb, MXG, MICS. Velocity software remains the leader and inovator in the z/VM performance, Linux performance, Managing cloud computing arenas.
About Us | Products | FAQ | Demo | Customer Area | Education | Linux Hints & Tips | Presentations | News | Industry and Events | Employment Opportunities
Home | Contact Us | License Info | Newsletter    

As delivered, Performance Reporter uses data generated by the VMPRF program as a source of VM performance information. Velocity Software customers can replace that source with data generated by ESAWRITE or ESAMAP. To do that requires users to map the historical data that Velocity creates into a format for processing.

Before you can use the Velocity Software component to collect data and create reports, you must customize and test the installation. This documentation describes the steps that you must perform to customize the Velocity Software component.

Velocity Software provides history data in two different ways: Real time, by way of ESAWRITE the data collection function for ESAMON, or as a post process, using ESAMAP. The format of the data will be identical the difference will be the granularity of the data. Using ESAWRITE to produce the data will be the most efficient. This data could be transmitted to Performance Reporter. Another option is to use ESAMAP to process the ESAWRITE data and reduce the amount of data to be transmitted to Performance Reporter. Another option is to use ESAMAP to produce history data directly from raw monitor data produced by MONWRITE.


Make input data available

Data in the DB2 tables that Performance Reporter uses for the Velocity Software component is originally generated by either the ESAWRITE or the ESAMAP program (from Velocity Software) running on a VM/ESA or VM/XA system. The Velocity Software history records contain many types of data, including virtual machine processor usage and response times, system performance characteristics, and system configuration, writing this data into multiple history files. Performance Reporter uses these history files as its data source in this component.

To make the data available to Performance Reporter, transmit these history files to the MVS system where you are running Performance Reporter. You might use net data format for this, or set up FTP tranmission.

Modify Collect JCL
The following sample JCL is provided to assist you in building batch jobs to process the ESAMAP history files.

Jobcard ..
 
//STEP0001 EXEC PGM=DRLPLC,PARM=('SYSTEM=xxx SYSPREFIX=xxxxxx')
//STEPLIB  DD DISP=SHR,DSN=DSN=PR.loadlib.name
//         DD DISP=SHR,DSN=DB2.loadlib.name
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//DRLIN    DD *
 
SET SYSTEM_ID = 'vm-system-id';
COLLECT log
   COMMIT AFTER BUFFER FULL ONLY
   BUFFER SIZE 80000000
   ON OVERFLOW CONTINUE;
 
//DRLLOG   DD DISP=SHR,DSN=ESAMAP.history.filename
//DRLOUT   DD SYSOUT=*,DCB=(RECFM=F,LRECL=80)
//DRLDUMP  DD SYSOUT=*,DCB=(RECFM=VB,LRECL=32756)
//*
Notes:

Update Lookup Tables

The Velocity Software component uses the DAY_OF_WEEK and PERIOD_PLAN control tables wheen updating data tables. The component also uses the USER_GROUP common lookup table. Ensure that these tables specify the days, periods, and user groups you want to report on. For descriptions of these tables and examples of their contents, refer to the Administration Guide.

Data Flow

The Velocity Software component uses the same tables as the VMPRF component with some extensions. Although the names contain VMPRF, the data source is Velocity Software history files.

The Velocity Software component uses the DAY_OF_WEEK and PERIOD_PLAN control tables when updating all data tables except VMPRF_CONFIG_T. The component also uses the USER_GROUP common lookup tables when updating the VMPRF_USER_x data tables.

LOG AND RECORD DEFINITIONS

Log NameVelocity Software history file typeDescription / Selection Criteria for logs
  1. VELLVSYS
  2. VELLVCPU
  3. VELLVUSR
  4. VELLVDEV
Note: For complete information on the data contained in the Velocity Software history files, refer to Velocity Software, Inc. documentation.

DATA TABLES

This section describes the data tables used by the Velocity Software component.

The default retention period for this table is 1825 days.

Software Release Requirements:

1. Tivoli Performance Reporter / MVS or Performance Reporter / OS390 Release 1.2, 1.3, or 1.4

Velocity Software, ESAMON Version 2.2

Performance Reporter Installation Instructions:

Load the following members into your *.LOCAL.DEFS dataset.

Process the member VELIVM, by using the Other pulldown member, Option 5.Process Performance Reporter Statements.

Enter the correct name of your *.LOCAL.DEFS dataset in the panel (with no around it), select the options as shown in the box below, and press PF5 to execute.

 
Process Performance Reporter Statements
 
 Type in the data set name. Then press Enter to edit the statements.
 
 Input data set name  xxxxxxx.LOCAL.DEFS(VELIVM)
 
 Type of statements  . . . . 1_  1.  Log collector
                                 2.  Report definition
 
 Show input statements . . . 2   1.  Yes
                                 2.  No
 
 Trace SQL calls . . . . . . 2   1.  Yes
                                 2.  No
 
  F1=Help     F2=Split    F5=Execute  F9=Swap    F12=Cancel
Once the Install member VELIVM has been processed, the new component, VM-ESAMAP by Velocity Software will be displayed on the Components panel. You can install the new component from the Components dialog panel, by selecting it and pressing PF6.

VM - ESAMAP (Velocity Software) Component


If you can't measure it, I'm just NOT interested!(TM)

COPYRIGHT 8, 1999 - VELOCITY SOFTWARE, INC. WEBMASTER@velocity-software.com



Don't miss Velocity Software's Performance Seminars