CHAPTER 2

Installing TimingDesigner
®
These instructions describe the installation procedure for TimingDesigner .

Configuration requirements
Before you install the software, take a moment to check your system
configuration. Following is the minimum system configuration needed to install
and use the software:

Operating Disk
Type system RAM space Other
Window PC Windows 2000/ 32MB 100MB • A parallel printer port (Windows
XP/Vista/Win7 locked licenses only) or a USB
port
• Internet access
Linux Red Hat Linux 32MB 80MB • X11R45 or later with most
Enterprise window managers
• Internet access
Sun Solaris 10 32MB 100MB • OpenWindows 3.x, or X11R4
Microsystems or later with most window
managers, including the
OpenLook Window Manager
(olwm) and the Motif Window
Manger (mwm)
• Internet access

Unless we need to note an exception, we use “UNIX” to refer to the Linux and
Solaris operating systems and “Windows” to refer to all supported versions of the
Windows operating system.

An overview of the installation process

There are basically two steps to the installation process: installing software and
authorizing the software to run. How you complete these steps is dependent
upon the type of license you have.
You can have one of two different types of licenses—floating and Windows
locked:
License type Solaris Linux Windows See
“Basic steps for floating
Floating Yes Yes Yes
licenses” on page 24
“Basic steps for Windows
Windows locked Yes
locked licenses” on page 25

Chapter 2 TimingDesigner 9.25

21 Installing TimingDesigner TimingDesigner User’s Guide
 Your system may have one type or a combination of different types of licenses.
Note the following about the procedures on the following pages:
• In the installation process, system-level procedures require that you have
system and licensing administration experience and rights as well as
familiarity with your operating system.

• $TDDIR (UNIX) or <install_dir> (Windows) indicates the installation directory.

In the procedures, be sure to replace these variables with your installation
directory.

Basic steps for floating licenses

Floating licenses are platform independent.
Therefore, you will typically find them on
networks that contain both UNIX- and Windows-
based clients.
Whether you are on a UNIX-only, Windows-only,
or mixed-platform system, the steps for installing
the software and setting up floating licenses
involve configuration at both the system level
and the user level:
1. Read “About the license manager” on page
25.
Floating Licenses
2. software on
Install the software. You can install the
the server node or any client’s machine
where you plan on running it. You do not have to install the software on the
same machine as the license manager.

See either “Installing the software on a UNIX system” on page 26 or

“Installing the software on a Windows system” on page 28.
3. Obtain your license information; see “Obtaining a license” on page 28.
4. At the system level, configure the license manager on your server node:
• If you will be using a UNIX-based server node, see “At the system level:
Configuring the license manager on your server node (UNIX)” on page
30.

• If you will be using a Windows system for the server node, see “At the
system level: Configuring the license manager on your server node
(Windows)” on page 32.

5. At the user level, configure each client’s machine upon which the software
will be run so that it can access the floating licenses; see “At the user level:
Accessing the floating licenses” on page 35.

Chapter 2 TimingDesigner 9.25

22 Installing TimingDesigner TimingDesigner User’s Guide
 About the license manager

When you start up the software, it first checks to see if it is authorized to run. It
does this by contacting the license manager daemon (or, license server). The
daemon, located on your server node, tracks the number of sessions
concurrently running on your network. If the daemon reports that a license is
available, it grants you a license and the software starts.
The software uses the Macrovision FLEXnet Licensing Module (FLEXnet) to
implement and track floating licenses. The most common floating license
configuration is to run the FLEXnet license manager daemon on a UNIX server
node for a network that supports both UNIX and Windows users (clients).
Configuring the license manager is the same whether your users are UNIX-
and/or Windows-based.
If you do not have a UNIX server node, you can configure the license manager
on a Windows server node.
A typical license manager installation consists of the following components:

Component Location on Unix Location on Windows

