Technical White Paper

16.15 Deleting the Pending Values for RAID-
DeletePendingConfiguration()
The DeletePendingConfiguration() method cancels the pending configuration changes made before
the configuration job is created with CreateTargetedConfigJob(). This method only operates on the
pending changes prior to CreateTargetedConfigJob() being called. After the configuration job is
created, the pending changes can only be canceled by calling DeleteJobQueue() in the Job Control
profile.
Invoke DeletePendingConfiguration() with the following parameters and syntax:
TARGET: This parameter is the FQDD of the DCIM_ControllerView (Section 16.7)
EXAMPLE:
wsman invoke -a DeletePendingConfiguration
http://schemas.dmtf.org/wbem/wscim/1/cimschema/
2/root/dcim/DCIM_RAIDService
?SystemCreationClassName=DCIM_ComputerSystem,
CreationClassName=DCIM_RAIDService,SystemName=DCIM:ComputerSystem,
Name=DCIM:RAIDService -h $IPADDRESS -V -v -c dummy.cert -P 443
-u $USERNAME -p $PASSWORD -J DeletePendingConfiguration_RAID.xml
-j utf-8 -y basic
The input file DeletePendingConfiguration.xml is shown below:
<p:DeletePendingConfiguration_INPUT
xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-
schema/2/root/dcim/DCIM_RAIDService">
<p:Target>RAID.Integrated.1-1</p:Target>
</p:DeletePendingConfiguration_INPUT>
OUTPUT:
<n1:DeletePendingConfiguration_OUTPUT>
<n1:ReturnValue>0</n1:ReturnValue>
</n1:DeletePendingConfiguration_OUTPUT>
16.16 Managing Hot-Spare
16.16.1 Determining Potential Disks-GetDHSDisks()
The GetDHSDisks() method is used to determine possible choices of drives to be a dedicated
HotSpare for the identified virtual disk.
Invoke GetDHSDisks() with the following parameters and syntax:
TARGET: This parameter is the FQDD of the target virtual disk. Its value will depend on the
number of virtual disks, obtainable in Section 16.10.
EXAMPLE:
wsman invoke -a GetDHSDisks http://schemas.dmtf.org/wbem/wscim/1/cimschema/
2/root/dcim/DCIM_RAIDService
?SystemCreationClassName=DCIM_ComputerSystem,