Reconfiguration Coordination Manager (RCM) Script Overview
The Reconfiguration Coordination Manager (RCM) is the framework that manages the dynamic removal of system components. By using RCM, you can register and release system resources in an orderly manner.
You can use the new RCM script feature to write your own scripts to shut down your applications, or to cleanly release the devices from your applications during dynamic reconfiguration. The RCM framework launches a script automatically in response to a reconfiguration request, if the request impacts the resources that are registered by the script.
You can also release resources from applications manually before you dynamically remove the resource. Or, you can use the cfgadm command with the -f option to force a reconfiguration operation. However, this option might leave your applications in an unknown state. Also, the manual release of resources from applications commonly causes errors.
The RCM script feature simplifies and better controls the dynamic reconfiguration process. By creating an RCM script, you can do the following:
What Is an RCM Script?
What Can an RCM Script Do?
For example, an RCM script for a tape backup application can inform the tape backup application to close the tape drive or shut down the tape backup application.
How Does the RCM Script Process Work?
You can invoke an RCM script as follows:
$ script-name command [args ...]
An RCM script performs the following basic steps:
The RCM daemon runs one instance of a script at a time. For example, if a script is running, the RCM daemon does not run the same script until the first script exits.
RCM Script Commands
You might include some or all of the following RCM commands:
For a complete description of these RCM commands, see rcmscript(4).
RCM Script Processing Environment
When you dynamically remove a device, the RCM daemon runs the following: