rmcondresp Command

Purpose

Deletes the link between a condition and one or more responses.

Syntax

To delete the link between a condition and one or more responses:

rmcondresp [-q] [-h] [-TV] condition[:node_name] [response [response...]]

To delete all of the links to one or more responses:

rmcondresp [-q] -r [-h] [-TV] response1 [response2...][:node_name]

To lock or unlock the condition/response association:

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

Description

The rmcondresp command deletes the link between a condition and one or more responses. A link between a condition and a response is called a condition/response association. The response is no longer run when the condition occurs. Use the -r flag to specify that the command parameters consist only of responses. This deletes all links to conditions for these responses. If only a condition is specified, links to all responses for that condition are deleted.

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 removed by the rmcondresp command. If the condition/response association you specify on the rmcondresp command is locked, it will not be removed; 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.

Flags

-q: Does not return an error when either condition or response does not exist.
-r: Indicates that all command parameters are responses. There are no conditions specified. This command removes condition/response associations from all conditions that are linked to 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.
-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 unless the -r flag is used.
response: Specifies the name of a response or more than one response. The links from the specified responses to the specified condition are removed.
node_name: Specifies the node where the condition is defined. If the -r flag is used, it is the node where the response is defined. node_name is a node within the scope determined by the CT_MANAGEMENT_SCOPE environment variable.

Security

The user needs write permission for the IBM.Association resource class to run rmcondresp. Permissions are specified in the access control list (ACL) file on the contacted system.

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.

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 delete the link between the condition "FileSystem space used" and the response "Broadcast event on-shift", run this command:

rmcondresp "FileSystem space used" "Broadcast event on-shift"

To delete the links between the condition "FileSystem space used" and all of its responses, run this command:
```
rmcondresp "FileSystem space used"
```

To delete the links between the condition "FileSystem space used" and the responses "Broadcast event on-shift" and "E-mail root anytime", run this command:

rmcondresp "FileSystem space used" "Broadcast event on-shift" "E-mail root anytime"

To delete the links between the response "Broadcast event on-shift" and all of the conditions that use it, run this command:
```
rmcondresp -r "Broadcast event on-shift"
```

These examples apply to management domains:

To delete the link between the condition "FileSystem space used" on the management server and the response "Broadcast event on-shift", run this command on the management server:
```
rmcondresp "FileSystem space used" "Broadcast event on-shift"                              													
```
To delete the links between the condition "FileSystem space used" on the managed node nodeB and the responses "Broadcast event on-shift" and "E-mail root anytime", run this command on the management server:
```
rmcondresp  "FileSystem space used":nodeB \
"Broadcast event on-shift" "E-mail root anytime"                              												
	
```

These examples apply to peer domains:

To delete the links between the condition "FileSystem space used" on nodeA in the domain and the responses "Broadcast event on-shift" and "E-mail root anytime", run this command on any node in the domain:
```
rmcondresp "FileSystem space used":nodeA \
"Broadcast event on-shift" "E-mail root anytime"                              												
	
```
To delete the links between all conditions on nodeA in the domain and the response "Broadcast event on-shift", run this command on any node in the domain:
```
rmcondresp -r "Broadcast event on-shift":nodeA        												
	
```

Location

/usr/sbin/rsct/bin/rmcondresp