Table of Contents Previous Chapter 5 System Setup

5 System Setup

In this chapter, you will find information about what startup scripts and what OS environment variables SDT takes advantage of. Also, you may find information about X Window and OSF/Motif factors that may affect the behavior of SDT. Some of the setup information in this chapter is applicable on a user level and may thereby be required to be performed by each SDT user.

Startup Scripts

The startup of SDT 3.0/3.01/3.02 is slightly changed compared to previous versions of SDT. All SDT applications that are possible to start from the UNIX prompt are invoked via commands in the $telelogic/bin directory ($telelogic is the SDT installation root directory). By adding this directory to the user's PATH he will be able to start all SDT applications with exception for stand-alone generated Simulators and Validators; please see section "Source Files" on page 54.

The start script $telelogic/bin/.tlwrapper is a common start script for Telelogic products that make use of SDT's integration mechanism, the PostMaster.

The SDT specific part is then setup by the SDT local $telelogic/sdt/bin/.wrapper script, which finally starts the correct application.

---------------------------------------------------------------
Caution!                                                         
The .tlwrapper and .wrapper scripts should never be invoked      
manually; they are only supposed to be executed via the SDT com  
mands.                                                           
---------------------------------------------------------------
--------------------------------------------------------------------
Command       Description                                             
--------------------------------------------------------------------
sdt           Start SDT and raise the Organizer window.               
sdtbatch      Start SDT in batch mode, without graphical user         
              interface. To be used with additional parameters -p     
              for print, -a for analysis, and -m for make. For more   
              information, see "SDT Batch Facilities" on page         
              1150 in chapter 22, The SDT Organizer, in the vol       
              ume SDT 3.01 Reference Manual.                          
sdtprint      Stand-alone print, corresponds to sdtbatch -p           
sdtsan        Start SDT Analyzer stand-alone (textual mode). See      
              "The Analyzer Command-Line UI" on page 1541 in          
              chapter 31, The Analyzer, in the volume SDT 3.01        
              Reference Manual.                                       
sdtconfig(a)  Start configuration of the SDT installation.            
startlicd     Start license server. See chapter 4, The Software       
              License Server for more information.                    
stoplicd      Stop license server. See chapter 4, The Software        
              License Server for more information.                    
updatelicd    Reread the license.dat file, useful after the license   
              file has been edited. See chapter 4, The Software       
              License Server for more information.                    
