| Where allowed to run: All environments (*ALL) Threadsafe: Yes |
Parameters Examples Error messages |
The Add Cluster Resource Group Device Entry (ADDCRGDEVE) command is used to add one or more configuration objects representing resilient hardware devices to a device cluster resource group. All devices being added must be able to be switched from one cluster node to another. When the cluster resource group is switched over or failed over to the first backup system, all devices in the device list are moved to the backup system.
If the cluster resource group contains any members of an auxiliary storage pool group, it must contain all members before the cluster resource group can be started. All members do not have to be specified at once. Additional members can be added later. If the auxiliary storage pool group has previously been created and clustering can determine which members are in the group, a warning message is sent if some members of the group were not added.
If an exit program is specified for the cluster resource group, the cluster resource group exit program is called with an action code of Add Device Entry on all active nodes in the recovery domain. The cluster resource group status is set to Add Device Entry Pending. If the exit program completes successfully, the cluster resource group status is reset to its value at the time the command was called. If the exit program fails and the cluster resource group cannot be restored to its original condition, the cluster resource group status is set to Indoubt.
Restrictions:
| Top |
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| CLUSTER | Cluster | Name | Required, Positional 1 |
| CRG | Cluster resource group | Name | Required, Positional 2 |
| CFGOBJ | Configuration object list | Values (up to 256 repetitions): Element list | Required, Positional 3 |
| Element 1: Configuration object | Name | ||
| Element 2: Configuration object type | *DEVD, *CTLD, *LIND, *NWSD | ||
| Element 3: Configuration object online | *OFFLINE, *ONLINE, *PRIMARY | ||
| Element 4: Server takeover IP address | Character value, *NONE |
| Top |
Specifies the cluster to which the cluster resource group belongs.
This is a required parameter.
| Top |
Specifies the cluster resource group which is to contain the device entries.
This is a required parameter.
| Top |
Specifies detailed information about the resilient devices to be added to the cluster resource group.
This is a required parameter.
Element 1: Configuration object
The name of the configuration object which can be switched between the nodes in the recovery domain. The configuration object can be specified in only one cluster resource group.
Element 2: Configuration object type
Specifies the type of configuration object.
Element 3: Configuration object online
Specifies what configuration action to take when the cluster resource group is switched over or failed over to a backup node. The configuration object can be varied on and start the server takeover IP address or leave the configuration object varied off and the server takeover IP address inactive and does not start or end the server takeover IP address when device ownership is moved to another node. This attribute does not vary the device on or off when the cluster resource group is started or ended. Switchover and failover completion may be delayed if the online attribute has a value of *YES for devices that may take a long time to vary on.
Element 4: Server takeover IP address
Specifies a takeover IP address for servers associated with the relational database name in the device description for an auxiliary storage pool. This element is optional and can only be specified for a primary auxiliary storage pool. If specified, the takeover IP address may be an IPv4 address (for any cluster version) or IPv6 address (if current cluster version is 7 or greater). The specified address must exist on all nodes in the recovery domain if the cluster resource group is active.
An IPv4 internet address is specified in the form nnn.nnn.nnn.nnn, where nnn is a decimal number ranging from 0 through 255. An IPv4 internet address is not valid if it has a value of all binary ones or all binary zeros for the network identifier (ID) portion or the host portion of the address.
An IPv6 internet address must be a unicast address and must not contain an imbedded IPv4 address (compatibility or mapped). An IPv6 internet address is specified in the form x:x:x:x:x:x:x:x, where x is a hexadecimal number ranging from 0 through X'FFFF'. The "::" may be used once in the IPv6 address to indicate one or more groups of 16 bits of zeros. The "::" may be used to compress leading, imbedded, or trailing zeros in the address. IP addresses created by IPv6 stateless address auto-configuration are not valid to be used as server takeover IP addresses.
If the IP address is entered from the command line, the address must be enclosed in apostrophes.
The specified address must exist on all nodes in the recovery domain if the cluster resource group is active. If not specified, or for configuration objects other than a primary auxiliary storage pool, the element must be set to *NONE.
| Top |
ADDCRGDEVE CLUSTER(MYCLUSTER) CRG(MYCRG)
CFGOBJ((IASP01 *DEVD *ONLINE
'2001:0DB8:333:4444:5555:6666:7777:F888'))
This command adds an ASP device description object, IASP01, to the device list of the resilient device cluster resource group MYCRG in the cluster MYCLUSTER. If MYCRG is switched over or failed over to a backup node, the device will be varied on to the new primary. The server takeover IP address is 2001:0DB8:333:4444:5555:6666:7777:F888.
| Top |
*ESCAPE Messages
| Top |