OID reference

recordingNumber

1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2

Description

<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their reco…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.1.1.7.9.9.1 (recRecordingEntry)
Node code
2
Node name
recordingNumber
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2
URN notation
urn:oid:1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recRecordingTable(9) recRecordingEntry(1) recordingNumber(2)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/1/1/7/9/9/1/2
  • /ISO/Identified-Organization/6/1/4/1/1206/4/1/1/7/9/9/1/2
  • /ISO/3/6/1/4/1/1206/4/1/1/7/9/9/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/Protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/Protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/Protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/Protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/Protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/Protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/Protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/Protocols/layers/application/recMech/recRecordingTable/recRecordingEntry/recordingNumber
  • Additional combinations skipped.

SNMP properties

Value type
Integer32, INTEGER
Maximum access defined by MIB
read-only
Status in MIB
deprecated, mandatory

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — NTCIP published standard MIB annexes (reviewed modules), ITE public NTCIP working repository MIBs

Value type
Integer32
Maximum access defined by MIB
read-only
Status in MIB
deprecated
Allowed ranges
1–254

Variant 2 — NTCIP published standard MIB annexes (reviewed modules)

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
mandatory
Allowed ranges
1–254

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In NTCIP1201-RecMech, the row index consists of these components in order:

  1. recordingClass (Integer32): one numeric subidentifier for the non-negative value.
  2. recordingNumber (Integer32): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2.<recordingClass>.<recordingNumber>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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

Available source records contain 3 distinct definitions; some records may not include a definition.

Show 3 published definitions

recordingNumber · deprecated

recordingNumber OBJECT-TYPE
SYNTAX       Integer32 (1..254)
MAX-ACCESS read-only
STATUS       deprecated
DESCRIPTION
   "<Definition>The recording number within this class for this recording.
   Recording numbers shall be assigned starting at 1 and shall increase to the
   value specified by the associated recClassLimit for the class associated
   with the rows. Recordings shall maintain a chronological ordering in the



                                                                                         

                 
        

  table, based on their recordingTriggerTime value, with the oldest recording
  of a class occupying the row with recordingNumber = 1, and subsequent
  recordings filling subsequent rows. This ordering shall be maintained for
  those rows still remaining when recordings are cleared.
  <Supplanted by> ISO26048-1-Recording.fdRecordingRecordingIndex
  <Informative> The syntax of the replacement object is ITSPositive16. The
  replacement table does not attempt to keep the oldest entry in slot one;
  clearance of rows is based on overall size rather than number of entries,
  which makes this type of row management more difficult - but since row
  numbers do not change, managers can keep track of the last row number
  retrieved and decrease the probability of missing a recording. A manager
  can also use a get-next operation to discover where the rows start in the
  table.
  <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2"
::= { recRecordingEntry 2 }

recordingNumber · mandatory

recordingNumber       OBJECT-TYPE
   SYNTAX INTEGER (1..254)
   ACCESS read-only
   STATUS mandatory
   DESCRIPTION
        "<Definition>The recording number within this class for this
           recording. Recording numbers shall be assigned starting at 1 and
           shall increase to the value specified by the associated
           recClassLimit for the class associated with the rows.
           Recordings shall maintain a chronological ordering in the table,
           based on their recordingTriggerTime value,
           with the oldest recording of a class occupying the row with
           recordingNumber = 1, and subsequent recordings filling subsequent
           rows. This ordering shall be maintained for those rows
           still remaining when recordings are cleared.
          <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2
        "
::= { recRecordingEntry 2 }

recordingNumber · deprecated

recordingNumber   OBJECT-TYPE
  SYNTAX      Integer32 (1..254)
  MAX-ACCESS  read-only
  STATUS      deprecated
  DESCRIPTION
    "<Definition>The recording number within this class for this 
      recording. Recording numbers shall be assigned starting at 1 and 
      shall increase to the value specified by the associated 
      recClassLimit for the class associated with the rows. 
      Recordings shall maintain a chronological ordering in the table, 
      based on their recordingTriggerTime value, 
      with the oldest recording of a class occupying the row with 
      recordingNumber = 1, and subsequent recordings filling subsequent 
      rows. This ordering shall be maintained for those rows 
      still remaining when recordings are cleared. 
    <Superseded by> NTCIP1201-RecMechV2.recMechV2RecordingIndex
    <Informative> The syntax of the replacement object is ITSPositive16. 
      The replacement table does not attempt to keep the oldest entry in 
      slot one; clearance of rows is based on overall size rather than 
      number of entries, which makes this type of row management more 
      difficult - but since row numbers do not change, managers can keep 
      track of the last row number retrieved and decrease the probability 
      of missing a recording. A manager can also use a get-next operation 
      to discover where the rows start in the table.
    <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2"
::= { recRecordingEntry 2 }

Meaning

Descriptions

3 unique

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

Description 1

<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. <Supplanted by> ISO26048-1-Recording.fdRecordingRecordingIndex <Informative> The syntax of the replacement object is ITSPositive16. The replacement table does not attempt to keep the oldest entry in slot one; clearance of rows is based on overall size rather than number of entries, which makes this type of row management more difficult - but since row numbers do not change, managers can keep track of the last row number retrieved and decrease the probability of missing a recording. A manager can also use a get-next operation to discover where the rows start in the table. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. <Superseded by> NTCIP1201-RecMechV2.recMechV2RecordingIndex <Informative> The syntax of the replacement object is ITSPositive16. The replacement table does not attempt to keep the oldest entry in slot one; clearance of rows is based on overall size rather than number of entries, which makes this type of row management more difficult - but since row numbers do not change, managers can keep track of the last row number retrieved and decrease the probability of missing a recording. A manager can also use a get-next operation to discover where the rows start in the table. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Evidence

Source records

3 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 · 1 source

Description 1

recordingNumber · deprecatedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: deprecated.

Names: recordingNumber

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recordingNumber",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "254",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. <Supplanted by> ISO26048-1-Recording.fdRecordingRecordingIndex <Informative> The syntax of the replacement object is ITSPositive16. The replacement table does not attempt to keep the oldest entry in slot one; clearance of rows is based on overall size rather than number of entries, which makes this type of row management more difficult - but since row numbers do not change, managers can keep track of the last row number retrieved and decrease the probability of missing a recording. A manager can also use a get-next operation to discover where the rows start in the table. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2\"",
    "::=",
    "{",
    "recRecordingEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            254
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. <Supplanted by> ISO26048-1-Recording.fdRecordingRecordingIndex <Informative> The syntax of the replacement object is ITSPositive16. The replacement table does not attempt to keep the oldest entry in slot one; clearance of rows is based on overall size rather than number of entries, which makes this type of row management more difficult - but since row numbers do not change, managers can keep track of the last row number retrieved and decrease the probability of missing a recording. A manager can also use a get-next operation to discover where the rows start in the table. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

recordingNumber · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: recordingNumber

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recordingNumber",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "254",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2 \"",
    "::=",
    "{",
    "recRecordingEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            254
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 3ITE public NTCIP working repository MIBs1 record · 2 sources

Description 3

recordingNumber · deprecatedITE public NTCIP working repository MIBs2 sources

Status in source: deprecated.

Names: recordingNumber

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recordingNumber",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "254",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. <Superseded by> NTCIP1201-RecMechV2.recMechV2RecordingIndex <Informative> The syntax of the replacement object is ITSPositive16. The replacement table does not attempt to keep the oldest entry in slot one; clearance of rows is based on overall size rather than number of entries, which makes this type of row management more difficult - but since row numbers do not change, managers can keep track of the last row number retrieved and decrease the probability of missing a recording. A manager can also use a get-next operation to discover where the rows start in the table. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2\"",
    "::=",
    "{",
    "recRecordingEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            254
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. <Superseded by> NTCIP1201-RecMechV2.recMechV2RecordingIndex <Informative> The syntax of the replacement object is ITSPositive16. The replacement table does not attempt to keep the oldest entry in slot one; clearance of rows is based on overall size rather than number of entries, which makes this type of row management more difficult - but since row numbers do not change, managers can keep track of the last row number retrieved and decrease the probability of missing a recording. A manager can also use a get-next operation to discover where the rows start in the table. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.1.1.7.9.9.1.1 recordingClass00
1.3.6.1.4.1.1206.4.1.1.7.9.9.1.3 recordingID00
1.3.6.1.4.1.1206.4.1.1.7.9.9.1.4 recordingConfigID00
1.3.6.1.4.1.1206.4.1.1.7.9.9.1.5 recordingTriggerTime00
1.3.6.1.4.1.1206.4.1.1.7.9.9.1.6 recordingStatus00
1.3.6.1.4.1.1206.4.1.1.7.9.9.1.7 recordingTriggerRecNum00
1.3.6.1.4.1.1206.4.1.1.7.9.9.1.8 recordingNumEntries00