User`s guide

112 DC 900-1317J
ADCCP NRM Programmer’s Guide
usTime: This field of the Monitor Data Notification header contains the time of the
event, in terms of milliseconds elapsed since a base time. If the ICP is located in a Free-
way server, or if it is embedded in a PCI-based host whose ICP driver supports Host
Timing. then the base time is start-of-day. Otherwise the base time is the time of ICP
startup. The reported time pertains to the completion of the transmission or reception
of the frame.
usEvent: This field of the Monitor Data Notification header contains the type of event
being conveyed. The defined event-type codes and their meanings are:
1: Received Frame Notification
2: Transmitted Frame Notification
usLinkID: This field of the Monitor Data Notification header contains the ICP-rela-
tive link number (0 through n-1, where n is the number of links on the ICP).
usLength: This field of the Monitor Data Notification header contains the number of
bytes of data that follows the header (i.e., the length of the frame image being con-
veyed). The minimum conveyed frame length is three bytes: one Address octet, one
Control octet, no Information octets, and no FCS octets.
usSequence: For received frames, this field of the Monitor Data Notification header
contains a sequence number. Otherwise 0 is stored. Received frames are associated with
a series of 16-bit sequence numbers (a distinct series for each link). The same number
is assigned both to the
usProtSequence field of the DLI_PROT_RECV_DATA (or
DLI_PROT_RECV_UNNUMBERED_DATA) command that reports receive data to the client,
and to this usSequence field in the associated Monitor Data Notification header.
This permits
the client to correlate the streams received at the link as they appear separately on the
Link and Monitor Sessions. (Note that since all received frames are assigned a one-up
sequence number regardless of frame type, the sequence numbers are generally not
consecutive for consecutive I-frames (or UI-frames).