Measure Reference Manual

Usage Note for H-Series and J-Series DEVICE Entities
• For CLIM-attached devices in Measure H03/J01 and later PVUs, the DEVICE entity specification
is updated to include lun and path and to not use scsi-id. As with FCSA devices, this
entity specification can be used in the ADD, DELETE, LIST, LISTACTIVE, and LISTALL commands.
NOTE: Although the path field still appears in PLPT structure in the ZMS Style DDL DEVICE
record syntax, in H06.23/J06.12 and later RVUs, use of the path field is disallowed for
DEVICE entities and only supported for CLIM-attached DISC entities.
• In H-series and J-series RVUs, all byte-count fields accommodate 64 bits. Field names ending
in -F are no longer used in ZMS style records but remain available to applications that request
data in legacy style.
Usage Note for G-Series DEVICE Entities
The DEVICE entity in G-series Measure is used only for tapes. TIL and THL are obsolete, and all
printer support is through LAN-attached devices. Tape is supported as a SCSI device and shares
module driver code with disk operations.
The 64-bit byte-count fields (fields ending in -F) collect the same data as older 32-bit byte-count
fields. For example, the 64-bit field INPUT-BYTES-F collects the same data as the 32-bit field
INPUT-BYTES. The 64-bit fields are less subject to overflow caused by high levels of I/O activity.
The 32-bit fields are currently active and continue to return values. If there is no field overflow, the
32-bit fields and the 64-bit fields return the same value. If a 32-bit field overflows, the corresponding
64-bit field returns the correct value, and the 32-bit field returns a value of -1. The ERROR field for
the measured entity also returns -1 to indicate an overflow condition.
Convert your applications to use the 64-bit fields; 32-bit fields might be deactivated in a future
release.
In MEASCOM commands and command (OBEY) files, use the names of the 32-bit fields. For
example, issue the command LIST DEVICE BY INPUT-BYTES, not LIST DEVICE BY INPUT-BYTES-F.
MEASCOM uses the names of the 32-bit fields in output displays such as reports and plots.
Usage Note for D-Series DEVICE Entities
You can use a D-series measurement application to measure devices on NonStop S-series servers
if the application specifies all devices (ADD DEVICE *) or specifies only $device or $device
(cpu). If the application specifies controller, channel, or unit, you must modify the entity
identifiers to measure NonStop S-series devices.
Examples
DescriptionCommand
Measure device named $TAPEADD DEVICE $TAPE
Measure all devicesADD DEVICE *
Measure all devices in CPU 2ADD DEVICE $* (2)
Measure all devices attached to a controller whose GMS is 110,3,1 and
whose scsi-id is 2 (ServerNet/DA or FCSA storage devices only)
ADD DEVICE $* (*, *, 110, 3, 1, 2)
Measure all devices attached to the SAC named CLIM3ADD DEVICE $* (*,*,CLIM3)
188 Entities and Counters