Created: 25 Mar 2013
Status: In Force (green)
Part: Part 7-1 (2011; Edition 2)
Paragraph: last before 6.4.5
Category: Issue for edition 2 of this part
The clause defines:
"For periodic calculation, the “event” ClcExp set to TRUE can be used as an event to report the new value (the statistical value) by the report control block or it may be logged as historical statistical data for later retrieval."
The ClcExp needs to be a member of a DataSet to be used as an event. But in this case only the ClcExp data object would be reported according to RBE (Report by exception). So, the "the new value (the statistical value)" cannot be reported.
We cannot use the concept of Statistical Data to send a set of values on a cyclical base AND start the cycle at the full hour! The ClcStr of CDC SPC (Enables the calculation start at time operTm from the control model (if set) or immediately, cannot be used because of the RBE definition of reports.
rptEna of the report control block could only be used to start, when a client sents a "enable=true" ... which may be received 5 seconds before the full hour or 10 seconds later ...
Define a possibility that a set of values of any number of data set members can be sent with a report.
The report usually is carrying a single member's value (RBE, dchg, qchg, or dupd), ALL members in case of integrity period (intpd) or general interrogation (gi), or a set of values of a set (less than ALL) of members in case of bufTm > 0. So, a client has to manage any set (1, many, all) of members' values.
It should at least be possible to send ALL member's values based on an event of any member's value change.