mkcondresp Command

Purpose

Creates a link between a condition and one or more responses.

Syntax

mkcondresp [-h] [-TV] condition[:node_name] response1 [response2...]

Description

The mkcondresp command creates a link between a condition and one or more responses. A link between a condition and a response is called a condition/response association. This command creates one or more condition/response associations; it does not start monitoring. In a cluster environment, the condition and the response must be defined on the same node. You can start monitoring for this condition and its linked responses later using the startcondresp command.

To lock a condition/response association, use the -L flag of the rmcondresp, startcondresp, or stopcondresp command.

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 to be 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.
response1 [response2...]: Specifies one or more response names. All responses are linked to condition.

Security

The user needs write permission for the IBM.Association resource class to run mkcondresp. 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 link the condition "FileSystem space used" to the response "Broadcast event on-shift", run this command:

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

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

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

These examples apply to management domains:

To link the condition "FileSystem space used" on the management server to the response "Broadcast event on-shift" (also on the management server), run this command on the management server:
```
mkcondresp "FileSystem space used" "Broadcast event on-shift"                              													
```
To link the condition "FileSystem space used" on the management server to the response "Broadcastevent on-shift", run this command on one of the nodes in the domain:
```
mkcondresp "FileSystem space used":nodeA "Broadcast event on-shift"                                												
```

This example applies to peer domains:

To link the condition "FileSystem space used" on node nodeA to the response "Broadcastevent on-shift" (also on nodeA), run this command on one of the nodes in the domain:
```
mkcondresp "FileSystem space used":nodeA "Broadcast event on-shift"                                												
```

Location

/usr/sbin/rsct/bin/mkcondresp