![]() |
![]() |
![]() |
![]() |
![]() |
Menu Bar
This section describes the menu bar of the Organizer Main window and all the available menu choices.
The menu bar contains the following menus:
Available Menu Choices
The following concepts affect the menu choices that are available in the menu bar.
Long and Short Menus
The user can choose between long and short menus with the menu choice View Options in the View menu. Menu choices only available in long menu mode are presented with the menu choice name within parenthesis in the textual enumeration of menu choices for a menu in the following sections.
License Dependent Menu Choices
The following menu choices are only available if the corresponding tool is available according to the license configuration:
Configurable Menus
In the SDL Suite, some menu choices may be available through the concept of user-defined menus. For more information, see "Defining Menus in the SDL Suite" on page 18 in chapter 1, User Interface and Basic Operations.
File Menu
The File menu contains the following menu choices. (Menu choices within parenthesis are not available in short menu mode.)
- New
- Open
- Save
- Save As
- Pack Archive
- Unpack Archive
- Print > All
- Print > Selected
- Print > Selected and Colored
- (Set Directories)
- PC Drives
- (Compare System)
- (Merge System)
- (Import SDL)
- Recently used system files
- Exit
New
This menu choice displays a dialog, with the following possibilities:
- Start with a new and empty system, containing the basic Organizer view (see "Chapters" on page 47).
- Start with a standard template system, saved as an archive file (*.tgz) in the SDL Suite installation. The archive files for the standard template systems are and should be saved in directory <install dir>/sdt/include/template/.
- Start with any template system, saved as an archive file (*.tgz) anywhere in the file system.
If you want to start with a template system, you will have to specify the directory to unpack the archive file in, in "Unpack Archive" on page 69 that follows.
If a system file already is open in the Organizer, the behavior is determined by the status of the existing system. If modified information exists, the user first gets the possibility to save it; see "The Save Before Dialog" on page 65.
The new system is then created in memory. Source Directory and Target Directory are left unchanged, i.e. set to the values they had before the New operation.
The actual value of a directory in the Set Directories dialog may change if the directory is set to System file directory. Since there is no system file associated with a new system, the SDL Suite and TTCN Suite start-up directory is used until the file is saved.
You have to save the system to create a system file on disk.
The old contents of the drawing area is replaced with the basic Organizer view. If any of the documents in the old system managed by the Organizer were opened in an editor, these editor windows are closed.
Open
This menu choice is usually used to open an existing system file. It can also be used to open a single diagram or document file, as well as to open and resolve a *.scu file.
Opening a System File
If a system file is already open in the Organizer, the behavior is determined by the status of the existing system. If the information is not modified, the Open dialog is issued (see below). If modified information exists, the user first gets the possibility to save it; see "The Save Before Dialog" on page 65.
The Open dialog is a standard file selection dialog, with the file filter set to *.sdt. The Open button in the dialog opens the specified system file. The old contents of the drawing area is replaced with the new system. If a system window state file is found, see "System Window State File" on page 200, the window position and size is restored to the position and state it had when the system file was saved. If any of the documents managed by the Organizer were opened in an editor, the editor windows are closed.
If the system file does not specify the Source Directory and/or the Target Directory explicitly, these directories are set to the directory where the system file was found.
The following information consistency checks are performed when opening a system:
- That the opened file is a valid system file. The case when an SDT-2 diagram file is opened is discussed above. If a system file created with an earlier version of SDT-3 is opened, you will be warned that the file will be saved in the current format
- All file bindings in the system file are verified. For each file, a check is made to see that the file exists and that the file is of the correct type. The file access permissions are also determined. If something is not correct, it is reported in the Organizer Log.
- If a document is marked Invalid, the user must later correct the file binding. The user could either reconnect the document to a valid file, or perform a disconnection in which case the document disappears.
- The SDL diagram structures in the system file and in the SDL diagram files are also compared, in terms of existing SDL reference symbols. If connected SDL diagrams in the system file are not present in the corresponding SDL diagram files, the diagram icons are marked Mismatch and the status is logged in the Organizer Log window. Unconnected SDL diagrams are removed from the system file and the Organizer's diagram structure. New reference symbols found in the SDL diagram files are added as unconnected diagrams in the system file and the Organizer's diagram structure.
- File protection of the system file and the working directory. If either of them is write protected, a warning message appears.
Opening a Diagram or Document File
If you are only interested in examining the contents of a single diagram or document file, you can specify the filename of that diagram or document in the open dialog. (It might be helpful to change the filter in the open dialog first, to be able to view the existing files of the type that you are interested in.)
If you specify the filename of a single diagram or document in the open dialog, then a new system file will be created, only containing the specified diagram or document. The diagram or document will also be loaded and shown in an appropriate editor. Note that no sub(structure) diagram files will be visible in the Organizer view.
Opening a *.scu File
Software control unit files *.scu are used to allow several people to work in parallel on the same SDL diagram structure. When you update your *.scu files, for instance by using the Configuration > Update menu choice, the SDL diagram structure might change, if someone else has changed the structure and checked in an updated *.scu file.
You can have a top *.scu file associated with the system file symbol in the Organizer drawing area. This *.scu file will take control of the diagram and document structure in the Organizer, leaving the *.sdt file with only control over the user settings (print, view...) and a little system state information (when was the SDL system analyzed without errors last?)
Opening an *.scu file is the same as creating a new system by attaching a *.scu file to the system file symbol in the Organizer and using Configuration > Update to update the diagram and document structure according to the contents of the *.scu file.
Opening an Archive File
Opening an archive file (*.tgz) invokes the unpack archive file operation. Read more about this in "Unpack Archive" on page 69.
Save
This menu choice saves all modified documents and control unit files known to the Organizer, the link file, and finally the system file used by the Organizer. You can still perform a save even if the Organizer contains a completely new system, or if the system has not been changed since the last save operation. The menu choice has the text Save (not needed) in this situation.
Whenever the system file is saved, the system window state file is saved as well. See "System Window State File" on page 200.
If the system file is modified and needs saving, an asterisk `*' is appended to the name of the system file in the Organizer's title bar.
When the first document that is modified is encountered in the Organizer's view of files, the Save dialog below appears. If not Save All, Quit All or Cancel is selected, the dialog will remain on the screen and all modified documents will be handled by the dialog subsequently.
Whether the document is connected to a file or not will affect the layout and behavior of the Save dialog. For any unsaved and unconnected documents found, the user must provide a filename to connect to.
If the system has been saved before, the system file is saved (without a dialog) after all diagrams and documents have been saved. If the system never has been saved, the Organizer presents a dialog and proposes a name for the system file; the prefix is the name of the first document in the structure, the extension is .sdt.
The fields and buttons in the Save dialog are:
- Save in file
- If the document is connected, the name of the connected file is shown. If the system file is to be saved for the first time, a proposed name for the system file is shown. The filename can be edited by the user.
- If the document is not connected, the Organizer proposes a filename based on the document name and a file extension corresponding to the document type, making the file name unique in the file system (see "Save" on page 11 in chapter 1, User Interface and Basic Operations for more information). The filename can be edited by the user.
- The Organizer will not accept a file name that would overwrite another document or a diagram file that is loaded in an editor.
- The user is prompted to confirm the file name if it is already used by a document included in the document structure.
- If the file exists in the file system when the Save button is pressed, the user is warned in a message box that the existing file will be overwritten.
- If a valid filename is provided, Save or Save All below also connects the diagram to the supplied file.
- Save
- No Save
- Ignores the file without saving it. Then the next file which needs to be saved is shown. If, during the save process, the user saves some SDL diagram files but not others, there is a risk of SDL diagram structure mismatches between the system file and the diagram files. Therefore, a warning dialog with the following alternatives is opened:
- Save All
- Quit All
- Quits all files (document files, control unit files, the link file, and the system file) without saving. If, during the save process, the user saves some SDL diagram files but not others, there is a risk of SDL diagram structure mismatches between the system file and the diagram files. Therefore, a warning dialog with the following alternatives is opened:
Save As
This menu choice works as the Save menu choice with the following differences:
- Save As is always selectable.
- There is always a Save dialog for the system file.
- The Save As menu choice is used to save the system file under a new name. If the system file is saved under the old system file name, the user has to confirm this in a dialog.
The Save Before Dialog
Some operations in the Organizer need to save information before the actual operation can be performed. The saving is only performed if modified information exists in the system. In these cases a Save Before dialog is opened, which is very similar to a normal Save dialog. The dialog title is Save before <command> and some buttons may behave differently (see Figure 12 on page 71). If not Save All, Quit All or Cancel is selected, the dialog will remain on the screen and all modified files will be handled by the dialog subsequently.
The Save Before dialog is opened for the following menu choices:
- File menu: New, Open and Exit
- The save process handles modified documents in all chapters. In the case of Exit, unsaved diagrams in editors that are not yet in the document structure of the Organizer are also handled.
- If an SDL diagram is modified, has a diagram substructure and some of these SDL diagrams are either opened in an editor or connected to a file, special care must be taken. If the user chooses not to save such an SDL diagram, inconsistencies between the system file and the diagram files may result. The user is warned in a dialog and may choose to continue, i.e. not to save, or to return to the Save Before dialog. (See "No Save" on page 64 and "Quit All" on page 64.)
- File menu: Compare System and Import SDL
- Generate menu: Analyze, Make and SDL Overview
- Generate menu: Convert to PR/MP
- The save process handles modified SDL diagrams in all chapters. The buttons No Save and Quit All are dimmed. If the user clicks Cancel, the Convert to PR/MP dialog is opened with the GR source diagram toggle dimmed.
Auto Saving
When selecting any of the Generate commands Analyze, Make, Convert to PR/MP or SDL Overview, the Save Before dialog does not appear if the preference AutoSaveBefore is set. However, unconnected and modified documents still require user interaction. If such documents exist, the dialog appears.
Pack Archive
Pack files related to the system loaded in the Organizer into an archive file (*.tgz).
The archive file has the extension *.tgz and is packed using tar and gzip. This means that the archive file can also be unpacked without using the SDL Suite, from the command line, using g(un)zip and tar.
Packing and unpacking archive files will only work if the SDL Suite can access the external tar and gzip programs, see "Additional required tools and utilities" on page 4 in chapter 1, Platforms and Products. The external tools can be pointed out with the preferences "TarCommand" on page 246 in chapter 3, The Preference Manager and "GzipCommand" on page 246 in chapter 3, The Preference Manager.
The first Pack Archive Dialog
To use the pack operation, have the files you want to create an archive file for in the Organizer and invoke the operation. The first pack archive dialog will appear, where you can do the following things:
- Pack all diagrams into archive. This text field is used to specify where the archive file should be saved, and under what name. As default, the archive file is saved in the target directory, with a name based on the SDL system diagram name, and with a *.tgz extension.
- Diagram files are relative to. This text field is used to specify a source directory for files put into the archive. As default, the source directory specified in the Organizer is used. Note that files outside this directory, that should be included in the archive file, are put in a separate directory named external.
- Include top directory in archive. To avoid mixing files from an archive with other files when unpacking, it is possible to create a top directory for all files in the archive when packing. As default, a top directory is created, with the same name as the SDL system diagram that is packed.
- Save system file for archive in. With this option, it is possible to create a new system file for the archive, only referencing files that really are packed with file references updated for the archive. Use this option (instead of packing the original system file) to get a portable archive file. As default, an archive system file is created, in the archive top directory, with a name based on the SDL system diagram that is packed.
The second Pack Archive Dialog
When pressing the Next button in the first pack archive dialog, the second pack archive dialog appears, where file types to include can be decided. The following file types are included as default:
- Archive System File
- SDL Package Diagrams
- Other SDL Diagrams
- MSCs
- UML Diagrams
- Chapter Files
- Other Text Files
- Index Files
- Header and Footer Files
The following file types are not included as default:
- Original System File
- Generic Files
- Tau Workspace / Project
- Rhapsody Project
- Simulator Script Files
- *.scu files
The second pack archive dialog also makes it possible to include files from the source or target directories with specific extensions. These extensions should be specified in the Also include files with the following extensions text field (a comma separated list of extension names). As default, *.lst files from the source or target directory are included in this way, with the text field text set to lst.
The third Pack Archive Dialog
Pressing the Next button in the second pack archive dialog displays the third pack archive dialog, where all files that will be included in the archive are listed. A file in the list is usually presented in the following way:
<file system file name> (-> <archive file name> )In the dialog, it is possible to include or exclude individual files.
- To include a file, press the Add button and specify the file in the file selection dialog that appears.
- To exclude a file, select it in the list, and press the Remove button.
When you are satisfied with the list of files that will be packed, press the Pack button to start the pack operation. Information from the pack operation can be found in the Organizer Log.
Unpack Archive
This operation unpacks files in an archive file (*.tgz), and places them in a directory in the file system.
An archive file is created and unpacked with the external tools tar and gzip, that both must be available for the operation to work. The external tools can be pointed out with the preferences "TarCommand" on page 246 in chapter 3, The Preference Manager and "GzipCommand" on page 246 in chapter 3, The Preference Manager.
An archive file can be unpacked in one of the following ways:
- By invoking the unpack archive operation in SDL Suite:
- From the command line, using gzip and tar directly. (For more information about this alternative, see the documentation for these tools.
The Unpack Archive Dialog
Whenever SDL Suite is used to unpack, and the unpack directory has not been specified, the Unpack Archive dialog appears. The dialog has three things that should be considered:
- Unpack archive file. In this text field, the archive file to unpack should be specified.
- In directory. In this text field, the directory to unpack the files in should be specified.
- Open unpacked system file in Organizer. If this option is on, the Organizer will after the unpack operation search for a system file (*.sdt) among the unpacked files, and if there is a system file, it will be opened in the Organizer.
Print > All
Similar to Print > Selected. The difference is that for Print All, the selection is not considered, all diagrams and documents are always printed, if the set of diagrams and documents to print is not further refined in the print dialog.
Print > Selected
Prints all or some of the diagrams in the Organizer. See chapter 5, Printing Documents and Diagrams, for more information about the dialog and some examples of how to print. The Organizer selection decides the set of diagrams and documents to print, if the set is not further refined in the print dialog.
Print > Selected and Colored
Similar to Print > Selected. The difference is that for Print Selected and Colored, only pages (when pages are shown in the Organizer drawing area) or diagrams (when pages are not shown in the Organizer drawing area) with at least one colored symbol are printed. A symbol is colored when the symbol has a border color other than black or a fill color other than white.
Print > Selection File
A file selection dialog appears, where a print selection file should be specified (*.sel). The print selection file is read, and the Organizer print dialog is displayed, updated to reflect the state that the print dialog had when the print selection file was saved from the print dialog. The print selection file is capable of remembering:
- Selected diagrams/documents/pages.
- Print options (scale, paper format...)
- Index Viewer filter options (filter types, uses and diagrams)
- State Matrix Viewer filter options (in Text Editor) (filter processes)
Note that print selection files can also be used by having a print selection symbol in the Organizer. In that case, you can use the print selection file and invoke the print dialog by double-clicking on the print selection symbol.
Set Directories
This menu choice sets the source and target directories. For more information on these directories, see "Source Directory" on page 44 and "Target Directory" on page 44.
This menu choice is only available if the system file can be changed.
If the source directory is changed while a Save dialog is active in an editor, the directory where the editor saves the diagram is undefined. An ongoing analysis is not affected by changing the target directory.
- Source Directory
- Target Directory
- Source and target directory settings are saved in the system file. Both these directories can be specified in three ways:
- SDL Suite start-up directory: Source or target directory is set to the directory where the tool was started from (in Windows the directory of the executable file or the specified start directory for a shortcut icon). This setting means that relative file bindings in the system will be evaluated starting from the start-up directory the next time the system file is loaded into the Organizer.
- System file directory: This is the default value for both source and target directory. Source or target directory is set to the directory where the system file resides. For a new system that has not been saved yet, the start-up directory is used until the system is saved. This setting means that relative file bindings in the system will be evaluated starting from the system file directory the next time the system file is loaded into the Organizer. This setting also makes it possible to move a system file and all related diagram and document files to a new directory without having to update the system file, provided that the positions of all diagram and document files relative to the system file are preserved.
- A specific directory. The directory specified in the text field will be used. Note that the target directory can here be specified using a relative file name. If this is done, the source directory is used as a base to dynamically calculate an absolute target directory. This is useful when you want to have a target directory as a sub directory to the source directory and you want to be able to move all your system files in or between file systems without great effort.
- Absolute file names
- Relative file names
- If this option is set (the default), the Organizer stores document files with paths relative to the source directory. There are two variants regarding showing document files in the Organizer drawing area:
- Short form on (the default). The file connection is shown exactly as it is stored in the system file.
- Short form off. The directory part of a file connection is shown in italics for a file connection that exactly matches the Source Directory path. All other file connections are shown as absolute file names, even if they are not necessarily stored with absolute file paths in the system file.
- Change document directory
- This operation is used to change the directory part of one or more file connections in one operation. A symbol that has a file connection including the directory that should be changed has to be selected before invoking the dialog. This operation will be dimmed if there is no selection or if the selected file has no file connection.
- In the To text field, the directory which the selected directory should be changed into should be specified. When pressing OK with Change document directory on, all file connections matching the From directory will be changed to the To directory.
PC Drives
This menu choice displays the drive table of the currently opened system, i.e. the mapping between drive names in Windows and the beginning of corresponding directory paths on UNIX. For more information, see "Windows and UNIX File Compatibility" on page 216.
This menu choice is only available if the system file can be changed.
The following dialog is opened:
The text area displays the drive table currently used in the system. The table can be edited directly in the text area. When the system file later is saved, the table is stored in the The Drives Section.
When clicking OK, a basic syntax check is performed on the entered drive table. Each line should consist of two items only:
- A Windows path, either a drive letter followed by a colon, e.g. H:, or a full path (e.g. C:\TEMP). UNC paths can be used (e.g. \\<host>\file). If you include a trailing backslash (optional) you must also include a trailing slash in the corresponding UNIX path.
- A UNIX directory path starting with a slash `/'. If you include a trailing slash (optional) you must also include a trailing backslash in the corresponding Windows path.
Paths containing spaces must be put within double quotes. Note that within double quotes, each backslash must be entered as two backslashes, i.e. a UNC path \\host\dir name (containing spaces) must be entered as "\\\\host\\dir name".
If any errors are found, the user is notified and the dialog is not closed. If the table was changed and found to be syntactically correct, the system file is marked as modified.
Changes made in the PC Drives dialog only take effect when the system file is reloaded.
Compare System
Works as Merge System, except that there is no possibility to merge the differences found during the compare operation.
Merge System
This menu choice compares the contents of the Organizer Main window with the contents of a system file (.sdt file). The compare operation is performed on a diagram/document level.
This menu choice is only available if the system file can be changed.
The two systems are compared and possible differences are reported to the user, with the option to merge them, by specifying which documents to add and which to remove in the Organizer system.
The information is processed according to the following scheme:
- The user is asked to exit any editors, if any is found running. This means that modified documents must be saved before the comparison can be started.
- If the system file is modified, the user is prompted to save it in a The Save Before Dialog.
- A standard file selection dialog is issued, where the system file to compare the Organizer system with may be selected. Choosing a system file in this dialog starts the compare operation.
- If there are differences between the options set in the Organizer and the options saved in the system file to compare with, these are reported first, as a text in a separate dialog. The text might look like this:
Comparing system in Organizerwith /home/develop/lat/target/DemonGame.sdt.Options saved in system file differs:SemanticControl differs: False TrueKernel differs: SCTVALIDATOR SCTADEBCOM
- If you want to remove these differences, you have to do it manually by changing different settings in the Organizer. For instance, to remove the SemanticControl difference by updating the Organizer settings, bring up the Analyzer dialog and select Semantic analysis. (SemanticControl is the word used in the system file, Semantic analysis are the words used in the graphical user interface for the same thing.)
- The Compare System dialog is issued, where the diagram and document differences are reported (if the Organizer system and the contents of a system file are found identical, this is reported in a message box and the operation is terminated).
- The user decides if and how to merge the two views, by selecting or deselecting the items to include or exclude from the resulting system. OK updates the system in accordance with the settings.
The Merge System Dialog
- The lists are sorted according to the order of appearance of the items in the Organizer Main window and the order of appearance in the system file.
- Each item in a list identifies a chapter, module or document that was found in only one of the two systems (i.e. in the Organizer or in the system file) or were found in both systems, but differ from each other (see "How Systems Are Compared" on page 78 for more information about how structures and documents are compared).
- A document is listed with its type, name and the file it is stored on. A module is listed with its type and name. A chapter is listed with its name.
- A chapter, module or document that was found in one system but missing in the other, is present in one list only and is identified in the other list with a non-selectable `-' (hyphen).
- Documents that were found in both systems and that are considered equal are not listed. See "equal" on page 78 for more information.
- Documents that were found in both systems and that are considered almost equal are presented in both lists. See "almost equal" on page 79 for more information.
- Association and dependency links are not included in the lists, but are preserved as far as possible. See "Associations and Dependencies" on page 79 for more details.
- The items in the two lists that are selected will be included in the resulting (merged) Organizer view.
The items in the Organizer diagrams list are the icons that were found in the Organizer's chapters.
By default, all items that originate from the Organizer are selected, meaning that they will be included in the merged view.
The <system file> list indicates the directory and name of the selected system file. The items in this list are the items that were found in the system file.
By default, given two documents that are considered almost equal, the dialog will select the document originating from the Organizer, not the document originating from the system file. See example in Figure 15, above.
How Systems Are Compared
Some rules that govern how systems are compared:
- Relative file names:
- Relative file names are managed as if they were relative to the Source Directory as currently specified in the Organizer.
- Handling of SDL diagrams (including packages, excluding macro diagrams):
- SDL diagrams in a tree structure are examined starting from the top and down. When two diagrams are found to differ, their diagram subtree is not examined further, the subtrees being considered as a part of the diagrams that differed.
- This means that if the user chooses to include a diagram that has a subtree, the complete subtree will also be included. Similarly, if the user chooses to exclude a diagram that has a subtree, the complete subtree will be excluded.
- The level of indentation used when listing SDL diagrams in the dialog indicates the structural level at which a diagram is found.
- Handling of Object Model diagrams, State Chart Diagrams, HMSC diagrams, MSC diagrams, SDL macro diagrams, and SDL overview diagrams:
- Rules for equality of diagrams:
Compare System and Merge System do only compare the structural system information saved in the system file. Compare System and Merge System do not compare the document contents, such as page names.
Associations and Dependencies
The Compare System function preserves, as far as possible, the association and dependency links that exist between documents:
- When an association link is found in a system file, the file names of the two documents are saved.
- If a document with an association link is selected by the user to be included in the Organizer, a new link is generated if a document with the previously saved file name can be found in the Organizer structure. If such a document cannot be found, the association link is removed from the included document.
Import SDL
Imports an SDL diagram or a number of SDL diagrams in SDT-2 or SDT-3 format, and extracts the diagram structure with the possibility to save it in a system file. The command may, on demand, convert the imported diagrams into SDT-3 format without the need to involve the user for each diagram to convert. It is not possible to import an SDT-3 system file.
This menu choice is only available if the system file can be changed.
To avoid potential name conflicts when saving an imported diagram structure, the menu choice will not perform any action, and causes a message box to be displayed, in the case any files are opened in an editor.
Basically, the involved diagrams and their corresponding files are bound and presented in the Organizer. A number of information entities can be extracted from the diagrams.
If a system file already is open in the Organizer, the behavior is determined by the status of the existing system structure. The user is first asked to exit any editors, if any is found running. This means that modified documents must be saved before the import is started. If a modified system file exists, the user first gets the possibility to save it; see "The Save Before Dialog" on page 65.
The following dialog is then opened:
The root diagram to import and convert can either be named logically with type and name, or physically with a file name. The specified diagram will become a new root diagram, placed last in the Organizer.
- Close the current system first
- Expand Substructure
- Extract MSC Diagrams from SDT2 SDL diagrams
- If this option is set (the default), references to MSC diagrams found in SDL diagrams saved in SDT-2 format will be extracted and placed after the SDL diagram structure, together with a file binding. An association link to the MSC diagram is also inserted in the SDL diagram structure where the MSC diagram was extracted.
- Extract SDL Overviews from SDT2 SDL diagrams
- If this option is set (the default), existing overview diagrams stored in SDL diagrams saved in SDT-2 format will be extracted and stored in a separate file. The overview diagram is placed after the SDL diagram structure. An association link to the overview diagram is inserted in the SDL diagram structure where the overview diagram was extracted.
- Extract code generator directives
- If this option is set, the diagrams will be searched for a number of directives to be included in the system file. The option is not set as default. The directives #SEPARATE and #WITH are handled
- #SEPARATE: a separator is set in the system structure on each diagram containing the directive (see "Separator symbols" on page 109).
- #WITH: a warning is issued in the Organizer log and a template makefile is generated with the object files found.
- For more information on directives, see "Directives to the Cadvanced/Cbasic SDL to C Compiler" on page 2722 in chapter 56, The Cadvanced/Cbasic SDL to C Compiler.
- Save imported diagrams in SDT 3.X format
- If this option is set, parts of the diagrams which are obsolete in SDT-3 are removed from the diagram files to convert them to SDT-3 format. The parts removed are the ones controlled by the options Extract SDL Overviews from SDT2 SDL diagrams and Extract MSC Diagrams from SDT2 SDL diagrams, described above. If these options are not set, some information may be lost when importing SDT-2 diagrams. In this case, the user will be warned in a dialog when pressing the Import button:
Recently used system files
Just above the Exit menu choice, there can be up to four menu choices representing recently opened system files. To open one of them again, select the appropriate menu choice. The information about recently used system files is saved in a file called .sdtfiles, in your home directory (see "Environment Variables" on page 33 in chapter 4, System Setup, in the Installation Guide).
Exit
This menu choice exits the Organizer.
The exit operation consists of four phases:
- Handling of modified files managed in the Organizer structure.
- If modified information exists in the current system structure, the user gets the possibility to save it; see "The Save Before Dialog" on page 65. The dialog is opened for the first file (document/system file) that is modified in the Organizer's view of files. The user can then choose how to continue. If the user does not select Save All, Quit All or Cancel, the dialog will remain on the screen and all modified files will be handled by the dialog subsequently.
- The link file and the system file are saved last, if necessary. If the Exit process at a later stage is cancelled, all documents in the editors are still available, since they are not closed until all modified documents are handled.
- Confirmation of Exit.
Edit Menu
A general mechanism to edit the document structure(s) in the Organizer does not exist. Some of the menu choices in the Edit menu are used for basic operations on root documents and file connections. However, most changes to the document structure are a result of operations made in the diagram editors; see "Reference Symbols" on page 1897 in chapter 43, Using the SDL Editor.
The Edit menu features the following menu choices (menu choices within parenthesis are not available in short menu mode):
- Edit
- Add New
- Add Existing
- Remove
- (Connect)
- (Disconnect)
- (Configuration > Group File)
- (Configuration > Update)
- (Configuration > Full Update)
- (Color > Set Default Colors)
- (Color > Set Black and White)
- (Associate)
- (Paste As)
- (Go To Source)
- (Update Headings)
- (Update Visibility)
- (Properties)
Edit
This menu choice edits the selected symbol or document. A document is edited by starting the corresponding editor. A document which is opened in an editor has its name shown in bold face in the Organizer.
The menu choice is dimmed if the selected icon is invalid, or if an instance or dashed SDL diagram icon is selected.
The operation performed depends on the type of symbol or document selected, according to the following:
The CM Group dialog is opened (see "Configuration > Group File" on page 97).
The Set Directories dialog is opened (see "Set Directories" on page 71).
The Edit Chapter dialog is opened. This dialog contains three choices:
- Edit chapter symbol: the Edit dialog is opened (see below) to allow editing the symbol type, the chapter name, or the connected text file.
- Edit chapter options: the Chapter Options dialog is opened (see "Chapter Options" on page 110).
- Edit first page after chapter: the first connected SDL diagram or page after the chapter symbol is edited (see below).
The Edit dialog is opened (see below) to allow editing the module name.
The document/file is opened in an editor. For a diagram, the first page in the diagram is shown, or if the user has specified a page to open first in the editor (see "The Open This Page First Option" on page 2039 in chapter 43, Using the SDL Editor), this page is shown instead.
The corresponding referenced document is edited as if it was the selected document.
The Edit dialog looks like this:
- The Document type and Document name fields can be used to change the type and name of a root document. If a non-root document is selected, these fields are dimmed. If the type is changed, the new document icon will replace the old one. However, the type of a module that contains documents cannot be changed.
- The Document name text field contains the current name of the document, chapter or module. The name must conform to the naming rules for the document type; otherwise an error dialog is issued. The name of a module must conform to the naming rules for SDL diagrams, but the name of a chapter may contain any printable characters except quotation marks.
- The Show in editor option opens the document in an editor. This option is by default on for document types that can be shown in an editor. Deselecting this option automatically deselects the Copy existing file option.
- The Copy existing file option copies the specified file and uses it as a starting point/template for the document. If no file is specified, or the file does not exist, no file is copied. Selecting this option automatically selects the Show in editor option.
Add New
This menu choice adds a new document to the system. Normally, the added document is placed as a root document below the current selection. If there is no selection, the document is placed as the first root document in the Organizer. Adding a diagram also involves an update of a control unit if there is one that is associated with the diagram substructure affected by the Add New command.
There are two exceptions to this:
- If the selection is a module, the new document is instead added at the top level in the module. If the selection is a document in a module, the new document is added in the module at the top level after the selection. To move diagram and documents in and out of modules when they are already in the Organizer, the Move Down and Move Up quick buttons should be used.
- If the selection is a root TTCN document and the user adds a TTCN document, the added document will be placed as a child document below the selected document. If the selection is a child TTCN document, the added document will be placed below the selected document in the same TTCN system. This menu choice is therefore, together with the Move Down and Move Up quick buttons, used to build TTCN systems.
This menu choice is only available if the system file can be changed.
To add SDL diagrams other than root SDL diagrams, the SDL Editor is used (see "Adding a Diagram Reference Symbol" on page 1915 in chapter 43, Using the SDL Editor).
The same dialog is opened as for Edit on an unconnected document (see Figure 20 on page 88). By default, the Show in editor button is on.
If there is a selection, Document type and Document name in the dialog will be set to the selected symbol's type and name. If there is no selection, the dialog will show the settings from the previous invocation. If it is the first time this dialog is used, the default type Module and the default name "Untitled" will be used.
Multiple root diagrams with the same name are allowed.
If an SDL diagram was selected and an MSC diagram is added, an association link to the MSC diagram is automatically added to the SDL diagram.
Add Existing
This menu choice adds an existing document file to the system. (It is also possible to add several documents by specifying a directory) The existing document is added at the same place as described for the Add New menu choice. Adding a diagram also involves an update of a control unit if there is one that is associated with the diagram substructure affected by the Add Existing command.
This menu choice is only available if the system file can be changed.
A dialog will be opened, that allows you to specify the file to add, either via a text field or via a standard file selection dialog.
There are also three options in the dialog:
- One to specify if the substructure of the added SDL diagram should be expanded.
- One to specify if the added diagram or document should be shown in an editor.
- One to specify if files existing in sub directories to the specified directory (or the directory where the specified file resides) should be added.
If the standard file selection dialog is used, the file filter is set to reflect the currently selected document type. If a module is selected, the file filter is the same as in the previous invocation. If no document is selected, the file filter is set to .s??.
The document type and logical name of the existing document is determined in different ways for different document types. The type and name is determined by:
- Reading the specified file for SDL, MSC, HMSC, OM, SC, and TTCN documents.
- Looking at the file name and extension for text files and generic documents.
It is not possible to add a document that does not have a default file extension. For information about default file extensions, see "Save" on page 11 in chapter 1, User Interface and Basic Operations.
If an SDL diagram was selected and an MSC or Overview diagram is added, an association link to the MSC or Overview diagram is automatically added to the SDL diagram.
The existing document is by default opened in an editor. This behavior can be changed by the preference Organizer*ShowAddExisting.
Remove
This menu choice removes a selected root document and its document substructure, if any, from the system structure. Modules, chapters and top-level documents in modules can also be removed.
This menu choice is only available if the system file can be changed.
Removing a root document may also involve the update of one control unit file if there is any containing the diagram substructure that has been removed. The menu choice is dimmed if no such document, module or chapter is selected, or if the document is modified.
Removing a chapter symbol does not remove the documents in that chapter; only the chapter symbol itself is removed.
The following dialog is opened:
- Keep sub documents as new roots
- If the selected document contains a substructure, this option moves all documents in the substructure to become new root documents (but with their substructures kept intact). It also keeps all bindings to diagrams loaded in an editor. The new root documents are placed directly after the selected root document. If the selected document is a top-level document in a module, the new root documents are placed as top-level documents in the module.
- If this option is not set, the document substructure is removed together with the selected document, but documents being edited are still kept as buffers in editors. This is the default setting, except when a module is selected.
- The option is dimmed if the document contains no substructure, if no substructure document is connected, or if a chapter symbol is selected.
- Delete file <file> at the same time
Connect
This menu choice connects a selected document to a file. It is possible to reconnect an already connected document. The menu choice is hazed if a directory, page, instance diagram, dashed diagram, chapter, or module symbol is selected. The menu choice is also hazed if the loaded system file (*.sdt) or any associated configuration group file (*.scu) file is read-only.
- To an existing file
- This option connects the document to an existing file. If the document already is connected, the name of the connected file is shown. If the document is unconnected, the field is filled in with the directory component of the file used the last time a document was connected. The filter in the associated file selection dialog corresponds to the file extension for the document type.
- It is possible to use an environment variable to specify the first part of the file path. This can be useful if you want the system to "update its file references" when the environment variable value has changed. For instance, there is an environment variable called "telelogic" that points out the top installation directory for SDL Suite when SDL Suite is run. You can use this environment variable to point out one of the SDL diagram files in the installation:
- $telelogic/sdt/examples/demongame/Main.spr
- (Please consider using relative file names first, because that is often a better solution. See "Set Directories" on page 71.)
- When the connection is to be made, the selected file is inspected. For instance, for an SDL diagram, if the file is not an SDL Suite object file, an error message box is issued:
- If the file contains a document of the correct type but with an incorrect name, the symbol in the Organizer is renamed.
- If the file contains a document which has an incorrect type or name, the user is warned in a dialog:
- If the document already is connected and only the directory part of the existing file connection is changed, the following dialog is opened:
- Search in directory
- This option searches the specified directory for a document file of a type and name matching the selected document. If such a file is found, the document is connected to the file. If no such file is found, an information box is opened. Pressing OK in the dialog returns to the Connect dialog.
- The directory field is filled in with the Source Directory the first time the dialog is used. After that, the directory from the previous usage of the dialog is remembered.
- Expand substructure
- This option is only available for SDL diagram symbols. This option recursively expands and connects SDL diagrams to files until no more reference symbols are found. If an SDL diagram has a USE clause, i.e. it references a package diagram, this option also tries to expand the package and put it as a root diagram in the system. The diagram substructure of the package is expanded. Package references are expanded recursively.
- After the expansion is completed, the Organizer display is updated.
- Show in editor
Error Notification
If an error occurs, the user is informed in a message box and control is returned to the Connect dialog.
Reconnect Connected SDL Diagram
When performing a reconnect to an already connected SDL diagram, the current SDL child diagram references are matched against those found in the connected file. If mismatches are found, icons are marked as such but the structure is kept intact, if possible.
Connect Open Documents
When connecting an unconnected document that is opened and unsaved in an editor, the file name binding is not conveyed to the editor, i.e., the editor binding is lost.
Disconnect
This menu choice disconnects the connected file from the selected diagram. The menu choice is hazed if the selected symbol has no file connection. The menu choice is also hazed if the loaded system file (*.sdt) or any associated configuration group file (*.scu) file is read-only.
The following dialog is opened:
If the document is currently loaded in an editor and is modified, the document reference in the Organizer gets the same status as if a new document is edited, i.e. new and unconnected. The editor binding is then lost.
Configuration > Group File
This command operates on the currently selected diagram, and is used to create or remove a Configuration Management Group for the diagram structure. The menu choice is hazed if the loaded system file (*.sdt) or any associated configuration group file (*.scu) file is read-only. When invoked, a dialog appears:
- No group file
- Group file
- Associates a group file with this document, i.e. a Control Unit file (*.scu) will be created to hold the structural information about the document and its document substructure. In the text field, the name of the Control Unit file is specified. See "Control Unit File" on page 201 for more information.
- A check is made that the name of the control unit file given by the user is unique within the system. If not, a warning dialogue is issued, making it possible to cancel the operation and to provide a new file name.
- The group file will be shown in the Organizer view like this:
- The name of the group file is presented directly below the document name, in italics. The asterisk `*' indicates that the control unit file is dirty and needs saving. After saving, the asterisk will be removed.
- The name of the control unit file is presented directly below the document's file name.
Configuration > Update
A faster version of Configuration > Full Update. The *.scu files are only read if they have changed since the last save.
Configuration > Full Update
Updates configuration groups recursively below the selection in the Organizer. Use this menu choice to update the Organizer contents if you have a system with configuration groups loaded in the Organizer and the configuration groups have changed outside the control of the Organizer, for instance by a software configuration management system operation.
Color > Set Default Colors
Invoking this menu choice will make sure that all SDL diagram symbols are colored according to preference values (such as Editor*StateSymbolColor) instead of individual colors set with SDLE > Edit > Symbol Border Color and SDLE > Edit > Symbol Fill Color. Note that this menu choice only operates on the diagrams selected in the Organizer.
Color > Set Black and White
Same as Organizer > Edit > Color > Set Default Colors, but instead of preference values, black and white is used for all symbols.
Associate
This menu choice associates or disassociates a selected document with another document. An association symbol indicates that two document symbols are connected. (A related symbol is the dependency symbol, see "Dependencies" on page 139.)
The menu choice is hazed if the loaded system file (*.sdt) or any associated configuration group file (*.scu) file is read-only.
If an association icon is selected, this menu choice operates on the associated document, not the icon itself. Any document may be associated with any other document, and a document may have more than one associated document.
The following dialog is opened:
- Associate <document> with
- The multiple selection list displays the type and name of all documents in the Organizer structure. When the dialog is opened, all documents that the current document is associated with are selected, i.e. the list shows all its associated documents.
- By selecting a new document in the list, an association link to the current document will be created in the selected document's structure. By deselecting a document in the list, the corresponding association link will be removed from the selected document's structure.
Paste As
This menu choice is used to paste copied objects as new diagrams in the Organizer. This menu choice is only available if the system file can be changed. A root diagram is created and opened in an editor. The following transformations are possible via Paste As in the Organizer:
- An Object Model class symbol can be pasted as an SDL system diagram.
- An Object Model object symbol can be pasted as an SDL system diagram.
- A text fragment can be pasted as an MSC diagram.
For more information about the Paste As dialog, see "The Paste As Command" on page 450 in chapter 9, Implinks and Endpoints.
Go To Source
This menu choice is used to open an editor with a document according to an SDT reference. The SDT reference is specified in a dialog, see Figure 30. If the SDT reference includes information about an object in the document, that object will be selected. SDT references can be obtained by using the menu choice Show GR Reference in an editor.
For information about SDT references, see chapter 18, SDT References.
The following dialog is opened:
An error message appears if the format of the SDT reference is incorrect or if the requested SDT reference cannot be found.
Update Headings
This menu choice checks the headings of SDL, HMSC, OM, and SC diagrams for correctness with respect to what is defined in the Organizer structure.
It operates on the selected diagram and its substructure. If no diagram is selected, all SDL, HMSC, Object Model, and State Chart diagrams in the Organizer are checked. For SDL diagrams, the kernel headings are checked.
Before the headings are checked, a check is made to see if any file is connected to more than one diagram. Such files are reported in the Organizer log, and a warning box is issued to the user. These files may be modified for each appearance and will cause all but the last update to be incorrect.
The heading check is made silently until the first incorrect heading is found. The diagram checked is then shown in the dialog below. If an incorrect qualifier is found, the user is prompted in the dialog whether to update the header or not. The user also has the possibility to silently update all incorrect headings. That is, they are loaded in an editor and are then corrected without confirmation by the user.
After the operation, all updated headings are in an unsaved mode in the editor.
This operation should be done regularly in order to avoid peculiar and hard-to-find analysis error caused by incorrect diagram headings.
In SDL diagrams, qualifiers can be placed in other symbols than the heading in the system, such as qualifying data types in a text symbol. Such qualifiers are not found by the Update Headings menu choice.
The following dialog is opened:
- Current kernel heading
- A read-only text field that shows the contents of the heading as defined in the SDL, HMSC, Object Model, or State Chart diagram, i.e. what is displayed in the editor. (The Kernel Heading in SDL diagrams.)
- Correct kernel heading
- Update
- No Update
- Update All
Update Visibility
Update SDL symbol visibility according to include expressions and external synonym values.
The SDL symbol visibility can also be set manually, see "Symbol Visibility > Hide" on page 2017 in chapter 43, Using the SDL Editor and "Symbol Visibility > Show" on page 2017 in chapter 43, Using the SDL Editor.
For more information about include expressions, see "Include Expression" on page 2017 in chapter 43, Using the SDL Editor.
External synonyms are saved in a plain text file with the extension *.syn in the Organizer. To specify that the boolean external synonym variable DEBUG should have the value of true, and the boolean external synonym variable VERSIONTWO should have the value of false, the *.syn file should have the following contents:
DEBUG 1VERSIONTWO 0By using these variable names as include expressions on selected symbols, and by having a reference to the *.syn file in the Organizer, it is possible to hide or show groups of symbols by setting up the correct values in the external synonym file and applying this command. Note that the symbol visibility can not be updated in read-only diagrams.
Properties
Edit bookmark properties for a selected bookmark symbol. Location should be set to a valid SDT reference or URL. Name is any name that makes it easy to remember the place the bookmark represents. You can get valid SDT references from SDL Suite editors, by selecting a symbol and using <editor>>Tools>Show GR Reference. The easiest way to create a new bookmark with a valid SDT reference is to use <editor>>Tools>Create Bookmark.
This menu choice is only available if the system file can be changed.
View Menu
The View menu includes the following menu choices (menu choices within parenthesis are not available in short menu mode):
- Expand
- Expand Substructure
- Collapse
- (Show Sub Symbols)
- (Hide)
- View Options
- Chapter Options
- (Set Scale)
- (Show High-Level View)
- (Show Detailed View)
Expand
This menu choice expands the symbol structure tree one level down for the selected document. If any symbols one level down are hidden, they are still hidden after this operation. (Use the menu choice Show Sub Symbols to show hidden symbols.)
- No document is selected
- The selected icon is a leaf (no child icons)
- The selected diagram is not connected
- The selected icon is marked invalid
- The selected icon is already expanded
Expand Substructure
This menu choice expands the symbol structure tree the whole way down for the selected document. This also expands sub symbols that are hidden, but those sub symbols are still hidden after this operation. (Use the menu choice Show Sub Symbols to show hidden symbols.)
- The selected icon is a leaf (no child icons)
- The selected diagram is not connected
- The selected icon is marked invalid
- The selected icon is already expanded
If no document is selected, all icons will be expanded.
Collapse
This menu choice collapses the selected document, i.e. the sub symbols are not shown after this operation. A collapsed document has a small triangle drawn below the icon to indicate that it is collapsed.
- The selected icon is a leaf (no children icons)
- The selected document is not connected
- The selected icon is marked invalid
- The selected icon is already collapsed
If no document is selected, all icons will be collapsed. A collapsed document does not affect a corresponding document file opened in an editor, i.e. it does not have to be closed or saved.
Show Sub Symbols
This menu choice is used to specify which sub symbols of the selected document that should be shown or hidden. The sub symbols can be documents, instance diagrams, pages, or associations. If a More symbol is selected, the operation applies to the parent document, which becomes selected instead.
Only the sub symbols one level down from the selected document is affected, not the complete symbol substructure. The menu choice is dimmed if there is no selection or the selected symbol has no sub symbols.
The following dialog is opened:
Hide
This menu choice hides the selected non-root document and its substructure. The document and its substructure is replaced by a More symbol, which is always placed last of the symbols on that level. If such a symbol already existed in the parent document, the document is hidden under the same More symbol. The symbol's count of hidden documents is updated.
The menu choice is dimmed if there is no selection, or the selected document is a root document.
By double-clicking on the More symbol, the Show Sub Symbols dialog is opened.
View Options
This menu choice sets options for controlling the appearance of the Organizer window, as well as options for which icon attributes to show.
The options are set in a modeless dialog, i.e. the Organizer can continue working without waiting for the dialog to be closed. The options are saved in the system file.
The following dialog is opened:
The figure above shows the default settings. The settings made in the dialog are preserved as default values the next time the dialog is invoked.
Tree mode
The Tree mode section contains options for the two different tree presentation modes available in the chapters (see "Presentation Modes" on page 46).
Menu bar
The Menu bar section contains options for which menu choices that are available (see "Long and Short Menus" on page 58).
Show
The Show section contains options for which window parts, documents and file attributes to show. The options are available as items in a multiple selection list, which can be selected or deselected. Options already turned on are pre-selected when the dialog is opened.
- Association symbols
- CM Groups
- This option governs whether CM Groups should be displayed or not. By default, CM Groups are visible. However, note that they are not shown in vertical tree mode (see "Presentation Modes" on page 46).
- Dashed diagrams
- Dependency symbols
- File access permissions
- Add/remove the file access permissions for connected files. An access permission can have one of the following values:
- In list mode, the permissions are added in front of the file names, if they are shown. In tree mode, the permissions are added on a separate line under each node in the document structure tree, just above the file names if they are shown.
- File directories
- Complements the File names option below. Add/remove the directory path of the connected files, in the same location as File names. If the File names option is set, the directory path is added in front of the file name. The path added is determined by the Source Directory option; see "Set Directories" on page 71.
- File names
- In list mode: Add/remove a column of connected file names to the documents.
- In tree mode: Add/remove a line of text with the connected filename under each node in the document structure tree. The texts do not overlap; document symbols are separated to make space for the full text.
- If a document is not connected to a file, [unconnected] is shown.
- Footer file
- Show/hide the Footer File icon.
- Header file
- Show/hide the Header File icon.
- Instance diagrams
- Link file
- This option sets the visibility of the Link File icon. The link file icon is hidden by default.
- Page symbols
- Separator symbols
- Source directory
- Show/hide the Source Directory.
- Status bar
- System file
- This option sets the visibility of the System File icon. The system file icon is visible by default.
- Target directory
- Show/hide the Target Directory.
- Tool bar
- Type names
- Virtuality
Chapter Options
This menu choice is used to set chapter properties.
The first chapter number is defined in the text field. This number defines the chapter number to use for the first chapter symbol of type Chapter 1, Chapter 1.1, Chapter 1.1.1 or Chapter 1.1.1.1 in the Organizer View area. For example, if the first chapter number is specified as "3.2", then an initial chapter symbol of type Chapter 1 will get chapter number 3. If the initial chapter symbol instead is of type Chapter 1.1.1.1, it will get a chapter number of 3.2.1.1.
The maximum TOC chapter level decides which chapter symbols that will be visible in the table of contents when a print is done from the Organizer. A maximum TOC chapter level of zero will only show chapter symbols of type Chapter, while a chapter level of 4 will show all chapter symbol types in the table of contents.
Set Scale
Sets the scale (20%-800%) used in the Organizer window. The setting is saved in the system file.
Show High-Level View
Sets the current view of all diagrams in the SDL Editor to the high-level view, showing only symbols which are marked as "important".
Show Detailed View
Sets the current view of all diagrams in the SDL Editor to the detailed view, showing all symbols.
Generate Menu
The Generate menu contains the following menu choices (menu choices within parenthesis are not available in short menu mode):
- Analyze
- (Make)
- Stop Analyze/Make (UNIX only)
- Targeting Expert
- SDL Overview
- State Overview
- (CPP2SDL Options)
- (Convert to PR/MP)
- (Convert to GR)
- (Convert GR to CIF)
- (Convert CIF to GR)
- (Convert State Chart to SDL)
- (Edit Separation)
- (Dependencies)
- (Merge ASN.1)
Analyze
This menu choice analyzes the selected SDL or TTCN system. If there is no SDL or TTCN system selected, the Organizer operates on the first SDL system found in the Organizer. The menu choice is dimmed if:
- A job using the Analyzer is already running.
- No SDL diagram is present in the Organizer and no TTCN system is selected.
- The selected SDL diagram or TTCN document is not connected.
- The selected icon is marked invalid.
The Analyze SDL variant of this menu choice is described below, followed by the Analyze TTCN variant.
Analyze SDL
This menu choice starts the Analyzer for one or several related SDL diagrams. If modified information exists in the current system structure, the user should first save it. See "The Save Before Dialog" on page 65 for more information.
Any SDL diagram can be selected for analysis, but in practice at least the parent block diagram will be the source of the analysis. If no SDL diagram is selected, the first SDL diagram found in the Organizer view will be used. The diagram will be analyzed in its context and together with its substructure.
Options for the Analyzer are specified in the modal dialog below. The settings are saved in the system file and persist until the next time the dialog is invoked for the same system.
The Analyze SDL Settings
Note: Normal versus full analyze (make)
In the Analyze and the Make dialog, the user can choose between the normal Analyze/Make and the Full Analyze/Make buttons. The last used button (normal or full) will be the default when any of these two dialogs is used the next time. The last used button will also determine if normal or full analyze/make will be used when invoking operations via the quick buttons Analyze, Make, Simulate and Explore. It is possible to toggle between normal or full analyze/make by pressing <Ctrl+T>.
- Select other(s)
- When the Analyze dialog is opened, the selection in the Organizer decides the SDL diagrams that will be analyzed. The part that will be considered for analysis is the diagram itself, all diagrams below the diagram and all parent diagrams. A used package is considered to be a parent diagram. All diagrams below a used package will be analyzed.
- This button opens a sub dialog, with the possibility to analyze SDL diagrams other than the one selected in the Organizer. For instance, it is possible to analyze two out of many blocks from the same level in one SDL system. In the sub dialog, just select the diagrams that you want analyzed. Note that you only have to select the top diagram you want analyzed, all sub diagrams will be included in the analysis. The initial label in the Analyze dialog (Analyze <diagram type> <diagram name>) will change to reflect the new selections you have made.
- Using values for external synonyms from file
- Instead of having a text symbol connected to an external synonym file (*.syn), the external synonym file can be specified here. If there is at least one synonym file in the Organizer view, the one closest to the SDL system will be used as the default value. See "Supplying Values of External Synonyms" on page 2242 in chapter 50, Simulating a System for more information.
- Include hidden symbols
- Decides if hidden SDL symbols should be included in SDL/PR or not. Read more about hidden SDL symbols in Symbol Visibility > Hide and Symbol Visibility > Show.
- If hidden symbols are excluded, then lines to and from hidden symbols will also be excluded. One exception to this is that flow lines going to a symbol that will be excluded, are reconnected to the first following symbol that will be included, if there is one and only one such symbol.
- To use include expressions is another way to decide if SDL/GR symbols should be included in SDL/PR or not. Read more about include expressions in Include Expression.
- Macro expansion
- Run the Macro Expander before the analysis. (See "The Macro Expander" on page 2504 for more information.)
- Case sensitive SDL
- Syntactic analysis
- Semantic analysis
- Perform a semantic check. This option automatically sets the option Syntactic analysis.
- Pressing the Details button displays the Semantic Analysis - Details dialog. These options are only used if a semantic analysis is done. They are also not used if a system or package was not the target for the analysis. For more information on these options, see "Performing Semantic Check" on page 2622 in chapter 55, Analyzing a System.
- Check output semantics
- Check unused definitions
- Check optional parameters
- Check trailing parameters
- Check references
- Check missing else answers
- Check missing answer values
- Check parameter mismatch
- External types should call GenericFree
- Allow implicit type conversion
- Include optional fields in make operator
- Generate a cross reference file
- Generate a cross reference file when performing the analysis. In the text field, a file name is proposed with the diagram to be analyzed as prefix and .xrf as extension. The file is by default generated in the Target Directory.
- Generate a complexity measurement file
- Generate a complexity measurement file when performing the analysis. In the text field, a file name is proposed with the diagram to be analyzed as prefix and .csv as extension. The file is by default generated in the Target Directory. See chapter 48, Complexity Measurements for more information.
- Generate an instance information file
- Generate an instance information file when performing the analysis. In the text field, a file name is proposed with the diagram to be analyzed as prefix and .ins as extension. The file is by default generated in the Target Directory.
- ASN.1 encode/decode parameter
- This option decides if the ASN.1 encode/decode buffer can be accessed from SDL. If the option is on, it is also possible to specify how the ASN.1 encode/decode buffer should be represented in SDL. For more information, see "SDL Encoding and Decoding Interfaces" on page 2844 in chapter 58, ASN.1 Encoding and De-coding in the SDL Suite.
- ASN.1 keyword substitution file
- Change keywords in files output by asn1util according to file. If no file is specified, the keywords in the file asn1util_kwd.txt in the SDL Suite installation are used. For more information, see "Keywords substitution" on page 708 in chapter 13, The ASN.1 Utilities.
- Error limit
- Log expressions deeper than
- Filter command
- If used, this option allows preprocessing of files before the different analyzer phases. An executable (script), possibly with parameters, should be specified in the text field. The executable will be called before the analyzer processes any file in any phase. The executable will be called with two parameters:
- Echo Analyzer commands
- Terminate Analyzer when done
The options above are forwarded to the Analyzer when the analysis process starts.
The Analyze SDL Buttons
- Analyze
- Starts the Analyzer in the background and closes the dialog. Status information from the ongoing analysis is shown in the Organizer Log window. Among those diagrams that are considered for analysis according to the top of the dialog (Select other(s)), only the following diagrams are really analyzed:
- Full Analyze
- Has the same effect as the Analyze button, except that it forces all diagrams that are considered for analysis to be analyzed.
- Set
Analyze TTCN
This menu choice is used to analyze a TTCN system and/or to generate a Flat View for a TTCN system.
Options for the Analyze process are specified in the modal dialog below. A selectable Generate Flat View phase is executed in the analyze process. The settings are saved in the system file and persist until the next time this dialog is invoked for the same TTCN system.
The Analyze TTCN Settings
- Analyze
- Generate Flat View
- Selecting this radio button means that a Flat View will be generated for the selected TTCN system. For a detailed description of this operation, see "Generating a Flat View" on page 1205 in chapter 26, Analyzing TTCN Documents (on UNIX).
- Generate and analyze Flat View
- Enable forced analysis
- This option is described in "Enable Forced Analysis" on page 1197 in chapter 26, Analyzing TTCN Documents (on UNIX).
- Verbose report
- This option is described in "Verbosity" on page 1197 in chapter 26, Analyzing TTCN Documents (on UNIX).
- Error limit
The Analyze TTCN Buttons
- Analyze
- Starts the Analyzer and closes the dialog. Status information from the ongoing analysis is shown in the TTCN Suite log. For more information, see "The TTCN Suite Logs" on page 6 in chapter 1, User Interface and Basic Operations.
- Set
For more information about this dialog, see "The TTCN Analyzer" on page 1194 in chapter 26, Analyzing TTCN Documents (on UNIX).
See also chapter 31, Analyzing TTCN Documents (in Windows).
Make
This menu choice makes the selected SDL or TTCN system, or the selected SDL block or process diagram (see "Partitioning" on page 2643 in chapter 56, The Cadvanced/Cbasic SDL to C Compiler). If a Build Script containing commands to the SDL to C Compiler is selected, that file will be used as input to the SDL to C Compiler, without opening the Make dialog (see "Build Scripts" on page 2644 in chapter 56, The Cadvanced/Cbasic SDL to C Compiler.
If no document or file of the above mentioned type is selected, the Organizer operates on the first SDL system found in the Organizer. The menu choice is dimmed if:
- A job using the Analyzer is already running
- There is no SDL system diagram in the chapters and no TTCN system is selected
- The selected diagram is not connected
- The selected icon is marked invalid
If modified information exists in the current system structure, the user should first save it; see "The Save Before Dialog" on page 65.
The SDL Make variant of this menu choice is described below, followed by the TTCN Make variant.
SDL Make
Options for the Make process are specified in the modal dialog below. An analysis phase is executed as part of the Make process. The existing Analyzer options as set in the Analyze dialog are used.
Code Generation Options
- Select other(s)
- When the Make dialog is opened, the selection in the Organizer decides the diagrams that will be used when code is created. This is used to select a partition to build. For a description on partitioning see "Partitioning" on page 2643 in chapter 56, The Cadvanced/Cbasic SDL to C Compiler. This button opens a sub dialog, with the possibility to generate code for diagrams other than those selected in the Organizer. For instance, it is possible to generate code for two out of many blocks on the same level in one SDL system. In the sub dialog, select the diagrams that you want to include in the code generation process. Note that you only have to select top diagrams, sub diagrams will be automatically included. The initial label in the Make dialog (Make <diagram type> <diagram name>) will change to reflect the new selections you have made.
- Analyze & generate code
- Code generator
- The code generator is selected with this option menu. The following code generators are supported to date:
- Cbasic (see chapter 56, The Cadvanced/Cbasic SDL to C Compiler)
- Cadvanced (see chapter 56, The Cadvanced/Cbasic SDL to C Compiler and chapter 61, The Master Library)
- X1 (UNIX only)
- Prefix
- The type of prefix for variables is selected with this option menu: Full (default), Entity Class, No or Special. For more information, see "Prefixes" on page 2739.
- Separation
- The type of modularity is selected with this option menu: No (default), Full or User Defined. For more information, see "Selecting File Structure for Generated Code - Directive #SEPARATE" on page 2723.
- Capitalization
- The type of capitalization is selected with this option menu: Lower Case or As Defined (default). For more information, see "Case Sensitivity" on page 2741.
- Generate environment header file
- If this option is set, a header file is generated containing the definitions of the SDL system's interface to the environment. For more information, see "System Interface Header File" on page 2779.
- Generate environment functions
- If this option is set, environment functions are generated. For more information, see "The Environment Functions" on page 2776.
- Generate prefixed names in ifc file
- If this option is set, the names generated in the ifc file will avoid name clashes by being prefixed with sig_%s_%n, lit_%s_%n etc. For more information, see "Avoiding name clashes" on page 2781.
- Generate signal number file
- If this option is set, a file with signal numbers will be generated. For more information, see "Generation of Support Files" on page 2647.
- Generate ASN.1 coder
- Generate SDL coder
- If this option is set, encoders and decoders from SDL will be generated, see "Type description nodes for SDL types" on page 2793. This option is only available through a special license.
Makefile Options
- Makefile
- Generate makefile
- Generate a makefile (default). Choose the file by adding a .m extension to the separation name of the selected unit and the file is created in the directory specified as target directory. See "Target Directory" on page 71 for more information.
- Generate makefile and use template
- Generates a makefile and appends the specified, user defined, template at the end of the makefile. Two "hooks" are provided in the generated part of the makefile: USERTARGET and USERLIBRARIES. This enables the user to define his own targets as well as adding properties in the make file. The recommended file name extension for a template file is .tpm.
- In the template file, USERTARGET is used to add additional object files to the link script in the generated make file, by defining this name as a list of object files.
- In the template file, USERLIBRARIES is used to add library modules, for example -lm or -lsocket, to the link script in the generated make file, by defining this name as a list of libraries.
- The template file can also contain the compilation scripts for the object files specified as USERTARGET.
Example 2 : Contents of a UNIX Make Template File
USERTARGET = sctenv$(sctOEXTENSION)USERLIBRARIES = -lm -lsocket# Dependencies and actionssctenv$(sctOEXTENSION): sctenv.c$(sctCC) $(sctCPPFLAGS) $(sctCCFLAGS) \$(TARGETDIRECTORY) sctenv.c \$(sctIFDEF) -o sctenv$(sctOEXTENSION)Compile & Link Options
- Compile & link
- Standard kernel
- Use one of the available standard kernels. The kernel is selected from this option menu. The available kernels depend on the license configuration.
- Each kernel is available in versions for different compilers. You should use a kernel corresponding to a compiler you have access to on your system.
- On UNIX, the following kernels are available. There are versions for standard ANSI C compilers (e.g. cc) and for the GNU C compiler (gcc).
- Simulation
- gcc-Simulation
- RealTimeSimulation
- gcc-RealTimeSimulation
- PerformanceSimulation
- gcc-PerformanceSimulation
- Application
- gcc-Application
- ApplicationDebug
- gcc-ApplicationDebug
- Validation
- gcc-Validation
- TTCN-Link
- gcc-TTCN-Link
- Microsoft Simulation
- Microsoft RealTimeSimulation
- Microsoft PerformanceSimulation
- Microsoft Application
- Microsoft ApplicationDebug
- Information about the kernels can be found in "Compilation Switches" on page 3121 in chapter 61, The Master Library and "Libraries" on page 2772 in chapter 57, Building an Application2. A list of the available kernels can also be found in the file sdtsct.knl (see "File sdtsct.knl" on page 3143 in chapter 61, The Master Library).
- Use kernel in directory
- Preprocess C file
- This option informs the SDL to C Compilers if the SDL C Compiler Driver (SCCD) should be invoked. See chapter 60, SDL C Compiler Driver (SCCD) for more information.
Miscellaneous Options
- Target directory
- This option is by default set to Target Directory. This option determines where the generated files will be put in the file system.
- File name prefix
- ASN.1 coder prefix
- The names of the generated encode/decode functions will be prefixed by the text put in this field. In the generated ASN.1 coder structures 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, ... );Dialog Buttons
For information about how Make/Full Make relates to Analyze/Full Analyze and quick buttons, see "Normal versus full analyze (make)" on page 114.
- Make
- Starts the code generation in the background and closes the dialog. Status from the ongoing Make process is shown in the Organizer Log window. First the time stamps of the SDL files, e.g *.sbk, *.spr, *.spd, etc, are compared with all their dependent generated c-file counterparts. Only those diagrams that have a newer timestamp are converted from SDL GR to PR, analyzed, and code is generated. After any needed code is generated the make function corresponding to the specified compiler is called to compile and/or link the system. Situations where a make will prove useful are when the following circumstances exist:
- Full Make
- Has the same effect as the Make button, except that it forces the entire system to be regenerated, even if only certain parts needs to be regenerated. After any needed code is generated the make function corresponding to the specified compiler is called to compile and/or link the system.
- Set
- Analyze Options
TTCN Make
This menu choice is used to make (generate code, compile and link) a TTCN system.
For more information about this operation, see chapter 27, The TTCN to C Compiler (on UNIX) or chapter 32, The TTCN to C Compiler (in Windows).
Stop Analyze/Make (UNIX only)
This menu choice stops an ongoing analyze/make operation. The Analyzer tool is also stopped. (The Analyzer tool normally remains resident in memory for the rest of the SDL Suite session once the first analyze/make is performed, and this menu choice is then renamed to Stop Analyzer. Using this menu choice is one way to free memory if needed.) Several commands, such as Analyze, Make, Convert to PR/MP and Convert to GR, are not available when the Analyzer is processing data. Stopping the Analyzer enables these commands again.
A message with the essence "Analyzer could not be stopped" may be issued as a response to this command; in this case, repeat the menu choice until the message "Analyze/make stopped" is issued in the message area.
Targeting Expert
This menu choice starts the Targeting Expert tool. See chapter 59, The Targeting Expert for more information.
SDL Overview
This menu choice generates an SDL overview diagram for the selected SDL diagram as the top diagram. The menu choice is dimmed if:
- No SDL diagram is present in the Organizer.
- The selected SDL diagram is not connected.
- The selected icon is marked invalid.
- The system file is read-only.
If modified information exists in the current system structure, the user should first save it; see "The Save Before Dialog" on page 65.
Any SDL diagram can be selected for generation. If no SDL diagram is selected, the first SDL diagram found in the Organizer view will be used.
- Name of Generated SDL Overview
- Use Expanded Diagrams Only
- Include Procedures & Operators
- Include States
- Include Lines
- Minimum Symbol Width
- Minimum Symbol Height
- Margin
- Distance between Lines
- Distance between Symbols
- Generate
- Causes the generation of the overview diagram to start. The user is informed about the progress of the generation in the Organizer Log window. The generated SDL Overview is added as a root document directly after the SDL structure for which the Overview diagram is generated. An SDL Editor opens and presents the Overview diagram.
State Overview
This menu choice is used to generate a state overview information file from an SDL system or a group of state charts. The state overview can be viewed either as state matrices in the Text Editor or as state charts in the State Chart Editor.
Before selecting this menu choice, make sure that the information source (an SDL system or one or more state charts) is selected directly or indirectly. For instance, you can select a group of state charts by selecting the chapter symbol that contains the state charts.
When you select this menu choice, a dialog is displayed where you can:
- Decide if the information source should be SDL or state charts.
- Change SDL system, if several SDL systems were selected in the Organizer. Use the first change button for this.
- Pick out individual state charts, among the state charts that were selected in the Organizer. Use the second change button for this.
- Decide name and directory for the generated state overview information file.
- Decide if an Organizer symbol should be created.
- Decide if the Text Editor should show the state overview information as state matrices.
- Decide if the State Chart Editor should show the state overview information as state charts.
CPP2SDL Options
This menu choice is available if a C or C++ Import Specification is selected. For more information, see "The CPP2SDL Tool" on page 765 in chapter 14, The CPP2SDL Tool.
Convert to PR/MP
This menu choice converts the selected diagram/document to textual form. SDL/GR is converted to SDL/PR and TTCN-GR is converted to TTCN-MP. If no diagram/document is selected, the Organizer operates on the first SDL system found in the Organizer. The menu choice is dimmed if a job using the Analyzer is already running.
The Convert to PR (SDL) variant of the menu choice is described below, followed by the Convert to MP (TTCN) variant.
Convert to PR (SDL)
The SDL variant of the Convert to PR/MP menu choice generates a formatted (pretty printed) SDL/PR file. Input is either an SDL/PR file or an SDL/GR diagram structure.
If modified information exists in the current system structure, the user should first save it; see "The Save Before Dialog" on page 65.
- Source:
<type> <name>
- Converts an SDL/GR diagram structure to PR. The top of the diagram structure appears in the name of the button.
- If an SDL diagram is selected, that diagram will be converted. Otherwise, the first SDL diagram structure found in the Organizer will be converted. If no SDL diagrams are found, this option is dimmed, in which case the name of the button is "<No SDL/GR diagram selected>". This will also be the case if the SDL diagram is not connected, or if its icon is marked invalid.
- If the SDL diagram to be converted has an expanded diagram substructure visible in the Organizer, this substructure is also converted. All PR code is put in the destination PR file.
- PR file
- Generates a pretty printed PR file from an existing PR file, which is specified in the input field. By default, this file is read from the Source Directory.
- Write reserved words in
- Expand included PR files
- Destination PR file name
- Specifies the pretty printed PR file to generate. The default name uses the selected diagram name as prefix and .sdl as extension. By default, this file is stored in the Target Directory.
- If no file name is provided, the user is warned and no conversion is performed.
- An Overwrite confirmation dialog is issued if the user changes the suggested file name and specifies a file that already exists.
- Convert
- Analyze Options
- Opens the Analyze dialog to set the analyze options. The Set button returns to the Convert to PR/MP dialog.
Convert to MP (TTCN)
This TTCN variant of the Convert to PR/MP menu choice converts a TTCN-GR document to a TTCN-MP text file.
For more information about Convert to MP, see "Exporting a TTCN Document to TTCN-MP" on page 1156 in chapter 24, The TTCN Browser (on UNIX) or "Converting to TTCN-MP" on page 1297 in chapter 30, Editing TTCN Documents (in Windows)
Convert to GR
This menu choice converts a textual file to one or more graphical diagrams. A TTCN-MP file is converted to TTCN-GR diagrams, and an SDL/PR file is converted to SDL/GR diagrams. The menu choice is dimmed if a job using the Analyzer is already running.
The Convert to GR (SDL) variant is described below, followed by the Convert to GR (TTCN) variant.
Convert to GR (SDL)
The Convert to GR dialog is in SDL mode when the radio button Convert SDL/PR to SDL/GR is on (see Figure 42).
- Source PR file name
- Write reserved words in
- Expand included PR files
- Destination directory for generated SDL/GR
- Specifies the directory where to put the generated SDL diagrams. By default, the Source Directory will be used (see "Set Directories" on page 71).
- Convert
- Analyze Options
- Opens the Analyze dialog to set the analyze options. The Set button returns to the Convert to GR dialog.
The Convert to GR command can be used to import SDL systems created using Object Geode. However, Object Geode allowed some extended SDL syntax that is not accepted by the SDL Suite Analyzer.
Convert to GR (TTCN)
The Convert to GR dialog is in TTCN mode when the radio button Convert TTCN-MP to TTCN-GR is on (see Figure 42).
For more information about the Convert to GR dialog in TTCN mode, see "Importing a TTCN-MP Document" on page 1161 in chapter 24, The TTCN Browser (on UNIX) or "Converting to TTCN-MP" on page 1297 in chapter 30, Editing TTCN Documents (in Windows).
Convert GR to CIF
This menu choice converts SDL/GR diagrams to the Common Interchange Format (CIF).
On UNIX, the Convert GR to CIF dialog is opened. For more information, see "Convert GR to CIF Dialog (UNIX only)" on page 908 in chapter 16, CIF Converter Tools.
In Windows, the SDT2CIF converter tool is started. For more information, see "Graphical User Interface (Windows only)" on page 910 in chapter 16, CIF Converter Tools.
Convert GR to Tau/Developer CIF
This menu choice generates a CIF file for an SDL system that should be imported into IBM Rational Tau. The command is a shortcut for the Convert GR to CIF command where it is only needed to specify the system file and the resulting CIF file. The functionality is the same as running Convert GR to CIF with the following options:
Convert CIF to GR
This menu choice converts diagrams in Common Interchange Format (CIF) to SDL/GR diagrams.
On UNIX, the Convert CIF to GR dialog is opened. For more information, see "Convert CIF to GR Dialog (UNIX only)" on page 893 in chapter 16, CIF Converter Tools.
In Windows, the CIF2SDT converter tool is started. For more information, see "Graphical User Interface (Windows only)" on page 894 in chapter 16, CIF Converter Tools.
Convert State Chart to SDL
This menu choice transforms the selected State Chart to an SDL process diagram. For more information, see "Converting State Charts to SDL" on page 1706 in chapter 39, Using Diagram Editors.
Edit Separation
This menu choice inserts or edits a separation on the selected SDL diagram. It is dimmed if the selected diagram type is not one of system, system type, block, block type, process, process type, procedure, and package. This menu choice is only available if the system file can be changed.
Diagram separation symbols are used during code generation and controls both the splitting of the target into separate modules and the naming of these modules. For more information, see "Selecting File Structure for Generated Code - Directive #SEPARATE" on page 2723 in chapter 56, The Cadvanced/Cbasic SDL to C Compiler. Separations can be shown in the diagram structure of the Organizer; see "Separator symbols" on page 109. Information about separations are stored in the system file.
Dependencies
This menu choice introduces or removes dependencies between a selected document and other documents. A dependency symbol below a document indicates that the document is depending on another document. For instance, if an SDL system is depending on an ASN.1 document, then the SDL system must be re-analyzed each time the ASN.1 document is updated. A related symbol is the association symbol, see "Associate" on page 98.
This menu choice is only available if the system file can be changed.
If a dependency icon is selected, this menu choice operates on the document the dependency icon is referring to, not the icon itself. Any document may depend on any other document, and a document may have be depending on more than one document.
The following dialog is opened:
- Select documents depending on <document>
- The multiple selection list displays the type and name of all documents in the Organizer structure. When the dialog is opened, all documents that the current document is depending on are selected, i.e. the list shows all dependencies for the document.
- By selecting a new document in the list, a dependency for the current document will be created. By deselecting a document in the list, the corresponding dependency link will be removed from the selected document's structure.
Merge ASN.1
This menu choice controls whether the ASN.1 files in an Organizer module should be merged (joined) into a single SDL package or not. For more information, see "Using the ASN.1 Utilities" on page 703 in chapter 13, The ASN.1 Utilities.
- No ASN.1 merge
- Merge ASN.1, separate name
- The ASN.1 files in this Organizer module should be merged; one SDL package will be generated, containing all ASN.1 modules from the ASN.1 files. The name of the SDL package will be the same as the name of the Organizer module, and the separate name will be used for the code generation in a similar way as for ordinary ASN.1 files.
Tools Menu
The Tools menu contains the following menu choices:
- Organizer Log
- Link > Create Endpoint
- Link > Traverse
- Link > Link Manager
- Link > Clear Endpoint
- Search
- Spelling > Comments
- Spelling > All Text
- Change Bars
- Compare > SDL Diagrams
- Compare > MSC Diagrams
- Compare > HMSC Diagrams
- Merge > SDL Diagrams
- Merge > MSC Diagrams
- Merge > HMSC Diagrams
- Split
- Join
- Compare State Machines
- Simulator Test > New Simulator
- Simulator Test > Existing Simulator
- Editors > Deployment Editor
- Editors > HMSC Editor
- Editors > MSC Editor
- Editors > OM Editor
- Editors > SDL Editor
- Editors > State Chart Editor
- Editors > Text Editor
- Editors > TTCN Browser
- SDL > Type Viewer
- SDL > Coverage Viewer
- SDL > Index Viewer
- SDL > Simulator UI
- SDL > Explorer UI
- SDL > Target Tester UI
- TTCN > Find Table
- TTCN > Access
- TTCN > Simulator UI
- Preference Manager
Organizer Log
This menu choice raises the Organizer Log window. The Organizer Log window can be raised automatically when the user performs an analysis or other forms of generation. There is only one Organizer Log window.
The Organizer Log window is described in "Organizer Log Window" on page 184.
Link > Create Endpoint
This menu choice creates an endpoint for the selected document. A document with an endpoint is recognized by a small triangle in the upper left corner of the document symbol. See "Link > Create Endpoint" on page 446 in chapter 9, Implinks and Endpoints.
This menu choice is only available if the system file can be changed.
Link > Traverse
This menu choice traverses a link for the selected document. A document with at least one link is recognized by a small black triangle in the upper left corner of the document symbol. See "Link > Traverse" on page 446 in chapter 9, Implinks and Endpoints.
Link > Link Manager
This menu choice opens the Link Manager's main window. For more information about the Link Manager, see "The Link Manager" on page 464 in chapter 9, Implinks and Endpoints.
Link > Clear Endpoint
This menu choice removes an existing endpoint for the selected document. See "Link > Clear Endpoint" on page 449 in chapter 9, Implinks and Endpoints.
This menu choice is only available if the system file can be changed.
Search
This menu choice searches for text in SDL, MSC, HMSC, Object Model, and State Chart diagrams. Textual documents (C Header, Text ASN.1, and Text Plain) are also searched if the Text Editor is used. (The Text Editor is used if the preference variable SDT*TextEditor is set to "SDT.") It is not possible to search in TTCN, Word, Tau/Rhapsody or Generic documents with this menu choice. To search in TTCN documents, use TTCN > Find Table.
The document scope of the search depends on the selection:
- If a module is selected, all searchable documents in that module will be searched.
- If a chapter is selected, all searchable documents in that chapter will be searched.
- If a root document is selected, all searchable documents in that document's substructure will be searched.
- If there is no selection, all searchable documents in the Organizer will be searched.
The menu choice is dimmed if the selected document is not a root document, not connected, or marked invalid.
The search will only take place in diagrams that are connected and do not have an invalid status. The search will start in the selected diagram and continue in top-down order for the rest of the diagrams (the order is left-right in a tree view).
The search function will go through the list of diagrams and stop each time the search criteria, as set in the dialog below, matches. If a search/replace string or any option is changed when the search is stopped (a match is found or the user pressed Abort), these values become the basis when the search is continued.
The search process will open an editor window, if necessary, and select the matched search text.
The searching is based on ASCII character matching. All text fragments in symbols are searched, with a few restrictions (see below).
When all diagrams have been searched, a beep is issued and the message Search completed appears.
Dialog Fields and Options
The Search dialog contains the following fields and options.
- Search for
- Replace with
- Search in
- Consider case
- Wildcard search
- Search substructure
- Whole word search
Only the textual elements that are visible in an MSC will be searched. See "Diagram Options" on page 1680.
Dialog Buttons
When the dialog is first opened, all buttons except Replace&Search and Replace All are enabled. When Search, Replace&Search or Replace All is pressed all fields and buttons are disabled except the Close button. (The Close button changes name during the search to Abort.) If a search string is found in an editor, it is selected and all buttons and fields are enabled.
When the first search or replace operation has been applied and control returns to the Search dialog, it is possible to perform a new search on the same diagram(s).
- Search
- Searches for the search string. An editor is opened when the search string is found. If no text is supplied in the Search for field, a warning message appears. Confirming the message box will return control to the Search dialog.
- Replace&Search
- Replace All
- Close/Abort
Search Restrictions
All data in the editors that affects the diagram structure maintained by the Organizer (primarily reference symbols and kernel headings in the SDL Editor) is regarded as read only during the search operation. That is, they are not affected by the search.
Externally editing (i.e. through means other than using replace) of a diagram during a search operation completely resets the search, i.e. the next search starts from the first diagram.
The search may fail if dialogs are opened in the editor during the search. In this case the editor blocks the continuation of the search process. To continue the search process, the editor dialog must be closed.
The Organizer's data is locked during the search process. This is normally not noticed since the Search dialog is modal, but the SDL Editor needs to access that data to perform operations affecting the diagram structure. The Organizer will deny the editor's requests to modify the data structure. The duration of the search process is the period of time during which the Search dialog is visible in the Organizer.
Fast Search
Fast search is invoked by pressing Ctrl+F on the keyboard.
Fast search behaves like normal search, except that:
- No dialog is used.
- The replace functionality can not be used.
- Consider case is always off.
- Wildcard search is always off.
- Search substructure is always on.
When Fast search is invoked, the message area displays the text that will be searched for. Initially, the text is Search for:. When you type on the keyboard with the mouse pointer over the drawing area, the characters will turn up in the message area. When you have typed the text pattern to search for, press enter or return to start the search operation.
The same search operation as for normal Search is used. If the search operation finds a match, you can search for another match by pressing enter or return once more in the Organizer window.
To finish the Fast search operation, click in the drawing area or select another operation.
The next time Fast search is invoked with Ctrl+F, the search text that was used the last time is proposed as a search text once more. To use it, press enter or return. To use another search text, press Ctrl+F once more or the delete key several times, to erase the search text.
Spelling > Comments
Check the spelling of comments in selected diagrams. Comments can be either comment symbols or /* C-style comments */
.
For spelling errors, the Spelling dialog appears, with the following possibilities:
- Word replacement text field. Initially, the word from the diagram is presented here. One way to correct the spelling mistake is to correct the spelling in this text field and press the change button.
- List of suggestions. For most words, the spelling checker will present possible corrections here. Click on a word in this list to update the word replacement text field. Double-click on a word to update the diagram.
- Add button. Add the word currently in the word replacement text field to your personal dictionary.
- Change button. Update the diagram with the word from the word replacement text field and find the next spelling error.
- Ignore button. Ignore the current spelling error and find the next spelling error.
- Ignore All button. Ignore all occurrences of the current spelling error during this session and find the next spelling error. For more "permanent ignorance", use the Add button.
Spelling > All Text
Works in the same way as Spelling > Comments, but all text is checked instead of just comment texts.
Change Bars
This menu choice is used to control the usage of change bars in SDL diagrams. A dialog with two options is opened:
- Reset change bars for selected SDL diagrams
- This option is used to reset change bars in SDL diagrams that fall under the selection in the Organizer. Note that removing a change bar makes the diagram dirty, i.e. change bars cannot be removed from diagram files where you do not have write access. If this option is on, a second dialog will be opened telling you about the diagrams that the operation will be applied upon.
- Create change bars when SDL changes occur
- This option is used to decide if change bars should be created when an SDL diagram is edited. This option is saved in the system file and is valid for all SDL diagrams in the system. The preference ChangeBars is used as default for new SDL systems. See "ChangeBars" on page 249 in chapter 3, The Preference Manager.
Compare > SDL Diagrams
This menu choice compares the contents of SDL diagram file pairs. A diagram file pair is constructed by matching an SDL diagram file loaded into the Organizer with an SDL diagram file with the same name, but in a different directory.
There is a similar operation in the SDL Editor for comparing one SDL diagram pair at a time. See "Compare Diagrams" on page 2030 in chapter 43, Using the SDL Editor.
The menu choice is dimmed if there are no SDL diagrams in the Organizer.
In the same way as for the Search menu choice, the compare operation is limited by the selection in the Organizer. Only SDL diagrams within the scope of the selection will be considered for the compare operation.
When the Compare SDL Diagrams menu choice is invoked, the compare SDL diagrams setup dialog appears.
In the compare SDL diagrams setup dialog, the following input parameters to the compare operation can be specified:
- Compare source directory
- The directory specified here is used instead of the normal source directory to find SDL diagrams to compare the SDL diagrams in the Organizer with.
- For SDL diagrams in the Organizer that are relative to the normal source directory, the relative part of the file path is kept, but the part of the file path that matches the normal source directory is replaced with a part of a path constructed from the diff source directory instead.
- For example, if the source directory is /home/lat (E:\home\lat in Windows) and the diff source directory is /opt/home/gn (E:\opt\home\gn), then the Organizer file /home/lat/demo/x.ssy (E:\home\lat\demo\x.ssy)
will be compared with /opt/home/gn/demo/x.ssy (E:\opt\home\gn\demo\x.ssy), if that file exists.- For SDL diagrams in the Organizer that are not relative to the normal source directory, the directory part of the file path is replaced with diff source directory.
- Textual difference report: Summary
- Textual difference report: Details
- Graphical difference report
- Ignore moved or resized objects
- When this option is chosen, the compare operation tries to ignore reporting differences only caused by moved or resized symbols by using symbol ids. This option should only be used when comparing two versions of the same original diagram file: moved symbols cannot be accurately detected by using symbol ids when comparing two versions of a diagram that are both built from scratch.
- Select and print differences
When the OK button in the dialog is pressed, the Organizer checks if a matching diagram can be found for all SDL diagrams in the operation. If that is not the case, a dialog appears to inform about this fact.
Finally, the real compare operation starts in the SDL Editor. Read more about this in "Compare Diagrams" on page 2030 in chapter 43, Using the SDL Editor.
Compare > MSC Diagrams
This menu choice compares the contents of MSC diagram file pairs in the same way as "Compare > SDL Diagrams" on page 149 does. Read more about this in "Compare Diagrams" on page 1694 in chapter 39, Using Diagram Editors.
Compare > HMSC Diagrams
This menu choice compares the contents of HMSC diagram file pairs in the same way as "Compare > SDL Diagrams" on page 149 does. Read more about this in "Compare Diagrams" on page 1694 in chapter 39, Using Diagram Editors.
Merge > SDL Diagrams
This menu choice compares the contents of SDL diagram file pairs in the same way as "Compare > SDL Diagrams" on page 149 does. The main difference is that this menu choice gives the possibility to merge differences: For each diagram pair, a new merge result diagram is created. Read more about how the actual merge is performed in "Merge Diagrams" on page 2031 in chapter 43, Using the SDL Editor.
Merge > MSC Diagrams
This menu choice compares the contents of MSC diagram file pairs in the same way as "Compare > MSC Diagrams" on page 152 does. The main difference is that this menu choice gives the possibility to merge differences: For each diagram pair, a new merge result diagram is created. Read more about how the actual merge is performed in "Merge Diagrams" on page 1694 in chapter 39, Using Diagram Editors.
Merge > HMSC Diagrams
This menu choice compares the contents of SDL diagram file pairs in the same way as "Compare > HMSC Diagrams" on page 152 does. The main difference is that this menu choice gives the possibility to merge differences: For each diagram pair, a new merge result diagram is created. Read more about how the actual merge is performed in "Merge Diagrams" on page 1694 in chapter 39, Using Diagram Editors.
Split
This menu choice is used to split one SDL diagram into two SDL diagrams. This menu choice can be applied several times to split one SDL diagram into several parts. This menu choice is, together with the menu choice Join, useful in situations where several people have to work simultaneously on one SDL diagram. The SDL diagram file is partitioned into several SDL diagram files and each person is given one part to work on.
To split an SDL diagram consisting of several pages, select the diagram symbol in the Organizer and select the Split menu choice. (It is also possible to select a page symbol associated with the diagram that should be split.)
A dialog appears with a list of all pages but the first one in the diagram, see Figure 48. Select a page to define how the SDL diagram should be split. All pages before the selected page will end up in the first SDL diagram part. The selected page and all pages after the selected page will end up in the second SDL diagram part.
The Split button in the first Split dialog closes the dialog and brings up the second Split dialog, as shown in Figure 49. The second Split dialog is used to specify the files that the two resulting SDL diagram parts should be saved in.
When the second Split dialog is closed with the Save button, the split operation is performed: The SDL Editor is loaded with the SDL diagram that should be split. Two new smaller SDL diagrams are created in the SDL Editor and saved under the file names specified in the second Split dialog.
The visible result of the Split operation is that the SDL Editor contains at least the diagram that was split and the resulting SDL diagram parts. Note that no additional symbols are created in the Organizer. The SDL diagram parts are accessed by opening the SDL diagram part files in the SDL Editor with the Open menu choice. It is of course possible to manually add symbols for the SDL diagram parts in the Organizer with for instance the Add Existing menu choice.
Join
This menu choice is used to join two SDL diagrams of the same type into one SDL diagram. This menu choice is, together with the Split menu choice, useful when several people have to work on the same SDL diagram at the same time.
Note that it is not necessary to do a Split before doing a Join. One way to work in parallel on the same diagram is to let one designer work on the existing SDL diagram, while another designer creates new pages destined for the same SDL diagram, in a new SDL diagram with the same type as the existing SDL diagram. A join operation when the parallel work is finished puts the new SDL pages in the correct SDL diagram.
The resulting SDL diagram is produced by copying the complete first diagram part and merging/joining pages from the second diagram part by copy and paste. This means that information that is common for all pages in an SDL diagram is taken from the first diagram part. This includes:
- The diagram name and any other information in the header.
- The information in the extended heading symbol.
- The information in the use text symbol.
Another consequence of this way of working is that duplicate page names and reference symbol names emerging from the second diagram part are changed by the join operation to make them unique. Auto-numbered pages from the second diagram part will also have their names changed.
When the Join menu choice is invoked, the Join dialog appears, see Figure 50.
In the dialog, specify the names of the two SDL diagram files that should be merged. Pressing the Join button will close the dialog and start the Join operation.
The result of the Join operation is that three diagrams will be loaded in the SDL Editor; the two SDL diagram parts that act as input to the Join operation and a new and unsaved SDL diagram that contains all the pages from both the input diagrams. The first thing that you will normally do after a Join operation is to save the new SDL diagram in a file. After that, it might be appropriate to check the new SDL diagram in the context of the SDL system with the Analyzer.
Compare State Machines
This menu choice is used to compare state machines with other state machines. This menu choice makes it possible to keep state machines expressed as a group of state charts consistent with state machines expressed as processes in an SDL system.
Before selecting this menu choice, make sure that the information sources (SDL systems and/or state charts) are selected directly or indirectly. For instance, to compare the only SDL system in the Organizer with all state charts in the Organizer, make sure that there is no selection in the Organizer by clicking in the background. The Organizer will interpret this as "everything is selected".
When you select this menu choice, a dialog is displayed where you can:
- Specify the two groups of state machines that should be compared. A group of state machines is either the state machines in an SDL system or a group of state charts. It is only possible to choose among the state machines that were selected in the Organizer. Use the Select buttons to select individual SDL systems or state charts.
- Specify the two state overview information files that will be generated and compared.
- Specify if SDL procedure calls and/or state chart call actions should be compared.
- Specify if SDL outsignals and/or state chart send events should be compared.
When the dialog is closed, two state overview information files are generated. A state overview describes a state machine in a normalized form:
- For an SDL system, diagram type inheritance and diagram type instantiation have been removed.
- For a state chart, state hierarchies (states in states) have been removed. The same rules as when converting a state chart to SDL are used, for more information, see "Converting State Charts to SDL" on page 1706 in chapter 39, Using Diagram Editors.
The compare operation compares the two generated state overview information files in the following way:
- State machines are matched by their names. For instance, SDL process A is matching state chart A.
- States are matched by their names.
- Transitions are matched by a combination of from-state name, insignal name and to-state name
.
If the compare operation finds anything that does not match, this is reported in the Organizer Log. You use the Organizer Log quick button Show Error to navigate to the SDL diagram or state chart with an entity that did not match anything in the other group of state machines.
Simulator Test > New Simulator
This menu choice is used to execute test cases in the simulator for an SDL system. Test cases can be described either as MSCs or as simulator UI input scripts (*.cui). A description of how to express MSCs in this context can be found in Using MSCs as test cases.
When this menu choice is invoked, a dialog appears with a list of all MSCs and input scripts. In the dialog, it is possible to select test cases that should be executed. The selection in the Organizer decides:
When the dialog is closed, an SDL simulator is generated and each selected test case is run. When all test cases have been executed, the Organizer Log will contain a one-line summary for each test case, with information about if the test case passed or failed. For test case failures, the MSC editor will pop up, showing the symbol in the MSC that failed (this happens only if the test case was expressed as an MSC). To be able to examine test case failures in detail, run each test case that fails separately, because then the MSC editor will show the place of the MSC test case failure and the textual output from the simulator will contain information about the test case failure.
Using MSCs as test cases
MSC test cases are MSCs written in a special way. MSC test cases are high-level test cases that are auto-converted to low-level simulator UI input script test cases before they are executed.
When MSCs are used as test cases, you can:
- send in a signal to the system and check that the expected signal is received as a response from the system.
- check that a process instance is in a certain state.
- check that a process instance variable has a certain value.
- check if a process instance exists.
- ...
Figure 51 illustrates MSC test case building blocks that are described in the text below.
MSC instance symbols are used in the following way in MSC test cases:
- Use an MSC instance symbol called environment or env_1 or something similar as an instance to send and receive signals to and from the SDL system.
- By using an .itt file other instances than environments can be mapped to act as an environment during testing. See "Mapping Instances to Different Environments" on page 2232 in chapter 49, The SDL Simulator.
- Use one or several MSC instance symbols to represent the SDL system. If you use one instance, give it the same name as the SDL system (for instance accesscontrol). If you use several instances, give each the name of an SDL process instance that you want to send and receive signals to and from (for instance panel or panel:1).
To send a signal into the system, draw an MSC signal from the environment instance to one of the instances representing the SDL system. Specify the signal name and any parameters that you know about.
To check that a signal is sent out from the system, draw an MSC signal from an instance representing the SDL system to the environment instance. Also here, you should specify the signal name and any parameters. The check is done by matching a text string created from the MSC with the actual textual output from the simulator. You can use the * character (matching any characters) if you for instance do not want to specify all parameters in the MSC.
MSC test scripts can check for unexpected signals sent to the environment. If unexpected (unchecked) signals are detected before the currently checked signal the test case will fail and a message will be displayed:
Unexpected signal(s) to environment arrived before currently checked signal:* OUTPUT of DSignal to env:1* OUTPUT of ASignal to env:1If unexpected (unchecked) signals are detected after the last checked signal in the script the test case will fail and a message will be displayed:
Unexpected signal(s) to environment arrived after last checked signal:* OUTPUT of CSignal to env:1Make sure that the script will run sufficiently long after the last checked signal, for the unexpected signals to arrive at the environment and be detected. This can for example be achieved with a finite number of "next-state" commands at the end of the test script. The statistics displayed after the test script has executed have been updated to show unexpected signals as follows:
Command statistics:checked: 2failed: 0updated: 0unexpected: 2There are several overlapping ways of specifying the process instance a signal should be sent to or from. Two of them involves a mapping table in an MSC text symbol. The text should look something like this (one line with a `=' for each mapping rule):
process id mappings:instance accesscontrol = panelsignal display = panel
- First of all, the SDL Suite finds out if there is a comment symbol connected to the signal. If there is, and the text is something like to panel or from panel, the SDL Suite uses panel as the process instance name (with :1 added because no : with a number was specified).
- Second, the SDL Suite finds out if there is a signal mapping rule matching the current signal name. If there is, the process instance name in that rule is taken.
- Third, the SDL Suite finds out if there is an instance mapping rule matching the instance name of the instance representing the SDL system that is attached to the current signal. If there is, the process instance name in that rule is taken.
- If no process instance name has been found yet, then the MSC instance name of the instance representing the SDL system is taken as the SDL process instance name. If a qualifier exists in the instance kind text this will be added to the name.
It is possible to include any simulator command in an MSC test script by attaching an MSC action symbol to the environment instance, and typing the simulator commands in it. One line for each command.
This can for instance be used to declare macros representing parameter values. If you have done add-macro myMacroName 5 in an action symbol, you can type $myMacroName instead of 5 as the value of a parameter. Macros can be defined in a separate MSC and used in normal MSC test cases. Just make sure that the macro MSC is executed before the normal MSC test cases when you do a simulator test.
There are three textual shortcuts that can be used in an action symbol:
- To check that an SDL process instance is in a certain state:
check state (panel) = IDLE- To check the value of a variable in an SDL process instance:
check variable (panel) DoorNo = 1- To check if an SDL process instance exists or not:
check exists (panel) = falseThe MSC reference symbol can be attached to the environment instance. Type in a name of a sub MSC test script that should be executed. This is a way to avoid repeating the same information in many places. It can for instance be used in the beginning of a test script to perform common initialization of the system.
Simulator Test > Existing Simulator
Same as "Simulator Test > New Simulator" on page 157, except that an already created simulator is used. Before the normal simulator test dialog (used to specify test cases to execute), a file selection dialog appears, where a simulator executable can be specified.
Editors > Deployment Editor
Adds a Deployment diagram symbol to the Organizer view, and starts the Deployment Editor. The symbol is added at the same place as when using the Add New command.
Editors > HMSC Editor
Adds a HMSC diagram symbol to the Organizer view, and starts the HMSC Editor. The symbol is added at the same place as when using the Add New command.
Editors > MSC Editor
Adds an MSC diagram symbol to the Organizer view, and starts the MSC Editor. The symbol is added at the same place as when using the Add New command.
Editors > OM Editor
Adds an Object Model diagram symbol to the Organizer view, and starts the OM Editor. The symbol is added at the same place as when using the Add New command.
Editors > SDL Editor
Adds an SDL System diagram symbol to the Organizer view, and starts the SDL Editor. The symbol is added at the same place as when using the Add New command.
Editors > State Chart Editor
Adds a State Chart diagram symbol to the Organizer view, and starts the State Chart Editor. The symbol is added at the same place as when using the Add New command.
Editors > Text Editor
Adds a Plain Text document symbol to the Organizer view, and starts the Text Editor. The symbol is added at the same place as when using the Add New command.
Editors > TTCN Browser
Adds a TTCN module symbol to the Organizer view, and starts the TTCN Browser. The symbol is added at the same place as when using the Add New command.
SDL > Type Viewer
This menu choice starts the Type Viewer. It is dimmed if there is no SDL diagram in the Organizer, or if the preference SDT*StartInformationServer is set to false. Only one instance of the Type Viewer exists. If the Type Viewer has already been started, its window is raised.
If a Referenced Diagram Type icon, an Instance Diagram icon or a Dashed diagram icon is selected in the Organizer, the Type Viewer selects the corresponding symbol when this menu choice is used.
The Type Viewer is described in chapter 45, The SDL Type Viewer.
SDL > Coverage Viewer
This menu choice starts a Coverage Viewer. A new instance of the Coverage Viewer is started each time this command is selected.
The Coverage Viewer is described in chapter 47, The SDL Coverage Viewer.
SDL > Index Viewer
This menu choice starts an Index Viewer. A new instance of the Index Viewer is started each time this command is selected.
The Index Viewer is described in chapter 46, The SDL Index Viewer.
SDL > Simulator UI
This menu choice starts a new, empty Simulator UI. Several Simulator UI's may exist at the same time.
The Simulator UI is described in "Graphical User Interface" on page 2201 in chapter 49, The SDL Simulator.
SDL > Explorer UI
This menu choice starts a new, empty Explorer UI. Several Explorer UI's may exist at the same time.
The Explorer UI is described in "Graphical User Interface" on page 2351 in chapter 52, The SDL Explorer.
SDL > Target Tester UI
This menu choice starts a new, empty SDL Target Tester UI. The SDL Target Tester UI is described in "Graphical User Interface" on page 3658 in chapter 67, The SDL Target Tester.
TTCN > Find Table
This menu choice invokes the find table operation on a selected TTCN system. In Windows, this functionality is not available and the menu choice is dimmed.
For more information about the find table operation on UNIX, see "TTCN Suite Preprocessor" on page 1209 in chapter 26, Analyzing TTCN Documents (on UNIX). For more information about finding tables in Windows, see "Finding and Sorting Tables" on page 1286 in chapter 30, Editing TTCN Documents (in Windows).
TTCN > Access
This menu choice starts a TTCN Access application for a selected TTCN document/system.
For more information, see chapter 21, TTCN Access.
TTCN > Simulator UI
This menu choice starts a TTCN simulator UI.
For more information about this, see chapter 28, The SDL and TTCN Integrated Simulator (U) or chapter 33, The SDL and TTCN Integrated Simulator (W).
Preference Manager
This menu choice starts the Preference Manager. Only one instance of the Preference Manager exists. If the Preference Manager has already been started, its window is raised.
The Preference Manager is described in chapter 3, The Preference Manager.
Bookmarks Menu
The Bookmarks menu contains the following menu choices:
Add Bookmark
This menu choice opens a dialog where a new bookmark can be created. The information needed is the location (a URL or a SDTREF), and a name for the bookmark. If desired, a systemfile can be specified that will be loaded together with the SDTREF.
Edit Bookmarks
Edit Bookmarks will open a dialog with a list with all bookmarks. After selecting a bookmark the buttons will have the following effect:
- OK - all changes made will be saved and the dialog will close.
- Open - the selected bookmark will be opened
- Edit - provides a dialog with the information form the selected bookmark, where the information can be edited.
- Remove - removes the selected bookmark from the list.
- Cancel - all alteration made will be disregarded and the dialog will be closed.
More Bookmarks
This choice will appear if more than 25 bookmarks are present. The dialog appearing is the same as in the Edit Bookmark menu choice. Selecting the desired bookmark and clicking on the Open button will open the bookmark.
Help Menu
For more information about Help menus, see "Help Menu" on page 15 in chapter 1, User Interface and Basic Operations. Two of the Organizer Help menu choices are described in more detail below.
About All
This menu choice starts an operation that presents version information about the individual tools in your SDL Suite configuration. The information is presented in the Organizer Log window. The produced information might look like this:
About All. Version information:Help Tool Version 6.3.0Link Manager Version 6.3.0MSC Editor Version 6.3.0OM InfoServer Version 6.3.0OM/SC/HMSC/DP Editor Version 6.3.0Organizer Version 6.3.0Preference Manager Version 6.3.0SDL Coverage Viewer Version 6.3.0SDL Editor Version 6.3.0SDL Index Viewer Version 6.3.0SDL Type Viewer Version 6.3.0SDT Welcome Window Version 6.3.0Text Editor Version 6.3.0About All. Additional version and kernel information:Information Server version 6.3.0SDT AnalyzerSDT Analyzer 6.3.0SDT CPP2SDL 6.3.0ASN.1 Analyzer 6.3.0SDL Targeting Expert: Version 6.3.0Simulation kernel:2 lrwxrwxrwx 1 nnn sdl 66 May 5 16:05 sctworld.oRealTimeSimulation kernel:2 lrwxrwxrwx 1 nnn sdl 68 May 5 16:05 sctworld.o...License Information
Opens a dialog with license information for all SDL Suite and TTCN Suite tools.
The dialog contains the following:
- The names of the tools that are included in SDL Suite and TTCN Suite and that are separately licensed.
Message Sequence Chart Editor and High-Level Message Sequence Chart Editor
SDT-X1 (UNIX only)
Package licenses, see "Description of packages" on page 43 in chapter 5, Licensing Management
1 The SDT-X is a generic name that allows to introduce new code generators that are under development. In "normal" installations, it has no meaning.
1
- On UNIX, beneath each tool, the following information is displayed:
- A Give Up License button which allows you to release the interactive licenses in your current SDL Suite session.
- A Get License button which allows you to reclaim licenses released by either the use of the Give Up License button or the automatic release of licenses.
- Licenses will be automatically released if the idle time limit, set in the preference LicenseTimeout, is exceeded. For more information, see "LicenseTimeout" on page 244 in chapter 3, The Preference Manager.
- The reclamation of licenses is limited in the sense that it will only attempt to reclaim lost licenses once, implying that you will have to save your work in and restart the tools for which licenses could not be obtained.
- A Configure License button which allows you to configure package licenses. See "Set up and change a Package license" on page 44 in chapter 5, Licensing Management.
X is reserved for future extensions in the SDL Suite applied to code generation.
2The TTCN-Link kernel is described in the TTCN Suite manuals.
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |