Home

FLEXlm End Users Manual

1. where 1 fpath1 is the path to the first license file 1 fpath2 is the path to the second license file etc Use a colon to separate the license file names on UNIX on Windows and Windows NT use a semicolon and on VMS use a space Each application queries each license file in the order it is listed in the LM_LICENSE_FILE path If the license server serving the license file listed in 1fpath1 is unreachable the other files listed in LM_LICENSE_FILE allow a user to obtain a license from another server 1 fpathncan also be port host using the port number and host name from the SERVER line in the license file See also e Section 5 3 2 Redundancy via License File List in LM_LICENSE_FILE e Appendix C FLEXIm Environment Variables e Section 3 1 2 Setting the Path with an Environment Variable Multiple License Files Selecting Server Nodes This chapter helps you decide which nodes to use as license server nodes 5 1 Resources Used by the Server This section discusses the resources used by the license server When you select a server node you may need to take into account the system limits on these resources For small numbers of licenses under about 100 most of these items should not be a problem on any workstation 5 1 1 Sockets When using TCP a single vendor daemon can support as many users as the per process system limit for fi
2. 0 0 0 0 eee eee 46 5 1 Resources Used by the Server 0 0 0 e eee ee eee 46 5 2 Remote Mounted Disks 00 00 c eee eee 49 5 3 JRedundant Severs cici o0 saccagonee Pangea ing Be Gate ne dad eyes 49 5 4 Counted vs Uncounted Licenses 0 0 20 eee eee 51 FLEXIm End Users Manual April 2000 iv Chapter6 The Options File 0 0 0 eee ee eee 54 6 1 Creating an Options File 0 0 0 0 54 6 2 Customizing the Options File 0 000000 0008 55 6 3 Understanding Options Files 0 0 0 0c eee eee 63 6 4 EXCLUDE Examples accuso ensani ant bb Gove oe pack aa ta 66 6 5 INCLUDE Example vcs daca cts phere PAA ea i 67 Chapter 7 License Administration Tools 0 0 00 002 e eee 68 Tel AMCKSUM eoe tena peta Qh ace Ota eae ad 69 TF2 diag aeih ea vheab aes Aare mle oenb ate E 70 Teds Wimd own sasuke ches al ole ce ane ene aac ante hae ian he 71 TA MMe ics he w als ante e agents E asia gs Bo ads eames nals wage a 72 TS AMHOSH estan insga ahh Son che node a a ra aa ra e atara ole 74 TO Minn stall se scice 5 taei be pee ee aa aaa aa hen od when ee a 75 TT iremove 2 0 eee hee ee ee Seek Ped ae oe oy 75 T8 Vimrer ad oie a Weed we ee cea has E a LY 77 TOS msta i Seek Ge eens Pap ie ee he et be ee hee Gas 78 TLO Tims witcher iiei stasen a a A aad taste tes Basan De ase ean ote 78 FAL DAVET ey ec eee ee babe Oe ee gee ee bee bee a 79
3. These steps are discussed briefly below with cross references to the appropriate locations for more detail LICENSE SERVERS AND HOSTIDS Before running any FLEX m licensed program using floating licenses you will need to set up your license server node or nodes You must select which node or nodes to run your license servers on and provide the hostid of those machines to your software vendor For pointers on selecting your server machine see Chapter 5 Selecting Server Nodes You can get the hostid of the server machine by running FLEX m s lmhostid utility on that machine If you don t have 1mhostid you can get the hostid of your machine by using the appropriate command as described in Appendix A Hostids for FLEXIm Supported Machines Using the hostid of your server machines your vendor will send you a license file that enables their application software FLEXIm End Users Manual April 2000 16 Getting Started Checklist 2 5 2 17 LMGRD AND LICENSE FILES Once you have received a license file from your vendor you must install it on your system and start up the license manager daemon 1Imgrd e Your software vendor may have selected a default location for your license file If not you can use any location you wish For more details see Chapter 3 The License File e To start Lmgrd automatically at boot time you will have to modify your system files UNIX or use Imtools Windows For detail
4. P lmdown lmremove License Administration Tools Restricts usage of 1mdown lmreread and lmremove to a FLEX m administrator who is by default root If there a UNIX group called Imadmin then use is restricted to only members of that group If root is not a member of this group then root does not have permission to use any of the above utilities The p option is available in FLEX m v2 4 and later Windows clients are unaffected by this restriction Disallow the 1mdown command no user can run 1mdown If 1mdown is disabled you will need to stop lmgrd via kill pid UNIX or stop the lmgrd and vendor daemon processes through the Task Manager or NT Service Windows On UNIX be sure the kill command does not have a 9 argument v4 lmgrd Disallow the Imremove command no user can run Imremove v4 lmgrd Run in foreground The default behavior is to run in the background Windows pre v7 lmgrd always runs in the foreground In v7 Imgrd runs in the background by default If 1 debug_log is present then no windows are used but if no 1 argument specified separate windows are used for Imgrd and each vendor daemon Prints Imgrd version number and copyright and exits Note 7 5 Imhostid Pre v6 1mgrd on Windows required app argument when not run as a service Imhostid The lmhostid utility reports the hostid of a system Usage is lmhostid n vsn flexid cpu Windows ether H
5. REPORTLOG Note that the log files should be local files on the server machine s to avoid networking dependencies SWITCHING OUTPUT OF THE DEBUG LOG FILE ON UNIX SYSTEMS On UNIX the debug log file output can be switched after the daemons are running The technique to do this involves piping the stdout of lmgrd to a shell script that appends to the file for each line Selecting Server Nodes Note Resources Used by the Server This is done as follows Instead of the normal startup lmgrd gt LOG Start lmgrd this way Imgrd sh c while read line do echo line gt gt LOG done With this startup method the output file LOG can be renamed and a new log file will be created You could even make LOG a symbolic link and change the value of the link to switch the log file This technique applies to UNIX systems only Memory The FLEX m daemons use little memory On SunOS 1lmgrd uses approximately 160 KB and the vendor daemons use approximately 180 KB each although memory usage increases in the vendor daemon with the size of the license file and the number of concurrent users Network Bandwidth FLEXI m sends relatively small amounts of data across the network Each transaction such as a checkout or checkin is typically satisfied with less than 1 KB of data transferred This means that FLEX m licensing can be effectively run over slow networks such as dial up SLIP lines for small numbe
6. In some environments the licensing information for several vendors may be combined into a single license file Most applications have an expected location for the license file documented by that application End users can usually override this location by setting the environment variable LM_LICENSE_FILE to point elsewhere or by following Introduction and Overview 2 2 4 2 3 The License Request Process instructions supplied with the licensed application If your site has software from multiple vendors with incompatible license files due to different sets of servers you can keep the data in separate files and set the LM_LICENSE_FILE variable to reference multiple files FLEX m has provided a default location for license files which is used only if no other location is provided by the application or user this is considered rare The default location is usr local flexlm licenses license dat UNIX C flexim license dat Windows Windows NT OS 2 SYSSCOMMON SYSMGR flexim dat VMS SYS SYSTEM flexim license dat Netware The default location should be used with caution setting LM_LICENSE_FILE may actually cause applications to fail if their license is located in the default location but that location is not included in LM_LICENSE_F ILE This is because setting LM_LICENSE_FILE removes the default location from the license file list It
7. This manual is written for two different audiences the license administrator and the end user FLEXIm End Users Manual April 2000 8 How to Use This Manual 1 2 1 License Administrator 1 2 2 If you are a license administrator read these chapters This chapter Welcome to FLEX m The License File Multiple License Files Selecting Server Nodes The Options File License Administration Tools Explains FLEXI m basics license and vendor daemons the license file configuring FLEXIm the license request process The license file format setting the path at start up different types of licensing policies Using license files from independent software vendors Selecting which machines will run the license servers resources required by the servers multiple servers quorums redundant servers Creating and editing the options file Managing FLEX m using GLOBEtrotter supplied utilities In addition you can refer to Appendix B Troubleshooting Guide which contains a list of common problems and their solutions and Appendix D Frequently Asked Questions End User If you are an end user read these chapters This chapter Welcome to FLEX m The License File Welcome to FLEXIm Explains FLEX m basics license and vendor daemons the license file configuring FLEX m the license request process The license file format setting the path at start up different types of licens
8. s strongly recommended that you keep a link on UNIX or copy of the license file in the vendor s expected license location so that users will not need to set LM_LICENSE_FILE to run their applications If the licenses are counted floating this license should have a USE_SERVER line directly after the SERVER line For details see Chapter 3 The License File See also Appendix C FLEXIm Environment Variables The Application Program The application program using FLEX m is linked with the program module called the FLEX m client library that provides the communication with the license server On Windows this module is called Imgrxxx d1l1 where xxx indicates the FLEX m version During execution the application program communicates with the vendor daemon to request a license The License Request Process When you run a counted FLEX m licensed application the following occurs 1 The license module in the client application finds the license file which includes the host name of the license server node and port number of the license manager daemon lmgrd 2 The client establishes a connection with the license manager daemon 1mgrqd and tells it what vendor daemon it needs to talk to FLEXIm End Users Manual April 2000 14 Configuring FLEXIm 2 4 Note 2 5 15 3 1mgrd determines which machine and port correspond to the master vendor daemon and sends that information back to the client
9. assuming everything is configured correctly since the network will resolve speedy corp com automatically 3 Finally there must be an alias for speedy so it s also known locally as speedy corp com This alias is added to the etc hosts file or if NIS Yellow Pages are being used then it will have to be added to the NIS database This requirement goes away in version 3 0 of FLEX m If all components application 1mgrd and vendor daemon are v6 0 or higher no aliases are required the only requirement is that the fully qualified domain name or IP address is used as a host name on the SERVER or as a host name in LM_LICENSE_FILE port host or host D 3 12 Does FLEX m work with NIS and DNS Yes However some sites have broken NIS or DNS which will cause FLEX m to fail In v5 of FLEX m NIS and DNS can be avoided to solve this problem In particular sometimes DNS is configured for a server that s not current available e g a dial up connection from a PC Again if DNS is configured but the server is not available FLEX m will fail FLEXIm End Users Manual April 2000 102 Windows Questions On PCs if a checkout seems to take three minutes and then fails this is usually because the system is configured for a dial up DNS server which is not currently available The solution here is to turn off DNS Finally host names must NOT have periods in the name These are not legal host names al
10. re not combining license files from different vendors the simplest thing to do is make sure you use the tools that are shipped by each vendor 1lmgrd will always correctly support older versions of vendor daemons and applications so it s always safe to use the latest version of 1mgrd and the lmut i 1 lmtools utilities If you ve combined license files from two vendors you must use the latest version of lmgrd If you ve received two versions of a product from the same vendor you must use the latest vendor daemon they send you An older vendor daemon with a newer client will cause communication errors Please ignore letters appended to FLEX m versions for example the d in v2 4d The appended letter indicates a patch and does NOT indicate any compatibility differences In particular some elements of FLEX m didn t require certain patches so a v2 4 1mgrd will work successfully with a v2 4b vendor daemon See also Section G1 Version Compatibility and Components ve received a new copy of a product from a vendor and it uses a new version of FLEX m Is my old license file still valid Yes Older FLEX m license files are always valid with newer versions of FLEXIm I ve received a new license file and the format is different from the old one I had from the same vendor Why Are they compat ible As of v3 0 FLEX m has an optional new format for license files FLEX m products always understand older versions
11. the license count field is gt 0 requires a server It s perfectly OK to have any number of separate license files with different Lmgrd server processes supporting each file Moreover since Imgrd is a lightweight process for sites without system administrators this is often the simplest and therefore recommended way to proceed With v6 Imgrd 1mdown 1lmreread you can restart stop reread a single vendor daemon of any FLEX m version This makes combining licenses more attractive than previously Also if the application is v6 using dir 1lic for license file management behaves like combining licenses without physically combining them D 1 2 When is it recommended to combine license files Many system administrators especially for larger sites prefer to combine license files to ease administration of FLEX m licenses It s purely a matter of preference D 1 3 Does FLEX m handle dates in the year 2000 and beyond Yes The FLEX m date format uses a four digit year Dates in the 20th century 19xx can be abbreviated to the last two digits of the year xx and use of this feature is quite widespread Dates in the year 2000 and beyond must specify all four year digits FLEXIm End Users Manual April 2000 98 FLEXIm Versions D 2 D 2 1 D 2 2 D 2 3 99 FLEX m Versions have products from several companies at various FLEX m ver sion levels Do I have to worry about how these versions work to gether If you
12. vendor used the wrong version of his license creation program to generate your license file or there is a bug in that process You may not modify the license file except for specific fields see Chapter 3 The License File If you need to change something in your license file you must get a new license file from your software vendor When the second user tries to check out a license the vendor daemon prints an error concerning Parameter mismatch in the debug log file and refuses the license The application may give the error Duplicate selection mismatch for this feature The most likely cause of this problem is that you are simultaneously trying to run two different versions of the application program and the software vendor has not specifically set up the new version for this kind of compatibility Check the debug log file for a comm version mismatch warning message this indicates that someone is running an older client than the license server daemon lmgrd Run only the new version of the application or only the old version FLEXIm End Users Manual April 2000 92 FLEXIm Troubleshooting List B 3 5 Other Server Problems Symptom When I run the vendor daemon on my VMS system I get the error message socket bind permission denied 13 Cause The daemon needs to bind the socket address in order to be able to listen for connections from clients This is done in the system name table so it requires the SYSN
13. 7 12 License Administration Tools Imtools for Windows 80 Appendix A Hostids for FLEX m Supported Machines 82 Appendix B Troubleshooting Guide 0 0 0 cee eee eee 86 B 1 General Debugging Hints 0 0 00008 86 B 2 FLEXLM_DIAGNOSTICS 0 0 00 0 0 e eee ee 87 B 3 FLEX m Troubleshooting List 0 000008 89 Appendix C FLEX m Environment Variables 0 0200 0005 96 C 1 How to Set Environment Variables 0 96 C 2 Environment Variables 0 0 cece eee eee 97 Appendix D Frequently Asked Questions 0 0 0 0 cece eee eee 98 D 1 License File Questions iana e EAEE eens 98 D 2 FLEXIm Versions 0 0 eee eens 99 D3 Using PLEX soot Aves ede hae bie Leth eels 100 D 4 Windows Questions 00 0 eee nee naa 103 Appendix E FPLEX m Error Codes 0 0 cece ee ene 104 E 1 Error Message Format 0 0 e cece 104 E 2 Error Code Descriptions 0 0 0 ee eee eee 105 v FLEXIm End Users Manual April 2000 Appendix F The Debug Log File 0 0 0 cece eee eee 112 F 1 Informational Messages 0 e eee eee eee 112 F 2 Configuration Problem Messages 02 00000 114 F 3 Daemon Software Error Messages 000002 ee eee 115 Appendix G FLEXIm Versions 0 c eee eee teenies 116 G 1 Version Compatibility and C
14. FLEX m v6 0 You can modify these data items in the license file e Node names on the SERVER line s e Port numbers on the SERVER line s FLEXIm End Users Manual April 2000 24 License File Format Note 3 2 1 25 e Paths on the DAEMON line s e Options file paths on the DAEMON line s e Optional port numbers on the DAEMON line s for firewall support only e USE_SERVER line FLEX m v5 only e Values in name value pairs on FEATURE lines if name is all lowercase Long lines normally use the line continuation character to break up long lines though this is not required with v7 applications FLEX m v2 did not support the line continuation character although this rarely matters since optional attributes weren t support then either Everything else is used to compute the license key and should be entered exactly as supplied by your software vendor All data in the license file is case sensitive unless otherwise indicated SERVER Lines The SERVER line specifies the node name and hostid of the license server and the port number of the license manager daemon 1mgrd Normally a license file has one SERVER line Three SERVER lines mean that you are using redundant servers The absence of a SERVER line means that every FEATURE or INCREMENT line in the license file is uncounted For more information about uncounted features see Section 3 2 4 FEATURE or INCREMENT Lines License administrators do not have th
15. Feature has expired Invalid date format in license file Invalid returned data from license server No SERVER lines in license file Cannot find SERVER host name in network database The lookup for the host name on the SERVER line in the license file failed This often happens when NIS or DNS or the hosts file is incorrect Workaround Use IP address e g 123 456 789 123 instead of host name Cannot connect to license server The server 1mgrd has not been started yet or the wrong port host or license file is being used or the port or host name in the license file has been changed Cannot read data from license server Cannot write data to license server License server does not support this feature Error in select system call Obsolete License file does not support this version Feature checkin failure detected at license server License server temporarily busy new server connecting Users are queued for this feature License server does not support this version of this feature Request for more licenses than this feature supports FLEXIm End Users Manual April 2000 106 Error Code Descriptions 27 Obsolete 28 Obsolete 29 Cannot find ethernet device 30 Cannot read license file 31 Feature start date is in the future 32 No such attribute 33 Bad encryption handshake with daemon 34 Clock difference too large between client and server 35 In the queue for this feature 36 Feat
16. IBM RS6000 systems etc rc cannot be used because TCP IP is not installed when this script is run Instead etc inittab must be used Adda line like this to etc inittab after the lines which start networking rclocal 2 wait etc rce local gt dev console 2 gt amp 1 This will not start the daemon until you reboot your license server machine WINDOWS From Imtools start Lmgrd You can optionally indicate that this should be started at system startup Setting the Path with an Environment Variable Most applications specify a location where they expect to find the license file Many will automatically install the license You should rarely if ever be required to specify where the license file is located with an environment variable However you can change the license location with LM_LICENSE_FILE or if a location is not set by the application you can set one Use the environment variable LM_LICENSE_FILE to set the location of the license file For example in the C shell setenv LM_LICENSE_FILE license_file_path The License File Note 3 2 License File Format In the Korn and Bourne shells LM_LICENSE_FILE license_file_path export LM_LICENSE_FILE On Windows 95 add the following line to C autoexec bat SET LM_LICENSE_FILE license_file_path On Windows NT use the System Control Panel to change the global environment a
17. Imreread not by lmgrd 1mgrd rereads the file it read originally Also Imreread cannot be used to change server node names or port numbers Vendor daemons will not reread their option files as a result of lmreread Imstat The lmstat utility helps you monitor the status of all network licensing activities Usage is imstat a A c license_file_path f feature i feature S vendor s host t value where a Display all information about A List all active licenses c license file_ path Use this license file f feature List users of feature i feature Print information about the named feature or all features if no feature is specified This option is usually not recommended since the information does not come from the license server and may not reflect what the server actually supports S vendor List all users of vendor s features s host Display status of clients running on host t timeout Set lmstat timeout value to timeout FLEXIm End Users Manual April 2000 78 Imswitchr 7 10 Note 7 11 79 Imswitchr The lmswitchr utility switches the report log file It will also start a new report log file if one does not already exist Usage is imswitchr c license_file_path feature new_report_log or with v5 vendor daemon imswitchr c license_file_path vendor new_report_log where c license_file_path Use this license file feature Any feature in this lice
18. a single license file If the SERVER lines in those FLEXIm End Users Manual April 2000 42 Overview of Combining License Files 43 files have identical hostids then you can combine the files into a single file If the SERVER lines have different hostids then you must keep the license files separate More precisely you can combine two license files under the following conditions 1 The number of SERVER lines in each file is the same 2 The hostid field of each SERVER line in one file exactly matches the hostid field of each SERVER line in the other file Some possible reasons license files may not be compatible are e License files are set up to run on different server nodes so hostids are different e One file is set up for single server has only one SERVER line the other is set up for redundant servers has multiple SERVER lines e One vendor uses a custom hostid algorithm so the hostids on the SERVER lines are different even though the files are for the same machine If your license files are compatible as described above then you have the option of combining license files and running a single 1mgrd as described below in Section 4 1 1 Combining License Files from Multiple Vendors If the license files are not compatible then you must keep the license files separate and run separate copies of 1mgrd for each license file as described in Section 4 1 3 Using Separate License Files on the Same Server N
19. a v5 application and v7 vendor daemon 6 1 Creating an Options File To create an options file 1 Use the appropriate options listed in Section 6 2 Customizing the Options File to create the options file using any text editor You can put the options file anywhere however we recommend that the options file for vendor XYZ whose vendor daemon is xyzd be placed in UNIX usr local flexlm options xyzd opt Windows C flexim options xyzd opt FLEXIm End Users Manual April 2000 54 Customizing the Options File 2 Add the path to the options file in the license file as the fourth field on the DAEMON line for the application s vendor daemon For example DAEMON xyzd etc xyzd usr local flexlm options xyzd opt would enable the xyzd vendor daemon to look at the specified options file In FLEX m v5 or later you can put opt ions before the path In FLEX m v6 or later adding the options path to the license file is optional Instead name the file vendor opt where vendor is the vendor daemon name and place it in the same directory as the license used by 1mgra and it will automatically be used at server startup 6 2 Customizing the Options File Below is an overview of the options file syntax See Section 6 3 Understanding Options Files for examples and additional information Each line of the file controls one option The options are EXCLUDE EXCLUDEALL GROUP HOST_
20. and Overview Getting Started Checklist GETTING INFORMATION ABOUT LICENSES To find out who is using a license run lmstat described in Chapter 7 License Administration Tools FLEXIm End Users Manual April 2000 18 Getting Started Checklist 19 Introduction and Overview The License File The license file contains all site specific information required by FLEX m This information includes e Server names and hostids e Vendor names and paths to vendor daemon executables Feature information In general the license file or a copy of it must be accessible to every machine that runs a FLEX m licensed application and each machine designated as a license server If the license file contains counted also called floating licenses before you can use the application you have to start the license manager daemon 1mgrqd using the following syntax imgrd c license_file_path 1 debug_log_path where license_file_pathis the full path to the license file and debug_log_path is the full path to the debug log file Note On VMS and Netware systems there is no lmgrd and the vendor daemon is run directly 3 1 Specifying Location of the License File Most software vendors recommend a specific location for your license file If you are running the application on multiple nodes you have these options for making your license available on all the machines e Place the license file in a partition which is availabl
21. called the vendor daemon The vendor daemon keeps track of how many licenses are checked out and who has them If the vendor daemon terminates for any reason all users lose their licenses though this does not mean the applications suddenly stop running Users normally regain their license automatically when 1lmgrd restarts the vendor daemon though they may exit if the vendor daemon remains unavailable Client programs communicate with the vendor daemon usually through TCP IP network communications The client application and the daemon processes the license server can run on separate nodes on your network across any size wide area network Also the format of the traffic between the client and the vendor daemon is machine independent allowing for heterogeneous networks This means the license server and the computer running an application can be either different hardware platforms or even different operating systems Windows and UNIX for example The License File Licensing data is stored in a text file called the license file The license file is created by the software vendor and edited and installed by the license administrator It contains information about the server nodes and vendor daemons and at least one line of data called FEATURE or INCREMENT lines for each licensed product Each FEATURE line contains a license key based on the data in that line the hostids specified in the SERVER line s and other vendor specific data
22. changed or deleted by end users This is indicated by a lowercase name asset_info dist_info m n user_info n m vendor_info m m Examples FEATURE INCREMEN Additional information provided by the license administrator for asset management A checksum useful with the 1mcksum utility which will verify that the license has been entered correctly by the end user Additional information provided by the software distributor Additional information provided by the license administrator Additional information provided by the software vendor xyz_app xyzd 2 300 31 dec 1997 20 1234567890 xyz fl xyzd 1 000 1 jan 0 5 12345678901234567890 HOS ID INTE RN ET 195 186 NOTICE Licensed to XYZ corp FEATURESET Lines The FEATURESET line is a rarely used line to prevent FEATURE lines from being added to or removed from the license file The format of the FEATURESET line is shown below where daemon key FEATURESET daemon key Name of the vendor daemon License key for this FEATURESET line This key encrypts the keys of all features this daemon supports so no FEATURE INCREMENT lines can be removed added or rearranged in this license file The License File Note 3 2 6 License File Format Example FEATURESET sampled 12345678 Nothing in a FEATURESET line can be edited Use the FEATURESET line
23. example the server host is cloud9 the port is 7654 and the license handle is 102 To remove this license issue the following command lmremove h f1 cloud9 7654 102 or Imremove f1 joe cloud9 dev ttyp5 When removing by handle if licenses are grouped as duplicates all duplicate licenses will also be removed Imreread The lmreread utility causes the license daemon to reread the license file and start any new vendor daemons that have been added In addition all running daemons will be signaled to reread the license file for changes in feature licensing information Usage is imreread c license_file_path vendor vendor all where c license_file_path Use the specified license file vendor vendor Only this one vendor daemon should reread the license file Imgrd will restart the vendor daemon if necessary Requires v6 lmreread and lmgrd the vendor daemon can be any version all If more than one 1mgrd is specified instructs all 1mgrds to reread v7 The license administrator may want to protect the execution of Imreread See the p and x options in Section 7 4 Imgrd for details about securing access to lmreread To stop and restart a single vendor daemon use Imdown vendor vendor then use lmreread vendor vendor which restarts the vendor daemon License Administration Tools Note Note 7 9 Imstat If you use the c option the license file specified will be read by
24. file the vendor daemon will automatically find and use it Vendor daemon port number Note This is for firewall support only and is otherwise not recommended This requires a v5 imgrd 3 2 3 3 2 4 Note License File Format v6 0 VENDOR sampled pre v6 0 DAEMON sampled usr local sampled usr local flexlm licenses sampled opt USE_SERVER Line v5 only USE_SERVER takes no arguments and has no impact on the server When the application sees USE_SERVER it ignores everything in the license file except preceding SERVER lines and the checkout validation occurs at the vendor daemon USE_SERVER is recommended since it improves performance when a license server is used For uncounted features USE_SERVER can be used to force logging of usage by the daemons FEATURE or INCREMENT Lines A FEATURE line describes the license to use a product An INCREMENT line can be used in place of a FEATURE line as well as to incrementally add licenses to a prior FEATURE or INCREMENT line in the license file Only the first FEATURE line for a given feature will be processed by the vendor daemon If you want to have additional copies of the same feature for example to have multiple node locked counted features then you must use multiple INCREMENT lines INCREMENT lines form license groups based on the feature name version and node lock hostid If the feature name version and node lock hostid and optionally the vendor stri
25. for UNIX and v5 0 or higher with Windows Also applications may choose not to provide this functionality FLEXLM DIAGNOSTICS is an environment variable that will cause the application to produce diagnostic information when a checkout is denied The format of the diagnostic information may change over time To set FLEXLM_DIAGNOSTICS on UNIX csh setenv FLEXLM_DIAGNOSTICS 1 sh FLEXLM _DIAGNOSTICS 1 export FLEXLM_DIAGNOSTICS On Windows 3 1 and 95 add the following line to C autoexec bat SET FLEXLM_DIAGNOSTICS 1 On NT use the System Control Panel applet to change the global environment adding FLEXLM_DIAGNOSTICS to 1 On UNIX the diagnostic output goes to stderr On Windows if the application is v5 11 or higher the output is a file in the current directory called flexpid 1log where pidis the application s process ID If the application is v5 0 the output file is called lex_err log Level 1 Content If FLEXLM_DIAGNOSTICS is set to 1 then the standard FLEX m error message will be presented plus a complete list of license files that the application tried to use For example setenv FLEXLM_DIAGNOSTICS 1 FLEX1m checkout error Cannot find license file 1 73 2 No such file or directory license file s usr myproduct licenses testing dat license dat Troubleshooting Guide FLEXLM_DIAGNOSTICS B 2 2 Level 2 Content If FLEXLM_DIAGNOSTICS is set to 2 then in addition to
26. is used with no arguments you are prompted for the name of the output license file The default name is today s date in yyyyddmm 1ic format The file should be moved to the application s default license file directory if specified by the software vendor Otherwise use LM_LICENSE_FILE or VENDOR_LICENSE_FILE to specify the directory where the Lic files are located Decimal format input is verified by checksum of each line To finish entering type q on a line by itself or enter two blank lines If in_license_fileisa dash it takes input from stdin When i is used default output is stdout otherwise if o out_license_fileis not specified lminstall prompts the user for an output file name LMINSTALL AS A CONVERSION TOOL lminstall can alternatively be used to convert licenses between decimal and readable format and between different versions of FLEX m license formats To convert from readable to decimal o lminstall i in_license_file o out_license_fil odecimal To convert to FLEX m v2 format lminstall i in_license_file o out_license_file verfmt 2 Conversion errors are reported as necessary lminstall has a limit of 1000 lines of input Imremove The lmremove utility allows you to remove a single user s license for a specified feature This is only needed when a client node crashes since that s the only condition where a license is not automatically freed
27. level 1 output the checkout arguments are presented For example setenv FLEXLM_DIAGNOSTICS 2 FLEX1m checkout error No such feature exists 5 116 2 No such file or directory license file s usr myproduct licenses testing dat license dat Im checkout f1 1 0 1 0x0 Ox4000 Note that the error message actually contains two separate problems which both occurred during the checkout e There s no such feature in the license it did find e It was unable to find the other license file which is what produces the message No such file or directory Following is a description of the arguments to Im_checkout im_checkout feature version lic queue_flag dupgroup_mask where feature The requested feature version The requested version The license file must contain a version gt the requested version lic Number of licenses requested Usually 1 queue_flag If 0 no queueing If 1 queue for license blocking queue If 2 queue for licenses but return to application non blocking queue dupgroup_mask Indicates duplicate grouping also called license sharing User host and display are as shown by imstat a FLEXIm End Users Manual April 2000 88 FLEXIm Troubleshooting List B 2 3 Level 3 Content FLEX m v6 only If FLEXLM_DIAGNOSTICS is set to 3 then in addition to level 1 and 2 output if a checkout is successful information is printed explaining how the license was grant
28. trying to run the license server on a different machine from the machine the file was made for 2 the hostid of the machine you are running on changed for example the dongle hostid was moved Windows or the CPU board was replaced 3 the hostid in the license file was modified Verify that the hostid of the machine on which the vendor daemon or node locked client program is being run matches the hostid specified in the license file on the SERVER line for the vendor or on the FEATURE line for a node locked client You can run the lmhostid program to see what FLEX m thinks the hostid is You may not modify the hostid in the license file If the hostid of your server machine changes you will have to get a new license file from your software vendor FLEXIm End Users Manual April 2000 90 FLEXIm Troubleshooting List B 3 3 Connection Problems 91 Symptom Cause Solution The application program or lmstat can t connect to the server to check out a license The FLEX m routines in the application are unable to make a TCP connection to the server and port specified in the license file Possible reasons for this are 1 the wrong license file is being referenced by the application program 2 the server machine specified in the license file is down 3 the vendor daemon specified in the license file is not running 4 the host name in the license file is not recognized by the system 5 the network between the clien
29. yyyy ISSUBR NOTICES a pe OVERDRAFT n PLATFORMS SN serial_num START dd mmm yyyy SUPERSEDE WEEE Le et USER_BASED n VENDOR_STRING n n License File Format Host names must be specified in INCLUDE statements in the end user options file and the number of hosts is limited to lic or the number specified in n Date issued Issuer of the license A field for intellectual property notices FLEXI m v4 0 and later The overdraft policy allows your vendor to specify a number of additional licenses which users will be allowed to use in addition to the licenses they have purchased This allows your users to not be denied service when in a temporary overdraft state Usage above the license limit will be reported by the SAMreport reporting tool Usage is limited to the listed platforms v5 11 only Serial number used to identify INCREMENT lines Start date FLEX m v6 or later only If this appears all licenses issued before the date specified in ISSUED are superseded by this line and become ineffective Users must be specified in INCLUDE statements in the end user options file and the number of users are limited to lic or the number specified in n Same as vendor_str above but in name value pair syntax FLEXIm End Users Manual April 2000 32 License File Format 3 2 5 33 The following attributes can be
30. 1 JUNE 1998 e Performance improvements 119 FLEXIm Versions How to Tell the License File Version v7 0 AuGusT 1999 License Certificate Manager support for automatic license fulfillment Support for try before you buy licensing License file handles inserted newlines from emailers License lines automatically optimally sorted Improved Imtools interface for Windows 1imgrd when run at command line on Windows runs in background by default Improved three server redundancy reliability v7 vendor daemon and Imgrd lmreread and 1mdown take a11 argument to shut down or reread all imgrds Support registry Windows and HOME flexlmrc for FLEX m environment variables Automatically install license path in registry or HOME flexlmrc after successful checkout Options support for LM_PROJECT with PROJECT Performance improvements especially for Windows NT Intel Pentium III CPU ID v7 0d November 1999 FLEXIm End Users Manual April 2000 120 How to Tell the License File Version 121 FLEXIm Versions Index A asset_info 33 ATM 102 C ck 33 configuring FLEXIm number of server nodes 49 D DAEMON line 26 Debug Log File 112 debug log file description of content 112 rotating to save space 47 Decimal format licenses lminstall 75 DISPLAY End user options file 57 dist_info 33 DNS 102 domains 102 DUP_GROUP 31 E Error Code Descriptions 105 EXCLUDE 57 Example 66 EXCLUDEALL 57 F FEATU
31. 4 The client establishes a connection with the specified vendor daemon and sends its request for a license 5 The vendor daemon checks in its memory to see if any licenses are available and sends a grant or denial back to the client 6 The license module in the application grants or denies use of the feature as appropriate Uncounted features where the license count is 0 do not require a server and the FLEX m client library routines in the application grant or deny usage based solely upon the license contents Configuring FLEX m Most of the parameters of FLEX m are configurable by the license administrator The license administrator can set the e Location of the license file though it s recommended that a copy or link of the license remains at the location where the application expects it e Location of all executables e Location of all log files e TCP IP port number used by the license manager process lmgrd In addition the license administrator can reserve licenses for specific users nodes or groups and control other license related options Changing parameters is discussed in Chapter 6 The Options File Refer to your vendor s documentation before attempting to change file names locations or contents Getting Started Checklist The following sections provide a quick overview of how to set up and use licensing for FLEX m licensed products By scanning the list you should be able to quickly find the areas o
32. AM privilege Solution Run the daemon in a process with the SYSNAM privilege set 93 Troubleshooting Guide Symptom Cause Solution FLEXIm Troubleshooting List When I start up Ilmgrd it says execl failedon my vendor daemon imgrd uses exec to start each vendor daemon running If there is a problem starting the vendor daemon this message is output to the log file This error is typically caused by one of the following 1 there is no executable at the location referred to by the license file and printed out in the log file 2 the executable does not have the proper permissions to be run the file does not have the x bit set or one of the directories in the path is not readable 3 there was an error building the executable and it can not be run 4 the executable is for a different machine architecture Verify that the path to the vendor daemon is absolute i e starts with a slash character and that it points to the executable program itself not the containing directory for FLEX m v1 5 Ensure that the file exists by doing an ls 1 of the vendor daemon file name s specified in the log file Make sure you do this as the same user that started lmgrd Verify that the file is executable Note that if you are running as root and using an NFS mounted file system the relevant protection bits are the other bits not the user bits even if the file is owned by root Do a whatis on the file if your sy
33. EATURE or INCREMENT lines may have different license keys if the start dates are different FLEXIm End Users Manual April 2000 30 License File Format 31 The following fields are all optional except for vendor str in the v2 format For optional fields of the name value syntax if the name is lowercase it can be modified and the license will remain valid vendor_str feat_hostid DUP_GROUP HOSTID feat_hostid The License File Vendor defined string enclosed in double quotes This string can contain any characters except a quote String returned by lmhostid Used only if the feature is to be bound to a particular host whether its use is counted or not Numeric hostids are case insensitive See Appendix A Hostids for FLEXIm Supported Machines for more information Duplicate grouping parameter can be specified in the license in FLEX m v4 0 and later The syntax is DUP_GROUP NONE SITE UHDV U DUP USER H DUP_HOST D DUP_DISPLAY V DUP_VENDOR_DEF Any combination of UHDV is allowed and the DUP_MASK is the OR of the combination For example DUP_GROUP UHD means the duplicate grouping is DUP_USERIDUP_HOSTIDUP_DISPLAY so for a user on the same host and display additional uses of a feature do not consume additional licenses Same as feat_hostid above but in the name value pair syntax FLEXIm v3 0 and later HOST_BASED n ISSUED dd mmm
34. FLEX m End Users Manual Version 7 0 GLOBEtrotter Software Inc San Jose CA 95125 Voice 408 445 8100 Fax 408 445 7760 Email info globes com Web http www globetrotter com April 2000 COPYRIGHT 1995 2000 GLOBEtrotter Software Inc All Rights Reserved GLOBEtrotter Software products contain certain confidential information of GLOBEtrotter Software Inc Use of this copyright notice is precautionary and does not imply publication or disclosure No part of this publication may be reproduced transmitted transcribed stored in a retrieval system or translated into any language in any form by any means without the written permission of GLOBEtrotter Software Inc TRADEMARK GLOBErtrotter and FLEX m are registered trademarks of GLOBEtrotter Software Inc Electronic Commerce for Software Electronic Licensing GLOBEtrotter Software Globetrotter Software GTwebLicensing No Excuses Licensing Policy in the License SAMreport SAMsolutions SAMsuite SAMwrap and the tilted compass image are all trademarks of GLOBEtrotter Software Inc All other brand and product names mentioned herein are the trademarks and registered trademarks of their respective owners RESTRICTED RIGHTS LEGEND Use duplication or disclosure by the government is subject to restrictions as set forth in subparagraph c 1 ii of the Rights of Technical Data and Computer Software clause of DFA
35. GROUP INCLUDE INCLUDEALL LINGER AX AX_OVERDRAFT NOLOG 55 The Options File Deny a user access to a feature Deny a user access to all features served by this vendor daemon Define a group of users for use with any options Define a group of hosts for use with any options Allow a user to use a feature Allow a user to use all features served by this vendor daemon Cause licenses to be held by the vendor daemon for a period after the application checks them in or exits Limit usage for a particular feature group prioritizes usage among users Limit overdraft usage to less than the amount specified in the license Turn off logging of certain items in the debug log file Customizing the Options File REPORTLOG Specify that a report log file suitable for use by the SAMreport license usage reporting tool be written RESERVE Reserve licenses for a user IMEOU Specify idle timeout for a feature returning it to the free pool for use by another user IMEOUTALL Set timeout on all features You can include comments in your options file by starting each comment line with a pound sign Everything in an options file is case sensitive Be sure that user names and feature names for example are entered correctly FEATURE SPECIFICATION Starting with FLEX m v5 you can select a particular line of a given feature name as follows feature name val
36. If the application is active it will re checkout the license after it is freed by Imremove License Administration Tools Imremove Usage is Imremove c license_file_path feature user host display or Imremove c license_file_path h feature host port handle where c license_file_path License file feature Name of the feature checked out by the user user Name of the user whose license you are removing as reported by lmstat a host Name of the host the user is logged into as reported by lmstat a display Name of the display where the user is working as reported by lmstat a port Port number as reported by lmstat a handle Handle as reported by Imstat a The uses host display port and handle information must be obtained from the output of lmstat a imremove removes all instances of user on host and display from usage of feature If the optional c license_file_pathis specified the indicated file is used as the license file You should protect the execution of 1imremove because removing a user s license can be disruptive See the p or the x options in Section 7 4 Imgrd for details about securing access to lmremove The h variation uses the server host port and license handle as reported by lmstat a Consider this example Imstat a output joe cloud7 dev ttyp5 v1 000 cloud9 7654 102 start Fri 10 29 18 40 FLEXIm End Users Manual April 2000 76 Imreread 7 8 77 In this
37. LEXIm End Users Manual April 2000 116 How to Tell the License File Version G2 117 How to Tell the License File Version The following rules apply to individual FEATURE INCREMENT or UPGRADE lines It s possible to have a mix of versions in a single file Only the features that a particular application checks out determine the version of the license for that feature Version 2 Blank quotes or a quoted string at the end of the FEATURE line gt Version 3 INCREMENT or UPGRADE line gt Version 4 OVERDRAFT DUP_GROUP INTERNET or PACKAGE appear gt Version 5 SUPERCEDE ISSUED USER_BASED HOST_BASED or SN appear gt Version 6 START appears v1 0 1988 First FLEX m Release containing all the basic FLEX m features V1 5 FEBRUARY 1990 First widely used version including DEMO v2 1 MARCH 1991 e Improved TIMEOUT support e Improved ethernet hostid support v2 21 NOVEMBER 1991 e Added support for many platforms and some platform specific improvements such as hostid e Hostid ANY added v2 26 MARCH 1992 USED ONLY BY SUN e Added license lingering v2 4 DECEMBER 1992 e Added use all feature lines capability for incremental license distribution Enhanced vendor customization routines FLEXIm Versions How to Tell the License File Version e Enhanced end user options file e Added new hostid types USER HOSTNAME and DISPLAY e Added port host to locate license file downloads license
38. Network connect to this_host failed The license file indicates this_host and the server is not running on this host If it s running on a different host this_host should be changed to the correct host Server node is down or not responding See the system administrator about starting the server or make sure that you re referring to the right host see LM_LICENSE_FILE The desired vendor daemon is down 1 Check the 1mgra log file or 2 Try Lmreread This FEATURE line can t be converted to decimal format The decimal format license is typed incorrectly Cannot remove a linger license All licenses are reserved for others The system administrator has reserved all the licenses for others Reservations are made in the options file The server must be restarted for options file changes to take effect Unused Unused Unused Unused License server out of network connections The vendor daemon can t handle any more users See the debug log for further information FLEXIm End Users Manual April 2000 110 Error Code Descriptions 107 Unused 108 Unused 109 Unused 110 Dongle not attached or can t read dongle Either the hardware dongle is unattached or the necessary software driver for this dongle type is not installed 111 Imgr res Windows Resource file not linked 112 Missing dongle driver In order to read the dongle hostid the correct driver must be installed The
39. Note 7 4 Imgrd You may want to protect the execution of 1mdown since shutting down the servers causes users to lose their licenses See the p or the x options in Section 7 4 Imgrd for details about securing access to 1mdown If 1mdown encounters more than one server for example if c specifies a directory with many lic files a choice of servers to shut down is presented To stop and restart a single vendor daemon use 1mdown vendor vendor then use lmreread vendor vendor to restart the vendor daemon When shutting down redundant servers there is a one minute delay before the servers shut down Do not use kill 9 to shut down the license servers See also Section 7 8 lmreread Imgrd lmgrd is the main daemon program for FLEX m When you invoke 1mgra it looks for a license file which contains information about vendors and features On UNIX systems it is strongly recommended that 1mgrd be run as a non privileged user not root Usage is imgrd c license_file_path 1 debug_log s timestamp_interval 2 p x lmdown x lmremove z v where c license_file_path Use the license file named 1 debug_log Write debugging information to file debug_log This option uses the letter 1 not the numeral 1 s timestamp_interval Specifies the debug log file timestamp interval in minutes The default is 360 minutes FLEXIm End Users Manual April 2000 72 Imgrd 73 FX TX
40. Or RE FILE LM_PROJECT 97 Use FLEXI m version introduced Windows only prevents interactive pop ups from appearing Set to 1 if a batch application Version 7 clients Used for debugging where applications don t print FLEX m error message text Set to 1 2 or 3 depending on the amount of diagnostic information desired Version 5 clients Reset path to license file Can be a license file list separated by on UNIX and on Windows If VENDOR_LICENSE_FILE used VENDOR is the vendor daemon name used by this application For example GLOBEtrotter Software products use GSI_LICENSE_FILE Can be a file name or port host See also Section 3 1 2 Setting the Path with an Environment Variable VENDOR_LICENSE_FILE requires v6 clients LM_PROJECT s value is logged in the report log file and later reported on by SAMreport Limited to 30 characters Version 5 client required This can also be used to RESERVE INCLUDE licenses with PROJECT For example RESERVE 1 f1 PROJECT airplane v5 clients and v7 vendor daemon are required for this feature FLEXIm Environment Variables Frequently Asked Questions D 1 License File Questions D 1 1 I ve received FLEX m license files from two different companies Do I have to combine them You don t have to combine license files Each license file that has any counted lines
41. P On Windows and HP optional hostids are available The output of this command looks as follows lmhostid Copyright c 1989 1997 Globetrotter Software Inc The FLEX1m hostid of this machine is 69021c89 n No header is printed only the hostid is printed vsn Volume Serial Number of the Windows c drive flexid GLOBEtrotter dongle based hostid Windows cpu 32 64 96 Pentium III hostid for Windows Requires FLEXI m v7 0d The cpuid is turned off by default so it must be enabled which is normally performed in the BIOS Setup usually pressing the DEL key during system boot The full ID is 96 bit and this is what must be used for a truly unique ID but the 32 bit duplicate hostids using the 32 bit are expected to be rare if they occur at all Where available this the recommended hostid type ether Ethernet hostid on HP On HP the default hostid is the true system hostid and is recommended but partly for historic reasons the ethernet address is also available as a hostid See also Appendix A Hostids for FLEXIm Supported Machines FLEXIm End Users Manual April 2000 74 Iminstall 7 6 7 7 75 Iminstall Introduced in v6 0 Iminstal1 is designed primarily for typing in decimal format licenses to generate a readable format license file Usage is lminstall i in_license_file o out_license_file overfmt 2 3 4 5 5 1 6 odecimal Normally 1minstall1
42. RE in depth 28 listing users of 78 overview 13 firewalls 100 FLEXLM_DIAGNOSTICS 87 H HOST End user options file 57 HOST_BASED 32 hostid determining without Imhostid 82 HOSTID 31 I INCLUDE 59 Example 67 INCLUDEALL 59 INCREMENT in depth 28 Installing 16 INTERNET End user options file 57 internet and FLEXIm 100 ISDN 102 ISSUED 32 ISSUER 32 L license file compatibility between different versions 43 DAEMON line 26 default location 13 FEATURE line 28 frequently asked questions 98 how to combine 42 INCREMENT line 28 list for redundancy and multiple vendors 45 node locking 37 overview 13 FLEXIm End Users Manual April 2000 122 PACKAGE line 34 rereading after an update 77 SERVER lines 26 43 USE_SERVER 28 with multiple servers 20 21 license file list 44 45 license request process overview of 14 license server how to choose 46 LINGER 60 LM_LICENSE_FILE License file list 45 syntax 23 used to reference multiple files 14 LM_PROJECT 61 97 Imcksum 69 Imdiag 70 91 debugging connectivity problems 91 troubleshooting Imdiag 70 troubleshooting with 86 Imdown 71 Imgrd 20 and redundant servers 21 combining license files 98 compatability between versions 44 debug log file 48 112 end user options file 63 hostnames 102 license file list support 42 Imdown 71 multiple license files 42 multiple or single Imgrd processes 43 overview 20 PORT 27 root perms on Unix 101 running as root 101 shutting dow
43. RS 252 227 0713 and FAR52 227 19 and or applicable Federal Acquisition Regulation protecting the commercial ownership rights of independently developed commercial software Printed in the USA April 2000 Contents Chapter 1 Welcome to FLEXIm 0 0 cee eee 8 1 1 Versions of FLEXIm vandie e ee ENa eE EA E E ENA E 8 1 2 How to Use This Manual 0 0 eee eee eee 8 1 3 Related Documents from GLOBEtrotter Software 10 Chapter 2 Introduction and Overview 0 0 0c eee eee eee ee 12 2 1 Introduction to FLEXIm 1 0 0 0 00 eens 12 2 2 FLEX m Components 00 0 12 2 3 The License Request Process 0 00 eee e ee eee ee 14 2 4 Configuring FLEXIm 1 0 0 cee eee 15 2 5 Getting Started Checklist 0 0 0 0 eee eee eee 15 Chapter3 The License Fil mr coi cp ceo eden bee ee ee ete hee 20 3 1 Specifying Location of the License File 20 3 2 License File Format 0 0 cece cece eee eee AN 24 3 3 Sample License File seen cnc as eae sede e eae gaye ea hayes 36 34 Types of License Piles occ gnc anA e ee a beret 37 3 5 Decimal Format o eia tee ek ae 38 3 6 License File Order 0 0 0 0 cece eens 39 Chapter4 Multiple License Files 0 0 eee eee eee 42 4 1 Overview of Combining License Files 0 42 4 2 Using LM_LICENSE_FILE License File List 45 Chapter5 Selecting Server Nodes
44. Section 6 2 3 GROUP and Section 6 2 4 HOST_GROUP type_name Name of the user or group to include To include user bob in the list of users able to use feature f1 INCLUDE 1 USER bob INCLUDE is required for USER_BASED or HOST_BASED features The system administrator specifies which users are allowed to use the product via INCLUDE and the license limits the number of users that can be INCLUDEd INCLUDEALL INCLUDEALL type type_name Includes a user host display or group in the list of who is allowed to use all features served by this vendor daemon Anyone not in an INCLUDEALL statement will not be allowed to use these features type One of USER HOST DISPLAY PROJECT GROUP HOST_GROUP or INTERNET see Section 6 2 3 GROUP and Section 6 2 4 HOST_GROUP type_name Name of the user or group to include The Options File 6 2 7 6 2 8 Customizing the Options File To allow the user jane to use all features served by this vendor daemon INCLUDEALL USER jane LINGER LINGER feature seconds Rarely used This causes the daemon to hold on to the license for feature for seconds after the application checks the license in or exits This could be useful for short duration programs which will be used many times in a row by the same user to ensure that the user will be able to re acquire the license repeatedly On the other hand other us
45. Windows Hardware Hostid Type this command on Example Platform the license server Windows ethernet lmutil lmhostid 0800200055327 address Disk serial DIR C look for DISK_SERIAL_NUM number Volume Serial Number 3e2e17fd is and remove Dongle lmhostid flexid FLEXID 7 b28520b9 parallel port hardware key Pentium Imhostid cpu 9077 5D77 0002 57C8 II CPU Imhostid cpu96 95D2 1D3D 96 bit V7 0d The 32 bit version is only Use the last nine characters BIOS Setup from the full id 95D2 1D3D 32 bit to enable FLEXIm End Users Manual April 2000 84 License Administration Tools Imtools for Windows 85 Hostids for FLEXIim Supported Machines Troubleshooting Guide This appendix documents areas of FLEX m that have given customers difficulty in the past We hope it helps you debug any problems you might experience at your site B 1 General Debugging Hints The following are tips for debugging When you start the license server 1mgrqd be sure that you direct the output into a log file where you can examine it The log file often contains useful information You should examine it when you have a problem and be prepared to answer questions about it when you talk to a support person If the license server appears to have started correctly which you should be able to determine from the log file try running Imstat a and 1lmdiag to see if that program has the same proble
46. Wrong hostid exiting The hostid is wrong for host BAD CODE for feature The specified feature name has a bad license key It was probably typed in wrong or modified by the end user CANNOT OPEN options file file The options file specified in the license file could not be opened License daemon 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 No features to serve A vendor daemon found no features to serve This could be caused by a corrupted or incorrectly entered license file UNSUPPORTED FEATURE request feature by user The 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 FLEXIm End Users Manual April 2000 114 Daemon Software Error Messages F 3 115 Unknown host host The host name specified on a SERVER line in the license file does not exist in the network database NO DAEMON lines exiting The license daemon logs this message if there are no DAEMON lines in the license f
47. XI m applications send periodic heartbeats to the server to discover if it has died What happens when the server dies is then up to the application Some will simply continue periodically attempting to re checkout the license when the server comes back up Some will attempt to re checkout a license a few times and then presumably with some warning exit Some GUI applications will present pop ups to the user periodically letting them know the server is down and needs to be restarted How do you tell if a port is already in use 99 44 of the time if it s in use it s because 1mgrd is already running on the port or was recently killed and the port isn t freed yet Assuming this is not the case then use telnet host port if it says Can t connect it s a free port FLEXIm End Users Manual April 2000 100 Using FLEXIm D 3 6 D 3 7 D 3 8 D 3 9 101 Does FLEX m require root permissions No There is no part of FLEX m 1mgrd vendor daemon or application that requires root permissions In fact it is strongly recommended that you do not run the license server 1mgrd as root since root processes can introduce security risks If Lmgrd must be started from the root user for example in a system boot script we recommend that you use the su command to run lmgrd as a non privileged user su username c Imgrd_path c license_file_path 1 debug_log_path where username is a non privileged user a
48. _hostid VENDOR_STRING vendor_str vendor_info dist_info user_info asset_info ISSUER NOTICE ck nnn OVERDRAFT nnn DUP_GROUP NONE SITE UHDV Nothing ina FEATURE INCREMENT line is editable except for values in the pairs where name is all lowercase where feature Name given to the feature by the vendor daemon Name of the vendor daemon also found in the DAEMON line The specified daemon serves this feature feat_version Version of this feature that is supported by this license The License File exp_date lic key License File Format Expiration date of license e g 7 may 1996 Note If the year is 0 or 00 000 0000 then the license never expires Dates before 2000 can be two or four digit years After 2000 they must be four digit years The expiration date is fully year 2000 compliant FLEX m v6 or later applications only the keyword permanent can be used instead of the date 1 jan 0 Number of concurrent licenses for this feature If the number of licenses is set to 0 the licenses for this feature are uncounted and no lmgrd is required but a hostid on the FEATURE line is required See Section 5 4 Counted vs Uncounted Licenses FLEX m v6 or later applications only the keyword uncounted can be used instead of a license count of 0 License key for this FEATURE line Two identical looking F
49. age Format FLEXI m error messages presented by applications have the following components FLEX m Error Number a negative number starting at 1 FLEX m Error Text short sentence lt 80 characters summarizing problem FLEX m Error Explanation optional short paragraph 3 5 lines explaining problem and possible solutions or workarounds FLEX m Minor Error Number a positive number starting at 1 These numbers are unique error identifiers and are used by FLEX m ISVs for more advanced support assistance Their meaning is not documented System Error Number optional a UNIX or Windows OS error code last set by the operating system System Error Explanation optional a short sentence lt 80 characters explaining the system error Other supporting information optional Error messages were improved in v6 FLEX m Error Explanation and supporting information are only available in applications using v6 0 These error messages may occur in two formats available with FLEX m or may appear in a format customized by the application E 1 1 Format 1 short FLEX1m error text lm_errno minor_num sys_errno sys_error_text The system error information may be missing Example Can t connect to license server 15 12 61 Connection refused FLEXIm End Users Manual April 2000 104 Error Code Descriptions E 1 2 Format 2 long version 6 E 2 105 FLEX1m error text FLEX1m error explanation Opti
50. al if OPTIONS SUITE is not set in this case the resulting number of licenses will be lic on the COMPONENTS line multiplied by the number of licenses in the FEATURE INCREMENT line Examples COMPONENTS compl comp2 comp3 comp4 COMPONENTS comp1 1 5 comp2 comp3 2 0 4 This is what distinguishes a package suite from a package used to ease distribution With OPTIONS SUITE the corresponding feature of the same name as the package is checked out in addition to the component feature being checked out If OPTIONS SUITE is not set then the corresponding feature of the same name as the package is removed once the package is enabled is not checked out when a component feature is checked out PACKAGE suite xyzd 1 0 3B24B2F508CB697641CC COMPONENTS compl1 comp2 OPTIONS SUITE FEATURE suite xyzd 1 0 1 jan 0 5 4193E6ABCCCB1A3970B3 This is a typical OPT IONS SUITE example There are two features comp1 and comp2 which are each version 1 0 each with five non expiring licenses available When comp1 or comp is checked out suite will also be checked out PACKAGE suite xyzd 1 0 2CBF44FCB9C1E825DC5C COMPONENTS c1 1 5 2 c2 3 0 4 FEATURE suite xyzd 1 0 1 jan 1999 3 321E78A17EC19AE81A43 SN 123 The License File 3 2 7 3 3 Sample License File In this example the component version overrides the feature version an
51. allowed to use the feature e The EXCLUDE list is checked before the INCLUDE list someone who is on both lists will not be allowed to use the feature Once you create an INCLUDE or EXCLUDE list everyone else is implicitly outside the group This feature allows you as an administrator the ability to control licenses without having to explicitly list each user that you wish to allow or deny access to In other words there are two approaches you can either e Give most users access and list only the exceptions or e Severely limit access and list only the those users that have access privileges Simple Options File Example RESERVE 1 compile USER robert RESERVE 3 compile HOST mainline EXCLUDE compile USER lori OLOG QUEUED This options file would e Reserve one license for the feature compile for the user robert e Reserve three licenses for the feature compile for anyone on a computer with the host name mainline e Prevent the user lori from using the compile feature on any node on the network e Cause QUEUED messages to be omitted from the debug log file FLEXIm End Users Manual April 2000 64 Understanding Options Files 6 3 4 65 The sum total of the licenses reserved must be less than or equal to the number of licenses specified in the FEATURE line In the example above there must be a minimum of four licenses on the compil
52. ally used in hexadecimal format On some systems including HP and SGI the system command returns the number in decimal format Since v3 0 of FLEX m a before the hostid indicates to FLEX m that this is a decimal number For example if the HP uname i command returns 2005771344 FLEX m will accept 2005771344 Or it can be converted to hexadecimal On UNIX systems you can convert to hex with the following script echo 2005771344 160 p dc 778DA450 FLEXIm End Users Manual April 2000 82 License Administration Tools Imtools for Windows Hardware Hostid Type this command on Example Platform the license server AIX 32 bit uname m returns 02765131 RS 6000 hostid 000276513100 then PPC remove last two digits and use remaining last eight digits DEC Alpha ethernet netstat i 080020005532 address HP 32 bit uname i and convert 778DA450 or hostid to hex or prepend with 2005771344 ethernet lanscan station 0000F0050185 address address without leading 0x Linux ethernet sbin ifconfig 00400516E525 address eth0 and remove colons from HWaddr 00 40 05 16 E5 25 SCO Hostid uname x Serial is ID_STRING SCO00354 String SCO00354 then prefix with ID_STRING SGI 32 bit etc sysinfo s 69064C3C or hostid convert to hex or prefix 1762020412 SH SUN 32 bit hostid 170a3472 hostid 83 Hostids for FLEXIm Supported Machines License Administration Tools Imtools for
53. boot log bin su daniel c home flexlm v5 12 hp700_u9 1lmdiag n c home flexilm v5 12 hp700_u9 license dat gt gt home flexlm v5 12 hp700_u9 boot log bin su daniel c echo exiting gt gt home flexlm v5 12 hp700_u9 boot log Please note the following about how this script was written e All paths are specified in full since no paths can be assumed at boot time e Since no paths are assumed the vendor daemon must be in the same DAEMON lines must be edited to include the full path to the vendor daemon e The su command is used to run Imgrd as a non root user daniel We recommend that 1mgrd not be run as root since it can be a security risk to run any program as root that does not require root permissions and 1lmgrd does not require root permissions FLEXIm End Users Manual April 2000 22 Specifying Location of the License File Note Note 3 1 2 23 e Daniel has a csh login so all commands executed as daniel must be in csh syntax All commands not executed as daniel must be in bin sh syntax since that is what is used by the boot scripts e The use of nohup and sleep are required on some operating systems notably HP UX and Digital UNIX for obscure technical reasons These are not needed on Solaris and some other operating systems but are safe to use on all e l1mdiag is used as a diagnostic tool to verify that the server is running and serving licenses On
54. d a license file from vendor XYZ with incompatible servers You can place the license file from vendor ABC into usr flexlm abc lic and the license file from vendor XYZ into usr flexlm xyz lic FLEXIm End Users Manual April 2000 44 Using LM_LICENSE_FILE License File List 4 2 Note 45 then set the LM_LICENSE_FILE environment variable to point to both of them 66499 Each name in LM_LICENSE_FILE should be separated by a colon on UNIX systems a semicolon on Windows and Windows NT systems in FLEXI m v4 1 a comma was used on Windows and NT and a space on VMS systems In the C shell setenv LM_LICENSE_FILE usr flexlm abc lic usr flexlm xyz lic In the Korn and Bourne shells LM_LICENSE_FILE usr flexlm abc lic usr flexlm xyz lic export LM_LICENSE_FILE Using LM_LICENSE FILE License File List If products use different license server nodes each set of license servers requires separate license files When multiple software vendors use the same set of license server nodes the technique described above in Section 4 1 Overview of Combining License Files can be used to combine license files The resulting multiple license files can be installed in convenient locations On UNIX you would set the LM_LICENSE_FILE environment variable as follows setenv LM_LICENSE_FILE lfpathil lfpath2
55. d the number of licenses available for any component is the product of the three licenses for suite and the number of licenses for that component The result is equivalent to FEATURE cl xyzd 1 5 1 jan 1999 6 OD3AD5F26BC868D476EC SN 123 FEATURE c2 xyzd 3 0 1 jan 1999 12 EBL6C5AE4A4E0F2961F0 SN 123 With FLEX m v6 or later applications only the PACKAGE lines can be stored in a separate file which need never be edited UPGRADE Lines UPGRADE feature daemon from_feat_version to_feat_version exp_date lic key vendor_str feat_hostid ck nnn All the data is the same as for a FEATURE or INCREMENT line with the addition of the from_feat_version field An UPGRADE line removes up to the number of licenses specified from any old version gt from_feat_version and creates a new version with that same number of licenses For example the two lines INCREMENT f1 xyzd 1 000 1 jan 1999 5 9BFACO3164EDB7BC0462 UPGRADE f1 xyzd 1 000 2 000 1 jan 1999 2 1B9A30316207EC8CCOF7 would result in three licenses of v1 0 of f1 and two licenses of v2 0 of f1 An UPGRADE line will operate on the closest preceding FEATURE or INCREMENT line with a version number that is gt from_feat_version and lt to_feat_version Note that UPGRADE lines do not work for node locked uncounted licenses before v6 Sample License File This is an example of a license file fo
56. dding LM_LICENSE_FILE to license_file_path where license_file_pathis the full path to the license file This can also be a port host setting where port and host are the port number and host name from the SERVER line in the license file v6 applications can use simply Ghost if the server uses a default port number In FLEX m v6 applications will accept an environment variable or Windows Registry named VENDOR_LICENSE_FILE where VENDOR is the vendor daemon name e g GSI_LICENSE_FILE With Imgrd and lmutil 1mstat lmdown etc the c option overrides the setting of the LM_LICENSE_FILE environment variable See Section 4 1 3 Using Separate License Files on the Same Server Node for more information about LM_LICENSE_FILE Some applications do not recognize the LM_LICENSE_FILE environment variable See also Appendix C FLEXIm Environment Variables License File Format License files usually begin with a SERVER line or three lines for redundant servers followed by one or more DAEMON lines followed by one or more FEATURE or INCREMENT lines In some cases the license file requires no SERVER line and no DAEMON line See Section 5 4 Counted vs Uncounted Licenses for more information Since FLEX m v6 0 the DAEMON line can be called VENDOR Wherever DAEMON appears VENDOR can be used if the 1mgrd and vendor daemon are both gt
57. diag 91 U Unix and Imgrd 101 UPGRADE 36 USE_SERVER 28 USER End user options file 57 USER_BASED 32 user_info 33 Vv vendor daemon and redundant servers 21 DAEMON or VENDOR license line 26 debug log file 112 FEATURE line 29 Imreread 77 Imswitchr 79 memory usage 48 netware support 20 options file 55 FLEXIm End Users Manual April 2000 124 restarting 72 sockets 46 TIMEOUT 63 uncounted licenses 52 VENDOR_LICENSE_FILE 97 version compatibility 44 VENDOR line 24 vendor_info 33 VENDOR_LICENSE_FILE 24 VENDOR_STRING 32 W wide area network performance 103 Windows 95 and license server 103 Windows Questions 103 Y year 2000 98 125 FLEXIm End Users Manual April 2000
58. e FEATURE line If fewer licenses are available only the first set of reservations up to the license limit is used If this data were in file usr local flexim options local options then you would modify the license file DAEMON line as follows DAEMON xyzd usr local xyzd usr local flexlm options local options Limiting Access for Multiple Users Each INCLUDE INCLUDEALL EXCLUDE EXCLUDEALL and RESERVE line must have a single user name or group listed To affect more than one user name create aGROUP For example to exclude bob howard and james from using the feature called toothbrush we could create the following options file EXCLUDE toothbrush USER bob EXCLUDE toothbrush USER howard EXCLUDE toothbrush USER james However there is an easier way Create a GROUP and exclude the list of users from using the feature Like the previous example the following options file would exclude bob howard and james from using the feature called toothbrush First define the group Hackers GROUP Hackers bob howard james Then exclude the group EXCLUDE toothbrush GROUP Hackers Now when you want to allow or deny access to any feature to that group you have an alias list to make it simple The GROUP function works for a list of user names prior to FLEX m v4 0 To control access to multiple displays and hosts in pre v4 0 FLEX m you must use m
59. e via NFS on UNIX systems to all nodes in the network that need the license file e Copy the license file to all of the nodes where it is needed FLEXIm End Users Manual April 2000 20 Specifying Location of the License File Note Note 21 e Set LM_LICENSE_FILE to port host where host and port come from the SERVER line in the license file With v6 you can use host if the license file SERVER line uses a default port or specifies a port in the default port range 27000 27009 e On Windows v6 if the application can t find the license the user is presented with a dialog box that asks for the license location or the name of the system running the license server or that allows the user to type in the license directly Since the vendor daemon keeps track of license usage and since the license file contains encrypted data to protect it against modification you may move and copy the license file as much as necessary For counted licenses no matter which option you choose you must first install imgrd and the vendor daemon With a FLEX m v6 vendor daemon and 1mgra the license path can be a list of files separated by colons on UNIX or semi colons on Windows If there is a directory in this list all files named 1ic in that directory are used You can only start lmgrd on the server node specified in the license file If you are running redundant servers you should have separate copies of the l
60. e FLEX m v6 0 the DAEMON line can be called VENDOR VENDOR can be used if the 1mgrd and vendor daemon are both at least FLEX m v6 0 FLEXIm End Users Manual April 2000 26 License File Format 27 DAEMON VENDOR vendor vendor_daemon_path loptions options_file_path port port where vendor vendor_daemon_ path options_file_ path port The License File Name of the vendor daemon used to serve some feature s in the file This name cannot be changed by the administrator Path to the executable for this daemon Generally the license administrator is free to install the daemon in any directory It is recommended however that it be installed in a local directory on the license server node If the vendor daemon is v6 this path is optional If left out Imgrd will look for the vendor daemon binary in the current directory the PATH list or in the directory where lmgrd is located If the vendor daemon path is blank then the options and port strings are required if options or port number are specified Full path to the end user options file for this daemon See Chapter 6 The Options File FLEX m does not require an options file The keyword options requires a v5 vendor daemon If the vendor daemon is v6 the options file need not be specified on this line If it is called vendor opt where vendor is the vendor daemon name and located in the same directory as the license
61. e 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 deamons MULTIPLE daemon servers running Please kill and restart license daemon The license daemon has detected that multiple licenses for vendor daemon daemon are running The user should kill all daemon processes and restart the license daemon OUT feature by user n licenses user has checked out n licenses of feature RESERVE feature for USER user A license of feature is reserved for user user Retrying socket bind address in use The license servers try to bind their sockets for approximately six minutes if they detect address in use errors Selected EXISTING master node This license daemon has selected an existing master node as the master The Debug Log File F 2 Configuration Problem Messages SERVER shutdown requested A daemon was requested to shut down via a user generated kill command SIGCHLD received Killing child servers A vendor daemon logs this message when a shutdown was requested by the license daemon Configuration Problem Messages host Not a valid server host exiting This daemon was run on an invalid host name host
62. e option of deleting SERVER lines from a license file because the hostids from the SERVER lines are computed into the license keys on every FEATURE and INCREMENT line For more information about redundant servers see Chapter 5 Selecting Server Nodes The License File 3 2 2 Note License File Format The format of the SERVER line is SERV where host hostid port Example SE RV ER host hostid port The system host name or IP address String returned by the UNIX hostname or uname n command On NT ipconfig all on Windows 95 winipcfg all return the host name If the application uses FLEX m v5 or higher this can be an IP address in nnn nnn nnn nnn format Usually the string returned by the Imhostid command This can only be changed by your software supplier TCP port number to use A valid number is any unused port number between 0 and 64000 On UNIX choose a port gt 1024 since those lt 1024 are privileged port numbers The port number is optional if Imgrd the vendor daemon and the application are v6 if no port number is specified one of the default ports in the range of 27000 and 27009 will be used ER enterprise 0122345 21987 DAEMON or VENDOR Lines The DAEMON line specifies the daemon name and path lmgrd uses this line to start the vendor daemon and the vendor daemon reads it to find its options file The format of the DAEMON line is shown below Sinc
63. eature f1 to be run but only on the node with hostid 1300ab43 In this case the daemons should be run on the same node that runs the software since there is no reason to run the daemons on another node SERVER lulu 1300ab43 1700 DAEMON xyzd etc xyzd FEATURE f1 xyzd 1 00 1 jan 99 3 key 1300ab43 Mixed Node Locked and Floating Licenses Uncounted node locked and concurrent usage licenses can be mixed in the same license file The following license file allows unlimited use of feature f1 on nodes 17001111 and 17002222 while allowing two other licenses for feature f1 to be used anywhere else on the network ERVER lulu 17001234 1700 AEMON xyzd C flexlm xyzd exe EATURE f1 xyzd 1 00 1 jan 1999 0 keyl 17001111 EATURE f1 xyzd 1 00 1 jan 1999 0 key2 17002222 EATURE 1 xyzd 1 00 1 jan 1999 2 key3 yuyyuo MN This configuration requires an 1mgrd and a vendor daemon because the concurrent usage of the two licenses on the third FEATURE line is counted Decimal Format The decimal format was introduced in v6 Users with older products can still use the decimal format but they will require a copy of the lminstall command which is part of 1mut i1 The lminstal11 utility allows the user to type in a decimal line which is then converted to the readable format and saved in the specified location The mixed node locked and floating e
64. ed o setenv FLEXLM_DIAGNOSTICS 3 application Checkout succeeded f0 14263EAEA8E0 License file servtest lic o server used application2 Checkout succeeded f1 BC64A7B120AE License file localhost License Server localhost application3 Checkout succeeded f1 BC64A7B120AE License file servtest lic License Server speedy Note that the feature name and license key are printed along with the license file location or host name if host were used and host name of the server where applicable B 3 FLEX m Troubleshooting List B 3 1 Problem Description Format Each problem is presented in three parts Symptom A description of the problem Cause A discussion of what causes the problem described in the Symptom section Solution Instructions on how to solve the problem You can scan through the list of problems to find any which appear to relate to your concerns In order to solve your problem you may have to use all or some of the solutions listed here 89 Troubleshooting Guide FLEXIm Troubleshooting List B 3 2 Hostid Problems Symptom Cause Solution When I run the license manager on my machine it tells me it is the wrong hostid The vendor daemon checks the hostid listed on the SERVER line in the license file if it does not match the hostid of the machine it is running on this message will be printed Possible causes include 1 you are
65. eed to know the path to the license file This can be specified with a c license_file_path argument or by setting the LM_LICENSE_FILE environment variable Otherwise the default location is used Version 7 utilities also honor all VENDOR_LICENSE_FILE environment variables verbose Prints longer description for all errors found The output from the utilities may be harder to read with this option but is useful for diagnostics v6 only e filename Redirects error message to a file v7 See also Section C 1 How to Set Environment Variables Imcksum The lmcksum program FLEX m v2 4 or later will perform a checksum of a license file This is useful to verify data entry errors at your location Lmcksum will print a line by line checksum for the file as well as an overall file checksum 1lmcksum takes the k switch to force the encryption key checksum to be case sensitive imcksum will ignore all fields that do not enter into the encryption key computation thus the server node name and port number as well as the vendor daemon and options file paths are not checksummed In addition Imcksum will treat non case sensitive fields correctly in general 1mcksum is not case sensitive 1imcksum takes an optional daemon name if specified only license file lines for the selected daemon are used to compute the checksums License Administration Tools 7 2 Imdiag For FEATURE lines that c
66. end otherwise the file will be overwritten each time the daemon is started SAMreport a separate product available from GLOBEtrotter can be used to read and report on REPORTLOG files This file is only useful with the SAMreport license administration utility LM_PROJECT The SAMreport report writer can report on projects A project is set up by having all users working on a project set their LM_PROJECT environment variable or registry on Windows to a string that describes the project SAMreport can then group usage by project as defined by what LM_PROJECT was set to when the application was run See also Appendix C FLEXIm Environment Variables The Options File Customizing the Options File 6 2 12 RESERVE Note RESERVE lic feature type type_nam Reserves licenses for a specific user lic Number of license to reserve for this user or group feature Feature this reservation applies to type USER HOST DISPLAY PROJECT GROUP HOST_GROUP or INTERNET type_name Name of the user or group to reserve licenses for To reserve one license of feature f1 for user mel RESERVE 1 f1 USER mel Any licenses reserved for a user are dedicated to that user Even when that user is not actively using the license it will be unavailable to other users However a RESERVEd license will not cause an overdraft to be reported by SAMreport if the license is not actually i
67. ers have to wait until the first user is completely finished plus a linger interval This is only useful if the application uses duplicate grouping Otherwise LINGER will cause you to use extra licenses Contact your software vendor for information about how they implemented duplicate grouping in their product MAX v5 11 vendor daemon only MAX lic feature type type_nam Limits usage for a group or user lic Usage limit for this user or group feature Feature this limit applies to type USER HOST DISPLAY PROJECT GROUP HOST_GROUP or INTERNET type_name Name of the user or group to limit 6 2 9 MAX_OVERDRAFT MAX_OVERDRAFT feature lic Limits usage below the OVERDRAFT allowed by the license file 6 2 10 NOLOG NOLOG event_type Turns off logging of specific events by the FLEX m daemons event_type can be one of IN OUT DENIED or QUEUED FLEXIm End Users Manual April 2000 60 Customizing the Options File Note 6 2 11 Note 61 To turn off logging of checkins NOLOG IN To turn off logging of checkouts and queued requests two separate NOLOG lines are required NOLOG DENIED NOLOG QUEUED License administrators might use this option to reduce the size of the 1mgra or debug log file REPORTLOG REPORTLOG report_log_path REPORTLOG specifies the report log file for this vendor daemon If report_log_path begins with a character the file will be opened for app
68. esses On NT you configure a real NT Service On Windows 95 98 it behaves similarly to an NT service In the first tab you need to select a service Use the Configure Services tab to define a license service When configuring a service a license file is selected similar to Configuration using License File but in addition locations for lmgrd and the debug log file are specified the service is given a unique name and you can also indicate that the service should be started with system boot FLEXIm End Users Manual April 2000 80 License Administration Tools Imtools for Windows 81 License Administration Tools Hostids for FLEX m Supported Machines FLEXI m uses different machine identifications for different machine architectures For example all Sun Microsystems machines have a unique hostid whereas all DEC machines do not For this reason the ethernet address is used on some machine architectures as the hostid An ethernet address is a 6 byte quantity with each byte specified as two hexadecimal digits Specify all twelve hex digits when using an ethernet address as a hostid For example if the ethernet address is 8 0 20 0 5 ac you would specify O800200005ac as the hostid The program lImhostid will print the exact hostid that FLEX m expects to use on any given machine The following table lists alternate methods to obtain the required hostid for each machine architecture Numeric 32 bit hostids are norm
69. exactly as it comes from your vendor PACKAGE Lines The purpose of the PACKAGE line is to support two different licensing needs e To license a product SUITE or e To provide a more efficient way of distributing a license file that has a large number of features which largely share the same FEATURE line arguments A PACKAGE line by itself does not license anything it requires a matching FEATURE INCREMENT line to license the whole package A PACKAGE line can be shipped by your software vendor with a product independent of any licenses Later when you purchase a license for that package one or more corresponding FEATURE INCREMENT lines will enable the PACKAGE line Example PACKAGE package daemon pkg_version pkg_key COMPONENTS pkg_list OPTIONS SUITE where package Name of the package The corresponding FEATURE INCREMENT line must have the same name daemon Name of the vendor daemon that supports this package pkg_version Version of the package The enabling FEATURE INCREMENT line must have the same version pkg_key 20 character license key FLEXIm End Users Manual April 2000 34 License File Format 35 pkg_list OPTIONS SUIT Gl Examples List of package components The format is feature version lic Packages must consist of at least one component Version and count are optional and if left out their values come from the corresponding FEATURE INCREMENT line lic is only leg
70. ey3 This license file specifies that two licenses for feature f1 six licenses for feature f2 and one license for feature f3 are available anywhere on the network that can access the license server lulu Node Locked Licenses Node locking means the licensed software can only be used on one node A node locked license has a hostid on any FEATURE line that is node locked to a particular host There are two types of node locked licenses uncounted and counted If the number of licenses is set to 0 then the license is uncounted and unlimited use is permitted on the specified node This configuration does not require an 1imgrd or a vendor daemon because it is not going to count the concurrent usage of the features The following license file allows unlimited usage of feature f1 on the nodes with hostids of 12001234 and 1700ab12 FEATURE f1 xyzd 1 000 1 jan 99 0 keyl 12001234 FEATURE fl xyzd 1 000 1 jan 99 0 key2 1700ab12 Alternately in FLEX m v5 0 or later these two FEATURE lines could have been issued by your software vendor with a hostid list FEATURE f1 xyzd 1 000 1 jan 99 0 key HOSTID 12001234 1700ab12 The License File 3 4 3 3 5 Decimal Format If these were the only FEATURE lines in this license file no Imgrd daemon would be necessary and you should not start one The following license file allows three licenses for f
71. f interest Cross references point to more details in other parts of this manual Introduction and Overview 2 5 1 Getting Started Checklist Installing Licensed Software As a license administrator you are responsible for setting up licensing on your system or network This section tells you how to do that If you are an end user of the application and you will not be involved in installing it then go to Section 2 5 2 Notes for End Users Remember that the installation guide for your application software is the final word on installing and configuring FLEX m Generally however installing FLEX m licensing requires the following steps 1 Select your license server nodes and get their hostids See Appendix A Hostids for FLEXIm Supported Machines 2 Give the hostids to your software vendor and get a license file or the data to enter in the license file in return 3 Consider combining the new license file with any existing license files See Chapter 4 Multiple License Files 4 Determine if an options file is desired and if so set it up 5 Determine where to install the FLEX m utility programs such as lmgrd and lmutil 1mstat 1mdown etc and install them unless your vendor s installation script does so for you 6 Start lmgrd the license manager daemon manually you may also want to set it up to start automatically at boot time See Section 3 1 1 Starting the License Server at System Startup
72. file from server v2 61 MARCH 1993 USED ONLY BY SUN e Added INCREMENT and UPGRADE lines to license file v3 0 May 1994 e INCREMENT and UPGRADE behavior changed and improved e Added UDP protocol support e Added uname i hostid for HP e Added multiple jobs for enhanced support of LM_LICENSE_FILE as a license file list e New optional license file format with name value syntax for optional new features including asset_info ISSUER and NOTICE V license file continuation character 2048 character limit per feature v4 0 DECEMBER 1994 e Removed use of floating point for enhanced reliability e FEATURE line additions ck for use with Imcksum OVERDRAFT DUP_GROUP INTERNET hostid e PACKAGE line e License Finder e Imdiag and FLEXLM_DIAGNOSTICS for end user diagnostics v4 1 May 1995 e Performance improvements and new platform support v4 1 PATCH RELEASE 6 OCTOBER 1995 e PC patch release for Windows 95 with various performance improvements V5 0 MARCH 1996 e Improved port host behavior client application doesn t read license file e Automatic port host via USE_SERVER line in license file e Hostid lists lock a feature to several hostids e New FEATURE attributes SN serial number USER_BASED HOST_BASED MINIMUM SUPERSEDE ISSUED issued date CAPACITY charging based on system capacity e Optional avoidance of NIS and DNS via IP address instead of host name FLEXIm End Users Manua
73. fully shuts down all license daemons both 1mgrd and all vendor daemons on the license server node or on all three nodes in the case of three server redundant servers 1mgrd the main daemon program for FLEX m lmhost id reports the hostid of a system 1lminstal1 install a decimal format license 1lmremove removes a single user s license for a specified feature lmreread causes the license daemon to reread the license file and start any new vendor daemons 1imstat helps you monitor the status of all network licensing activities 1lmswitchr switches the report log file 1lmver reports the FLEX m version of a library or binary file Beginning in FLEX m v2 4 all FLEX m utility programs except 1mgrd are packaged as a single executable called lmut il 1mutil can either be installed as the individual commands either by creating links to the individual command names or making copies of lmutil as the individual command names or the commands can be run as 1mutil command for example lmutil lmstat or lmutil lmdown On Windows systems the Imutil command forms of the commands are available There is also a graphical user interface for these commands on Windows see Section 7 12 License Administration Tools Imtools for Windows FLEXIm End Users Manual April 2000 68 Imcksum 7 1 69 The following are valid arguments for all Imut i1 utilities c license_file_path Most Imutil utilities n
74. haos from using all features served by EXCLUDEALL HOST chaos 57 The Options File 6 2 3 Note Note 6 2 4 Customizing the Options File GROUP GROUP group user_list Defines a group of users for use in INCLUDE INCLUDEALL EXCLUDE EXCLUDEALL and RESERVE option lines group Name of the group being defined user_list List of user names in that group To define the group Hackers consisting of bob howard and james GROUP Hackers bob howard james In FLEX m v3 0 multiple GROUP lines will add all the users specified into the group Pre v3 0 FLEX m daemons do not allow multiple GROUP lines to concatenate In fact the second GROUP line would redefine the GROUP In FLEXIm v4 0 or later USER GROUP is an alias for GROUP HOST_GROUP HOST_GROUP group host_list Defines a group of hosts for use in INCLUDE INCLUDEALL EXCLUDE EXCLUDEALL and RESERVE option lines group Name of the group being defined host_list List of host names in that group FLEXIm End Users Manual April 2000 58 Customizing the Options File 6 2 5 Note 6 2 6 59 INCLUDE INCLUDE feature type type_nam Includes a user host display or group in the list of who is allowed to use the feature Anyone not in an INCLUDE statement will not be allowed to use that feature feature Name of the feature being affected type One of USER HOST DISPLAY PROJECT GROUP HOST_GROUP or INTERNET see
75. here multiple counted FEATURE lines exist for the same feature make sure the desired FEATURE line appears first All but the first is ignored 3 Place node locked uncounted lines before floating lines for the same FEATURE Otherwise the floating license may be consumed when a node locked would have been used resulting in denial for other users 4 The placement of a USE_SERVER line affects behavior A USE_SERVER line is recommended Normally the USE_SERVER line is placed immediately after the SERVER line However if there are uncounted licenses which you don t want to fail if the server is unavailable these should be placed at the top of the file with the USE_SERVER line following them This only works however if each user that needs the The License File License File Order uncounted license has direct access to a current copy of the file The advantage to placing USE_SERVER right after the SERVER line is users don t need up to date copies of the license file FLEXIm End Users Manual April 2000 40 License File Order 41 The License File Multiple License Files Since more than 2000 vendors have chosen FLEX m as their license manager chances are good that you will have to administer FLEX m licenses from more than one vendor or multiple products from the same vendor 4 1 Overview of Combining License Files When you are running FLEX m licensed products from multiple vendors you may need to take steps to preven
76. hey are not on the excluded IP addresses and they are not a member of the painters GROUP and they are not bob to use feature spell by implication Note that bob could have been added to the group painters However painters might be used for some other purpose in the future so the license administrator chose to handle bob as a special case here In this case the two EXCLUDE statements concatenate to create a list of four users FLEXIm End Users Manual April 2000 66 INCLUDE Example 6 5 INCLUDE Example INCLUD INCLUD INCLUD ry a ry paint USER picasso paint USER mondrian paint HOST bigbrush This options file would e Allow the user picasso to use the feature paint on any machine on the network e Allow the user mondrian to use the feature paint on any machine on the network e Allow any user as long as they are on the host bigbrush to use feature paint e Deny access to the feature paint to anyone except picasso mondrian or anyone from the host bigbrush by implication 67 The Options File License Administration Tools FLEXI m provides utilities for the license administrator to help manage the licensing activities on the network These utilities are 1imcksum v2 4 or later prints license checksums 1imdiag v4 0 or later diagnoses license checkout problems 1mdown grace
77. hicago SERVER chicago 17007ea8 1700 DAEMON xyzd etc mydaemon FEATURE f1 xyzd 1 000 01 jan 99 5 26C7DD9CD665B8270186 FEATURE 2 xyzd 1 000 01 Jan 99 5 0739D2F78CE46C57041D License 2 for tokyo SERVER tokyo 17007ea8 1700 DAEMON xyzd etc mydaemon FEATURE f1 xyzd 1 000 01 jan 99 5 16BE40E1DAEEEDA8798D FEATURE f2 xyzd 1 000 01 jan 99 5 6DBO6F3E40E61885712DF The user in Chicago could set LM_LICENSE_FILE to 1700 chicago 1700 tokyo The user in Tokyo could set LM_LICENSE_FILE to 1700 tokyo 1700 chicago The application attempts the first server in the list and if that fails for any reason the second server is tried FLEXIm End Users Manual April 2000 50 Counted vs Uncounted Licenses 5 3 3 Comparing Three Server to License File List 5 4 51 ARE THERE ANY DRAWBACKS TO USING THE LICENSE FILE LIST FOR REDUNDANCY Yes By default once a license job has successfully checked out a license from one host all subsequent checkouts must be satisfied from the same host If the application requires more than one license this could result in a license denial when the license is available on another server An application can bypass this restriction if it is coded with the use of multiple FLEX m license jobs Only your application vendor can tell you if their application is programmed in this
78. icense file as well as the binaries for Imgrd and the vendor daemons on each server node If you do not do this you lose all the advantages of having redundant servers since the file server holding these files becomes a single point of failure Starting the License Server at System Startup If any licenses in the license file are counted license count gt 0 then the license server must be started before the product can be used UNIX To start the license manager daemon 1mgrd execute a command similar to the following If you are running in the C shell o Imgrd_path c license_file_path 1 debug_log_path amp If you are using either the Korn or Bourne shell nohup Imgrd_path c license_file_path 1 debug_log_path 2 gt amp 1 amp The License File Specifying Location of the License File Each UNIX operating system can have some quirks in doing this but the following script has been successfully tested for HP700 systems See the notes following for a full explanation bin su daniel c echo starting lmgrd gt home flexlm v5 12 hp700_u9 boot log bin nohup bin su daniel c umask 022 nome flexlm v5 12 hp700_u9 lmgrd c home flexilm v5 12 hp700_u9 license dat gt gt home flexlm v5 12 hp700_u9 boot log bin su daniel c echo sleep 5 gt gt home flexlm v5 12 hp700_u9 boot log bin sleep 5 bin su daniel c echo Imdiag gt gt home flexlm v5 12 hp700_u9
79. ile Since there are no vendor daemons to start there is nothing to do NO DAEMON line for daemon A vendor daemon logs this error if it cannot find its own daemon name in the license file Daemon Software Error Messages read error message An error in a read system call was detected select message An error in a select system call was detected This is usually a sign of a system networking failure The Debug Log File FLEX m Versions G1 Version Co mpatibility and Components In general always use the latest lmgrd and lmutil Imtools which are available from http www globetrotter com and you ll automatically enjoy many of the enhancements available in the most recent versions However some enhancements require upgraded vendor daemons and yet others require upgraded client Imgrd applications Given the following components e Imutil includes Imstat 1mdown etc and Imtools on Windows e Vendor daemon e License file the rules about compatibility can be summarized as follows Version of Version of Lmut il must be gt lmgrd which must be gt Version of vendor daemon which must be gt Version of client application which must be gt Version of icense file format Except for the license file you can use 1mver to discover the version of all these components For the vendor daemon lmgrd and lmut il you can also use the v argument to print the version F
80. ing policies 1 3 Related Documents from GLOBEtrotter Software In addition you can refer to Appendix B Troubleshooting Guide which contains a list of common problems and their solutions Related Documents from GLOBEtrotter Software The SAMsuite Users Guide describes the SAMsuite license administration tool for managing FLEX m enabled applications and the SAMwrap Users Guide describes SAMwrap for administrators who wish to provide FLEX m license management for applications shipped without embedded license management The FLEXIm Programmers Guide and FLEXIm Reference Manual are for programmers responsible for incorporating FLEX m into their products FLEXIm End Users Manual April 2000 10 Related Documents from GLOBEtrotter Software 11 Welcome to FLEXIm Introduction and Overview This chapter explains the basics of floating network licensing and gives a quick overview of the components of FLEX m It explains where license administrators have control and where end users have control Section 2 5 Getting Started Checklist tells both license administrators and end users how to start managing FLEX m 2 1 Introduction to FLEX m FLEXI m is the most popular license manager used in the software industry FLEXIm is best known for its ability to allow software licenses to be available or float anywhere on a network instead of being tied to specific machines Floating licensing benefits both users and license adm
81. inistrators Users can make more efficient use of fewer licenses by sharing them on the network License administrators can control who uses the licensed application and the node s where the licenses will be available See Section 3 4 Types of License Files for details about the different licensing models supported by FLEXI m 2 2 FLEX m Components The four main components of FLEX m are e License manager daemon e Vendor daemon e License file e Application program 2 2 1 The License Manager Daemon Imgrd The license manager daemon 1mgrd handles the initial contact with the client application programs passing the connection on to the appropriate vendor daemon It also starts and restarts the vendor daemons FLEX m permits multiple redundant license manager daemons on three server nodes FLEXIm End Users Manual April 2000 12 FLEXIm Components Note 2 2 2 2 2 3 13 allowing you to make your license available if any two of the three server nodes is running Redundancy can be achieved with three server redundant servers or by using a license file list with any number of servers lmgrd is not present on VMS or Netware systems The Vendor Daemon In FLEX m licenses are granted by running processes unless they re node locked uncounted licenses in which case they need only read the license file to run There is one process for each vendor who has a FLEX m licensed product on the network This process is
82. l April 2000 118 How to Tell the License File Version e Improved report log file format e Server upon startup notifies of licenses that will expire within two weeks e Improved end user options file functionality v5 11 FEBRUARY 1997 e SUPERSEDE lists PLATFORMS license attribute e new end user options MAX TIMEOUTALL e Windows control panel added e Windows license generator GENLIC added V5 12 APRIL 1997 e Performance improvements and new platform support v6 0 SEPTEMBER 1997 e Imgrd can read multiple license files e FLEXIm license directory support 1ic automatically used e License files require no editing for use at the end user site e Optional path on DAEMON VENDOR line PATH variable used e Decimal license format with lminstall utility for typing in licenses e FEATURE lines are shorter easier to understand and type in e PACKAGE lines can be shipped in separate files that never require user editing e Default port numbers make SERVER line port number optional e Default end user options file path e this_host host name supported on SERVER line e VENDOR_LICENSE_FILE supported e g GSI_LICENSE_FILE e host supported where default port numbers are used e Windows only user prompted for license file or license server name e License files are optionally case insensitive e 1mdown and lmreread accept vendor vendor argument e START dd mmm yyyy optional license attribute V6
83. le descriptors which ranges from 256 on SunOS 4 x to 4000 on DEC Alpha When no more file descriptors are available to a daemon additional vendor daemons are spawned to allow for extra file descriptors though this is not recommended When using UDP there is no limit to the number of end users per vendor daemon process since they can share a single socket in the vendor daemon UDP has other drawbacks and TCP is normally preferred If there are more than 250 concurrent clients from a SunOS vendor daemon it may be a good idea to move the server to a different OS since all other OSs support more file descriptors If there are more than 1000 concurrent clients being supported by a single vendor daemon then it s probably good to split the license file into more than one file from different servers to lighten the networking traffic which will require the ISV to agree to issue new licenses Clients can check out licenses from multiple servers using a license file list via LM_LICENSE_FILE Each client connected to a license server uses one socket The total number of sockets used by the license server programs is slightly larger than the total number of simultaneous clients FLEXIm End Users Manual April 2000 46 Resources Used by the Server Note 47 On older SCO systems the default number of sockets may be set fairly low if you choose to run a server on such a machine you may need to reconfigure your kernel to ha
84. m as your application If your application is FLEX m v4 1 or later v5 or later on Windows you can use the FLEXLM_DIAGNOSTICS environment variable Set FLEXLM_DIAGNOSTICS to 1 2 or 3 A setting of 3 gives more information than 2 2 gives more information than 1 in particular the feature name that was denied When you talk to a support person you should be prepared to answer the following questions What kind of machine is your license server running on What version of the operating system What machine and operating system is the application running on What version of FLEX m does the program use Use the 1mver script or on UNIX execute the following command on your Imgrd vendor daemon and application strings binary_name grep Copy Alternatively Imgrd v gives the lmgrd version and this works with the vendor daemon also FLEXIm End Users Manual April 2000 86 FLEXLM_DIAGNOSTICS B 2 Note B 2 1 87 e What error or warning messages appear in the log file Did the server start correctly Look for a message such as server xyz started for featurel feature2 e What is the output from running lmstat a e Are you running other products which are also licensed by FLEX m Are you using a combined license file or separate license files e Are you using redundant servers multiple SERVER lines in your license file FLEXLM_DIAGNOSTICS Available only with applications using FLEX m v4 1 or higher
85. manner If the application supports license queueing all licenses are only queued from the first host on the list Finally if one server becomes unavailable some licenses will be unavailable WHEN IS IT RECOMMENDED TO USE A LICENSE FILE LIST FOR REDUNDANCY RATHER THAN TRUE REDUNDANT SERVERS e When there s less system administration available to monitor license servers e When load balancing is needed for clients located far apart e g London and Tokyo You can make servers available locally with remote servers available as backup e License file list is more forgiving if you lose quorum e It s not limited to three servers any number will work For wide area networks you can make servers available locally with remote servers available as backup e Clients do not require reliable networking to a single node with license file list so this is recommended where networking itself requires redundancy Counted vs Uncounted Licenses The license file determines whether a license server is needed If all the FEATURE or INCREMENT lines have a license count of 0 unlimited or uncounted FLEX m v6 or later only then no server is needed This type of license is called uncounted Alternatively if any FEATURE lines have a non zero license count then a server is required to count those licenses If a vendor wants to use FLEX m without a server they must issue uncounted licenses With FLEX m v5 or later the license
86. n use 6 2 13 TIMEOUT TIMEOUT feature seconds Sets the time after which an inactive license is reclaimed by the vendor daemon feature Name of the feature seconds Number of seconds after which inactive license is reclaimed To set the timeout for feature f1 to one hour 3600 seconds TIMEOUT f1 3600 TIMEOUT checks in the licenses if the process has been idle for a period longer than the specified time period and someone else wants the license The daemon declares a process idle when it has not heard from the process the FLEXIm End Users Manual April 2000 62 Understanding Options Files client sends heartbeats The application must explicitly declare itself idle for this to work or on UNIX the application must be stopped Z That is unless the application explicitly supports this feature it will not work Contact your software vendor for information about how they implemented this feature in their product The application vendor can also disable the timeout feature in which case the TIMEOUT option has no effect The vendor can set a minimum value for the timeout If you specify a timeout value smaller than the minimum the minimum is used The default minimum value is 900 seconds 15 minutes If you do not specify a timeout value in your options file then there will be no timeout for that feature With a pre v5 vendor daemon licenses are only freed by TIMEOUT when a new request for a license
87. n with Imdown 71 starting automatically at boot time 17 syntax 72 tcp ports 100 Unix startup script 21 usage 72 v6 supports license path 21 VENDOR DAEMON line usage 26 version compatibility 116 Windows 23 Imhostid 31 74 Iminstall 75 Imremove 75 Imreread 77 Imstat 78 Imstat a troubleshooting flexlm with 86 Imswitchr 78 LMTOOLS 80 Imver 79 log file managing 47 M MAX 60 MAX_OVERDRAFT 60 Multiple License Files 42 N network FLEXIm load 101 network bandwidth and FLEXIm 48 NFS 101 NIS 102 node locking mixed with floating 37 NOLOG 60 NOTICE 32 123 FLEXIm End Users Manual April 2000 O Options File Example 64 Options file overview 17 options file and Imreread 77 required for HOST_BASED and USER_BASED 32 specifying on DAEMON line 26 syntax and description 54 usage examples 63 OPTIONS SUITE 35 OVERDRAFT 32 P PACKAGE syntax 34 PROJECT 57 R Redundant Servers Overview 49 redundant servers and SERVER line 25 keep separate license file copies 21 selecting server nodes 49 remote disks guidelines for using 49 REPORTLOG 47 61 RESERVE 62 S SERVER lines combining license files 43 server nodes deciding number of 49 servers disk space used 47 sockets used 46 SN 32 sockets differences under SCO 47 number used by license server 46 START 32 subnets 102 SUITE 35 SUPERSEDE 32 T TIMEOUT 62 TIMEOUTALL 63 Troubleshooting 89 guide 86 troubleshooting FLEXLM_DIAGNOSTICS 87 Im
88. nd the paths are the correct paths to lmgrd the license file and the debug log file You will have to ensure that the vendor daemons listed in the license file have execute permissions for username The paths to all the vendor daemons in the license file are listed on each DAEMON line Is it OK to run Imgrd as root UNIX only It is not prudent to run any command particularly a daemon as root on UNIX as it may pose a security risk to the operating system Therefore we recommend that 1mgrd be run as a non privileged user not root If you are starting 1mgrd from a boot script we recommend that you use su username c umask 022 Imgrd to run lmgrd as a non privileged user Does FLEX m licensing impose a heavy load on the network No but partly this depends on the application and end user s use A typical checkout request requires five messages and responses between client and server and each message is lt 150 bytes When a server is not receiving requests it requires virtually no CPU time When an application or lmstat requests the list of current users this can significantly increase the amount of networking FLEX m uses depending on the number of current users Also prior to FLEX m v5 use of port host can increase network load since the license file is downloaded from the server to the client port host should be if possible limited to small license files say lt 50 features In v5 port ho
89. ng if the vendor specified this match a prior INCREMENT or FEATURE line the new number of licenses is added to the old number If any of the three do not match a new group of licenses is created in the vendor daemon and this group called a license pool is counted independently from others with the same feature name INCREMENT is not available for pre v2 61 FLEX m clients or servers A FEATURE line does not give an additional number of licenses whereas an INCREMENT line always gives an additional number of licenses There is a rarely used option in FLEX m which causes FEATURE lines to function as INCREMENT lines This option is called Is_use_all_feature_lines You will have to ask your vendor if they use this option If they do then all FEATURE lines behave exactly as INCREMENT lines FLEXIm End Users Manual April 2000 28 License File Format Note Note 29 A FEATURE line placed after another FEATURE or INCREMENT line will be ignored unless Is_use_all_feature_lines is set The format for the FEATURE line changed in FLEX m v3 0 and again in FLEX m v6 0 The older formats are understood by new clients and servers but the new formats are more flexible v2 format FEATURE INCREMENT feature daemon feat_version exp_date lic key vendor_str feat_hostid v3 format FEATURE INCREMENT feature daemon feat_version exp_date lic key HOSTID feat
90. not work properly with an older lmgrd e A newer vendor daemon or 1mgrd can be used with an older client program but a newer client program might not work properly with an older vendor daemon From these two compatibility rules come the simple rules for selecting which version of administration tools to use 1 Always use the newest version of 1mgrd and the newest version of each vendor daemon 2 Use the newest FLEX m utilities For specific application programs you can use either the new or the old version of course the vendor daemon for that application must be at least as new as the application itself See also Section G1 Version Compatibility and Components Using Separate License Files on the Same Server Node You must run a separate copy of 1mgrd for each license file When you run multiple copies of 1mgrd there are two details to remember 1 The port number on the SERVER line of each license file must be unique You can use a standard text editor to change the port number in each license file so that they are all different 2 You must make sure that you are using a compatible version of Imgrd when you start it up for a particular license file This can be done by using an explicit path to lmgrd When running client programs such as a licensed application you can set the LM_LICENSE_FILE environment variable to point to multiple license files For example you may have a license file from vendor ABC an
91. nse file vendor Vendor daemon in this license file new_report_log Path to new report log file imswitchr does not work with FLEX m v3 0 vendor daemons Ask your vendor for a later version of their vendor daemon Imver The lmver utility reports the FLEX m version of a library or binary file Usage is imver filename where filename is the name of an executable file built with FLEX m For example if you have an application called spell type o lmver spell Alternatively on UNIX systems you can use the following commands to get the FLEX m version of a binary strings filename grep Copy License Administration Tools 7 12 7 12 1 License Administration Tools Imtools for Windows License Administration Tools Imtools for Windows For the 32 bit Windows platforms an Imtools program is provided With Imtools you can start stop and configure FLEX m license servers get system information including hostids get server status and more Imtools v7 has two modes in which to configure a license server e Configuration using a license file e Configuration using services Configuration Using License File Operations are performed on a particular license file In this mode you cannot start the Lmgrd process but you can do everything else In the first tab you need to select a license file 7 12 2 Configuration Using Services Operations are performed on a Windows Service which allows starting lmgrd proc
92. o lm_init Local checkout filter rejected request FLEXIm End Users Manual April 2000 108 Error Code Descriptions 85 86 87 88 89 Attempt to read beyond end of license file path SYS SETIMR call failed VMS Internal FLEXIm error please report to GLOBEtrotter Software Bad version number must be floating point number with no letters FLEXIm internal error 78 FLEXIm internal error 79 FLEXIm internal error 80 FLEXIm internal error 81 Invalid PACKAGE line in license file FLEXI1m version of client newer than server USER_BASED license has no specified users see server log License server doesn t support this request License object already in use Java only Checkout exceeds MAX specified in options file System clock has been set back This platform not authorized by license Future license file format or misspelling in license file The file was issued for a later version of FLEX m than this program understands ENCRYPTION_SEEDS are non unique Feature removed during Imreread or wrong SERVER line hostid 109 FLEXIm Error Codes 102 103 104 105 106 Error Code Descriptions This feature is available in a different license pool This is a warning condition The server has pooled one or more INCREMENT lines into a single pool and the request was made on an INCREMENT line that has been pooled Attempt to generate license with incompatible attributes
93. ode Note that you are not required to combine compatible license files you always have the option of running separate 1mgrds and there is virtually no performance or system load penalty for running separate 1mgra processes Combining License Files from Multiple Vendors If your license files are compatible you can combine them with any text editor To combine license files read all of the compatible license files into one file then edit out the extra SERVER lines so that only one set of SERVER lines remains Write out this data and you have your combined license file If you combine license files from multiple vendors it is a good idea to keep a copy of the combined license file in each vendor s default license file location This way users can avoid having to set LM_LICENSE_FILE because each package finds it s license information in the default place On UNIX you can do this with a symbolic link from each default location to the location of the combined license file Multiple License Files 4 1 2 Overview of Combining License Files FLEX m Version Component Compatibility When you combine license files for two different FLEX m licensed products it may be the case that those products do not use the same version of FLEX m FLEX m is designed to handle this situation There are two basic compatibility rules for FLEX m e A newer lmgrd can be used with an older vendor daemon but a newer vendor daemon might
94. of either the license server machine or the file server machine will cause the licenses to be unavailable Redundant Servers FLEX Im supports two methods of redundancy a set of three redundant license servers and redundancy via a license file list in the LM_LICENSE_FILE setting With three server redundancy if any two of the three license servers are up and running two out of three license servers is referred to as a quorum the system is functional and hands out its total complement of licenses With LM_LICENSE_FILE list redundancy each one of a group of license servers serves a subset of the total licenses The end user sets LM_LICENSE_FILE to a list of license files where each license file refers to one of the license servers The application then tries each server in the list in order until it succeeds or gets to the end of the list See also Section 4 2 Using LM_LICENSE_FILE License File List Three Server Redundancy SELECTING SERVER NODES If all the end user data is on a single file server then there is no need for redundant servers and GLOBEtrotter Software recommends the use of a single server node for the FLEX m daemons If the end user s data is split among two or more server nodes and work is still possible when one of these nodes goes down or off the network then multiple server nodes can be employed In all cases an effort should be made to select stable systems a
95. omponents 116 G 2 How to Tell the License File Version 0 4 117 FLEXIm End Users Manual April 2000 vi vii FLEXIm End Users Manual April 2000 Welcome to FLEX m FLEX m is the de facto standard network license manager used by over 2000 leading software vendors to control the use of their software products If you are a system administrator or user chances are one or more of the products currently on your network is licensed by FLEX m This manual explains FLEX m from an end user standpoint and how to use the tools which are part of the standard FLEX m distribution kit GLOBEtrotter Software also provides the SAMsuite asset management tool for more advanced license server control and reporting Please contact GLOBEtrotter Software by email at info globes com or on the Internet at http www globetrotter com for more information about SAMsuite Keep in mind that certain topics such as password encryption are vendor specific and proprietary so we cannot document them in any detail Also because FLEX m does not enforce a particular licensing strategy each vendor s implementation can have subtle differences If you do not find out what you need to know here you should contact your vendor s technical support group 1 1 Versions of FLEX m This manual covers features of interest to license administrators and end users in FLEX m versions 1 0 through 7 0 1 2 Howto Use This Manual
96. onal Supporting information FLEX1m error Ilm_errno minor_num System Error sys_errno system_error_text Example Cannot connect to license server The server lmgrd has not been started yet or the wrong port host or license file is being used or the port or hostname in the license file has been changed Feature f1 Server name localhost License path localhost license dat lic FLEX1m error 15 12 System Error 61 Connection refused Error Code Descriptions Errors marked with an indicates errors which should not appear in shipping software These are errors intended to help the programmer incorporate FLEX m in their product and should be fixed before shipping Errors marked with indicate errors due to an operating system failure Error Description 1 Cannot find license file 2 Invalid license file syntax 3 No server for this feature 4 Licensed number of users already reached 5 No such feature exists 6 No port number in license file and FLEXIm service does not exist pre v6 only 7 No socket connection to license manager service 8 Invalid inconsistent license key The license key and data for the feature do not match This usually happens when a license file has been altered FLEXIm Error Codes 10 11 12 13 14 15 Error Code Descriptions Invalid host The hostid of this system does not match the hostid specified in the license file
97. ontain ck nnn lmcksum prints simply OK or BAD Usage is imcksum c license_file_path where c license_file_pathis the path to the license file to checksum By default Imcksum uses license dat in the current directory unlike other lmutil commands Example output is imcksum Copyright C 1989 1997 GLOBEtrotter Software Inc imcksum using license file usr local flexlm licenses license dat189 SERVER speedy 08002b32b161 2837 189 SERVER speedy 08002b32b161 2837 166 DAEMON xyzd C flexlm xyzd exe 8 FEATURE f1 xyzd 1 000 01 jan 99 0 3B2BC33CE4E1B8F3A0BF OK 231 FEATURE f2 xyzd 1 0 01 jan 0 1 8B1C30015351B7737F5E DUP_GROUP HD ck 231 109 overall file checksum Imdiag lmdiag FLEX m v4 0 or later allows you to diagnose problems when you cannot check out a license Usage is imdiag c license_file_path n feature where c license_file_path Path to the file to diagnose n Run in non interactive mode 1mdiag will not prompt for any input in this mode In this mode extended connection diagnostics are not available feature Diagnose this feature only FLEXIm End Users Manual April 2000 70 Imdown 7 3 71 If no feature is specified 1mdiag will operate on all features in the license file s in your path Imdiag will first print information about the license then attempt to check out each license If the checkou
98. r a single vendor with two features SERVER excellent_server 17007ea8 1700 DAEMON xyzd etc xyzd FEATURE xyz_appl xyzd 1 000 01 jan 1999 10 1EF890030EABF324 FEATURE xyz_app2 xyzd 1 000 01 jan 1999 10 0784561FE98BA073 The license file above would allow the license server excellent_server with the hostid 17007ea8 to serve ten floating licenses for xyz_app1 and xyz_app2 to any user on the network FLEXIm End Users Manual April 2000 36 Types of License Files 3 4 3 4 1 3 4 2 37 Types of License Files License files are created by the software vendor License files can specify floating concurrent usage node locked both counted and uncounted and any combination of floating counted and uncounted Floating Concurrent Licenses A floating license means anyone on the network can use the licensed software up to the limit specified in the license file also referred to as concurrent usage or network licensing Floating licenses have no hostids on the individual FEATURE lines Floating licenses requires an 1mgrd and a vendor daemon to be running to count the concurrent usage of the licenses An example of a license file that provides floating licenses is SERVER lulu 17001234 1700 DAEMON xyzd etc xyzd FEATURE f1 xyzd 1 00 1 jan 99 2 key1 E E EATURE f2 xyzd 1 00 1 jan 99 6 key2 FATURE 3 xyzd 1 00 1 jan 99 1 k
99. rs of clients For a large number of clients hundreds each of which will be exchanging heartbeat messages with the vendor daemon the network bandwidth used may start to become significant In this case you should run client and server on the same local area network which may require splitting licenses between two files for two servers Users can use a license file list in LM_LICENSE_FILE to have effective access to both servers In high traffic networks with FLEX m clients older than v5 you may also want to avoid setting LM_LICENSE_FILE toa port host address Instead the license administrator should place a copy of the license file in a file system local to the application See Section 3 1 Specifying Location of the License File FLEXIm End Users Manual April 2000 48 Remote Mounted Disks 5 2 5 3 5 3 1 49 Remote Mounted Disks GLOBEtrotter Software recommends that you do not use remote mounted disks when you run the license server In other words we recommend that lmgraq the vendor daemons the license file and the debug and report log files are all on locally mounted disks If any of these files is on a remote mounted disk you double the points of failure which could lead to a temporary loss of all of your licenses When all files are mounted locally the licenses will be available as long as the server machine is up but when the files are on a different machine then the loss
100. s see Section 3 1 1 Starting the License Server at System Startup ADMINISTRATION TOOLS GLOBEtrotter Software supplies administration tools to your software vendor The vendor usually includes them with their product The recommended location for the tools is usr local bin UNIX C flexlm Windows or SYSSCOMMON SYSMGR VMS but you can install them in a different location or not at all See Chapter 7 License Administration Tools for more information OPTIONS FILES The options file controls various options such as reservations and timeouts of licenses Most users run without an options file but you may decide you want to use some options For example many administrators use an option to limit the quantity and content of logged messages To set up an options file see Chapter 6 The Options File Notes for End Users As a user of a FLEX m licensed application you may need to know a few things to use the system effectively The main things you need to know are e How to tell an application which license file to use e How to query the system to find out who is using a license How TO SPECIFY A LICENSE FILE The license file determines what features are available to a program It also contains information telling the application how to connect to the license server For information about the standard way of specifying a license file for an application see Chapter 3 The License File Introduction
101. s server nodes in other words do not pick systems that are frequently rebooted or shut down for one reason or another The three server nodes can be any supported server nodes it is not required that they be the same architecture or operating system Selecting Server Nodes 5 3 2 Redundant Servers Three server redundancy does not provide load balancing Use LM_LICENSE_FILE list instead for this type of redundancy This is because with three server redundancy only one of the three servers is master capable of issuing licenses Since all clients must contact the master all clients must have reliable networking to a single node These three server redundant servers should have excellent communications and should be on the same subnet Often this means that the three servers should be located physically close to each other This form of redundancy requires that the servers exchange heartbeats periodically and poor communications can cause poor performance You should never configure redundant servers with slow communications or dial up links Redundancy via License File List in LM_LICENSE_FILE This is best explained by example If ten licenses are desired for both f1 and f2 the ISV would issue two sets of licenses with a count of 5 for each of f1 and f2 The server nodes unlike three server redundancy can be physically distant The license files would look like License 1 for c
102. se drivers are available at http www globetrotter com or from your software vendor 111 FLEXIm Error Codes The Debug Log File The daemons all generate debug log files in the following format hh mm daemon message where hh mm Time that the message was logged daemon Either 1mgra or the vendor daemon name In the case where a single copy of the daemon cannot handle all of the requested licenses an optional _ followed by a number indicates that this message comes from a forked daemon message The text of the message The debug log files can be used to e Diagnose configuration problems e Diagnose daemon software errors Note The debug log file cannot be used for usage reporting with SAMreport F 1 Informational Messages Connected to node This daemon is connected to its peer on node CONNECTED master is node The license daemons log this message when a quorum is up and everyone has selected a master FLEXIm End Users Manual April 2000 112 Informational Messages 113 DENIED n feature to user 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 EXPIRED feature feature has passed its expiration date IN feature by user n licenses user has checked back in n licenses of feature Lost connection to host A daemon can no longer communicate with its peer on node host which can cause th
103. server can serve uncounted licenses as well This is done so that the report log file will include transactions for all license requests which can then be reported on by SAMreport To do this Selecting Server Nodes Counted vs Uncounted Licenses include a SERVER line in the license file and put the USE_SERVER line immediately after the SERVER line The vendor daemon will service the uncounted licenses and the USE_SERVER line indicates to applications that they will be authorized by the server FLEXIm End Users Manual April 2000 52 Counted vs Uncounted Licenses 53 Selecting Server Nodes The Options File The options file allows the license administrator to control various operating parameters of FLEX m Users can be identified by their user name host name display IP address or PROJECT which is set with the LM_PROJECT environment variable Specifically the license administrator can Allow the use of features Deny the use of features Reserve licenses Control the amount of information logged about license usage Enable a report log file Options files allow you as the license administrator to be as secure or open with licenses as you like Lines in the options file were limited to 200 characters prior to FLEX m v3 0 In v3 0 and later the line length is 2048 characters FLEX m v4 0 allows the character as a continuation character in options file lines Identifying users by LM_PROJECT requires
104. st actually improves performance Does FLEX m work with NFS Yes FLEX m has no direct interaction with NFS FLEX m uses an NFS mounted file like any other application Frequently Asked Questions Using FLEXIm D 3 10 Does FLEX m work with ATM ISDN Token Ring etc In general these have no impact on FLEX m FLEX m requires TCP IP or SPX Novell Netware So long as TCP IP works FLEX m will work D 3 11 Does FLEX m work with subnets fully qualified names multiple domains etc Yes although this behavior was improved in v3 0 and v6 0 When a license server and a client are located in different domains fully qualified host names have to be used A fully qualified host name is of the form node domain where node is the local host name usually returned by the hostname command or uname n and domain is the Internet domain name e g globes com To ensure success with FLEX m across domains do the following 1 Make the sure the fully qualified host name is the name on the SERVER line of the license file 2 Make sure ALL client nodes as well as the server node are able to telnet to that fully qualified host name For example if the host is locally called speedy and the domain name is corp com local systems will be able to logon to speedy viatelnet speedy But very often telnet speedy corp com will fail locally Note that this telnet command will always succeed on hosts in other domains
105. stem has that program whatis should tell you the file is an executable for the machine you are trying to run it on Run the vendor daemon directly from the command line If the vendor daemon is properly linked it will tell you that it must be run from imgrq if it crashes or fails to execute then it is not properly linked FLEXIm End Users Manual April 2000 94 FLEXIm Troubleshooting List 95 Symptom Cause Solution The license server keeps reporting lost lock errors in the log file and exiting The lock file normally placed in usr tmp on UNIX C flexlm on Windows NT SYS SYSTEM FLEXLM on Netware is being removed by someone else There could be another daemon running or the license administrator or a script he set up could have deleted the file Check to see if there is more than one copy of the daemon running On UNIX use a command like ps aux grep vendor to search for it Check for more than one lmgrd running as well since it will restart your vendor daemon when it is killed If more than one 1mgrd is running kill them all using the kill command not kill 9 on UNIX or Imtools on Windows NT then kill any remaining vendor daemons on UNIX try a simple kill if that fails then try kill 9 the lmgrd and all vendor daemons and start one fresh copy of lmgrd On UNIX check to see if there is a shell script running that cleans out tmp or usr tmp If so try modifying it so that i
106. t does not delete zero length files Troubleshooting Guide FLEX m Environment Variables Environment variables should never be required to use FLEX m licensed applications Environment variables are normally used for debugging or for changing license default location C 1 How to Set Environment Variables FLEX m environment variables are set in two different ways e The normal set or setenv commands or the System Control Panel on Windows NT e The registry Windows v6 or in SHOME flexlmrc UNIX v7 which functions like the registry for FLEX m on UNIX C 1 1 Registry On Windows the FLEX m registry location is HK EY_LOCAL_MACHINE gt SOFTWAR E FLEX1m License Manager On UNIX the equivalent information is stored in HOME flexlmrc In this file the syntax is variable value C 1 2 Precedence If the variable is LM_LICE NSE_FILE or VENDOR_LICENSE_FILE then both the environment and the registry are used with the environment used first and the registry appended to the path If it s a different variable then if the environment set only that is used otherwise the registry is used That is the registry is only used if the environment is not set FLEXIm End Users Manual April 2000 96 Environment Variables C 2 Environment Variables Variable FLEXLM_BATCH FLEXLM_ DIAGNOSTICS LM_LICENSE_FI VENDOR_LICENS E
107. t licensing conflicts during installation There are three ways you can accomplish this e Multiple license server nodes each running one Imgrd and one license file e One license server node running one lmgrd and several license files e One license server node running multiple 1mgrds and multiple license files Note that before v6 each 1mgrd could read only a single license file In the first option mentioned above you will have more license servers to monitor in the third option you have only one server but multiple 1mgrds to administer If all applications and vendor daemons are FLEX m v6 lmgrd can process multiple license files even when the hostids in each license file are different so long as they refer to the same node For example on UNIX imgrd c license_file_path_1l license_file_path_2 Your product s license file s define the license server s by host name and hostid in the SERVER line s in the license file If the license files for two or more products contain identical hostids on the SERVER line s then these files can be combined If the license files for two products contain different hostids on a SERVER line then the license servers for those products will be running on different nodes and the license files cannot be combined If you have two or more products whose license servers run on the same node as specified by the SERVER lines in the license files you may be able to combine the license files into
108. t machine and the server machine is down 6 You are mixing FLEX m v1 5 or earlier and v2 1 or later vendor daemons in one license file and have run lmgrd without the b command line option 7 TCP is not running on your machine The lmdiag utility is designed primarily to debug this problem so first try lmdiag Verify that the application is using the proper license file Verify that specified server machine is up and reachable by executing another command that uses TCP such as telnet from the client to the server Verify that the vendor daemon is running you can use ps on the server to look for it Examine the license log file to see if any problems are reported particularly messages indicating that the vendor daemon has quit Run lmstat a from the server machine to verify that the vendor daemon is alive Run lmstat a from the client machine to verify the connection from client to vendor daemon across the network Try using telnet host port where host and port are the same as on the SERVER line in your license file Troubleshooting Guide FLEXIm Troubleshooting List B 3 4 Other Client Problems Symptom Cause Solution Symptom Cause Solution When I run my application program or vendor daemon I get the error bad code or inconsistent encryption code Possible causes for this are 1 the license file was modified either the hostid on a SERVER line or anything on the FEATURE line was changed 2 the
109. t succeeds 1mdiag will indicate this If the checkout fails 1mdiag will give you the reason for the failure If the checkout fails because 1mdiag cannot connect to the license server then you have the option of running extended connection diagnostics These extended diagnostics attempt to connect to each port on the license server node and can detect if the port number in the license file is incorrect lmdiag will indicate each port number that is listening and if it is an Lmgrd process lmdiag will indicate this as well If 1mdiag finds the vendor daemon for the feature being tested then it will indicate the correct port number for the license file to correct the problem See also Section B 2 FLEXLM_DIAGNOSTICS Imdown The 1lmdown utility allows for the graceful shutdown of all license daemons both imgrd and all vendor daemons on all nodes Usage is imdown c license_file_path vendor vendor q all where c license_file_path Use the specified license file vendor vendor Only shutdown this one vendor daemon lmgrd will always continue running if this option is specified Requires v6 0 1mdown and 1mgrd the vendor daemon can be any version g Don t prompt or print a header Otherwise 1mdown asks Are you sure y n all If multiple servers are specified automatically shuts down all of them Otherwise only one is shutdown q is implied with a11 v7 License Administration Tools
110. therefore the pre v3 0 files are understood by every FLEX m version However your old applications pre FLEX m v3 0 will not be able to use the new license file See also Section 3 2 License File Format Frequently Asked Questions D 3 D 3 1 D 3 2 D 3 3 D 3 4 D 3 5 Using FLEXIm Using FLEX m Does FLEX m work across the Internet Yes A server on the Internet will serve licenses to anyone else on the Internet This can be limited with the INTERNET attribute on the FEATURE line which limits access to a range of Internet addresses You can also use the INCLUDE and EXCLUDE options in the daemon option file to allow or deny access to clients running on a range of Internet addresses Does FLEX m work with Internet firewalls Many firewalls require that port numbers be specified to the firewall FLEX m v5 lmgrd supports this If my client dies does the server free the license Yes unless the client s whole system crashes or becomes disconnected from the network Assuming communications is TCP the license is automatically freed immediately If communications are UDP then the license is freed after the UDP timeout which is set by each vendor but defaults to 45 minutes UDP communications is normally only set by the end user so TCP should be assumed If the whole system crashes then the license is not freed and you should use 1mremove to free the license What happens when the license server dies FLE
111. though PCs will allow you to enter them and they will not work with DNS D 3 13 We re using FLEX m over a wide area network What can we do D 4 D 4 1 Note D 4 2 103 to improve performance FLEX m network traffic should be minimized With the most common uses of FLEXIm traffic is negligible In particular checkout checkin and heartbeats use very little networking traffic There are two items however which can send considerably more data and should be avoided or used sparingly e Imstat a should be used sparingly lmstat a should not be used more than say once every 15 minutes and should be particularly avoided when there s a lot of features or concurrent users and therefore a lot of data to transmit say more than 20 concurrent users or features e Prior to FLEX m v5 the port host mode of the LM_LICENSE_FILE environment variable should be avoided especially when the license file has many features or there are a lot of license files included in LM_LICENSE_FILE The license file information is sent via the network and can place a heavy load Failures due to port host will generate the error LM_SERVNOREADLIC 61 Windows Questions What PC Platforms are supported FLEXI m v7 supports Windows 95 98 2000 and NT Networking is required on all 32 bit versions Will the Server run on Windows 95 Yes Frequently Asked Questions FLEX m Error Codes E 1 Error Mess
112. u For example 1 VERSION 2 0 You can specify a feature by any of the following fields VERSION HOSTID EXPDATE KEY VENDOR_STRING ISSUER NOTICE dist_info user_info asset_info In FLEX m v5 11 or later you can use a package name in place of a feature name and the option will apply to the whole package FLEXIm End Users Manual April 2000 56 Customizing the Options File 6 2 1 EXCLUDE EXCLUDE feature type type_nam Excludes a user host display or group from the list of who is allowed to use the feature Excluded users will not be allowed to use the feature feature type type_name Name of the feature being affected One of USER HOST DISPLAY PROJECT GROUP HOST_GROUP or INTERNET see Section 6 2 3 GROUP and Section 6 2 4 HOST_GROUP Name of the user or group to exclude To exclude the user hank from the list of users able to use feature f1 EXCLUDE f1 US ER hank 6 2 2 EXCLUDEALL EXCLUDEALL type type_name Excludes a user host display or group from the list of who is allowed to use all features served by this vendor daemon type type_name To exclude any user this vendor daemon One of USER HOST DISPLAY PROJECT GROUP HOST_GROUP or INTERNET see Section 6 2 3 GROUP and Section 6 2 4 HOST_GROUP Name of the user or group to exclude on the machine c
113. ultiple option lines in your options file For example in pre v4 0 FLEX m to exclude all users logged in on the hosts fred and barney from using a feature called f1 add these lines to your options file EXCLUDE fl USER fred EXCLUDE f1 USER barney The Options File Note 6 4 EXCLUDE Example With a FLEX m v4 vendor daemon you can use HOST_GROUP to allow deny or reserve licenses for multiple hosts For example to exclude all users logged in on the hosts fred and barney from using a feature called f1 add these lines to your options file HOST_GROUP writers fred barney EXCLUDE f1 HOST_GROUP writers See Section 6 2 3 GROUP and Section 6 2 4 HOST_GROUP for more information about defining groups EXCLUDE Example First Define the group painters GROUP painters picasso mondrian klee EXCLUDE spell GROUP painters EXCLUDE spell USER bob EXCLUDE spell INTERNET 123 123 123 This options file would 99 66 Prevent the users picasso mondrian and klee from using the feature spell on any machine on the network Prevent the user bob from using the feature spell on any machine on the network Prevent any user logged into a host with an IP address in the range 123 123 123 0 through 123 123 123 255 from using the feature spell Allow any other user as long as t
114. ure database corrupted in daemon 37 Duplicate selection mismatch for this feature 38 User host on EXCLUDE list for feature 39 User host not on INCLUDE list for feature 40 Cannot locate dynamic memory 41 Feature was never checked out 42 Invalid parameter 43 No FLEXIm key data supplied in initializing call 44 Invalid FLEXIm key data supplied 45 FLEXIm function not available in this version 46 Obsolete 47 Clock setting check not available in daemon 48 FLEXIm platform not enabled 49 Date invalid for binary format 50 FLEXIm key data has expired 51 FLEXIm not initialized 107 FLEXIm Error Codes Error Code Descriptions FLEXIm vendor daemon did not respond within timeout interval Checkout request rejected by vendor defined checkout filter No FEATURESET line in license file Incorrect FEATURESET line in license file Cannot compute FEATURESET data from license file socket call failed Obsolete Message checksum failure Server message checksum failure Cannot read license file data from server Network software TCP IP not available You are not a license administrator Imremove request before the minimum Imremove interval Unknown VENDORCODE struct type passed to Im_init FLEXIm include file library version mismatch Obsolete Obsolete Obsolete Obsolete Invalid TZ environment variable Old VENDORCODE three word struct type passed t
115. ve more sockets The number of sockets available for Windows 95 clients is about 60 In general NT is preferred for server systems where there is no such limit and the operating system is better designed for server processes CPU Time For small numbers of clients the license servers use very little CPU time The servers might have only a few seconds of CPU time after many days For a large number of clients who are each exchanging heartbeat messages with the server or for high checkout checkin activity levels hundreds per second the amount of CPU time consumed by the server may start to become significant although even here CPU usage is normally not high In this case you may need to ensure that the server machine you select will have enough CPU cycles to spare GLOBEtrotter Software has rarely encountered a situation where CPU cycles were an issue Disk Space The only output files created by the license servers are the debug and report log files The report log files are used to generate accurate usage reports by SAMreport These log files contain one line for each checkout and one line for each checkin If you have a lot of license activity these log files will grow very large You will need to consider where to put these files and how often to delete or prune them The license administrator can opt not to log messages to the debug log file if disk space is at a premium See Section 6 2 10 NOLOG and Section 6 2 11
116. would require a license that can be freed with TIMEOUT With v5 licenses are freed when they time out 6 2 14 TIMEOUTALL 6 3 6 3 1 63 v5 11 vendor daemon only TIMEOUTALL seconds Same as TIMEOUT but applies to all features Understanding Options Files The following information gives an overview of the syntax of a complete options file and some samples intended to illustrate ways to effectively control access to your licenses How the Vendor Daemon Uses the Options File When the vendor daemon is started by 1mgrd the vendor daemon reads its options file There can only be one options file per vendor daemon and each vendor daemon needs its own options file Lmreread does not cause the vendor daemon to reread its options file for any changes in the options file to take effect 1mgrd must be stopped and restarted The Options File 6 3 2 6 3 3 Understanding Options Files Rules of Precedence in Options Files Before you can use options to utilize licenses effectively you must understand the options file precedence INCLUDE and EXCLUDE statements can be combined in the same options file and control access to the same features When doing so keep in mind the following e If there is only an EXCLUDE list everyone who is not on the list will be allowed to use the feature e If there is only an INCLUDE list only those users on the list will be allowed to use the feature e If neither list exists everyone is
117. xample above looks as follows in decimal format xyzd 1 01761 55296 37046 04544 00017 06551 18072 57346 18754 136 xyzd 1 01761 55296 37046 08896 00034 235 xyzd 1 00481 55296 17590 2 FLEXIm End Users Manual April 2000 38 License File Order 3 6 39 A simple demo license in readable format FEATURE f1 xyzd 1 00 1 jan 1999 0 keyl HOSTID DEMO converted to decimal xyzd 1 00737 55296 1825 Note that by default Iminstall converts to v6 format It can convert to a format compatible with older versions by using lminstall overfmt 2 or 3 4 5 depending on the FLEX m version License File Order In some cases the ordering of lines in a license file can be crucial Version 7 vendor daemons and clients automatically internally sort the lines so that in most cases the optimal result is achieved For earlier versions of FLEX m note the following suggestions which are all based on the fact the checkouts are attempted on lines in the order they appear in the license file 1 Place FEATURE lines before INCREMENT lines for the same feature The rule regarding FEATURE lines is that only the first counted FEATURE line is observed by the license server and that if there is a FEATURE line and INCREMENT lines the FEATURE line must appear first A few large older FLEX m licensed companies have FEATURE lines that behave identically to INCREMENT lines and only the rules applying to INCREMENT apply to them 2 W

FLEXlm End Users Manual

Contents

Download Pdf Manuals

Related Search

Related Contents