Southern California CAD Summit San Diego Convention Center September 25, 2008.
Autodesk Network Licensing Taming Your Inner Daemons
DESCRIPTION: This session will discuss the basic functions and components of the Autodesk Network License Manager. Users will learn how to use FlexLM functions, LMTools interface, and the configuration of the license manager. Explore the setup and use of an Options File and the ability to manage license usage within a company. Installing LMTools Configuring LMTools Combining License Files Configuring Options Files
3191 Red Hill Ave Suite 200 Costa Mesa, CA 92626

877.648.7223

www.uscad.com
Introduction: There are three different License Server Configurations that are support by Autodesk. The three models are the Single Server, Distributed, and Redundant licensing configurations. I will detail the definitions of each below in order of installation frequency from most to least. The majority of firms will be able to use the Single Server model which is easy to install, maintain, and troubleshoot. Single Server Model: The single license server provides one central license server that allocates licenses throughout the network. This configuration requires a reliable, low-latency network connection to maintain the link between the client and server. The FlexLM server allows for brief periods of downtime, typically less than 120 minutes (2 hours), after which the client is warned that contact with the network has been lost. The network administrator registers and activates the server one time to obtain the pool of authorized network licenses. Distributed Server Model The distributed license server configuration allows a computer to work through a list of network license servers to obtain a network license. Each workstation stores the location of some or all of the available network license servers. This configuration allows for communication over wide-area networks and offers protection against network failures. In this deployment model, a separate license must be created for each seat in the pool. (ex. 100 ACAD 2009 licenses, Server1 gets 50seats, Server 2 gets 50seats. If Server1 fails, client machine will search for a license from the Server2 pool.) Redundant Server Model The redundant license server configuration provides protection against network failure by sharing a single pool of network licenses among three servers, which must be in constant communication across a high-availability, low-latency network. The network administrator registers and activates one server one time to obtain the pool of authorized network licenses. This master license is backed up on each of the redundant servers.
Installation of the Single License Server Model: 1. Obtain a Network License for your Autodesk Network Licensed products. You can do this several ways, but I prefer to call in 1-800-551-1490 2,1. Before you call be sure to have selected your email address, Licensing Server Name, MAC address, and the Serial Number(s) from the products requiring a network license. Select Run, type cmd and then type ipconfig /all.
2. Record the Host Name which is the Server Name. Next look for the Ethernet adapter Local Area Connection header and find the Physical Address which is the 12 digit MAC address required to generate a.LIC 3. Obtain your.LIC file and rename to USCAD_Autodesk.LIC and remember to only work with ASCII editors (notepad) when using.LIC files!!!
3191 Red Hill Ave Suite 200 Costa Mesa, CA 92626 877.648.7223 www.uscad.com
4. A sample 2009 Civil 3D product license would look like this (bold text below): PACKAGE 64900CIV3D_F adskflex 1.000 COMPONENTS="59700CIV3D_2009_0F 55400CIV3D_2008_0F 52200CIV3D_2007_0F 49700CIV3D_2006_0F"\ OPTIONS=SUITE SUPERSEDE ISSUED=07-May-2008 SIGN="148A C4AD \ BF4F 1776 CA80 BFB2 0AC3 4F7A 696C F445 1A93 F3A1A \ F004 1D12 587E 5390 EE38 C4BF 7243 63E9 D026 8AC0 \ 7376 7EFD 7CD7 6332" SIGN2="085A 3565 E6C7 B113 60B9 D36F 91D7 \ BE7F 3559 A1B6 E2FB A701 28BB 3C0B62 F762 92B3 D857 \ E34C 6D3C EC29 344F D65F CD0C F7D5 4EAB52D 0174" INCREMENT 64900CIV3D_F adskflex 1.000 permanent 16 \ VENDOR_STRING=commercial:permanent BORROW=4320 SUPERSEDE \ DUP_GROUP=UH SUITE_DUP_GROUP=UHV ISSUED=07-May-2008 \ SN=123-45678901 SIGN="1478 5F01 7F00 B851 AF44 F73C 86CF DD60 \ D9F1 C859 70FB 64B8 CAF3BCD 1F24 4AAB 262F 6736 26F5 \ BA22 179A 09B3 DF2B 59FF61C DEB2" SIGN2="0DEC \ F79C 01E4 D460 DAD1 153B 0B69D0 179D 7CB4 3EB8 345B \ DA1E E73F 0159 4E96 0C4C 26A3 F600 8AF4 A44A7 33C4 \ 08FF 432E 1122 A784 4C07" INCREMENT PLIST adskflex 1.000 permanent 1 \ VENDOR_STRING=A07:51600ACDLAND_2007_0F:52200CIV3D_2007_0F;B07:51 900AMECH_PP_2007_0F:51300INVBUN_11_0F:52900INVPRORS_11_0F:53000INVPROS IM_11_0F:51400INVPRO_11_0F;C07:51200ACD_2007_0F:52500REVITS_9_0F:54100RE VITS_9_1F:53700REVSU_3_0F:54200REVSU_4_0F;D07:52600REVIT_9_0F:52500REVIT S_9_0F;E07:57600ACD_2009_0P:59300INVBUN_2009_0P;F07:51800BLDSYS_2007_0F: 53100REVSYP_1_0F:54500REVSYP_2_0F;G07:53400REVITST_3_0F:53700REVSU_3_0F ;H07:54300REVIT_9_1F:54100REVITS_9_1F;I07:54400REVITST_4_0F:54200REVSU_4_ 0F;A08:55500ACDLAND_2008_0F:55400CIV3D_2008_0F;B08:54900AMECH_PP_2008_0 F:55000INVBUN_2008_0F:55100INVPRORS_2008_0F:55200INVPROSIM_2008_0F:5530 0INVPRO_2008_0F;C08:54600ACD_2008_0F:54700REVITS_2008_0F:54800REVSU_200 8_0F;D08:57100REVIT_2008_0F:54700REVITS_2008_0F;F08:55600BLDSYS_2008_0F:5 5700REVSYP_2008_0F;G08:57200REVITST_2008_0F:54800REVSU_2008_0F;A09:59800 ACDLAND_2009_0F:59700CIV3D_2009_0F;B09:59200AMECH_PP_2009_0F:59300INVB UN_2009_0F:59400INVPRORS_2009_0F:61700INVMFG_2009_0F:59500INVPROSIM_20 09_0F:59600INVPRO_2009_0F;D09:62100REVIT_2009_0F:60900REVITS_2009_0F;C09 :57600ACD_2009_0F:60900REVITS_2009_0F:61000REVSU_2009_0F;F09:59900BLDSYS _2009_0F:60000REVSYP_2009_0F;G09:62200REVITST_2009_0F:61000REVSU_2009_0 F;J09:67800RVTMPJ_2009_0F:60000REVSYP_2009_0F \ SUPERSEDE ISSUED=07-May-2008 SIGN="029C 86E211E 7968 \ D00B DFE4 F139 7C9C5A 29CC 2C9B D500 DFAD 1ECD A3A3 \ FC4E 55E4 EE21 DF0B D312 3C17 1CB2 C03B C2AE 35AB 3620 C033 \ D95F" SIGN2="03F5 796D 6840 6D4D DEE3 37C9 77D59A8 67C5 \ 1C6A E196 A2B3 6C00B7 F3F6 CDC0 DA23 FA9E 6BCB DF6F

PACKAGE 64900CIV3D_F - Is an example of the 4year package licenses issued for 2009 products. Below are the feature codes for the products and release years available to pull a license from this file. o 59700CIV3D_2009_0F o 55400CIV3D_2008_0F o 52200CIV3D_2007_0F o 49700CIV3D_2006_0F INCREMENT 64900CIV3D_F adskflex 1.000 permanent 16 \ - This is the Increment value for the product feature code that lists the license pool for this license (16). INCREMENT PLIST Priority List increment for the cascading licensing functionality and controls the hierarchy of products capable to pull a license from this license file.
5. A Sample 2008 Viz product license would look like this (bold text below): INCREMENT 56900VIZ_2008_0F adskflex 1.000 permanent 1 \ VENDOR_STRING=commercial:permanent BORROW=4320 SUPERSEDE \ DUP_GROUP=UH ISSUED=07-May-2008 SN=123-45678901 SIGN="011B\ 765C 0AF2 BC21D1 0C36 CE611D 2973 E54A B08F \ F657 CF21 1B1A 2B65 B4ABD0F A50D F7711 8B59 \ D355 A9CE1AC 0BB7" SIGN2="15AB 3189 F872 93B2 5AFB 689D \ 6335 CBEEB 72D9 DA71 DDFA F705 B14C 12A3 A258 858A \ A07E F09A E9FE B58A 7F68 C37A 10E1 7F49 0D2C 25F8 414F 1D88" INCREMENT 56900VIZ_2008_0F Is an example of the 2008 and prior license file. There are PLIST sections in the Autodesk vertical apps, but the Package licensing is not present in 2008 and prior license files.
6. Using your ASCII editor you can combine several product licenses into 1.LIC file. Maintain the first three lines; these list the licensing server, MAC, and the client port (2080):
7. Copy and paste the entire 2009 contents from Package last string DF6F and place it under any other license entry in the.LIC. This way all product license files fall under the first three lines calling the License Server Name and MAC. 8. Once all of your product licenses are combined you are ready to begin the installation or upgrade of LMTools. 9. Insert the Product Disk in the Server or a shared DVD drive 10. Select Install Tools and Utilities (below):
11. Check the Autodesk Network License Manager box:
12. Read, read, read yup looks like a licensing agreement!
13. The next screen allows you to configure the installation of the Autodesk Network License Manager. However I strongly suggest that you accept the defaults and click Install to the install the License Manager to the default location C:\Program Files\Autodesk Network License Manager. Note: I have seen several instances of the ADLM installed to a mapped drive
which have not been able to issue licenses. Upon re-installation to C:\. the ADLM worked correctly.
14. Click Configuration Complete to begin the installation
15. Verify the final screen after installation
16. Upon the successful installation of the Autodesk Network License Manager you can verify the installation by reviewing the installation location (below):

