ETSI's Bug Tracker - Part 05: TTCN-3 Runtime Interface
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006015 | Part 05: TTCN-3 Runtime Interface | New Feature | public | 05-03-2012 13:05 | 11-12-2012 15:18

Reporter | tepelmann |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.5.1 (published 2013-04) | Fixed in Version | v4.5.1 (published 2013-04) |
Clause Reference(s) | 201 873-5 V4.3.1 - 5.2
Source (company - Author) | Testing Technologies - tepelmann

Summary | 0006015: Introduction of triErrorReq for the TRI as it is defined in TCI-CD

Description

In the TRI specification in chapter 5.2. "Error handling" there is nothing stated how to handle "asynchronous" notifications about an unrecoverable error situation in the SA or PA.
E.g. such a situation can occur at any time when a lower layer indicates an error while processing communication operations like receive, where the layer has been initialized and the receiver thread has been started while mapping a port.
Like in the TCI-CD required interface we propose to introduce the following method as equivalent for the TRI:
Signature : void triErrorReq(in TString message)
In Parameters: message: A string value, i.e. the error phrase describing the problem.
Return Value : void
Constraint : Shall be called whenever an error situation has occurred.
Effect : The TE will be notified about an unrecoverable error situation within the SA or PA and forward the error indication to the test management.

Steps To Reproduce |
Additional Information | As an addition to the above proposed method for the TRI interface, for the extended TRI there could be an additional method with a parameter of type Object, where the error can be given in any representation, i.e. as exception.
Tags | No tags attached.

Relationships

parent of | 0006176 | closed | Ina Schieferdecker | Ext Pack: Extended TRI (ES 202 789) | Extension of triErrorReq to Object

Attached Files | CR6015.docx (53,108) 12-07-2012 17:38 http://oldforge.etsi.org/mantis/file_download.php?file_id=2695&type=bug CR6015_v2.docx (54,760) 13-07-2012 11:34 http://oldforge.etsi.org/mantis/file_download.php?file_id=2699&type=bug

Issue History
Date Modified | Username | Field | Change
05-03-2012 13:05 | tepelmann | New Issue |
05-03-2012 13:05 | tepelmann | Clause Reference(s) | => 201 873-5 V4.3.1 - 5.2
05-03-2012 13:05 | tepelmann | Source (company - Author) | => Testing Technologies - tepelmann
10-07-2012 12:13 | Ina Schieferdecker | Project | TTCN-3 Change Requests => Part 05: TTCN-3 Runtime Interface
10-07-2012 12:15 | Gyorgy Rethy | Assigned To | => Ina Schieferdecker
10-07-2012 12:15 | Gyorgy Rethy | Status | new => assigned
10-07-2012 12:15 | Gyorgy Rethy | Target Version | => Edition 4.5.1
12-07-2012 16:47 | Ina Schieferdecker | Issue cloned: 0006176 |
12-07-2012 16:47 | Ina Schieferdecker | Relationship added | parent of 0006176
12-07-2012 17:38 | Ina Schieferdecker | File Added: CR6015.docx |
12-07-2012 17:39 | Ina Schieferdecker | Note Added: 0010903 |
12-07-2012 17:39 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Tomas Urban
12-07-2012 17:39 | Ina Schieferdecker | Resolution | open => fixed
13-07-2012 08:55 | Tomas Urban | Note Added: 0010907 |
13-07-2012 08:55 | Tomas Urban | Assigned To | Tomas Urban => Ina Schieferdecker
13-07-2012 11:18 | Ina Schieferdecker | File Added: CR6015_v2.docx |
13-07-2012 11:20 | Ina Schieferdecker | File Deleted: CR6015_v2.docx |
13-07-2012 11:20 | Ina Schieferdecker | File Added: CR6015_v2.docx |
13-07-2012 11:34 | Ina Schieferdecker | File Deleted: CR6015_v2.docx |
13-07-2012 11:34 | Ina Schieferdecker | File Added: CR6015_v2.docx |
13-07-2012 11:35 | Ina Schieferdecker | Note Added: 0010914 |
13-07-2012 11:35 | Ina Schieferdecker | Status | assigned => resolved
13-07-2012 11:35 | Ina Schieferdecker | Note Added: 0010915 |
13-07-2012 11:35 | Ina Schieferdecker | Status | resolved => closed
11-12-2012 15:18 | Ina Schieferdecker | Fixed in Version | => Edition 4.5.1

Notes

(0010903)
Ina Schieferdecker
12-07-2012 17:39

Please check

(0010907)
Tomas Urban
13-07-2012 08:55

I think the proposed draft is OK, but maybe we could consider to extend the description part of the new functions so that it is obvious that the error calls should not be performed when the SA or PA is processing a TRI call from the TE, because this situation is handled by returning TRI_ERROR:
Shall be called whenever an error situation has occurred.
-->
(triSAError:) Shall be called by the SA whenever an error situation has occurred, with exceptions of errors that appear during processing of TRI calls initiated by the TE.
(triPAError:) Shall be called by the PA whenever an error situation has occurred, with exceptions of errors that appear during processing of TRI calls initiated by the TE.

(0010914)
Ina Schieferdecker
13-07-2012 11:35

Added the new error handling operations to the IDL spec in Annex A

(0010915)
Ina Schieferdecker
13-07-2012 11:35

Implemented as described in v2