Statemate version 4.6.1.9 Release Notes

IBM Corporation
10 Mar, 2014

 

 

This file contains last-minute product information and updates to Statemate 4.6.1.9

It is divided into the following sections:


Description

For information about IBM Rational Statemate see the Rational Statemate Support overview web page.

 

System requirements

To run Statemate 4.6.1.9 you need:

Operating System

Required Software

Supported Compilers

Hardware

Solaris 5.10

OpenWindows

Sun Studio 12 Update 1
GNAT Ada gcc 2.8.1

sun4u sparc SUNW,A70
1 GB RAM
Approximately 500Mb free
disk space

Windows XP SP3
Windows 7

MKS XServer 8.6
MKS Platform
Components 9.4

Microsoft Visual C++ 2008, 2010

Intel® Core™2CPU, 2 GHz
Minimum 1 GB, recommended 2 GB RAM
Approximately 600Mb free
disk space

 

At the time of writing, the third party products tested with <productname> n.n are:

 

Compatible products

  • Adobe Acrobat Reader 6.0 or newer
  • CANoe V3.0
  • ClearCase V3.1.1
  • Continuous 4.5
  • DOORS 9.3, 9.4, 9.5 (Windows Systems)
  • dSPACE (models 1102 & 1103)
  • dSPACE ControlDesk 1.2 P2
  • FlexNet v 11.5.0.0
  • FrameMaker 7.0
  • PVCS Version Manager v6.7.00 (Build 894)
  • QNX V6.3.2
  • VxWorks: 5.4 (Tornado 2.0)
  • Word 2003
  • GNAT ADA version 2.8.1 (Solaris)

 

Installing Statemate 4.6.1.9

Before installing, it is recommended that you check in and unlock all configuration items in all workareas.
For more information, see the Statemate Administrator’s Guide and Statemate Installation Guide.

Download of electronic images

Statemate uses Telelogic Lifecycle Solutions licensing. - hidden
For more details about obtaining a license, please see “
TLS_licensing_guide”. - hidden
The file can be found on the distribution CD, under “
license_server_windows_1.3” - hidden
directory for Windows, and under “
license_server_1.3” directory for Solaris. – hidden
For download information, please view the Rational Statemate 4.6.1.9 download page.

The installation packages are available for download at IBM Fix Central.
Select these filters:

·        Product Group: Rational

·        Product: IBM Rational Statemate

·       Installed version: 4.6.1

 

Fixed Defects in this release

For information about the APARs fixed in version 4.6.1.9 see the Fix List for Rational Statemate 4.6 page.

What's new in version 4.6.1.9

  • General Enhancements
    • Statemate was enhanced to support MS Visual C 2010 with Windows 7.
    • Convert_wa was enhanced to check command syntax and parameters.
      Upon completion the tool reports count of deleted elements and converted expressions.
      The extension of the convert_wa mapping file was changed from doc to txt.
    • Statemate was enhanced to block usage of reset_element operator on context variables. In Workareas where such an expression already exists, database diagnostics will report an error.

  • CheckModel Enhancements
    • A new Check-model test was added under design warnings, to report a warning when MicroC code may not execute default transitions of parallel And-state components on the same step:
      "(C15011) And State component with entering reactions, causing delay of default transition step".
    • 2 new Check-model tests were added, to report inconsistent input/output of Data-store:
      "(C4149) Elements input to data-store that are not output".
      "(C4151) Elements output from data-store that are not input".
    • A new Check-model test was added, to warn when Arrays are referenced with indices of wrong type:
      "Elements containing wrong type Array indices".

  • Dataport Enhancements
    • A new function was added to Dataport API to check-out license once before a series of pm functions, and hold it until stm_finish() is called:
      stm_boolean stm_init_uad_for_pm(int *status).
    • The dataport function stm_check_out_item() was enhanced to overwrite a existing modified chart in the Workarea, if the variable STM_YES_TO_ALL is set to ON.
    • New Dataport functions were added to handle Use-cases:
      stm_list stm_r_uc_name_of_uc(char* pattern, int *status);
      stm_list stm_r_uc_synonym_of_uc(char* pattern, int *status);
    • New Dataport functions were added to handle Actors:
      stm_list stm_r_actor_name_of_actor(char* pattern, int *status);
      stm_list stm_r_actor_synonym_of_actor(char* pattern, int *status);
    • New Dataport function was added to retrieve enforced status of a scenario attribute:
      stm_boolean stm_r_uc_scen_attr_enforced(stm_id id, stm_attr_name st_attr_name, stm_name st_attr_val , int *status)

  • MicroC Enhancements
    • The MicroC Code generator was enhanced to comply with the Simulation's behavior and will not re-start an already running activity.
      The code generation for the start_activity_XXX macros will check if the activity is not started before re-starting it.

  • Doors interface Enhancements
    • A new variable setting is required for the DOORS interface:
      SET DOORS_VERSION=v.r.m.f
      The setting (commented) was added in run_stmm.bat.

  • MKS X-Server update
    • The MKS X-Server distributed with Statemate was upgraded to version 8.6.

 


Contacting Support

IBM Rational Software Support Communities

  • Visit the Rational Support Resources site.
  • Visit the IBM Support Portal to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.
  • Visit developerWorks to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community.

Helpful Hints For Obtaining Technical Assistance:

Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

  • What software versions were you running when the problem occurred?
  • Do you have logs, traces, or messages that are related to the problem?
  • Can you reproduce the problem? If so, what steps do you take to reproduce it?
  • Is there a workaround for the problem? If so, be prepared to describe the workaround.

If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.

Follow IBM Rational Client Support on Twitter | Facebook | YouTube | devWorks Blog