17. Verify that the lmgrd.exe daemon is present
18. Create a New Folder named Log in this directory
19. Open the Log directory and right click to create a new Text Document (.txt) document. Switch the Files of type: drop down to *.* all files to be able to view the newly created.txt file. Rename the document to Debug.log and select Ok to change the file type.

Final.log file:

20. Launch the Shortcut from the server Desktop. 21. Verify the version by selecting Help About
22. To run Autodesk 2009 Licenses you must have version 11.4x (below) which can be installed from an Autodesk 2009 Product Disc (excluding AutoCAD LT):
23. Now lets configure LMTools. Select the Service/License File tab and verify that the Configure using Services radio button is selected and all other boxes remain unchecked.
24. Next, jump over to the Config Services tab and Create the Server Service Autodesk Licensing and select the browse buttons below to select the default path: Autodesk Licensing Daemon C:\Program Files\Autodesk Network License Manager\lmgrd.exe Autodesk License File C:\Program Files\Autodesk Network License Manager\License\USCAD_Autodesk.lic Autodesk Licensing Daemon Log File C:\Program Files\Autodesk Network License Manager\Log\Debug.log
Select the two Check Boxes at the bottom:
Finally, dont forget to Save Service:
25. Finally you need to verify that your license file is being read. You can select the Start/Stop/Reread Tab. These buttons will allow you to Start the Server Service Autodesk Licensing, Stop the Server Service Autodesk Licensing, or to reread the license file USCAD_Autodesk.lic. Note: Keep your eyes on the Status Bar at the bottom to see the results and
notice that your service is shown in the window Autodesk Licensing
26. Lastly you can verify the service configuration in the Microsoft Management Console Services Autodesk Licensing. It should read Started and in the properties it should be Automatic.
Other Controls/Requirements for LMTools: Server Configuration: Server Name Server MAC address for LAN Ethernet Card Minimal Space on C:\ required (~10MB or less)
Server TCP/IP Port monitoring: 2700027009 Client Configuration: Client Workstation Port: 2080 Ability to see the licensing server over you network LICPATH.LIC or Windows Environment Variable or.REG Key Note: This is the hierarchy of configurations that the client machine uses to
search for an available license.
Example LICPATH.LIC file (Hidden file located C:\Program Files\Autodesk Product) SERVER ML-C-1 0018DE4015BF USE_SERVER Example Windows Environment Variable ADSKFLEX_LICENSE_FILE @SERVER1;@SERVER2 If both are present at the client workstation the Windows Environment Variable will supersede the LICPATH.LIC file. Options File: LMTools has the ability to use an ASCII file to assist with license administration. This file is called an Options File and must be named adskflex.opt and placed in the same directory as your Autodesk.LIC: (C:\Program Files\Autodesk Network License Manager\License\adskflex.opt)

Options File Commands: BORROW_LOWWATER - Set the number of BORROW licenses that cannot be borrowed. MAX_BORROW_HOURS - Changes the maximum borrow period for the specified feature. TIMEOUT - Specify idle timeout for a feature, returning it to the free pool for use by another user. TIMEOUTALL - Set timeout on all features. REPORTLOG - Specify that a report log file suitable for use by the FLEXnet Manager license usage reporting tool be written. Sample Options File: REPORTLOG [+]"C:\Program Files\Autodesk Network License Manager\SamLite\report.rl" MAX_BORROW_HOURS 480 TIMEOUTALL 39600 BORROW_LOWWATER 60200MAP_2009_0F 50 BORROW_LOWWATER 59700CIV3D_2009_0F 10 BORROW_LOWWATER 61300ARDES_2009_0F 10

. 30. 31. 31

Appendix B SAMreport-Lite Error Messages. 33
Runtime Error Messages. 34

Index. 37

vi | Contents
Quick Start to SAMreport-Lite

In this chapter

How to Obtain a License
This section gives you step-by-step instructions for installing SAMreport-Lite on your system. If you have any questions that are not addressed in this Quick Start section, consult the appropriate sections in this User's Guide.

How to Install Java

Runtime Environment

How to Install

SAMreport-Lite

How to Create and Set

Up an Options File

How to Use

How to Upgrade to

SAMreport

