3.1.5.1.3 Atomic
The Atomic command is used by the client to start initialization of a session. If execution fails for any of the commands contained within the atomic unit, all previously executed commands within the unit MUST be rolled back to their previous state. All commands within the atomic unit MUST be valid for any of the commands within the unit to be executed.
The following XML snippet shows example usage of the Atomic command. In the example, the originator issues two Replace (section 3.1.5.1.7) commands inside of the Atomic command. The syntax for the Atomic element type is specified in section 2.2.7.3.
-
<SyncBody> <Atomic> <CmdID>10</CmdID> <Replace> <CmdID>8</CmdID> <Item> <Target> <LocURI>./cimv2/MDM_ConfigSetting/MDM_ConfigSetting. SettingName=%22UnEnrollOnCertExpiry%22/SettingValue</LocURI> </Target> <Data>true</Data> </Item> </Replace> <Replace> <CmdID>9</CmdID> <Item> <Target> <LocURI>./cimv2/MDM_Restrictions/MDM_Restrictions. Key=%221%22/DataRoamingEnabled</LocURI> </Target> <Data>true</Data> </Item> </Replace> </Atomic> ... </SyncBody>
No classes are specified for the Atomic command. Valid classes for the commands specified within an atomic unit are specified in the definition for each command in this section. For example, the valid classes for the Delete command are as specified in the definition for the Delete command in section 3.1.5.1.4.