386   GetDataValues - leafs not accessible

Created: 14 Sep 2006

Status: In Force (green)

Part: Part 7-2 (2003)

Links:

Page: 054

Clause: 10.4.2.3

Paragraph:

Category: Issue for edition 2 of this part

Issue

It should be specified what happens when a leaf of a structured DataAttribute is not available for access (for get and set).

Should the service fail if one component fails? Should the response indicate success/failure for each component?

It would be helpful for future SCSMs to have such a definitive specification.

Proposal

tbd

Discussion Created Status
Status set to green. 17 Mar 07 In Force (green)
In case of Get there is no issue ... whatever is defined for the Reference will be returned. For set it is an issue. Because the structured value provided with the set may not match with the structure of the referenced object.

Added the following text to 10.4.3.4 Response -:

The attempt to set a DataAttribute or an underlying component that is not available shall be interpreted as a service failure. 		15 Feb 07 Ballot Period
I don't know what "leaf" means in the context of 7-2? However, in 8-1, due to the atomicity of MMS, that failure to access a DataAttribute causes the object access to fail.

However, this may not be the case when mapping to IEC 60870-5.

What SCSM is not specific? 		14 Sep 06 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1