IBM Rational SDL Suite 6.3.0.4 Latest news

IBM Rational TTCN Suite 6.3.0.4 Latest news

IBM Corporation
November 06 2013

 

 

 

  

Whats new in 6.3.0.4

 

CR ID

Synopsis

Release Notes Text

TLOG#72218

support generating 64-bit applications 6304

  The support for generating 64-bit applications is added

TLOG#72517

3-way Merge - No space to insert difference

-Fixed the problem with connector line not copied to merged result diagram

 

 

Whats new in 6.3.0.3

Customer reported issues fixed in 6.3.0.3:

 

APAR Information

Call Ticket

Synopsis

Release Notes Text

PM60962

24005,019,866

Non-deterministic prefix for external types is no longer used by CMicro code generator causing compilation conflicts

Using several packages with imported C types could cause compile errors or warnings for conflicting variable, type or macro names, like these:

Pac1.h(422) : warning C4005: 'ySrtN_arr_32_int' : macro redefinition
Pac2.h(422) : see previous definition of 'ySrtN_arr_32_int'

Pac2_smc.obj : error LNK2005: _ySDL_arr_32_int already defined in Pac1_smc.obj
HelloWorld_smc.exe : fatal error LNK1169: one or more multiply defined symbols found

These problems could happen if different C header files imported to different SDL packages contain similar implicit array types, for example, int var1[32]; and int var2[32];

This problem has been fixed.


PM73469

52984,019,866

Multiple dynamic processes given same PID

During PId creation a global variable was referenced in a thread-unsafe style and sometimes this could lead to different created processes getting the same PIDs. This problem has been fixed and sctneutrino.h from RTOS integrations has been updated.

 

31378,140,702

Supporting the 64 Bit Integer values in TTCN Suite (TTCN2)

64bit integer support has been added to TTCN Suite runtime.
To enable 64bit integer support in TTCN Suite, you need to apply two changes to the default make process:
1) Add /DVC_INT64_SUPPORT to "Additional Compiler Options" in TTCN Suite "Build Options" tab
AND
2) Replace the default ttcnstatic library with 64bit ttcnstatic library.
Step 2) can be done in 2 different ways:
- EITHER replace the file in installation C:\IBM\Rational\SDL_TTCN_Suite6.3\itex\itexlib\wini386\ttcn2c\ttcnstatic.lib with C:\IBM\Rational\SDL_TTCN_Suite6.3\itex\itexlib\wini386\ttcn2c\ttcnstatic64.lib
- OR fix the generated Makefile for TTCN model to use another library for linking :
LFLAGS = /nologo /link user32.lib "$(STATICDIR)\ttcnstatic64.lib" /subsystem:console $(SIMULATOR_LIBS)

 

Whats new in 6.3.0.2

Starting with Rational SDL and TTCN Suite 6.3.0.2, Red Hat 4 and Solaris 9 are no longer supported.

Customer reported defects fixed in 6.3.0.2:

 

APAR Information

Synopsis

Release Notes Text


PM08964

The MSC editor hangs when merging MSC diagrams

When using instance heads inside inline expressions the MSC Merge can hang. This has been fixed now


PM16208

TTCN Editor crashes in Linux while doing a 'Generate Import'

This has been resolved in 6.3.0.2


PM20822

Signal dictionary font does not display properly

On UNIX the Signal Dictionary was using a font that is no longer delivered. Therefore the window appearance is now the same on both UNIX and Windows using the previous Windows behavior.


PM24010

SDL Editor is crashing once; a route is drawn and released in a interaction page

This has been resolved in 6.3.0.2


PM26712

NESTED RPC CALLS DO NOT RETURN CORRECTLY

For RTOS Tight Integration kernels, if a process is executing an RPC that has an internal state and another nested RPC is handled by that process, the return of the
original RPC does not work.
This problem has been fixed.


PM33072

'Data Abort' crashes while decoding recieved messages

PER decoder could result in 'DataAbort' crashes while decoding corrupt messages. This could happen in PERDecode function after we return to it with an error status.
This problem has been fixed.


PM34716

