startcondresp Command

Purpose

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

Syntax

To start monitoring a condition:

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

To unlock or lock the condition/response association:

startcondresp {-U | -L} [-h] [-TV] condition[:node_name] response

Description

The startcondresp command starts the monitoring of a condition that has a linked response. A link between a condition and a response is called a condition/response association. 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.

If a particular condition/response association is needed for system software to work properly, it may be locked. A locked condition/response association cannot be started by the startcondresp command. If the condition/response association you specify on the startcondresp command is locked, it will not be started; instead an error will be generated informing you that this condition/response association is locked. To unlock a condition/response association, you can use the -U flag. However, because a condition/response association is typically locked because it is essential for system software to work properly, you should exercise caution before unlocking it. To lock a condition/response association so it cannot be started, stopped, or removed, reissue this command using its -L flag.

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.
-U: Unlocks a condition/response association so it can be started, stopped, or removed. If a condition/response association is locked, this is typically because it is essential for system software to work properly. For this reason, you should exercise caution before unlocking it. When unlocking a condition/response association using the -U flag, no other operation can be performed by this command.
-L: Locks a condition/response association so it cannot be started, stopped, or removed. When locking a condition/response association using the -L flag, no other operation can be performed by this command.

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 one or more responses. 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: Administration Guide 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_IP_AUTHENT

When the CT_IP_AUTHENT environment variable exists, the RMC daemon uses IP-based network authentication to contact the RMC daemon on the system that is specified by the IP address to which the CT_CONTACT environment variable is set. CT_IP_AUTHENT only has meaning if CT_CONTACT is set to an IP address; it does not rely on the domain name system (DNS) service.

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.

Implementation Specifics

This command is part of the Reliable Scalable Cluster Technology (RSCT) fileset for AIX®.

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