License file STDDIR/FLEXnet/licenses/ <install_dir>\FLEXnet\licenses\license.
[Link] dat
License manager STDDIR/FLEXnet/<platform>/ <install_dir>\FLEXnet\<platform>\bin\lm
daemon bin/lmgrd [Link]
Vendor daemon STDDIR/FLEXnet/<platform>/ <install_dir>\FLEXnet\<platform>\bin\e
bin/emalmd [Link]

Note: TimingDesigner requires version 10.1.3 of the FLEXnet Licensing Module.

Earlier versions used version 9.5 of FLEXlm, the predecessor to FLEXnet. In
order to use TimingDesigner, the FLEXnet license manager daemon (lmgrd) and
the EMA vendor daemon ($TDDIR/<platform>/bin/emalmd) must be at version
10.1.3 or later.
Note: If you need additional information about using the Macrovision FLEXnet
Licensing Module, refer to the FLEXnet Licensing End User Guide at
<install_dir>/ FLEXnet/[Link].

Basic steps for Windows locked licenses

Windows locked licenses are available on Windows-based

systems via a FLEXid hardware key. The FLEXid hardware
key is commonly a USB key, but can also be a parallel port
key.
Windows Locked Licenses
The steps for installing the software and setting up Windows
locked licenses are as follows:
1. Install the software; see “Installing the software on a Windows system” on
page 28.
2. Configure each user’s machine upon which the software will be run; see
“Setting up a Windows locked license” on page 38.

Chapter 2 TimingDesigner 9.25

23 Installing TimingDesigner TimingDesigner User’s Guide
 If you are upgrading from a previous version

If you are upgrading from a previous version, follow the installation instructions
appropriate to your platform and license type.
While the new version can open files created with previous versions, previous
versions generally cannot open files created with the new version.
If you have a floating license, you must obtain a new license. If you have not
received a new license from EMA Design Automation, see “Obtaining a license”
on page 28.
Note that the emalmd vendor daemon distributed with TimingDesigner 9.0 will
not license previous versions of TimingDesigner. If you try to start a previous
version with the new emalmd daemon, you’ll receive an “encryptioned
handshake failed with vender daemon emalmd” error. If you want to run both
versions, you must be licensed using servers that run on separate machines.
If you have a Windows locked license with a FLEXid hardware key, you will need
to obtain a new license from EMA Design Automation, see “Obtaining a license”
on page 28.

Installing the software on a UNIX system

Besides system administration experience, the following procedures assume that
you are using a C shell (csh) command interpreter. If this is not the case, be sure
to translate the literal commands given to the appropriate commands for your
shell.
• To install the software

1. Create a directory for your installation.

For example:
mkdir /usr/local/ema

cd /usr/local/ema

Make sure the directory will be readable from the hosts of all potential
users. Users do not need write access to this directory.
2. Do one of the following:

If you are obtaining the software from our web site:

• Download the archive from the site.

• Extract the software:

tar -xzf td.<platform>.<version>.[Link]

If you are obtaining the software from a CD-ROM:

Chapter 2 TimingDesigner 9.25

24 Installing TimingDesigner TimingDesigner User’s Guide
 • Insert the CD-ROM into the drive, and mount as needed.

• Extract the software.

tar -xzf /<cdrom_path>/td.<platform>.<version>.[Link]

3. Set the environment variable TDDIR to point to the installation.

Your installation will be under a directory of the form:

<install_dir>/td.<platform>.<version>

For example:
/usr/local/ema/[Link].9101

You can set your environment variable to this directory:

setenv TDDIR /usr/local/ema/[Link].9101

4. Modify each user’s environment. Add the following initialization steps to

each user’s .login files, replacing <install_dir> with the installation
directory:

setenv TDDIR <install_dir>

set path = ($path $TDDIR/bin)

Users may use the command td to run TimingDesigner. You may want
to examine the $TDDIR/bin/td script for any changes appropriate for your
site.
5. The software is now installed. Continue with “Obtaining a license” on
page 28.

Installing and accessing required libraries

Unix systems require access to specific libraries. It is likely that your system
already has these libraries. Please verify the following:
1. On Solaris systems, verify that /usr/lib/X11, /usr/sfw/lib, and /usr/local/lib are
added to LD_LIBRARY_PATH.
2. On both Solaris and Linux systems, verify that the following libraries are
installed:
• zlib ([Link])
• gthread-2.0 ([Link])
• glib-2.0 ([Link])
• Xrender ([Link])
• Xrandr ([Link])
• Xfixes ([Link])
• Xcursor ([Link])
• Xinerama ([Link])
• freetype ([Link])
• fontconfig ([Link])

Chapter 2 TimingDesigner 9.25

25 Installing TimingDesigner TimingDesigner User’s Guide
 Installing the software on a Windows system
You can obtain the software from our web site or a CD-ROM. If you are installing
on a Windows server node, you must have network administration experience
and rights to create directories and files on the network drive.
• To install the software

1. Download the software from our web site. Or, if you’ve obtained the
software from a CD-ROM, insert the CD-ROM into the drive

2. Double-click the td.win32.<version>.exe file.

3. Follow the instructions in the installation program.

4. The software is now installed. Continue with “Setting up floating licenses”

on page 28 (if you have floating licenses) or “Setting up a Windows
locked license” on page 38.

Setting up floating licenses

Setting up floating licenses requires obtaining your license file, configuring the
license manager on your server node, and configuring each user’s machine so
that it can access the floating licenses.
Before you begin, be sure you have read “Basic steps for floating licenses” on
page 24 and “About the license manager” on page 25.

Obtaining a license

Before you begin configuring the license manager, you need a license file, which
contains the license information that you will need when you configure the
license manager on your server node.
• To obtain a license

1. To obtain a license file, contact the Licensing group at EMA Design

Automation (e-mail update@[Link]). In order to expedite the
process as much as possible, please provide the following information:

• The name, mailing address, phone, fax, and e-mail address of the
individual to whom the license(s) are registered or to whom the
license(s) should be registered.

• The FLEXnet hostname and hostid of the license server(s).

Redundant servers are supported. If the licenses are distributed
among more than one set of FLEXnet servers, please specify which
licenses are to be authorized on each specific server set.

Chapter 2 TimingDesigner 9.25

26 Installing TimingDesigner TimingDesigner User’s Guide
 For details on obtaining the hostname and hostid, see “How to
gather the hostname and hostid for your license request” on page
29.
• If the licenses were purchased directly from EMA Design
Automation: Provide any one of the following for the license(s) being
installed:

- Your purchase order number(s)

- EMA Design Automation invoice number(s)
- The order number(s) (from the paperwork enclosed with the
shipment)

• If the license(s) were obtained through a third party, such as a VAR:

Provide the corporate name of the third party.

• If you are obtaining a change request for an existing authorization:

Provide the feature or featureset number (from the existing license
file or by choosing Help>License Info).

2. After you e-mail the information to update@[Link], we will send

you the license.

How to gather the hostname and hostid for your license request

The steps for gathering the hostname and hostid are different for UNIX and
Windows licensing.
For UNIX licensing:
• Hostname of the license server node—To obtain the hostname, execute
the following command on the server node on which you’re planning to run
the license manager:

/bin/uname -n

• Hostid of the license server node—To obtain the hostid, execute the
following command on the server node on which you’re planning to run the
license manager:

$TDDIR/FLEXnet/<platform>/bin/lmhostid

For Windows licensing:

• Hostid of license server node (Ethernet address or FLEXid hardware
key) — The license manager requires a unique hostid for the Windows
server node. If you are using an Ethernet address for the server node’s
hostid, execute the following command:

<install_dir>\FLEXnet\win32\bin\lmutil lmhostid

The resulting address value will be a 12-character string containing hex

digits.
Ordinarily, the Ethernet address from the Windows server node’s network
hardware is used as the hostid. The advantage of this method is that it
requires no new hardware.

Chapter 2 TimingDesigner 9.25

27 Installing TimingDesigner TimingDesigner User’s Guide
 • Hostid of license server node (FLEXid hardware key) — A FLEXid
parallel port or FLEXid USB authorization key can be used to provide a
unique hostid for the Windows server node. If you are using an authorization
key for the server node’s hostid, locate the hostid of the authorization key
printed on the key’s label. It is an 8 or 12-character hexadecimal number.

The advantage of this method is that it lets you move your license server
node to a different computer without obtaining new license files.
Or, if you already have a FLEXid key to support FLEXnet licensing for
another company’s products, you can use the key you already have.
Otherwise, a key must be ordered separately from EMA Design Automation.

At the system level: Configuring the license manager on your server

node (UNIX)
Once you receive your license file with authorization codes, you are ready to
configure the license manager on your server node.
• To configure the license manager

1. After receiving the license information from EMA Design Automation’s

Technical Support, install it on your system.
In order to decide where to install the license file, you need to understand
where the software will look for the file. First, if there is a
EMALMD_LICENSE_FILE environment variable set, the software will use it
to find the license file. If it is unset or cannot be used to find a license file, it
will use LM_LICENSE_FILE. If neither can be used to find a license file, it will
look for the license file in the default location
$TDDIR/FLEXnet/licenses/[Link].
The method you use to install the license file depends upon which of the
following three scenarios fits your particular situation:
• Your users will not have a EMALMD_LICENSE_FILE or
LM_LICENSE_FILE environment variable set. In this case, place the
license information in a file named
$TDDIR/FLEXnet/licenses/[Link]. If you wish to place your license
file in a location other than under the installation directory, you can
create a symbolic link at $TDDIR/FLEXnet/ licenses/[Link] that
points to the actual license file. When you are finished, continue with
step 2 below.

• Your users will access a single license file, which may contain
license information for other vendors using FLEXnet; the users will
reference the license file using the EMALMD_LICENSE_FILE or
LM_LICENSE_FILE environment variable. In this case, integrate the
new license information with the existing license file referenced by
EMALMD_LICENSE_FILE or LM_LICENSE_FILE. Once you have
added the new license information, use the following command to cause
the license manager to re-read the license file:

Chapter 2 TimingDesigner 9.25

28 Installing TimingDesigner TimingDesigner User’s Guide
 lmreread -c <license_file>

where <license_file> is the full path to the license file ($TDDIR/FLEXnet/

licenses/[Link]). When you are finished, continue with steps 2, 5,
and 6 below (skip steps 3 and 4).
• Your users will access more than one license file, and want to use the
EMALMD_LICENSE_FILE or LM_LICENSE_FILE environment variable to point to
each separate license file. In this case, start a separate license daemon for your new
software, as described in steps 2 and 3 below. Place the new license information in a file
such as $TDDIR/FLEXnet/licenses/ [Link]. All users will need to update their
EMALMD_LICENSE_FILE or LM_LICENSE_FILE environment variable; see “At the user
level: Accessing the floating licenses” on page 35.

2. If the license manager daemon ([Link]) and the vendor daemon

([Link]) are located in the same directory, you can skip this step and
continue with the next step. Otherwise, you need to tell the license manager
where the vendor daemon is located by entering the actual path to the
emalmd daemon in the license file:
• In the license file, locate the line for the emalmd daemon. It will contain
the following location for the daemon:

DAEMON emalmd $TDDIR/bin/emalmd

• To specify the path to the emalmd daemon, replace $TDDIR with your
installation path. For example, if you’ve set TDDIR to /usr/local/td, enter
the following:

DAEMON emalmd /usr/local/td/bin/emalmd

3. Start the license manager daemon by hand. Check for the appropriate
feature check out, and observe any error messages.
cd $TDDIR/FLEXnet/<platform>/bin
./lmgrd -c <license_file>

Replace <license_file> with the location of your license file (/usr/local/td/

FLEXnet/licenses/[Link], for example).
Examples of the correct messages are as follows:
2/10 8:45 (lmgrd) FLEXnet (v10.1.3) started on
<hostname>
2/10 8:45 (lmgrd) CONNECTED, master is <hostname>
2/10 8:45 (lmgrd) Started emalmd
2/10 8:45 (emalmd) Server started on <hostname> for:
2/10 8:45 (emalmd) TimingDesigner

4. Add the lmgrd command to the system startup files, if desired.

In the following commands, replace <license_file> with the location of your
license file, and set TDDIR to your installation directory.

Solaris:
Insert the following into an appropriately named file in the /etc/rc2.d directory:
#
# Macrovision FLEXnet Licensing Module
#

Chapter 2 TimingDesigner 9.25

29 Installing TimingDesigner TimingDesigner User’s Guide
 TDDIR=/usr/local/td
if [ -f $TDDIR/FLEXnet/<platform>/bin/lmgrd ]; then
$TDDIR/FLEXnet/<platform>/bin/lmgrd -c <license file> -l
/var/
log/[Link]
echo -n ’ lmgrd’
unset TDDIR
fi

Linux:
Insert the following into an appropriately named file in the /etc/rc.d directory:
#
# Macrovision FLEXnet Licensing Module
#
TDDIR=/usr/local/td
if [ -f $TDDIR/FLEXnet/<platform>/bin/lmgrd ]; then
$TDDIR/FLEXnet/<platform>/bin/lmgrd -c <license file> -l
/var/
log/[Link]
echo -n ’ lmgrd’
unset TDDIR
fi

5. To ensure FLEXnet starts back up correctly, use the lmdown command to

shut down FLEXnet and perform cleanup functions. The lmdown command
is located in $TDDIR/FLEXnet/<platform>/bin.
For more information about the lmdown command and other FLEXnet
administration commands, refer to the FLEXnet documentation
at<install_dir>\FLEXnet\[Link].
6. The license manager is now configured. Continue with configuring each
user’s system; see “At the user level: Accessing the floating licenses” on
page 35.

At the system level: Configuring the license manager on your server

node (Windows)
Once you receive your license information file with authorization codes, you are
ready to create the license file and configure the license manager on your
Windows server node. FLEXnet v7.0+ has a tool (LMTOOLS) that allows you to
configure your machine for Services. Services allows the license manager to run
in the background as long as the Windows machine is turned on, regardless of
who is logged onto it.
In the following procedure, we assume that you are familiar with using the
Macrovision FLEXnet Licensing Manager. In addition, we assume that you are
setting up a dedicated license manager for your EMA products. If you have
questions about FLEXnet or if you want to combine the license manager with
other products’ licenses, refer to the FLEXnet documentation
at<install_dir>\FLEXnet\[Link].

Chapter 2 TimingDesigner 9.25

30 Installing TimingDesigner TimingDesigner User’s Guide
 Creating the license file

After receiving the license information from EMA Design Automation’s Technical
Support, create the license file and install it on your system.
Note: Because Wordpad automatically saves all files with a .txt extension, use a
different text editor (e.g. Notepad) to create and save your license file or make
sure you rename the file appropriately after you save it.
• To create the license file

1. Create Create a text file (e.g., named [Link]) and save it in the
location of your choice.

2. Edit the license information to include only the server, daemon, and
feature information between the Begin and End comment lines. It will
look something like this:

# Begin: EMA Design Automation License File Generated:

21 May 2007

SERVER myserver 550003ef 1701

DAEMON emalmd <install_dir>/bin/emalmd
FEATURE TimingDesigner emalmd 9.199 31-aug-2007 1
SUPERSEDE \ ISSUED=21-may-2007 SIGN=855481A20D2A

# End: EMA Design Automation License File Generated: 21

May 2007
#

3. If the license manager daemon ([Link]) and the vendor daemon

([Link]) are located in the same directory, you can skip this step
and continue with the next step. Otherwise, you need to tell the license
manager where the vendor daemon is located:

• Locate the line for the emalmd daemon. For example:

DAEMON emalmd <install_dir>/bin/emalmd

• To specify the path to the emalmd daemon, replace <install_dir>/bin/

emalmd with the location of the emalmd daemon. For example:

DAEMON emalmd "c:\Program

Files\EMA\TimingDesigner\FLEXnet\win32\bin\[Link]"

4. Save the edited file. You are now ready to configure the license
manager.

Chapter 2 TimingDesigner 9.25

31 Installing TimingDesigner TimingDesigner User’s Guide
 Configuring the license manager

After creating the license file, you are ready to configure the license manager.
• To configure the license manager

1. Choose Start>All Programs>EMA>LMTools to start the LMTOOLS utility.

2. Click the Service/License File tab, if needed.

3. Choose the Configuration using Services option.

4. Click the Config Services tab, then set up the service name, license
manager file, and license file:

• Select a new Service Name and name it EMA Design Automation

License Manager.

• Use the Browse button to locate and enter the path to the license
manager daemon ([Link]) that came with the software.

• Use the Browse button to locate and enter the path to your license
file ([Link] or [Link]) that contains your authorization codes.

• Use the Browse button to create the debug log file

(c:\FLEXnet\EMA_license.log, for example).

• Choose the Use Services option.

• Choose the Start Server at Power Up option.

5. Click the Save Service button, and answer Yes to save the settings.

6. Click the Start/Stop/Reread tab, then:

• Select the EMA Design Automation License Manager from the list of
Services.

• Click the Start Server button. The status message in the lower left
corner reads, “Server Starting.”

7. To check that the license manager is set up and running, click the Server
Status tab. Click Perform Status Enquiry to check the status of the
license manager and the license file being used. You should see lines
similar to the following:

License server status: 1701@myserver

License file(s) on myserver: c:\FLEXnet\[Link]

8. Choose File>Exit to exit the LMTOOLS utility.

9. Your license manager is now configured. To allow individual users to

access the floating license, continue with “At the user level: Accessing
the floating licenses” on page 35.

Chapter 2 TimingDesigner 9.25

32 Installing TimingDesigner TimingDesigner User’s Guide
 At the user level: Accessing the floating licenses
Once you’ve configured the license manager on your server node, each user
must be able to access it. In order to access a product license, you need to set
the EMALMD_LICENSE_FILE or LM_LICENSE_FILE environment variable so
FLEXnet can find the license manager.
Note: If you have more than one license file that needs to be accessed using
LM_LICENSE_FILE, the value of LM_LICENSE_FILE in the steps below will
consist of a list of values separated by colons (:) on UNIX or semi-colons (;) on
Windows. For example:
UNIX: <value1>:<value2>:...<valuen>

Windows: <value1>;<value2>;...<valuen>

EMALMD_LICENSE_FILE and LM_LICENSE_FILE environment variables are

set using the same syntax. If your LM_LICENSE_FILE is used to license several
other tools, you may want to put the TimingDesigner-specific entries in the
separate EMALMD_LICENSE_FILE environment variable. The following
information can be used for LM_LICENSE_FILE or EMALMD_LICENSE_FILE.
For more information, refer to the FLEXnet documentation
at<install_dir>\FLEXnet\[Link].
• To set LM_LICENSE_FILE (UNIX)

1. To access the license file, set the LM_LICENSE_FILE environment

variable to the appropriate value. Usually, you’ll want to set the value in
your startup script, so that it is persistent. The value can take one of two
forms:

• If the license file is visible from your machine, you can enter the path to
the file. For example, if the license file is visible as
/usr/licenses/[Link], add the following line to your startup script:

setenv LM_LICENSE_FILE /usr/licenses/[Link]

:$LM_LICENSE_FILE

• If you don’t have access to the license file or you don’t want to directly
reference the license file, you must know the name of the server node
running the license manager (lmgrd) and the TCP/IP port number used
for your license file. This information appears on the SERVER line of the
license file. For example, if the server line in the license file looks like
this:

SERVER myserver 550003ef 1701

add the following line to your startup script:

setenv LM_LICENSE_FILE 1701@myserver:$LM_LICENSE_FILE

If you don’t know what your default startup script is, ask your system
administrator.

2. Your new software is ready to be used. As a final test, start up the

software to confirm that the license file is being properly accessed.

Chapter 2 TimingDesigner 9.25

33 Installing TimingDesigner TimingDesigner User’s Guide
 • To set LM_LICENSE_FILE (Windows)

1. Go to the Environment Variables dialog box:

• (Windows XP/Vista) Click the Start button, choose Control Panel,

and switch to Classic View, if needed. Double-click the System icon,
select the Advanced (XP) or Advanced System Settings (Vista) tab,
and then click the Environment Variables button.

• (Windows 2000) Click the Start button, choose Settings>Control

Panel. Double-click the System icon, select the Advanced tab, and
click the Environment Variables button.

2. Add a user environment variable named LM_LICENSE_FILE with the

appropriate value. The value can take one of two forms:

• If the license file ([Link]) is visible from your PC, then you can
enter the path to the file. For example, if the license file is visible as
h:\licenses\[Link], set the value of the LM_LICENSE_FILE
variable to:

h:\licenses\[Link]

• If you don’t have access to the license file or you don’t want to
directly reference the license file, you must know the name of the
machine running the lmgrd license daemon and the TCP/IP port
number used for your license file. This information appears on the
SERVER line of the license file. For example, if the server line in the
license file looks like this:

SERVER myserver 550003ef 1701

Set the value of the LM_LICENSE_FILE environment variable to:

1701@myserver

3. Your new software is ready to be used. As a final test, start up the

software to confirm that the license file is being properly accessed.

Borrowing a license
Licenses containing BORROW in the FEATURE line may be borrowed.
Borrowing a licence causes a license to remain checked out even when
TimingDesigner is not running.
• To borrow a license (command line)

1. Connect to the network.

2. Specify the date and time when the license should be returned:

lmborrow emalmd dd-mmm-yyyy [hh:mm]

where mmm is the three letter abbreviation for the month.

3. Start and then exit TimingDesigner. This will check out a license and
keep it checked out.

Chapter 2 TimingDesigner 9.25

34 Installing TimingDesigner TimingDesigner User’s Guide
 The borrowed license will expire on the date/time provided; you can also
return the license early.
To see which licenses are currently checked out:
lmborrow -status

• To borrow a license (Windows LMTOOLS)

1. Connect to the network.

2. Choose Start>All Programs>EMA>LMTools to start the LMTOOLS utility.

3. In the Service/License File tab, select EMA Design Automation License

Manager in the Configuration Using Services list.

4. Click the Borrowing tab, then:

• Specify a Return Date in the format dd-mmm-yyyy, where mmm is

the three letter abbreviation for the [Link] example, enter 09-jul-
2007 for a license expiring on July 9, 2007.

• Optionally, you may specify a Return Time in the format hh:mm. For
example, type 14:00 for a license expiring at 2 PM. If no time is
specified, the license will expire at midnight on the date specified.

5. Click Set Borrow Expiration.

6. Start and then exit TimingDesigner. This will check out a license and
keep it checked out.

7. Return to the LMTOOLS utility, and click Don’t Borrow Anymore Today.

The borrowed license will expire on the date/time provided; you can also
return the license early.
To see which licenses are currently checked out, click the List Currently
Borrowed Features button in the LMTOOLS utility’s Borrowing tab.
• To return a license (command line)

1. Reconnect to the network.

2. Return the license:

lmborrow -return TimingDesigner

• To return a license (Windows LMTOOLS)

1. Reconnect to the network.

2. Choose Start>All Programs>EMA>LMTools to start the LMTOOLS utility.

3. Click the Borrowing tab.

4. Enter TimingDesigner in the Feature Name field, then click Return

Borrowed Licenses Early.

Chapter 2 TimingDesigner 9.25

35 Installing TimingDesigner TimingDesigner User’s Guide
 Setting up a Windows locked license
Windows locked licenses use a FLEXid hardware key.
Note: If you are installing on a network, each computer running the application
must have its own authorization key.
• To install the FLEXid hardware key

FLEXid hardware keys are used to provide a hostid for use with a license file.
The key can be either a parallel port or USB key. The authorization key
should not cause any problems with either your computer or your printer.
1. Install the FLEXid device driver by running the [Link]
program located in the win32 directory of your installation.