How to Obtain a License File
Before you install SAMreport-Lite, you must obtain a license file. SAMreport-Lite runs on any computer, but it can read only the report logs from the license server(s) where you obtain a license file. You will be asked for the location of this file during installation. To obtain a license file 1 On the server where you plan to manage licenses and report on them, click Start menu All Programs (or Programs) Autodesk Network License Manager LMTOOLS. 2 In LMTOOLS, click the System Settings tab. 3 Record the host ID, which is located in the Ethernet Address field. NOTE If your server has more than one Ethernet adapter, select one that corresponds to a physical network adapter. 4 Exit lmtools.exe. 5 Next, you need to request a license file from Macrovision Corporation. On the Internet, go to the following website: http://autodesk.globes.com 6 Follow the online instructions for requesting a license file. 7 After completing the online request for the license file, you will receive an email that contains the license information. Copy and paste the license information from the email into a text editor. Save the file with an extension of.lic or.dat. Make sure you note where you saved the file and what you named it. You will be prompted for the location of the license file during the SAMreport-Lite installation.
How to Install Java Runtime Environment
SAMreport-Lite requires Java Runtime Environment 1.4.2_04. To install Java Runtime Environment 1 Insert the Autodesk product CD into your CD-ROM drive. 2 On the Media Browser, click the Install tab. 3 Click Network Deployment.

2 | Chapter 1 Quick Start to SAMreport-Lite
4 On the Network Deployment tab, under Install Supplemental Tools, click SAMreport-Lite 3.4. 5 Click Install JRE 1.4.2, and follow the on-screen instructions.
How to Install SAMreport-Lite
To install SAMreport-Lite 1 Insert the Autodesk product CD into your CD-ROM drive. 2 On the Media Browser, click the Install tab. 3 Click Network Deployment. 4 On the Network Deployment tab, under Install Supplemental Tools, click SAMreport-Lite 3.4. 5 Click Install, and follow the on-screen instructions. NOTE During installation of SAMreport-Lite, you will be asked for the location of your license file. If you do not have a license file, follow the procedures in How to Obtain a License File on page 2 to obtain one.
How to Create and Set Up an Options File
To use SAMreport-Lite, you must configure your license server(s) to generate report logs. In the Network License Manager, you set up an Options file to enable SAMreport-Lite to create report logs. NOTE Complete instructions for setting up an Options file are located in the Autodesk Network Licensing Guide. You can access the guide from your product's Media Browser or in the Help system. To create and set up an Options file 1 In a text editor, create a file called adskflex.opt. 2 In the adskflex.opt file, enter the following syntax on a single line:
REPORTLOG [+] report_log_path REPORTLOG must be uppercase, as shown.
In the REPORTLOG syntax, [+] means that entries to the log file you create are appended rather than replaced each time the Network License
How to Install SAMreport-Lite | 3
Manager is restarted. (It is recommended that you use this option so that you retain a history of log entries.) Path names that contain spaces must be enclosed in quotation marks. For example, the syntax REPORTLOG + c:\My Documents\report.rl means that a report log named report.rl is located in the folder c:\My Documents. 3 Save the adskflex.opt file to the same location where your license file exists. 4 Stop and then restart the Network License Manager.
How to Use SAMreport-Lite
To use SAMreport-Lite to generate a report 1 Click Start menu (Windows) All Programs (or Programs) SAMreport SAMreport. 2 In the SAMreport-Lite window, click the Browse button. 3 In the Report Log dialog box, locate and specify your report log file. By default, the Report Log dialog box lists only files named with a.rl file name extension. If your report log file has a different extension, such as.log, open the Files of Type list and select All Files to list all the files. 4 In the SAMreport-Lite window, in the Output File box, specify the folder location and file name for your report output files. You do not need to specify the file name extension; the extension is automatically added to the name you supply based on the output formats you select. For example, if you select HTML and Text output formats and specify c:\my documents\report in Output File, the following report files are generated: c:\my documents\report.html c:\my documents\report.txt NOTE Be sure to specify the full path name for your output files. If you don't, output files are written to the current working directory, which may be the Windows desktop. Specifying a full path name ensures that your report files are saved in the folder you choose. 5 On the Report menu, click Generate. 6 The report you specified is generated.

4 | Chapter 1 Quick Start to SAMreport-Lite
For more information about generating reports, see Basics of Generating a Report on page 11 and Usage Summary Report on page 15.
How to Upgrade to SAMreport
The full-featured SAMreport product provides additional types of reports and options, and includes additional features such as command line batch processing. Upgrading to the full version of SAMreport does not require a new installation, just a new license file. To learn about the full-featured version of SAMreport, go to the Macrovision Corporation website at: www.macrovision.com
How to Upgrade to SAMreport | 5

Introduction

Intended Audience About This Manual What is License
This chapter contains introductory information about license management, a description of SAMreport-Lite and explanatory information about this guide.

Management?

What is SAMreport-Lite

Intended Audience

SAMreport-Lite and this manual are intended for use by system administrators, system analysts, and managers who use FLEXlm license management to produce usage reports for your software.

About This Manual

