Telelogic Tau 4.3 Latest news 2001-09-19

Telelogic Tau 4.3
Latest news 2001-09-19

This document contain the latest information regarding the following aspects of the Telelogic Tau 4.3 release:

Errors corrected since release 4.2.0.
Known errors and bugs in the software.
Known errors and corrections to the documentation.
Undocumented known limitations.
Other undocumented features.
Available patches.
Features added after the 4.3.0 release

1. How to install a patch

Is your installation modified?
Files changed by patch installations
On Windows
On Unix

2. Release 4.3.0

Corrected errors in 4.3.0

SDL Suite and TTCN Suite common tools corrected errors

ASN.1 Encoding/Decoding Library
ASN.1 Utilities
Autolink
DOORS Integration
Help Viewer
Organizer
Organizer Log
Print
TTCN Link

SDL Suite corrected errors

Cadvanced / Cbasic Library
Cadvanced / Cbasic SDL to C Compiler
CIF / SDL Converter
Cmicro Library
Cmicro SDL to C Compiler / Cmicro Library
CPP2SDL
H2SDL
MSC Editor
OM Editor
SDL Analyzer
SDL Editor
SDL Simulator
SDL SimUI / ValUI
SDL Simulator
SDL Target Tester
SDL Validator
Targeting Expert
Tight Integration

TTCN Suite corrected errors

Defcon Utility
GCI / EGCI API
Test Execution
TTCN Access
TTCN Analyzer
TTCN Browser / Desktop
TTCN Co-simulator
TTCN to C Compiler

Known software errors in 4.3.0

SDL Suite and TTCN Suite common tools known errors

General
Organizer
ASN.1 Utilities
ASN.1 BER/PER Encoding/Decoding
Doors integration
Java Interface
Microsoft Word Integration (Windows only)
Print
Text Editor

SDL Suite known errors

Cadvanced / Cbasic SDL to C Compiler
Cmicro SDL to C Compiler / Cmicro Library
CPP2SDL
H2SDL
MSC Editor
OM Editor
Preprocessing during Make
SC to SDL converter
SDL Editor
SDL Index Viewer
SDL Info Server
SDL Simulator
SDL SimUI / ValUI
SDL Validator
Targeting Expert
Target Simulation
Target Tester
Threaded Light Integration

TTCN Suite known errors

General
ASN.1
On-Line Help
Table Editor
TTCN Analyzer
TTCN to C Compiler
TTCN Co-simulator
TTCN Desktop / Browser
TTCN Link
Test Execution

Known documentation errors in 4.3.0

SDL Suite
TTCN Suite known documentation errors

Test Suite Parameters

Undocumented limitations in 4.3.0

SDL and TTCN Suite known limitations

Doors integration

TTCN Suite known limitations

TTCN Browser / Desktop

Undocumented changed functionality in 4.3.0

SDL and TTCN Suite changed functionality

Licensing with FLEXlm 7.2g

SDL Suite changed functionality

CPP2SDL
SDL Analyzer

TTCN Suite changed functionality

GCI / EGCI API
TTCN to C Compiler

1 How to install a patch

Is your installation modified?

If any files have been changed or modified from standard distributions the patch installation will not overwrite these files. For example, if you have received a special versions or have modified a source code file these files will be left as is without updates.

As a precaution, always save backups of the original files and revert to these prior to installing a patch.

Files changed by patch installations

All files included in a patch delivery are listed in the file patchfiles.log located in the installation directory after installing a patch.

On Windows

Download the file p-<product>-<patch level>-win.exe to your computer. Then execute the downloaded file by double-click on it. Select the appropriate installation directory if needed.

Toggle backing up is possible if button change options is pressed in the Confirm Telelogic Tau 4.3 Upgrade dialog.

On Unix

Download the file p-<product>-<patch level>-<OS-platform>.rtp to the installation directory of SDL and/or TTCN Suite.
Change directory to the installation directory of SDL and/or TTCN Suite.
Issue the command:

./bin/patch p-<product>-<patch level>-<OS-platform>.rtp

e.g. ./bin/patch p-ttcn-43-1-sun.rtp

Note: Do not use /bin/patch. You must use ./bin/patch.

2 Release 4.3.0

This chapter contains a list of errors in Telelogic Tau 4.2.x that have been corrected in the Telelogic Tau 4.3.0 release. The chapter also contains a list of known errors in the Telelogic Tau 4.3.0 release.

Corrected errors in 4.3.0

SDL Suite and TTCN Suite common tools corrected errors

