1317   No clear MMS ServiceError code mapping in 8-1 table 23 for ACSI code "parameter-value-inappropriate"

Created: 10 Oct 2014

Status: In Force (green)

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

Links: #1338 SetBRCBValues(unknow EntryID)

Page: Table 23


Paragraph: 8

Category: Issue for edition 2 of this part


After the buffer of one BRCB is cleared, Client sends SetRCBValues to EntryID with correct value, server shall response- with ACSI code "parameter-value-inappropriate", which indicates SetBrcbValues of entryID fails because the setable entryID is no longer available. (7-2 clause
But there is no clear mapping in 8-1 table 23 for parameter-value-inappropriate. So which kind of MMS ServiceError code is acceptable?


Suggest to use MMS error code "object-value-invalid" to map ACSI service error "parameter-value-inappropriate"

Discussion Created Status
06 Feb 15 In Force (green)
I agree. 18 Dec 14 Ballot Period
proposal of Andreas accepted.
See tissue 7-2 1338.
MMS remains object-value-invalid in the write(BRCB$entrID, unknownEntryID).
18 Dec 14 Discussion (red)
I think it this is an error in 7-2 (clause Such (semantical) errors normally map to parameter-value-inconsistent, whereas parameter-value-inappropriate is used for syntactical errors (e.g. filename syntax error).

I propose to move this tissue to 7-2 and change the ACSI error there to parameter-value-inconsistent, which already maps to the MMS DataAccessError code "object-value-invalid".
14 Nov 14 Triage


Privacy | Contact | Disclaimer

Tissue DB v.