Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dcmStudyFilterRelation",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"and",
"(",
"1",
")",
",",
"or",
"(",
"2",
")",
",",
"endOfDef",
"(",
"3",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Indicates how several rows (filters) with the same value of the dcmSFMStudyNum object are related to each other. It is up to the actual implementation (database population) to ensure that the association of rows is logical. The first two entries for any defined filter are processed first, the result of that is then processed with the next row, the result of that with the 4th, etc. The currently defined values are: and (1) – combine the criteria of this row (dcmSFMFilterNum) with the next row (next higher value of the dcmSFMFilterNum object) within the same dcmSFMStudyNum. or (2) – select the criteria of either this row (dcmSFMFilterNum) or of the next row (next higher value of the dcmSFMFilterNum object) within the same dcmSFMStudyNum. endOfDef (3) – indicates that the criteria of this row is the last criteria valid for this dcmSFMStudyNum. If only one criteria is used per study (dcmSFMStudyNum), the value of this object shall be set to ‘endOfDef’. In opposite to the common setup of SNMP MIB objects, this object was purposely setup to NOT include a value of (other).\"",
"::=",
"{",
"dcmStudyFilterMapEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"and",
1
],
[
"or",
2
],
[
"endOfDef",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Indicates how several rows (filters) with the same value of the dcmSFMStudyNum object are related to each other. It is up to the actual implementation (database population) to ensure that the association of rows is logical. The first two entries for any defined filter are processed first, the result of that is then processed with the next row, the result of that with the 4th, etc. The currently defined values are: and (1) – combine the criteria of this row (dcmSFMFilterNum) with the next row (next higher value of the dcmSFMFilterNum object) within the same dcmSFMStudyNum. or (2) – select the criteria of either this row (dcmSFMFilterNum) or of the next row (next higher value of the dcmSFMFilterNum object) within the same dcmSFMStudyNum. endOfDef (3) – indicates that the criteria of this row is the last criteria valid for this dcmSFMStudyNum. If only one criteria is used per study (dcmSFMStudyNum), the value of this object shall be set to ‘endOfDef’. In opposite to the common setup of SNMP MIB objects, this object was purposely setup to NOT include a value of (other)."
],
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:
Show more related files and packages
- 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: