HP Panter 2Tier manual Lmdiag, Diagnoses licensing problems

Page 70

FLEXlm Utilities

lmdiag

Diagnoses licensing problems

lmdiag [–c license_file] [–n] [feature]

–clicense_file

Name of license file to diagnose. If this switch is not specified, lmdiag looks for

 

the environment variable LM_LICENSE_FILE. If the environment variable is not

 

set, lmdiag looks for the file /usr/local/flexlm/licenses/license.dat.

–n

Non-interactive mode; lmdiag does not prompt for any input. In this mode,

 

extended connection diagnostics are not available.

feature

Diagnose only the specified feature.

 

 

Description

If no feature is specified, lmdiag operates on all features in the license file in your

 

path. lmdiag first prints information about the license, then attempts to check out

 

each license. If the checkout succeeds, lmdiag indicates this. If the checkout fails,

 

lmdiag gives you the reason for the failure. If the checkout fails because lmdiag

 

cannot connect to the license server, then you have the option of running “extended

 

connection diagnostics.”

 

Extended diagnostics attempt to connect to each port on the license server node,

 

and can detect if the port number in the license file is incorrect. lmdiag indicates

 

each port number that is listening, and if it is an lmgrd process, lmdiag indicates

 

this as well. If lmdiag finds the vendor daemon for the feature being tested, then it

 

indicates the correct port number for the license file to correct the problem.

Appendix C License Administration

63

Image 70
Contents Tier Installation Page Table of Contents Chapter Web Application Server Windows Appendix D License File About this Guide Organization of this GuideText Conventions ConventionsKeyboard Conventions Panther Documentation Panther Documentation Online Documentation Procedure or module Collateral Documentation Additional Help Page Installation Installation ChecklistPre-Installation Post-InstallationContents of the Installation Package General InformationWhich Panther Components to Install? Application ArchitectureFor More Information Client Pre-Installation for Windows Client Windows InstallationHardware and Software Requirements Upgrading Installation Procedure Client Installation for WindowsTo run the setup program To install database drivers Installing a Database DriverInformix Microsoft SQL Server OracleSybase Create New Prolifics Executables Client Post-Installation for WindowsPost-Installation Overview To create a new Prolifics executableSpecifying Executables To include the appropriate database in your executables Configure the Client EnvironmentLinking Database For each Windows clientClient Installation Verify the InstallationTroubleshooting Look at Sample ApplicationsWindows Path Settings Online Help Manuals Adding Panther DocumentsWeb Application Server Pre-Installation for Windows Web Application Server WindowsBefore Installing Licensing for Prolifics Web Application Server Web Application Server Post-Installation for WindowsObtaining a Permanent License File To install a permanent license file Installing the License FileTo obtain the license file Configure the Web Application Server Environment Location License FileTo verify the Prolifics web application server installation Web Application Server InstallationCreating a Web Application QuickStart Look at SamplesProlifics Gallery web application Client Unix Installation Client Pre-Installation for UnixFile Ownership and Protection Implement File ProtectionDetermine File Location UpgradingClient Installation for Unix To install Panther from a CD-ROMConfiguring the Installation To configure the installationAdditional Procedures Client Post-Installation for Unix Licensing for ProlificsInstalling License File To determine the version of lmgrd Location of the License File Starting ManagerTo start the license manager Create New Prolifics Executables Specifying Executables Linking in the Database Configure the Client Environment ApplicationDir/setup.sh To verify a Unix client installation Look at a Sample ApplicationLicense Manager Post-Installation NotesImplementing Character-Mode Utilities Motif Version Number Graph Functionality.ebtrc file $SMBASE/docs = Panther Web Application Server Pre-Installation for Unix Web Application Server UnixWeb Application Server Post-Installation for Unix Preliminary StepsWeb Application Server Unix Creating Your Web Application Determine File LocationsMonitor -start applicationName Windows DLLs for Jpeg DecodingUsing Prolifics Utilities Environment Space Visual C++ Floating-Point Options` Run the utilities from DOS Initialization Databases For Windows 95/98 and Windows NTFor Windows 95/98 For Windows NT Driver=ora8dmnt.dll License Administration License Daemons and License Types Licensing in ProlificsTypes Daemons Options File License TypesContents Options File FLEXlm Utilities ExampleLmcksum Performs a checksum of a license fileDiagnoses licensing problems LmdiagLmdown Takes down license daemonsLmgrd Starts up the license manager daemonLmhostid Output from lmhostid is similar to the followingLmremove Removes a user license and returns it to the license poolLmreread Tells the license daemon to reread the license fileReports status on license manager daemons and feature usage LmstatLmswitchr Lmver Reports the FLEXlm version of a library or binaryContents of the License File License FileDaemon Increment Error Messages Prolifics Installation Error MessagesFilename No such file or directory Informix-Specific Messages DLL MessagesMicrosoft SQL Server-Specific Messages ODBC-Specific Messages Oracle-Specific MessagesSybase-Specific Messages License Manager Error MessagesGraph-Related Messages DLL Version Mismatch MessagesProlifics License-Related Messages All License TypesProlifics License Manager Initialization failed Floating Licenses Node-locked LicensesCreate License Utility Cause feature has passed its expiration date FLEXlm Informational MessagesCause License daemon received fatal signal nnn FLEXlm Configuration Problem Messages Daemon Software Error Messages Cause An invalid server connect message was received Cause An error in a read system call was detected Index Tier Installation Odbc