OID reference

dcmFileStrucTable

1.3.6.1.4.1.1206.4.2.9.7.4

Description

This is a doubly-indexed table. It defines which items shall be stored in the data files. By default, the dcm MIB Version Number object shall always be included as the first object. The device shall also include the required data packets (encoded as Data Structure Tables) for the included studies. The objects specifie…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.9.7 (dcmFileConfig)
Node code
4
Node name
dcmFileStrucTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.9.7.4
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.9.7.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 9 7 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFileStrucTable(4)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/9/7/4
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/9/7/4
  • /ISO/3/6/1/4/1/1206/4/2/9/7/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/dcm/dcmFileConfig/dcmFileStrucTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF DcmFileStrucEntry
Maximum access defined by MIB
not-accessible
Status in MIB
optional

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

dcmFileStrucTable OBJECT-TYPE
 SYNTAX SEQUENCE OF DcmFileStrucEntry
 ACCESS not-accessible
 STATUS optional
 DESCRIPTION
 "This is a doubly-indexed table. It defines which items shall be stored in
the data files. By default, the dcm MIB Version Number object shall always be
included as the first object. The device shall also include the required data
packets (encoded as Data Structure Tables) for the included studies.       The
objects specified in this table shall be stored in the data file in the same
order as specified in this table. There may be other objects included in the
header information section that have not been specified in this table, however
these object can be skipped over by using the length field of the OID and the
length field of the associated Value."
::= {dcmFileConfig 4}

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This is a doubly-indexed table. It defines which items shall be stored in the data files. By default, the dcm MIB Version Number object shall always be included as the first object. The device shall also include the required data packets (encoded as Data Structure Tables) for the included studies. The objects specified in this table shall be stored in the data file in the same order as specified in this table. There may be other objects included in the header information section that have not been specified in this table, however these object can be skipped over by using the length field of the OID and the length field of the associated Value.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 1

dcmFileStrucTable · optionalNTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: optional.

Names: dcmFileStrucTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dcmFileStrucTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "DcmFileStrucEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"This is a doubly-indexed table. It defines which items shall be stored in the data files. By default, the dcm MIB Version Number object shall always be included as the first object. The device shall also include the required data packets (encoded as Data Structure Tables) for the included studies. The objects specified in this table shall be stored in the data file in the same order as specified in this table. There may be other objects included in the header information section that have not been specified in this table, however these object can be skipped over by using the length field of the OID and the length field of the associated Value.\"",
    "::=",
    "{",
    "dcmFileConfig",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "DcmFileStrucEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "This is a doubly-indexed table. It defines which items shall be stored in the data files. By default, the dcm MIB Version Number object shall always be included as the first object. The device shall also include the required data packets (encoded as Data Structure Tables) for the included studies. The objects specified in this table shall be stored in the data file in the same order as specified in this table. There may be other objects included in the header information section that have not been specified in this table, however these object can be skipped over by using the length field of the OID and the length field of the associated Value."
    ],
    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)
  • 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)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.9.7.4.1 dcmFileStrucEntry44

Siblings (10)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.9.7.1 dcmNumFileStructures00
1.3.6.1.4.1.1206.4.2.9.7.2 dcmFSTMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.7.3 dcmFSTCurNumRows00
1.3.6.1.4.1.1206.4.2.9.7.5 dcmFPTMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.7.6 dcmFPTCurNumRows00
1.3.6.1.4.1.1206.4.2.9.7.7 dcmFPTable19
1.3.6.1.4.1.1206.4.2.9.7.8 dcmDFIntegrity00
1.3.6.1.4.1.1206.4.2.9.7.9 dcmFDSTMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.7.10 dcmFDSTCurNumRows00
1.3.6.1.4.1.1206.4.2.9.7.11 dcmFileDirStrucTable19