1336   enhanced the mapping text for the setValues.

Created: 08 Dec 2014

Status: In Force (green)

Part: Part 8-1 (2011; Edition 2)

Links:

Page:

Clause:

Paragraph:

Category: Issue for edition 2 of this part

Issue

As discussed in Tissue #1322, an enhanced description of the set<CB>Values is required to address one-or-multiple set<CB>Values in the next revision of 8-1.

Proposal

SetBRCBValue(BRCBRef, brcbAttribute1, value1) is mapped to a MMS write Request (BRCBRef.brcbAttribute1, value1).

SetBRCBValue(BRCBRef, brcbAttribute1, value1, brcbAttribute2, value2) is mapped to either
-> two MMS write Requests
(BRCBRef.brcbAttribute1, value1)
(BRCBRef.brcbAttribute2, value2)
it results in 2 write responses therewith with two accessResults.
-> a single MMS write Request ({BRCBRef.brcbAttribute1, value1}, {BRCBRef.brcbAttribute2, value2}) equivalent to 2 writes as the MMS write response will have 2 accessResults.

in both case, it is clear that the MMS mapping provides only access to single attributes, and the number of accessResult shows how many SetBRCBValue were in deed performed.

Discussion Created Status
06 Feb 15 In Force (green)
Atomicity, in terms of MMS, refers to the V-PUT service procedure. The V-PUT (according to ISO 9506-1) is executed on a per VariableAccessSpecification basis (e.g. for MMS Write-Request). For each VariableAccessSpecification a V-PUT will succeed or fail resulting in a AccessResult for each VariableAccessSpecification found in the Write-Request.

I agree with the proposal to add enhanced text. 		18 Dec 14 Ballot Period

 

Privacy | Contact | Disclaimer

Tissue DB v. 24.12.4.1