Measure Reference Manual

Future RVUs might adjust the mixed workload design to let applications take full advantage
of the increase in CPU and disk capacity. The adjustment in design might require priority
adjustments to the mixed workload environment. The most recent changes of the mixed workload
algorithm include adjustments to let you increase the speed of the query but cause only
moderate increases in response time.
NOTE: For guidelines to control mixed workload applications using priority settings, see the
white paper Mixed Workload Priority Guide, Version Id.: 1.0, Date: September 2001.
Usage Note for D-Series DISC Entities
You can use a D-series measurement application to measure disks on NonStop S-series servers if
the application specifies all disks (ADD DISC *) or specifies only $disk or $disk (cpu). If an
application specifies controller, channel, or unit, you must modify the entity identifiers to
measure NonStop S-series disks.
Examples
DescriptionCommand
Measure disk named $SYSTEM (all paths)ADD DISC $SYSTEM
Measure all disksADD DISC *
Measure all disks in CPU 2ADD DISC $* (2)
Measure all disks attached to a controller whose GMS is 110,3,1 and
whose scsi-id is 2 (ServerNet/DA or FCSA storage devices only)
ADD DISC $* (*, *, 110, 3, 1, 2)
Measure backup path of $SYSTEMADD DISC $SYSTEM-B
Measure all disks attached to the SAC named CLIM3ADD DISC $* (*,*,CLIM3)
DISCOPEN
The DISCOPEN entity measures the I/O operations performed by the disk process on a specified
file (physical file access) on behalf of an individual open of a file. The measured file must be local
to the system being measured, but the process accessing the measured file can be local or remote.
NOTE: The keyword DISKOPEN is interchangeable with DISCOPEN in any MEASCOM command
except HELP.
In Measure G09 and later PVUs, the DISCOPEN entity supports the use of OSS file pathnames. It
displays OSS file pathnames in DISCOPEN reports and provides direct mapping between external
structured records and OSSNAMES structured record output.
In Measure H01 and later PVUs, MEASCOM accepts ANSI SQL names in a DISCOPEN entity
specification.
PageTopic
209Entity specification syntax for DISCOPEN entities
210DDL records for DISCOPEN entities
212DDL field definitions for DISCOPEN entities
215Usage notes for DISCOPEN entities
217Example of DISCOPEN measurement
208 Entities and Counters