ApiMoveGroupToNodeEx (Opnum 133)

(Protocol Version 3) The ApiMoveGroupToNodeEx method SHOULD<94> instructs the server to move ownership of a group to the specified node in the cluster.

The server MUST handle this method in the same manner as ApiMoveGroupToNode (section except as follows:

  • The server handles the dwMoveFlags and lpInBuffer parameters as specified for ApiMoveGroupEx (section, with any reference to the destination node now referring to the node designated by the hNode parameter.

The server accepts an ApiMoveGroupToNodeEx request only if it is in the read/write state, as specified in section 3.1.1.

The server MUST require that the access level associated with the hGroup parameter is "All" (section 3.1.4).

 error_status_t ApiMoveGroupToNodeEx(
   [in] HGROUP_RPC hGroup,
   [in] HNODE_RPC hNode,
   [in] DWORD dwMoveFlags,
   [in, size_is(cbInBufferSize)] BYTE* lpInBuffer,
   [in] DWORD cbInBufferSize,
   [out] error_status_t *rpc_status

hGroup: An HGROUP_RPC context handle that was obtained in a previous call to ApiOpenGroup (section, ApiOpenGroupEx (section, or ApiCreateGroup (section

hNode: An HNODE_RPC context handle that was obtained in a previous call to ApiOpenNode (section or ApiOpenNodeEx (section, indicating the node that will take ownership of the group specified in the hGroup parameter.

dwMoveFlags: The available values for this parameter are identical to those specified for the ApiMoveGroupEx (section method.

lpInBuffer: A pointer to a buffer that the server will provide to implementation-specific objects that control the resource operations for each resource in the group. The client SHOULD set this parameter to a PROPERTY_LIST (section For each value in this list, the client sets the property name to the name of the resource type of one of the resources in the group. The client can provide a buffer that does not have a property value corresponding to each resource type in the group, and the client can provide a buffer that has multiple property values for the same resource type. Except for the following property values, the server MUST treat all property values provided by the client identically.

cbInBufferSize: The size in bytes of the buffer pointed to by the lpInBuffer parameter.

rpc_status: A 32-bit integer used to indicate success or failure. The RPC runtime MUST indicate, by writing to this parameter, whether it succeeded in executing this method on the server. The encoding of the value passed in this parameter MUST conform to encoding for comm_status and fault_status, as specified in Appendix E of [C706].

Return Values: This method MUST return the same error codes as specified for ApiMoveGroupToNode (section and ApiMoveGroupEx (section