Setting the environment variables
- CT_CONTACT
- When the CT_CONTACT environment variable is set to a host name or IP address, the command contacts the Resource Monitoring and Control (RMC) daemon on the specified host. If the environment variable is not set, the command contacts the RMC daemon on the local system where the command is being run. The resource class or resources that are displayed or modified by the command are located on the system to which the connection is established.
- CT_LOCAL_SCOPE
- The CT_LOCAL_SCOPE environment variable sets the RMC subsystem
scope to the standalone environment. By default, the RMC subsystem
monitors and controls the resources and resource classes on all nodes
in the cluster. A cluster can consist of one or more nodes. When a
cluster consists of one node, it is said to operate in a standalone
environment. The scope of a command in the standalone environment
is the local node. The scope of a command in a cluster environment
of more than one node is the entire cluster. For a cluster of more
than one node, to return or change resources or resource classes only
on the node where RMC is running, set the CT_LOCAL_SCOPE environment
variable to 1, as follows:
For example, assume that a cluster consists of nodes A, B, and C and the following command is run:export CT_LOCAL_SCOPE=1
Resources for the file systems associated with nodes A, B, and C are returned.lsrsrc IBM.FileSystemIf CT_LOCAL_SCOPE is set to 1 and the lsrsrc command is run on Node A, then only the file system resources associated with node A are returned.
- CT_MANAGEMENT_SCOPE
- The CT_MANAGEMENT_SCOPE environment variable must be set on all nodes for all users of IBM Tivoli System Automation. Enter CT_MANAGEMENT_SCOPE=2 (peer domain scope). The variable may be permanently set in the profile.