To summarize - (Thanks to all that replied - especially PTC):
License Borrowing does affect the headcount of licenses on the server.
It will make those borrowed licenses unavailable for the rest of the
users during the timeframe of the borrowing.
Therefore, in my example: If I have 10 Pro/ENGINEER Flex3C floating
licenses served from a centralized location, and I want to borrow one of
these to work at home the next day, I would do the following:
1. On my network where I can see the existing license server, I would
run proe_borrow.bat from my local client's \loadpoint\bin directory.
2. In the "Startup Configurations" area of this utility, I would select
the startup configuration that I wanted to borrow.
3. In the "Borrowing Period in Days" portion, I would select "1" since I
want to borrow it one day. At the bottom of this utility, it will show
me the start date, and the end date (expiring at 11:59 pm on the end
4. Click on "Start", which will launch the selected Pro/E configuration
and you will be in "borrow" mode.
5. Once Pro/E has started, you can check out any floating options that
you would like to borrow that are not built in to the selected startup
6. Exit Pro/ENGINEER. For Windows systems, the license is created in
the registry under the current user. On UNIX systems, the license is
created in the $HOME/.flexlmrc directory. The LM_BORROW environment
variable is created and stores the information.
At this time, you can take your system off the network, and it will
start to use the borrowed license.
DURING THIS TIME - The server now indicates that one of the licenses is
borrowed, thus reducing my available number of licenses for on-site
users to 9. At midnight on the day after my end date, the server
automatically releases this borrowed license. PTCSTATUS can be used to
show this borrowed status.
TO USE BORROWED LICENSES: You must first contact PTC Order & License
Management and have them generate new license codes that include a
special line in the Increment that indicates that borrowing is allowed
for that license. You must also be running the FlexLM version that
comes on your Wildfire 2.0 CD (Version 8.4a or later), and your licenses
file should indicate version 25 (the simplified version for 2.0).
Here's the last bit of information related to this functionality. As of
Wildfire 2.0, build F000...
Only Wildfire 2.0 software will work with this license borrowing, even
if you are successfully running 2001 and Wildfire 1.0 with the 2.0
license file in place. This is due to the "Borrow" keyword in the
license file. See TAN 125362 - SPR 1078914
Also, once the license is checked out, you can not use PTCFlush to clear
it from the server, and the maximum number of days you can check out a
license is 5. I checked with PTC, and found out that even if you stop
and re-start the flexlm service, it will remember which licenses were
borrowed. See TAN 125363 - SPR 1065328
For more information, see the Wildfire 2.0 Installation and
Administration Guide, Page A-11.
Hope this helps.
THIS MESSAGE MAY CONTAIN INFORMATION THAT IS CONFIDENTIAL AND/OR PROTECTED BY LAW. IF THE READER OF THIS MESSAGE IS NOT THE INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY DISSEMINATION, DISTRIBUTION, COPYING OR COMMUNICATION OF THIS MESSAGE IS STRICTLY PROHIBITED. IF YOU HAVE RECEIVED THIS COMMUNICATION IN ERROR, PLEASE CONTACT THE SENDER IMMEDIATELY AND DELETE THE MESSAGE. PLEASE NOTE THAT ALTHOUGH WE WILL TAKE ALL COMMERCIALLY REASONABLE EFFORTS TO PREVENT VIRUSES FROM BEING TRANSMITTED FROM OUR SYSTEMS, IT IS THE RESPONSIBILITY OF THE RECIPIENT TO CHECK FOR AND PREVENT ADVERSE ACTION BY VIRUSES ON ITS OWN SYSTEMS .
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.