ASN.1 Encoding/Decoding Library
1005373 (HP only): The _HPUX_SOURCE switch being defined in the file scttypes.h didn't affect the compilation of the coder library, thus causing compilation errors when compiling. This is solved in 4.2.3.
1005744: Memory leak in ASN1EncodeOctet function. This affects encoding from SDL when the OctetString buffer is used. This is corrected in 4.2.2.
1006062: The small buffer detected buffer full one byte too early and either allocated more bytes (buffer allocated memory) or returned an error message (user allocated memory). This is solved in 4.2.3.
1006063, 1006065: The small buffer implementation of BMS in some cases fails to detect that the buffer is full and continues to write outside allocated memory. This is correct in 4.2.2.
1006557: BufGetDataLen( Buf) did not return length 0 on a freshly created Buffer. This is solved in 4.2.4.
1006811: The default for PER encoding is aligned, but it should be unaligned. This is solved in 4.2.4.
3001620: Problem when using user defined memory management. This is solved in 4.2.4.
If a BIT STRING or OCTET STRING is restricted by size constraint with extension marker for Type1 below there is wrong PER encoding for zero length value. Encoding bit-field doesn't have extension bit. This conflicts with X.691 15.5 for BIT STRING and X.691 16.3 for OCTET STRING. This is solved in 4.3.0.
Type1 ::= BIT STRING (SIZE(5..8, ..., 0..3))
Compiling with the switch CODER_BER_CONSTRUCTED produced compiler errors in module ber_base.c and ber_content.c. This is solved in 4.2.3.
In 4.2.3, BER constructed encoding is corrected for the following case:
Base ::= VisibleString 
Type1 ::= [APPLICATION 3] IMPLICIT Base 
Type2 ::= [2] Type1
In 4.2.3, PER encoding for extensibility zero string corrected for the following case:
Type1 ::= VisibleString (SIZE(...)) 
Value1 Type1 ::= ""
Previously, PER decode produced the error message:
ERROR 12: No more data for read
In 4.2.3, all ASN.1 type info is stored in ROM. Previously some parts were stored in RAM.
In 4.2.3, include statements in the ASN.1 Encoding / Decoding Library are changed to be using UNIX style paths (`/') on all platforms.
If a sequence, set or choice type is restricted by WITH COMPONENTS with an ABSENT qualifier there is a memory access error in the BER/PER decode procedure for Type2 in the example below. The problem applies to generic function C code generation only. This is solved in 4.2.3.
Type1 ::= CHOICE {
 a SEQUENCE OF INTEGER,
 b SET {
  str PrintableString DEFAULT "Print me ... :))))"
              }
}
Type2 ::= Type1 (WITH COMPONENTS {
 a ABSENT,
 b PRESENT
})
ASN.1 Utilities

1007354: The test suite generation via TTCN Link produces values with incorrect names for values in CHOICE types resulting from open types. According to ASN.1 standard the names of types begin with capital letter and the names of values with lower letter. This is solved in 4.2.4.

Autolink

1005050: Inconsistency between SDL newtypes with literals and TTCN enumerated types. Now (in 4.2.1), the values for TTCN enumerated starts with 0 instead of 1.

DOORS Integration

1004812: Problems with the integration between TTCN Suite and DOORS. This is corrected in 4.2.1.

Help Viewer

1005216 (Windows only): When using the Help application from the CIF converters the sdthelp.exe and the sdt.exe applications must be terminated from the Task Manager. This is solved in 4.3.0.
1005518 (Windows 2000 only): The Help Viewer (sdthelp.exe) crashes if it is running when closing the Organizer. This is corrected in 4.2.1.

Organizer

1003902: When doing Copy + Paste or Clear + Undo of reference symbols in the SDL Editor now in 4.3 also the MSCs and typebased instances in the underlying substructure are handled correctly.
1004713 (Windows only): The command Tools | TTCN | Find Table is in 4.3 always dimmed on Windows. The command is only implemented on UNIX.
1005476: The `Show Target Directory' setting is not saved in the system file. This is corrected in 4.2.1.
1005629: When using Add Existing on an SDL package, any SDL PR files contained were not handled correctly; for instance, it was impossible to open them in an editor. This is corrected in 4.2.2.
1005777: It is not possible to build a SDL Validator by using the Validator quick-button in the Organizer. This is corrected in 4.2.1.
1006695: When adding a new SDL PR Text object in the Organizer and connecting it to an existing file the name of the object was gone. This is corrected in 4.2.4.
1007260 (Windows only): It is now (in 4.2.4) possible to start the Organizer by double clicking on an xx.sdt file where the path and/or filename contains spaces.
1007401: When using include expressions and *.syn files we now in 4.3 use the synfile that is closest to the diagram.

Organizer Log

1006149 (Japanese version only): It is not possible to use the Navigate Up and Down quick-buttons to browse between messages. This is corrected in 4.2.3.
1006149 (Japanese version only): The Organizer Log sometimes crashes. This is corrected in 4.2.2.

Print

1002544: Existing files (.png and .html files) were overwritten when printing to Web files. This is corrected in 4.2.1.
1004295: When printing to Framemaker formats it is now in 4.3 possible to set a special paper layout and margin settings. These settings should be set to reflect the layout that is used in the Framemaker document.
1004669: The Edit Footer Template Dialog now in 4.3 have a correct title.
1005138: If Print margins in the preference file are set to values that are larger than the paper size the application can crash. This is solved in 4.3.
1005292: When printing to Word and using the "print to fit page" option the diagrams are not scaled to fit the Word document. This has been fixed in 4.3. The paper size and the margin values are in 4.3 the values given from the Word document (as created when choosing a new blank document, normal.dot template). Thus the Print preferences are not used anymore when printing to Word.
2001292: Margins and Paper Format should not be selectable when the destination format is print to Word. The actual values are taken from the current Word document. Therefore, in 4.3 the margins button is dimmed when the Word printing option has been chosen.

TTCN Link

1005052: Inconsistency between SDL newtypes with literals and TTCN enumerated types. Now (in 4.2.1), the values for TTCN enumerated starts with 0 instead of 1.

SDL Suite corrected errors

Cadvanced / Cbasic Library

1006078: The compilation switches XNOUSEOFREAL and XNOUSEOFOCTETBITSTRING are missing in a number of places in the Cadvanced / Cbasic Library, causing compilation errors when compiling with those switches. This is solved in 4.2.3.

Cadvanced / Cbasic SDL to C Compiler
1004768: Generated lines that were longer than 2000 sometimes lost a space character. This is corrected in 4.3.0.
1005738: Code generated for an `output to' expression with a PId variable do not compile if generic operator-functions are used. This is corrected in 4.2.2.
1005800: An implicit void ** cast in the GenericFreeSort macro definition causes compilation errors. This error only occurs if generic functions are used together with C++ compilation. This is solved in 4.2.3.
1006022: Using Charstring as index type in an array type generated wrong code in the Readfunction. This is corrected in 4.3.0.
1006186: Extra parentheses around expressions in for example (.(2).) might lead to compilation errors when generic functions are used. This is solved in 4.2.3.
1006191: An error occurs when the String generator is instantiated with a structured type as parameter. This is corrected in 4.2.2.
Example:
The following 2 types are defined in the SDL system:
newtype A struct
x, y integer;
endnewtype;
newtype S String(A)
endnewtype;
If then an extract operator is applied directly to the result of the First operator (or Last operator) a C compilation error occurs, i.e. when writing:
First(Var_S) ! x
The same kind of problem occurs for Take operators in the Powerset and Bag generators.
1006344: Macro definitions generated in the environment header files for some types (Bag, Powerset and String) have the wrong number of parameters in generic functions mode. This is solved in 4.2.4.
1007159: When generic functions are used the initialization of structural types doesn't work fully in all cases. This is solved in 4.2.4.
3001118: Extracting a component of a choice which in itself is a component in a structured type might lead to compilation errors. This error occurs if generic functions are used. This is solved in 4.2.3.
3001214: A cast is missing in the macro definition for yMkString in some cases when generic functions are used together with a C++ kernel. This is solved in 4.2.4.
Initialization of Pid, Time, Duration and Object_identifier components might cause compilation error. This is solved in 4.2.4.
Example:
In 4.2.4 the type str will no longer cause compilation errors.
newtype str Struct
	  p Pid := Null;
endnewtype;
A type name instead of the value is sometimes generated for the actual generator parameter. This might occur for constant parameters of user defined generators. This is solved in 4.2.3.
In some circumstances for in/out parameters to operators and procedures, when the actual parameter is a component of a general array or a string, compilation errors might occur. This is solved in 4.2.3.
Continuous signals and enabling conditions where the expression contains values or variables of structured data types might lead to compilation errors if generic functions are used. This is solved in 4.2.3.
Code that does not compile is generated for a two level extract when the outer level is an array or a carray, and the inner extract is a general array or string. This is solved in 4.2.3.
When indexing an array, with character as index type, with a value in the range 128 to 255, the index might be treated as a signed char and will thus be in the range -128 to -1. This is corrected by adding a type cast to unsigned char to the index expression. This is solved in 4.2.3.
Indexing a syntype of array may cause problems. This is fixed in 4.2.1.
CIF / SDL Converter

1005395: A quote character is now in 4.3.0 allowed in a note on the heading for a diagram, when doing CIF to SDT.
3001161: When doing SDT to CIF and back to SDT extra spaces are inserted for comment and text-extension symbols. This is solved in 4.2.4.

Cmicro Library

1004217: Array bounds read while starting SDL processes. This is corrected in 4.2.1.
1005315, 1005316: When removing a expired timer from the signal queue the search algorithm continues after finding the timer signal. This is corrected in 4.2.1.

Cmicro SDL to C Compiler / Cmicro Library
105427: The Cmicro SDL to C Compiler crashes when using external procedures in process types. This is corrected in 4.2.1.
1005924: The state index and transition tables are not always generated correctly in systems where one process inherits another process type. This could lead to signals being implicitly consumed. This is solved in 4.3.0.
1006344: Macro definitions generated in the environment header files for some types (Bag, Powerset and String) have the wrong number of parameters in generic functions mode. This is solved in 4.2.4.
1007159: When generic functions are used the initialization of structural types doesn't work fully in all cases. This is solved in 4.2.4.
1007365: A decision variable is not initialized correctly and might cause a problem in free. This happens if the decision is complex (more than one path plus an else path), if the decision expression is of a type containing pointers, and if the decision is in a procedure or an operator diagram. Such variables are now (in 4.2.4) initialized as they should.
3001179: In the case of an operator returning a structured type and if the operator at the same time has a return variable, i.e. "returns <variable> <SDL_type>", the return variable is not initialized correctly, which might lead to crashes in the generated application. This is solved in 4.2.3.
3001214: A cast is missing in the macro definition for yMkString in some cases when generic functions are used together with a C++ kernel. This is solved in 4.2.4.
Incorrect initialization of Pid components. This is solved in 4.2.4.
Example:
newtype str Struct
	  p Pid;
endnewtype;
dcl v str;
In earlier versions this results in v!p /= Null. In 4.2.4, v!p = Null.
CPP2SDL
1004940: The translation of a few types, corresponding to predefined SDL sorts, had previously an incorrect case. This is corrected in 4.2.1. The table below shows the affected C/C++ types and their corresponding SDL type translation.

C / C++ type SDL type

SDL_Bit_String

Bit_string

SDL_Object_Identifier

Object_identifier

SDL_Octet_String

Octet_string

SDL_PId

Pid

SDL_Null

NULL
3001124: In some cases CPP2SDL fails to translate classes derived from template classes. This is solved in 4.2.3.
Example:
In 4.2.3 the C++ class CUseTemplate below will be translated to SDL.
template <class T>
class CTemplateBase
{
public:
    int GetSize() { return sizeof(T); }
};
class CUseTemplate: public CTemplateBase<CUseTemplate>
{
public:
 CTemplateBase<int> MyAttr;
};
3001139: The constructor for a C++ class that is defined in a namespace is generated incorrectly. This can for example occur in the read function for that class. This is solved in 4.2.4.
3001515: The REFNAME directive generated by CPP2SDL is in some cases ignored when code is generated for the assign function. This problem only occurs if generic functions are used. This is solved in 4.2.4.
A typedef of a tagged type, where the name of the tag is the same as the name of the typedef, was previously not translated if an import specification was used. This is corrected in 4.3.0.
Example:
Import Specification:
TRANSLATE {

  S

}
C Header:
typedef struct S {

  int x;

} S;
CPP2SDL only issues a warning if an undeclared identifier is encountered in an expression, although it is a semantic error. In 4.3.0 CPP2SDL will issue an error instead.
Previously CPP2SDL crashed when a C++ reference was translated with the option -novariables set. This is corrected in 4.3.0.
Example:
int i = 128;

int& j = i;
H2SDL

3001082: Dereferencing a pointer in SDL causes compilation error. This is solved in 4.2.3.
3001256: Sometimes H2SDL generates SDL code where the #SDL operator will map names to wrong entities. This is corrected in 4.2.4.

MSC Editor

1005962: When simulating and creating an MSC PR trace file lost messages are displayed incorrectly when opened in the MSC editor. This is solved in 4.2.3.
1006504, 1007033: In the MSCE when using a condition symbol and typing a line ended by an underscore the Editor crashes when typing characters on the second line. This is corrected in 4.2.4.
1007561: When navigating from a MSC reference by double clicking on the name, sometimes the wrong diagram was chosen. This is solved in 4.3.0.

OM Editor

1004782: In the HMSC editor, the command Create Link is now in 4.3.0 hazed when there is nothing selected.

SDL Analyzer

1005602: Defining a method called `Copy' causes the SDL Analyzer to crash. This is corrected in 4.2.1.
1005801: The analyzer no longer crash when a variable is used in an assignment without a right hand side. This is corrected in 4.3.0.
1006012: The analyzer no longer picks the wrong definition when there are several with the same name. This is corrected in 4.3.0.
1006891: When having two SDL systems in the sdt file and also two sets of ASN.1 modules under two separate modules in the sdt file, the SDL Analyzer crashes when extracting the info about which ASN.1 modules are used in the SDL system. This is solved in 4.2.4.
1007026: A MSC has been connected to the SDL system diagram as a dependency. When you try to do a semantic and syntax analysis the SDL Analyzer crashes with an application error. This is solved in 4.2.4.
1007455: The SDL Analyzer do not complain on assignment statements where left and right side have incompatible types if the left side have several matches. This is solved in 4.2.4.
3001024: In the 4.2.1 patch graphical macros are not handled correctly by the SDL Analyzer. This is corrected in 4.2.2.
3001474: Analyzer error when inherited type symbol is above base type symbol in diagram. This is solved in 4.2.4.
3001609: When the #SDL directive is used local names in a compound statement of an operator diagram or procedure are not recognized. This results in an error during semantic analysis. This is solved in 4.2.4.

SDL Editor
1003940: In version 4.3 for each diagram we save the status (on/off) of the textual syntax check in the diagram file.
1004119: When moving the decision symbol and the outgoing line is moved (not selected) it is now in 4.3.0 correctly updated during the movement.
1004816: In the SDL editor, endpoint markers is now in 4.3.0 always shown for the heading symbol when a link to it is created.
1004823: When using `Tidy Up' or when converting SDL PR to SDL GR an existing label name ending with _1 might give duplicates when new automatic labels are generated. This is corrected in 4.2.1.
1004893: In 4.3 the command line `sdtbatch -anything SDLfile' is no longer accepted.
1005088: When doing tidy up the heading will no longer in 4.3 overlap with a symbol for process diagrams.
1005253: The following syntax is no longer in 4.3.0 marked as being wrong in the SDL Editor.
1. Using (2,4) in a decision case
2. syntype s = charstring constants from ('0':'9',' ') 
endsyntype;
3. newtype n operators make!: *integer, out integer -> 
integer; endnewtype;
4. newtype n endnewtype n; external 'C';     also for syntype
1005982 (Windows only): When using the Ctrl-F feature in the SDL editor to search for text in symbols now (in 4.2.3) all characters can be used in the search.
1006210: Tidy up on diagrams with create line fails. This is solved in 4.2.3.
1006211: When opening the same diagram in two windows and doing Revert the editor can crash in certain situations.This is solved in 4.3.
1006978: The option 'Detect Moved Symbols' has been misleading in the Compare and Merge dialogs. The text has been changed in 4.3 to 'Find difference groups using object ids' to better reflect the functionality.
1007002: The mismatch warning when copying pages from one diagram to a diagram of a different type has now less lines. On Windows all the text in the message was not shown. This is solved in 4.3.0.
1007129: In the SDL editor when comparing two diagrams the editor exits unexpectedly if the window showing the Source 2 diagram is closed and then the compare operation is chosen again and the window showing the Source 2 diagram is closed again. For some other operations similar to this the editor might crash. This is solved in 4.3.0 by not allowing any menu commands when the compare or merge dialog is used. However it is still possible to edit the diagrams and scroll the windows.
1007462 (Windows only): On Windows, the symbol menu and symbol text windows now in 4.3 show the correct title.
2001518: When using the name ABC_ (without a following newline) in a reference symbol an empty name will show up in the Organizer. This is solved in 4.3.0.
2001608: When merging two diagrams the additional heading text and the package reference text did not appear in the merged diagram. This is solved in 4.2.3.
2001520: The red line marking syntax errors now in 4.3 works correctly after pasting a reference symbol that is duplicated. The red underline now also works correctly for text extension symbols.
3001120: In a text symbol the correct syntax below was marked with the red line as being wrong in the SDL editor. This is solved in 4.3.0.
SYNTYPE test = integer 
      CONSTANTS (Val1):(Val2) 
ENDSYNTYPE;
 
3001126: When doing a merge and the two diagrams do not have the same position of the frame, the merge does not detect all symbols. This is solved in 4.2.3.
A single note in a task with the characters "<underscore><newline>" inside the note was marked as bad syntax and the PR produced were not correct. This is solved in 4.3.0.
When resizing a symbol in a process diagram the symbol will now in 4.3.0 always be horizontally centered. Thus for example when resizing the right bottom corner the left side of the symbol will also be resized to keep the symbol as a whole centered.
SDL Simulator

1005468: Problem with reception of an empty SEQUENCE. This is corrected in 4.2.2.

SDL SimUI / ValUI

1006032: When using a button file in the SimUI / ValUI any line length is now (in 4.2.2) allowed.

SDL Simulator

1005363: Reading optional components in structs do not work correctly. This is corrected in 4.2.1.
1006588: If your SDL system contains more than one entity with similar names in one scope and another entity also with similar name in another scope, the simulator will sometimes crash. This is corrected in 4.2.4.

SDL Target Tester

1004520: Misleading text in `Set Timer' message box. This is corrected in 4.2.1.
1004912: Incorrect semantics in generated MSC PR. This is corrected in 4.2.1.
1004986: Incorrect MSC trace for signals with complex parameters. This is corrected in 4.2.1.
1005283: The SDL Target Tester crashes while exploring the SDL queue. This is corrected in 4.2.1.
1005394: The SDL Target Tester crashes while tracing implicit consumption of timer. This is corrected in 4.2.1.
1005582: Help command in command line writes lines multiple times. This is corrected in 4.2.2.
When sending messages with parameters to the target via the target tester the parameters are not correctly received on the target. This is corrected in 4.2.2.
Problem with "not used" file for all Gateways. This is corrected in 4.2.2.
Communication trace in all gateways is fixed and conform is available via Gate parameter 3. This is fixed in 4.2.1.

SDL Validator

1005363: Reading optional components in structs do not work correctly. This is corrected in 4.2.1.

Targeting Expert

1004869: Obsolete flag `XMK_ADD_TEST_OPTIONS' in Cmicro integrations. This is corrected in 4.2.1.
1005176: Settings for `Compile as C++' and `Compile as debug' are not saved correctly. This is corrected in 4.2.1.
1005123: Selecting multiple integration with the Integration combo box may cause incorrect tools to be launched. This is corrected in 4.2.1.
1005302: The SDL Analyzer option `Case sensitive SDL' is overridden by the Preference setting `SDT*CaseSensitive'. This is corrected in 4.2.1.
1005373 (HP only): The compiler and linker options are not correct for use with the coder library. This is solved 4.2.3.
1005901 (Japanese version only): The Analyzer messages are not displayed correctly. This is solved in 4.2.3.
1006396 (Cmicro only): The environment file generation do not use the correct .ifc file if full separation is selected. This is solved in 4.2.3.
3001020: The use of merged ASN.1 modules is not possible. This is corrected in 4.2.2.
3001091: The parameters of the THREAD command sent to the SDL Analyzer if doing a Threaded Light Integration are in the correct order now. This is fixed in 4.2.3.
When deleting an integration in the PDM tree of the Targeting Expert UI, the tool sometimes crashes. This is corrected in 4.2.2.
(HP only): The generated makefile is incorrect if coders are used. This is corrected in 4.2.1.

Tight Integration

1004471: Illegal memory access in the VxWorks Tight Integration when SDL create is used with parameters. This is corrected in 4.2.2.
1006771: Problem with generation of SDL-coder-buffers. This is solved in 4.2.4.
1006779: In 4.2.4, if full separation is selected procedures are no longer separated.
1007013: Incorrect handling of the SDL Analyzer Filter command. This is solved in 4.2.4.
3001078: Remote procedure calls from inherited process types. This is solved in 4.2.3.
3001122: Missing #ifdef XFREESIGNALFUNCS in scttypes.h. This is solved in 4.2.3.
3001135 (Solaris and Win32 Tight Integration): Compile errors due to a process creation in a procedure. This is solved in 4.2.3.
3001378 (Windows only): The Targeting Expert crashes during startup if the limit of available license is reached. This is solved in 4.2.4.
Incorrect handling of H2SDL options. This is solved in 4.2.4.
Max amount of bytes of message length allocated for every signal sending in VxWorks Tight Integration. This is solved in 4.2.3.

TTCN Suite corrected errors

Defcon Utility

1006020: When generating constraints by the use of "defcon", the depth of the number of SEQUENCE/CHOICE that could follow a variable in a constraint was limited. The allowed depth is now increased.

GCI / EGCI API

The EGciGetMemberByName function can not be used to extract members in a CHOICE. This is corrected in 4.2.1.
The timer identifier semantics was changed in the 4.1 release. A timer instance is only unique within its component. The GciGetTimer function, looking up timer by index, is not properly updated. Now (in 4.2.1) it uses the currently active context as scope when indexing timers.
The GciLog function changed prototype for the log identifier from int to GciLogValue which is an enum. This was a change to the standard GCI prototype and has now (in 4.2.1) been changed back to int.

Test Execution

Temporary memory handling was not correctly implemented. In 4.2.1 a stack-based strategy is used. This could potentially result in all different sorts of problems during behavior execution.
IMPLICIT SEND is not logged. This is corrected in 4.2.1.
Matching of SEQUENCE OF when matching constraint that contains ANYORNONE elements has been implemented in 4.2.1.
Logging of values containing InsteadOf values has been improved in 4.2.1.
SEQUENCE OF and SET OF values are now (in 4.2.1) indexed from 0 (zero). The access to elements of these values was erroneously generated as 1-based, causing the generated code to access wrong elements and causing internal error.
Constraints was always allocated in temporary memory due to the assumption that constraint are only created in the dynamic part, in behavior lines. The usage of constraint values as values to constants, variables, etc., required that constraints could be allocated in permanent memory in the respective context. This is corrected in 4.2.1.
Handling of explicitly omitted value has been improved in 4.2.1. This includes OMIT values as arguments to constraints, Test Steps, etc.
Copying of ENUMERATED values now (in 4.2.1) works correctly.
Equality of INTEGER values now (in 4.2.1) works correctly.

TTCN Access

1000545: Launching ITEX-Access application from Organizer does work. This is solved in 4.2.3.
1004730, 1005997: The Access applications has the same global names that are present in our library. Now (in 4.2.3) all these generated files are converted and prefix ts_ is added to the names.

TTCN Analyzer

1002445: The Analyzer now detects when a Meta-PDU is used in either comparisons or in rvalue in assignments, if lvalue is not a Meta-PDU.
1005183: A crash scenario caused by a constraint with object reference that has a component list. This is corrected in 4.2.1.
1005224: Improved check, by the Analyzer, of parameters in a CREATE statement.
1005342: Analyzer is now able to resolve circular dependency in error checking. It is not allowed for test steps and local trees to call itself recursively (directly or indirectly) on top level i.e. at indentation depth 0. The Analyzer now (in 4.2.3) checks this.
2001413: The Parameter Type (PCO) has improved check by the Analyzer.
3001032: A previous crash experienced during analysis of a test suite with constraint that called a TS operation with parameters, is solved in 4.2.4.
3001181: Reference to a Test Case, from another test case caused a crash. An attachment to a Test Case is not allowed according to the standard. Previously, the analyzer detected an attachment to a Test Case, except for the case when it referred to the Test Case itself (Circular dependency). In 4.2.4, the Analyzer detects all references to a Test Case.

TTCN Browser / Desktop

1000545 (Windows only): When selecting a TTCN document in the Organizer and choosing Access... in the Tools/TTCN menu, selecting a TTCN Access application and pressing OK, the user now (in 4.2.4) correctly get a DOS shell to pop up, showing the execution of his TTCN Access application.
1001293: Now, on Windows 2000, the TTCN Browser does popup on top (in focus) of the Organizer. Previously the Browser started behind the Organizer.
1004048: The problem with slow editing of a large constraint is improved.

A new TTCN Suite functionality is added so that changes in a table are not saved immediately. The save command performs after the time set by environment variable ITEX_TYPE_DELAY_TIMER_RATE or when the editing field loses its focus. The delay of the environment variable ITEX_TYPE_DELAY_TIMER_RATE is set in milliseconds. The default value, if the variable is not set, is 2000 (2 seconds).
1004614: The TTCN table and tree titles are updated after they are created.
1004788: Previously an error message was given, when a non-root TTCN document in the Organizer was removed, and there, at the same time, where another TTCN document of the same subtree opened. This is solved in 4.2.3.
1004790: Previously, when removing a root TTCN document and setting "Keep sub documents as new roots" an error message appeared. This is solved in 4.2.3.
1004982:When several Undo commands are pressed, the table where the undo is being performed is placed in focus.

Note: If the ITEX_TYPE_DELAY_TIMER_RATE (described in case 1004048) is not set, the default value is 2000ms. Each Undo will remove what is typed within a period if these 2 seconds. In order to remove each symbol typed, reduce the value of ITEX_TYPE_DELAY_TIMER_RATE.
1004988: When, in the Browser window, changing the name of a table, the parameterized variables associated to that table will be kept.
1005013 (Windows only): Trying to open a disconnected node document causes the tool to crash. This is corrected in 4.2.1.
1005228 (Windows only): The tool crashes when trying to delete a table that is open. This is corrected in 4.2.1.
1007306 (Windows only): It is now (in 4.2.4) possible to save itex- and mp-files in the root directory.

TTCN Co-simulator

1002331: The decoding of omitted values is improved in 4.2.1.
1005920, 2001374: A problem when running target/standalone simulator with concurrent test components has been fixed. The problem occurred when a parallel component was created.
1006290: Problem with reading of BOOLEAN PIXIT parameters during co-simulation is solved 4.2.4.
1007256: In 4.2.4, the output in simulation will show the name of an ENUMERATED instead of the value.
3001157: Problem when using enumerated types with same literals in simulation is solved 4.2.4.
The decoding of CHOICE values used in SEQUENCE OF constructs is corrected in 4.2.1.
Logging of decoding failure during co-simulation is improved. In 4.2.1, the offending signal from the SDL Simulator is logged.

TTCN to C Compiler
1003048: The support for IF_PRESENT in constraints has been added in 4.2.1.
1005171: IMPLICIT SEND statements are now logged in the conformance log.
1005925: Parameters to local test trees were not handled properly. Any enclosing formal parameters (parameterized Test Step of Default) is now (in 4.2.3) added to any declared Local Test Steps parameter list. Since Local Test Steps are generated as separate functions and can use parameters from the enclosing scope this is necessary.
1005926: A previous problem, when using constraint as value for a Test Suite Variable, is solved in 4.2.3.
1005961: In generated code, references to field of the received ASP are made by mean of VcGetMemberByName function could cause problems. By the work done, it is possible to set the name and type correct into the value that is build (this is done recursively through the whole value). It is supposed to look like this:
GciValue *result_value = EGciMkValue(type_id);
EGciAssign(result_value, decoded_value);
return result_value; 
1006044: IF_PRESENT now do matches if a NO value arrives on the PCO.
1006208: Now, TTCN Suite generates indexed access instead of by name when evaluating assignments to/from the receive/send object

The matching for SEQUENCE in combination with OMIT and IF PRESENT is improved.

IS PRESENT has been fixed to check for OMIT status.

Assignment to fields with Meta-PDU type now keeps the original name setting.
1006707: A problem that occurred when a TS Parameter is used in a SIZE restriction for a string type is solved in 4.2.4. A padding scheme is applied and a run time context is implemented in order to accessing the TS Parameter.
1006710: The largest positive number using a 32 bit signed integer is 2^31-1 and the smallest negative number is -2^31. The handling of -2^31 (only) previously caused a problem. This number is now (in 4.2.4) implemented in a correct way.
1007255: It is now (in 4.2.4) allowed to select member of a CHOICE value even after the value was instantiated with another member of CHOICE (this will delete previous value).
1007259: The output in the Log Manager now (in 4.2.4) says "Telelogic AB", when generating code.
1007292: Problem with READTIMER and GciReadTimer() is solved in 4.2.4.
1007323: Minor problem with EGciSetNULL and GciGetNULL is solved in 4.2.4.
2001340: The GciGetTimerName function has been corrected since it returned the wrong name for the given timer identifier.
2001360: A timer instance for a specific timer has different identifiers in different components. Now in 4.2.3, it is implemented so the currently active component will be used to map to a unique id.
3001110: A problem with code generation, when using formal parameters as ConstraintRefs, is solved in 4.2.4.
3001153: The INT_TO_BIT functionality is now (in 4.2.4) implemented in a correct way.
3001640: An error when re-assigning a CHOICE value to another selected field has been corrected in 4.3.0.
3001644: An EGciRmValue function has been added in 4.3.0, as an option to free memory associated with the GciValue.
Problems with running test using concurrent test components. The implementation is improved in 4.2.1.
Unsupported features like REPLACE BY, SELECTION values and REAL types and values are now (in 4.2.1) detected in the early stages of code generation. If such constructs are encountered, proper warnings are made and code generation will terminate.
Test Suite Parameters could not be used for type restrictions. The generated type check functions are now (in 4.2.1) able to look up these constants in the appropriate run time context.
In 4.2.1, ASN.1 Type By Reference ASN.1 and TTCN names do no longer have to be the same in order to make our generated BER/PER encoders/decoders work.
Known software errors in 4.3.0

SDL Suite and TTCN Suite common tools known errors

General

Not all tools are able to handle file names with spaces, such tools are Simulator/Validator, H2SDL, CIF tools and ASN.1 to SDL tool. It is not possible to start the Organizer by double-clicking on a file name that contain spaces.
The function "frequency logging" does not work in Windows.

Organizer

(Windows only) The Archive commands Pack and Unpack does not work on Windows NT or Windows 98. For Windows 2000 it might work but the functionality is unreliable.

ASN.1 Utilities

Undefined components of OBJECT IDENTIFIER are not reported.
Predefined OBJECT IDENTIFIER components have no value in SDL.
When we use PermittedAlphabet constraint for some string type, and then assign Tuple or Quadruple, which is out of constraint, no error message is reported, for example, T ::= IA5String ( FROM ( "a" | "b" ) ) t2 T ::= { 1,1 } does not produce any messages.
Values for integer types with constraints outside the range of 32 bit integers, cannot be handled correctly.

ASN.1 BER/PER Encoding/Decoding
Empty SEQUENCE has no values in SDL. Consider the following example:
T1 ::= SEQUENCE {}
v11 T1 ::= {}
this is mapped to the following SDL:
newtype T1
endnewtype;
synonym v11 T1 = (. .);
The SDL type T1 do not have any values and the synonym will not be accepted by the SDL Analyzer. When mapping WITH COMPONENT constraint to SDL inline types are created on fly, information about them is not stored in the internal ASN.1 representation and type structures for those inline types are not generated for encoders/decoders generation request. This will produce compile errors for C code generated from the SDL package when Encode and Decode operators are generated for SDL types, because they will reference type information that does not exist.
ASN.1
  T1 ::= SET OF INTEGER
  T2 ::= T1 ( WITH COMPONENT( 0 .. 5 ) )
generated SDL
newtype T1
  String (Integer, emptystring)
endnewtype;
 
syntype T2 = T2_INLINE_0 endsyntype;
newtype T2_INLINE_0 /*#SYNT*/
  String (T2_INLINE_1, emptystring)
endnewtype;
syntype T2_INLINE_1 = Integer constants 0 : 5 endsyntype;
Information about T2_INLINE_0 and T2_INLINE_1 is generated only to SDL and is not generated to type structures for coders.
Simple workaround is not to use WITH COMPONENT, but create a new type which will be used in SET OF type:
  ConstrainedINTEGER ::= INTEGER ( 0 .. 5 )
  T1 ::= SET OF INTEGER
  T2 ::= SET OF ConstrainedINTEGER
TTCN generator: Automatic tagging is not mapped correctly to TTCN. When automatic tagging is applied, all implicit automatic tags are mapped as explicit to TTCN, because there are no means to define automatic tags for TTCN ASN.1 types. In ASN.1 automatic tagging assume IMPLICIT type of tags, but when mapped to TTCN this information is lost, and tags are treated as EXPLICIT.
M
DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
S ::= SEQUENCE {
        x BIT STRING,
        y INTEGER
}
END
Types for fields x and y should have [1] IMPLICIT and [2] IMPLICIT tags after automatic tagging.
mapped to TTCN
S ::= SEQUENCE { 
        x [0] BIT STRING,
        y [1] INTEGER
}
Tags for fields x and y are EXPLICIT by default, which is not consistent with ASN.1 semantics.
This problem does not influence the encoding and decoding because tags are extracted from the generated type info for each type, which is correct, and not from the TTCN internal type description.
Doors integration

(Windows 2000 only) The SDL Suite - Doors integration will lock up when trying to save a link (.sli) file during the initial connect/synchronize to the currently loaded SDL system in the Organizer, if the link file is to be created or is write protected.

Workaround: Either ensure that you have a readable .sli file connected to your system or start the connection between DOORS and Tau by starting the synchronisation when Tau is not executing (then you have to select the .sdt file for the system which you want to connect to).

Java Interface

In the file postmaster.java, line 53, you must change the string "libsdtpost" to "sdtpost" before compiling. Additionally you must change the name of the library on Windows, not UNIX, from libsdtpost.dll to sdtpost.dll.

Microsoft Word Integration (Windows only)

When the cursor is placed directly after endpoint text, and you add some characters, they will not become part of the endpoint text, even though the character format will indicate so. (Word95 only)
When you add/remove a link between two endpoints belonging to documents loaded in MS Word, only one of them changes character format.
There is a problem with MS Word files that resides on a mounted file system. When opening such documents from MS Word they are notified (with the full path) as opened to the Organizer. If the source directory in the Organizer is given with a drive letter, the Organizer cannot determine that the file belongs to the SDL system and consequently the file is not marked as open in the Organizer. (Word95 only)
Work-around: Open MS Word files from the Organizer.

Print

Generated pictures are sometimes incorrectly scaled when printing to Microsoft Word 97.

Workaround: Install at least SR-1 (Service Release) of Office 97.

Defect 10216: The lpr.exe print command on Windows does not work for MSC diagrams that contain long text strings (more than 100 characters), e.g. long instance names or parameter lists.
All used colors are displayed as white when using the option WebPrint on UNIX.

Text Editor

When you deselect text in the Text Editor on UNIX, endpoints fail to redraw endpoint underlines under the selection.

Work-around: Use <Ctrl-L> to redraw the text after deselecting a selection covering endpoints.

SDL Suite known errors

Cadvanced / Cbasic SDL to C Compiler
Combinations of component selections sometime give C compilation errors. Assume the following types in SDL:
newtype s struct
 a, b integer;
endnewtype;
newtype t string(s, empty)
endnewtype;
dcl v t;
When now the following two level component selection is performed:
 v(2) ! a
i.e. select struct component a in the second string component a compilation error might occur, as the string component selection must be performed using a function, while struct component selection can be performed using standard C ".". The generated C code will thus look something like:
 Extr_t(v, 2).a
The problem is that not all compilers accept component selection on a function result.
A suitable work around is perform the component selection in two steps:
 tmp := v(2),
 x := tmp ! a;
Cmicro SDL to C Compiler / Cmicro Library

The SDL to c compiler generates superfluous macro calls in the parameter list for operators defined in SDL. These macro calls will cause compiler errors. This only affects tight integrations.
If undefining the flag XMK_USE_RECEIVER_PID_IN_SIGNAL it is not possible to use xRouteSignal() function in any case.

CPP2SDL
When using the option "Recognize SDL sorts in input", the CPP2SDL translation of predefined SDL types is inconsistent with the naming of these types in the predef.sdl file.
Work-around: When using case-sensitive analysis in SDL define the following syntypes in the SDL system.
syntype Bit_String = Bit_string
endsyntype;
syntype Null = NULL
endsyntype;
syntype Object_Identifier = Object_identifier
endsyntype;
syntype Octet_String = Octet_string
endsyntype;
syntype PId = Pid
endsyntype;
If, on Unix, the CC or cc compiler is used for preprocessing the input to CPP2SDL, and messages are output during preprocessing, these messages will be present in the preprocessed file. This could lead to problems when this file is translated to SDL.

Work-around: Make sure that no messages will be issued during preprocessing by first preprocessing the files from the command-line.
Tagged types, where the name of the tag is the same as another declaration in the same scope, are not handled in an acceptable way. There will be errors when the generated code is compiled.
Example:
struct S {

};

int S;
Work-around: Change the name of either the tag or the other declaration.
Overloading on the dereference operator (*) is not correctly handled by the Code Generator.
Complex combinations of pointers and multi-dimensional arrays are not correctly handled by the Code Generator.
The Simulator will not be able to simulate an SDL system that uses a C++ class with public members that are inherited from a base class with virtual inheritance. However, application generation for such a system works.
In Windows, CPP2SDL sometimes reports syntax errors in the preprocessed file rather than in the header file. Such an error message is therefore not navigable from the Organizer Log.
H2SDL

H2SDL does not correctly translate function prototypes with parameters of function pointer type.

MSC Editor

Defect 9258: When you decompose an instance that contains syntax errors (shown by a red line), the syntax errors will not be visible in the decomposed diagram before you move or edit that symbol.
Defect 9284: If you copy a lost/found message and paste it into an empty diagram, you get an "Clipboard empty" dialog. This error message that means that the contents of the clipboard could not be pasted, in some cases this is due to the fact that the clipboard really is empty, but in this case the contents of the clipboard can not be pasted, since there is nothing to connect to. The big problem in this case is that the symbols are pasted anyway (after you press OK). If you don't remove (delete) these symbols immediately, the editor may crash.
Defect 10149: If you use the "Edit | Make Space..." command with a value larger 100 or larger the symbols below your selected object will "disappear". The error occurs, since only one page is added to the diagram. You can reclaim your symbols by increase the diagram size with the "Edit | Drawing Size..." command.
Defect 13737: If you are running the MSC Editor Standalone (i.e. not started from the Organizer), the changes you make in the Organizer takes no effect automatically. In order for the changes to take effect you have to copy the sdt.ini (on Windows) or .sdtpref (on UNIX) to the directory from where you are starting the editor in order for the preferences to take effect. E.g. if you are want to try out the example in the msctrace directory, you should copy the preference file to the <install dir>/examples/msctrace/<platform>.
When opening an MSC PR file in the MSC Editor all the notes ( /* ... */ ) written in PR will be lost when the diagram is converted to MSC GR.
Sometimes lines or symbols might get unconnected. If you experience this problem in some rare case, you should proceed as follows to avoid a crash: Try to drag the symbol or the (end of) the line so that it gets reconnected. If you succeed with this everything is fine again. What you definitely should avoid is to delete the symbol that the "unconnected" symbol or line was connected to before getting "unconnected", since if you then move the "unconnected" symbol or line, the editor will crash.
When generating Encapsulated Postscript files (EPS) for multiple page Message Sequence Charts, only one file is generated containing the last page of the MSC.

OM Editor

If you have changed the name of a symbol with an endpoint, it will not be updated in the Link Manager if you exit the OM Editor before you deselect the symbol.

Work-around:

Select Check endpoints in the Link Manager.
Open the diagram in the OM Editor again.

When you print with a larger scale than 100%, the printout may cut off the vertical right part of the frame if the frame coincides with the page border.

Work-around: Decrease the Right margin in the Print > Margins sub-dialog.

Preprocessing during Make
Windows 95 - Borland only: During make and using the feature "Preprocess C file".
If the allocated space for environment variables is insufficient the following message appears in the log.
****** WARNING ******
$sctdir\sccd.cfg$SCTDIR\sccd.cfg does not exist; Using internal defaults.
.
Error: Could not find file 'sccdtmp\<system-name>.i'
To adjust add or change if existing the following line in Config.sys
shell=<W95-Install-Path>\command.com <W95-Install-Path> 
/E:<new env. value> /P
Adjust <new env. value> as needed. Example:
shell=C:\WINDOWS\command.com C:\WINDOWS /E:1024 /P
SC to SDL converter

Converting SC to SDL, does not work unless case sensitivity in SDL is set to OFF.

SDL Editor

1003008, 1006262: Editing Reference symbols:

When changing the name of a reference symbol and directly after the editing clicking in the symbol but outside the text will not update the name change in the Organizer.
Work-around: After editing the text in a reference symbol always click outside the symbol when deselecting the text.

Text outside drawing area:

If you type a lot of text in an object or if you open a diagram and the font that is used is larger than when the diagram was last saved, the text may flow outside the drawing area. This is visible if the text appears to the right or below the bottom of the drawing area, and the whole drawing area is visible in the window.

Connect to Text Editor:

When you select Connect to Text Editor - to edit object text in another text editor - and then exit the Organizer before you exit the Text Editor, a number of error messages may be displayed.
Work-around: Close the Text Editor or the SDL Editor before you close the Organizer.

The preference Editor*GateSymbolColor is ignored by the SDL Editor.

SDL Index Viewer

The normal search function in the Index Viewer can in some situations not find all occurrences of a text string.

Work-around: Make sure that no symbol is selected before the search begins or use the fast search function instead (by just typing on the keyboard when the Index Viewer window is in focus).

SDL Info Server

The SDL Info Server is used by the Signal Dictionary in the SDL Editor and the Type Viewer.
The SDL Info Server does not handle the new preference: SDT*CaseSensitive.
When using the Signal Dictionary, the SDL Info Server is not able to find signals sent in algorithms in task-symbols. E.g.:
task {if (IsCorrect)
  output ok;};
Here the signal ok will not be found.
The following examples will not the SDL Info Server be able to parse:
newtype a inherits b
operators
putbits: W -> W;
endnewtype ;
The following is OK:
newtype a inherits b adding
operators
putbits: W -> W;
endnewtype ;
SDL Simulator

Transitions in global procedures are not handled in coverage table.
Undo does not work correctly if the system contains external synonyms.
Undo does not work correctly if Define-Continue-Mode is set to `On'.

SDL SimUI / ValUI

When you simulate or validate in the UI and regenerate the running simulator/validator in the Organizer and then choose select Restart in the UI, the UI might hang.
If compile and link fails in Windows 95 when you generate a simulator, the UI will be started anyway. The reason is that the command.com shell does not propagate the exit code. This applies to the validator as well.
Quotation marks that are not within a string is consumed by the UI. So e.g. patterns in Validator commands can only be enclosed in apostrophes.

SDL Validator

Transitions in global procedures are not handled in coverage table.
Time syntype in SDL system leads to compilation error for xEq_SDL_Time

Work-around: Do not use syntypes of time.

Faulty behavior if queues are added to channels to or within block instance sets with the Define-Queue command.
ANY in an expression is deterministic. Only one result is given.

Work-around: If possible, use ANY in a decision instead. The Validator will then explore all the decision alternatives.

The MSC trace of input none in the Simulator is output of none with no input. This type of MSC cannot be verified in the Validator. In the Validator there is no trace of input none.

Work-around: Remove them manually.

MSC verification of block instance sets is not correct. The Validator cannot differ between signals sent from environment to one specific instance of the block type.

Targeting Expert

Windows only: The Targeting Expert will not work if the Tau installation is done in a directory path containing spaces.
Target directory structure ...

... is not updated correctly if an SDL system (.sdt) file contains several SDL systems and the order of the systems is changed (or a new system is inserted between existing systems).
... is not set up correctly if working in one target base directory using several different SDL system (.sdt) files.

When building a Threaded Light Integration for OSE with the coder library, a linker error may occur (efs_stderr not found at linking).

Work-around: Change the linking order in the generated makefile so that the OSE libs are linked in after the coder library.

Target Simulation

In Windows 95, remote target simulation does not work as described in User's Manual. The host part does not execute properly.

Target Tester
1007951: 'Break All' break points are not triggered.
If 'Allow large signal parameters' for the target library, the MSC trace is wrong (the output of the signal containing the large signal parameter is missing). In addition you'll get the following error in the text trace:
**ERR: Unknown trace message cannot be converted

**ERR: to MSCE message. Message will be ignored.
Complex signal parameters may lead to wrong values in the trace.
Complex signal parameters may lead to wrong values in the trace.
The Target Tester sometimes cannot establish contact to the Organizer, although the Organizer is running. Start the Target Tester again, it always works in the second attempt.
UNIX only: The Target Tester cannot remove some temporary files below the /tmp directory accordingly in some machine configurations. The result is that /tmp contains many files called /tmp/.sdt.cmicro.*. It is possible to either remove the files by hand (rm /tmp/.sdt.cmicro.*) or to use the reset command from the Cmicro postmaster $sdtbin/sdtmpm -r). This problem has to do with Solaris 2.5, which contains a bug when socket connections are to be finished.
Threaded Light Integration

When building an OSE threaded light integration using the TCP/IP module, an include path is missing in the Targeting Expert.

Work-around: Add -I$(OSEROOT)/sfk-solaris2/std-include in the "Include" text box in the "Compiler" tab in the Targeting Expert.

TTCN Suite known errors

General

You cannot open or convert test suites in the 3.1 format in Windows. This is because there is no version of ITEX 3.1 for Windows. If you have ITEX 3.1 on UNIX, you should export the file to MP format and import it in Windows.
Directory list not updated on UNIX:

You can use a filter command in file selection dialogs to specify a new filter and update the file list. However, the directory list will not be updated. This means that if you recently created a new directory, it will not be visible.

MP file format problem:

When you import certain test suites from MP, there may be a problem with transferring the information (e.g. Description) in the overview tables to the tables in the dynamic part.
The TTCN standard allow path specifications to optionally include the suite identifier first. This has the unfortunate effect that if the test suite contains a top level group with the same name as the test suite there is, in general, no way of knowing if the first part of the paths is a group identifier or the test suite identifier.
ITEX assumes that if the first part of the path is equal to the suite identifier, it is the optional suite identifier and, when you import, strips it away. When you export to MP, it is always added to the front of all paths. That way ITEX is always able to import the MP files it exports. Note that ITEX v2.0 did not add the suite identifier at export, and therefore the problem described here may apply when you import MP files exported by ITEX v2.0.
The only remaining problem is importing test suites that have top level group identifiers that are equal to the test suite identifier without having the suite identifier prefixing all paths. You can avoid this problem by temporarily renaming the test suite to something unique before importing it into ITEX and then renaming it back when in ITEX.

Restructuring of the test suite can be slow on UNIX:

When you restructure a test suite on UNIX, by pasting or merging, it may take a while before the operation is completed. This is due to frequent check-pointing in order to keep the test suite consistent even if the operation would fail somehow.

ASN.1

ASN.1 X.683 is not supported in TTCN Suite 4.1.0.

On-Line Help

Viewer selection confusion on UNIX:

In the UNIX version, there are two separate ways to specify what application to use for displaying on-line help. You can either select it in the ITEX resource file or in the Preference Manager. If these are set differently, what application will be used depends on from where you invoke the on-line help first.

Table Editor

Typing problems in the Table Editor on UNIX:

If you start typing with very high speed in the Table Editor on UNIX, the text you typed may not appear correctly and you will be notified with a beep.
Work-around: Make a brief pause between typing the first and consecutive characters.

Handling of the tab character on UNIX:

You cannot type a tab character in the Table Editor. However, a tab character from an MP file will appear, but the width will be different in the Table Editor compared to the printout. When you convert a test suite from MP, you will be warned if tab characters are found.
Work-around: Remove tab characters from the MP file before you import it into ITEX.

TTCN Analyzer
Defect 4980: The analyzer will make an incomplete analysis when there is an empty behavior line following a (possibly erroneous) send or receive statement.
Confusing error messages:
When a problem with an ASP or PDU constraint's ASP or PDU type reference is discovered during analysis, the error message on the following rows often says something like:
The field name <- is not declared
You should ignore these kind of messages when the ASP or PDU type reference field has an Analyzer error message. On the other hand, if the ASP or PDU type reference field does not have an error message, you should examine the constraint and look for incompatibilities between it and the associated ASP or PDU type.
Type lookup:
Due to how the type lookup mechanism is implemented, the context where a type is referenced have to be seen before encountering the value to look up. This has the effect that constructs like:
[{a 2} = variable_with_sequence_as_type]
is going to fail looking up the type of the sequence value.
Work-around: Rewrite that construct to reference the variable first:
[variable_with_sequence_type = {a 2}]
References to named numbers:
References to named numbers from the same table that defines them is not supported.
Work-around: Define the type defining the named numbers in another table and have a symbolic reference to this type instead.
Example (part of a SEQUENCE):
  tag INTEGER {one(1), two(2), three(3)} (one | two)
would be changed to:
  tag IntegerNumerals (one | two)
where IntegerNumerals contain:
  INTEGER {one(1), two(2), three(3)}
Absent constraint references in behavior tables:

The Analyzer does not allow absent constraint references in the behavior tables when a send/receive statement is for an "empty" ASN.1 ASP. The Analyzer do allow absent constraint reference for an empty TTCN ASP though.

Local tree limitation:

The DataObjRef constructs (that is, x.y and x.[y]) are not allowed when applied to a local tree parameter (that is, x above is a parameter name). It is, however, allowed if applied to a test step parameter.
Work-around: Redefine the local tree as a test step instead.

ITEX does not analyze the "Type Encoding" field in "Simple Type Definitions" and the "Encoding Variation" field in "Structured Type Definition". These fields do not have any semantics in the current implementation of ITEX.
TTCN to C Compiler

Defect 6238: TTCN encoding definitions are not supported by the CCG. This is not considered an error, but rather a limitation.
In Windows 2000, it is not possible to compile with the Borland 5.02 compiler.
Code generated on HP 10.20 and 11.00 cannot be compiled with the compiler c89.

TTCN Co-simulator

Defect 5918: When doing TTCN-SDT real-time co-simulation, timers sometimes does not expire when they should.
Defect 6556: The TTCN Simulation kernel cannot encode OBJECT IDENTIFIER:s.
Defect 9122: On Windows NT platforms, manually sent signals to the TTCN Simulator at Simulator startup are not consumed properly.
Defect 10626: It is not always possible to compile a TTCN Simulator with MS Visual C++ 6.0 on Windows 95 platforms.
Defect 10764: CANCEL statements without parameters does not work in TTCN-SDL co-simulation with concurrent TTCN.
Aborting an TTCN Simulator run:

Aborting the execution of the TTCN Simulator when the SDL Simulator is running, will inhibit further communication. Always restart the SDL Simulator when you abort the execution of the TTCN Simulator.

TTCN Desktop / Browser

Defect 6882: On UNIX, the save dialogue is not always presented when the user closes a TTCN document that has been edited.
Defect 7175: When a simulator is running, the keyboard shortcuts for the browser menu commands are disabled. This is known from Windows 95 only.

TTCN Link

Defect 5224: Generated TTCN-Link executable built with the Borland compiler sometimes has memory leakage.

Test Execution

Copying of parent defaults in local test steps could cause a crash due to an algorithmic error in the implementation.

Known documentation errors in 4.3.0

SDL Suite

Bullet number 4 in "Installing the dongle and drivers" on page 37 in the Installation Guide should read:

If you are using Windows NT/2000 you need to install drivers from the included CD-ROM. The files are located in d:\FLEX\FLEXID8\WINNTDRV.

TTCN Suite known documentation errors

Test Suite Parameters
In a pixit-file, the variables declared are to be named according to the following list of predefined type names. The names showed are typed with respect to case and spelling:
NULL	 INTEGER	 BOOLEAN
BITSTRING	 HEXSTRING	 OCTETSTRING
NumericString	 PrintableString	 TeletexString
T61String	 VideotexString	 VisibleString
ISO646String	 IA5String	 GraphicString
GeneralString	 RTYPE	 SEQUENCE
SEQUENCEOF	 SET	 SETOF
CHOICE	 ENUMERATED	 OBJECTIDENTIFIER
UTCTime	 GeneralizedTime	 ObjectDescriptor
Undocumented limitations in 4.3.0

SDL and TTCN Suite known limitations

Doors integration

Filtering a formal module that is connected to a system file (.sdt) might give unintuitive results.

When filtering with "Any string or text attribute" DOORS sometimes shows sections that does not contain the text that is searched for. This has to do with the fact that DOORS also looks in the currently not shown attributes. E.g. if you have a system file in a directory named "demongame" and you set the filter to show strings or attributes with the text "demon", then all the items that were visible before will still be visible even if they do not contain the string "demon". The reason for this behavior is due to the fact that the SDL and TTCN Suite DOORS integration stores file references in the DOORS database that point to the relevant files. Since, in this example, the files are stored in a directory named "demongame" all items will have an attribute that contains the string "demon", so it will seem like the filter has no effect.

TTCN Suite known limitations

TTCN Browser / Desktop

1005047 (Windows only): When converting a file from MP format to TTCN/GR, files are named so that previous .itex-files, with the same name, are overwritten.

Undocumented changed functionality in 4.3.0

SDL and TTCN Suite changed functionality

Licensing with FLEXlm 7.2g

When running the SDL and TTCN suite applications and upon successful feature checkout, the license file location used for the checkout is stored and remembered for all future checkouts for products using the same vendor daemon. This may lead to checkouts from an unexpected license or license server, The information is cached in the registry on Windows and in $HOME/.flexlmrc on Unix.

To avoid this behavior set the environment variable FLEXLM_NO_CKOUT_INSTALL_LIC to 1. This can be set in the environment, or on Windows in the FLEXlm registry, or on Unix in $HOME/.flexlmrc.

SDL Suite changed functionality

CPP2SDL

When the Microsoft Visual C/C++ preprocessor is used, CPP2SDL now (in 4.3.0) sets an additional option to the preprocessor to specify the source file type. In C mode the option /TC is used, while in C++ mode the option /TP is used.

SDL Analyzer

In 4.2 the SDL Analyzer changed to give an ERROR for unconnected gates that should be connected to comply with Z.100. In 4.3.0, an environment variable named SDTSAN_WARN_GATE is introduced to give the possibility to revert the error to a warnings, thus making it possible to continue with code generation.

By setting the environment variable SDTSAN_WARN_GATE to any value the SDL Analyzer will give warnings instead of errors for unconnected gates that should be connected. This option is only provided for backwards compatibility and should not be used if possible.

The SDL output from ASN.1 Utilities is now put in a separate file. This means that if no changes are made to the ASN.1 source files the ASN.1 Utilities will not regenerate the SDL output thus saving time during analysis.

TTCN Suite changed functionality

GCI / EGCI API
The following EGCI functions have been added in 4.3.0:
Bool EGciGetAnyValue(GciValue *value);
Bool EGciGetAnyOrOmit(GciValue *value);
Bool EGciGetIfPresent(GciValue *value);
Bool EGciGetDefault(GciValue *value);
TTCN to C Compiler

The licenses needed during code generation have changed in 4.3.0. Now, the licenses needed are:

When generating code for Co-Simulation, only a Simulator licenses is required.
When generating code for Exerciser, only a Exerciser licenses is required.
For all other cases, a TTCN to C Compiler license is required.

The SHARED_MEMORY and FULL_ERROR_MESSAGES defines have been removed from makefile generation. Their default behavior has been kept and the semantics are `on' in both cases.

C / C++ type	SDL type
`SDL_Bit_String`	`Bit_string`
`SDL_Object_Identifier`	`Object_identifier`
`SDL_Octet_String`	`Octet_string`
`SDL_PId`	`Pid`
`SDL_Null`	`NULL`

Telelogic AB
http://www.telelogic.com

Telelogic Tau 4.3Latest news 2001-09-19

1. How to install a patch

2. Release 4.3.0

1 How to install a patch

Is your installation modified?

Files changed by patch installations

On Windows

On Unix

2 Release 4.3.0

Corrected errors in 4.3.0

SDL Suite and TTCN Suite common tools corrected errors

ASN.1 Encoding/Decoding Library

ASN.1 Utilities

Autolink

DOORS Integration

Help Viewer

Organizer

Organizer Log

Print

TTCN Link

SDL Suite corrected errors

Cadvanced / Cbasic Library

Cadvanced / Cbasic SDL to C Compiler

CIF / SDL Converter

Cmicro Library

Cmicro SDL to C Compiler / Cmicro Library

CPP2SDL

H2SDL

MSC Editor

OM Editor

SDL Analyzer

SDL Editor

SDL Simulator

SDL SimUI / ValUI

SDL Simulator

SDL Target Tester

SDL Validator

Targeting Expert

Tight Integration

TTCN Suite corrected errors

Defcon Utility

GCI / EGCI API

Test Execution

TTCN Access

TTCN Analyzer

TTCN Browser / Desktop

TTCN Co-simulator

TTCN to C Compiler

Known software errors in 4.3.0

SDL Suite and TTCN Suite common tools known errors

General

Organizer

ASN.1 Utilities

ASN.1 BER/PER Encoding/Decoding

Doors integration

Java Interface

Microsoft Word Integration (Windows only)

Print

Text Editor

SDL Suite known errors

Cadvanced / Cbasic SDL to C Compiler

Cmicro SDL to C Compiler / Cmicro Library

CPP2SDL

H2SDL

MSC Editor

OM Editor

Preprocessing during Make

SC to SDL converter

SDL Editor

SDL Index Viewer

SDL Info Server

SDL Simulator

SDL SimUI / ValUI

SDL Validator

Targeting Expert

Target Simulation

Target Tester

Threaded Light Integration

TTCN Suite known errors

General

Telelogic Tau 4.3
Latest news 2001-09-19