Chapter 4 The Reactis Top-Level Window

The next several chapters of this manual contain detailed descriptions of different components of Reactis. This chapter concentrates on the functionality available in the top-level window when Simulator is turned off, or disabled. Simulator is disabled when Reactis is first invoked; it may also be explicitly turned off by clicking button (window item 16 in Figure 4.1). Clicking button (window item 17) turns Simulator on; the functionality of the on mode is described in Chapter 7.

Figure 4.1: The Reactis top-level window.

4.1 Labeled Window Items

An annotated screen shot of the Reactis top-level window may be found in Figure 4.1. This section describes the functionality of the numbered items in this figure, while the section following discusses the workings of the pull-down menus.

The numbers below refer to the labels in Figure 4.1.

The model hierarchy panel shows the subsystems in the model and how they are related. Clicking the + to the left an item displays the subsystems of the item. Clicking on an item causes the diagram for the item to be displayed in the main panel (window item 2). Pressing the “F2” key causes the parent of the currently displayed system to be displayed. Hovering in the hierarchy panel over a child of the currently displayed system causes the child to be highlighted in the main panel.
Right-clicking on an item in the hierarchy panel causes a pop-up menu to be displayed with several disabled entries. These menu items become enabled when Simulator is enabled and are described in Chapter 7.
The main panel displays the current Simulink / Stateflow diagram. Double-clicking on a subsystem causes the subsystem to be displayed.
Right-clicking in the main panel brings up a pop-up menu. The entries in the menu vary depending on the location of the click and whether or not Simulator is enabled. The items available only when Simulator is enabled are described in Chapter 7. Many items enabled when Simulator is disabled are related to adding or editing Validator objectives. These operations are described in Chapter 9.
When right-clicking on a Simulink subsystem or Stateflow chart in the main panel, the resulting pop-up menu contains an entry Extract Subsystem. Selecting this item causes the selected subsystem and any components related to the triggering of the subsystem to be extracted from the model and inserted into a new model. Reactis may then be applied to the newly extracted subsystem. Usage of this feature is described in more detail below in Section 4.4.
Also, the menu resulting from right-clicking in a subsystem, Stateflow chart or block contains an entry “View Block Parameters.” Selecting this entry brings up a panel showing block-specific data similar to that available within Simulink.
When right-clicking on a data item (Simulink block or signal or Stateflow variable) in the main panel, the pop-up menu contains an entry Add to Test Points. A list of test points may be associated with a model, stored in the model’s .rsi file, and viewed from the Reactis Info File Editor. Test points are internal data items that Reactis treats as virtual outputs; specifically, the tool records values for test points in test suites and Reactis Simulator flags any differences between the values computed by a model for a test point and those stored in a test suite. For more details on test points please see Section 5.1.3.
When a diagram is too big to display completely in the main panel, scroll bars appear for repositioning the diagram. Alternatively the diagram may be repositioned by left-clicking and dragging in the panel or by using the cursor keys. If your mouse includes a scroll wheel, then you may scroll vertically by clicking in the main panel and then using the scroll wheel.
Left-clicking and dragging in the panel while holding down the control key defines a “print region” that can be used for printing parts of a model. The print region is represented as a shaded blue box; it may be removed using the File -> Remove Print Region menu entry or pressing the escape key.
Finally, clicking the F2 key within this panel causes the parent of the currently displayed subsystem to be displayed.
Load a new model into Reactis.
Undo an operation (add, edit, remove, move) on a Validator objective.
Redo last undone operation (add, edit, remove, move) on a Validator objective.
Cut the currently selected Validator objective from the model and place it in the clipboard.
Copy the currently selected Validator objective to the clipboard.
Paste a Validator objective from the clipboard to a default location of the currently displayed subsystem. Note that, alternatively, a user may specify a location in the diagram by right-clicking at the desired location and selecting Paste.
Print the currently loaded model.
Zoom in.
Zoom out.
Fit to page.
Go back in the history of displayed subsystems.
Go forward in the history of displayed subsystems.
Display the parent of the currently displayed subsystem.
Disable Reactis Simulator.
Enable Reactis Simulator.
Display the Configuration Variable Panel in the main panel. See Section 4.3 for details.

