rmresponse Command

Purpose

Removes a response.

Syntax

rmresponse [-f] [-q] [-h] [-TV] response[:node_name]

Description

The rmresponse command removes the response specified by the response parameter. The response must already exist in order to be removed. When the response must be removed even if it is linked with conditions, specify the -f flag. This forces the response and the links with the conditions to be removed. If the -f flag is not specified and links with conditions exist, the response is not removed. This command does not remove conditions.

If a particular response is needed for system software to work properly, it may be locked. A locked response cannot be modified or removed until it is unlocked. If the response you specify on the rmresponse command is locked, it will not be removed; instead an error will be generated informing you that the response is locked. To unlock a response, you can use the -U flag of the chresponse command. However, since a response is typically locked because it is essential for system software to work properly, you should exercise caution before unlocking it.

Flags

-f: Forces the response to be removed even if it is linked with conditions. The links with the conditions are removed as well as the response, but the conditions are not removed.
-q: Does not return an error when response does not exist.
-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

response: Specifies the name of a defined response to be removed.
node_name: Specifies the node in a cluster where the response 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 write permission for the IBM.EventResponse resource class to run rmresponse. 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 remove the response definition named "Broadcast event on-shift", run this command:
```
 rmresponse  "Broadcast event on-shift"
```
To remove the response definition named "Broadcast event on-shift" even if the response is linked with conditions, run this command:
```
rmresponse -f "Broadcast event on-shift"
```

This example applies to management domains:

In this example, the current node is the management server. To remove the response definition named "Broadcast event on-shift" on managed node nodeB, run this command:
```
 rmresponse  "Broadcast event on-shift":nodeB
```

This example applies to peer domains:

To remove the response definition named "Broadcast event on-shift" defined on node nodeA, run this command from any node in the domain:
```
 rmresponse  "Broadcast event on-shift":nodeA
```

Location

/opt/rsct/bin/rmresponse