DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Designing SCOadmin object service agents

Defining execution procedures

An OSA defines ``execution procedures'' that can be performed on the objects or attributes of a class. The presentation level of a SCOadmin manager calls these procedures with arguments specifying affected object instances and attributes, data values, and other relevant informations. The procedures should return appropriate data and error messages to the calling routine.

There are only 10 possible operation types:

for attributes only for objects only
get delete
replace action
replaceWithDefault create
add list
remove  
filter  
The possible operations are divided into two categories; those that work on the object's attributes, and those that work on the object as a whole. For each object and attribute, the class definition tables specify which procedures may act on the object or attribute.

Execution procedures can be split into four types of functions:

The first three of these are the functions that are named in a ODT execution procedure field of a class.
Next topic: Application procedures
Previous topic: Binding class definitions to the Object API

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003