4.2 Menus

Some of the top-level menu items are described here; the rest are discussed in Chapter 7, which is devoted to Reactis Simulator, and in Chapter 9, which covers Reactis Validator.

Some menu entries also have keyboard shortcuts that enable the relevant operations to be invoked from the keyboard. These shortcuts are displayed to the right of the relevant entries in the menus.

File menu.

The file menu contains the following entries.

Open Model...: Load a new model into Reactis.
Close Model.: Close the currently loaded model.
Reload Model.: Reload the currently loaded model.
Select Info File...: Specify a Reactis Info File (.rsi file) to be used with the current model. See Chapter 5 for details.
Extract Info File...: Extract an .rsi file from an .rtp file . Reactis Tester may be configured to store launch parameters and the .rsi file used for a given run in a Reactis Tester Parameter file (.rtp file). Selecting this menu item retrieves the .rsi file from the .rtp file.
Save Info File.: Save the current .rsi file.
Save Info File As...: Rename and save the current .rsi file.
Print...: Open a print dialog for model printing. Section 4.5 explains this feature in more detail.
Remove Print Region.: Clear the selected printing region in the main panel. Users may select a region of a model for printing by left-clicking and dragging in the panel while holding down the control key. The resulting selection is highlighted within a blue box. Selecting this menu item removes the blue box.
Settings...: Opens dialog to adjust Reactis settings. Section 4.6 describes the use of this dialog.
Exit Reactis.: Exit Reactis.

Edit menu.

This menu includes entries used to manipulate .rsi files. These files contain constraints on the values assumed by top-level inports, details related to Validator objectives, and other model information maintained by Reactis. Note that .rsi files may be modified only when Simulator is disabled. Therefore, when Simulator is enabled the first five menu items are disabled, and the last five launch the Info File Editor in a read-only mode (the information may be viewed but not changed).

Undo.: Undo an operation (add, edit, remove, move) on a Validator objective.
Redo.: Redo last undone operation (add, edit, remove, move) on a Validator objective.
Cut.: Cut the currently selected Validator objective and place it in the clipboard.
Copy.: Copy the currently selected Validator objective to the clipboard.
Paste.: Paste a Validator objective from the clipboard to the current subsystem. To paste an objective to a specific position, right-click on that position in your model and select Paste from the context menu.

The following five entries invoke the Info File Editor to the tab specified by the menu entry. The Info File Editor is described in more detail in Chapter 5.

Port Types...: Constrain the values arriving at top-level inports.
Configuration Variables...: Manipulate workspace data items that configure model.
Test Points...: Manipulate test points for observing model behavior. Test points are internal data items that Reactis treats as virtual outputs; specifically, the tool records values for test points in test suites and, when executing a test suite, Reactis Simulator flags any differences between the values computed by a model for a test point and those stored in a test suite.
Callbacks...: Specify fragments of MATLAB code to execute before and/or after a model is loaded. Note that these operations are distinct from the similar Simulink callbacks.
Search Path...: Specify model-specific search path.
Dependencies...: Specify files on which a model depends.

View menu.

The following are the menu entries that are enabled when Simulator is disabled. The other elements of the menu are only enabled when Simulator is enabled. See Section 7.2 for descriptions of these items.

Back.: Go back in the history of displayed subsystems.
Forward.: Go forward in the history of displayed subsystems.
Go to Parent.: Cause the parent of the currently displayed subsystem to be displayed in the main panel.
Zoom In.: Same as labeled window item 10.
Zoom Out.: Same as labeled window item 11.
Zoom to Fit.: Fit to page; same as labeled window item 12.
Expand Tree.: Causes the entire tree in the model hierarchy panel to be expanded.
Collapse Tree.: Causes the entire tree in the model hierarchy panel to be collapsed.
Select Label Font Type...: Select font for labels in Simulink / Stateflow diagrams.
Select Label Font Size...: Select size of font for labels in Simulink / Stateflow diagrams. If a negative value is entered, the font size given in the model will be scaled by (the absolute value of) the entry. For example, enter -1 to use the font size from the model; use -0.9 to scale the font from the model down by 10 percent; use -1.1 to scale the font from the model up by 10 percent.
Select C Source Font...: Select font for displaying C source code in the main panel when using Reactis for C Plugin.
Select Line Styles...: Select styles and colors for drawing various Simulink / Stateflow diagram items.
Show Recent Errors...: Display recent error messages encountered for the current model.
Clear Recent Errors.: Remove all entries from the list of recent errors.

