System Management Release Notes
4.19 WBEM Services and WBEM Providers for OpenVMS
4.19.3 Based on OpenPegasus 2.9
WBEM Services for OpenVMS Version 2.9 is based on the OpenPegasus 2.9 code
stream of The Open Group’s Pegasus open source project.
4.19.4 Supports nPartitions and iCAP
On cell-based systems, Version 2.0 supports local nPartitions and iCAP providers.
Only the functions and capabilities needed by these providers are supported.
4.19.5 Restart cimserver.exe to Unload Providers on OpenVMS
After entering the cimprovider -r command, you must stop and restart the
cimserver to complete the process of replacing a provider. (OpenVMS does not
support unloading a dynamically loaded image.)
4.19.6 Use Quotes Around Command Line Options
Ensure that you use quotes around a command line option to preserve its case.
For example,
Correct:
$ cimmofl "-E" "--xml"
Incorrect:
$ cimmof -E -xml
4.20 Writing the System Dump File to an Alternate Disk
V8.4
On Superdome class of servers, writing the system dump file to an alternate disk
(DOSD) does not work and the following message is displayed:
**** Unable to locate SYSDUMP.DMP on any valid DUMP_DEV device
**** Attempting to write the crash dump to the system disk
4.21 Monitor Utility Changes
The Monitor utility (MONITOR) has undergone several changes since OpenVMS
Version 7.3-2. Most of these changes are related to providing improved formatting
of the recording file and including additional class data. These changes have
introduced some compatibility issues between data collected by one version of
MONITOR that is subsequently processed by another version. This section
discusses these issues.
4.21.1 Guest Operating System on Integrity VM
V8.4
OpenVMS Integrity servers Version 8.4 supports Guest Operating System on HP
Integrity Virtual Machines (Integrity VM). When the OpenVMS Integrity servers
is running as a guest on an Integrity VM system, the monitor utility indicates the
amount of CPU time used by the guest. The Monitor also indicates the amount of
CPU time allocated to the guest by Integrity VM.
The
MONITOR MODES
and
MONITOR SYSTEM /ALL
commands provide this information.
When the system is running as a guest, the above commands display "In use
by Host" instead of "Compatibility Mode". This field is to be interpreted as the
amount of CPU time that was unavailable to the current guest and that is being
used by the other guests or Integrity VM. The display is scaled based on the
number of vCPUs (Virtual CPUs) configured for the guest irrespective of the
actual number of physical CPUs in the host.
System Management Release Notes 4–19
