bottrap
< Prev Back to Table of Contents Next >

Querying Database Properties

The majority of database properties are geared toward gathering information about the names and types of records defined in modules loaded into the database, and various subsets thereof. These properties provide heirarchical lists-of-lists with depth and elements determined by the specified property. Other properties are available for configuring the database, such as where to send messages generated by the validate command.

Syntax:

% dbcmd get property ?property ...?

Returns:

The value of the specified parameter (see below).

Properties:

Option Description
-capabilities Like -modules, but each module name is coupled with a list of all AGENT-CAPABILITIES statements defined within the module. @File1 { MODULE1 { cap1 cap2 cap3 ... } ... } ...
-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. @File1 { MODULE1 { cap1 { 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. @File1 { 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. @File1 { MODULE1 { comp1 comp2 comp3 ... } ... } ...
-filename Returns the path of the currently configured file name for the database (typically a project file).
-files Returns a list of file record handles (such as @File1), listing each of the files loaded into the database. @File1 @File2 @File3 ...
-fullname Equivalent 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. @File1 { MODULE1 { group1 group2 group3 ... } ... } ...
-logchannel Returns the name of the currently configured log channel (e.g. stdout, stderr, etc.) where compiler error/warning and log command messages are sent to.
-name Returns the name of the database (which is the same as dbcmd).
-members Like -modules, but each module name is coupled with a list of all records that are immediate children of the module. @File1 { MODULE1 { Type1 Type2 rec1 rec2 rec3 ... } ... } ...
-moduleids Like -modules, but each module name is coupled with a list of all MODULE-IDENTITY statements defined within the module. @File1 { MODULE1 {} MODULE2 modid2 } @File2 { MODULE3 modid3 } ...
-modules Like -files, but each file handle is coupled with a list of the names of modules defined within the given file. @File1 { MODULE1 MODULE2 } @File2 MODULE3 ...
-ngroups Like -modules, but each module name is coupled with a list of all NOTIFICATION-GROUP records defined within the module. @File1 { MODULE1 { group1 group2 group3 ... } ... } ...
-notifications Like -modules, but each module name is coupled with a list of all NOTIFICATION-TYPE and TRAP-TYPE records defined within the module. @File1 { MODULE1 { trap1 trap2 trap3 ... } ... } ...
-objects Like -modules, but each module name is coupled with a list of all OBJECT-TYPEs defined within the module. @File1 { MODULE1 { obj1 obj2 obj3 ... } ... } ...
-ogroups Like -modules, but each module name is coupled with a list of all OBJECT-GROUP records defined within the module. @File1 { MODULE1 { group1 group2 group3 ... } ... } ...
-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. @File1 { MODULE1 { rec1 rec2 rec3 ... } ... } ...
-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. @File1 { MODULE1 { Type1 Type2 Type3 ... } ... } ...
-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. Normally this will be an empty list, since only OID Value Assignments are permitted in MIB and PIB modules. @File1 { MODULE1 { val1 val2 val3 ... } ... } ...
-variations Like -cmodules, but each conformance module name is coupled with a list of all variations (OBJECT/VARIATION) defined within the conformance statement. @File1 { MODULE1 { cap1 { MODULE1 { var1 var2 ... } ... } ... } ... } ...
< Prev Back to Table of Contents Next >