Parstatus -P -V: Apparent Incorrect Output; Parstatus: Local Partition Error; Parstatus: Unable To Get Read Lock Error; Using Wmiop.exe To Pinpoint Problems - HP Rx2620-2 - Integrity - 0 MB RAM Manual

Parstatus -p -V: apparent incorrect output

This issue occurs when the parstatus -p -Vcommand appears to give incorrect output. In
reality these are not errors at all, since the output displayed for "PDC Revision" should be
interpreted as your "system firmware revision". Also, the output displayed for "IODCH Version"
(seen as "FFFF") is only relevant with PA-RISC systems. This output should be ignored, since
it is not valid for Integrity servers running Windows Server 20003.

Parstatus: local partition error

After using the parstatus command you might see the following message:
Note: The -g option can require up to 2 minutes to complete. Please
wait...
Error: Unable to get the local partition number.
This error occurs when the -w and -g options are used in the same command. This is actually a
syntax error, since there is no local partition when using the -g option.

Parstatus: unable to get read lock error

After using the parstatus command you might see the following message:
Note: The -g option can require up to 2 minutes to complete. Please
wait...
Error: Unable to get read lock for partition.
This error occurs when a lock has been placed on the partition. The lock might have been issued
by an Administrator or by an application. If it was issued by an application that has terminated,
you can remove it using the parunlock command.

Using WMIOP.EXE to pinpoint problems

When relying on multiple software components that are running simultaneously, locating the
source of a problem can sometimes be difficult. In cases where an error message does not
adequately describe the source of the problem, or when the error could have multiple causes,
using the "wmiop.exe" utility that is included with the WMI Mapper component can help track
the problem down.
Wmiop.exe is installed in the %PEGASUS_HOME%\bin directory. Since this directory is added
to the PATH during installation, wmiop can be executed from any directory. If it cannot, that is
your first indication that something is wrong, most likely that your PATH environment variable
is not set correctly.
Syntax for the wmiop utility is described below (an abbreviated usage explanation can also be
viewed from the command line by running wmiop with no options):
Usage:
wmiop <cimoperation> [arg, ...]
Implemented operations (not case sensitive) are:
getClass|gc <class>
enumerateClassNames|ecn [ <class> ]
getInstance|gi <class> [ list ]
enumerateInstances|ei <class>
enumerateInstanceNames|ein <class>
getProperty|gp <class> { ask | list } [ <propnam> ]
setProperty|sp <class> { ask | list } [ <propnam> [ <value> ] ]
114 Troubleshooting