This chapter describes the HP NonStop utility programs MEASFLS and MEASRPT that assist with the sizing of Oracle GoldenGate trails.
Specifically:
MEASFLS parameters collect statistics using the Measure program.
MEASRPT parameters interpret the statistics collected by MEASFLS and produce a report to assist with sizing.
MEASFLS starts Measure processes for collecting file I/O data at specified intervals. The collected data is used by MEASRPT to generate a report. See the Administering Oracle GoldenGate for HP NonStop (Guardian) for details about creating the MEASFLS parameter file and running the program.
This section includes an alphabetic listing of the MEASFLS parameters shown in the following summary table.
| Parameter | Description |
|---|---|
DURATION |
Determines how long the measurement runs. |
FILE |
Specifies a file name or wildcard file set. |
FILEMEGABYTES |
Enables the explicit sizing of Measure files. |
GETSYSTEMUTILS |
Specifies whether TMF statistics are collected for programs that reside on |
GETTMFDETAIL |
Specifies the collection of TMF begin and abort transaction statistics on a per-process basis. |
INTERVAL |
Specifies a reporting interval for gathering statistics. |
MAXFILESPERMEAS |
Increases the number of files per measure. |
MEASFILES |
Identifies the location for the files that Measure uses to gather statistics. |
PURGEMEASFILES |
Controls whether existing measurement files are purged before starting Measure (default is |
START |
Controls when the measurement starts. |
STOP |
Controls when the measurement stops. |
WILDCARD |
Specifies a name of a file or wildcard file set. |
Use DURATION to specify a length of time for collecting measurements in terms of minutes, hours, or days. The following is an example:
DURATION 48 HOURS
It starts measurements at the time specified by the START parameter, and continues until 48 hours have elapsed.
Alternatively, you can use the STOP parameter to specify a time, such as 15:00:00, to stop measurements.
One day
DURATION number {MINUTES | HOURS | DAYS}
numberThe amount of time for collecting measurements.
MINUTES | HOURS | DAYSThe unit of time for collecting data.
Use FILE to specify a file set to collect measured data. You can include multiple FILE statements or use wildcard arguments. However, when using wildcards, the arguments are expanded, creating an entry for each file on the system that satisfies the wildcard definition.
For example, FILE $DATA3.SUB1.ACCOUNT explicitly names the file set. Alternatively, FILE $DATA*.SUB?.FL2 uses a wildcard argument to specify any file set in any volume beginning with $DATA, and any subvolume with the name SUBn, that contains a file set FL2.
Whenever possible, use the WILDCARD parameter as an alternative to wildcard arguments to reduce the chances of collecting unnecessary measurements. However, be aware that FILE gives you more flexibility for defining file sets than does WILDCARD.
For example, use FILE to explicitly specify secondary partitions you wish to measure block-level activity against, such as from FUP LOAD. Using FILE, you can also filter out activity against selected files and types of files during the reporting phase. Explicitly specifying the files that might be accessed during data gathering allows more flexible reporting.
FILE $vol.subvol.fileset
$vol.subvol.filesetThe fully qualified file set name.
Use FILEMEGABYTES to set the size of Measure files.
FILEMEGABYTES megabytes
megabytesThe file size, in megabytes.
Use GETSYSTEMUTILS to specify whether or not TMF statistics are collected for programs that reside on $SYSTEM (notably SQLCI).
OFF (Do not collect TMF statistics)
GETSYSTEMUTILS {ON | OFF}
Use GETTMFDETAIL to specify whether or not TMF statistics are collected on a per-process basis.
OFF (Do not collect TMF statistics)
GETTMFDETAIL {ON | OFF}
Use INTERVAL to specify a statistics reporting interval in terms of the amount of minutes, hours, or days that have elapsed. For example, INTERVAL 30 MINUTES, reports performance statistics every 30 minutes.
You can specify short reporting intervals for MEASFLS, then longer intervals for MEASRPT (using the MEASRPT INTERVAL parameter). Since short intervals can consume significant amounts of disk space and CPU, intervals of at least 30 minutes are recommended and should suffice for most installations. INTERVAL determines the level that peak activity can be reported against.
One hour
INTERVAL num_units unit
num_unitsThe amount of time for collecting data.
unitThe interval for collecting data. Enter one of the following literal values:
MINUTES
HOUR
DAY
Use MAXFILESPERMEAS to change the default maximum number of files per measure.
40
MAXFILESPERMEAS num_files
num_filesThe number of files per measure. The maximum is 40,000.
Use MEASFILES to identify the locations of the file sets into which Measure gathers statistics. The MEASFLS program creates one measurement, and one Measure file, for every 40 file entries created with the FILE parameter. If a FILE entry expands to 120 files, for example, three Measure files are required.
If you specify file locations with the WILDCARD parameter, only one file set argument is required since MEASFLS relies on Measure to control the expansion.
If you are specifying PURGEMEASFILES ON, MEASFILES must follow PURGEMEASFILES.
MEASFILES $vol.subvol.fileset
$vol.subvol.filesetA fully qualified file set name with the file portion no more than six characters. MEASFLS appends a sequence number to the MEASFILES entry for each measurement
MEASFILES $DATA3.MEASDAT.MDAT
WILDCARD $*.DAT*
Use PURGEMEASFILES to control whether or not existing measurement files are purged before starting the Measure program.
Must precede the MEASFILES parameter.
OFF (Do not purge measurement files)
PURGEMEASFILES {ON | OFF}
Use START to define when the measurements begin. The default is the date and current time. For example, START 2010-03-12 15:00:00, specifies measurements to start on March 12, 2010 at 1500 hours.
By default, the current time is rounded up to an even unit of time. For example, if the current time is 9:52, and the INTERVAL parameter specifies 1 hour for the time argument, the measurement starts at 10:00.
The current date and time
START date time
dateThe date in yyyy-mm-dd format. The default is the current date.
timeThe time is hh:mm:ss format. The default is the current time, rounded to the next hour. When specifying a time, specify 00 (zeros) for minutes and seconds.
Use STOP instead of the DURATION and START parameters for specifying a time of day to stop measurements. For example, STOP 2010-03-12 15:00:00 specifies measurements to stop on March 12, 2010 at 1500 hours.
Alternatively, you can use the DURATION and START parameter.
The default is the start time defined with the START parameter plus the default value for the DURATION parameter (one day). The STOP time is rounded up to an even interval. For example, if the stop time is 13:45, and the INTERVAL parameter specifies one hour, the measurement stops at 14:00.
STOP date time
dateThe date in yyyy-mm-dd format. The default is the current date.
timeThe time is hh:mm:ss format. The default is the current time, rounded to the next hour. When specifying a time, specify 00 (zeros) for minutes and seconds.
Use the WILDCARD parameter instead of FILE or MEASFILES to let the Measure program determine the files and file sets to configure and use.
WILDCARD arguments may contain $* to designate any volume, * to designate any subvolume, and * to designate any file, in a syntax similar to: WILDCARD $*.DAT.*.
The wildcard indicator cannot be combined with letters.
Use WILDCARD instead of FILE whenever possible to reduce the number of possible Measure configurations. WILDCARD produces only one measurement entity to configure. FILE creates an entry for each item satisfying the wildcard. In addition, WILDCARD allows activity to be detected against files that have not yet been created.
To measure block-level activity against secondary partitions of files (for example, from a FUP LOAD), include those partitions explicitly.
You can filter out activity against selected files and types of files during the reporting phase. Specifying the most files that might be accessed during reporting in the data gathering phase allows more flexible reporting.
WILDCARD file_set
file_setIndicates a volume, subvolume, or file set.
| Valid WILDCARD Examples | Invalid WILDCARD Example |
|---|---|
WILDCARD $*.DAT.* WILDCARD $DATA3.SUBV.* |
WILDCARD $DATA3.DAT.FL* You cannot combine a volume, subvolume, or file name with a wildcard designator. |
MEASRPT outputs Oracle GoldenGate for Mainframe sizing statistics gathered by MEASFLS. See the Administering Oracle GoldenGate for HP NonStop (Guardian) for details about creating the MEASFLS parameter file and running the program.
This section contains an alphabetic listing of MEASRPT parameters shown in the following table.
| Parameter | Description |
|---|---|
AVGCOMPRESSEDBYTES |
Estimates the bytes needed per update record for bandwidth and disk storage. |
DEFAULTEXCLUDES |
Determines whether or not I/O resulting from OSIMAGE and ORSERV ( |
DURATION |
Determines the reporting period. |
EXCLUDEALTKEYS |
Determines whether or not statistics for alternate key files are included in the report. |
EXCLUDEFILE |
Determines whether or not statistics for a file set are included in the report. |
EXCLUDEPROGRAM |
Determines whether or not statistics for files updated by the specified programs are excluded from the report. |
EXCLUDETANDEMFILES |
Determines whether or not statistics for files with file codes between 1 and 1000 are excluded. |
Reporting Lag Information |
Determines whether or not the details of each file's activity are reported by reporting period. |
GETAUDITED |
Determines whether or not audited files are included in the report. |
GETENSCRIBE |
Determines whether or not Enscribe files are included in the report. |
GETNONAUDITED |
Determines whether or not non-audited files are included in the report. |
GETSQL |
Determines whether or not NonStop SQL tables are included in the report. |
GETTMFDETAIL |
Determines whether or not TMF transaction information is reported on a per-program basis. |
INCLUDEFILE |
Determines whether or not statistics for a file set are included in the report. |
INCLUDEPROGRAM |
Determines whether or not statistics for files updated by the programs specified are included in the report. |
INTERVAL |
Specifies an interval for reporting peak activity. |
LISTLIMIT |
Limits the number of files and programs listed in the report to those files or programs that generate the most output activity. |
MEASFH |
Identifies the location of the MEASFH program. |
MEASFILES |
Identifies the location of the files Measure will use to report statistics. |
PROGDETAIL |
Determines whether or not to report details regarding each program that updates the specified files. |
PROGSTATS |
Determines whether or not to report statistics for programs that update the file set specified. |
REPORTRATE |
Determines whether or not statistics are reported as absolute numbers or on a per-second basis. |
RETENTION |
Estimates the maximum disk file capacity needed for an extended outage. |
START |
Controls when the reporting period starts. |
STOP |
Controls when the reporting period stops. |
SUPPRESSZEROTOTALS |
Determines whether or not to report files for which statistics were captured but did not experience file updates. |
Use AVGCOMPRESSEDBYTES to estimate the bytes needed per update record for bandwidth and disk storage. This figure approximates the maximum number of bytes likely to change in records or rows. For SQL, this is the number of columns specified in an update statement, plus the key.
100 bytes
AVGCOMPRESSEDBYTES bytes
bytesThe number of bytes needed per update record.
Use DEFAULTEXCLUDES to determine whether or not I/O resulting from OSIMAGE and ORSERV (FUP RELOAD) is excluded from the report.
ON (exclude results)
DEFAULTEXCLUDES {ON | OFF}
Use DURATION to specify a length of time for collecting measurements in terms of minutes, hours, or days. For example, DURATION 48 HOURS, starts measurements at the time specified by the START parameter, and continues until 48 hours have elapsed.
Alternatively, you can use the STOP parameter to specify a time, such a 15:00:00, to stop measurements.
One day
DURATION num_units unit
num_unitsThe amount of time for collecting measurements.
unitThe unit of time for collecting data. Enter one of:
MINUTES
HOURS
DAYS
Use EXCLUDEALTKEYS to determine whether or not statistics for alternate key files are included in the report.
ON (exclude alternate keys)
EXCLUDEALTKEYS {ON | OFF}
Use EXCLUDEFILE to determine whether or not statistics for a file set are included in the report.
Include all files gathered in the statistics phase
EXCLUDEFILE file_set
file_setThe fully qualified file set to exclude. You can use wildcards.
EXCLUDEFILE $DATA*.MYAPP*.FL?
Use EXCLUDEPROGRAM to determine whether or not statistics for files updated by the specified programs are excluded from the report. For example, EXCLUDEPROGRAM $SYSTEM.SYS*.FUP excludes updates from FUP.
Exclude FUP RELOADS
EXCLUDEPROGRAM file_set
file_setThe fully qualified program name to exclude.
Use EXCLUDETANDEMFILES to determine whether or not statistics for files with file codes between 1 and 1000 are captured. Setting this parameter to ON results in the exclusion of object, EDIT and other files from the report.
Exclude files
EXCLUDETANDEMFILE $vol.subvol.fileset
$vol.subvol.filesetThe fully qualified file set to exclude.
EXCLUDETANDEMFILE $DATA*.MYAPP*.FL???
Use FILEDETAIL to determine whether or not the details of each file's activity are reported by period. If you do not specify FILEDETAIL, only summary totals are provided per period, along with a report of peak file activity.
ON (include file activity details)
FILEDETAIL {ON | OFF}
Use GETAUDITED to determine whether or not audited files are included in the report.
ON (include audited files)
GETAUDITED {ON | OFF}
Use GETENSCRIBE to determine whether or not Enscribe files are included in the report.
ON (include Enscribe files)
GETENSCRIBE {ON | OFF}
Use GETNONAUDITED to determine whether or not non-audited files are included in the report.
ON (include non-audited files)
GETNONAUDITED {ON | OFF}
Use GETSQL to determine whether or not NonStop SQL tables are included in the report.
ON (include SQL tables)
GETSQL {ON | OFF}
GETTMFDETAIL determines whether or not TMF transaction information is reported on a per-program basis. If you want to report on TMF transaction information, the MEASFLS GETTMFDETAIL parameter must also specify ON.
ON
GETTMFDETAIL {ON | OFF}
Use INCLUDEFILE to determine whether or not statistics for a file set are included in the report. The default is to include all files gathered in the statistics phase.
If INCLUDEFILE is specified for one file set, then only files included with other INCLUDEFILE entries are output (unless excluded with EXCLUDEFILE).
INCLUDEFILE file_set
file_setThe fully qualified file set to include.
INCLUDEFILE $DATA*.MYAPP*.FL??
Use INCLUDEPROGRAM to determine whether or not statistics for files updated by the programs specified are included in the report. For example, INCLUDEPROGRAM $DATA2.APPLPROG.*, includes all programs in the $DATA2.APPLPROG file set.
If INCLUDEPROGRAM is specified for one set of programs, then only statistics explicitly named in other INCLUDEPROGRAM entries are output. To explicitly include a program, specify an argument similar to INCLUDEPROGRAM $DATA2.APPLPROG.program_name.
If no INCLUDEPROGRAM entries are found, all program updates are included in the report unless excluded by the EXCLUDEPROGRAM parameter.
All program updates (except as excluded with EXCLUDEPROGRAM)
INCLUDEPROGRAM file_set
file_setThe fully qualified program name to include.
Use INTERVAL to specify a statistics reporting interval in terms of the amount of minutes, hours, or days that have elapsed. For example, INTERVAL 30 MINUTES, reports performance statistics every 30 minutes.
You can specify short reporting intervals for MEASFLS, then longer intervals for MEASRPT (using the MEASRPT INTERVAL parameter). Since short intervals can consume significant amounts of disk space and CPU, intervals of at least 30 minutes are recommended and should suffice for most installations. INTERVAL determines the level that peak activity can be reported against.
The MEASRPT INTERVAL parameter can exceed that previously specified by the MEASFLS INTERVAL parameter.
Interval specified by MEASFLS INTERVAL
INTERVAL num_units unit
num_unitsThe amount of time for collecting data.
unitThe interval for collecting data. Enter one of:
MINUTES
HOUR
DAY
Use LIMITLIST to include only those files and programs in the report that generate the most output activity. You can limit the number of included files by specifying the count argument. For example, LISTLIMIT 20, lists only the 20 most active files and programs.
LISTLIMIT count
countLimits the number of reported files and programs to the first n files and programs specified as count.
Use MAXSTATPROGS to change the default table size for the number of process entities that MEASRPT tracks.
2000
MAXSTATPROGS num_entries
num_entriesThe number of entries to track.
Use MEASFH to identify the location of the MEASFH program.
When processing Measure data from a customer you often have to use the MEASFH object that matches the customer Measure date file. If specified, the MEASFH file name will be passed into MEASOPEN(); otherwise MEASOPEN() uses the default on the local system.
MEASFH file_name
file_nameThe name of an object file. The name may be partially qualified.
Use MEASFILES to identify the locations of the file sets Measure will use to report statistics.
MEASFILES file_set
file_setA fully qualified file set name to be included in reports.
MEASFILES $DATA3.MEASDAT.MDAT
Use MAXSTATFILES to specify internal statistics arrays larger than 10,000 entries. Allocate one entry per file measured in the system.
MAXSTATFILES num_files
num_filesThe number of files.
Use MAXSTATPROGS to change the default table size for the number of process entities that MEASRPT tracks.
2000
MAXSTATPROGS num_entries
num_entriesThe number of entries
Use PROGDETAIL to determine whether or not to report details about each program that updates the specified files.
ON (report details)
PROGDETAIL {ON | OFF}
Use PROGSTATS to determine whether or not to report statistics about programs that update the file set specified.
ON (report statistics)
PROGSTATS {ON | OFF}
Use REPORTRATE to determine whether or not statistics are reported as absolute numbers or on a per-second basis. For example, REPORTRATE ON, reports statistics on a per-second basis.
OFF (report absolute numbers)
REPORTRATE {ON | OFF}
Use RETENTION to estimate the maximum disk file capacity needed for an extended outage. For example, RETENTION 1 DAYS, specifies to retain one day.
One day
RETENTION num_units unit
num_unitsThe amount of time for collecting data.
unitThe interval for collecting data. Enter one of:
HOURS
DAYS
Use START to control when the reporting period starts. For example, START 2010-03-12 15:00:00, starts reporting at 1500 hours on March 12, 2010.
START date time
dateThe date in yyyy-mm-dd format. The default is the date at which the measurement was started by the MEASFL START parameter.
timeThe time is hh:mm:ss format. The default is the time the measurement was started by the MEASFL START parameter.
Use STOP to control when the reporting period stops. For example, STOP 2010-03-12 15:00:00, stops reporting at 1500 hours on March 12, 2010.
STOP date time
dateThe date in yyyy-mm-dd format. The default is the date at which the measurement was started by the MEASFL START parameter.
timeThe time is hh:mm:ss format. The default is the time the measurement was started by the MEASFL START parameter.
Use SUPPRESSZEROTOTALS to determine whether or not to report files for which statistics were captured but did not experience file updates.
ON (suppress zero totals)
SUPPRESSZEROTOTALS {ON | OFF}