User Manual
Appendix E
GFK-2849A
Oct 2019
Protocol Implementation extra Information for Testing (PIXIT)
140
Description
Value / Clarification
quality change
Yes
data update
Yes
general interrogation
Yes
The minimum required optional
fields are:
sequence-number
Yes
report-time-stamp
No
reason-for-inclusion
No
data-set-name
Yes
data-reference
No
buffer-overflow
No
entryID
Yes
conf-rev
No
Does the client support
segmented reports?
Yes
Does the client support pre-
assigned RCB?
Yes
Does the client support
reported data sets containing
structured data objects or data
attributes?
reporting of data objects
Yes
reporting of data attributes
Yes (By Polling)
Describe how the client does
respond when an URCB is
already reserved.
The client tries to use another URCB if dynamically allocated;
fallback is polling.
Describe how the client
responds when a BRCB is
already reserved.
Variables will be polled
Describe how the client
responds to a
SetBRCBValues(EntryID).
The client accepts negative responses internally.
Describe how the client
responds when a report has an
unknown: dataset, RptId,
unexpected number of dataset
entries, and/or unexpected data
type format entries.
Dataset directory and RCB configuration is read out at each
associate
Describe how the client detect
reporting configuration
changes (mismatches). Does it
check the “configuration
revision” attributes and/or does
it check the dataset members?
RCB configuration is read out at each associate, “conf
iguration
revision” doesn’t care
Describe how to force the client
to change the RCB buffer time.
Not used
