OpState attribute
System Automation for Multiplatforms uses the OpState dynamic attribute to specify the aggregate operational state of the collection (of managed resources). It is determined from the individual operational states of the member resources of the resource group.
These are the possible values that the OpState attribute can have:
| Status | Value | Description |
|---|---|---|
| Unknown | 0 | |
| Online | 1 | Specifies that all of the Mandatory member resources are Online. The Non-Mandatory member resources in terminal states are ignored. |
| Offline | 2 | Specifies that all of the member resources are Offline. |
| Failed Offline | 3 | Specifies that one or more member resources
contained in the resource group, are FailedOffline. In this case,
all resources contained in the resource group will be set to Offline. A resource group can reach the status Failed Offline as a result of a binder run if a resource group members could not be placed. See also Assigning node location. If this is the case the automation details show a BindingState of Sacrificed. See also AutomationDetails attribute. |
| Stuck Online | 4 | Specifies that a member resource is stuck online. |
| Pending Online | 5 | Specifies that a Start command is executed (the NominalState attribute of the resource group is set to online). The resource group must begin processing an online action. |
| Pending Offline | 6 | Specifies that an offline action has been initiated. |
| Ineligible | 8 | The resource group is offline and temporarily unable to process automation orders. This is typically caused when node-fencing is in progress or has failed. See RSCT or DB2 pureScale documentation for more details regarding node-fencing. |