TTCN2 Crash when compiling Test Suite containing Large number of Type Declaration (from escalation TLOG#64776)

On Windows, code generation failed to do anything for big test suites containing large number of type declarations because of stack overflow for code generator.
We have fixed this problem by increasing the STACK size to 10000000 for ttcn2c.exe and iedit2.exe (both executables invoke code generation from ccg.dll, ttcn2c is called from command line, iedit2 invokes code generation from GUI).
If 10000000 is not enough, stack size can be set to a higher value by Microsoft Visual Studio utility "editbin.exe", for example:

editbin /STACK:20000000 <installation>\bin\wini386\iedit2.exe


PM36106

SDL suite freezes during a search/replace operation.

This problem has been fixed in the Organizer for version 6.3.0.2. When an object found by the Search operation has been manually edited it will no longer be possible to use the Replace button in the Search dialog.


PM36554

Error : Illegal start of HEX string during Co-Simulation

There was an error observed during the co-simulation. If a message sent from TTCN contains any Octet field, SDL binary will discard it.
This problem has been fixed.


PM37129

Execution Stops During Co-Simulation (escalation tlog#63968)

SDL - TTCN Co-Simulation may hang if the model uses timers with very small time intervals, less than 1/10000 sec. This problem has been fixed.


PM47169

Check for Use of GOTO

According to TTCN 2 standard [chapter 15.14 Labels and the GOTO construct]: A GOTO to a label may be specified within a behaviour tree provided that the label is associated with the first of a set of alternatives, one of which is an ancestor node of the point from which the GOTO is to be made.

The ability to disable the check for GOTO has been added. If there is an environment variable NOCHECK_GOTO set to any value, TTCN2 analyzer will not report "GOTO to this label isn't allowed" errors.


PM48459

TTCN generated code causes memory leak (esc TLOG#66261)

The TTCN Suite Methodology Guidelines documentation has been updated to clarify how to allocate memory for user defined TTCN operations.


PM50167

SDL Diff tool do not report on changed symbol sequence

When using Compare Diagrams in the SDL Editor together with the option "Ignore moved and resized objects", moved symbols having identical object IDs are not detected as being different. It might then happen that a semantic change will not be detected. This has been fixed in SDL Suite 6.3.0.2.

 

Whats new in 6.3.0.1

Now Windows 7 and Red Hat 5 are supported.

 

Call Ticket

Internal number

Synopsis

Release Notes Text

7013064

TLOG#28238

Telelogic ITEX 4.6 patch level 4 Problem with de-referencing members

Members de-referencing for SEQUENCE, SET, SEQUENCE OF and SET OF that are the InsteadOfValues was implemented.

4041596

TLOG#29869

Hanging due to Signals not consumed

The problem in TTCN Suite RTL, that may cause hang and then crash when not-defined value used as index of SEQUENCE OF, is now fixed.

1066081

TLOG#45646

RH5: Copy/paste of text on linux doesn't work.

On Linux RedHat 5 when editing text in the Editors the Paste command was not available. This has been fixed.

 

SDL#215

Explorer/validator uses double licenses when starting with tau -fg

On UNIX, if you start SDL suite with "-fg", e.g. "sdlsuite -fg" (to keep the program in the foreground) and then start the SDL Explorer UI and open the SDL Explorer binary it happened that two licenses are checked out. This has now been fixed such that only one license is used.

58916,SGC,724

TLOG#51136

Support for SDL suite and code generator on 64 bit Linux platforms

Support for 64bit Linux has been added to SDL Suite. All exes (both the tool itself as well as the generated code) are in 32-bit mode, so generated code is compiled using the 32bit flag.

71047,019,866

TLOG#52257

Entity class name identifiers for structures.

When the same name is used for the field in two different choice types, it leads to name clash in #SDL(name_of_choice_field) reference and result in incorrect system behavior.

This problem has been fixed.

 

#SDL(name_of_choice_field) may reference literals from implicit <choice type name>present type in target code which are used to check presence of choice fields.

In addition to the name clash between different choice types, there is also name clash between choice field and implicit literal from implicit <choice type name>present type.

To avoid these name clashes, the ability to qualify literals from implicit <choice type name>present type has been added, for example:

 

#SDL(<<PACKAGE Pac/TYPE ChoiceT/TYPE present>>name_of_choice_field), where "TYPE present" denotes implicit ChoiceTpresent type generated for ChoiceT.

 

Qualifier facility in #SDL directive has also been improved with ability to use FIELD as entity class qualifier,

which allows to point to a type in some structure or choice field. This is useful for inline types translated from ASN.1

(they get name with INLINE_<number> postfix where the number may change if ASN.1 specification is updated). For example, for the following ASN.1 type:

 

FrequencyInfo1 ::= SEQUENCE {

modeSpecificInfo CHOICE {

fdd INTEGER,

tdd INTEGER

}

}

 

choice type is defined inline and does not have a name. It will be translated to the following in SDL:

 

newtype FrequencyInfo1_INLINE_0 /*#SYNT*/ choice

fdd Integer;

tdd Integer;

endnewtype;

 

newtype FrequencyInfo1 struct

modeSpecificInfo FrequencyInfo1_INLINE_0;

endnewtype;

 

It is possible to use the name of the structure field to denote inline choice type and reference <choice type>present literals like this:

#(<<PACKAGE MyDefs/TYPE FrequencyInfo1/FIELD modeSpecificInfo/TYPE present>>tdd)

77948,019,866

TLOG#54781

Not possible to add parameters in redefined Process Type, but no error or warning for the redefinition

It is not allowed to add formal parameters in redefined/finalized process type, but no error or warning message is printed when formal parameters are defined there.

This problem has been fixed and now "ERROR 356 Formal parameter not allowed in redefined or finalized definition" is printed for redefined or finalized process type with formal parameters.

53637,999,866

TLOG#55130

Need elaborate description on the steps to build & run light integration.

The documentation has been updated

51698,999,866

TLOG#55131

Mismatch of the description and the snapshots in the help manual

In the SDL and TTCN Suite online help, in the section on Integration with Operating Systems some figures are shown from the Solaris platform but the description is aimed for the Windows platform. This has been fixed by updating the figures.

53636,999,866

TLOG#55132

Description of typedef of a structure is not syntactically correct in help

The documentation has been updated

53639,999,866

TLOG#55158

Code snippets of xInEnv, xOutEnv Function are not correct.

The documentation has been updated

 

Whats new in 6.3.0.0 IFix 1

No major new functionality has been added to this release.

 

Call Ticket

Internal number

Synopsis

Release Notes Text

2091643

TLOG#47144

Conflicts during compilation of Telelogic ASN.1 codecs

It has not been possible to automatically add custom prefixes or suffixes to the symbol names in the code generated out of ASN.1 modules.

This is fixed in SDL Suite 6.3.0.0-if1.

A new option is available in asn1util and in the Make dialogs in the Organizer and the Targeting Expert.

In the generated ASN.1 coder structures a specified prefix is added after the standard yASN1_ prefix, for example:

CHOICE_TYPE_DECL(EXTERN_INFO,yASN1_MyPrefix_NetworkAddress);

CHOICE_TYPE_DEF(GLOBAL_INFO,yASN1_MyPrefix_NetworkAddress,EXTMARKER_ABSENT,NONE_EXTMARKER, ... );

4056461

TLOG#47820

Faulty/unclear message when trying to install SDL-Suite in Program Files, Vista.

Now a check is performed during installation that there is no space in the installation path.

61079,019,866

TLOG#49961

Missing SDT-SDL-Coder License feature results in compilation error in Linux

When the SDT-SDL-Coder license FEATURE is missing and the Targeting Expert tries to build a system using SDL coder functions there was no error message shown indicating the missing license. This is fixed in 6.3.0.1.

61933,019,866

TLOG#50439

SDL suite should support calling of macro through macro keyword.

SDL Suite has been updated to allow macro calling through 'macro' keyword in task symbols. Textual macrodefinition can be inserted into any task symbol, it can contain only statements that are allowed for the task symbol (for example, x := x + 1;). Macros can be called through the 'macro' keyword inside text symbols.

78494,999,724

TLOG#51564

Is a length check performed on the data held by the parameter of the (PER) DECODE function.

A potantial problem in PERDecodePrimBIT_STRING function may lead to a crash during PER Decode.

 

Crash can happen when the buffer is broken or truncated and decoded length of the bit string is greater than the actual bit string available in the buffer, or when user append function is used to read another portion of data to decode.

 

This problem has been fixed.

68650,999,744

TLOG#51695

The "Simulate" Shortcut icon doesnot consider the Selected Standard Kenrel in Make Dialogue

On Windows the "Simulate" Shortcut icon in the Organizer did not consider the Simulation Kernel that was last selected in the Make dialog. It always chose the Simulation Kernel. This is fixed in 6.3.1.

42490,999,672

TLOG#51740

GciSnapshot function not called correctly

Now it is possible to use configuration with MTC component only.

72037,019,866

TLOG#52254

A variation is observed in the results of the Simulator UI command Output-To and Output-Via.

When using the Simulator with a system supporting signal priorities, sending a signal with the command "Output-To" would not deliver it to its receiver. This has now been fixed.

72034,019,866

TLOG#52255

Wrong signal names in generated code for remote procedure calls lead to compile and link error.

When using Targeting Expert to generate a threaded system with remote procedure calls, the signals used for the remote procedure calls would get their names wrong in the generated code, leading to compile and link errors. This has now been fixed.

71047,019,866

TLOG#52257

Entity class name identifiers for structures.

When the same name is used for the field in two different choice types, it leads to name clash in #SDL(name_of_choice_field) reference and result in incorrect system behavior.

This problem has been fixed.

 

#SDL(name_of_choice_field) may reference literals from implicit <choice type name>present type in target code which are used to check presence of choice fields.

In addition to the name clash between different choice types, there is also name clash between choice field and implicit literal from implicit <choice type name>present type.

To avoid these name clashes, the ability to qualify literals from implicit <choice type name>present type has been added, for example:

 

#SDL(<<PACKAGE Pac/TYPE ChoiceT/TYPE present>>name_of_choice_field), where "TYPE present" denotes implicit ChoiceTpresent type generated for ChoiceT.

 

Qualifier facility in #SDL directive has also been improved with ability to use FIELD as entity class qualifier,

which allows to point to a type in some structure or choice field. This is useful for inline types translated from ASN.1

(they get name with INLINE_<number> postfix where the number may change if ASN.1 specification is updated). For example, for the following ASN.1 type:

 

FrequencyInfo1 ::= SEQUENCE {

modeSpecificInfo CHOICE {

fdd INTEGER,

tdd INTEGER

}

}

 

choice type is defined inline and does not have a name. It will be translated to the following in SDL:

 

newtype FrequencyInfo1_INLINE_0 /*#SYNT*/ choice

fdd Integer;

tdd Integer;

endnewtype;

 

newtype FrequencyInfo1 struct

modeSpecificInfo FrequencyInfo1_INLINE_0;

endnewtype;

 

It is possible to use the name of the structure field to denote inline choice type and reference <choice type>present literals like this:

#(<<PACKAGE MyDefs/TYPE FrequencyInfo1/FIELD modeSpecificInfo/TYPE present>>tdd)

72039,019,866

TLOG#52302

Variation in the generated code w.r.t XTRACE when compared with SDL Suite 4.4 and 6.3 which leads to compilation failure.

Decision statements with argument of the same type in base and derived process types may result in the following compile error message:

error: structure has no member named `yDcn_somename'

 

The error occurs when decision in the base process type is simple (i.e. contains one branch with one case value, and one else branch), while decision in derived process type is not simple.

 

This problem has been fixed.

 

Whats new in 6.3

No major new functionality has been added to this release.

Problems solved in IBM Rational SDL and TTCN Suite 6.3

 

Call Ticket

Internal number

Synopsis

Release Notes Text

5018585

TLOG#32722

experiencing some problems with abbreviation facility included with simulator

Faulty error message "Name was ambiguous" for similar enum literals, like SCH_HD, SCH_HM, SCH_H (one literal name is a substring of some other literal names), has been fixed.

7020638

TLOG#36084

Capitalization in SDL Make

Compile errors for Lower case capitalization mode with ctypes package have been fixed. Messages like "ctypes.c(54) : error C2065: 'type_SDL_shortint' : undeclared identifier" are not printed any more.

4051741

TLOG#41345

How to get past redeclaration of global_namespace?

"Illegal redeclaration of name global_namespace" error that appeared when using several import specifications in one system has been fixed. Now, CPP2SDL tool appends the name of import specification to the name "global_namespace".

7029627

TLOG#44439

Problem to print PS files

When printing to Postscript files on Linux it can happen that the generated Postscript is not correct. The problem can appear when using tools to convert Postscript to pdf and the converter complains because fontnames are missing. This problem has been seen when using locales having UTF-8 fonts. This has been fixed in 6.3.0.

3041982

TLOG#45342

Support for Visual Studio 2008 for SDL Suite

IBM Rational SDL and TTCN Suite now supports Visual Studio 2008

3042046

TLOG#45378

Defect in the Help Manual regarding the supported compilers for Windows Vista

The problem in the user documentation has now been corrected.

3043229

TLOG#46610

Crash during co-simulation from batch mode (command line)

Crash when co-simulate executable built by VC8 in batch mode was fixed.

02971,140,702

TLOG#49543

Error : ERROR 261 Answers are not mutually exclusive

SDL Analyzer treated external synonyms without values as equal (for example, SYNONYM X Integer = EXTERNAL;) and if two or more external synonyms were used as decision answers, "ERROR 261 Answers are not mutually exclusive" was reported.

3041489

TLOG#44886

Unable to Generate Cextreme Code from Commandline using sdtbatch

Now it is possible to generate CExtreme code with the sdtbatch command by specifying options file in the command line.

 

 

Copyright IBM Corporation 2003, 2012.  All Rights Reserved.

U.S. Government Users Restricted Rights:  Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.