Interval tracking data structure

Edit online

Learn about the interval tracking data structure as it is returned by the GETINTVL rule array keyword.

Table with three columns: Offset, length and description
Offset Length Description
00 14 Timestamp for the start of the interval. This is the time according to the adapter internal clock when a START request was received for the role_ID. This time value is set when the first START is received for the role_ID when the value of the start of the interval is currently zero. The value of the start of the interval is set to zero at system initialization, when a CLRDATA request is processed and tracking is stopped for the role_ID, or when a higher level zeroize request is processed that also clears the ACP tracking data. If a CLRDATA request is processed while tracking is enabled for the role_ID, then a new timestamp is written for the start of the interval.

If the value for the start of the interval is currently zero in the adapter, then this field is set to 0x00 bytes. If the value for the start of the interval is non-zero, the according timestamp is returned in this field in the CCA generalized time format: "YYYYMMDDHHMMSS".
14 14 Timestamp for the end of the interval. This is the time according to the adapter internal clock when a STOP request was received for the role_ID (after a previous START). This time value is set to zero when a new START request is received for the role_ID, at system initialization, when a CLRDATA request is processed, or when a higher level zeroize request is processed that also clears the ACP tracking data.

If the value for the end of the interval is currently zero in the adapter, then this field is set to 0x00 bytes. If the value for the end of the interval is non-zero, the according timestamp is returned in this field in the CCA generalized time format: "YYYYMMDDHHMMSS".
28 4 Counter (Big-Endian) of STOPPED intervals since the first START was issued for the role_ID. This counter is incremented when a START has been issued after a previous STOP that was issued during collection of ACP tracking data. At a high level, this counter indicates the number of times that tracking for the role_ID was stopped and then re-started. This count can be helpful when looking at audit logs to determine how many gaps need to be accounted for.

This counter is not allowed to roll over. A value of 0xFFFFFFFF indicates that this many or more gaps occurred. This counter is set to zero at system initialization, when a CLRDATA request is processed, or when a higher level zeroize request is processed that also clears the ACP tracking data.