Connected: An Internet Encyclopedia
RFC 1904 - 6.5.2.4. Mapping of the CREATION-REQUIRES clause

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1904
Up: 6. Mapping of the AGENT-CAPABILITIES macro
Up: 6.5. Mapping of the SUPPORTS clause
Up: 6.5.2. Mapping of the VARIATION clause
Prev: 6.5.2.3. Mapping of the ACCESS clause
Next: 6.5.2.5. Mapping of the DEFVAL clause

### 6.5.2.4. Mapping of the CREATION-REQUIRES clause

The CREATION-REQUIRES clause, which need not be present, is used to name the columnar objects of a conceptual row to which values must be explicitly assigned, by a management protocol set operation, before the agent will allow the instance of the status column of that row to be set to `active'. (Consult the definition of RowStatus [5].)

If the conceptual row does not have a status column (i.e., the objects corresponding to the conceptual table were defined using the mechanisms in [6,7]), then the CREATION-REQUIRES clause, which need not be present, is used to name the columnar objects of a conceptual row to which values must be explicitly assigned, by a management protocol set operation, before the agent will create new instances of objects in that row.

This clause must not present unless the object named in the correspondent VARIATION clause is a conceptual row, i.e., has a syntax which resolves to a SEQUENCE containing columnar objects. The objects named in the value of this clause usually will refer to columnar objects in that row. However, objects unrelated to the conceptual row may also be specified.

All objects which are named in the CREATION-REQUIRES clause for a conceptual row, and which are columnar objects of that row, must have an access level of "read-create".

Next: 6.5.2.5. Mapping of the DEFVAL clause

Connected: An Internet Encyclopedia
RFC 1904 - 6.5.2.4. Mapping of the CREATION-REQUIRES clause