This manual is divided into five chapters and two appendixes: Quick Start to SAMreport-Lite on page 1 provides quick instructions for installing and using SAMreport-Lite. This chapter defines license management and introduces SAMreport-Lite. Basics of Generating a Report on page 11 contains instructions for generating a Usage Summary report from the SAMreport-Lite interface. Usage Summary Report on page 15 describes the Usage Summary report, and describes how to arrange report output. Report Input and Output on page 21 shows how to specify input files and describes output formats. Enabling and Managing Report Logs on page 27 provides guidelines for enabling and managing report logs. SAMreport-Lite Error Messages on page 33 lists some errors that you might get while running SAMreport-Lite.
What is License Management?
License management is a set of technologies that monitors the use of software. In some cases, it may also limit use of a product or record usage of a product. Most software companies have legal agreements that detail the obligations of the manufacturer and user to each other. These agreements are often referred to as licenses. Some companies also include license management technology to simplify the legal use of their products. Throughout this documentation, the term license refers to a token obtained through some electronic technology, not the legal agreement between a customer and a software vendor. License management is embedded into a software product by the software vendor.

Version

List of input report log(s) Name of report output file Earliest start date in any report log Latest end date in any report log Date to begin reporteither a filter start date or the starting date of the earliest report log Date to end the reporteither a filter end date or the ending date of the latest report log Duration in real clock time between the report start and end dates that a license server was up Vendor daemon name(s) Report breakdown categories, if any Date set to start report, if any Date set to end report, if any List of event filters for the report, if any List of time period filters for the report, if any List of features in the scope of this report (that is, not filtered out) that have license activity displayed in the report List of features in the scope of this report (that is, not filtered out) that do not have license activity displayed in this report

Features Without Usage:

A Usage Summary report with default settings contains one line per feature and 11 columns per line. From left to right in the report, the columns are:
16 | Chapter 4 Usage Summary Report

Category

Available

Column Heading

max hours

Description

Maximum number of available licenses. Includes overdraft licenses. Number of available hours of license usage. Total number of license requests. Number of licenses requests fulfilled. Number of license requests queued. Number of license requests denied. Number of license requests not fulfilled because the feature is unsupported. Percent of license requests that were denials. Maximum number of licenses used simultaneously. Includes overdraft licenses. Number of available license hours used. Percent of available license hours used.

License Requests

total used que den unsup %den

max hours %hrs

Usage Summary Report Output | 17
Possible explanations for denials in reports where the maximum available number of licenses were never used include: The number of available licenses changed during the report period. For example, you start your report log when you have 10 licenses of FeatureA, then a few months later, still writing to the same report log, you add 10 more FeatureA licenses. Your report might show the max available licenses = 20, max used licenses = 18, and denials. Remember that the denials may have occurred when you only had 10 licenses available. Licenses are reserved for particular users. Even though all licenses for a feature are not checked out, they are not available to all users. If someone outside the reservation group tries to check out a reserved license, that user will be denied a license. License reservations are set in a vendor daemon's options file. Users are excluded from the group of users who can check out a license. Even though all licenses for a feature are not checked out, a particular user may be excluded from using a license and gets a denial when trying to check out a license. Exclusions are set in a vendor daemon's options file.

Output Arrangement and Detail
The Usage Summary report shows license usage by feature. To create a report that shows more detail about the nature of license usage, you can use a combination of: Summary period
18 | Chapter 4 Usage Summary Report
Breakdown category Sort order specification Feature description Using these controls, you can decompose the usage of each feature into useful groupings according to your particular reporting requirements. You may use the Summary choice lists in the SAMreport-Lite main window, which provide easy access to the Feature, User Name, and User Host Name breakdown categories. You will notice that changing the breakdown settings automatically changes the sort order to defaults that correspond to your breakdown settings. If you specify multiple breakdown categories, the resulting report shows use of features by each unique combination of breakdown categories.
Output Arrangement and Detail | 19

Report Input and Output

Specifying Input Report
You can create reports using one or more report logs from one or more FLEXlm vendor daemons, as long as each report log is written by a single vendor daemon running on a single host. (Each redundant vendor daemon must write to its own report log.)

Displaying Output to the

Viewer Window

Navigating the

SAMreport-Lite Viewer Window

Selecting Output Type

and Output File Names
Output Formats Data Filters Reports and Time Zones Setting Start and End

Dates for a Report

Specifying Input Report Logs
The only valid input files are FLEXlm report logs. These report logs may have been produced by redundant license servers or distributed license servers, or they may simply be archived report logs from one or more license servers. Report logs must be accessible to SAMreport-Lite. Enabling and Managing Report Logs on page 27 describes how to start and manage report log files. You must specify at least one report log before running a report. You must specify the location of each of the report logs you want to run with SAMreport-Lite using one of the following two methods. Type the path to the report log in the text field to the right of the Browse button. Press Enter. Repeat this process for each report log that you want to add. Click the Browse button and use the report log file browser to select a report log from your system. Double-click the report log file. You can repeat this process to select more than one report log from the browser. After you select a report log, the report log file name appears in the text box above the Remove button. To remove a report log from the list, click to highlight the report log, then click the Remove button. There is no fixed limit on the size of a report log that you run through SAMreport-Lite, but the execution time of a report is proportional to the amount of report log data that is processed.

