Home

FLEXlm End User Manual

1. if it says can t connect it s a free port D 3 5 How do you tell if a port is already in use D 3 6 Does FLEX m require root permissions No There is no part of FLEX m Imgrd vendor daemon or application that requires root permissions In fact it is strongly recommended that you do not run the license server Imgrd as root since root processes can introduce security risks If Imgrd 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 path lmgrd c path license dat l path log where username is a non privileged user and path is the correct paths to Imgrd license dat and debug log file You will have to ensure that the vendor daemons listed in path to license license dat have execute permissions for username The paths to all the vendor daemons in the license file are listed on each DAEMON line D 3 7 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 mgrd be run as a non privileged user not root If you are starting Imgrd from a boot script we recommend that you use su username c umask 022 Imgrd to run mgrd as a non privileged user D 3 8 Does FLEXI m licensing impose a heavy load on the network No but partly
2. FLEX m End User Manual FLEX m version 7 0 GLOBEtotter Software Inc Campbell Califomia 95008 Voice 408 370 2800 Fax 408 370 2884 email info globes com web http www globetrottercom November 1999 FLEXIm End User Manual November 1999 Copyright 1994 1999 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 Trademarks GLOBErrotter and FLEX m are registered trademarks of Globetrotter Software Inc Electronic Commerce for Software Electronic Licensing FLEXadmin FLEXcrypt FLEXexpress FLEXid FLEXmeter FLEXwrap GLOBEforms GLOBEhelp GLOBEsupport GLOBEtrrack Globetrotter Software No Excuses Licensing Policy in the License 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 subpara
3. 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 file 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 checkout 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 On older SCO systems the default number of sockets may be set fairly low if you choos
4. For counted licenses no matter which option you choose you must first install Jmgrd and the vendor daemon With a FLEX m v6 vendor daemon and Imgrd 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 lic in that directory are used Note You can only start mgrd on the server node specified in the license file Note If you are running redundant servers you should have separate copies of the license 3 1 1 17 file as well as the binaries for mgrd 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 Start Up If any licenses in the license file are counted count gt 0 then the license server must be started before the product can be used UNIX To start the license manager daemon mgrd execute a command similar to the following If you are running in the C shell o Imgrd_path c license_file_path gt amp log_path amp If you are using either the Korn or Bourne shell nohup Imgrd_path c license_file_path gt log_path 2 gt amp 1 amp On Unix edit the appropriate boot script which may be etc rc boot etc rce local etc rc2 d Sxxx sbin rc2 d Sxxxx etc Remember that these scripts are run in bin sh so do not us
5. and james GROUP Hackers bob howard james Note 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 re define the GROUP Note In FLEX m v4 0 or later USER_GROUP is an alias for GROUP 6 2 4 HOST GROUP HOST_GROUP groupname hostnamelist Defines a group of hosts for use in INCLUDE INCLUDEALL EXCLUDE EXCLUDEALL and RESERVE option lines e groupname name of the group being defined e hostnamelist list of host names in that group 6 2 5 INCLUDE INCLUDE featurename type name 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 e featurename name of the feature being affected e 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 on page 45 e name name of the user or group to include To include user bob in the list of users able to use feature f1 INCLUDE f1 USER bob Note 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 6 2 6 INCLUDEALL INCLUDEALL type name Includes a user host display or group i
6. or the license administrator or a script he set up could have deleted the file Solution Check to see if there is more than one copy of the daemon running On Unix use a command like ps aux grep vendorname to search for it Check for more than one mgrd running as well since it will restart your vendor daemon when it is killed If more than one mgrd is running kill them all using the kil 1 command not kill 9 on Unix or the Control Panel Services dialog 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 Imgrd 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 it does not delete zero length files 69 FLEXIm End User Manual November 1999 http www globetrotter com FLEXIm 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 FLEXIm environment variables are set in 2 different ways e The normal set or setenv commands or the System Control Panel on Windows NT The registry Windows or in HOME flexlmre Unix which functions like the registry for FLEXIm on Unix Version 6 required and HOME flexlmrc requires version 7 C 1 1_ Reg
7. resources required by the servers multiple servers quorums and redundant servers The Options File Creating and editing the options file License Administration Tools Managing FLEX m using GLOBEtrotter supplied utilities In addition you can refer to Appendix B Troubleshooting Guide on page 64 which contains a list of common problems and their solutions and Appendix D License File Questions on page 72 End User If you are an end user read these chapters This chapter Explains Welcome to FLEXIm FLEX m basics license and vendor daemons the license file configuring FLEX m the license request process The License File The license file format setting the path at start up different types of licensing policies In addition you can refer to Appendix B General Debugging Hints on page 64 which contains a list of common problems and their solutions Related Documents from GLOBEt rotter Software FLEXadmin FLEXwrap Users Guide describes both the FLEXadmin license administration tools for managing FLEX m enabled applications and FLEXwrap for administrators who wish to provide license management for applications shipped without embedded license management FLEXIm Programmers Guide and FLEXIm Reference Manual for programmers responsible for incorporating FLEX m into their products FLEXIm End User Manual November 1999 http www globetrotter com Introduction and Overview This cha
8. usage by project as defined by what LM_PROJECT was set to when the application was run 6 2 12 RESERVE RESERVE numlic featurename type name Reserves licenses for a specific user e numlic number of licenses to reserve e featurename name of feature to reserve e 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 on page 45 e name name of the user or group to reserve licenses for To reserve one license of feature f1 for user mel RESERVE 1 1 USER mel Note 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 FLEXadmin if the license is not actually in use 47 FLEXIm End User Manual November 1999 http www globetrotter com TIMEOUTALL 6 6 2 13 TIMEOUT TIMEOUT featurename seconds Sets the time after which an inactive license is reclaimed by the vendor daemon e featurename name of the feature e 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 n
9. 29 overview 11 PACKAGE line 26 rereading after an update 58 SERVER lines 20 33 USE_SERVER 22 with multiple servers 16 17 license file list 34 license request process overview of 12 license server how to choose 36 LINGER 46 LM_LICENSE_FILE 39 License file list 34 syntax 19 used to reference multiple files 11 LM_PROJECT 47 71 Imcksum 53 Imdiag 53 67 debugging connectivity problems 67 troubleshooting Imdiag 53 troubleshooting with 64 Imdown 54 Imgrd 16 and redundant servers 17 combining license files 72 compatability between versions 33 debug log file 37 84 end user options file 48 firewall support 73 hostnames 75 license file list support 32 94 Imdown 54 Imreread 59 multiple or single Imgrd processes 33 NT service 18 overview 16 PORT 22 root perms on Unix 74 running as root 74 shutting down with Imdown 54 starting automatically at boot time 14 syntax 55 tcp ports 74 Unix startup script 17 usage 55 v6 supports license path 17 VENDOR DAEMON line usage 21 version compatibility 88 Windows 95 18 77 Imhostid 24 56 Iminstall 57 Imremove 57 Imreread 58 Imstat 59 Imstat a troubleshooting flexlm with 64 Imswitchr 59 LMTOOLS 60 Imver 60 log file managing 37 M MAX 46 MAX_OVERDRAFT 46 Multiple License Files 32 95 FLEXIm End User Manual November 1999 N network FLEXIm load 74 network bandwidth and FLEXIm 38 NFS 74 NIS 75 node locking mixed with floating 29 NOLOG 46 NOTICE 24 O Options
10. 3 5 3 51 and 4 0 on Intel Mips and Alpha Netware 3 12 and 4 X OS 2 3 0 Networking is required on all 32 bit versions What is WINSOCKX DLL Winsockx dll is a DLL provided by GLOBErtrotter Software that is used by 16 bit applications to interface between FLEX m and other networking software provided by networking ISV s It allows node locked applications to not require networking 76 D Frequently Asked Questions software It also interfaces between winsock dll for TCP IP and the Novell DLLs that provide IPX SPX on 16 bit operating systems D 4 3 Why do I need to include NWlink IPX SPX NT and Win 95 This is necessary for either obtaining the Ethernet card address or to provide connectivity with a Netware License server Version 6 1 applications will not require this on NT D 4 4 Will the Server run on Windows 95 Yes If available NT systems are preferred since it can be run as an NT service A version 7 Imgrd will run the background on Windows 95 77 FLEXIm End User Manual November 1999 http www globetrotter com FLEX m Error Codes E 1 Error Message Format FLEX m error messages presented by applications have the following components FLEXIm Error Number a negative number starting with 1 FLEXIm Error Text short sentence lt 80 characters summarizing problem FLEXIm Error Explanation optional short paragraph 3 5 lines explaining problem and possible solutions or workarounds FLEXIm Minor
11. 57 7 8 Imreread 58 7 9 Imstat 59 7 10 Imswitchr 59 7 11 Imver 60 7 12 License Administration Toolk LMTOOLS for Windows 60 Appendix A Hostids for FLEX m Supported Machines 62 A lHostidTable 62 Appendix B Troubleshooting Guide 64 B 1General Debugging Hints 64 B 2FLEXLM_DIAGNOSTICS 65 B 3FLEX m Troubleshooting List 66 B 4Other Client Problems 68 B 5Other Server Problems 68 Appendix C FLEXIm environment variables 70 C 1How to set environment variables 70 3 2 Environment variables 70 Appendix D Frequently Asked Questions 72 D 1License File Questions 72 D 2FLEXI mVersions 72 D 3UsingFLEXIm 73 D 4WindowsQuestions 76 Appendix E FLEXIm Error Codes 78 E 1Error Message Format 78 E 2Error Code Descriptions 79 Appendix F The Debug Log File 84 F 1InformationalMessages 84 F 2Configuration Problem Messages 85 F 3Daemon Software Error Messages 86 Appendix G FLEX m Versions 88 G 1Version compatibility and components 88 7 FLEXIm End User Manual November 1999 Welcome to FLEX m FLEXLM is the de facto standard network license manager used by over 1500 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
12. Error Number a positive number starting with 1 These numbers are unique error identifiers and are used by FLEXIm license ISVs for more advanced support assistance Their meaning is not documented System error code optional This is a Unix or Windows OS error code last set by the operating system System error code explanation optional A short sentence lt 80 characters explaining the system error code Other supporting information optional Error messages were improved in v6 FLEXIm error explanation and supporting information are only available in applications using v6 0 These error messages may occur in two formats available with FLEXIm 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 E 1 2 Format 2 long version 6 FLEX1lm error text FLEX1m error explanation Optional Supporting information FLEX1m error lm_errno minor_num sys_errno system error text Example 78 FLEX Im Error Codes E 2 79 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 EL Server name localhost License path localhost license d
13. File Example 49 Options file overview 14 options file and Imreread 59 required for HOST_BASED and USER_BASED 24 specifying on DAEMON line 21 syntax and description 42 usage examples 48 OPTIONS SUITE 27 OVERDRAFT 24 P PACKAGE syntax 26 PROJECT 44 R Redundant Servers Overview 38 redundant servers and SERVER line 20 keep separate license file copies 17 selecting server nodes 39 96 remote disks guidelines for using 38 REPORTLOG 37 47 RESERVE 47 S SERVER lines combining license files 33 server nodes deciding number of 39 servers disk space used 37 sockets used 36 SN 25 sockets differences under SCO 36 number used by license server 36 START 25 subnets 75 SUITE 27 SUPERSEDE 25 T TIMEOUT 48 TIMEOUTALL 48 Troubleshooting 66 guide 64 troubleshooting FLEXLM_DIAGNOSTICS 65 Imdiag 67 U Unix and Imgrd 74 UPGRADE 27 USE_SERVER 22 USER 97 FLEXIm End User Manual November 1999 End user options file 44 USER_BASED 25 user_info 25 V VENDOR 18 vendor daemon and redundant servers 17 DAEMON or VENDOR license line 21 debug log file 84 FEATURE line 23 Imreread 58 Imswitchr 60 memory usage 38 netware support 16 options file 43 restarting 55 sockets 36 TIMEOUT 48 uncounted licenses 41 VENDOR_LICENSE_FILE 71 version compatibility 33 vendor_info 25 VENDOR_STRING 25 W wide area network performance 76 Windows 95 and license server 77 Windows Questions 76 WINSOCKX DLL 76 X X Displ
14. Imcksum will print a line by line checksum for the file as well as an overall file checksum 1mcksum takes the k switch to force the encryption key checksum to be case sensitive 1lmcksum 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 daemon pathname and options file names are not checksummed In addition Imcksum will treat non case sensitive fields correctly in general 1mcksum is not case sensitive lmcksum takes an optional daemon name if specified only license file lines for the selected daemon are used to compute the checksums For FEATURE lines that contain ck nnn Imcksum prints simply OK or BAD Usage is imcksum c license_file where is the c license_file path to the file to checksum By default Imcksum uses license dat in the current directory unlike other mutil commands Example output is imcksum Copyright C 1989 1997 GLOBEtrotter Software Inc lmcksum using license file usr local flexlm licenses license dat 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 0O 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 FLEXIm End User Manual Novemb
15. Imgrd on page 55 for details about securing access to lmreread To stop and restart a single vendor daemon use 1mdown vendor name then use lmreread vendor name which restarts the vendor daemon Note lIf you use the c option the license file specified will be read by 1mreread not by mgrd lmgrd rereads the file it read originally Also Lmreread cannot be used to change server node names or port numbers Note Vendor daemons will not reread their option files as a result of lmreread 7 9 7 10 59 Imstat The lmstat utility helps you monitor the status of all network licensing activities Usage is Imstat a A c license_file f feature i feature S vendor s hostname t value where is a Display all information A List all active licenses c license_file Use the license file named f feature_name List users of feature_name i feature_name Print information about the named feature or all features if no feature_name is given 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 hostname Display status of clients running on hostname t value Set lmstat timeout to value Imswitchr The lmswitchr utility switches the report writer REPORTLOG log file It will also start anew REPORTLOG file if one does not a
16. 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 2 4 Imgrd will work successfully with a 2 4b vendor daemon See also Appendix G Version compatibility and components on page 88 I 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 FLEX m ve received a new license file and the format is different from the old one had from the same vendor Why Are they compatible As of v3 0 FLEX m has an optional new format for license files FLEX m products always understand older versions 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 on page 19 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 requi
17. The server must be restarted for options file changes to take effect 102 105Unused 106 License server out of network connections The vendor daemon can t handle any more users See the Imgrd debug log for further information 82 FLEX Im Error Codes 107 109Unused 110 Dongle not attached or can t read dongle Either the hardware dongle is unattached or the necessary software drivers 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 These drivers are available at www globetrotter com or from your software vendor 83 FLEXIm End User Manual November 1999 http www globetrotter com Appendix F The Debug Log File The daemons all generate debug log files in the following format hh mm DAEMON NAME message where is the hh mm Time that the message was logged DAEMON NAME Either Imgrd 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 should not be used for usage reporting F 1 Informational Messages Connected to node This daem
18. Windows ethernet Imutil lmhostid 0800200055327 Disk serial DIR C look for Volume DISK_SERIAL_NUM number Serial Number is and 3e2e17fd remove Dongle lmhostid flexid FLEXID 7 b28520b9 parallel port hardware key Pentium I lmhostid cpu 9077 5D77 0002 57C8 CPU V7 0d Imhostid cpu96 95D2 1D3D 96 bit only Use The 32 bit version is the 95D2 1D3D 32 bit BIOS Setup Jast 9 characters from the to enable full id 63 FLEXIm End User Manual November 1999 http www globetrotter com 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 mgrd 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 lmstat a and 1lmdiag to see if that program has the same problem 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 or 2 2 gives more informa
19. also provides the FLEXadmin asset management tool for more advanced license server control and reporting Please contact GLOBEtrotter Software info globes com or www globetrotter com for more information about FLEXadmin 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 FLEXIm versions 1 0 through 7 0 1 2 Howto Use This Manual This manual is written for two different audiences the license administrator and the end user 1 2 1 License Administrator If you are a license administrator read these chapters This chapter Welcome to FLEX m The License File Multiple License Files 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 licensing policies Using license files from independent software vendors Welcome to FLEXIm 1 2 2 1 3 This chapter Explains Selecting Server Nodes Selecting which machines will run the license servers
20. architecture Numeric 32 bit hostids are normally 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 system you can convert to hex with the following script echo 2005771344 160 p dc 778DA450 A 1 Hostid Table Hardware Hostid Type this command onthe Example Platform license server AIX RS 6000 32 bit hostid uname m returns 02765131 PPC 000276513100 then remove last 2 digits and use remaining last 8 digits DEC Alpha ethernet netstat i 080020005532 address 62 Hostids for FLEX m Supported Machines Hardware Hostid Type this command onthe Example Platform license server HP 32 bit hostid uname i andconvertto 778DA450 or hex or prepend with 200577 1344 ethernet lanscan station address 0000F0050185 address without leading 0x Linux ethernet sbin ifconfigeth0O 00400516E525 address and remove colons from HWaddr 00 40 05 16 E5 25 SCO Hostid String uname x Serial is ID_STRING SCO00354 SCO00354 then prefix with ID_STRING SGI 32 bit hostid etc sysinfo s 69064C3C or convert to hex or prefix 1762020412 SUN 32 bit hostid hostid 170a3472
21. available this the recommended hostid type See A 1 Hostids for FLEXIm Supported Machines 56 License Administration Tools 7 6 7 7 57 Iminstall Introduced in v6 0 Iminstall is designed primarily for typing in decimal format licenses to generate a readable format license file Usage is lminstall i infile o outfile overfmt 2 3 4 5 5 1 6 odecimal Normally Iminstall 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 lic 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 66 To finish entering type q on a line by itself or enter 2 blank lines If infile is a dash it takes input from stdin When i is used default output is stdout otherwise if o is not specified Iminstall prompts the user for an output file name LMINSTALL As A CONVERSION TOOL Iminstall 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 infile o outfile odecimal To convert to FLEX m Version 2 format o
22. by the ttyname function call or the tty command and is usually something like dev ttyp4 However the application developer can change this default to the X Display A paper is available on this topic to FLEX m developers from GLOBEtrotter Software We re using FLEX m over a wide area network What can we do 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 Imstat 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 FLEX m supports Windows 3 1 Windows for Workgroup 3 11 Windows 95 98 Windows NT
23. checkout or checkin is typically satisfied with less than 1 Kbyte of data transferred This means that FLEX m licensing can be effectively run over slow networks such as dial up SLIP lines for small numbers 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 2 files for 2 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 filesystem local to the application See Section 3 1 Specifying Location of the License File on page 16 5 2 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 mgrd 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
24. daemon prints an error concerning Parameter mismatch in the log file and refuses the license 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 license server log file fora comm version mismatch warning message this indicates that someone is running an older client than the license server daemon Imgrd Run only the new version of the application or only the old version Other Server Problems Symptom Cause Solution When I run the vendor daemon on my VMS system I get the error message socket bind permission denied 13 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 SYSNAM privilege Run the daemon in a process with the SYSNAM privilege set 68 BY Troubleshooting Guide Symptom When I start up Imgrd it says execl failed on my vendor daemon Cause 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
25. daemon might not work properly with an older mgrd 2 A newer vendor daemon or mgrd 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 mgrd and the newest version of each vendor daemon 2 Use the newest FLEX m utilities FLEXIm End User Manual November 1999 http www globetrotter com 4 1 3 4 2 Using LM_LICENSE_FILE License File List 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 e Section G 1 Version compatibility and components on page 88 Using Separate License Files on the Same Server Node You must run a separate copy of mgrd for each license file When you run multiple copies of Imgrd 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 mgrd when you start it up for a particular license file This can be done by using an explicit path to Imgrd When running client programs such as a licensed applicati
26. feature this limit applies to e type USER HOST DISPLAY PROJECT GROUP HOST_GROUP or INTERNET e name name of the user or group to limit 6 2 9 MAX_OVERDRAFT MAX_OVERDRAFT featurename numlic Limits usage below the OVERDRAFT allowed by the license file 6 2 10 NOLOG NOLOG what Turns off logging of specific events by the FLEX m daemons e what what to turn off one of IN OUT DENIED or QUEUED To turn off logging of checkins NOLOG IN 46 6 The Options File To turn off logging of checkouts and queued requests two separate NOLOG lines are required NOLOG DENIED NOLOG QUEUED Note License administrators might use this option to reduce the size of the mgrd or debug log file 6 2 11 REPORTLOG REPORTLOG filename REPORTLOG specifies the file which will contain the report writer log for this vendor daemon If filename begins with a character the file will be opened for append otherwise the file will be overwritten each time the daemon is started F LEXadmin a separate product available from Globetrotter can be used to read and report on REPORTLOG files Note This file is only useful with the FLEXadmin license administration utility LM_PROJECT The FLEXadmin 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 FLEXadmin can then group
27. flexlim license dat Windows Windows NT OS 2 SYSS COMMON SYSMGR flexlm dat VMS SYS SYSTEM flexlm license dat Netware 11 FLEXIm End User Manual November 1999 http www globetrotter com 2 1 3 Introduction to FLEXIm 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_FILE This is because setting LM_LICENSE_FILE removes the default location from the license file list It s strongly recommended that you keep a copy or link on Unix 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 on page 16 See also Appendix C How to set environment variables on page 70 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 LMGRxxx DLL 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 a
28. from the client to the FLEXIm End User Manual November 1999 http www globetrotter com B 4 B 5 Other Client Problems Be 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 lt hostname gt lt portnum gt where hostname and portnum are the same as on the SERVER line in your license file 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 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 on page 16 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
29. 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 3 2 4 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 string 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 is counted independently from others with the same feature name called a license pool 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 addit
30. the following syntax imgrd c license_file_path c license_file_path full pathname to the license file Otherwise LM_LICENSE_FILE or the default location are used Note On VMS and Netware systems there is no Imgrd and the vendor daemon is run directly 3 1 Specifying Location of the License File Most software vendor 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 available 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 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 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 16 The License File
31. the server machine is up but when the files are on a different machine then the loss of either the license server machine or the file server machine will cause the licenses to be unavailable 5 3 Redundant Servers FLEXI m 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 the system is functional and hands out its total complement of licenses Two out of three license servers is referred to as a quorum 38 Selecting Server Nodes 5 3 1 5 3 2 39 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 e Section 4 2 Using LM_LICENSE_FILE License File List on page 34 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 GLOBErtrotter 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 n
32. 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 1exnnn 1log where nnn is the application s process ID If the application is v5 0 the output file is called flex_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 Level 2 Content If FLEXLM_DIAGNOSTICS is set to 2 then in addition to 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 lm_checkout f1 1 0 1 0x0 Ox4000 Note that the error message actually contains 2 separate problems which both occurred during
33. 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 FEATURESET daemon_name key FLEXIm End User Manual November 1999 http www globetrotter com License File Format Note Nothing in a FEATURESET line can be edited Use the FEATURESET line exactly as 3 2 6 it comes from your vendor where is the daemon_name name of the vendor daemon key 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 Example FEATURESET sampled 12345678 where is the sampled name of the vendor daemon 12345678 key generated by the 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 licenses will enable the PACKAGE Example PACKAGE pkg_name vendor pkg_version pkg_
34. 15 Error Code Descriptions Cannot connect to license server The server Imgrd 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 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 Obsolete Obsolete Cannot find ethernet device Cannot read license file Feature start date is in the future No such attribute Bad encryption handshake with daemon Clock difference too large between client and server In the queue for this feature Feature database corrupted in daemon Duplicate selection mismatch for this feature User host on EXCLUDE list for feature User host not on INCLUDE list for feature Cannot allocate dynamic memory Feature was never checked out Invalid parameter No FLEXIm key data supplied in initializing call Invalid FLEXIm key data supplied FLEXIm function not available in this version Obsolete 80 FLEX Im Error Codes 81 Clock setting check not available in daemon FLEXIm platform not enabled Date inv
35. 999 http www globetrotter com Version compatibility and components 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 hostname e Improved REPORTLOG format e Server upon startup notifies of licenses that will expire within 2 weeks e Improved end user options file functionality e New FEATURE attributes SUPERSEDE ISSUED USER_BASED HOST_BASED SN V5 11 February 1997 e SUPERSEDE lists PLATFORMS license attribute e new end user options MAX TIMEOUTALL CPU_USAGE_INTERVAL CPU_USAGE_DELTA 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 lic automatically used e License files require no editin
36. ATURE line are 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 Iminstall command which is part of Imutil The Iminstall 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 floating example above looks as follows in decimal format xyzd f 1 01761 55296 37046 04544 00017 06551 18072 57346 18754 136 xyzd 1 01761 55296 37046 08896 00034 235 xyzd f 1 00481 55296 17590 2 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 Iminstall 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 FLEXIm 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 FEATU
37. 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 e Enhanced vendor customization routines e Enhanced End User Options file e Added new hostid types USER HOSTNAME and DISPLAY e Added port host to locate license file down loads license 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 89 FLEXIm End User Manual November 1
38. RE 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 Where multiple counted FEATURE lines exist for the same feature make sure the desired FEATURE line appears first because the others are 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 USE_SERVER The 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 30 The License File 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 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 31 FLEXIm End User Manual November 1999 http www globetrotter com Multiple License Files Since more than 1500 vendors have chosen FLEX m as their license manager chances are good that you will have to admini
39. SERVE 3 compile HOST mainline EXCLUDE compile USER lori NOLOG 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 hostname 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 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 compile 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 flexlm 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 FLEXIm End User Manual November 1999 http www globetrotter com Understanding Options Files 6 6 4 4 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 a GROUP For example to exclude bob howard and james from using the feature called toothbrush we could create the following options file EXCLUDE toothbrush USER bo
40. Section 7 4 Imgrd on page 55 for details about securing access to lmremove The h variation uses the serverhost port and license handle as reported by lmstat a Consider this example lmstat a output joe cloud7 dev ttyp5 v1 000 cloud9 7654 102 start Fri 10 29 18 40 In this example the serverhost 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 lmremove f1 joe cloud7 dev ttyp5 When removing by handle if licenses are grouped as duplicates all duplicate licenses will also be removed Iimreread 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 lmreread c license_file vendor name all where is c license_file Use the specified license file 58 License Administration Tools vendor name Only this one vendor daemon should reread the license file Imegrd will restart the vendor daemon if necessary Requires v6 Imreread and Imgrd the vendor daemon can be any version all If more than one Imgrd is specified instructs all Imgrds to reread v7 The license administrator may want to protect the execution of 1mreread See the p and x options in Section 7 4
41. XCLUDE 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 50 6 The Options File 6 4 6 51 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 they 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 INCLUDE Example INCLUDE paint USER picasso INCLUDE paint USER mondrain INCLUDE paint HOST bigbrush This options file would Allow the user picasso to use the feature paint on any machine on the network Allow the user mondrain to use the feature paint on any machine on the network Allow any u
42. _FILE lfpath1 lfpath2 lfpathN 34 Multiple License Files Note Use a colon to separate the license file names on Unix on Windows and 35 my man Windows NT use a semicolon and on VMS use a space where is the lfpath1 path to the first license file lfpath2 path to the second license file lfpathN path to the last Nth license file 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 lfpath1 is unreachable the other files listed in LM_LICENSE_FILE allow a user to obtain a license from another server fpath can also be port host using the port number and hostname from the SERVER line in the license file SEE ALSO Section 5 3 2 Redundancy via License File List in LM_LICENSE_FILE on page 39 e Appendix C How to set environment variables on page 70 e Section 3 1 2 Setting the Path with an Environment Variable on page 19 FLEXIm End User Manual November 1999 http www globetrotter com 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
43. aemon name e g GSI_LICENSE_FILE With Imgrd and Imutil Imstat lmdown etc the c option overrides the setting of the LM_LICENSE_FILE environment variable for See Section 4 1 3 Using Separate License Files on the Same Server Node on page 34 for more information about LM_LICENSE_FILE Note Some applications do not recognize the LM_LICENSE_FILE environment variable 3 2 19 See Also Appendix C How to set environment variables on page 70 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 on page 40 for FLEXIm End User Manual November 1999 http www globetrotter com License File Format more information Since FLEX m v6 0 the DAEMON line can be called VENDOR Wherever DAEMON appears VENDOR can be used if the Imgrd and vendor daemon are both gt 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 SERVER line s e pathnames on the DAEMON line s e options file pathnames on DAEMON line s e Optional port numbers on DAEMON line s for firewall support only e USE_SERVER line FLEX m v5 and later only
44. alid for binary format FLEXIm key data has expired FLEXIm not initialized 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 3 word struct type passed to Im_init Local checkout filter rejected request 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 FLEXadmin API functions not available FLEXIm internal error 79 FLEXIm internal error 80 FLEXIm internal error 81 FLEXIm End User Manual November 1999 http www globetrotter com Error Code Descriptions Invalid PACKAGE line in license file FLEXIm version of client newer than server USER_BASED license has no specified users see server log License server d
45. at 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 server 8 Invalid inconsistent license key The license key and data for the feature do no match This usually happens when a license file has been altered 9 Invalid host The hostid of this system does not match the hostid specified in the license file 10 Feature has expired 11 Invalid date format in license file 12 Invalid returned data from license server 13 No SERVER lines in license file 14 Cannot find SERVER hostname in network database The lookup for the hostname 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 hostname FLEXIm End User Manual November 1999 http www globetrotter com
46. ate options listed in Section 6 2 Customizing the Options File on page 43 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 be placed in usr local flexlm options xyz opt Unix C flexlm options xyz opt Windows NT Add the pathname 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 xyz opt 42 6 The Options File would enable the xyzd vendor daemon to look at the specified options file 6 2 43 In FLEXI m v5 or later you can put options 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 and it will automatically be used at server startup Customizing the Options File Below is an overview of the options file syntax See Section 6 4 Understanding Options Files on page 48 for examples and additional information Each line of the file controls one option The options are EXCLUDE EXCLUDEALL GROUP HOST_GROUP INCLUDE INCLUDEALL LINGER MAX MAX_OVERDRAFT NOLOG REPORTLOG RESERVE TIMEOUT TIMEOUTALL deny a user access to a feature deny a user access to all features served by this
47. ature is reserved for either user name Retrying socket bind address in use The license servers try to bind their sockets for approximately 6 minutes if they detect address in use errors Selected EXISTING master node This license daemon has selected an existing master node as the master SERVER shutdown requested A daemon was requested to shut down via a user generated kill command SIGCHLD received Killing child servers A vendor daemon logs this message when a shutdown was requested by the license daemon Configuration Problem Messages hostname Not a valid server host exiting This daemon was run on an invalid hostname hostname Wrong hostid exiting The hostid is wrong for hostname BAD CODE for feature name The specified feature name has a bad license key It was probably typed in wrong or modified by the end user FLEXIm End User Manual November 1999 http www globetrotter com Daemon Software Error Messages 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 ot
48. ay 76 Y year 2000 72 98
49. b EXCLUDE toothbrush USER howard EXCLUDE toothbrush USER james There is an easier way though 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 multiple 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 f1 USER fred EXCLUDE f1 USER barney 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 Note See Section 6 2 3 GROUP and Section 6 2 4 HOST_GROUP on page 45 for more information about defining groups 6 4 5 E
50. by 1mhostid 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 Hostid Table on page 62 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_USER DUP_HOST DUP_DISPLAY so for a user on the same host and display additional uses of a feature do not consume additional licenses Same as hostid above but in the name value pair syntax FLEX m v3 0 and later Hostnames 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 FLEX 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 24 The License File PLATFORMS SN serial_num START dd mmm yyyy SUPERSEDE 7 7 f2 USER_BASED n be denied service when in a temporary overdraft state Usage above the
51. checked out Examples PACKAGE suite xyzd 1 0 3B24B2F508CB697641CC COMPONENTS compl comp2 OPTIONS SUITE FEATURE suite xyzd 1 0 1 jan 0 5 4193E6ABCCCB1A3970B3 This is a typical SUITE example There are 2 features comp and comp2 which are each version 1 0 with 5 non expiring licenses available When comp or comp2 are checked out suite will also be checked out PACKAGE suite xyzd 1 0 2CBF44FCB9C1E825DC5C COMPONENTS c1 1 5 2 e233 034 FEATURE suite xyzd 1 0 1 jan 1999 3 321E78A17EC19AE81A43 SN 123 In this example the component versions override the FEATURE versions and the number of licenses available for any component is the product of the 3 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 EB16C5AE4A4E0F2961F0 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 3 2 7 UPGRADE Lines UPGRADE name daemon fromversion version exp_date lic key string hostid ck nnn 27 FLEXIm End User Manual November 1999 http www globetrotter com 3 3 3 4 3 4 1 Sample License File All the data is the same as for a FEATURE or INCREMENT line with the addition of the fromversion field An UPGRADE line removes up to the number of licenses specified from any old version gt f
52. d to as concurrent usage or network licensing Floating licenses have no hostids on the individual FEATURE lines Floating licenses requires an Jmgrd 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 keyl FEATURE f2 xyzd 1 00 1 jan 99 6 key2 28 The License File 3 4 2 3 4 3 29 FEATURE f3 xyzd 1 00 1 jan 99 1 key3 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 mgrd 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 f1 xyzd 1 000 1 jan 99 0 k
53. des allowing you to make your license available if any two out of the three server nodes is running Redundancy can be achieved with 3 server redundant servers or by using a license file list with any number of servers Note mgrd is not present on VMS or Netware systems 10 Introduction and Overview THE VENDOR DAEMON In FLEX m licenses are granted by running processes unless they re node locked uncounted 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 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 mgrd 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
54. directory It is recommended however that it be installed in a local directory on the license server node If the Imgrd and vendor daemon are gt FLEX m v6 0 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 Imgrd is located If the path is blank then the options and port strings are required if options or port number are specified options_path full pathname of the end user specified options file for this daemon See Chapter 6 The Options File on page 42 FLEXI m does not require an options file The keyword FLEXIm End User Manual November 1999 http www globetrotter com License File Format options requires a v5 vendor daemon If the vendor daemon is FLEX m v6 or later 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 file the vendor daemon will automatically find and use it portnum Vendor daemon port number NOTE This is for firewall support only and is otherwise not recommended This requires a v5 Imgrd Examples v6 0 VENDOR sampled pre v6 0 DAEMON sampled usr local sampled usr local flexlm licenses sampled opt 3 2 3 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
55. e file with any existing license files See Chapter 4 Multiple License Files on page 32 Determine if an options file is desired and if so set it up Determine where to install the FLEX m utility programs such as Imgrd and lmutil 1mstat 1lmdown etc and install them unless the your vendor s installation script does so for you 6 Start Imgrd the license 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 Start Up on page 17 These steps are discussed briefly below with cross references to the appropriate locations for more detail FLEXIm End User Manual November 1999 http www globetrotter com 2 2 2 Getting Started Checklist 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 on page 36 LICENSE SERVERS AND HOSsTIDS You can get the hostid of the server machine by running FLEX m s lmhost id utility on that machine If you don t have 1mhost id you can get the hostid of your machine by using the appropriate command as described in A 1 Hostids for FLEX1m Supported Machines Using the hostid of your server mac
56. e the csh gt amp redirection syntax 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 Imgrd gt home flexlm v5 12 hp700_u9 boot log bin nohup bin su daniel c umask 022 hnome flexlm v5 12 hp700_u9 1mgrd c home flexlm 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 FLEXIm End User Manual November 1999 http www globetrotter com Specifying Location of the License File bin su daniel c echo lmdiag gt gt home flexlm v5 12 hp700_u9 boot log bin su daniel c home flexlm v5 12 hp700_u9 1mdiag n c home flexlm 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 All paths are specified in full since no paths can be assumed at boot time Since no paths are assumed the vendor daemon must be in the same directory as Imgrd or the VENDOR lines must be edited to include the full path to the vendor daemon binary file The su command is used to run Imgrd as a non root user daniel We recommend that Imgrd not be ru
57. e to run a server on such a machine you may need to reconfigure your kernel to have more sockets WINDowsS 95 The number of sockets available for 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 36 Selecting Server Nodes 5 1 2 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 Note GLOBErrotter Software has rarely encountered a situation where CPU cycles were an issue 5 1 3 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 FLEXadmin 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 administrat
58. 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 version 7 applications FLEX m version 2 did not support the line continuation character although this rarely matters since optional attributes weren t support then either Note Everything else is used to compute the license key and should be entered exactly as 3 2 1 supplied by your software vendor All data in the license file is case sensitive unless otherwise indicated In the following sections options modifiable by the license administrator are italicized SERVER Lines The SERVER line specifies the node name and hostid of the license server and the port number of the license manager daemon mgrd 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 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 on page 22 License administrators do not have the 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 on page 36 The format of t
59. ense files would look like e License 1 for chicago SERVER chicago 17007ea8 1700 DAEMON xyzd etc mydaemon FEATURE f1 xyzd 1 000 01 jan 99 5 26C7DD9CD665B8270186 FEATURE f2 xyzd 1 000 01 jan 99 5 0739D2F78CE46C57041D e License 2 for tokyo SERVER tokyo 17007ea8 1700 FLEXIm End User Manual November 1999 http www globetrotter com Counted vs Uncounted Licenses DAEMON xyzd etc mydaemon FEATURE fl xyzd 1 000 01 jan 99 5 16BE40E1DAEEEDA8798D FEATURE f2 xyzd 1 000 0l jan 99 5 6DB6F3E40E61885712DF 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 5 3 3 Comparing Three Server to License File List 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 FEATURE 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 manner If the application supports license queueing all licenses are only que
60. er 1999 http www globetrotter com 7 3 Imdown Usage is imdiag c license_file n feature where is the c license_file 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 Ifno feature is specified 1mdiag will operate on all features in the license file s in your path 1mdiag will first print information about the license then attempt to check out each license If the checkout 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 1mdiag will indicate each port number that is listening and if it is an Jmgrd process 1mdiag 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 Appendix B FLEXLM_DIAGNOSTICS on page 65 Imdown The 1mdown utility allows for the graceful shutdown of all license daemons both Imgrd and all vendor daemons on all nodes Usage is imd
61. ey2 1700ab12 Alternately in FLEX m v5 0 or later these 2 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 If these were the only FEATURE lines in this license file no Jmgrd daemon would be necessary and you should not start one The following license file allows three licenses for feature 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 xyzy FEATURE f1 zyzd 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 SERVER lulu 17001234 1700 DAEMON xyzd C flexlm xyzd exe FEATURE f1 xyzd 1 00 1 jan 1999 0 keyl 17001111 FEATURE f1 xyzd 1 00 1 jan 1999 0 key2 17002222 FEATURE f1 xyzd 1 00 1 jan 1999 2 key3 FLEXIm End User Manual November 1999 http www globetrotter com 3 5 3 6 Decimal Format This configuration requires an mgrd and a vendor daemon because the concurrent usage of the two licenses on the third FE
62. file as described in Section 4 1 3 Using Separate License Files on the Same Server Node on page 34 Note that you are not required to combine compatible license files you always have the option of running separate mgrds and there is virtually no performance or system load penalty for running separate Imgrd 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 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 Im 1 A newer mgrd can be used with an older vendor daemon but a newer vendor
63. g for use at the end user site e Optional path on DAEMON VENDOR line PATH used e Decimal license format with Iminstall 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 90 FLEX Im Versions Default port numbers make SERVER line port number optional Default end user options file path this_host hostname supported on SERVER line VENDOR_LICENSE_FILE supported e g GSI_LICENSE_FILE host supported where default port numbers are used Windows only user prompted for license file or license server name License files are optionally case insensitive Imdown and Imreread accept vendor name argument Iminstall utility START dd mmm yyyy optional license attribute v6 1 June 1998 Performance Improvements v7 0 August 1999 91 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 exe interface for Windows Imgrd when run as command line on Windows runs in background by default Improved 3 server redundancy reliability v7 vendor daemon and Imgrd Imreread and Imdown take all argument to shutdown or reread all Imgrds Support Registry Windows and flexlmre for FLEXIm environment variables Automat
64. ge 42 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 14 Introduction and Overview 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 on page 16 GETTING INFORMATION ABOUT LICENSES To find out who is using a license run 1mst at described in Chapter 7 License Administration Tools on page 52 15 FLEXIm End User Manual November 1999 http www globetrotter com 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 e 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 mgrd using
65. graph c 1 ii of the Rights of Technical Data and Computer Software clause at DFARS 252 227 0713 and FARS2 227 19 and or applicable Federal Acquisition Regulation protecting the commercial ownership rights of independently developed commercial software Printed in the USA November 1999 Chapter 1 Welcome to FLEX m 8 1 1 Versions of FLEX m 8 1 2 Howto Use This Manual 8 1 2 1 License Administrator 8 1 2 2 End User 9 1 3 Related Documents from GLOBErrotter Software 9 Chapter 2 Introduction and Overview 10 2 1 Introduction to FLEX m 10 2 1 1 FLEX m Components 10 2 1 2 The License Request Process 12 2 1 3 Configuring FLEX m 12 2 2 Getting Started Checklist 13 2 2 1 Installing Licensed Software 13 2 2 2 Notes for End Users 14 Chapter 3 The License File 16 3 1 Specifying Location of the License File 16 3 1 1 Starting the license server at system Start Up 17 3 1 2 Setting the Path with an Environment Variable 19 3 2 License File Format 19 3 2 1 SERVER Lines 20 3 2 2 DAEMON or VENDOR Lines 21 3 2 3 USE_SERVER line v5 only 22 3 2 4 FEATURE or INCREMENT Lines 22 3 2 5 FEATURESET Lines 25 3 2 6 PACKAGE Lines 26 3 2 7 UPGRADE Lines 27 3 3 Sample License File 28 3 4 Types of License Files 28 3 4 1 Floating Concurrent Licenses 28 3 4 2 Node Locked Licenses 29 3 4 3 Mixed Node Locked and Floating Licenses 29 3 5 Decimal Format 30 3 6 License file order 30 Chapter 4 Multiple License Files 32 4 1 Overview of Combining Lice
66. 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 lines and other vendor specific data 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 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 Flexlm provides a default location for license files which is used only if no other location is provided by the application or user and this is considered rare The default location is usr local flexlm licenses license dat Unix C
67. he SERVER line is 20 The License File 3 2 2 SERVER nodename id port number where is the nodename or IP address The system hostname String returned by the UNIX hostname or uname n command On NT ipconfig all on Win95 winipcfg all return the hostname If the application uses FLEX m v5 or higher this can be an IP address in nnn nnn nnn nnn format id Usually the string returned by the 1mhost id command This can only be changed by your software supplier port number 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 lt 1024 are privileged port numbers Example SERVER enterprise 0122345 21987 DAEMON or VENDOR Lines The DAEMON line specifies the daemon name and path mgrd uses this line to start the vendor daemons and the vendor daemon reads it to find the options file The format of the DAEMON line is shown below Note Since FLEX m v6 0 the DAEMON line can be called VENDOR VENDOR can be 21 used if the Imgrd and vendor daemon are both at least FLEX m v6 0 DAEMON VENDOR daemon_name daemon_path options options_path port portnum where is the daemon_name name of the vendor daemon used to serve some feature s in the file This name cannot be changed by the administrator daemon_path pathname to the executable for this daemon Generally the license administrator is free to install the daemon in any
68. he enhancements available in the most recent versions However some enhancements require upgraded vendor daemons and yet others require upgraded client applications Given the following components Imgrd e Imutil includes Imstat Imdown etc and lmtools on windows e vendor daemon e license file the rules about compatibility can be summarized as follows version of version of version of version of version of lmutil must be gt lmgrd which must be gt vendor daemon which must be gt client application which must be gt license file format Except for the license file you can use Imver to discover the version of all these components For the vendor daemon Imgrd Imutil you can also you v argument to print the version G 1 1 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 checkout determine the version of the license for that feature Version 2 gt Version 3 gt Version 4 gt Version 5 gt Version 6 blank quotes or a quoted string at the end of the FEATURE line INCREMENT or UPGRADE lines OVERDRAFT DUP_GROUP INTERNET or PACKAGE appear SUPERSEDE ISSUED USER_BASED HOST_BASED or SN appear START appears 88 FLEX Im Versions V1 0 1988 First FLEX m Release containing all the basic
69. he 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 Imhostid 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 Connection Problems Symptom The application program or lmstat can t connect to the server to check Cause Solution 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 hostname in the license file is not recognized by the system 5 the network between the client 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 mgrd without the b command line option 7 TCP is not running on your machine The Imdiag utility is designed primarily to debug this problem so first try Imdiag 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
70. her daemon that is running via a ps command and kill it with kill 9 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 Unknown host hostname The hostname 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 file Since there are no vendor daemons to start there is nothing to do NO DAEMON line for name A vendor daemon logs this error if it cannot find its own DAEMON name in the license file F 3 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 86 The Debug Log File 87 FLEXIm End User Manual November 1999 http www globetrotter com FLEX m Versions G 1 Version compatibility and components In general always use the latest Imgrd and Imutil Imtools exe which are available from www globetrotter com and you ll automatically enjoy many of t
71. hines your vendor will send you a license file that enables their application software 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 Imgrd 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 on page 16 e To start Imgrd automatically at boot time you will have to modify your system files Unix or use the FLEX m Control Panel Windows For details see Section 3 1 1 Starting the license server at system Start Up on page 17 ADMINISTRATION TOOLS GLOBErtrotter 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 on page 52 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 on pa
72. ically install license path in registry flexlmrc after successful checkout Options support for LM_PROJECT with PROJECT Performance improvements especially for Windows NT Intel Pentium II CPU ID v7 0d November 1999 FLEXIm End User Manual November 1999 http www globetrotter com A asset_info 25 ATM 75 C ck 25 configuring FLEXIm number of server nodes 39 D DAEMON 21 Debug Log File 84 debug log file description of content 84 rotating to save space 37 Decimal format licenses Iminstall 57 DISPLAY End user options file 44 dist_info 25 DNS 75 domains 75 DUP_GROUP 24 E Error Code Descriptions 79 EXCLUDE 44 Example 50 EXCLUDEALL 44 F FEATURE in depth 22 listing users of 59 overview 11 firewalls 73 FLEX Im Error Codes 78 FLEXIm Versions 92 compatibility with different FLEXIm versions 72 description of all previous versions 88 FLEXLM_DIAGNOSTICS 65 H HOST End user options file 44 HOST_BASED 24 hostid determining without mhostid 62 HOSTID 24 I INCLUDE 45 Example 51 INCLUDEALL 45 INCREMENT in depth 22 Installing 13 INTERNET End user options file 44 internet and FLEXIm 73 ISDN 75 ISSUED 24 ISSUER 24 L license file compatibility between different versions 33 DAEMON line 21 default location 11 FEATURE line 22 frequently asked questions 72 how to combine 32 INCREMENT line 22 list for redundancy and multiple vendors 34 93 FLEXIm End User Manual November 1999 node locking
73. ile the server is running you must use Imreread to have the vendor daemon reread the options file There can only be one options file per vendor daemon and each vendor needs a separate options file 48 6 The Options File 6 4 2 6 4 3 49 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 Ifthere 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 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 RE
74. ional number of licenses 22 The License File Note There is a rarely used option in FLEX m which causes FEATURE lines to function as INCREMENT lines This option is called 1s_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 Note A FEATURE line placed after another FEATURE or INCREMENT line will be ignored unless 1s_use_all_feature_lines is set The format for the FEATURE line changed in FLEX m v3 0 and 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 name vendor ver expdate lic key vendor_str hostid v3 format FEATURE INCREMENT name vendor version exp_date lic key HOSTID hostid VENDOR_STRING vendor string vendor_info asset_info OVERDRAFT nnn dist_info user_info ISSUER NOTICE ck nnn DUP_GROUP NONE SITE UHDV Note Nothing in a FEATURE INCREMENT line is editable except for values in the name value pairs where name is all lowercase where name vendor version exp_date lic is the name given to the feature by the vendor name of the vendor daemon also found in the DAEMON line The specified daemon serves this feature version of this feature that is supported by this license expiration date for exa
75. istry On Windows the FLEXIm registry location is HKEY_LOCAL_MACHINE gt SOFTWARE gt FLEX1m License Manager On Unix the equivalent information is stored in SHOME flexlmrc In this file the syntax is variable value C 1 2 Precedence If the variable is LM_LICENSE_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 3 2 Environment variables Variable Meaning FLEXIm version introduced FLEXLM_BATCH Windows only prevents interactive popups from appearing Set to 1 if a batch application Version 7 clients FLEXLM_DIAGNOSTICS 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 LM_LICENSE_FILE 70 FLEX Im environment variables 71 VENDOR_LICENSE_FILE LM_PROJECT 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 GLOBErrotter Software products use GSI_LICENSE_FILE Version 6 client required for VENDOR_LICENSE_FILE Can be a filename or port host See a
76. key COMPONENTS pkg_list OPTIONS pkg_options where is the pkg_name name of the PACKAGE The corresponding FEATURE INCREMENT line must have the same name vendor 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 pkg_list list of components The format is feature version num_lic 26 The License File 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 num_lic is only legal if OPTIONS SUITE is not set in this case the resulting number of licenses will be num_lic on the COMPONENTS line multiplied by the number of licenses in the FEATURE INCREMENT line Examples COMPONENTS compl1 comp2 comp3 comp4 COMPONENTS comp1 1 5 comp2 comp3 2 0 4 Gl OPTIONS SUITI This is what distinguishes a suite PACKAGE from a PACKAGE used to ease distribution With OPTIONS SUITE the corresponding FEATURE of the same name as the package name 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 and it is not checked out when a component feature is
77. l This is done so that the REPORTLOG file will include transactions for all license requests which can then be reported on by FLEXadmin To do this 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 41 FLEXIm End User Manual November 1999 http www globetrotter com The Options File The options file allows the license administrator to control various operating parameters of FLEX m Users can be identified by their username hostname 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 And more Options files allow you as the license administrator to be as secure or open with licenses as you like LINE LENGTH 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 PROJECT Identifying users by LM_PROJECT requires a v5 application and v7 vendor daemon 6 1 Creating an Options File To create an options file 1 Use the appropri
78. l hostname usually returned by the hostname command or uname n 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 hostname 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 hostname 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 via telnet speedy But very often telnet speedy corp com will fail locally Note that this telnet command will always succeed on hosts in other domains 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 Imgrd 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 hostname on the SERVER or as a hostname in LM_LICENSE_FILE port host or host Does FLEX m work with NIS and DNS Yes However some sites ha
79. licensed limit will be reported by the FLEXadmin 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 VENDOR_STRING Same as vendor_string above but in name value pair syntax Note The following attributes can be changed or deleted by end users This is indicated by 3 2 5 25 a lowercase name 99909 asset_info ck nnn 99909 dist_info 9999 user_info 3 vendor_info Examples Additional information provided by the license administrator for asset management A checksum useful with the Imcksum 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 FEATURE xyz_app xyzd 2 300 31 dec 1997 20 1234567890 xyz INCREMENT f1 xyzd 1 000 1 jan 0 5 12345678901234567890 HOSTID INTERNET 195 186 NOTICE Licensed to XYZ corp FEATURESET Lines The FEATURESET line is a rarely
80. lminstall i infile o outfile verfmt 2 Conversion errors are reported as necessary Iminstall 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 If the application is active it will re checkout the license after it is freed by Imremove Usage is imremove c file feature user host display or imremove c file h feature host port handle where is the c license_file license file FLEXIm End User Manual November 1999 http www globetrotter com 7 8 Imreread feature name of the feature checked out by the user user name of the user whose license you are removing from Imstat a host name of the host the user is logged in to from Imstat a display name of the display where the user is working from Imstat a port port as reported by Imstat a handle handle as reported by Imstat a The user host display port and handle information must be obtained from the output of lmstat a Imremove removes all instances of user on host on display from usage of feature If the optional c file is specified the indicated file is used as the license file You should protect the execution of 1mremove since removing a user s license can be disruptive See the p or the x options in
81. lready exist FLEXIm End User Manual November 1999 http www globetrotter com Imver Usage is imswitchr c license_file feature new file imswitchr c license_file vendor new file v5 0 vendor daemon only where is the c license file path feature any feature this daemon supports new file new file path Note lmswitchr does not work with FLEX m v3 0 vendor daemons Ask your vendor for a 7 11 7 12 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 is the filename name of the executable of the product For example if you have an application called spell type lmver spell Alternatively on Unix systems you can use the following commands to get the FLEXI m version of a binary strings file grep Copy License Administration Tools LMTOOLS for Windows For the 32 Bit Windows Platforms an LMTOOLS EXE Windows program is provided With Imtools you can start stop and configure Imgrd license servers get system information including hostids get server status and more Imtools v7 has 2 modes CONFIGURATION USING LICENSE FILE Operations are performed on a particular license file In this mode you cannot start the Imgrd process but you can do everything else In the first tab you need to select a license file CONFIGURATION USING SERVICES Operations are performed on a Window
82. lso Section 3 1 2 Setting the Path with an Environment Variable on page 19 SVENDOR_LICENSE_FILE requires v6 clients LM_PROJECT s value is logged in REPORTLOG 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 End User Manual November 1999 http www globetrotter com Frequently Asked Questions D 1 License File Questions D 1 1 I ve received FLEX m license files from 2 different companies Do I have to combine them You don t have to combine license files Each license file that has any counted lines the number of licenses field is gt 0 requires a server It s perfectly OK to have any number of separate license files with different Imgrd 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 Imdown Imreread you can stop reread restart 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 lic for license file management behaves like combining licenses without physically combining them D 1 2 When i
83. ment otherwise lmgrd attempts to put up console windows 18 The License File 3 1 2 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 provided by the location 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 In the Korn and Bourne shells LM_LICENSE_FILE license_file_path export LM_LICENSE_FILE On Windows 3 1 and 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 adding LM_LICENSE_FILE to license_file_path where is the license_file_path full pathname to the license file This can also be a port host setting where port and host are the port number and hostnames from the SERVER line in the license file v6 applications can use simply host 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 d
84. mple 7 may 1996 Note If the year is O or 00 000 0000 then the license never expires Dates before 2000 can be 2 or 4 digit years After 2000 they must be 4 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 users is set to 0 the licenses for this feature are uncounted and no mgrd is required but a hostid on the FEATURE line is required See Section 5 4 Counted vs Uncounted Licenses on page 40 FLEX m v6 or later applications only the keyword uncounted can be used instead of a count of 0 23 FLEXIm End User Manual November 1999 http www globetrotter com key License File Format license key for this FEATURE line Two identical looking FEATURE or INCREMENT lines may have different license keys if the start dates are different The following fields are all optional except for vendor string in the old 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_string hostid DUP_GROUP2 HOSTID hostid HOST_BASED ISSUED dd mmm yyyy ISSUER NOTICE OVERDRAFT nnn vendor defined string enclosed in double quotes This string can contain any characters except a quote string returned
85. n as root since it can be a security risk to run any program that does not require root permissions and Imgrd does not require root permissions 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 s what s used by the boot scripts The use of nohup and sleep are required on some operating systems notably HPUX 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 Imdiag is used as a diagnostic tool to verify that the server is running and serving licenses Note On IBM RS6000 systems etc re cannot be used because TCP IP is not installed when this script is run Instead etc inittab must be used Add a 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 Note This will not start the daemon until you reboot your license server machine WINDows NT From the Control Panel use the FLEXIm License Manager to start Imgrd as a service You can optionally indicate that this should be started at system startup WINDowsS 95 98 Services are not supported on this platform However you can start v7 lmgrd in the autoexec bat Be sure to start to give the full path to the Imgrd exe the vendor daemons must be in the path and you must include l1 logfile argu
86. n 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 45 FLEXIm End User Manual November 1999 http www globetrotter com Customizing the Options File 6 e 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 on page 45 e name name of the user or group to include To allow the user jane to use all features served by this vendor daemon INCLUDEALL USER jane 6 2 7 LINGER LINGER featurename interval Rarely used This causes the daemon to hold on to the license for featurename for interval 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 users 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 6 2 8 MAX v5 11 vendor daemon only MAX numlic featurename type name Limits usage for a group or user e numlic usage limit for this user or group e featurename
87. n use a PACKAGE name in place of a feature name and the option will apply to the whole package 6 2 1 EXCLUDE EXCLUDE featurename type name 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 e featurename name of the feature being affected e 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 on page 45 e name 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 USER hank 6 2 2 EXCLUDEALL EXCLUDEALL 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 e 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 on page 45 e name name of the user or group to exclude To exclude any user on the machine chaos from using all features served by this vendor daemon EXCLUDEALL HOST chaos 6 2 3 GROUP GROUP groupname usernamelist 44 6 The Options File Defines a group of users for use in INCLUDE INCLUDEALL EXCLUDE EXCLUDEALL and RESERVE option lines e groupname name of the group being defined e usernamelist iist of user names in that group To define the group Hackers consisting of bob howard
88. nager process Imgrd 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 on page 42 Note Refer to your vendor s documentation before attempting to change file names 2 2 2 2 1 13 locations or contents Getting Started Checklist The following sections provide a quick overview of how to set up and use licensing for FLEXI m licensed products By scanning the list you should be able to quickly find the areas of interest Cross references point to more details in other parts of this manual 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 2 2 Notes for End Users on page 14 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 A 1 Hostids for FLEX1m 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 licens
89. nse Files 32 4 1 1 Combining License Files from Multiple Vendors 33 4 1 2 FLEX m Version Component Compatibility 33 4 1 3 Using Separate License Files on the Same Server Node 34 4 2 Using LM_LICENSE_FILE License File List 34 Chapter 5 Selecting Server Nodes 36 5 1 Resources Used by the Server 36 5 1 1 Sockets 36 5 1 2 CPU Time 37 5 1 3 Disk Space 37 5 1 4 Memory 38 5 1 5 Network Bandwidth 38 5 2 Remote Mounted Disks 38 5 3 Redundant Servers 38 5 3 1 Three Server redundancy 39 5 3 2 Redundancy via License File List in LM_LICENSE_FILE 39 5 3 3 Comparing Three Server to License File List 40 5 4 Counted vs Uncounted Licenses 40 Chapter 6 The Options File 42 6 1 Creating an Options File 42 6 2 Customizing the Options File 43 6 2 1 EXCLUDE 44 6 2 2 EXCLUDEALL 44 6 2 3 GROUP 44 6 2 4 HOST_GROUP 45 6 2 5 INCLUDE 45 6 2 6 INCLUDEALL 45 6 2 7 LINGER 46 6 2 8 MAX 46 6 2 9 MAX OVERDRAFT 46 6 2 10 NOLOG 46 6 2 11 REPORTLOG 47 6 2 12 RESERVE 47 6 2 13 TIMEOUT 48 6 3 TIMEOUTALL 48 6 4 Understanding Options Files 48 6 4 1 How the Vendor Daemon Uses the Options File 48 6 4 2 Rules of Precedence in Options Files 49 6 4 3 Simple Options File Example 49 6 4 4 Limiting Access for Multiple Users 50 6 4 5 EXCLUDE Example 50 6 4 6 INCLUDE Example 51 FLEXIm End User Manual November 1999 Chapter 7 License Administration Tools 52 7 1 Imcksum 53 7 2 Imdiag 53 7 3 Imdown 54 7 4 Imgrd55 7 5 Imhostid 56 7 6 Iminstall 57 7 7 mremove
90. odes 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 as 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 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 dialup links Redundancy via License File List in LM_LICENSE_FILE This is best explained by example If 10 licenses are desired for both f1 and f2 the ISV would issue 2 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 lic
91. oesn 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 FLEXIm than this program understands ENCRYPTION_SEEDs are non unique feature removed during Imreread or wrong SERVER line hostid 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 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 the you re referring to the right host see LM_LICENSE_FILE The desired vendor daemon is down 1 Check the Imgrd log file or 2 Try Imreread 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
92. on 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 and a license file from vendor XYZ with incompatible servers You can place the license file from vendor ABC into usr flexlm abc dat and the license file from vendor XYZ into usr flexlm xyz dat then set the LM_LICENSE_FILE environment variable to point to both of them Each 66 99 name in LM_LICENSE_FILE should be separated by a colon on Unix systems a semicolon on Windows and Windows NT systems in FLEX 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 dat usr flexlm xyz dat In the Korn and Bourne shells LM_LICENSE_FILE usr flexlm abc dat usr flexlm xyz dat 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 on page 32 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
93. on is connected to its peer on node node CONNECTED master is name The license daemons log this message when a quorum is up and everyone has selected a master 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 84 The Debug Log File F 2 85 Lost connection to host A daemon can no longer communicate with its peer on node host which can cause the clients to have to reconnect or cause the number of daemons to go below the minimum number in which case clients may start exiting If the license daemons lose the connection to the master they will kill all the vendor daemons vendor daemons will shut themselves down Lost quorum The daemon lost quorum so will process only connection requests from other deamons MULTIPLE xxx servers running Please kill and restart license daemon The license daemon has detected that multiple licenses for vendor daemon xxx are running The user should kill all xxx daemon processes and re start the license daemon OUT feature by user N licenses user has checked out N licenses of feature RESERVE feature for USER name A license of fe
94. or can opt not to log messages to the debug log file if disk space is at a premium See Section 6 2 10 NOLOG on page 46 and Section 6 2 11 REPORTLOG on page 47 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 Imgrd to a shell script that appends to the file for each line This is done as follows Instead of the normal startup lmgrd gt LOG Start Imgrd 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 Note This technique applies to Unix systems only 37 FLEXIm End User Manual November 1999 http www globetrotter com Remote Mounted Disks 5 1 4 Memory The FLEX m daemons use little memory On SunOS mgrd 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 5 1 5 Network Bandwidth FLEXI m sends relatively small amounts of data across the network Each transaction such as a
95. oreground In v7 Imgrd runs in the background by default If l logfile is present then no windows are used but if no l argument specified separate windows are used for Imgrd and each vendor daemon v Prints mgrd s version number and copyright and exits Note Pre v6 Imgrd on Windows required app argument when not run as a service 7 5 Imhostid The lmhostid utility reports the hostid of a system Usage is imhostid n vsn flexid Windows ether HP The output of this command looks as follows imhostid Copyright c 1989 1997 Globetrotter Software Inc The FLEXIm hostid of this machine is 69021c89 With the n argument no header is printed only the hostid On Windows and HP optional hostids are available where is vsn Volume Serial Number of the C drive flexid Globetrotter dongle based hostids ether Ethernet hostid 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 cpu 32164196 Pentium III hostid Requires Windows FLEX m v7 0d Pentium III 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 IDis 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
96. ot heard from the process the 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 would require a license that can be freed with TIMEOUT With v5 licenses are freed when they time out 6 3 TIMEOUTALL v5 11 vendor daemon only TIMEOUTALL seconds Same as TIMEOUT but applies to all features 6 4 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 6 4 1 How the Vendor Daemon Uses the Options File When the vendor daemon is started by mgrd it is passed the location of the options file If you modify the options file wh
97. own c license_file vendor name q all where is c license_file Use the specified license file vendor name Only shutdown this one vendor daemon 1mgrd will always continue running if this option is specified Requires v6 0 Imdown and 1mgrd the vendor daemon can be any version q 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 1 is shutdown q is implied with all v7 54 License Administration Tools 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 on page 55 for details about securing access to 1mdown If lmdown encounters more than one server for example if c specifies a directory with many lic files a choice of servers to shutdown is presented To stop and restart a single vendor daemon use 1mdown vendor name then use lmreread vendor name which restarts the vendor daemon Note When shutting down redundant servers there is a one minute delay before the servers 7 4 55 shut down Do not use kill 9 to shut down the license servers See Also Section 7 8 Imreread on page 58 Imgrd lmgrdis the main daemon program for FLEX m When you invoke mgrd it looks for the license file which contains the information abo
98. pplication 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 mgrd 2 The client establishes a connection with the license manager daemon mgrd and tells it what vendor daemon it needs to talk to 3 Imgrd determines which machine and port correspond to the master vendor daemon and sends that information back to the client 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 number of licenses 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 12 Introduction and Overview e the 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 the location of all executables e the location of all log files e the TCP IP port number used by the license ma
99. programs except mgrd are packaged as a single executable called mutil Imutil can either be installed as the individual commands either by creating links to the individual command names or making copies of Imutil as the individual command names or the commands can be run as Imutil command e g Imutil Imstat or Imutil Imdown On Windows or Windows NT systems the Imutil command_name form of the commands are available There is also a Windows version of these commands see Section 7 12 License Administration Toolsk LMTOOLS for Windows on page 60 ARGUMENTS VALID FOR ALL LMUTIL UTILITIES c license_file Most mutil utilities need to know the path to the license file This can be specified with a c license_file 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 52 License Administration Tools 7 1 7 2 53 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 version 6 only e file Redirect error messages to file v7 SEE ALSO e Section C 1 How to set environment variables on page 70 Imcksum The 1mck sum 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
100. pter 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 A section called Getting Started Checklist on page 13 tells both license administrators and end users how to start managing FLEXIm 2 1 Introduction to FLEX m FLEXI m is the most popular license manager used in the software industry FLEX m 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 administrators 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 on page 28 for details about the different licensing models supported by FLEXI m 2 1 1 FLEX m Components The four main components of FLEX m are e license manager daemon e vendor daemon e license file e application program THE LICENSE MANAGER DAEMON LMGRD The license manager daemon Imgrd 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 no
101. re that port numbers be specified to the firewall FLEX m v5 Imgrd 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 Imremove to free the license What happens when the license server dies FLEXI 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 re started FLEXIm End User Manual November 1999 http www globetrotter com Using FLEXIm aD 99 44 of the time if it s in use it s because Imgrd 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
102. romversion 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 9BFAC03164EDB7BC0462 UPGRADE f1 xyzd 1 000 2 000 1 jan 1999 2 1B9A30316207EC8CCOF7 would result in 3 licenses of v1 0 of f1 and 2 licenses of v2 0 of f1 UPGRADE will operate on the most recent FEATURE or INCREMENT line i e closest preceding FEATURE or INCREMENT line with a version number that is gt fromversion and lt version Note that UPGRADE does not work for node locked uncounted licenses before version 6 Sample License File This is an example of a license file for 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 10 floating licenses for xyz_app1 and xyz_app2 to any user on the network 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 referre
103. 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 Solution 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 1s 1 of the vendor daemon filename s specified in the log file Make sure you do this as the same user that started Imgrd Verify that the file is executable Note that if you are running as root and using an NFS mounted filesystem 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 system has that program what is 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 mgrd if it crashes or fails to execute then it is not properly linked Symptom The license server keeps reporting lost lock errors in the log file and exiting Cause The lockfile normally placed in usr tmp on Unix C flexlmon Windows NT SYS SYSTEM FLEXLM on Netware is being removed by someone else There could be another daemon running
104. s Service which allows starting Imgrd processes 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 60 License Administration Tools Use the Configure Services tab to define a license service When configuring a service a license file is chosen similar to Configuration using License File but in addition locations for Imgrd and debug log file are specified and the service is given a unique name and you can also indicate that the service should be started with system boot 61 FLEXIm End User Manual November 1999 http www globetrotter com Appendix A Hostids for FLEX m Supported Machines FLEXI m uses different machine identifications for different machine architectures For example all Sun Microsystems Inc 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 12 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 0800200005ac as the hostid The program 1mhostid 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
105. s 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 4 digit year Dates in the 20th century 19xx can be abbreviated to the last 2 digits of the year xx and use of this feature is quite widespread Dates in the year 2000 and beyond must specify all 4 year digits D 2 FLEX m Versions D 2 1 Ihave products from several companies at various FLEX m version levels Do I have to worry about how these versions work together If you 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 lmgrd will always correctly support older versions of vendor daemons and applications so it s always safe to use the latest version of Imgrd and the Imutil Imtools utilities If you ve combined license files from 2 vendors you must use the latest version of Imgrd If you ve received 2 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 72 D Frequently Asked Questions D 2 2 D 2 3 D 3 D 3 1 D 3 2 D 3 3 D 3 4 73 Please ignore letters appended to FLEX m versions i e v2 4d
106. ser as long as they are on the host bigbrush to use feature paint 35 66 Deny access to the feature paint to anyone except picasso mondrain or anyone from the host bigbrush By implication SEE ALSO APPENDIX C ENVIRONMENT VARIABLES ON PAGE 70 FLEXIm End User Manual November 1999 http www globetrotter com License Administration Tools FLEXI m provides utilities for the license administrator to help manage the licensing activities on the network These utilities are Imcksum v2 4 or later prints license checksums page 53 Imdiag v4 0 or later diagnoses license checkout problems page 53 Imdown gracefully shuts down all license daemons both mgrd and all vendor daemons on the license server node or on all three nodes in the case of redundant servers page 54 Imgrd the main daemon program for FLEXIm page 55 Imhostid treports the hostid of a system page 56 Iminstall install a decimal format license page 57 Imremove removes a single user s license for a specified feature page 57 Imreread causes the license daemon to reread the license file and start any new vendor daemons page 58 Imstat helps you monitor the status of all network licensing activities page 59 Imswitchr switches the report log file page 59 Imver teports the FLEX m version of a library or binary file page 60 Beginning in FLEX m v2 4 all FLEX m utility
107. 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 a single license file If the SERVER lines in those 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 32 Multiple License Files 33 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 mgrd as described below in Section 4 1 1 Combining License Files from Multiple Vendors on page 33 If the license files are not compatible then you must keep the license files separate and run separate copies of mgrd for each license
108. ster 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 prevent licensing conflicts during installation There are three ways you can accomplish this e Multiple license server nodes each running one mgrd and one license file e One license server node running one mgrd and several license files e One license server node running multiple mgrds and multiple license files Note that before version 6 each Jmgrd 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 mgrds to administer If all applications and vendor daemons are FLEX m v6 Imgrd can process multiple license files even when the hostids are different so long as they refer to the same node Your product s license file s define the license server s by hostname 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
109. te that the feature name and license key are printed along with the license file location or hostname if host were used and hostname 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 66 BY Troubleshooting Guide B 3 2 B 3 3 67 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 Hostid Problems Symptom When I run the license manager on my machine it tells me it Cause Solution 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 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 t
110. the checkout there s no such feature in the license it did find and it was unable to find the other license file which is what produces the message No such file or directory FLEXIm End User Manual November 1999 http www globetrotter com FLEXIm Troubleshooting List Be Following is a description of the arguments to m_checkout lm_ checkout feature_name version nlic queue_flag dupgroup_mask where is feature_name the requested feature version requested version The license file must contain a version gt the requested version nlic 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 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 granted setenv FLEXLM_DIAGNOSTICS 3 application Checkout succeeded 0 14263EAEA8E0 License file servtest lic No 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 No
111. this depends on the application and end user s use A typical checkout request requires 5 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 Imstat 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 down loaded from the server to the client port host should be if possible limited to small license files say lt 50 features In v5 port host actually improves performance D 3 9 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 74 D Frequently Asked Questions D 3 10 D 3 11 D 3 12 75 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 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 hostname is of the form node domain where node is the loca
112. tion 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 mgrd vendor daemon and application strings program grep Copy Alternatively mgrd v gives the Imgrd version and this works with the vendor daemon also 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 What is the output from running lmstat a Are you running other products which are also licensed by FLEX m Are you using a combined license file or separate license files 64 BY Troubleshooting Guide B 2 e Are you using redundant servers multiple SERVER lines in your license file FLEXLM_DIAGNOSTICS Note Available only with applications using FLEX m v4 1 or higher for Unix and v5 0 or B 2 1 B 2 2 65 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
113. ued 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 when clients are 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 3 servers any number will work and 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 5 4 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 40 Selecting Server Nodes 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 server can serve uncounted licenses as wel
114. ut vendors and features On Unix systems it is strongly recommended that Imgrd be run as a non privileged user not root Usage is imgrd c license_file l logfile s timestamp_interval 2 p x lmdown x lmremove z v where is c license_file Use the license file named l logfile Write the debug log to logfile s timestamp_interval Specifies the logfile timestamp interval in minutes The default is 360 minutes 2 p Restricts usage of lmdown 1mreread 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 x Imdown Disallow the Imdown command no user can run Imdown If Imdown is disabled you will need to stop Imgrd via kill pid Unix or CTRL ALT DEL and stop the Imgrd and vendor daemon processes Windows 95 On Unix be sure the kill command does not have a 9 argument v4 Imgrd FLEXIm End User Manual November 1999 http www globetrotter com Imhostid x Imremove Disallow the Imremove command no user can run Imremove v4 Imegrd Z Run in foreground The default behavior is to run in the background Windows pre v7 Imgrd always runs in the f
115. ve 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 In addition some systems particularly Sun SGI HP require that applications be linked dynamically to support NIS or DNS If a vendor links statically this can cause the application to fail at a site that uses NIS or DNS In these situations the vendor will have to relink or recompile with v5 FLEX m when it becomes available in Q1 of 96 Vendors are strongly encouraged to use dynamic libraries for libc and networking FLEXIm End User Manual November 1999 http www globetrotter com D 3 13 D 3 14 D 4 D 4 1 D 4 2 Windows Questions libraries since this tends to improve quality in general as well as making NIS DNS work On PCs if a checkout seems to take 3 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 hostnames must NOT have periods in the name These are not legal hostnames although PCs will allow you to enter them and they will not work with DNS Is the FLEX m display the same as an X Display Not by default The default FLEX m display is what is returned
116. 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 certain items specify that a logfile be written suitable for use by the FLEXadmin End User Administration Tool reserve licenses for a user specify idle timeout for a feature returning it to the free pool for use by another user 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 FLEXIm End User Manual November 1999 http www globetrotter com Customizing the Options File 6 Starting with FLEX m v5 you can select a particular line of a given featurename as follows FEATURENAME SPECIFICATION featurename name value 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 ca

FLEXlm End User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents