MIB Smithy

Querying File Properties

Like databases, the majority of file properties are geared toward gathering information about the names and types of records defined in modules defined in a paritcular file, and various subsets thereof. These properties carry the same names as those of the database, but remove the file handle layer off the heirarchy so that the first layer is that of the modules.

Syntax:

% dbcmd get property ?property ...? @File#

Returns:

• The value of the specified property or properties (see below).

Properties:

-capabilities

Like -modules, but each module name is coupled with a list of all AGENT-CAPABILITIES statements defined within the module.

MODULE1 { cap1 cap2 ... } MODULE2 { cap3 cap4 ... } ...

-cgroups

Like -cmodules, but each conformance module name is coupled with a list of all conformance groups (GROUP) defined within the conformance module of a MODULE-COMPLIANCE.

MODULE1 { comp1 { MODULE1 { group1 group2 ... } ...} ... } ...

-cmodules

Like -capabilities and -compliances, but each conformance name is coupled with a list of all conformance modules (SUPPORTS/MODULE) defined within the conformance.

MODULE1 { comp1 { MODULE1 MODULE2 ... } ... } ...

-compliances

Like -modules, but each module name is coupled with a list of all MODULE-COMPLIANCE statements defined within the module.

MODULE1 { comp1 comp2 ... } MODULE2 { comp3 comp4 ... } ...

-container

Provided only for consistency with other record types. For this record types, this property always returns an empty string.

-filename

Returns the path of the source file associated with the file record.

-fullname

Equilvalent to -name for this record type.

-groups

Like -modules, but each module name is coupled with a list of all OBJECT-GROUP and NOTIFICATION-GROUP records defined within the module.

MODULE1 { group1 group2 ... } MODULE2 { group3 group4 ... } ...

-members

Like -modules, but each module name is coupled with a list of all records that are immediate children of the module.

MODULE1 { rec1 rec2 ... } MODULE2 { rec3 rec4 ... } ...

-modified

Returns the current state of the Modified flag for the file record. This flag is set by any call to new, set or destroy for any record within the file, except by directly clearing the flag during a set.

-moduleids

Like -modules, but each module name is coupled with a list of all MODULE-IDENTITY statements defined within the module.

MODULE1 modid1 MODULE2 {} ...

-modules

Returns a list of the names of modules defined within the given file.

MODULE1 MODULE2 MODULE3 ...

-name

Returns the name of the file handle (e.g. @File1) passed as the first argument to the get subcommand.

-objects

Like -modules, but each module name is coupled with a list of all OBJECT-TYPEs defined within the module.

MODULE1 { obj1 obj2 ... } MODULE2 { obj3 obj4 ... } ...

-ngroups

Like -modules, but each module name is coupled with a list of all NOTIFICATION-GROUP records defined within the module.

MODULE1 { group1 group2 ... } MODULE2 { group3 group4 ... } ...

-notifications

Like -modules, but each module name is coupled with a list of all NOTIFICATION-TYPE and TRAP-TYPE records defined within the module.

MODULE1 { trap1 trap2 ... } MODULE2 { trap3 trap4 ... } ...

-ogroups

Like -modules, but each module name is coupled with a list of all OBJECT-GROUP records defined within the module.

MODULE1 { group1 group2 ... } MODULE2 { group3 group4 ... } ...

-oids

Like -modules, but each module name is coupled with a list of all record definitions that assign or register an object identifier value, including various macro invocations and ASN.1 OID Value Assignments.

MODULE1 { rec1 rec2 ... } MODULE2 { rec3 rec4 ... } ...

-typedefs

Like -modules, but each module name is coupled with a list of all ASN.1 Type Assignments and TEXTUAL-CONVENTIONs defined within the module.

MODULE1 { Type1 Type2 ... } MODULE2 { Type3 Type4 ... } ...

-values

Like -modules, but each module name is coupled with a list of all ASN.1 Value Assignments (other than OIDs) defined within the module.

MODULE1 { val1 val2 ... } MODULE2 { val3 val4 ... } ...

-variations

Like -cmodules, but each conformance module name is coupled with a list of all variations (OBJECT/VARIATION) defined within the conformance statement.

MODULE1 { comp1 { MODULE1 { var1 var2 ... } ...} ... } ...