780   What are 'unsupported trigger option at a control block?

This tissue has following status: green

Created: 04 Oct 2011

Links:

Page:

Clause: 14.2.2.11

Paragraph:

Category: Issue may impact interoperability of implementations of Edition 2

Issue: Part 7-2 states: If a BRCB does not support one or more of the trigger options, the attempt to set the TrgOp attribute to TRUE for one of these not supported values, shall cause a negative response of the SetReportControlValues service.
Unfortunately it is not clear what 'not supported' means:
a). the client tries to set trigger options unknown by the client (e.g. because they are defined by another edition of the standard). b). the trigger option does not apply to the implemented data model or the defined data set.
c). one of the server level trigger options (GI, Integrity period) is enabled.

Proposal: Clarify what 'Not supported' means. Suggested are the cases identified above, with following solution:
a). a negative ack is needed.
b). this case is irrelevant from the server / stack point of view, i.e. a positive ack is OK.
c). This MUST be supported by all servers, so again a negative ack is no choice....
Note that due to point a). above a client must be prepared to handle negative acks.

Discussion Created Status
?
Ballot until Editor
The change of TrgOps also applies to URCB and LCB as well as BRCB 26 Aug 13 green
The text in 7-2 Ed2
If a BRCB does not support one or more of the trigger options, the attempt to set the TrgOps attribute to TRUE for one of these not supported values shall cause a negative response of the SetBRCBValues service

shall be changed to:
The BRCB must support all of the trigger options.
13 Mar 13 green
The trigger options: data-change, quality-change, data-update, integrity and GI shall be supported by each instance of Report Control Block to grant a application interoperability.
However, the data model defines which trigger options (data-change, quality-change, data-update) are implemented in the object model.

In the event the trigger options are extended in a future version of the standard, it is mandatory that the server implementation responses with a negative SetBRCBValues when the requested Trigger option are not known by the server implementation.
24 Oct 11 final proposal

 

Privacy | Contact | Disclaimer