dcmRelativeAddrOID

Status in source: optional.

Names: dcmRelativeAddrOID

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dcmRelativeAddrOID",
    "OBJECT-TYPE",
    "SYNTAX",
    "OBJECT",
    "IDENTIFIER",
    "ACCESS",
    "read-write",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "“",
    "Indicates",
    "the",
    "OID",
    "address",
    "which",
    "shall",
    "be",
    "referenced",
    "by",
    "any",
    "object",
    "in",
    "the",
    "specified",
    "data",
    "file",
    "if",
    "relative",
    "OID",
    "’",
    "s",
    "have",
    "been",
    "enabled",
    "(",
    "through",
    "the",
    "File",
    "Parameter",
    "Table",
    ")",
    ".",
    "The",
    "last",
    "number",
    "indicated",
    "in",
    "the",
    "OID",
    "value",
    "shall",
    "not",
    "be",
    "repeated",
    "in",
    "the",
    "relative",
    "OID",
    "’",
    "s",
    ".",
    "This",
    "object",
    "has",
    "been",
    "included",
    "to",
    "reduce",
    "overhead",
    "relative",
    "to",
    "OID",
    "’",
    "s",
    "when",
    "specified",
    "in",
    "data",
    "files",
    ".",
    "This",
    "object",
    "shall",
    "not",
    "be",
    "used",
    "to",
    "shorten",
    "OID",
    "’",
    "s",
    "within",
    "SNMP",
    "messages",
    ".",
    "The",
    "device",
    "shall",
    "return",
    "an",
    "‘",
    "out",
    "of",
    "range",
    "’",
    "error",
    "if",
    "the",
    "application",
    "attempts",
    "to",
    "set",
    "this",
    "object",
    "to",
    "an",
    "OID",
    "below",
    "where",
    "this",
    "object",
    "resides",
    ".",
    "This",
    "will",
    "prevent",
    "a",
    "situation",
    "where",
    "this",
    "object",
    "cannot",
    "be",
    "accessed",
    "anymore",
    ".",
    "An",
    "application",
    "can",
    "only",
    "enable",
    "the",
    "usage",
    "of",
    "this",
    "object",
    "within",
    "specified",
    "data",
    "files",
    ".",
    "Once",
    "enabled",
    ",",
    "it",
    "will",
    "be",
    "determined",
    "by",
    "the",
    "device",
    "where",
    "and",
    "how",
    "often",
    "to",
    "use",
    "it",
    "to",
    "optimize",
    "the",
    "storage",
    "requirements",
    "of",
    "OID",
    "’",
    "s",
    ".",
    "This",
    "object",
    "may",
    "be",
    "used",
    "multiple",
    "times",
    "within",
    "the",
    "same",
    "data",
    "file",
    "by",
    "the",
    "device",
    "to",
    "change",
    "the",
    "relative",
    "addressing",
    "of",
    "the",
    "OID",
    "’",
    "s",
    "in",
    "order",
    "to",
    "optimize",
    "storage",
    ".",
    "”",
    "::=",
    "{",
    "dcm",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OBJECT IDENTIFIER",
      null
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "Indicates the OID address which shall be referenced by any object in the specified data file if relative OID’s have been enabled (through the File Parameter Table). The last number indicated in the OID value shall not be repeated in the relative OID’s. This object has been included to reduce overhead relative to OID’s when specified in data files. This object shall not be used to shorten OID’s within SNMP messages. The device shall return an ‘out of range’ error if the application attempts to set this object to an OID below where this object resides. This will prevent a situation where this object cannot be accessed anymore. An application can only enable the usage of this object within specified data files. Once enabled, it will be determined by the device where and how often to use it to optimize the storage requirements of OID’s. This object may be used multiple times within the same data file by the device to change the relative addressing of the OID’s in order to optimize storage."
    ],
    null,
    null,
    null,
    null
  ]
}

• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1206:2005, Object Definitions for Data Collection and Monitoring (DCM) Devices Published November 2005 — original PDF · Official record

  Module: DCM-MIB1

  See published definition above

  Module imports

  {'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}

  Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.

  Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

  Source data warning: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

  Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

  Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

  Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

  · Download NTCIP1206v0123f.pdf — DCM-MIB1 (MIB transcription)

  Related source files and packages:

  • NTCIP 1206:2005, Object Definitions for Data Collection and Monitoring (DCM) Devices Published November 2005 — original PDF
  • NTCIP 8004 v02 (2010) — normative namespace, pages 43–44
  • RFC 1155 — original SMI enterprise namespace

  Show more related files and packages

  • NTCIP8004-NEMA.mib — ITE namespace dependency
  • NTCIP8004-Transportation.mib — ITE namespace dependency
• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1206:2005, Object Definitions for Daqta Collection and Monitoring (DCM) Devices Published November 2005 (superceded by NTCIP 1206 v02) — original PDF · Official record

  Module: DCM-MIB1

  Same published definition

  Module imports

  {'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}

  Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.

  Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

  Source data warning: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

  Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

  Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

  Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

  · Download NTCIP1206v0123f-1.pdf — DCM-MIB1 (MIB transcription)

  Related source files and packages:

  • NTCIP 1206:2005, Object Definitions for Daqta Collection and Monitoring (DCM) Devices Published November 2005 (superceded by NTCIP 1206 v02) — original PDF