White Papers
Dellâ„¢ Lifecycle Controller 2 Web Services Interface Guide for Linux  Version: 2.1.0 
74 
 <n1:SystemID>1231</n1:SystemID> 
 <n1:SystemRevision>0</n1:SystemRevision> 
 <n1:TempRollupStatus>1</n1:TempRollupStatus> 
 <n1:UUID>4c4c4544-0036-3510-8034-b7c04f333231</n1:UUID> 
 <n1:VoltRollupStatus>1</n1:VoltRollupStatus> 
 <n1:smbiosGUID>44454c4c-3600-1035-8034-b7c04f333231 
 </n1:smbiosGUID> 
 </n1:DCIM_SystemView> 
10  Job Control Management 
10.1  Description of Job Management 
The Dell Common Information Model (CIM) class extensions for supporting update and attribute 
configuration job control are defined in the Dell Job Control Profile
2
 and related MOF files
3
. The 
diagrams representing the classes that are implemented by the Lifecycle Controller 1.5 firmware can 
be found in Dell Job Control Profile as well. 
Profile and Associated MOFs:  
http://www.delltechcenter.com/page/DCIM.Library.Profile 
10.2  Remote Job Control Examples 
10.2.1  Setup Job Queue  
The SetupJobQueue() method takes in an array of jobids and schedules them to run immediately or at 
a later time. The jobids are acquired via enumerating DCIM_LifecycleJob as described in Section 
10.2.3.  When there is a Reboot Job, in a job array that contains multiple jobs, the system will reboot 
the UEFI (Unified Extensible Firmware Interface) at the scheduled time. 
Invoke SetupJobQueue() with the following parameters and syntax: 
JobArray: The jobids are listed in the JobArray element. Multiple jobs are listed in the order of 
job execution sequence. If a system is to reboot at the scheduled start time, a reboot job will 
need to be added to the list. This reboot job has a prefix of RID_ for its jobid. 
Note, scheduling a job that is already scheduled will result in an error message. 
If there is no reboot job in the job array, the system will schedule the jobs for execution at the 
specified start time.  The jobs will not be executed until the system is rebooted by something other 
than Lifecycle Controller. At the specified UntilTime, any jobs that have not been executed are failed 
with an error indicating that the job was not executed in the specified maintenance window. For some 
component updates such as Diagnostics, USC, and iDRAC firmware, a system reboot is not needed. 










