ICE - Dassault Systèmesmedia.3ds.com/.../FlexLM_61_manual_Deutsch.pdfKapitel 2 Ü berblick 2-1...

ICETechnologies

ICEM Lizensierung

mit FLEXlm™ 6.1

Allgemeine Informationen und User’s Guide

Juli 2000

© ICEM Technologies GmbH 2001

Informationen zum Urheberrecht

Copyright © 2001 Parametric Technology Corporation. Alle Rechte vorbehalten.

Die Benutzer- und Schulungsdokumentation der Parametric Technology Corporation (PTC) unterliegt den Urheberrechten derVereinigten Staaten und anderer Staaten sowie einem Lizenzvertrag, der die Vervielfältigung, Veröffentlichung und Verwendungbesagter Dokumentation einschränkt. PTC gewährt dem lizenzierten Benutzer hiermit das Recht, diese auf Softwaredatenträ-gern bereitgestellte Dokumentation in gedruckter Form zu vervielfältigen, jedoch ausschließlich für den internen/persönlichenGebrauch und in Übereinstimmung mit dem Lizenzvertrag, unter dem die jeweilige Software lizenziert ist. Jede angefertigte Kopiemuß den urheberrechtlichen Hinweis von PTC und sonstige von PTC bereitgestellte eigentumsrechtliche Hinweise enthalten.Diese Dokumentation darf ohne vorherige schriftliche Genehmigung von PTC nicht veröffentlicht, weitergegeben, geändert oderauf irgendeine Form reduziert werden, einschließlich elektronischer Datenträger, oder auf irgendeine Weise übertragen oderöffentlich verfügbar gemacht werden, und zum Herstellen von Kopien zu solchen Zwecken wird keine Berechtigung erteilt.

Die hierin enthaltenen Informationen dienen nur zur allgemeinen Information; sie können ohne vorherige Bekanntgabe geändertwerden und enthalten keinerlei Garantien oder Verpflichtungen seitens PTC. PTC übernimmt keine Verantwortung oder Haftungfür etwaige Fehler oder Ungenauigkeiten, die unter Umständen in diesem Dokument auftreten.

Die in diesem Dokument beschriebene Software unterliegt einem schriftlichen Lizenzvertrag; sie enthält wertvolle Betriebsge-heimnisse und Eigentumsinformationen, die unter den Urheberrechten der USA und den Urheberrechten anderer Ländergeschützt sind. DIE UNBEFUGTE VERWENDUNG DER SOFTWARE ODER DER DAZUGEHÖRIGEN DOKUMENTATIONKANN SCHADENSERSATZFORDERUNGEN ZUR FOLGE HABEN ODER ZU STRAFRECHTLICHER VERFOLGUNG FÜH-REN.

Eingetragene Warenzeichen der Parametric Technology Corporation oder einer Tochtergesellschaft

CADDS, Parametric Technology, Parametric Technology Corporation, Pro/ENGINEER and Windchill.

Warenzeichen der Parametric Technology Corporation oder einer Tochtergesellschaft

3DPAINT, Associative Topology Bus, DIVISION, e/ENGINEER, e-Series, Flexible Engineering, ICEM, Import Data Doctor, Infor-mation for Innovation, i-Series, Pro/DESIGNER, Pro/PHOTORENDER, Pro/PHOTORENDER TEXTURE LIBRARY, Pro/SCAN-TOOLS, Pro/SURFACE, PTC i-Series, Shaping Innovation, Shrinkwrap, The Product Development Company, Virtual DesignEnvironment, Windchill e-Catalog, Windchill e-Series, Windchill ProjectLink, das DIVISION Logo und das ICEM Logo.

Warenzeichen von Drittparteien

Oracle ist ein eingetragenes Warenzeichen der Oracle Corporation. Windows und Windows NT sind eingetragene Warenzeichender Microsoft Corporation. Java und alle Java-basierten Zeichen sind Warenzeichen oder eingetragene Warenzeichen von SunMicrosystems, Inc. Adobe ist ein eingetragenes Warenzeichen von Adobe Systems. Metaphase ist ein eingetragenes Warenzei-chen von Metaphase Technology Inc. Unigraphics ist ein eingetragenes Warenzeichen von EDS Corp. I-DEAS ist ein eingetrage-nes Warenzeichen von SDRC. AutoCAD ist ein eingetragenes Warenzeichen von Autodesk, Inc. CADAM und CATIA sindeingetragene Warenzeichen von Dassault Systems. IRIX ist ein eingetragenes Warenzeichen von Silicon Graphics, Inc. PDGS istein eingetragenes Warenzeichen der Ford Motor Company. FLEXlm ist ein eingetragenes Warenzeichen von Globetrotter Soft-ware Inc. HOOPS Graphics System ist ein proprietäres Software-Produkt von Tech Soft America, Inc., für das Tech Soft America,Inc. die Urheberrechte besitzt. Alle sonstigen Marken- oder Produktnamen sind Warenzeichen oder eingetragene Warenzeichenihrer jeweiligen Eigentümer.

EINGESCHRÄNKTE RECHTE VON US-BEHÖRDEN

Im Sinne der Gesetze und Regelungen der Vereinigten Staaten, namentlich FAR 12.212(a)-(b) sowie DFARS 227.7202-1(a) und227.7202-3(a) gilt die vorliegende Dokumentation als Dokumentation für kommerzielle Computersoftware, und die dazugehö-rende Software gilt als kommerzielle Computersoftware, die Behörden und amtlichen Stellen gemäß dieser Gesetze und Rege-lungen zur Verfügung gestellt wird. Bei Beschaffungen vor Eintritt der genannten Bestimmungen unterliegt die Nutzung,Vervielfältigung und Veröffentlichung durch Behörden und amtliche Stellen den Bestimmungen von Unterabsatz (c)(1)(ii) derRechte an technischen Daten und Computersoftware gemäß DFARS 252.227-7013 bzw. der Eingeschränkten Rechte an kom-merzieller Computersoftware gemäß FAR 52.227-19.

Parametric Technology Corporation, 140 Kendrick Street, Needham, Massachusetts 02494, USA2. April 2001

Inhalt

Inhalt

Kapitel 1 Einleitung 1-1

1.1 Sicherheitshinweis zum Lizensierungsmechanismus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

1.2 Plattform für den Lizenz-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

1.3 Hinweis zu FlexLM-Versionen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Kapitel 2 Überblick 2-1

Kapitel 3 Ermittlung von Maschineninformationen 3-1

Kapitel 4 Aktivierung des Lizensierungsmechanismus 4-1

Kapitel 5 Installationsüberprüfung 5-1

Kapitel 6 User’s Guide 6-1

6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

6.2 Components of ICEM Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

6.2.1 Borrowing console Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

6.2.2 License Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

6.3 License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3

6.3.1 Example License Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3

6.3.2 Modifying the License File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3

6.3.3 Alternate License File Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5

6.4 Customization Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-6

6.5 Three Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

6.6 The License Daemon /<install_path>/lic/lmgrd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

6.7 The ICEM Daemon /<install path>/lic/icem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9

6.8 The License Finder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9

6.8.1 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10

6.8.2 License Finder Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10

6.9 Other Utilities in /<install_path>/lic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10

6.9.1 autlook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11

6.9.2 optdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11

6.9.3 lmcksum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11

6.9.4 lmdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11

6.9.5 lmdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11

6.9.6 lmhostid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12

6.9.7 lmremove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12

6.9.8 lmreread . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12

6.9.9 lmstat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

6.9.10 lmswitchr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

6.9.11 lmver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

1

Inhalt

6.9.12 S99license (UNIX only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

6.10 The License Daemon Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Kapitel 7 License Management and Error Messages 7-1

7.1 The Program autlook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

7.2 The Program optdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

7.3 Sample License Daemon Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

7.4 License Daemon Log File Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

7.5 Licensing Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

2

Kapitel 1 Einleitung


Das vorliegende Dokument beschreibt den ICEM Lizensierungsmechanismus, der auf dem Lizensierungspro-

gramm Flexible License Manager FLEXlm basiert. FLEXlm ist ein Warenzeichen der Globetrotter Inc. (http://

www.globetrotter.com/home.htm). Wesentliche Teile des vorliegenden Handbuchs sind dem “FLEXlm End

User Manual” entnommen (http://www.globetrotter.com/manual.htm).

Die Dateien, die zu ICEM Lizensierung gehören, befinden sich im Verzeichnis /<install path>/lic. Unter

Unix enthält die Datei bom_lic eine Liste dieser Dateien (bom = Bill of Materials; bom_lic befindet sich ebenfalls

im Verzeichnis /<install path>/lic). Unter Windows wird das FLEXlm-Hilfsprogramm LMUTIL im Verzeich-

nis /<install path>/bin gespeichert.

Hinweis:Alle Dateipfade werden im UNIX-Format angezeigt, d. h. die Verzeichnisnamen sind durch Schrägstriche ("/")

getrennt. Windows-Anwender sollten die Schrägstriche gegen inverse Schrägstriche ("\") austauschen. Außerdem

sollte den Dateipfaden die Laufwerkskennung der Festplatte (i. d. R. "C:") vorangestellt sein.

1.1 Sicherheitshinweis zum Lizensierungsmechanismus

FLEXlm hat uns darüber informiert, daß ein Sicherheitsrisiko bestehen kann, wenn die Lizenzüberwachungspro-

gramme (licensing daemons) mit den Zugriffsrechten des Anwenders “super-user” laufen. Daher empfehlen wir

Ihnen, daß die Hilfsprogramme von ICEM Lizensierung nicht dem Anwender “super-user” gehören und nicht von

ihm gestartet werden. Bitte lesen Sie hierzu auch Kapitel Kapitel 4 “Aktivierung des Lizensierungsmechanismus”,

Seite 1, Schritte 1 und 7.

1.2 Plattform für den Lizenz-Server

Die Lizenzüberwachungsprogramme von ICEM Lizensierung werden grundsätzlich für alle Plattformen (Alpha,

HP, IBM, SGI, Sun und Windows NT) ausgeliefert. Das ist unabhängig davon, für welche Plattform Sie ICEM

Software-Releases gekauft haben. Dadurch kann der Systemadministrator aussuchen, welche Plattform als

Lizenz-Server dienen soll. In großen Netzwerken ist dies typischerweise ein Datei-Server, dessen Plattform-Typ

anders sein kann als von der Maschine, auf der die ICEM-Software läuft. Standardmäßig werden die Lizenzüber-

wachungsprogramme für die Plattform installiert, auf der die Installation von ICEM Licensing durchgeführt wird.

1.3 Hinweis zu FlexLM-Versionen

ICEM Surf läuft noch unter FlexLM 5.12. Wenn Sie jedoch die Direktschnittstellen ICEM CATIA, ICEM

CADDS oder ICEM Unigraphics entweder aus ICEM Surf heraus oder im standalone-Modus verwenden wollen,

muß FlexLM 6.x laufen.

Für ICEM DDN und die zugehörigen Hilfsprogramme und Anwendungen wird empfohlen, daß Sie die FlexLM-

Version installieren, die zusammen mit Ihrer DDN-Software ausgeliefert wurde.

1-1


1-2

Kapitel 2 Überblick


ICEM verwendet die Lizenzdatei /<install path>/lic/license.dat (wobei /<install path> üblicherweise

auf /icem eingestellt ist; /icem ist auch die Standardeinstellung). Die Lizenzdatei legt fest, wer eine Applikation

oder eine ihrer Funktionen benutzen darf und wieviele Anwender gleichzeitig mit ihr arbeiten dürfen. Die Lizenz-

datei kann Lizenzen mit einer begrenzten Zugriffszahl und Lizenzen mit einer unbegrenzten Zugriffszahl enthal-

ten. Lizenzen mit einer begrenzten Zugriffszahl verwenden Lizenzüberwachungsprogramme, um die Anzahl

gleichzeitiger Zugriffe auf die lizensierte Applikation oder Funktion zu zählen und ggf. zu begrenzen und um den

Zugriff auf die Applikation oder Funktion von jeder Maschine im Netzwerk aus zu ermöglichen.

Wenn die Lizenzdatei Server-Lizenzen für einen bestimmten Server-Rechner enthält, sind am Anfang der Lizenz-

datei Zeilen vorhanden, die mit den Schlüsselwörtern SERVER und DAEMON beginnen. Wenn eine SERVER-

Zeile vorhanden ist, müssen die Lizenzüberwachungsprogramme (licensing daemons) lmgrd und icem auf der

Maschine laufen, für die die Server-Lizenz ausgestellt ist. Wenn drei SERVER-Zeilen vorhanden sind, müssen die

Lizenzüberwachungsprogramme auf mindestens zwei der genannten Maschinen laufen.

Wenn Sie Netzwerk-Lizenzen haben, sollten Sie die in Kapitel Kapitel 4 “Aktivierung des Lizensierungsmecha-

nismus”, Seite 1 beschriebenen Schritte abarbeiten.

Wenn keine SERVER- oder DAEMON-Zeilen vorhanden sind, haben Sie eine sogenannte knotengebundene

Lizenz, die nicht für einen Serverrechner bestimmt ist. Bei knotengebundenen Lizenzen ist in der FEATURE-

Zeile als maximal zulässige Benutzerzahl "0" angegeben. Außerdem steht am Ende der FEATURE-Zeile eine

Maschinenkennung, damit die lizensierte Applikation oder Funktion nur auf dieser bestimmten Maschine ausge-

führt werden kann.

Knotengebundene Lizenzen funktionieren nur auf der Maschine, die in der Maschinenkennung angegeben ist.

Basislizenzen sind knotengebundene Lizenzen ohne Angabe eines Server-Rechners. Floating- und Zusatz-Lizen-

zen sind Netzwerk- bzw. Server-Lizenzen mit Angabe eines Server-Rechners. Eine Lizenzdatei kann sowohl Ser-

ver-Lizenzen als auch knotengebundene Lizenzen enthalten.

Alle Lizenzen haben ein Ablaufdatum, das in einer FEATURE- oder INCREMENT-Zeile im Format dd-mm-yy

oder dd-mm-yyyy angegeben ist, z. B. 31-dec-97. Bei Lizenzen, die im Jahr 2000 oder später ablaufen, wird ein

anderes Format verwendet, z. B. 31-dec-2001.

Für Testinstallationen und Demos wird meist eine Demonstrationslizenz ausgestellt. Eine typische Demonstrati-

onslizenz enthält in der ersten Zeile einen Kommentar, der angibt, daß es sich um eine Demonstrations-Lizenz

handelt. Eine Demonstrations-Lizenz ist normalerweise eine knotengebundene Lizenz, die nicht für einen Server-

Rechner bestimmt ist und nur auf einer bestimmten Maschine läuft, die in der FEATURE-Zeile angegeben ist. Sie

kann aber auch eine Server-Lizenz (Floating-Lizenz) für jede Maschine sein, die eine in der/den SERVER-

Zeile(n) angegebene Maschine als Server hat. Die Demonstrations-Lizenz hat nur eine kurze Gültigkeitsdauer.

2-1


2-2

Kapitel 3 Ermittlung von Maschineninformationen


Bitte ermitteln Sie Maschinennamen, Maschinenkennung, Betriebssystemnamen und -version sowie Seriennum-

mer für jede Maschine, die eine Lizenz für ICEM- Produkte benötigt. Wenn Sie eine Floating- oder Zusatz-Lizenz

erworben haben, ermitteln Sie bitte auch die TCP/IP-Port-Nummer. Um diese Informationen zu erhalten, führen

Sie auf jeder Maschine, die als Lizenz-Server eingesetzt werden soll, die unten beschriebenen Schritte aus. Ihr

Software-Händler kann dann vor dem Ablaufdatum der alten Lizenz eine neue für Sie besorgen. Wenn Sie für

einige Produkte Basis-Lizenzen erworben haben, die nur auf bestimmten Maschinen eingesetzt werden sollen,

dann müssen Sie – falls noch nicht geschehen – Ihrem Software-Verkäufer ebenfalls den Maschinennamen, die

Maschinenkennung, den Betriebssystemnamen, die Betriebssystemversion, die Seriennummer und evtl. die TCP/

IP-Portnummer für diese Maschinen nennen.

1. Schritt

Loggen Sie sich als “root” ein auf der Workstation, die als Lizenz-Server verwendet werden soll.

2. Schritt

Windows IPX/SPX-Netzwerktreiber-Setup.

Dieser Schritt ist nur notwendig, wenn der Windows-Rechner mit einer Ethernetkarte ausgerüstet ist. Der Rechner

verwendet dann eine Ethernet Node-Locked Basislizenz oder es läuft die ICEM-Lizenzüberwachungssoftware für

Floating-Lizenzen auf diesem Rechner.

• Windows 2000 Workstations

Es muß entweder NetBIOS service oder NWLink IPX/SPX protocol auf der Maschine laufen, damit FLEXlm

die Ethernet-Nummer für Netzwerklizenzen oder maschinengebundene Lizenzen unter Windows finden kann.

Überprüfen Sie folgendermaßen, ob das NetBIOS Interface oder der NWLink IPX/SPX-Treiber installiert ist.

1. Legen Sie die NT-Installations-CDROM in das Laufwerk.

2. Wählen Sie ”Start”

3. Wählen Sie ”Einstellungen”

4. Wählen Sie ”Systemsteuerung”

5. Wählen Sie ”Netzwerk und Wählverbindungen”

6. Klicken Sie eine ”local area connection” mit der rechten Maustaste an

7. Wählen Sie ”Eigenschaften”

8. Lesen Sie ab, ob das "NetBIOS Interface" oder der ”NW Link IPX/SPX-Treiber” installiert ist

Wenn weder das NetBIOS Interface noch der NWLink IPX/SPX-Treiber installiert ist, führen Sie die folgen-

den Schritte durch.

1. Wählen Sie ”Installieren”

2. Markieren Sie ”Protokolle”

3. Klicken Sie auf ”Hinzufügen”

4. Fügen Sie das "NetBIOS Interface" oder den "NWLink IPX SPX driver" hinzu.

5. Klicken Sie auf ”OK”

3-1


• Windows NT 4.0 Workstations

Es muß entweder NetBIOS service oder NWLink IPX/SPX protocol auf der Maschine laufen, damit FLEXlm

die Ethernet-Nummer für Netzwerklizenzen oder maschinengebundene Lizenzen unter Windows finden kann.

Das NetBIOS Interface wird folgendermaßen installiert.





5. Wählen Sie ”Netzwerk”

6. Wählen Sie ”Dienste”

7. Klicken Sie auf ”Hinzufügen ...”

8. Wählen Sie "NetBIOS Interface".

Der NWLink IPX/SPX-Treiber wird folgendermaßen installiert.






6. Wählen Sie ”Protokolle”

7. Klicken Sie auf ”Hinzufügen ...”

8. Fügen Sie den "NWLink IPX SPX driver" hinzu.

Starten Sie den Rechner neu.


1. Legen Sie die Windows 95-Installations-CDROM in das Laufwerk.

2. Wählen Sie ”Hauptgruppe”



5. Wählen Sie ”Konfiguration”

6. Wählen Sie ”Hinzufügen”

7. Wählen Sie ”Protokoll”

8. Wählen Sie ”Microsoft”

9. Wählen Sie ”IPX/SPX-kompatibles Protokoll”.

10. Danach werden Sie dazu aufgefordert, den Rechner neu zu starten.

3. Schritt

Ermitteln und notieren Sie bitte den Maschinennamen (hostname), die Maschinenkennung (hostid) sowie Name

und Version des Betriebssystems. Welche Befehle hierfür zu verwenden sind, hängt von der Hardware ab.

3-2


• SGI Workstations

1. Maschinenname:

/usr/bsd/hostname oder

uname -n

2. Maschinenkennung:

/<install path>/lic/lmhostid oder

echo ‘/etc/sysinfo -s‘ 16o p | dc oder

/usr/sbin/lmhostid

Auf Crimson-, Challenge- und Onyx-Workstations müssen Sie das Programm lmhostid verwenden (nach-

dem Sie ICEM Lizensierung installiert haben), weil der Befehl sysinfo auf diesen Maschinen keine ein-

deutige Maschinenkennung liefert.

3. Betriebssystemlevel:

uname -sr

• HP Workstations

1. Maschinenname:

/usr/bsd/hostname oder

uname -n



echo ‘uname -i‘ 16o p | dc

Die ICEM-Lizensierung unterstützt nicht mehr die Ethernet-Adresse für die Lizenz-Maschinenkennung

auf HP-Maschinen.


uname -srv

• IBM Workstations


/<install path>/lic/lmhostid

2. Maschinenname/Maschinenkennung/Betriebssystem:

uname -a

Es werden Informationen ausgegeben, die wie im folgenden Beispiel aussehen:

AIX ibm_1 2 3 000017133700

wobei

AIX = Betriebssystemname

ibm_1 = Maschinenname

2 3 = Betriebssystemlevel 3.2.x

171337 = Maschinenkennung

(die letzten zwei Nullen und alle führenden Nullen werden nicht verwendet)

• SUN Workstations

1. Maschinenname:

3-3


/usr/ucb/hostname oder

uname -n



hostid


uname -srv

• DEC Alpha Workstations

1. Maschinenname:

/usr/bin/hostname oder

uname -n



pfstat

Diese Maschine verwendet die 12 Zeichen lange Ethernet-Adresse als Maschinenkennung. Mit dem

Befehl pfstat können mehrere Informationszeilen ausgegeben werden. Lesen Sie die Zeile "Interface

Address", um die Ethernet-Adresse zu ermitteln.


uname -srv


1. Maschinenname:

Wählen Sie ”Start”

Wählen Sie ”Einstellungen”

Wählen Sie ”Systemsteuerung”

Wählen Sie ”Netzwerk und Wählverbindungen”

Klicken Sie auf den Link ”Netzwerk-Identifikation”

Wählen Sie die Registerkarte ”Netzwerk-Identifikation”

Notieren Sie den Maschinennamen.


Öffnen Sie ein Fenster mit einer ”MS/DOS Eingabeaufforderung” und geben Sie den folgenden Befehl

ein:

/<install path>/BIN/LMUTIL.EXE lmhostid

Wenn Sie als Maschinenkennung “ffffffff” erhalten, müssen Sie ein IPX/SPX-Netzwerktreiber-Setup vor-

nehmen (siehe Schritt 2) und die Schritte 1 und 3 erneut durchführen oder

/winnt/system32/ipconfig /ALL

Notieren Sie die “Physische Adresse” ohne die Bindestriche.





Wählen Sie ”System”

Wählen Sie die Registerkarte ”Allgemein”

3-4


Notieren Sie das Betriebssystem.

• Windows NT 4.0 Workstations

1. Maschinenname:




Wählen Sie ”Netzwerk”



Öffnen Sie ein Fenster mit einer ”MS/DOS Eingabeaufforderung” und geben Sie den folgenden Befehl

ein:

/<install path>/BIN/LMUTIL.EXE lmhostid

Wenn Sie als Maschinenkennung “ffffffff” erhalten, müssen Sie ein IPX/SPX-Netzwerktreiber-Setup vor-

nehmen (siehe Schritt 2) und die Schritte 1 und 3 erneut durchführen oder

/winnt/system32/ipconfig /ALL

Notieren Sie die “Physische Adresse” ohne die Bindestriche.









1. Maschinenname:




Wählen Sie ”Netzwerk”

Wählen Sie ”Identifikation”



Öffnen Sie ein Fenster mit einer ”MS/DOS-Eingabeaufforderung” und geben Sie den folgenden Befehl

ein:

/<install path>/BIN/LMUTIL lmhostid

oder

winipcfg

Notieren Sie die ”Netzwerkkartenadresse” ohne die Bindestriche.


3-5








• Ausgabe des Befehls lmhostid

Die Ausgabe des Befehls lmhostid sollte ungefähr aussehen wie folgt (unabhängig vom Hardware-System):

lmhostid - Copyright (C) 1989-1998, Globetrotter Software, Inc.

The FLEXlm host ID of this machine is "1200abcd"

4. Schritt

Wenn Sie Floating- oder Zusatz-Lizenzen erworben haben und einen UNIX-Server verwenden, ermitteln und

notieren Sie bitte auch die Nummer des TCP/IP-Ports, über den das ICEM-Lizenzüberwachungsprogramm (licen-

sing daemon) mit den anderen Maschinen in Ihrem Netzwerk kommunizieren soll. Für Windows-Rechner ist die-

ser Schritt nicht notwendig. Verwenden Sie unter Windows die Standard-Portnummer 1733. Verwenden Sie unter

UNIX den folgenden Befehl, um die Port-Nummern herauszufinden, die z. Zt. auf dem Server-Rechner verwendet

werden.

cat /etc/services

Die Ausgabe dieses Befehls sollte ungefähr aussehen wie folgt:

#

#Network services, Internet style

#

tcpmux 1/tcp #TCP port multiplexer (RFC 1078)

echo 2/tcp

Das zweite Feld enthält die Port-Nummer (z. B. steht 1/tcp für Port 1). Suchen Sie in der Datei nach der Stan-

dard-Port-Nummer für das ICEM-Lizenzüberwachungsprogramm 1733. (Wenn Sie schon eine Lizenzdatei haben,

ist die zugewiesene Port-Nummer im vierten Feld der SERVER-Zeile enthalten.) Wenn Sie die Standard- oder die

zugewiesene Port-Nummer nicht in der services-Datei finden, kann Sie für ICEM Lizensierung verwendet wer-

den. Wenn die Standard- oder die zugewiesene Port-Nummer in der services-Datei jedoch vorhanden ist, dann

kann irgendeine andere, verfügbare Port-Nummer zwischen 1733 und 6000 verwendet werden. (Wie Sie die zuge-

wiesene Port-Nummer in der Lizenz-Datei ändern, falls in der services-Datei ein konkurrierender Eintrag ent-

halten ist, können Sie in Abschnitt 6.3.2 “Modifying the License File”, Seite 3 finden. Für alle Maschinen im

Netzwerk, die vom ICEM-Lizenzüberwachungsprogramm (licensing daemon) beobachtet werden, sollte dieselbe

Port-Nummer verwendet werden.

Es wird empfohlen, daß die folgende Zeile in der Datei /etc/services auf jeder Maschine im Netzwerk ergänzt

wird als Platzhalter für das ICEM-Lizenzüberwachungsprogramm (licensing daemon). Setzen Sie die entspre-

chende Port-Nummer ein, die Sie für das ICEM-Lizenzüberwachungsprogramm verwenden möchten.

icem 1733/tcp #ICEM Licensing daemon port

5. Schritt

Bitte notieren Sie die Seriennummer Ihrer Workstation. Sie ist auf der Rückseite der Workstation auf einem Auf-

kleber mit einem Strichcode angegeben.

3-6


6. Schritt

Wenn Sie Ihrem ICEM-Software-Händler den/die Maschinennamen, Maschinenkennung(en), Betriebssystem-

Namen, Betriebssystem-Version(en), TCP/IP-Port-Nummer(n) und die Seriennummer(n) geben, kann eine

Lizenzdatei erzeugt werden.

3-7


3-8

Kapitel 4 Aktivierung des Lizensierungsmechanismus


Der Lizensierungsmechanismus muß auf jeder Workstation, die als Lizenzserver dient, aktiviert werden.

Anmerkung:Wenn Sie eine FLEXlm-Lizenzdatei von einem anderen Händler haben, dann möchten Sie vielleicht die verschie-

denen Lizenzdateien miteinander kombinieren. Bitte lesen Sie in diesem Fall Abschnitt “Combining License Files

from Multiple Vendors”, Seite 4, bevor Sie an dieser Stelle weiterlesen.

1. Schritt

Loggen Sie sich auf jeder Workstation ein, die als Lizenzserver dient, und zwar als der Benutzer, dem das Ver-

zeichnis und die Dateien gehören, wo ICEM Lizensierung installiert ist. Dieser Benutzer sollte auf keiner der

eben genannten Maschinen Superuser-Rechte haben, weil beim Ausführen eines gegen unbefugte Zugriffe nicht

abgesicherten Überwachungsprogramms (auch des Lizenzüberwachnungsprogramms) mit privilegierten Benut-

zerrechten ein potentielles Sicherheitsrisiko besteht. Dieses potentielle Sicherheitsproblem liegt in der Natur von

UNIX-Netzwerkprogrammen und ist deshalb ein FLEXlm-Software-Problem, das nicht in der ICEM-Software

selbst begründet ist. Deshalb sollten diese Dateien nicht dem root-Benutzer gehören oder von ihm ausgeführt

werden. Falls Dateien oder Verzeichnisse, die zur Lizensierung gehören, dem root-Benutzer gehören, weisen Sie

diesen Dateien oder Verzeichnissen mit dem Befehl chgrp die Gruppe des Systemadministrators zu, und ändern

Sie die Benutzerkennung der Dateien oder Verzeichnisse mit dem Befehl chown so, daß sie dem Systemadmini-

strator gehören. Dieser Benutzer muß auch zur lmadmin-Gruppe gehören. Wenn diese Gruppe nicht existiert,

dann muß sie erzeugt werden.

2. Schritt

Wechseln Sie in das Verzeichnis, in dem ICEM Lizensierung installiert wurde.

cd /<install path>/lic

3. Schritt

Wenn Sie zuvor eine vorhandene Lizenzdatei in ein anderes Verzeichnis verschoben haben, um zu verhindern, daß

sie durch die Installation überschrieben wird, holen Sie die Datei zurück und fahren Sie mit dem 5. Schritt fort.

4. Schritt

Wenn Sie die Lizenzdatei verwenden möchten, die Sie gerade installiert haben (/<install path>/lic/

license.dat), dann prüfen Sie nach, ob für die Datei ein Lizenzüberwachungsprogramm (licensing daemon)

gestartet werden muß. Es muß kein Lizenzüberwachungsprogramm gestartet werden, wenn die Datei keine Zeilen

enthält, die mit "SERVER" oder "DAEMON" beginnen. Wenn das für Sie zutrifft, können Sie mit Kapitel Kapitel

5 “Installationsüberprüfung”, Seite 1 fortfahren. Anderenfalls geht es weiter mit dem 5. Schritt.

5. Schritt

Stellen Sie sicher, daß die Lizenzdatei /<install path>/lic/license.dat auf allen Maschinen, auf denen

ICEM-Software verwendet werden soll, verfügbar ist. Diese Datei muß auf allen Maschinen, die von den Lizenz-

überwachungsprogrammen (licensing daemons) überwacht werden, identisch sein.

Überprüfen Sie, ob der Server-Maschinenname im zweiten Feld der SERVER-Zeile korrekt ist. Möglicherweise

war er bei der Erzeugung der Lizenz nicht bekannt. In diesem Fall wurde in der Lizenzdatei der Name

“UNKNOWN”, “hostname” oder ähnliches eingetragen. Wenn der Maschinenname nicht korrekt ist, ändern Sie

bitte die SERVER-Zeile und tragen Sie den richtigen Maschinennamen ein (beachten Sie dabei die Groß- und

Kleinschreibung!).

4-1


6. Schritt

Alle Maschinen, die die ICEM-Software verwenden und die von den Lizenzüberwachungsprogrammen über-

wacht werden sollen, müssen an das Netzwerk angeschlossen sein, um mit dem/den Server(n) kommunizieren zu

können. Überprüfen Sie bitte in diesem Zusammenhang die hosts-Datei auf jeder Maschine, auf der ICEM-Soft-

ware verwendet werden soll, und stellen Sie sicher, daß alle Server in der Datei enthalten sind. Unter UNIX ist der

Pfadname der hosts-Datei /etc/hosts. Unter Windows finden Sie die Datei hosts - falls Sie Domain Name

System (DNS) verwenden - oder lmhosts - falls Sie Windows Internet Name Service (WINS) verwenden - im

Verzeichnis /winnt/system32/drivers/usw. Wenn Sie unter UNIX die Netzwerk-Software Domain Name

System (DNS) verwenden, überprüfen Sie die Verbindung zu dem/den Server(n) mit dem Befehl nslookup

<hostname>. Wenn Sie unter UNIX die Netzwerk-Software Network Information Service (NIS) verwenden, über-

prüfen Sie die Verbindung zu dem/den Server(n) mit dem Befehl ypmatch <hostname> hosts.

Wenn Sie die Netzwerk-Software Network File System (NFS) oder Network Information Service (NIS) verwen-

den, um das Verzeichnis /<install path> auf einem Server-Rechner zu mounten, sollten Sie auf dem Server-

Rechner ein eigenes, lokales Verzeichnis lic erzeugen. Die ICEM Licensing-Hilfsprogramme müssen dann im

Verzeichnis /<some_path>/lic gespeichert sein. Dadurch ist sichergestellt, daß die Hilfsprogramme auch dann

noch zur Verfügung stehen, wenn der Rechner mit der gemounteten Festplatte eine Störung hat. Dieses lokale

Verzeichnis sollte nicht im Boot-Verzeichnis sein. Kopieren Sie die folgenden Dateien (soweit vorhanden) in das

lokale lic-Verzeichnis:

Danach sollten Sie die Datei license.dat editieren und den Pfad des Lizenzüberwachungsprogramms (licensing

daemon) in der DAEMON-Zeile (drittes Feld) verändern, so daß das lokale lic-Verzeichnis verwendet wird. Auch

alle folgenden Verweise auf /<install path> sollten in dieser Datei ersetzt werden durch das lokale lic-Ver-

zeichnis auf dem Server-Rechner.

Unter UNIX werden die FLEXlm-Hilfsprogramme für alle von ICEM Lizensierung unterstützten UNIX-Plattfor-

men zusammen mit dieser Software ausgeliefert. Die Hilfsprogramme befinden sich in plattform-spezifischen

Unterverzeichnissen im Verzeichnis /<install path>/lic. Die Unterverzeichnisse haben die folgenden Namen:

Standardmäßig werden in /<install path>/lic die FLEXlm-Hilfsprogramme für die Plattform installiert, auf

der ICEM Lizensierung laufen soll. Wenn Sie die FLEXlm-Hilfsprogramme von einer anderen als der installier-

ten Plattform aus benutzen möchten, müssen Sie die Hilfsprogramme aus einem dieser Verzeichnisse auf die

Maschine kopieren, von der aus Sie die Hilfsprogramme benutzen möchten.

S99license lmcksum lmgrd lmreread lmver

icem lmdiag lmhostid lmstat

license.dat lmdown lmremove lmswitchr

Unterverzeichnis-Name Plattform und Betriebssystem-Version

alpha_u3 DEC Alpha OSF1

hp700_u9 HP, HP-UX

i86_n3 Intel, Windows 95/NT/2000

rs6000_u3 IBM, AIX

sgi32_u5 SGI, IRIX 5, IRIX 6

sun4_u5 SUN, SunOS 5 (Solaris)

4-2


7. Schritt

Editieren Sie die Lizenz-Datei S99license (bei UNIX). Gehören die Lizensierungsdateien einem anderen Benut-

zer als dem root-Benutzer, tragen Sie in der “user=root”-Zeile den richtigen Benutzer der Lizenz-Dateien ein,

z. B. user=icem. Wenn die ICEM-Lizensierungsdateien dem root-Benutzer gehören, ändern Sie die Zeile

"check_user=1" um in "check_user=0".

8. Schritt

Unter Windows werden die Lizenzüberwachungsprogramme (licensing daemons) zusammen mit dem Anwen-

dungsprogramm installiert. Die Lizenzüberwachungsprogramme werden nach jedem Neustart des Servers erneut

als ein Unterprozeß gestartet.

Ändern Sie die Boot-Dateien (bei UNIX), so daß das Lizenzüberwachungsprogramm (license daemon) von ICEM

bei jedem Bootvorgang des UNIX-Servers gestartet wird. Der Boot-Vorgang ist plattform-abhängig.

Für IRIX-, Solaris-, Alpha- und HP-UX 10-Maschinen erzeugen Sie einen symbolischen Link für S99license

zum Boot-Verzeichnis.

• IRIX und Solaris Workstations

ln -s /<install path>/lic/S99license /etc/rc2.d/S99license

• Alpha und HP-UX 10 Workstations

ln -s /<install path>/lic/S99license /sbin/rc2.d/S99license

Wenn Sie so vorgehen und einen symbolischen Link verwenden, wird beim booten automatisch die neueste Ver-

sion der Lizenzprogramme verwendet.

Auf HP-UX 8- und HP-UX 9-Maschinen müssen Sie die Datei /etc/rc editieren. Fügen Sie die folgenden Zeilen

vor den letzten beiden Zeilen ein.

• HP-UX Workstations

# Startup ICEM Licensing daemons

if [ -x /<install path>/lic/S99license ]

then

/<install path>/lic/S99license start

fi

Auf AIX-Maschinen fügen Sie die folgenden Zeilen am Ende der Datei /etc/inittab ein.

• AIX Workstations

: Start ICEM License daemons

s99license:2:once:/<install path>/lic/S99license start

9. Schritt

Aktivieren Sie den Lizensierungsmechanismus.

• UNIX Workstations

cd /<install path>/lic

./S99license start

• Windows Workstations

Starten Sie den Rechner neu.

4-3


Dadurch wird das Lizenzüberwachungsprogramm (license daemon) lmgrd gestartet und eine Protokolldatei

erzeugt. Unter UNIX wird, wenn schon eine Lizenz-Protokolldatei vorhanden war, diese Datei umbenannt, indem

das aktuelle Datum und die aktuelle Uhrzeit an den Dateinamen angehängt wird, z. B. license.log-06-27-

94.14:09. Unter Windows wird eine vorhandene Lizenz-Protokolldatei überschrieben.

Anmerkung:Beim nächsten Hochfahren des Servers wird das Lizenzüberwachungsprogramm (license daemon) automatisch

gestartet.

10. Schritt

Überprüfen Sie die Protokolldatei des Lizenzüberwachungsprogramms.


more /<install path>/lic/license.log


Öffnen Sie ein Fenster mit einer MS-DOS Eingabeaufforderung und geben Sie den folgenden Befehl ein:

more </winnt/system32/lmgrd.log

Bitte lesen Sie Kapitel Kapitel 6 “User’s Guide”, Seite 1, um weitere Details bezüglich der Protokolldatei des

Lizenzüberwachungsprogramms zu erfahren.

Anmerkung:Das Lizenzüberwachungsprogramm registriert jeden Zugriff auf eine Floating- oder Zusatz-Lizenz und macht

einen entsprechenden Eintrag in der Protokolldatei. Dadurch kann die Protokolldatei im Laufe der Zeit sehr groß

werden. Deshalb sollten Sie das Lizenzüberwachungsprogramm in regelmäßigen Abständen unterbrechen und

neu starten, um eine neue Protokolldatei zu erzeugen. Die alte Protokolldatei kann dann jeweils gelöscht werden.

Unter UNIX kann dieser Vorgang mit Hilfe eines cron-Prozesses (Kommandos in regelmäßigen Abständen starten

lassen) automatisch wöchentlich oder monatlich durchgeführt werden.

4-4

Kapitel 5 Installationsüberprüfung


1. Schritt

Loggen Sie sich ein unter einem Anwendernamen, dessen Umgebung für eine ICEM-Anwendung eingestellt ist.

2. Schritt

Geben Sie die folgenden Befehle ein, um zu überprüfen, ob die Lizensierung für alle gekauften ICEM-Produkte

korrekt aktiviert wurde.


setenv LM_LICENSE_FILE /<install path>/lic/license.dat

/<install path>/lic/autlook | more

Für jedes installierte Produkt zeigt autlook die folgenden Informationen:

1. die Anzahl der installierten und verfügbaren Lizenzen,

2. das Ablaufdatum,

3. den Maschinennamen (wenn ein Produkt nur auf einer bestimmten Maschine verfügbar ist) und

4. eine Liste von Benutzern, die gerade mit dem Produkt arbeiten.

In Abschnitt “2.1 The Program autlook” finden Sie eine detaillierte Beschreibung von autlook.


Öffnen Sie ein Fenster mit einer ”MS/DOS-Eingabeaufforderung” und geben Sie die folgenden Befehle ein:

cd /<install path>/bin

lmutil lmstat -a -c /<install path>/lic/license.dat

Das Hilfsprogramm lmstat zeigt nur Netzwerklizenzen an. Um die maschinengebundenen Lizenzen zu über-

prüfen, sollten Sie sich die Lizenzdatei direkt ansehen.

Überprüfen Sie, ob alle Produkte und die Anzahl der von Ihnen gekauften Lizenzen korrekt aufgelistet werden.

5-1


5-2

Kapitel 6 User’s Guide

Kapitel 6 User’s Guide1

6.1 Introduction

The Flexible License Manager (FLEXlm™) is a network-wide floating licensing package that allows a software

application to be licensed on a concurrent-usage, as well as on a per-computer, basis. With FLEXlm the use of

ICEM software packages may be restricted to:

• a single specified computer, node-locked Base licenses.

• a specified number of users in a network containing heterogeneous computer systems, Floating or Additional

Access licenses.

• any combination of the above.

When Floating or Additional Access licenses are used FLEXlm requires a pair of daemons to be active on one or

three servers in the network. If no redundancy is required, then these daemons run on one server node. If your net-

work has only a single file server which contains all user files, there is no advantage in having redundant daemons.

If redundancy is desired, FLEXlm allows three server nodes operating as a single “logical” server node. If you

have split your data among two or more server nodes and work is still possible when one of these nodes goes

down or off the network, three server nodes can be employed. Only in very volatile situations or in very large net-

works should more than one server node be required. With three server nodes network licensing remains fully

functional if at least two of the servers are running. In either case, an effort should be made to select stable machi-

nes as server nodes, not machines that are frequently rebooted or shut down.

When there are licensing errors, error messages will be output in the window in which the application was execu-

ted. A listing of these messages may be found in section 7.5 “Licensing Error Messages” on page 10.

6.2 Components of ICEM Licensing

The components of ICEM Licensing are located in the /<install path>/lic directory. On UNIX, a complete

summary of these files is given in the bom_lic (Bill of Materials for Licensing) file found in this directory. Some

of the key files in this directory follow.

Note:On Windows, only the lmgrd, icem, and license.dat files are found in this directory. The FLEXlm utilities are

contained in the single file lmutil found in the /<install path>/bin directory.

1. Aus technischen Gründen ist dieses Kapitel nur in englischer Sprache verfügbar.

README ICEM Licensing Readme file

S99license ICEM license daemon start/stop procedure

autlook ICEM Program to look at your authorizations

bom_lic License utilities bill of materials

icem ICEM license daemon program

license.dat License file

lmcksum License manager program to checksum the license file

lmdiag License manager program to diagnose license problems

6-1

6.2 Components of ICEM Licensing

A complete description of all the files in the lic directory follows later.

6.2.1 Borrowing console Licenses

In ICEM DDN, non-console display (Xterminal) users normally use Additional Access licenses. When an Addi-

tional Access license is unavailable ICEM DDN automatically checks to see if a corresponding served (Floating)

console license is available. If so, it is checked out.

The ICEM DDN license code distinguishes between node-locked (Base) and served licenses (Floating or Additio-

nal Access). ICEM DDN requires a served license whenever the terminal display is not local to the machine on

which ICEM DDN is running.

6.2.2 License Sharing

ICEM DDN allows license sharing. This feature allows an ICEM DDN user with Floating licenses to share a sin-

gle license when multiple ICEM DDN sessions are run on the same workstation at the same display device. That

is, with this option, a user may have an unlimited number of ICEM DDN sessions running at one display and they

will be using only one Floating license for all of them.

There is one restriction with this option. All ICEM DDN users must either turn it on or leave it off. The FLEXlm

licensing daemons do not allow mixing of shared and non-shared licenses. If an attempt is made to run ICEM

DDN sessions simultaneously, with and without License Sharing, the first session accepted by the licensing

daemons will dictate. Users running in the other mode will receive the following error message.

License error 37: Duplicate selection mismatch for this feature

This also means that use of License Sharing is not backward compatible with versions of ICEM DDN before ver-

sion 3.3.

This option is available on the ICEM DDN command line and as a global setting.

The ICEM DDN command line invocation is done by using the License Sharing option ls on the command line.

For example

icemddn tt ls

The global invocation is via a license_sharing file in $ICEM_ACN/lic, as in

/<install path>/lic/license_sharing

If this file exists, license sharing will be used by all ICEM DDN sessions. When this file exists there is no way to

turn off License Sharing. This file is a convenient way to make License Sharing globally available to a user base

once all users are converted from versions of ICEM DDN before version 3.3.

lmdown License manager program to bring license daemons down

lmgrd License manager daemon program

lmhostid License manager hostid generation program

lmremove License manager program to remove a single user’s license for a product

lmreread License manager program to update the license daemon on the fly

lmstat License manager program to report license usage statistics

lmswitchr License manager program to switch the license reporting log file

lmver License manager program to display the FLEXlm version of an executable

6-2

6.3 License File

6.3 License File

The license file contains descriptions of the server nodes that run your license daemon, your ICEM daemon, and

the specific ICEM products you have purchased. The following is an example license file. It is fully explained

below.

# Example ICEM 3.4 license file

SERVER garfield 69062932 1733

DAEMON icem /icem/lic/icem

FEATURE DD icem 3.400 31-jul-2000 0 9B0C2471CB995C24AD5E "Design Drafting" \

690717c7

FEATURE DD icem 3.400 31-dec-2000 2 5B5C543BDD1B41A02649 "Design Drafting"

FEATURE DDX icem 3.400 31-dec-2000 2 0BCC040BE0E683D59F73 "Design Drafting"

FEATURE AD icem 3.400 31-jul-2000 0 8B6C24A12806FDE87C0B "Curves and Surfaces" \

690717c7

FEATURE AD icem 3.400 31-dec-2000 2 4BFCC4FBEC89A970BAAA "Curves and Surfaces"

FEATURE ADX icem 3.400 31-dec-2000 2 6B3C341BBAB8FBA4833E "Curves and Surfaces"

FEATURE NRB icem 3.400 31-dec-2000 2 AB8C849B1A5678EAACB9 "NURBS Geometries"

FEATURE NRBX icem 3.400 31-dec-2000 2 8B4C447182F39D557ED8 "NURBS Geometries"

FEATURE IGE icem 3.400 31-dec-2000 2 8B5C443BB6C90C37F8F2 "IGES Interface"

FEATURE TVD icem 3.400 31-dec-2000 2 DBDC54BBD9179DC9FE24 "VDA/FS Interface"

6.3.1 Example License Summary

The example license is an ICEM 3.4 license file. It contains both served and non-served licenses. The license

daemons must be run on the machine garfield with the hostid 69062932. The applications will communicate with

the license daemons over port number 1733. There is one license daemon defined, icem, which is located in file /

icem/lic/icem. There is no FLEXlm daemon options file. The ”\” denotes continuation to FLEXlm and the

remaining license data is continued on the next line.

Node-locked licenses ("non-served")

Machine-specific licenses are node-locked and are usually non-served licenses, because they have a user count of

zero. This indicates that an unlimited number of users may use this license. Therefore, the license daemons do not

manage the use of licenses with zero users. There are two non-served licenses in the sample license file above, one

for DD and one for AD. These may be used through July 31, 2000 and may only be used on machine 690717c7.

Network licenses ("served"; "Floating" or "Additional Access")

Served licenses are also called network licenses, because the license may be used by anyone in the network. The

license daemon keeps a count of the number of served licenses in use and distributes available licenses to the users

in the network. There are eight served licenses (features) in the sample license file above for DD, DDX, AD,

ADX, NRB, NRBX, IGE, and TVD. Each allows two concurrent users on any machine in the network. These

licenses may be used through December 31, 2000.

These licenses are subdivided into floating (console) licenses and Additional Access (non-console) licenses. The

DDX, ADX, and NURBX features may be used by non-console (typically X-Terminal) users. These Additional

Access licenses can be recognized because they have an "X" after the feature identifier. The served DD, AD,

NRB, IGE, and TVD features are for console use but may also be used by non-console users, if they are not

already being used.

6.3.2 Modifying the License File

The license file may be modified if necessary. There are only five items which can be modified in the lines of the

license file (they are described in more detail below):

6-3

6.3 License File

• the server host name on the SERVER line may be changed

• the order of the SERVER lines may be rearranged (to designate the preferred master and primary backup)

• the port number on the SERVER line(s) may be changed

• the path to the ICEM daemon on the DAEMON line may be changed

• a daemon options file may be added to the DAEMON line

Combining License Files from Multiple Vendors

Note:Do not combine license files for any vendor products which use FLEXlm versions prior to FLEXlm version 2.4.

You may combine FLEXlm type license files if they use the same set of server nodes. To combine them copy the

license files into one file and then remove the extra SERVER lines leaving just one unique set of SERVER lines.

Since the other vendors probably use a different location for their license file you will have to either select one

location to store the combined file or copy it to the default location of each vendor. It is recommended that a neu-

tral location be selected and that the licensing files from all vendors be copied there. This will require changing

the DAEMON line in the license file to point to the new location where the vendor daemon may be found. It is

recommended that the highest version of the FLEXlm license manager daemon, lmgrd, and its utilities (e.g. lmho-

stid and so on) be used to manage combined licenses. You can determine the version of the various lmgrd and

utilities files you have by running the following commands.

<install_path>/lic/lmgrd -v

<install_path>/lic/lmhostid -v

etc.

Whenever you receive a new version of vendor software using FLEXlm licensing you should run the above com-

mands to see whether the new FLEXlm daemon and utilities should be used in place of the current ones.

For ICEM products, if a location other than /icem/lic is used for the licensing files then the LM_LICENSE_FILE

environment variable will need to be set for the users (see below) in the system login file.

On UNIX, only one boot procedure (see S99license below) should be installed in the system boot directory/file.

You will need to review the various vendor boot procedures and determine which one best suits your needs.

COMMENT Lines

Lines beginning with "#" are considered comment lines and ignored.

SERVER Lines

SERVER lines identify which servers are required to use served licenses. They only exist in the license file when

it contains served licenses. A SERVER line consists of 4 fields; keyword, host name, hostid, and port number.

There will be one or three server lines. They may not be deleted when served licenses are present in the license

file. The server host name field may be changed. It must be correct for the machine identified in the hostid field.

The order of the SERVER lines may be rearranged to indicate priority for selecting the master server. The hostid

is hardware dependent. On some machines it may be the ethernet address. In general, it is the number received via

the utility /<install path>/lic/lmhostid. The port number may be changed, it should be the same on all SER-

VER lines.

USE_SERVER Lines

The USE_SERVER line tells the client application to retrieve all subsequent license information from the license

daemon. The remainder of the license file is ignored. A SERVER line must precede the USE_SERVER line in the

license file. This method is recommended when licenses are distributed across many machines. When this method

is used only the server license needs to be updated when changes occur.

6-4

6.3 License File

DAEMON Line

The DAEMON line identifies information about the icem licensing daemon. It only exists in the license file when

it contains a SERVER line. A DAEMON line consists of 4 fields; keyword, daemon name, daemon path, and an

optional FLEXlm daemon options file path. Only the path to the ICEM daemon may be changed if the icem

daemon is located somewhere other than that given. That is, if /<install path> is not /icem, then this field pro-

bably needs to be changed. A daemon options file, field 4, may be added to the DAEMON line.

See the Customization Options section below for use of the daemon options file. More than one DAEMON line

may exist in the license file if all daemons use the same servers.

FEATURE Lines

FEATURE lines identify the features, or products, which are licensed to be used by you. A FEATURE line may

consist of two formats, as follows.

FEATURE feature daemon version expiration_date number_of_users ..

encryption_key "description" [hostid]

or

FEATURE feature daemon version expiration_date number_of_users \

encryption_key [VENDOR_STRING="description"] [HOSTID=hostid] \

[OVERDRAFT=nnn]

There may be an unlimited number of feature lines. None of the fields may be changed. The feature name identi-

fies the product for which you are licensed. The daemon name identifies the vendor daemon to contact when

checking out a served license. The version identifies the highest level version of the product which may be used

with this license. The expiration date allows usage of the product through the date shown. The number of allowed

users identifies how many users may use the product concurrently. The licensing daemons keep track of this infor-

mation. If the number of allowed users is zero, then the license is a non-served license and any number of users

may use the product on the machine specified in the hostid field. The encryption field incorporates all of the SER-

VER, DAEMON, and FEATURE information (except that which may be changed as described above) to prevent

misuse of the license. The description field contains the feature description and sometimes customer information.

The hostid field may or may not be present. If it is present then the license may be used only on that machine. If it

is not present, the license may be used on any machine. Base licenses are node-locked. On Floating and Additio-

nal Access licenses the hostid field will not be present. This means the license may be used on any machine which

is connected to a server which is mentioned in the SERVER line and has this license file installed.

INCREMENT Lines

INCREMENT lines identify additions to licensed features which are defined in the license file. They are issued to

increase the number of users of a FEATURE for a limited period of time. They are only effective when the corre-

sponding FEATURE or UPGRADE line already exists in the license file. The syntax for an INCREMENT line is

identical to that of a FEATURE line.

6.3.3 Alternate License File Path

The default license file path is /<install path>/lic/license.dat for ICEM Licensing. This name can be over-

ridden by setting the environment variable LM_LICENSE_FILE to the pathname of the license file, either on the cli-

ent machines, on the server machines, or both:


setenv LM_LICENSE_FILE

[:<port@host>][:<port@host2>]<license_file_path>[:<license_file_path2>]

where:

6-5

6.4 Customization Options

– <port@host>

Port number and host where to obtain license file information from the license manager daemon.

– <port@host2>

Alternative port number and host where to obtain license file information from the license manager

daemon.

– <license_file_path>

Full path to the license file.

– <license_file_path2>

Full path to an alternative license file.

Note:

The information <port@host> must be the first information in a row of several location specifiers. It can be follo-

wed by an arbitrary number of other <port@host> or <license_file_path> specifiers. There must be at least one

location specifier that points to a valid license file or license manager daemon. Examples:

setenv LM_LICENSE_FILE /icem/lic/license.dat or

setenv LM_LICENSE_FILE /icem/lic/license.dat /home/joe/license.dat or

setenv LM_LICENSE_FILE 1733@james:/icem/lic/license.dat or

setenv LM_LICENSE_FILE 1733@james:1733@beluga:/icem/lic/license.dat

The ":" (colon) separated location specifier list may be used when multiple vendor license files are used.


Set the LM_LICENSE_FILE environment variable in the System Properties option of the Control Panel. Use the

same syntax as for the ”UNIX Workstations” above, except that the file separator for Windows is a ”;” (semi

colon) rather than a colon.

Note:Most FLEXlm utilities will accept a "-c <license_file>" option to specify a different license file location.

Note:Using the "port@host" method of retrieving the license file information will add to network traffic and may cause

some application startup delay on heavily used networks or if the license file exceeds 250 lines. License informa-

tion will be retrieved only once per session.


You have two customization options. You can create individual user options files, or a daemon options file for any

ICEM application.

For ICEM DDN you can create an options file, icemopt_310. This file limits the options checcked out at startup of

ICEM DDN to the options defined in the file. The program which creates and maintains this binary file is optdef.

See section 7.2 “The Program optdef” on page 3 for a full description of optdef.

ICEM DDN tries to locate the file icemopt_310 in the following order:

1. ICEM DDN will check for an environment variable ICEMOPT_310. If it finds this environment variable it will

use the path contained in the variable as the path of the icemopt_310 file.

2. Next, ICEM DDN will check for a user’s icemopt_310 file in modals/icemopt_310 in the current working

directory.

3. Then, ICEM DDN will check for a default icemopt_310 file in $ICEM_ACN/ddn/modals/icemopt_310 where

$ICEM_ACN defaults to /icem when not defined.

6-6


You can also customize the use of the ICEM software via the daemon options file supported by FLEXlm. This

options file should not be confused with the icemopt_310 file described above. These two files are completely

separate and distinct.

The daemon options file allows you to reserve licenses for specified users or groups of users, to allow or disallow

use of the software to certain people, and to log activity. This file is created on site by your ICEM Licensing admi-

nistrator.

Note:Without a daemon options file, anyone having access to your license file can use your licenses.

This file may contain the following options.

In order to use the daemon options capability, you create a daemon options file and list its pathname as the fourth

field on the "DAEMON" line in the license file.

A daemon options file consists of lines in the following format:

EXCLUDE feature {USER | HOST | DISPLAY | GROUP} name

EXCLUDEALL {USER | HOST | DISPLAY | GROUP} name

GROUP groupname <list_of_users>

HOST_GROUP groupname <list_of_host_names>

INCLUDE feature {USER | HOST | DISPLAY | GROUP} name

INCLUDEALL {USER | HOST | DISPLAY | GROUP} name

LINGER feature interval_seconds

NOLOG {IN | OUT | DENIED | QUEUED}

REPORTLOG [+]file

RESERVE number feature {USER | HOST | DISPLAY | GROUP} name

Lines beginning with the character ’#’ are ignored, and can be used as comments. All entries in the daemon opti-

ons file are case sensitive. FLEXlm 2.4 limits line length to 200 characters. FLEXlm 4.1 limits line length to 2048

characters and recognizes the "\" continuation character.

If the filename in the REPORTLOG line starts with a ’+’ character, the old report log file will be opened for

append, otherwise it will be overwritten.

For example, the following options file would reserve a copy of feature "NC" for user pat, a copy for user lee,

and three copies for anyone on a computer with the hostname terry. In addition, user joe would not be allowed to

use the "NC" feature:

EXCLUDE allows you to exclude certain users use of the ICEM software.

EXCLUDEALL allows you to exclude certain users use of all ICEM software.

GROUP allows the specification of a group of users for use in the other commands.

HOST_GROUP allows the specification of a group of hosts for use in the other commands.

INCLUDE allows you to specify a list of users who are allowed access to the ICEM software.

INCLUDEALL allows you to specify a list of users who are allowed access to all ICEM software.

LINGER causes the vendor daemon to hold specified licenses for the user for a certain period of time after the they check them in.

NOLOG causes messages of the specified type to be filtered out of the daemon’s log output.

REPORTLOG specifies that a logfile be written.

RESERVE insures that the ICEM application software will always be available to one or more users or on one or more host computer systems.

6-7

6.5 Three Server Configurations

RESERVE 1 NC USER pat

RESERVE 1 NC USER lee

RESERVE 3 NC HOST terry

EXCLUDE NC USER joe

If this data were in file /<install path>/lic/local.options, then you would modify the license file DAEMON

line to add a fourth field as follows:

DAEMON icem /<install path>/lic/icem /<install path>/lic/local.options

6.5 Three Server Configurations

When three server nodes are used one node becomes the master node, and the other two are backups. Generally,

the first server listed in the license file will be chosen as the master node when the servers are started. If there is a

delay in starting the first server node, or slow communications occur, it is possible that the second node will be

chosen. Once a master server is chosen it will remain the master unless it is shutdown or the system crashes.

When the master server is shutdown then the remaining servers determine if there is a quorum, and if so, normally

the second server listed in the license file will become the master server. Generally, this takes place within just a

few moments. Occasionally, with a system crash, the remaining servers may not be aware of the loss of the master

server for several minutes. Quorum may take up to ten minutes to be re-established, but normally it is much quik-

ker. Licenses may continue to be checked out and in as long as at least two servers are running.

The order of the SERVER lines may be rearranged in the license file to take advantage of a more stable or higher

performance machine to be the master server.

Generally, the licensing daemons have little impact on network performance. The general load factor of the net-

work does, however, influence the licensing performance. On a highly loaded network, there may be delays in

application initialization, during license checkout, and listing license status (e. g. ICEM DDN menu f.1.17.5.1 or

autlook).

6.6 The License Daemon /<install_path>/lic/lmgrd

Note:On UNIX, the license daemon is normally started by S99license (see below).

The license daemon lmgrd is a standard component of FLEXlm. It is the daemon process that sends client proces-

ses to the ICEM daemon on the correct machine. This daemon does not dispense licenses; i. e., it processes no

user requests on its own, but forwards these requests to the icem daemon. The license daemon allows you to set

the license file location and the server-to-server connection timeout interval. These options are set by command

line arguments when starting lmgrd.

The command line for lmgrd is:

lmgrd [-app] [-2] [-p -2] [-c <license>] [-t <timeout>] [-s <interval>]

[-l <logfile>] [-x lmdown | lmremove] [-v] [-z]

where:

-app Windows only. Run lmgrd in a command prompt (MS-DOS) window. To shut down lmgrd, you will need to run lmdown in a second command prompt window.

-2 Use the FLEXlm v2.4 startup arguments.

6-8

6.7 The ICEM Daemon /<install path>/lic/icem

6.7 The ICEM Daemon /<install path>/lic/icem

This is the daemon that dispenses licenses for requested ICEM products. It contains the ICEM Systems private

encryption code. It is started by the lmgrd daemon. This daemon is also called the "vendor daemon".

6.8 The License Finder

The license manager daemon, lmgrd, may also be run as a license finder. The license finder provides one interface

to access the license files. Rather than setup the LM_LICENSE_FILE environment variable for each user, the finder

will tell the application where to find the license files. This is particularly useful when the you want to use the

"port@host" method of retrieving the license file information rather than distributing new license files to each

machine or setting LM_LICENSE_FILE for each user.

Note:Using the license finder and the "port@host" method of retrieving the license file information will add to network

traffic and may cause some application startup delay on heavily used networks or if the license file exceeds 250

lines. The finder will be contacted only once per session and license information will be retrieved once per ses-

sion.

The following is the order of priority, in descending order, for finding the license file.

• Force usage of the license finder via existence of the environment variable FLEXLM_USE_FINDER. The variable's

content is irrelevant.

• Force license file search path via license file list in environment variable LM_LICENSE_FILE.

• Check /etc/hosts file for flexlm license finder aliases (see below) and if found attempt to contact the license

finder.

• If environment variable ICEM_ACN exists, use $ICEM_ACN/lic/license.dat for path to license file.

• Use /icem/lic/license.dat for path to license file.

-p -2 Restricts usage of lmdown, lmreread and lmremove to a FLEXlm administrator who is by default root if user lmadmin does not exist. Requires "-2" option.

-c <license> Is the pathname to the license file.

-t <timeout> Is the interval (in seconds) during which daemons must complete connections to each other. The default value is ten seconds. A longer value may be desirable if the daemons are being run on busy systems and/or a very heavily loaded network. S99license default is 15 seconds.

-s <interval> Is the logfile stamp interval, in minutes. The default is 360 minutes.

-l <logfile> Is the file where the output log is to be written. The default is standard output.

-x lmdown Disable lmdown command. Will require kill command to stop the licensing daemons.

-x lmremove Disable lmremove command. Will require stopping the licensing daemons to free licenses being held by non-existing processes.

-v Display FLEXlm version of lmgrd and exit.

-z Run lmgrd in foreground. Default at v4.1 is to run lmgrd in the background.

6-9

6.9 Other Utilities in /<install_path>/lic

6.8.1 Setup

By default, FLEXlm uses the "official" FLEXlm port number of 744 to connect to the license finder on the finder

server(s). If you do not want the finder running under root you will need to specify an alternate FLEXlm port

number above 1024 in the /etc/services file. You will need to add this entry in the /etc/services file on each

finder server and each machine contacting the finder server(s). If, for example, you were to select port 1734

instead, the

/etc/services entry on the finder server would look like the following.

FLEXlm 1734/tcp #FLEXlm license finder port

The finder server machine(s) may be different from the ICEM Licensing server machines.

Alias names must be added to the /etc/hosts file on each of the machines which will try to contact a finder ser-

ver(s). The alias names are:

flexlm_license_finder flexlm_license_finder2 flexlm_license_finder3

These names will be searched for in the above order. The application will contact the finder server and attempt to

connect to the finder.

6.8.2 License Finder Usage

The command line for running lmgrd as a license finder is:

lmgrd -f <finder_file>

where:

The finder file format is:

DATA lfpath

<license_file_path1>[:<license_file_path2>][:<port@host>]

where:


The following files are provided by FLEXlm and ICEM Systems GmbH for various purposes.

Note:On Windows, the FLEXlm utilities are all combined into the single file lmutil, which is found in the /<install

path>/bin directory. To execute the FLEXlm commands described below, precede each command with the com-

mand lmutil, for example:

lmutil lmhostid

-f <finder_file> Specifies the path to license finder data file.

lfpath Finder keyword

<license_file_path1> Full path to the license file

<port@host> Port number and host where to obtain license file information from the license manager daemon

6-10


6.9.1 autlook

The autlook utility can be used to obtain license options information. It displays the number of installed and

available licenses, the expiration date, the hostid if a license is only available on a specified host, a list of users and

the number of licenses held by the user. Refer to section 7.1 “The Program autlook” on page 1 for more informa-

tion on the autlook program.

6.9.2 optdef

The program optdef can be used to define license option requirements for ICEM 3.4 Design/Drafting sessions.

When starting ICEM 3.4 Design/Drafting it will, by default, attempt to request all ICEM 3.4 modules. An option

will be available if you have purchased at least one license for it. By running the program optdef you can define a

set of license options and ICEM 3.4 Design/Drafting will only request this set of license options. See section 7.1

“The Program autlook” on page 1 for a complete description of optdef.

6.9.3 lmcksum

The lmcksum utility does a FLEXlm context specific checksum of the license file. This is useful for checking the

accuracy of distributed or modified license files against the one delivered.

lmcksum -c <license_file>

where:

6.9.4 lmdiag

The lmdiag utility allows you to diagnose problems when you can not checkout a license.

lmdiag -c <license_file> <feature>

where:

The <feature> is the name found in the field immediately after the FEATURE or INCREMENT keyword on

FEATURE or INCREMENT lines.

6.9.5 lmdown

Note:The lmdown utility is normally run by S99license (see below).

The lmdown utility allows for the graceful shutdown of all license daemons (both /<install path>/lic/lmgrd

and /<install path>/lic/icem) on all nodes.

lmdown -c <license_file>

where:

-c <license_file> Use specified license file.


<feature> Name of feature to diagnose.

6-11


You should protect the execution of lmdown, since shutting down the servers will cause loss of licenses.

6.9.6 lmhostid

The lmhostid program is used to print the correct host ID value on any machine supported by FLEXlm. FLEXlm

uses different machine identifications for different machine architectures. The output from lmhostid will be simi-

lar to the following:

lmhostid - Copyright (C) 1989-1998 Globetrotter Software, Inc.

The FLEXlm host ID of this machine is "6907b241"

6.9.7 lmremove

The lmremove utility allows you to remove a single user’s license for a specified product. This could be required in

the case where a licensed user was running software on a node that subsequently crashed. This situation will

sometimes cause the license to remain unusable. lmremove will allow the license to return to the pool of licenses.

lmremove -c <license_file> <feature> <user> <host> <display>

where:

lmremove removes all instances of user on node host on display from usage of feature (product). You should pro-

tect the execution of lmremove since removing a user’s license can be disruptive.

6.9.8 lmreread

The lmreread utility causes the license daemon to reread the license file. It is a signal to the ICEM daemon to

reread the license file for changes in feature (product) licensing information.

lmreread -c <license_file>

lmreread cannot be used to change server node names or port numbers.

Note:The license file specified on the lmreread command line is only used by lmreread to obtain the port number for

contacting the licensing daemons. The daemons will read from the license file path given at startup, not the

license file specified on this command line.



<feature> name of feature to remove

<user> name of user to remove feature from

<host> name of host where user is found

<display> name of display on host

6-12


6.9.9 lmstat

Note:The ICEM autlook utility provides a similar function displaying all information about current users.

License administration is simplified by the lmstat utility. It allows you to instantly monitor the status of all net-

work licensing activities and license management operations, including:

• which daemons are running

• users of individual products

• users of products served by the ICEM daemon

lmstat [-a] [-S [icem]] [-f [<feature>]] [-s [<server>]] \

[-t <value>] [-c <license_file>] \

[-A] [-l [<regular expression>]]

where:

6.9.10 lmswitchr

The lmswitchr utility switches the log file name for the report log

lmswitchr -c <license_file> <feature> <new_log_file>

where:

You should protect the execution of lmswitchr since it should only be used for administrative purposes.

6.9.11 lmver

The lmver utility displays the FLEXlm version of the libraries used when an executable was built.

lmver <filename>

-a displays everything

-S lists all users of the ICEM daemon’s (icem) features

-f <feature> lists users of feature(s)

-s <server> displays status of server node(s)

-t <value> sets lmstat timeout to "value"

-c <license_file> use specified license file

-A lists all active licenses

-l <regular expression> lists users of license(s) matching the regular expres-sion

-c <license_file> use specified license file

<feature> feature name to switch reporting on

<new_log_file> path to new report log file

6-13

6.10 The License Daemon Log File

where:

6.9.12 S99license (UNIX only)

The S99license utility is a startup script. If it is installed under a directory which is executed when the machine

boots, it starts the license daemon at boot time. S99license may also be used to manually shutdown and restart

the license daemon and ICEM daemon on a single server.

• S99license start

• S99license stop

• S99license down

Where start starts the ICEM license daemons on the current machine, stop stops (kills) the ICEM license

daemons only on the current machine. The down option shuts down the ICEM daemons on all machines in the net-

work.

Be sure that S99license is always used with a valid license file path. We recommend naming the license file /

<install path>/lic/license.dat. If you want to use a different license file location, use the environment varia-

ble LM_LICENSE_FILE to override the default location of the license file:

setenv LM_LICENSE_FILE <license_file_path>

where:

The startup script will automatically create a log file in /<install path>/lic/license.log each time it starts up

the daemon. If a license log file already exists at that location it will be moved to a name which includes the date

and time when moved. These backed up log files may be deleted when they are no longer of use.


The daemons all generate log files in the following format.

mm/dd hh:mm (<DAEMON NAME>) message

where:

Log files can be used to:

• inform users of daemon status

<filename> name of executable to check

<license_file_path> is the full pathname to a copy of the license file

mm/dd hh:mm is the time that the message was logged

<DAEMON NAME> is either the license daemon lmgrd or the ICEM daemon icem

message is the text of the message

6-14


• diagnose configuration problems

• diagnose daemon software errors

A sample license daemon log file is located in section 7.3 “Sample License Daemon Log File” on page 4. License

daemon messages are described in section 7.4 “License Daemon Log File Messages” on page 6.

6-15


6-16

Kapitel 7 License Management and Error Messages

Kapitel 7 License Management and Error Messages1

7.1 The Program autlook

The program autlook can be used to get license options information. It displays the number of installed and

available licenses, the expiration date, the hostid if a license is only available on a specified host, a list of users and

the number of licenses held by the user.

Setup the autlook command execution as follows:

• UNIX command window:

setenv LM_LICENSE_FILE /<install_path>/lic/license.dat

/<install_path>/lic/autlook | more

• Windows MS-DOS command window:

set LM_LICENSE_FILE \<install_path>\lic\license.dat

\<install_path>\lic\autlook | more

The autlook output is organized by product number. The output for each product number is in three sections:

The #Lic. User, User Name, and Host Name are repeated for each license checked out for this product.

When started the program autlook gives the following kind of display:

For ICEM 3.4, the following options are installed/available at this time:

Product Description Installed\X Available\X

#Licenses Exp.-date Host ID

#Lic. User User name Host name

-----------------------------------------------------------------

DD DESIGN/DRAFTING unlimited\2 2\1

----------- ------------ ---------

3 31-dec-2000 network

unlimited 31-dec-2000 9ee11504

1. Aus technischen Gründen ist dieses Kapitel nur in englischer Sprache verfügbar.

Column Name Description

ProductDescriptionInstalled \XAvailable \X

Product numberSelf explanatoryTotal number of Console/Additional Access licenses you have installed for this productTotal number of Console/Additional Access licenses you have available to be used on this machine at this moment, e. g. not being used by someone

#LicensesExp. DateHost ID

Number of licenses installed by machineExpiration date for these licensesThe machine ID on which this license may be used. If "network" is displayed, it is a floa-ting license which is usable on any machine in the network.

#Lic. User

User NameHost Name

Number of licenses for this product used by a particular user on a particular machine (always 1, multiple occurrences of the same user are listed multiple times)User name of user using product on a particular machineHost id of the machine on which the product is being used

7-1

7.1 The Program autlook

2 31-dec-2000 xterm

---------- ------------ ---------

1 abc mach01

1 xyz mach02

AD CURVES AND SURFACES unlimited 1

---------- ------------ ---------



---------- ------------ --------

1 abc mach01

1 xyz mach02

NRB NURBS GEOMETRY unlimited 0

---------- ------------ --------


---------- ------------ ---------

*** no user information ***

NC NC BASIC 1 1

---------- ------------ ---------


---------- ------------ ---------

*** no user information ***

The above example indicates that for Design/Drafting (DD) there are an unlimited number of Console licenses

and 2 Additional Access licenses installed. Of these, 2 Console and 1 Additional Access licenses are available to

this machine at this time. There are three DD license entries in the license file which provide these licenses. The

first entry is a Floating (network) option, which licenses 3 console users on any machine in the network. The

second is a Base (node-locked, non-served) option which licenses an unlimited number of console users on

machine 9ee11504. We know it is a Base option because it licenses an unlimited number of users. The last entry is

an Additional Access (xterm) option which licenses 2 non-console users on any machine in the network. The

counted licenses require use of the licensing daemons. Currently, of the 2 licenses checked out, 1 is a Floating

license and 1 is an Additional Access license. There are 3 licenses available to this machine at this time, 2 Floa-

ting and 1 Additional Access. Actually, because they are Floating and Additional Access options, they are availa-

ble to any machine in this network. We know the current machine is not 9ee11504, otherwise the number of

Console licenses available to it would be shown as unlimited. Because the 9ee11504 licenses are not served, we

cannot know if anyone is using them. The ICEM daemon keeps track of the licenses checked out and reports them

to autlook. The two licenses are held by users abc on mach01 and xyz on mach02. We do not know from this infor-

mation which is the console user and which is the Additional Access user.

For Curves and Surfaces (AD) there are an unlimited number of Console licenses installed. Of these, 1 is available

on this machine at this time. There are no Additional Access licenses installed. There are two AD entries in the

license file which provide these licenses. The first entry is a Floating option, which licenses 3 console users. The

second is a Base option which licenses an unlimited number of console users on machine 9ee11504. Currently, of

the 2 licenses checked out, one is being used by a console user, the other by a non-console user. We know this

from the DD licenses above. Additional Access users may "borrow" available Floating licenses when an Additio-

nal Access license is unavailable. Base licenses may not be "borrowed" by Additional Access users. They may

only be used at the console. Again, because the 9ee11504 option is not served, we cannot know if anyone is using

it. The two licenses are held by users abc on mach01 and xyz on mach02. We do not know from this information

which is the console user and which is the additional access user.

For NURBS Geometry there is just one option installed, a Base option which licenses an unlimited number of

console users on machine 9ee11504. Again, we cannot know anything about its usage.

7-2

7.2 The Program optdef

For NC Basic there is just one option installed, a Floating option which licenses one console user on any machine

in the network. Currently all licenses are available. No license is in use and therefore no user information is

available.

7.2 The Program optdef

The program optdef can be used to define license option requirements for ICEM 3.4 Design/Drafting sessions.

When starting ICEM 3.4 Design/Drafting it will, by default, attempt to request all ICEM 3.4 modules. An option

will be available if you have purchased at least one license for it. By running the program optdef you can define a

set of license options and ICEM 3.4 Design/Drafting will only request this set of license options.

Setup the optdef command execution as follows:

• UNIX command window:

setenv LM_LICENSE_FILE /<install_path>/lic/license.dat

/<install_path>/bin/optdef

• Windows MS-DOS command window:

set LM_LICENSE_FILE \<install_path>\lic\license.dat

\<install_path>\bin\optdef

The optdef program displays the licensed option product mnemonic, description, the current availability and the

selection status. By keying in ordinals of options the user can select them. After every input line the display is

repeated with updated status. A selection can also be undone. Some options have prerequisites. When an option

which requires a prerequisite is selected, and that prerequisite has not been selected, the program automatically

adds it to the list of selections. An option cannot be selected if its prerequisite(s) are not available. When the pro-

gram ends, the final status is stored in the current working directory under modals/icemopt_310. If this file does

not exist, ICEM 3.4 Design/Drafting will request all options for which there is a license.

When optdef is started and the directory ‘modals’ does not exist under the current working directory, optdef ter-

minates with the following message:

DIRECTORY ’$cwd/modals’ DOES NOT EXIST

If the directory $cwd/modals exists, optdef prints something like the following:

ICEMDDN 3.4.0 options selection:

Ordinal Product Description Available Selected

------------------------------------------------------------------------

1 DD DESIGN/DRAFTING X

2 AD CURVES AND SURFACES X

3 NRB NURBS/GEOMETRY X

4 NC NC BASIC

5 PAR 2D PARAMETRICS X

To select, key in the ordinals separated by spaces or "+".

To drop, use "-" before ordinal. Terminate by empty line:

The above example assumes that only the first 5 options are licensed, and that NC BASIC is not available cur-

rently (used elsewhere).

If the input is not numeric, the following error message appears:

WRONG INPUT; SUPPLY 1 OR 2 DIGITS

If the input is numeric, but none of the choices is given above, the following error message appears:

7-3

7.3 Sample License Daemon Log File

WRONG INPUT; SUPPLY ONLY LISTED ORDINALS

Assume the user keys in "5-3" followed by carriage return. Then the display appears:

Ordinal Product Description Available Selected

------------------------------------------------------------------------

1 DD DESIGN/DRAFTING X

2 AD CURVES AND SURFACES X

3 NRB NURBS/GEOMETRY X

4 NC NC BASIC

5 PAR 2D PARAMETRICS X

To select, key in the ordinals separated by spaces or "+".

To drop, use "-" before ordinal. Terminate by empty line:

To terminate the user presses the RETURN key without any input. This stores the current selection under $cwd/

modals/icemopt_310. The next call of optdef will read them again.

If no changes were made optdef ends with the message:

NO OPTIONS SPECIFIED; LEAVE ’$cwd/modals/icemopt_310’ UNCHANGED

If you do not want ICEM 3.4 Design/Drafting users to run optdef you should protect the execution of optdef.


The following sample license daemon log files illustrate the correct starting of the Flexible License Manger

FLEXlm™, with the license daemons lmgrd and the ICEM 3.4 daemon "icem". The example configuration based

on a license file with a set of three server nodes, any two of which must be running for the system to function. On

sites with multiple redundant servers, one of the servers is selected as the master node. The first server in the list

which is available at the time a quorum is established will be the master. If the master is going down and a quorum

is up the next specified server will be the master.

The ICEM products Design/Drafting ("DD"), 2D Parametrics ("PAR"), Design Tools ("DTO"), and Curves and

Surfaces ("AD") are all licensed for 10 users. This sample license file allows anyone on the network able to reach

the server nodes via TCP/IP to use this ICEM software up to the concurrent limit of 10 users. ICEM Licensing is

installed on the server nodes under /<install path>/lic.

Sample License File /<install path>/lic/license.dat

SERVER pat 69003456 1733

SERVER lee 69004355 1733

SERVER terry 69007ea8 1733

DAEMON icem /<install path>/lic/icem

FEATURE DD icem 3.4 31-dec-2000 10 1EF890030EABF324 "Design/Drafting"

FEATURE PAR icem 3.4 31-dec-2000 10 1E078451FE98BA07 "2D Parametrics"

FEATURE DTO icem 3.4 31-dec-2000 10 12A07F009E40B037 "Design Tools"

FEATURE AD icem 3.4 31-dec-2000 10 4B38F001109BF80A "Curves & Surfaces"

Sample License Daemon Log File /<install path>/lic/license.log (UNIX)or /winnt/system32/lmgrd.log (Windows) for License Server pat

Server "pat" is the first server in the list. It will be the master.

15:13:03 (lmgrd) ----------------------------------------------

15:13:03 (lmgrd) Please Note:

15:13:03 (lmgrd)

15:13:03 (lmgrd) This log is intended for debug purposes only.

15:13:03 (lmgrd) There are many details in licensing policies

7-4


15:13:03 (lmgrd) that are not reported in the information logged

15:13:03 (lmgrd) here, so if you use this log file for any kind

15:13:03 (lmgrd) of usage reporting you will generally produce

15:13:03 (lmgrd) incorrect results.

15:13:03 (lmgrd)

15:13:03 (lmgrd) ----------------------------------------------

15:13:03 (lmgrd)

15:13:03 (lmgrd)

15:13:03 (lmgrd) FLEXlm (v6.1) started on pat (hp 9000/730) (9/8/2000)

15:13:03 (lmgrd) FLEXlm Copyright 1988-2000, Globetrotter Software, Inc.

15:13:03 (lmgrd) World Wide Web: http://www.globetrotter.com

15:13:03 (lmgrd) License file: "/icem/lic/license.dat"

15:13:03 (lmgrd) Trying connection to terry

15:13:03 (lmgrd) Trying connection to lee

15:13:06 (lmgrd) Connected to lee

15:13:06 (lmgrd) CONNECTED, master is pat

15:13:06 (lmgrd) Starting vendor daemons ...

15:13:06(lmgrd) Started icem (internet tcp_port 1353 pid 3669

15:13:07 (icem) Server started on pat for: DD

15:13:07 (icem) PAR DTO AD

15:13:08 (icem) Trying connection to terry

15:13:08 (icem) Connected to lee

15:13:40 (lmgrd) Connected to terry

15:13:41 (icem) Connected to terry

15:18:41 (icem) OUT: "DD" user1@host1

15:18:41 (icem) OUT: "AD" user1@host1

15:18:42 (icem) OUT: "PAR" user1@host1

15:18:43 (icem) OUT: "DTO" user1@host1

15:18:51 (icem) IN: "DD" user1@host1

15:18:51 (icem) IN: "PAR" user1@host1

15:18:51 (icem) IN: "DTO" user1@host1

15:18:51 (icem) IN: "AD" user1@host1

Sample License Daemon Log File /<install path>/lic/license.log (UNIX) or /winnt/system32/lmgrd.log (Windows) for License Server "lee"

15:13:05 (lmgrd) ----------------------------------------------


15:13:05 (lmgrd)







15:13:05 (lmgrd)

15:13:05 (lmgrd) ----------------------------------------------

15:13:05 (lmgrd)

15:13:05 (lmgrd)

15:13:05 (lmgrd) FLEXlm (v6.1) started on lee (IBM RS/6000) (9/8/2000)




15:13:06 (lmgrd) Trying connection to terry

15:13:06 (lmgrd) Connected to pat


15:13:06 (lmgrd) Starting vendor daemons . . .

15:13:06 (lmgrd) Started icem (internet tcp_port 1050 pid 12593)

15:13:08 (icem) Trying connection to terry

7-5

7.4 License Daemon Log File Messages

15:13:08 (icem) Connected to pat

15:13:25 (lmgrd) Connected to terry

15:13:41 (icem) Connected to terry

Sample License Daemon Log File /<install path>/lic/license.log (UNIX)or /winnt/system32/lmgrd.log (Windows) for License Server "terry"

15:13:25 (lmgrd) ----------------------------------------------


15:13:25 (lmgrd)







15:13:25 (lmgrd)

15:13:25 (lmgrd) ----------------------------------------------

15:13:25 (lmgrd)

15:13:25 (lmgrd)

15:13:25 (lmgrd) FLEXlm (v6.1) started on terry (sgi IP22) (9/8/2000)




15:13:25 (lmgrd) Connected to pat

15:13:25 (lmgrd) Connected to lee

15:13:40 (lmgrd) selected (EXISTING) master pat


15:13:40 (lmgrd) Starting vendor daemons . . .

15:13:40 (lmgrd) Started icem (internet tcp_port 8366 pid 3727)

15:13:41 (icem) Connected to lee

15:13:41 (icem) Connected to pat


Note:The ICEM daemon "icem" is referred to as "vendor daemon" below.

License Daemon Log File Informational Messages

• Connected to <node>

The daemon is connected to its peer on node <node>.

• CONNECTED, master is <hostname>

The license daemons log this message when a quorum is up and everyone has selected a master.

• DEMO mode supports only one SERVER host!

An attempt was made to configure a demo version of the software for more than one server host.

• DENIED: <n> <feature> to <user> (<mm/dd/yy hh:mm>)

<user> was denied access to <n> licenses of <feature>.

• EXITING DUE TO SIGNAL <nnn>

• EXITING with code <nnn>

All daemons list the reason that the daemon has exited.

7-6


• EXPIRED: <feature>

<feature> has passed its expiration date

• FLEXlm started on <node>

The license daemon was started on node <node>

• IN: <feature> by <user> (<n> licenses) (used: <d:hh:mm:ss>)

<user> has checked back in <n> licenses of <feature> at <mm/dd/yy hh:mm>.

• IN server died: <feature> by <user> (<n> licenses) (used: <d:hh:mm:ss>)

<user> has checked in <n> licenses by virtue of the fact that his server died.

• Lost connection to <hostname>

A daemon can no longer communicate with its peer on node <hostname>, which may force the clients to have

to reconnect, or cause the number of daemons to go below the minimum number, in which case clients may

start exiting. If the license daemons lose the connection to the master, they will kill all the vendor daemons;

vendor daemons will shut themselves down.

• Lost quorum

The daemon lost quorum, so will process only connection requests from other daemons.

• MASTER SERVER died due to signal <nnn>

The license daemon received fatal signal <nnn>.

• MULTIPLE <xxx> servers running. Please kill, and restart license daemon

The license daemon has detected that multiple copies of vendor daemon <xxx> are running. The user should

kill all <xxx> daemon processes and re-start the license daemon.

• OUT: <feature> by <user> (<n> licenses) (<mm/dd/yy hh:mm>)

<user> has checked out <n> licenses of <feature> at <mm/dd/yy hh:mm>

• Removing clients of children

The top-level daemon logs this message when one of the child daemons dies.

• RESERVE <feature> for HOST <name>

• RESERVE <feature> for USER <name>

A license of <feature> is reserved for either user <name> or host <name>.

• REStarted <xxx> (internet port <nnn>)

Vendor daemon <xxx> was restarted at internet port <nnn>.

• Retrying socket bind (address in use)

The license servers try to bind their sockets for approximately 6 minutes if they detect "address in use" errors.

• Selected (EXISTING) master <node>.

This license daemon has selected an existing master <node> as the master.

• SERVER shutdown requested.

A daemon was requested to shut down via a user-generated kill command.

• Server started on <node> for: <feature><feature>....

A (possibly new) server was started for the features listed.

• Shutting down <xxx>

The license daemon is shutting down the vendor daemon <xxx>.

• SIGCHLD received. Killing child servers

A vendor daemon logs this message when a shutdown was requested by the license daemon.

• Started <name>

The license daemon logs this message whenever it starts a new vendor daemon.

7-7


• Trying connection to <node>

The daemon is attempting a connection to <node>.

• Using license file <license_file>

The license daemon is using the license file <license_file>.

License Daemon Log File Configuration Problems

• <hostname>: Not a valid server host, exiting

This daemon was run on an invalid <hostname>.

• <hostname>: Wrong hostid, exiting

The hostid is wrong for <hostname>.

• BAD CODE for <feature>

The specified <feature> has a bad encryption code.

• Couldn’t find a master

The daemons could not agree on a master.

• lmgrd: lost all connections

This message is logged when all the connections to a server are lost, which often indicates a network problem.

• lost lock, exiting

• Error closing lock file

• Unable to re-open lock file

The vendor daemon has a problem with its lock file, usually because of an attempt to run more than one copy

of the daemon on a single node. Locate the other daemon that is running via a ps command, and kill it with

kill -9.

• NO DAEMON line for <daemon>

The license file does not contain a "DAEMON" line for <daemon>

• No <license> service found

The TCP <license> service did not exist in /etc/services.

• No license data for <feature>, feature unsupported

There is no feature line for <feature> in the license file.

• No features to serve!

A vendor daemon found no features to serve. This could be caused by bad data in the license file.

• UNSUPPORTED FEATURE <request>: <feature> by <user>

The user <user> has requested a <feature> that this vendor daemon does not support. This can happen for a

number of reasons: the license file is bad, the feature has expired, or the daemon is accessing the wrong license

file.

• Unknown host: <hostname>

The hostname specified on a "SERVER" line in the license file does not exist in the network database (pro-

bably /etc/hosts).

• <license_server>: lost all connections

This message is logged when all the connections to a server are lost. This probably indicates a network pro-

blem.

• NO DAEMON lines, exiting

The license daemon logs this message if there are no "DAEMON" lines in the license file. Since there are no

vendor daemons to start, there is nothing to do.

7-8


• NO DAEMON line for <name>

A vendor daemon logs this error if it cannot find its own DAEMON <name> in the license file.

License Daemon Log File Daemon Software Errors

• accept: <message>

An error was detected in the "accept" system call.

• ATTEMPT TO START VENDOR DAEMON <xxx >with NO MASTER

A vendor daemon <xxx> was started with no master selected. This is an internal consistency error in the

daemons.

• BAD PID message from <nnn>: pid: <xxx> (<message>)

A top-level vendor daemon received an invalid PID message from one of its children (daemon number <xxx>).

• BAD SCONNECT message: (<message>)

An invalid "server connect" message was received.

• Cannot create pipes for server communication

The "pipe" call failed.

• Can’t allocate server table space

A malloc error. Check swap space.

• Connection to <node> TIMED OUT

The daemon could not connect to <node>

• Error sending PID to master server

The vendor server could not send its PID to the top-level server in the hierarchy.

• Illegal connection request to <DAEMON>

A connection request was made to <DAEMON>, but this vendor daemon is not <DAEMON>

• Illegal server connection request

A connection request came in from another server without a DAEMON name.

• KILL of child failed, errno = <nnn>

A daemon could not kill its child.

• No internet port number specified

A vendor daemon was started without an internet port.

• Not enough descriptors to re-create pipes

The "top-level" daemon detected one of its sub-daemon's death. In trying to restart the chain of sub-daemons,

it was unable to get the file descriptors to set up the pipes to communicate. This is a fatal error, and the

daemons must be re-started.

• read: <error message>

An error in a "read" system call was detected.

• recycle_control BUT WE DIDN’T HAVE CONTROL

The hierarchy of vendor daemons has become confused over who holds the control token. This is an internal

error.

• return_reserved: can’t find feature listhead

When a daemon is returning a reservation to the "free reservation" list, it could not find the listhead of features.

• select: <message>

An error in a select system call was detected.

• Server exiting

The server is exiting. This is normally due to an error.

7-9

7.5 Licensing Error Messages


If an ICEM application encounters errors when trying to checkout licenses or establish communications with the

licensing daemons, the following error messages may be output in the execution window. These are FLEXlm

reported error conditions. Depending upon the application, they may be displayed as either positive or negative

numbers. There are also ICEM specific licensing errors which are listed at the end of this section.

Error Code

Message Description

1 cannot find license file.The license file cannot be opened. FLEXlm attempted to open the file spe-cified by the vendor (/<install path>/lic/license.dat or $ICEM_ACN/lic/license.dat), or the file specified by the user in LM_LICENSE_FILE.

2 invalid license file syntax.A feature name is > MAX_FEATURE_LEN (30)A daemon name is > MAX_DAEMON_NAME (10)A server name is > MAX_SERVER_NAME (32)A feature specifies no hostid and # of licenses is <= 0.

3 cannot connect to a license server.The daemon name specified in the license file FEATURE line does not match the vendor daemon name.

4 licensed number of users already reached.The license number of users has been reached.

5 no such feature exists.The feature could not be found in the license file. A call was made to one of the software license working group usage metering functions (um_xxx_record()).

6 no TCP license service exists.This happens if a SERVER line does not specify a TCP/IP port num-ber and the TCP license service does not exist in /etc/services.

7 no socket connection to license manager server.lm_disconn() was called after the process had been disconnected from the socket. This error can also occur if an internal error happens within l_sndmsg() or l_rcvmsg().

8 encryption code in license file is inconsistent.The code in a license file line does not match the other data in the license file. This can happen when a FEATURE line has been moved from one license file to another which has different SERVER information. This may be the result of using daemons incompatible with the software being licensed.

9 invalid host.The hostid specified in the license file does not match the node on which the software is running. That is, the server does not know about the hostid specified in the license file.

10 feature has expired.The feature has expired, i.e., today’s date is after the expiration date in the license file.

11 invalid date format in license file.The start or expiration date in the license file is invalid.

12 invalid returned data from license server.The port number returned from lmgrd is invalid. The daemon did not send back a message within the timeout interval, possibly increase -t value on lmgrd command. An attempted connection to a vendor daemon did not result in a correct acknowledgment from the daemon. A message from the daemon had an invalid checksum.

13 no SERVER lines in license file.There is no SERVER line in the license file. All non-zero license count features need at least one SERVER line.

14 cannot find SERVER hostname in network database.Verify that all license files contain the same SERVER information. The gethostbyname() system call failed for the SERVER nodename in the license file. Check that /etc/hosts contains hostnames of all servers given in license file.

15 cannot connect to license server.The connect() system call failed, while attempting to connect to the daemon. The attempt to connect to the vendor daemon on all SERVER nodes was unsuccessful. Returned if the feature has been checked out but the program is in the process of reconnecting.

7-10


16 cannot read data from license server.The process cannot read data from the daemon within the timeout interval. The connection was reset by the daemon (usually because the daemon exited) before the process attempted to read data.

17 cannot write data to license server.The process could not write data to the daemon after the con-nection was established.

18 license server does not support this feature.The feature has expired (on the server node) or has not yet started, or the version is greater than the highest supported version.

19 error in select system call.Application internal error, contact ICEM support.

20 license server busy (no majority).The license server is busy establishing a quorum of server nodes so that licensing can start. This request should be retried.

21 license file does not support this version.The version requested is greater than the highest ver-sion supported in the license file FEATURE line.

22 feature checkin failure detected at license server.The checkin request did not receive a proper reply from the vendor daemon (the license might still be considered in use).

23 license server temporarily busy (new server connecting).The vendor daemon is in the process of establishing a quorum condition. New requests from clients are deferred during this period. This request should be retried.

24 users are queued for this feature.This error is similar to MAXUSERS, but supplies the additional information that there are other users in the queue for this feature.

25 license server does not support his version of this feature.The version specified in the checkout request is greater than the highest version number the daemon supports.

26 request for more licenses than this feature supports.A checkout request was made for more licenses than are supported in the license file. This request will never succeed.

27 cannot read /dev/kmem.The file /dev/kmem is not readable on this system. This error will only occur if using extended hostid checking

28 cannot read /vmunix.The file /vmunix is not readable on this system. This error will only occur if using extended hostid checking.

29 cannot find ethernet device.The ethernet device could not be located on this (VMS) system.

30 cannot read license file.

The license file could not be read (errno == EPERM or EACCES). Check user read permits on /<install path>/lic and /<install path>/lic/license.dat.

31 feature not yet available.The feature is not enabled yet (current date is before the feature start date).

32 No such attribute.The application specified an unknown attribute code.

33 Bad encryption handshake with daemon.The client performs an encryption handshake operation with the daemon prior to any licensing operations. This handshake operation failed.

34 Clock difference too large between client and server.The date on the client system does not agree closely enough with the date on the server (daemon) system. The amount of difference allowed is set by the software vendor.

35 In the queue for this feature.This checkout request has resulted in the process being placed in the queue for this feature. Subsequent calls to lm_status() will yield the status of this queued request.

36 Feature database corrupted in daemon.The daemon’s run-time feature data structures have become corrupted. This is an internal daemon error.

Error Code

Message Description

7-11


37 Duplicate selection mismatch for this feature.The checkout request for this feature has specified a duplicate mask that does not match the mask specified by an earlier checkout. This is probably the result of using different versions of your client software.

38 User/host on EXCLUDE list for feature.The user/host/display has been excluded from this feature by an end-user’s daemon option file.

39 User/host not on INCLUDE list for feature.The user/host/display has NOT been included in this feature by an end-user’s daemon option file.

40 Cannot allocate dynamic memory.The malloc() call failed to return sufficient memory. This can hap-pen while reading the features from the license file (especially if the user has an extremely long LM_LICENSE_FILE path set).

41 Feature was never checked out.Application internal error, contact ICEM support.

42 Invalid parameter.Application internal error, contact ICEM support.

43 No FLEXlm key data supplied in lm_init() call.Application internal error, contact ICEM support.

44 Invalid FLEXlm key data supplied.Application internal error, contact ICEM support.

45 FLEXlm function not available in this version.

Application internal error, contact ICEM support.

46 FLEXlm software is demonstration version.Application internal error, contact ICEM support.

47 Clock setting check not available in daemon.Application internal error, contact ICEM support.

48 FLEXlm platform not enabled.Application internal error, contact ICEM support.

49 Date too late for binary format. The expiration date format in FLEXlm licenses are good until the year 2027. This is probably a bogus date.

50 FLEXlm key data has expired.Application internal error, contact ICEM support.

51 FLEXlm not initialized.Application internal error, contact ICEM support.

52 Server did not respond to message.UDP communications failure. UDP communications are not guaranteed. Failure to recover lost or garbled message.

53 Request rejected by vendor-defined filter.The application checkout filter rejected the checkout request

54 No FEATURESET line present in license file.Application internal error, contact ICEM support.

55 Incorrect FEATURESET line in license file.Check FEATURESET line in license file.

56 Cannot compute FEATURESET line.This can happen because there’s no FEATUREs in the file.

57 socket() call failed.

This can occur when the UNIX OS runs out of system resources.

58 setsockopt() failed.The setsockopt() call has failed. This is likely due to an OS error

59 message checksum failure.Communications error – messages between client and server are encrypted and checksummed for security and integrity. The checksum will usually fail because of poor networ-king communications.

60 For Internal UseApplication internal error, contact ICEM support.

61 Cannot read license file from server.This occurs when the license file, via LM_LICENSE_FILE, is incorrectly defined. This occurs when LM_LICENSE_FILE is set to port@host.

Error Code

Message Description

7-12


62 Network software (TCP/IP) not available.This is reported on systems where this is detectable. Some systems may have this problem, but the error will not be reported as LM_NONETWORK-system calls will simply fail.

63 Not a license administrator.Various functions require that the user be a license administrator, depending on how lmgrd was started. See lmgrd(), lmremove() and lmdown().

64 lmremove request too soon.Application internal error, contact ICEM support.

65 Bad VENDORCORE struct passed to lc_init().Application internal error, contact ICEM support

66 FLEXlm include file/library mismatch.Application internal error, contact ICEM support.





71 Invalid TZ environment variable.

On some operating systems, the end-user can significantly change the date using the TZ environment variable. This error detects this type of theft.

72 ’Old-style’ vendor keys (3-word).Application internal error, contact ICEM support.

73 Local checkout filter requested request.Request was denied by an application specific restriction

74 Attempt to read beyond the end of LF path.An error occurred with the colon-separated list of license files in the LM_LICENSE_FILE environment variable.

75 SYS$SETIMR call failed.SYS$SETIMR is used on VMS to time out certain FLEXlm system calls.

76 Internal FLEXlm Error - Please report to Globetrotter Software.Application internal error, contact ICEM support.

77 Bad version number - must be floating point number, with no letters.Application internal error, contact ICEM support.

78 FLEXadmin API functions not available.Application internal error, contact ICEM support.




82 Invalid PACKAGE line in license file.PACKAGE missing or invalid COMPONENTS. A COMPO-NENT has number of users set, with OPTIONS=SUITE. A COMPONENT has number of users==0.

83 Server FLEXlm version older than client’s.The server daemons are older than the FLEXlm ver-sion used in the application. Upgrade the daemons.

84 Incorrect number of USERS/HOSTS INCLUDED in options file – see server log.The FLEXlm options file requests USERS/HOSTS inclusion exceeding the number of licenses in the file.

85 Server doesn't support this request.Application internal error, contact ICEM support.

86 This license object is already in use (Java only).Self explanatory.

87 Checkout exceeds MAX specified in options file.The FLEXlm options file being used limits the number of users for this feature. This limit has been exceeded.

88 System clock has been set back.Self explanatory.

Error Code

Message Description

7-13


The following error messages are issued by the ICEM Licensing interface to FLEXlm. Depending upon the appli-

cation, these messages may appear as 900 series errors or simply as errors 1 through 12, in which case the

FLEXlm error numbers above will be negative numbers.

89 This platform not authorized by license.This license does not permit use of this product on this hardware platform.

90 Future license file format or misspelling in the license file.Self explanatory.

91 ENCRYPTION_SEEDs are non-unique.Application internal error, contact ICEM support.

92 Server removed during reread, or server hostid mismatch with license.

Shutdown daemons and start them on the correct machines.

93 This feature is available in a different license pool.The application only supports one license pool.

94 Attempt to generate license with incompatible attributes.Application internal error, contact ICEM support.

95 Network connect to THIS_HOST failed.Application internal error, contact ICEM support.

96 Server node is down or not responding.Check status of license server.

97 The desired vendor daemon is down.Check status of vendor daemon or the vendor daemon lock file in /tmp/<daemon_name>. Remove the lock file if the vendor daemon is not running.

98 The FEATURE line can’t be converted to decimal format.Application internal error, contact ICEM support.

99 The decimal format license is typed incorrectly.Recheck license.

100 Cannot remove a lingering license.Wait for license to be freed.

101 All licenses are reserved for others.

The user is not listed in the options file.

Error Code

Message Description

901 Workstation License Customer Information data is missing.A "WL" workstation license is mis-sing the customer information. Contact ICEM support.

902 Feature License Customer Information data is missing.This license requires Customer Informa-tion included in the "Feature Description" string. Contact ICEM support.

903 Workstation and Feature License Customer Information data mismatch.The Customer Informa-tion in the “Feature Description” string does not match the information defined in the "WL" license. Contact ICEM support.

904 Permanent Feature invalid with Demo or Lease Workstation License.This permanent non-expi-ring feature can only be used with a permanent non-expiring "WL" license.

905 Workstation License is required to use this feature.A "WL" workstation license is required for this machine in order to use this license.

906 Maximum license file path length, 1024 characters, exceeded.

Shorten the license file path or combined paths in LM_LICENSE_FILE to less than 1024 characters.

Error Code

Message Description

7-14


907 Maximum DAEMON name length, 10 characters, exceeded.Application internal error, contact ICEM support.

908 Maximum FEATURE name length, 30 characters, exceeded.Application internal error, contact ICEM support.

909 Unknown Vendor DAEMON specified during initialization: ""Application internal error, contact ICEM support.

910 iautcc: Invalid action code.Application internal error, contact ICEM support.

911 Served or DEMO license required.The application will only accept a served or DEMO node-lokked license for this feature.

912 Served license required.The application will only accept a served license for this feature.

913 Cannot setup atexit processing for licensing.Application internal error, contact ICEM support.

Error Code

Message Description

7-15


7-16

ICE - Dassault Systèmesmedia.3ds.com/.../FlexLM_61_manual_Deutsch.pdfKapitel 2 Ü berblick 2-1...

Documents

Transcript of ICE - Dassault Systèmesmedia.3ds.com/.../FlexLM_61_manual_Deutsch.pdfKapitel 2 Ü berblick 2-1...