The device driver allows the software to access the hardware key on the
computer’s parallel port or USB port.
2. Locate the parallel or USB hardware key that was shipped with your
software.

3. Locate the parallel or USB port at the rear of your computer.

Note: If you have more than one parallel or USB port, you can place the
key on any port connector.
4. Plug the parallel or USB key into the port.

5. If you disconnected a printer cable or another authorization key from the

parallel port, reconnect it to the female end of the key.

6. You will need to obtain a license file before the software can be run. See
“Obtaining a license” on page 28 for more information.

Setting UNIX environment variables

The following environment variables are used to help configure TimingDesigner.
The default values are initialized in the td script in TimingDesigner’s bin
directory. The TDDIR environment variable is assumed to be set to the
TimingDesigner installation directory.
• LM_LICENSE_FILE The location of the license file (typically named
[Link]). If you already have an LM_LICENSE_FILE set, TimingDesigner
uses it to locate the license file. Otherwise, the td script sets
LM_LICENSE_FILE to $TDDIR/flexlm/ licenses/[Link].

• XPPATH The location of the Xp subdirectory. Default=$TDDIR/lib/Xp.

• LD_LIBRARY_PATH The location of the application’s shared libraries.

Default=$TDDIR/lib:$LD_LIBRARY_PATH.

• DOTFONTPATH The directory used by DOT to find fonts.

Default=$TDDIR/lib.

Chapter 2 TimingDesigner 9.25

36 Installing TimingDesigner TimingDesigner User’s Guide
 General license troubleshooting
If you’re having trouble configuring your license manager, or if you can’t check
out a license for some reason, you can look up your licensing information in
TimingDesigner’s License Information dialog box. This dialog shows you how
many licenses you have, how many licenses are checked out and by whom, and
other information useful for diagnosing licensing problems.
• To access the License Information dialog box

• In any TimingDesigner window, choose Help>License Info.

Troubleshooting a license server running on UNIX

• To start FLEXnet

Use the following command:

$TDDIR/FLEXnet/<platform>/bin/lmgrd –c $TDDIR/FLEXnet/
licenses/[Link]

• To determine the status of the license file

Use the following command:

$TDDIR/FLEXnet/<platform>/bin/lmstat -a -c $TDDIR/FLEXnet/
licenses/[Link]

• To shut down the license file

Use the following command:

$TDDIR/FLEXnet/<platform>/bin/lmdown -c $TDDIR/FLEXnet/
licenses/[Link]

• To determine the version of lmgrd

Use the following command:

$TDDIR/FLEXnet/<platform>/bin/lmver TDDIR/FLEXnet/bin/lmgrd

• To determine the version of TimingDesigner

Use the following command:

$TDDIR/bin/td -version

• To determine the LM_LICENSE_FILE setting

At the shell prompt, use the following command:

printenv LM_LICENSE_FILE

Alternatively:
In TimingDesigner, choose Help>License Info.
Chapter 2 TimingDesigner 9.25
37 Installing TimingDesigner TimingDesigner User’s Guide
 • To list processes

Use the following commands:

Solaris or Linux:
ps -auwx | grep lmgrd

• Combining license files

License files can be combined if and only if the SERVER lines have the
same hostnames and hostids, and an equal number of servers. Combining
license files is discussed in “At the system level: Configuring the license
manager on your server node (UNIX)” on page 30.

Troubleshooting a license server running on Windows

• To create a log file of lmgrd activity

If you are having difficulty starting lmgrdand a lot of messages are being
printed to the screen, you can capture the information in a log file. Use the
following commands:
cd <install_dir>\FLEXnet\<platform>\bin
lmgrd -app -c <license_file> -l [Link]

where [Link] is the name of the log file.

• To determine whether lmgrd is acknowledging the license file

Use the following commands:

cd <install_dir>\FLEXnet
lmutil lmstat -a -c <license_file>

This lets you determine if the emalmd daemon is up and how many licenses
are available.

Chapter 2 TimingDesigner 9.25

38 Installing TimingDesigner TimingDesigner User’s Guide