Commands Reference, Volume 5

startcondresp Command

Purpose

Starts monitoring a condition that has one or more linked responses.

Syntax

startcondresp [-h] [-TV] condition[:node_name] [response [response...]]

Description

The startcondresp command starts the monitoring of a condition that has a linked response. In a cluster environment, the condition and the response must be defined on the same node. After monitoring is started, when the condition occurs, the response is run. If no responses are specified, monitoring is started for all responses linked to the condition. This causes all of the linked responses to run when the condition occurs. If more than one response is specified, monitoring is started only for those linked responses.

If one or more responses are specified and the responses are not linked with the condition, the startcondresp command links the specified responses to the condition, and monitoring is started. Use the mkcondresp command to link a response to a condition without starting monitoring.

Flags

-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: Specifies the name of the condition linked to the response. The condition is always specified first.
node_name: Specifies the node in the domain 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.
response: Specifies the name of a response or more than one response. Specifying more than one response links the responses to the condition if they are not already linked and starts monitoring for the specified responses.

Security

The user needs write permission for the IBM.Association resource class to run startcondresp. Permissions are specified in the access control list (ACL) file on the contacted system. See the 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 start monitoring for the condition "FileSystem space used " by using the response "Broadcast event on-shift", whether or not the response is linked with the condition, run this command:
```
startcondresp  "FileSystem space used" "Broadcast event on-shift"                               												
	
```
To start monitoring for the condition "FileSystem space used " by using all of its linked responses, run this command:
```
startcondresp "FileSystem space used" 
```
To start monitoring for the condition "FileSystem space used " by using the response "Broadcast event on-shift" and "E-mail root anytime", whether or not they are linked with the condition, run this command:
```
startcondresp "FileSystem space used" "Broadcast event on-shift" "E-mail root anytime"
```

These examples apply to management domains:

To start monitoring for the condition "FileSystem space used" on the management server using the response "Broadcast event on-shift", whether or not the response is linked with the condition, run this command on the management server:
```
startcondresp  "FileSystem space used" "Broadcast event on-shift"                               												
	
```
To start monitoring for the condition "FileSystem space used" on the managed node nodeB using the response "Broadcast event on-shift", whether or not the response is linked with the condition, run this command on the management server:
```
startcondresp  "FileSystem space used":nodeB "Broadcast event on-shift"                               												
	
```

This example applies to peer domains:

To start monitoring for the condition "FileSystem space used" on nodeA in the domain using the response "Broadcast event on-shift" (also on nodeA in the domain), whether or not the response is linked with the condition, run this command on any node in the domain:
```
startcondresp  "FileSystem space used":nodeA "Broadcast event on-shift"                               												
	
```

Location

/usr/sbin/rsct/bin/startcondresp: Contains the startcondresp command

Related Information

ERRM commands: lscondresp, mkcondition, mkcondresp, mkresponse, stopcondresp

Files: rmccli

Books: see the RSCT Guide and Reference for more information about ERRM operations