[ Bottom of Page | Previous Page | Next Page | Contents | Index | Library Home |
Legal |
Search ]
Commands Reference, Volume 3
lscondresp Command
Purpose
Lists
information about a condition and its linked responses, if any.
Syntax
lscondresp [-a | -n]
[ -l | -t | -d |
-D delimiter ] [-q] [-x] [-z] [-h] [-TV] [condition[:node_name] [response1 [response2...]]]
lscondresp [ -a | -n ]
[ -l | -t | -d |
-D delimiter] [-q] [-x] [-z] -r [-h] [-TV] response1[:node_name] [response2...]
Description
The lscondresp command lists information about a condition and
its linked responses. The information shows which responses are linked with
a condition and whether monitoring is active for a condition and its linked
response.
The following information is listed:
- Condition
- The name of the condition linked with a response.
- Response
- The name of the response linked with the condition.
- State
- The state of the response for the condition. The state indicates whether
a specified response is active or not.
- Location
- The location of the condition and the response.
To list a particular condition and response, specify both the condition
and the response. To list all responses to a condition, specify the condition
only. To list all conditions to which a response is linked, specify the response
and the -r flag. To list all conditions and their linked responses, do not specify
any condition or response parameters.
Specifying a node name limits the display to the linked conditions and
responses defined on that node. List all of the linked conditions and responses
on a node by specifying a colon (:) followed by the node name. The
node name is a node within the management scope determined by the CT_MANAGEMENT_SCOPE
environment variable. The management scope determines the list of nodes from
which the linked conditions and responses are listed. For local scope, only
linked conditions and responses on the local node are listed. For management
domain scope and peer domain scope, the linked conditions and responses
from all nodes within the domain are listed.
When neither the -a flag nor the -n flag is specified, all selected conditions for the responses are listed.
Tabular format is the default.
Flags
- -a
- Lists only those responses that are active for the condition.
- -n
- Lists only those responses that are not active for the condition.
- -l
- Displays the condition information and response information on separate
lines (long format).
- -t
- Displays the condition information and response information in separate
columns (table format).
- -d
- Specifies delimiter-formatted output. The default delimiter is a colon
(:). Use the -D flag if you want to change the default delimiter.
- -D delimiter
- Specifies delimiter-formatted output that uses delimiter. Use
this flag to specify
something other than the default colon (:). For example, when the
data to be displayed contains colons, use this flag to specify another delimiter of one or more characters.
- -q
- Does not return an error if either the condition or the response does not exist.
- -x
- Suppresses header printing.
- -z
- Specifies that this command applies to all nodes in the cluster. The
cluster scope is determined by the CT_MANAGEMENT_SCOPE environment variable.
If it is not set, first the management domain scope is chosen if it exists,
then the peer domain scope is chosen if it exists, and then local scope is
chosen, until the scope is valid for the command. The command will run once
for the first valid scope found. For example, if both a management and peer
domain exist, lscondresp -z with CT_MANAGEMENT_SCOPE not set will
list the management domain. In this case, to list the peer domain, set CT_MANAGEMENT_SCOPE
to 2.
- -r
- Indicates that all command parameters are responses. There are no conditions
specified. This lists all linked condition-response information for the specified
responses.
- -h
- Writes the command's usage statement to standard output.
- -T
- Writes the command's trace messages to standard error. For your software
service organization's use only.
- -V
- Writes the command's verbose messages to standard output.
Parameters
- condition
- The condition can be a condition name or a substring of a condition
name. When it is a substring, any defined condition name that contains the
substring and is linked to the response will be listed.
- response1 [response2...]
- This parameter can be a response name or a substring of a response name.
You can specify more than one response name. When it is a substring, any defined
response name that contains the substring and is linked to the condition will
be listed.
- node_name
- Specifies the node where the condition is defined. If node_name is not specified, the local node is used. node_name is a
node within the scope determined by the CT_MANAGEMENT_SCOPE environment variable.
Security
The user needs read permission for the IBM.Association resource
class to run lscondresp. Permissions are specified in the access
control list (ACL) file on the contacted system. See RSCT Guide and Reference for details on the ACL file and how to
modify it.
Exit Status
- 0
- The command ran successfully.
- 1
- An error occurred with RMC.
- 2
- An error occurred with a command-line interface script.
- 3
- An incorrect flag was entered on the command line.
- 4
- An incorrect parameter was entered on the command line.
- 5
- An error occurred that was based on incorrect command-line input.
Environment Variables
- CT_CONTACT
- Determines the system where the session with the resource monitoring
and control (RMC) daemon occurs. When CT_CONTACT is set to a host name or
IP address, the command contacts the RMC daemon on the specified host. If
CT_CONTACT is not set, the command contacts the RMC daemon on the local system
where the command is being run. The target of the RMC daemon session and
the management scope determine the resource classes or resources that are
processed.
- CT_MANAGEMENT_SCOPE
- Determines the management scope that is used for the session with the
RMC daemon in processing the resources of the event response resource manager
(ERRM). The management scope determines the set of possible target nodes
where the resources can be processed. The valid values are:
- 0
- Specifies local scope.
- 1
- Specifies local scope.
- 2
- Specifies peer domain scope.
- 3
- Specifies management domain scope.
If this environment variable is not set,
local scope is used.
Standard Output
When the -h flag is specified, this command's usage statement is written to standard
output. All verbose messages are written to standard output.
Standard Error
All trace messages are written to standard error.
Examples
These examples apply to standalone systems:
- To list all conditions with their linked responses, run this command:
lscondresp
The output will look like this:
Condition Response State Location
"FileSystem space used" "Broadcast event on-shift" "Active" nodeA
"FileSystem space used "E-mail root any time" "Not Active" nodeA
"Page in Rate" "Log event any time" "Active" nodeA
- To list information about the condition "FileSystem space used", run
this command:
lscondresp "FileSystem space used"
The output will
look like this:
Condition Response State Location
"FileSystem space used" "Broadcast event on-shift" "Active" nodeA
"FileSystem space used "E-mail root any time" "Not Active" nodeA
- To list information about the condition "FileSystem space used" for responses
that are active, run this command:
lscondresp -a "FileSystem space used"
The output will look like this:
Condition Response State Location
"FileSystem space used" "Broadcast event on-shift" "Active" nodeA
- To list information about the condition "FileSystem space used" with the
linked response "Broadcast event on-shift", run this command:
lscondresp "FileSystem space used" "Broadcast event on-shift"
The output will look like this:
Condition Response State Location
"FileSystem space used" "Broadcast event on-shift" "Active" nodeA
- To list all conditions that have the string space in their names
with their linked responses, run this command:
lscondresp space
The
output will look like this:
Condition Response State Location
"FileSystem space used" "Broadcast event on-shift" "Active" nodeA
"FileSystem space used "E-mail root any time" "Not Active" nodeA
These examples apply to management domains:
- In this example, the condition "FileSystem space used" is defined on the
management server. To list information about "FileSystem space used", run
this command on the management server:
lscondresp "FileSystem space used"
The output will look like this:
Condition Response State Location
"FileSystem space used" "Broadcast event on-shift" "Active" nodeB
"FileSystem space used" "E-mail root any time" "Not Active" nodeB
- In this example, the condition "FileSystem space used" is defined on the
managed node nodeC. To list information about "FileSystem space used",
run this command on the management server:
lscondresp "FileSystem space used":nodeC
The output will look like this:
Condition Response State Location
"FileSystem space used" "Broadcast event on-shift" "Active" nodeC
"FileSystem space used" "E-mail root any time" "Not Active" nodeC
This example applies to a peer domain:
- In this example, the condition "FileSystem space used" is defined in the
domain. To list information about "FileSystem space used", run this command
on one of the nodes in the domain:
lscondresp "FileSystem space used"
The output will look like this:
Condition Response State Location
"FileSystem space used" "Broadcast event on-shift" "Active" nodeD
"FileSystem space used" "E-mail root any time" "Not Active" nodeD
"FileSystem space used" "Broadcast event on-shift" "Active" nodeE
"FileSystem space used" "E-mail root any time" "Not Active" nodeE
Location
- /usr/sbin/rsct/bin/lscondresp
- Contains the lscondresp command
Related Information
ERRM commands: mkcondition, mkcondresp, mkresponse, rmcondresp, startcondresp, stopcondresp
Files: rmccli
Books: see the RSCT Guide and Reference for more information about ERRM operations
[ Top of Page | Previous Page | Next Page | Contents | Index | Library Home |
Legal |
Search ]