HP NonStop G-Series User Manual
Page 41
Measure Command Interface (MEASCOM)
Measure User’s Guide — 520560-003
2- 13
Modifying D-Series Command Files for Systems
Running G-Series RVUs
Modifying D-Series Command Files for
Systems Running G-Series RVUs
After you migrate from a D-series RVU to a G-series RVU, you might have to change
your Measure command (OBEY) files.
In command files written for D-series RVUs, you use channel, controller, and unit
numbers to identify specific storage devices (DEVICE, DISC) and communication
devices (LINE, NETLINE, TERMINAL). In G-series RVUs, instead of channel,
controller, and unit numbers, you must specify group, module, and slot numbers for
storage devices, or track ID, CLIP, and line numbers for communication devices.
Therefore, you must change any command file that specifies channel, controller, or
unit.
You might not have to change a command file that specifies all devices of a particular
type (such as ADD DISC *) or that specifies only a CPU number or device name.
Assuming that the CPU and device exist on the G-series RVU, the command file runs
without modification.
The CONTROLLER entity type does not exist in G-series PVUs. It is replaced by the
SERVERNET entity type, which measures ServerNet addressable controllers (SACs).
However, you can use a command file that specifies all controllers (ADD
CONTROLLER *) to measure all SACs on a G-series RVU. To measure a specific
SAC, you must use the SERVERNET entity type and specify the SAC identifiers.
Similar considerations apply to custom measurement applications migrated from a
D-series RVU to a G-series RVU. To modify applications to measure G-series entities,
see
Modifying D-Series Applications for G-Series Systems
Accessing D-Series Measurement Files From a
System Running a G-Series RVU
You can access a measurement data file created by a D-series PVU of the Measure
performance monitor from a system running a G-series RVU. However, you must use a
D-series PVU of MEASCOM. To ensure compatibility with all D-series RVUs, always
use the most recent D-series MEASCOM.
In all Measure PVUs, the MEASFH version and the data file version must be the same.
You must use D30 MEASFH to access a D30 data file, G02 MEASFH to access a G02
data file, and so on.
Note.
OPDISK entities are also identified by channel, controller, and unit numbers. Optical
disks are currently supported only in D-series RVUs.