stat          Show statistics about the license server, useful        
              optional parameters [-a | -A | -f `feature']            
              See chapter 4, The Software License Server for more     
              information.                                            
configlicda   Configure the SDT start script to, by default, use      
              another license file than                               
              $telelogic/license.dat See chapter 4, The Soft          
              ware License Server for more information.               
--------------------------------------------------------------------
(a)
This command is normally only performed during the Installation Procedure.

User Setup

For each SDT user, the following setups should be made.

Source Files

The SDT installation provides a file which is suitable to be "sourced" at login, when executing the user's .cshrc or .profile file. This source file will make the following environment variables visible in the terminal shell:

telelogic
sdtrelease
sdtdir
sdtbin
These environment variables are useful for the SDT users. They can easily be used as pointers into the SDT installation, without knowing were the installation is placed in the file system.

------------------------------------------------------------------
Note:                                                               
A generated Simulator or Validator needs these environment vari     
ables to be set up, if it is run from the UNIX prompt without the   
graphical user interface.                                           
------------------------------------------------------------------
Example 7 : Using SDT Environment Variables  
  ls $sdtrelease/examples
  ls $sdtrelease/include/ADT
  ls $sdtrelease/doc
  
To read the source file (/appl/telelogic is assumed to be the root directory for the SDT installation):

source /appl/telelogic/bin/telelogic.sou
. /appl/telelogic/bin/telelogic.profile

Path and Display Variables

For each user, the SDT 3.02 bin directory should be contained in the list of directories defined by the PATH environment variable:

set path = ( $path $telelogic/bin )
This should be done in the shell startup files, as described above.

In the case the computers on which you run the X Windows server and the client (the SDT applications) coincide, the environment variable DISPLAY should be set to unix:0.0 before starting SDT. Do not use the notation hostname:0.0

Environment Variables

Preferences

The default behavior of the SDT tools may be specified using the SDT Preference Manager. You may define preferences in such way that they apply to an entire company, a specific project that uses SDT, or to an individual user only. See chapter 5, Managing Preferences in the volume SDT 3.01 User's Guide for how to customize SDT with the Preference Manager.

X Window System Factors

Display Resolution

SDT relies on the display resolution reported by the X Server for mapping between screen (pixel) coordinates and diagram unit coordinates. If the X Server has erroneous resolution information, the screen image of an SDT document will have the wrong scale.

If required, the X Server must be adjusted to report the correct display resolution. See the documentation from the computer / software vendor for how to do this.

Installed Fonts

SDT assumes that the fonts included in the MIT distribution of X11R5 are available.

Font Scaling

To achieve WYSIWYG between screen and printout, SDT can use scalable fonts in conjunction with AFM (Adobe Font Metrics) files. Not all fonts scale well without the use of an X11R5 font server. Therefore, it is possible to turn off font scaling (at the price of the WYSIWYG capabilities), in which case SDT will try to use only pre-scaled X fonts.

To turn off font scaling, the Preference Manager is used. See chapter 30, The Preference Manager for a reference to handling of preferences in SDT.

X Server Version

SDT has been tested with the MIT X11R5 server. No interoperability with earlier or later versions of X11 is guaranteed.

Window Manager

SDT is tested with Mwm, the OSF/Motif window manager. It is the recommended window manager to use with SDT.

Color Allocation

In the case of another X application having allocated all available color cells, SDT might fail to allocate colors for its windows and icons. SDT will try to allocate colors as close as possible to the ideal in the case of icons, but window colors cannot be guaranteed. To avoid this problem, a user might consider closing color-intensive applications that are not necessary to run in conjunction with SDT.

Changing the Color Settings

The color settings for SDT are specified in the file: $sdtrelease/X11lib/app-defaults/SDT. The colors can be changed by modifying the color resources settings; the color settings are found at the end of this file. When changing the colors you may find some help about usable color names in the file: $sdtrelease/X11lib/rgb.txt

Please find the work order of how to modify resources in section "Work Order for Modifying SDT resources", below.

OSF/Motif Factors

Event Translations

The X resource file SDT uses both OSF/Motif virtual bindings and ordinary X event specifications in translation tables. Refer to the OSF/Motif documentation for a discussion of virtual bindings.

Work Order for Modifying SDT resources

Modification of SDT resources is only recommended to users who have good knowledge about the X Window System.

  1. Exit SDT.
  2. Copy the default SDT resource file to a local directory (e.g. $HOME/Resources)
cp $sdtrelease/X11lib/app-defaults/SDT \ 
$HOME/Resourses/SDT
  1. Edit your local SDT file to change the appropriate resources.
vi $HOME/Resources/SDT
  1. Specify that SDT should use your local resource file, in one of the following ways:
setenv XAPPLRESDIR $HOME/Resources
setenv XUSERFILESEARCHPATH \ 
$XAPPLRESDIR/%N:$HOME/Resources/SDT
setenv XUSERFILESEARCHPATH \ 
$XUSERFILESEARCHPATH:$HOME/Resources/SDT
  1. Restart SDT:
sdt

The system.mwmrc File

The /usr/lib/X11/system.mwmrc file is the default Motif Window Manager startup file. In this file, which contains definitions of the button bindings and the root menu, your system manager may, for instance, add a menu choice for starting SDT.

Any user can override the settings in this file by creating his own .mwmrc file in his login directory.

-----------------------------------------------------------------
Note:                                                              
On SUN workstations you will find the system.mwmrc file in the     
SDT distribution. This file is placed in $telelogic/X11lib and     
is only used if you run the X Window and Motif software provided   
by SDT.                                                            
-----------------------------------------------------------------

The app-defaults/Mwm File

The /usr/lib/X11/app-defaults/Mwm file contains the default resource specifications for Motif Window Manager. This file contains the names of the button bindings which are defined in the system.mwmrc file, mentioned above.

If you want to add resources to Mwm, you can create your own .Xdefaults in your home directory, containing your personal resource definitions.

Example 8 : Changing Pointer Focus Policy  
For example, to indicate the current window by pointing to it with the cursor, instead of clicking in the window, add the following line to .Xdefaults

Mwm*keyboardFocusPolicy:      pointer.
  
------------------------------------------------------------------
Note:                                                               
On SUN workstations you will find the Mwm file in the SDT distribu  
tion. This file is located in $telelogic/X11lib/app-defaults        
and is only used if you run the X Window and Motif software pro     
vided by SDT.                                                       
------------------------------------------------------------------
 
Table of Contents Next Chapter