White Papers

Dell™ Lifecycle Controller 2 Web Services Interface Guide for Linux Version: 2.1.0
85
<wsman:ResourceURI>http://schemas.dell.com/wbem/wscim/1/cim-
schema/2/DCIM_OSDConcreteJob</wsman:ResourceURI>
<wsman:SelectorSet>
<wsman:Selector Name="InstanceID">DCIM_OSDConcreteJob:1</wsman:Selector>
<wsman:Selector Name="__cimnamespace">root/dcim</wsman:Selector>
</wsman:SelectorSet>
</wsa:ReferenceParameters>
</n1:Job>
<n1:ReturnValue>4096</n1:ReturnValue>
</n1:UnpackAndShare_OUTPUT>
A missing command line character, such as a “-“, could result in the following error:
Connection failed. response code = 0
Couldn't connect to server
11.3.5 Check Job Status
The following methodology is used to determine the status of the jobs generated by the invocation of
the UnpackAndAttach() and UnpackAndShare() methods. The methodology involves enumerating the
DCIM_OSDConcreteJob instances, and checking the JobStatus property value.
When the jobs are complete, the JobStatus property value will be “Successful” if the job completed
successfully or “Failed” if an error occurred while executing the request. If the job failed, the Message
property on the returned DCIM_OSDConcreteJob instance will contain more detailed error information
on the cause of the failure.
For the Lifecycle Controller 1.5 version of the OS Deployment Profile there is only one instance of a job
generated by various method invocations, and it will persist until the next method that generates a job
is invoked. The job must complete before another method that generates a job can be called
successfully. This is unchanged from the Lifecycle Controller 1.2 for OS Deployment.
Invoke enumerate DCIM_OSDConcreteJob instance with the following syntax:
EXAMPLE:
wsman enumerate http://schemas.dmtf.org/wbem/wscim/1/cim-
schema/2/root/dcim/DCIM_OSDConcreteJob
-h $IPADDRESS -V -v -c dummy.cert -P 443
-u $USERNAME -p $PASSWORD
-j utf-8 -y basic
OUTPUT:
The enumeration will return the instances of OSDConcreteJob as shown:
<n1:DCIM_OSDConcreteJob>
<n1:Caption xsi:nil="true"/>
<n1:CommunicationStatus xsi:nil="true"/>