Users Guide

20 Introduction
The next level of complexity includes commands that contain command
levels 1 and 2. All of the about commands are examples of command level 2
complexity. The omconfig about and omreport about commands cause a very
brief summary to display. The summary shows version information for the
systems management software installed on your system; for example, Server
Administrator 1.x.
Some commands have command level 1 and command level 2 and one
name=value pair. Consider the following example command that instructs
Server Administrator for more details about the environment for Server
Administrator:
omreport about details=true
Command level 1 is omreport, command level 2 is about, and the name=
value pair is
details=true.
Many commands use command level 1, command level 2, and command level
3, but do not require any parameters (name=value pairs). Most omreport
commands are of this type. For example:
omreport system alertaction
causes a list of alert actions that are configured for components on your
system to be displayed.
The most complex commands have all three command levels and can
have multiple name=value pairs. An example of two name=value pairs:
omconfig system assetinfo info=depreciation
duration=3
An example of nine name=value pairs:
omconfig system assetinfo info=acquisition
purchasecost=
<n> waybill=<n> installdate=<mmddyy>
purchasedate=<mmddyy> ponum=
<n> signauth=<text>
expensed=<yes | no> costcenter=<text>
In each section, command syntax and other information about commands is
formatted with any of the following fields that apply:
command level 1 command level 2 command level 3 name=value pair 1 name=value pair 2