Specifications

4.4.28 FORMAT-SPEC-X
MIB Entry: Data Format X specification
Index: 9.5.X
Label: FORMAT-SPEC-X
Description: FORMAT-SPEC-X returns the specification of the X
th
recording
format. This specification is an ordered list of Keep or Drop opera-
tions to be performed on portions of the received data packet. This
feature’s primary use is in conserving storage space by discarding
portions of a packet that may not be needed before the packet is
written to disk.
Response Element Type and Size Description
Format (ASCII-256-A) The format is defined as an ordered list of terms
Kxxxx or Dyyyy where Kxxx means that xxxx
bytes should be kept, and Dyyyy means that yyyy
bytes should be dropped. For instance, the pattern
“D0024K0512D0488” reads as “Drop the first 24 bytes,
keep the next 512, and drop the 488 subsequent bytes.
All xxxx and yyyy will add up to the specified UDP
packet payload size, so for the example shown, the
UDP packet payload size is 1024. These formats are
predefined based on data formats specified in the DP
ICD.
4.4.29 LOG-COUNT
MIB Entry: System Log Length
Index: 10.1
Label: LOG-COUNT
Description: LOG-COUNT reports the number of system log entries.
Response Format: <Count>
Response Element Type and Size Description
Count (ASCII-6-#) The number of entries in the system log.
4.4.30 LOG-ENTRY-X
MIB Entry: System Log Entry X
Index: 10.2.X
Label: LOG-ENTRY-X
Description: LOG-ENTRY-X reports the X
th
entry in the system log.
Response Format: <MJD>’<MPM>’<Message Class>’<Message>
Response Element Type and Size Description
MJD (ASCII-6-#) MJD when the entry was logged.
MPM (ASCII-9-#) MPM when the entry was logged.
Message Class (ASCII-7-A) One of: “info...”, “warning”, or “error..” (periods in-
dicate padding spaces)
Status (ASCII-234-A) A human readable string of at most 234 characters,
padded with spaces, describing an event of interest.
21