0008675: Historical Read raw, timestampsToReturn Neither, must return Bad_InvalidTimestampArgument at service level

ID	Project	Category	View Status	Date Submitted	Last Update

0008675	Compliance Test Tool (CTT) Unified Architecture	4 - Test Case Definition	public	2023-02-03 09:43	2023-02-20 21:18

Reporter	Stephen TISSOT	Assigned To	Paul Hunkar
Priority	high	Severity	major	Reproducibility	always
Status	assigned	Resolution	open

Summary	0008675: Historical Read raw, timestampsToReturn Neither, must return Bad_InvalidTimestampArgument at service level
Description	In this documentation https://reference.opcfoundation.org/Core/Part4/v104/docs/5.10.3.4#Table58 Bad_InvalidTimestampArgument is required at operational level, but looks like the requirement is to return this status code at service level. 2 possible solutions: • Add the Bad_InvalidTimestampArgument to the list of ServiceResults • Add a description in the timestampsToReturn service parameter to explain that the result is to be returned for all Operations.
Tags	No tags attached.

Files Affected

Date Modified	Username	Field	Change
2023-02-03 09:43	Stephen TISSOT	New Issue
2023-02-06 15:38	Paul Hunkar	Assigned To	=> Paul Hunkar
2023-02-06 15:38	Paul Hunkar	Status	new => assigned
2023-02-15 16:36	Paul Hunkar	Relationship added	related to 0008453
2023-02-15 16:44	Paul Hunkar	Assigned To	Paul Hunkar => Alexander Allmendinger
2023-02-15 16:45	Paul Hunkar	Assigned To	Alexander Allmendinger => Paul Hunkar
2023-02-20 21:16	Matthias Damm	Relationship added	related to 0008452
2023-02-20 21:18	Matthias Damm	Note Added: 0018775

related to	0008453	closed	Paul Hunkar	10000-011: Historical Access	Timestamps related error handling needs clarification
related to	0008452	closed	Matthias Damm	10000-004: Services	TimestampsToReturn related status codes for HistoryRead inconsistent

Matthias Damm 2023-02-20 21:18 reporter ~0018775	Part 4 was wrong to require Bad_InvalidTimestampArgument for Neither. The right status Bad_InvalidTimestampArgument is listed in the service level status code table. The Change in Part 11 is related to the case where the server does not support Server timestamp.