0005550: Method out parameter handling if Method result is bad

ID	Project	Category	View Status	Date Submitted	Last Update

0005550	10000-004: Services	Spec	public	2020-03-22 16:52	2020-06-15 17:56

Reporter	Matthias Damm	Assigned To	Matthias Damm
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	fixed

Summary	0005550: Method out parameter handling if Method result is bad
Description	It is not defined if output arguments are valid if the Method result is bad. This is especially an open question for the case where a Method has a custom out parameter with status information about an error. To be consistent, with the Service level, the Method output arguments should be ignored if the Method result is bad. But this is not defined at the moment. If the result is Bad_InvalidArgument, the method must return inputArgumentResults. If we define that no output arguments are returned in the bad case, we should defined a Uncertain status code that indicates that Method call did not succeed but that the out parameters contain additional error information.
Tags	No tags attached.

Commit Version
Fix Due Date

Jim Luth 2020-05-12 15:48 administrator ~0012047	We don't need to define a new Uncertain sub-status. The Uncertain code with no sub-status should be used by Methods. The spec needs to add the statement that "Servers shall omit output arguments when returning BAD StatusCode(s) and Clients shall ignore output arguments when receiving a BAD result".

Matthias Damm 2020-06-10 18:39 developer ~0012230	Added to Method Response statusCode If the Method execution fails but the outputArguments provide additional information like an application specific error code, the Method shall return a StatusCode with Severity Uncertain. outputArguments The list shall be empty if the statusCode Severity is Bad. Added in OPC 10000-4 - UA Specification Part 4 - Services Draft 1.05.08.docx

Jim Luth 2020-06-15 17:56 administrator ~0012310	Agreed to changes in Virtual F2F.

Date Modified	Username	Field	Change
2020-03-22 16:52	Matthias Damm	New Issue
2020-03-23 09:22	Matthias Damm	Description Updated
2020-05-12 15:48	Jim Luth	Note Added: 0012047
2020-05-12 15:48	Jim Luth	Assigned To	=> Matthias Damm
2020-05-12 15:48	Jim Luth	Status	new => assigned
2020-06-10 18:39	Matthias Damm	Status	assigned => resolved
2020-06-10 18:39	Matthias Damm	Resolution	open => fixed
2020-06-10 18:39	Matthias Damm	Note Added: 0012230
2020-06-14 11:52	Matthias Damm	Relationship added	related to 0004542
2020-06-15 17:56	Jim Luth	Status	resolved => closed
2020-06-15 17:56	Jim Luth	Fixed in Version	=> 1.05
2020-06-15 17:56	Jim Luth	Note Added: 0012310