Displaying Output to the Viewer Window
All reports generated in the SAMreport-Lite interface are displayed on the screen in a SAMreport-Lite Viewer window, even if you specify one or more output files.
Navigating the SAMreport-Lite Viewer Window
The SAMreport-Lite Viewer window is divided into two sections. A list of the titles of individual pages of a report or a list of output formats is displayed in the left side of the SAMreport-Lite Viewer. A textual page of a report is displayed in the right side of the Viewer. If the displayed page is longer than the display space (often the case with textual report output), you can read the rest of the
22 | Chapter 5 Report Input and Output
page by moving the scrollbar at the right margin of the Viewer. A navigation toolbar and report progress indicator are displayed at the top of the Viewer. You can display different pages or output formats of a report in one of three ways: Click the page name in the left side of the window. Click the Back and Forward buttons in the toolbar. Select Next or Previous from the Page menu.
Selecting Output Type and Output File Names
Different output formats are available; unavailable output formats are grayed out. All reports written to files require an output file name base and at least one output format selection. The file name base can be entered in one of two methods: Type the path and file name base in the text field to the right of the Output File button. If no path is specified, the files are written to the current working directory. Click the Output File button to open a file selection browser. Find and double-click the directory in which you want to save the output file. Type the file name base in the file selection browser. Click the Save button. The appropriate file name extension is automatically appended to a file name base, depending on the files's output format: Output Format
HTML Text Report Interchange Format See a description of RIF in Output Formats on page 24.

File Name Extension

.html.txt.rif
SAMreport-Lite will not warn you if the output file that you are defining already exists and that you are about to overwrite it.
Selecting Output Type and Output File Names | 23

Output Formats

Usage Summary reports are available in the following formats: Text. This format is suitable for printing and reading, but not for parsing. HTML. This format is suitable for posting textual reports to a web page. Report Interchange Format (RIF). This format is a simple, flexible, plain text format that is designed to pass tabular information between the report generator and another program, such as a spreadsheet. Fields are delimited by multiple spaces. Textual reports are written to a single RIF file; each page of a multipage graphical report is written to a separate RIF file. Sequential numbers (starting with 0) are appended to the file name base of the RIF files and they have the extension.rif. A Table of Contents RIF file is generated for each RIF report and is named output_filename_base _toc.rif.

Format Specification:

#BEGIN HEADER header lines #END HEADER #cols [#rows] name of dataset column labels [rows] // These lines contain // info for the first // table.
If you break down data by more than one category in a Usage Summary report written in RIF, each of the categories is presented in its own column. More than one table may be contained in a RIF file. The #rows entry is not present if the file contains rows from only one table. If the #rows entry is missing, read all of the rows until the end of the file. If there is more than one table in the RIF file, the table-specific portion of the format is repeated for each additional table.
#cols [#rows] name of dataset column labels [rows] // These lines contain // the first table. //
24 | Chapter 5 Report Input and Output

Data Filters

Some of the information contained in the report log is subject to filtering. Two filters can be specified for a Usage Summary reportfeature and user. Multiple filter categories for one report are applied with a Boolean AND operationall the specified conditions must be satisfied. If a report is filtered on user==User1 and feature==Feature2, the resulting report contains usage of Feature2 by User1. Multiple instances of a single filter category are applied with a Boolean OR operation. If a report is filtered on user==User1 and user==User2, the resulting report contains usage of features by either User1 or User2. Multiple filter values for the same filter category can be specified on the same line separated by a space or on separate lines. For example, user==User1 User2 is equivalent to user==User1 and user==User2.

Reports and Time Zones

Timestamps in a report log are determined by the clock on the license server machine. The times are converted from the time zone of the license server machine and stored in the report log in Greenwich Mean Time (GMT), also known as Universal Time (UTC). Therefore, the data in a report log is insensitive to time zones, and you can run a report using report logs that were written on machines in different time zones without compensating for time differences. Reports, on the other hand, show time using the time zone set on the machine where the report was generated. SAMreport-Lite translates times in UTC from the report log using the offset for the time zone of the machine on which SAMreport-Lite is running. For example, if you have an event in a report log that was written at 1pm by a vendor daemon running on a license server in the US Eastern time zone, its timestamp in the report log would be written as 6pm GMT. If an event in a report log was written at 10am by a vendor daemon running on a license server in the US Pacific time zone, its timestamp would also be written as 6pm GMT. If those two report logs were used to generate a report in the US Pacific time zone, those two events would both be reported at 10am. If the same report were generated on a computer in the US Eastern time zone, the events would both be reported at 1pm. Possible causes for the times in reports that are different than you expect are: The time zone on the license server machine is set incorrectly. If the time zone is not set correctly, and the system clock has been set to show local

Data Filters | 25