Simulate menu.

Only one menu entry is enabled when Simulator is disabled, and it is described below. The remaining elements of the menu are only enabled when Simulator is enabled, and are described in Section 7.2.

Simulator on/off.: Toggles whether Simulator is enabled or disabled. Implements the same behavior as labeled window items 16 and 17 in Figure 4.1.

Test Suite menu.

The following menu entries are enabled when Simulator is disabled. The remaining elements of the menu are only enabled when Simulator is enabled, and are described in Section 7.2.

Create...: Launch Reactis Tester. See Chapter 8 for details.
Browse...: Launches the Test-Suite Browser by first opening a file-selection dialog to allow user to indicate which test suite is to be browsed. See Chapter 11 for details.

Validate menu.

Since Validator objectives may only be modified when Simulator is disabled, the first four entries are disabled when Simulator is active. Depending on the state of the main panel, these entries might be enabled when Simulator is disabled. See Chapter 9 for more details.

Add Assertion: Add an assertion to the system currently displayed in the main panel. The sub-menu enables the user to specify whether the assertion should be an expression, a diagram, or a timer. This menu item is enabled when the subsystem currently displayed in the main panel is a Simulink diagram, but disabled when it is Stateflow diagram; to add assertions into Stateflow diagrams, right-click in the diagram.
Add User-Defined Target: Add a user-defined target to the system currently displayed in the main panel. The sub-menu enables the user to specify whether the target should be an expression, a diagram, or a timer. This menu item is enabled when the subsystem currently displayed in the main panel is a Simulink diagram, but disabled when it is a Stateflow diagram; to add user-defined targets into Stateflow diagrams, right-click in the diagram.
Edit Objective...: Edit the currently selected Validator objective. This menu item is disabled if no objective is selected.
Remove Objective.: Remove the currently selected Validator objective. This menu item is disabled if no objective is selected.
Check Assertions...: Launch Reactis Validator to search for assertion violations. See Chapter 9 for details.

Coverage menu.

No items are enabled when Simulator is disabled.

Window menu.

Enables user to switch between models currently loaded in Reactis.

Help menu.

The Help menu contains five entries.

Contents.: Go to the table of contents in the on-line documentation.
Index.: Go to the index in the on-line documentation.
Frequently Asked Questions: Go to the Frequently Asked Questions section of the on-line documentation.
Release Notes.: Display the release notes for the current Reactis version.
Top Level.: Go to the section of the on-line documentation that describes the Reactis top-level window.
About.: Open a dialog displaying the Reactis version and other configuration information. The dialog includes a Copy To Clipboard button to transfer the information to the Windows Clipboard. When requesting assistance, sending this information to Reactive Systems via email often facilitates the efficient delivery of support.

4.3 Configuration Variable Panel

If you have defined configuration variables for your model (see Section 5.1.2), Reactis will include an entry “(Configuration Variables)” in the top-level of the hierarchy panel. Clicking on this entry displays an entry in the main panel for each currently defined configuration variable. This panel allows you to view and manipulate configuration-variable information.

Double-clicking on a configuration variable when Simulator is disabled opens the type editor dialog to specify the type of the configuration variable. When Simulator is enabled and at the start of a simulation run (no steps have been taken), double-clicking on the configuration variable opens a dialog to specify a value for the variable.

When Coverage -> Show Details is selected in Simulator, information on boundary value coverage for configuration variables is conveyed in the panel. A block is highlighted in red if it has any uncovered boundary value targets. See Section 6.3.2.1 for a description of the boundary value targets associated with a configuration variable. Hovering over the variable in this panel displays test and step in which exercised targets were covered.

