Arthur Foster

Hillman House,  4, Madeira Road,

Parkstone,  Poole,  Dorset   BH14 9ET

UK

Description of GDMO
Delete Operation

e-mail:

arthur@arthurfoster.com

tel: 

+44 (01202) 469468

fax:

+44 (01202) 469861

  

Home Site Map Search

Home Up Action Operation Create Operation Delete Operation Get Operation Event Report Operation Set Operation Cancel Get Operation Complex Operation

 

Delete Operation Syntax
Delete Argument
Delete Result
Managed Object Template
Name Binding Template

 

Instances of managed objects can be deleted from the agent system by the manager system using the DELETE operation.

The mode of the DELETE operation is always confirmed.

The NAME BINDING template specifies whether a delete operation is supported when that name binding relationship is employed. The naming relationships defines if a delete operation is possible for a pariticular managed object instance and if the managed object instance can be deleted the rules that govern the way in which the managed object instance will be deleted.

 

 

A DELETE operation is invoked by the system acting in the manager role. A message is sent using a CMIP INVOKE request from the manager system to the system acting as an agent. The CMIP INVOKE request includes the information defined in the DeleteArgument syntax of the DELETE definition. The agent will attempt to perform the operation that was requested on the selected managed objects indicated by the CMIP INVOKE.

If the operation is successful, the agent system will return a CMIP RESULT response to the manager to indicate that the operation was successful. The CMIP RESULT includes information defined in the DeleteResult syntax of the DELETE definition.

If the operation fails, a CMIP ERROR is returned. If an error occurs because the APDU could not be decoded, either due to stack failure or an unrecognised syntax, then a CMIP REJECT is returned to the manager.

 

see ITU-T Recommendation X.711
 
Author: Arthur Foster
28 May 2002

Arthur Foster is a

founder member of

 
 

Hosted by