( ESNUG 316 Item 13 ) ---------------------------------------------- [4/8/99]
Subject: ( ESNUG 313 #14 ) Installing Synopsys 98.08 Messes Up 98.02 Access!
> we have a license server running on a unix host, currently 1998.02. we
> want to install 1998.08 software on a pc/nt system and have access to the
> unix license server over the network. we are told by our in-house people
> that upgrading the license server, on unix, to 1998.08 (necessary for pc/nt
> access) will disrupt 1998.02 software access. synopsys says it will work
> fine and suggests we do exactly that. does anyone have any experience that
> they can share?
>
> - Richard B. Katz
> NASA Goddard Space Flight Center Greenbelt, MD
From: Peter Kamphuis <kamphuis@hl.siemens.de>
John,
There shouldn't be a problem here. We've never seen problems since newer
licenses (higher version number) should always enable older software
(lower version number). Unless, of course, feature names change. Recently,
for example, we've received the 1999.05 licenses and we've noticed that
Designware-Developer now is called DW-Developer. We have two entries now
in our key file and we should not forget to request for both features
again when they would expire. So I would recommend to always check your
feature lines before installing new licenses.
- Peter Kamphuis
Siemens Semiconductor Group Munich, Germany
---- ---- ---- ---- ---- ---- ----
From: miller@symbol.com (Wayne Miller)
Hi John,
We're running versions from V3.5a to 1998.08 all from the same license
server. We also have a lone NT evaluator who pulls keys. We haven't
seen any problems, except for a wacky issue with the LM_LICENSE_FILE
variable and the order that the Synopsys and Xilinx keys are listed.
(Get it wrong, and 1998.08 won't pull keys.)
- Wayne Miller
Symbol Technologies, Inc.
---- ---- ---- ---- ---- ---- ----
From: Tom Hicks <thicks@fore.com>
John,
We seemed to have some trouble back in August when we installed 98.08.
However, we did a reinstallation (not sure whether we did this because of a
change in the update from Synopsys or because a sysadmin installed the
upgrade incorrectly), and we have been running fine with 99.5/98.08/98.02/97.
- Tom Hicks
FORE Systems Pittsburgh, PA
---- ---- ---- ---- ---- ---- ----
From: Rich Katz <rich.katz@gsfc.nasa.gov>
hi john,
here's the follow-up i got from synopsys on my problem.
From: [ The Synopsys R&D Licensing Team Manager ]
Dear Rich,
Thank you very much for your patience over the last six
months while we isolated and resolved the two licensing
environment variable issues reported in the 1998.08
release.
This letter is to inform you about these resolved issues with
the licensing variables used by Synopsys Design Tools Group's
products in release 1998.08 on all supported UNIX and Windows
NT platforms. These issues have been resolved in the
1998.08-B58544 release, the 1998.08 cluster release and the
1999.05 release and they have also been documented in detail
in the 1999.05 Release Notes and Installation User Guides,
the 1998.08-B58544 SOLV-IT! article (Sys_Admin-42.html),
and the 1998.08 cluster release notes.
In the 1998.08 release, Synopsys software looked for the license
key file(s) in the following order:
1. $LM_LICENSE_FILE,
2. $SYNOPSYS_KEY_FILE,
3. Synopsys default location ($SYNOPSYS/admin/license/key,
where $SYNOPSYS is set to the Synopsys root directory). In
addition, if $LM_LICENSE_FILE was defined, $SYNOPSYS_KEY_FILE and
the default license file were not acknowledged. With the solution
we implemented, the software now uses license files specified by
all 3 environment variables ($SYNOPSYS_KEY_FILE, $LM_LICENSE_FILE,
and $SYNOPSYS/admin/license/key) for the license keys.
In the 1998.08 release, there was a problem in our software
(STAR # 58944) that required the Synopsys key file to be
specified at the end of the list for either $SYNOPSYS_KEY_FILE
or $LM_LICENSE_FILE for customers who did not purchase the
DTG feature 'SNPS-CSL' for their license servers. With the
solution we implemented, the location of the Synopsys license
file within $SYNOPSYS_KEY_FILE or $LM_LICENSE_FILE is order
independent.
We apologize for the inconvenience caused by the licensing
issues in the 1998.08 release. We have addressed and resolved
these issues in the post-1998.08 releases and have implemented
new processes and improved testing to ensure that this type of
error does not occur again. We are excited about the licensing
infrastructure upgrades to our products that are planned for
release during the next 6 to 12 months.
- [ The Synopsys R&D Licensing Team Manager ]
hopes this helps any other esnug readers who ran into my bug, john.
- Richard B. Katz
NASA Goddard Space Flight Center Greenbelt, MD
|
|