4.4 Extracting Subsystems

It is sometimes useful to apply Reactis to individual subsystems within a larger model. For example, if a given model is closed-loop, with a controller connected to a plant, then isolating the controller subsystem may be needed in order to perform model-driven testing of controller code. In other cases, very large models might require subsystem-at-a-time analysis. Reactis enables such analyses by providing a facility to extract subsystems from models. This feature isolates a subsystem, along with portions of the model involved in triggering the subsystem, and stores the result as a new model in a separate .mdl file.

The subsystem extraction utility is invoked by loading a model into Reactis, then right-clicking on the Simulink subsystem or Stateflow chart to be extracted and selecting the Extract Subsystem entry in the pop-up menu. The name of the file in which to store the extracted model may be specified using the resulting file-selection dialog. Reactis then extracts the subsystem, saves it under its new name, opens a new Reactis window, and loads the extracted model. Note that the extracted subsystem is saved as a standard .mdl file, making it easy to edit the extracted model using Simulink if changes to new model are necessary.

When extracting a subsystem, Reactis retains the hierarchical structure of the original model. That is, the original subsystem interfaces enclosing the extracted subsystem are retained, although the input and output ports connected to these interfaces are altered to coincide with those of the extracted subsystems. Retaining the model hierarchy in this fashion facilitates the inclusion of triggering mechanisms in the extracted model.

If the extracted subsystem

is a triggered subsystem,
is located within a triggered subsystem, or
contains one or more triggered subsystems whose triggers are connected to something outside the extracted subsystem

then Reactis determines which portions of the model residing outside of the extracted subsystem should be retained in order to trigger the extracted subsystem properly. This ensures that the simulation times during which the extracted subsystem is executed match those of the subsystem before it was extracted.

If the extracted subsystem references Data Store Memory blocks located outside the extracted subsystem, Reactis will keep those Data Store Memory blocks. However, Reactis will not keep any Data Store Write blocks outside the extracted subsystem.

Note that the extraction tool can extract parts of a model even if Reactis reports errors when trying to run it. This enables Reactis to be used on models that contain Simulink features that are unsupported by Reactis, as long as those features are not used in the extracted subsystem. For example, one may extract a discrete-time controller subsystem from a model that includes a continuous-time plant.

4.5 Printing Models

Figure 4.2: The Print dialog.

Reactis includes a flexible facility for printing models. Upon selecting menu item File -> Print... or clicking the button (window item 9 in Figure 4.1) the print dialog shown in Figure 4.2 appears. The radio buttons and check-boxes in the Print Range section of the dialog specify which portions of the model should be printed as follows.

Selection.: Prints only the portion of the model located within the current print region in the main panel. If no print region is defined, this entry is disabled. A print region is selected by left-clicking and dragging in the main panel while holding down the control key. The print region is cleared by selecting menu item File -> Remove Print Region.
Current system.: Prints only the system currently displayed in the main panel.
Current system and above.: Prints the system currently displayed in the main panel and all systems between the current system and the top-level system in the current model. Each such system is printed on a separate sheet of paper.
Current system and below.: Prints the system currently displayed together with all its subsystems, sub-subsystems, etc. Each system is printed on a separate sheet of paper.
Whole model.: Prints the whole model.
Expand unique library links.: When checked, library blocks referenced by the model will be printed. Note that each library block is printed only once, even though some blocks might be referenced multiple times by a model.
Look under masks.: When checked, masked subsystems will be printed.

The following radio buttons and check-boxes in the Frame section specify whether a frame should be printed on each page, and if so what content should be included in the frame.

No frame.: When checked, no frame is printed.
Frame.: When checked, a frame is printed.
Include system name.: When checked, the name of the system is printed in the upper left part of the page frame.
Include print date.: When checked, the date the model was printed is include in the bottom left corner of the frame on each page.
Include page number: When checked, the page number is printed in the bottom right corner of the frame on each page.
Include file name.: When checked, the name of the .mdl file containing the model and the folder containing the file is printed in the bottom left corner of each page.