time, an error is introduced into the UTC timestamps recorded in the report log. The time zone on the machine where SAMreport-Lite is running is set incorrectly. Even if the clock time looks correct, the time zone may not be set correctly.
Setting Start and End Dates for a Report
Start and end dates for report output can be set in text fields in the middle portion of the SAMreport-Lite main window. Times can be included. If no start and end dates are set, the report is generated with data from the entire report log. If no time is specified, days begin at midnight, 00:00:00. The following formats are accepted for 3:30 pm on January 31, 2007:
MM/dd/yyyy HH:mm:ss MM/dd/yyyy HH:mm MM/dd/yyyy yyyyMMdd HHmmss yyyyMMdd HHmm yyyyMMdd MMM dd, yyyy HH:mm:ss MMM dd, yyyy HH:mm MMM dd, yyyy 1/31/2007 15:30:00 1/31/2007 15:30 1/31/Jan 31, 2007 15:30:00 Jan 31, 2007 15:30 Jan 31, 2007
HH is measured by a 24-hour click (0-23). MMM can be either the three-letter abbreviation for the name of a month or the full name of the month (Jan, January, jan, january, JAN, JANUARY).
26 | Chapter 5 Report Input and Output
Enabling and Managing Report Logs

How to Turn on a

To use SAMreport-Lite, you need one or more report log files that are accessible to SAMreport-Lite. Each report log must be written by a single vendor daemon on a single host. (Vendor daemons running on more than one server must each write to their own report logs.) SAMreport-Lite cannot produce reports from debug log files (lmgrd's standard output).

Report Log

Size of the Report Log Flushing Data to a Report
Managing Report Logs Avoiding Corruption in

Report Logs

How to Turn on a Report Log
SAMreport-Lite can read report logs that are accessible to the machine where SAMreport-Lite runseither by being located on the machine where SAMreport-Lite runs or via a network share. After you enable report logging with the following method, your vendor daemon will be writing a report log from which you can generate a report with SAMreport-Lite. Depending on your license usage, you should wait a few hours or a few days before generating a report from this report log. The options files and license files for each license server in a redundant license server configuration must also be set up in order for report logging to continue when the master changes. If a master license server goes down, the new master will read its license and options files and write to its own report log. To enable report logging for one of your Flexlm vendor daemons 1 Create an options file for the vendor daemon, if one doesn't already exist. The options file is a plain text file with any name (we recommend an.opt extension). For example, for a vendor daemon called vend, the options file could be: C:\Program Files\Autodesk Network License Manager\vend.opt 2 In the options file, enter a line of the following form:

Size of the Report Log | 29
4 Archive (and probably compress) a report log when it is no longer needed to run reports. You must rotate a report log at the following times: If you move the license server to a new machine. If SAMreport-Lite detects that the license server hostid changes in a report log used to generate a report, it will stop processing the report log and include only the data preceding the hostid change in the report. If a vendor daemon name changes. If SAMreport-Lite detects that the vendor daemon name changes in the report log used to generate a report, it will stop processing the report log and include only the data preceding the vendor daemon name change in the report. You may want to rotate a report log at a regular time interval, such as weekly or monthly, depending on how quickly the report log grows. The rotation of a report log does not need to be tied to the interval over which you run your reportsremember that you can run a report on multiple report logs and that you can filter report data with designated start and end dates. You may also want to rotate report logs when the license limit for a feature changes, but alternatively, you can also set start and end date filters to isolate usage for given license limits. NOTE You can corrupt a report log by rotating it incorrectly. A report log must begin with a header that is written by the vendor daemon. Without this header, the report log is corrupted. The data in the report log is unusable and unsalvagable from the start of the report log until the first time in that report log that the license server is restarted. The report log will have no header and will be corrupted if you manually copy an active report log to a new file name, delete the original active report log, and keep the vendor daemon writing to the original active report log file name.
Finding the Version of the Vendor Daemon and lmswitchr
How you are able to rotate report logs depends on the version of the vendor daemon and lmswitchr that you use. The -switchlog batch option in SAMsuite uses lmswitchr.
30 | Appendix A Enabling and Managing Report Logs
Find the version of the vendor daemon. To find the version of a vendor daemon, start lmtools, the FLEXlm utility. Select the Utilities tab where you can find the version of FLEXlm that is built into a file. Enter or browse to the vendor daemon and click the Find Version button. The FLEXlm version will be displayed at the bottom of the lmtools window. lmswitchr is found in the lmtools interface. Check the version of lmtools (and therefore lmswitchr ) by selecting Help About.
Rotating a Report Log with lmswitchr
This method of rotating a report log is recommended if you are not using SAMsuite. 1 Start lmtools. In the Service/License File tab, select the license server whose report log you want to rotate. Click the Switch Report Log tab. Type the Vendor Name and the New Report Location. Be sure to specify a new file name (do not reuse the old file name) for the new report log. Click the Switch Report Log button. 2 Edit the options file with the new report log path and file name. If the license server goes down and comes back up, the vendor daemon will read its options file and will continue to write to the new report log. For redundant license servers, update each of the three options files. 3 Move the closed report log to where it can be accessed for reporting and storage. You will move one report log for a single license server and up to three report logs for a redundant license server. 4 Eventually you will not need to run reports on some of your old report logs. Those report logs can be compressed and archived to a location that does not necessarily need to be accessed by SAMreport-Lite.

Avoiding Corruption in Report Logs
Flexlm has been improved from version to version to make report logging more robust. Nevertheless, particularly in older versions of the vendor daemon, corruption can occur in the report log. Follow these guidelines to avoid corrupt report log files: In pre v 5.1 vendor daemons, rereads, and shutdowns could possibly introduce corruption, particularly if the server is busy. With these older vendor daemons, the best policy is to issue reread or shutdown when no licenses are checked out, if possible.
Rotating a Report Log with lmswitchr | 31
Issuing an lmdown command while the server is shutting down can cause corruption. Don't move, copy, or edit the report log file while the server is running. Never configure more than one license server to write to the same report log file. In the case of a redundant server, each vendor daemon must write to a distinct file, preferably one which is local to the server machine. Even if the report log is not corrupted, SAMreport-Lite will not run a report using a report log that has been written by a vendor daemon running on more than one license server machine. Never configure different vendor daemons to write to the same report log file. Even if the report log is not corrupted, SAMreport-Lite will not run a report using a report log that has been written by more than one vendor daemon. Do not use lmswitchr or -switchlog to switch the report log to an existing report log file. Switch to a file with a new name. Never hand-edit a report log or combine report logs together into the same file. If you change a server host name, make sure you stop the license manager and create a new report log when the name change is complete.
32 | Appendix A Enabling and Managing Report Logs
SAMreport-Lite Error Messages

Runtime Error Messages

This section lists SAMreport-Lite runtime error messages and the output report log details.

Runtime Error Messages

The following runtime error messages may be written to the Status History tab of the SAMreport-Lite interface or to a terminal window: Error
Error: Report log has been corrupted (-4) file line no (id 50)(minor -1) (Invalid key found, record lost) Error: Internal Error (-7) file line no (id 54)(minor 0) feature key Error: A reportlog is missing (-9) file line no (id 40)(minor 0) feature key Error: Reportlog is truncated (-11) file line no (id 48)(minor -5) (Vendor daemon crashed and restart)

Output Report Log

Corrupt report log event found in a report log. May be associated with a vendor daemon crash. Indicates an unexplained problem in SAMreport-Lite. This error should be reported to Autodesk. Report log contains a gap of significant duration between an end (or lmswitchr) and the following start event. Report log event fragment is seen immediately followed by a restart. The feature corresponding to the event fragment is undetermined. Usually caused by vendor daemon crash. Report log event fragment is seen immediately followed by a restart. The feature corresponding to the event fragment is shown. This event is unusable. Usually caused by vendor daemon crash. Report log file ends abruptly. Probably caused by reading or copying the report log while the vendor daemon is running. Could also be the result of a vendor daemon crash with no subsequent restart. No matching checkin event found for a checkout event. Because the error is reported much later than the actual error occurred, the line number is not particularly relevant. Sometimes this error is reported in error.
Error: Reportlog is truncated (-11) file line no (id 48)(minor -5) (Vendor daemon crashed and restart) feature key
Error: Reportlog is truncated (-11) file line no (id 42)(minor 0) feature key
Error: An error was found in the reportlog (-13) file line no (id 51)(minor -4) (Checkout occurred without checkin, recovery attempted) feature key
Error: An error was found in the reportlog (-13) f Indicates corruption in one of the report event ile line no fields. (id 37)(minor -7) (A data field is corrupted, record recovered, field recovery attempted) feature key Error: end date may be using 2 digit year instead This is an example of an error that occurs when of 4 digits Error occurred: gsi. SAMreport-Lite.JrepException: a parameter or an argument is invalid and a Unable to generate report. report cannot be generated. The first line
34 | Appendix B SAMreport-Lite Error Messages
describes which parameter or argument is invalid.
Error: In file vendor changed from vendor_name1 (hostid1) to vendor_name2 (hostid2). No further events will be read from this file. Error reporting threshold of 2000 has been reached. No further errors will be reported.

This report log has been written by more than one vendor daemon or by a vendor daemon running on more than one hostid. Corruption: Significant corruption in the input report log(s) has rendered parts of this report suspect. Please contact your Autodesk dealer or reseller.
Runtime Error Messages | 35
combining report logs 21 report log file 2122, 25, 2829 enable 28 from redundant servers 22 manage 29 size 29 time zones 25 using multiple 21 reports 13, 21, 26 combining report logs 21 date formats 26 errors/warnings 13 start and end dates 26 using multiple report logs 21 rotate report log 29
date formats, for reports 26

enable a report log 28

formats, date 26

size of report log 29

manage report log 29 merging report logs 21

time zones 25

redundant servers 22 report logs 22

37 | Index