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.
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:
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.
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
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=CancelOnce 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