The remaining buttons in the print dialog work as follows.

Help.: Display print dialog help.
Page Setup...: Invokes a dialog that allows the user to specify paper size and margins, and whether printing should be portrait or landscape.
Preview.: Open a viewer to display what will be printed.
Print...: Begin printing.
Close.: Close the dialog (and cancel printing).

4.6 Reactis Settings

Selecting File -> Settings... invokes the Reactis Settings dialog, which allows users to adjust the behavior of Reactis. The settings are partitioned into seven groups: “General”, “Reactis for C”, “MATLAB”, “Path”, “Files”, “User Info”, and “License”. Each group is displayed in a separate tabbed pane as described below.

4.6.1 General Settings

The General settings tab shown in Figure 4.3 includes the following items.

Figure 4.3: The Settings dialog with tab “General” selected.

Language.

Language used in the Reactis GUI.

Model file encoding.

Character encoding used by .mdl files.

On integer overflow.

Integer overflow can occur during the evaluation of some blocks. These blocks typically have a SaturateOnIntegerOverflow parameter. When set to ’on’, this parameter specifies that the block should evaluate to the maximum value for the type on overflow and the minimum value on underflow. When SaturateOnIntegerOverflow is set to ’off’ Simulink uses the model parameter IntegerOverflowMsg ¹ to determine how overflows are handled. There are three possible settings:

none.: Return the wrapped around value ².
warning.: Return the wrapped around value but also issue a warning.
error.: Raise an error and halt simulation.

Reactis gives users a way to override the IntegerOverflowMsg parameter with the ’On Integer Overflow’ setting which may have one of three possible values:

Wrap over.: Return the wrapped around value.
Produce error.: Raise an error and halt simulation or test-generation. In the case of interrupted test-generation, Reactis Tester returns a test suite that includes a test leading to the overflow.
Inherit from model settings.: Use the IntegerOverflowMsg setting from the model; however, Reactis does not currently generate warnings. When IntegerOverflowMsg is set to ’warning’, Reactis behaves as if it is set to ’none’.

Conditional input branch execution.

Conditional input branch execution is an optimization that causes some blocks in a model not to execute when they are not necessary to compute the outputs of the model. Please see Section 15.1 for a description of this optimization. This menu options are:

On: Use conditional input branch execution.
Off: Do not use conditional input branch execution.
Inherit from model settings: Enable or disable conditional input branch execution according to the settings in the .mdl file.

When Detecting Stateflow Outport Merge.

This setting configures Reactis to issue a warning or error when a model contains a particular configuration of Stateflow charts and merge blocks that can yield unexpected behavior. Note that even for models with this unexpected behavior, Reactis implements the same semantics as the MathWorks Simulink / Stateflow engine.

We now describe how the unexpected behavior can occur. If an outport of a Stateflow chart is directly connected to a merge block and the outport is read within the chart, then an unexpected back-propagation of values from outside the chart into the chart via the outport can occur. This setting enables you to configure Reactis to produce a warning or error when such a construct is detected. The following example shows a model in which this back-propagation occurs.

Figure 4.4: Unexpected back-propagation of a value through an outport of a Stateflow diagram. In this example, the value output by the digital clock is propagated back into Chart2 via out1. The value is then output on out2, yielding the matching scopes for the clock and out2.

Stateflow infinite loop detection timeout.

Maximum time for Reactis to compute a simulation step. If the computation of a simulation step takes longer, Reactis assumes there is an infinite loop; the simulation is then terminated and an error message printed.

Create and use cache files (with extension ’.mwi’).

Instructs Reactis to create a file containing intermediate information it has computed about a model. These files can significantly improve subsequent load times. Clicking the Flush Cache button causes the cache to be emptied. Subsequently intermediate information will be recomputed as needed. Note, however, that .mwi files are not deleted on disk.

When creating a test suite, also create a parameters file (extension .rtp).

Instructs Reactis Tester to store launch parameters and the .rsi file used for a given run in a Reactis Tester Parameter file (.rtp file ). Subsequently:

the .rsi file may be extracted from the .rtp file by selecting File -> Extract Info File...;
the Tester parameters may be loaded into the Tester launch dialog by clicking the Load button.

Re-running Tester with the same .rsi file and same parameters on the same model will regenerate the test suite produced by the original Tester run.

Track boundary coverage for relational operators

As described in Section 6.3.2.2, Reactis tracks boundary value coverage for Relational Operator blocks. Since this coverage criterion has the potential to introduce a large number of very hard to cover targets, some users might prefer to not track these targets. This checkbox enables and disables boundary value coverage tracking for relational operators.

Ignore ToFile and ToWorkspace blocks.

Checking this box enables Reactis to process models that include these blocks by ignoring them. If not checked, Reactis reports an error whenever it simulates a model containing such blocks. This behavior is due to the fact that Reactis does not maintain a MATLAB session while simulating a model.

Short-circuit Simulink boolean operators.

Checking this box indicates that evaluation of logic blocks should be short-circuited, i.e. should be halted as soon as its output value has been determined. For example, once one input to an AND block has been found to be false, it is known that the output of the AND block should be false; if this box is checked, then the remaining inputs are not examined. Short-circuiting affects coverage analysis and reporting for Condition, Decision and MC/DC coverage metrics, as unexamined inputs are treated as “don’t care” points. More information about coverage may be found in Chapter 6.

Short-circuit Stateflow boolean operators.

Checking this box indicates that boolean operators in Stateflow guards should be short-circuited. See the previous item for a discussion of short-circuiting.

Automatically check for updates (once a day).

Instructs Reactis to check once per day whether updates to Reactis are available for download. If updates are found you will be asked if you would like to download and install the patch. Note: this feature can be disabled at install time; in which case this checkbox will not appear in the dialog.

Enable logging.

Enables logging, specify a log level, and indicate the file to which the log should be written. Note that logging degrades performance and can create very large log files; therefore, it is typically only used to diagnose problems. The log level string will by provided by the Reactis support team if you are asked to create a log file.

4.6.2 Reactis for C

This tab is used to enable and configure Reactis for C Plugin. Please see Section 16.2 for details.

4.6.3 MATLAB Settings

Reactis sometimes invokes MATLAB during simulation, test-generation, and validation. The MATLAB settings tab, shown in Figure 4.5, enables the user to configure some aspects of how Reactis invokes MATLAB as follows.

Figure 4.5: The Settings dialog with tab “MATLAB” selected.

Use MATLAB version

If a user has multiple versions of MATLAB installed, this pull-down menu may be used to specify the version of MATLAB that Reactis will invoke. Each installation of MATLAB that Reactis automatically detects will have an entry in the menu. The menu includes two additional entries:

None specified (use Windows path): When this entry is selected, Reactis will invoke the version of MATLAB that appears first in the Windows path.
Custom: When this entry is selected, Reactis will invoke the version of MATLAB that appears in the MATLAB root text entry box (just below this menu in the MATLAB tab of the settings dialog).

Use MATLAB root

This text entry box becomes enabled when the Custom entry of the MATLAB version menu is selected. By entering a folder name (directly or by clicking the button to the right and using the file-selection dialog), the user specifies a folder containing the MATLAB installation which Reactis should use. This configuration is typically only used for a custom MATLAB installation that Reactis is unable to detect automatically.

MATLAB startup timeout (seconds)

When Reactis invokes MATLAB , it will wait this long for a response indicating a successful invocation before assuming that MATLAB will not start properly.

Prepend Reactis search path to MATLAB path

When this box is checked, every time Reactis launches MATLAB it will prepend the Reactis search path to the MATLAB path.

Execute startup.m and pathdef.m scripts in model folder

When this box is checked, every time Reactis launches MATLAB it will look for pathdef.m and startup.m files residing in the same folder as the model. If a pathdef.m file is found, Reactis will set the MATLAB path according its contents. If a startup.m file is found, Reactis will direct MATLAB to execute it prior to loading the model.

4.6.4 Path Settings

The Path settings tab, shown in Figure 4.6, enables the user to specify the list of folders in which Reactis will search for files such as Simulink model libraries (.mdl), MATLAB scripts (.m), and S-Functions (.dll, .mexw32, .m). The order in which folders are listed in the dialog specifies the search order (from top to bottom).

Note that Reactis also gives users the capability to define model- specific search paths which consist of a list of folders to be searched when loading a given model. The model-specific path is set using the Reactis Info File Editor as described in Chapter 5. When searching for files, the complete search path is constructed by prepending the model-specific path to the global path.

The buttons labeled in the figure work as follows.

Figure 4.6: The Settings dialog with tab “Path” selected.

Add a new folder to the list.
Open a dialog to edit the currently selected folder.
Remove the currently selected folder(s) from the list.
Select all folders in the list.
Copy the currently selected folder(s) to the clipboard.
Paste from the clipboard to the list.
Invoke MATLAB , query the MATLAB path, and add each folder in the MATLAB path to the list.
Move the currently selected folder up one spot in the list.
Move the currently selected folder down one spot in the list.
Move the currently selected folder to the top of the list.
Move the currently selected folder to the bottom of the list.

4.6.5 Files

The Files tab, shown in Figure 4.7, enables you to specify the folder where Reactis should store files that it creates and uses.

Figure 4.7: Specify the folder where Reactis should store files that it creates and uses.

4.6.6 User Info Settings

The User Info settings tab is shown in Figure 4.8. When Reactis is configured to use a remote license server as described in the next section, info contained in this panel is submitted to the server when Reactis is started, and available to all users who have access to the server.

The list of users occupying licenses at a given time may be obtained using the License tab of the Settings dialog as described below, or using the standalone License Monitor utility included in the Reactis distribution. This utility may be invoked by selecting Reactis V2008 -> License Manager -> License Monitor from the Windows Start menu.

Figure 4.8: The Settings dialog with tab “User Info” selected.

4.6.7 License Settings

The License tab is shown in Figure 4.9 and enables the user to query and specify license configuration information. The first two sections display the MAC address of the machine on which Reactis is running and the location of a local license file if one is in use.

The third section of the tab displays a list of servers running the Reactis License Manager. When Reactis is invoked, this list will be searched from top to bottom for an available license. The lower portion of the tab displays information for each License Manager in the list. This information includes the status of the License Manager, the total number of licenses, the number of licenses currently being used, the IP addresses currently occupying licenses, and any info (names, phone numbers) available for users actually using the licenses.

Figure 4.9: The Settings dialog with tab “License” selected.

Each of the window items labeled in Figure 4.9 is interpreted and used as follows.

Information about the contents of the local license file. If there is a problem with the license file, then a description of the error condition is listed here. If no problem exists, then a list of licensed products and their expiration dates is given.
This is the list of servers running the Reactis License Manager. Each entry in the list includes the following:
Host
The name or IP address of the server running the License Manager.
Status
The status of the connection to the License Manager.
For each product managed by the server:
Product
Name of the product (Reactis or Reactis for C Plugin).
Total
The total number of licenses for the product.
In Use
The number of currently occupied licenses for the product.
Add a new License Manager to the list.
Remove the currently selected License Manager from the list.
Move the currently selected License Manager up one spot in the list, down one spot in the list, to the top of the list, or to the bottom of the list.
Information regarding the currently selected License Manager is displayed here. If there is a problem with the connection to the License Manager, then a description of the error condition is listed here. If no problem exists, then for each license currently occupied, this section lists:
IP Address.
The IP address of the computer on which the Reactis application occupying the license is running.
Name.
The contents of the Name field in the User Info settings tab of the person occupying the license.
Phone.
The contents of the Phone field in the User Info settings tab of the person occupying the license.
Duration.
The length of the time this computer has been holding the license.

1: To set the IntegerOverflowMsg parameter, from the Simulink main menu select Simulation -> Configuration Parameters. In the resulting dialog, select the ’Data Integrity’ item from group ’Diagnostics’ and then set via ’detect overflow’.
2: Wrapping around works in the usual fashion. Incrementing the maximum value in a type by one yields the minimum value in the type. Decrementing the minimum value in a type yields the maximum value in the type.