XANSYS Message: 7155 [Go back to message list]
[bookmark on del.icio.us]
No rating yet
Rate item:

Subject: Re: License Manager problems in ANSYS
Author: Sheldon Imaoka
Date: 1999-12-22 02:08:00

License Manager problems in ANSYS
Hello Venkat,
I'll attempt to see if I can answer your question:

The first thing I'd like to point out is that ANSYS actually uses Elan
licensing for ANSYS 5.4, 5.5, and 5.6, *not* FlexLM. ANSYS used to use
FlexLM in revision 5.3, I believe, but 5.4 through 5.6 are FlexLM. I'm
assuming you're using 5.4 and above? (The reason why I ask is that the
following commands are Elan commands, not FlexLM commands)

There are several things you can do to "kill" or release a license, even
without system administrative priviledges.

1) On UNIX, you can create a "wheel" group to give users administrative
priviledges for ANSYS licensing *without* giving a user "regular"
administrative rights. The "wheel" group is used by Elan licensing and does
not provide a user with regular system administrative rights on the
workstation. You sys admin shouldn't have to worry about creating this
group as a result. This allows a regular user in the "wheel" group to kill
a specific client(s). Please see the ANSYS Installation and Configuration
Guide, Appendix A, for more details about the wheel group and how to create
one (basically, it is modifying the /etc/group file to create this group).

2) A user should be able to kill his/her own client from the server
without special administrative rights (as mentioned above). For the
command-based method, use the "elmadmin" command. It is located as follows:
UNIX:
/ansys55/licutil//elmadmin
Windows:
C:ansys55licutilintelelmadmin
where is your UNIX platform (e.g., "usparc", "sgi32", etc.). You
can add the above directory to your PATH (in UNIX and Windows), so you don't
have to type it the full pathname all the time. To list the clients, type:
elmadmin -l
This will list clients with client ID (CID). Find that CID and then type:
elmadmin -b #
where # is the CID from above.

3) You can perform the same tasks as point (2) above with a GUI-based
administrative utility (instead of a command-based utility). To do so:
UNIX:
/ansys55/licutil//xelmadmin
Windows:
C:ansys55licutilintelwlmcntrl
This is more user-friendly since it is GUI-based. Please see the ANSYS
Installation and Configuration Guide on more details on how to use these
utilities (it's not hard to use, but it takes a bit longer to explain than
the command-based method, so please refer to this document for the various
options).

I hope the above helps. Points (2) and (3) shouldn't require administrative
rights. Also, if you're familiar w/ UNIX commands, you can probably create
a simple csh script which will kill your own license on your workstation
(license server) to automate this process. There's a few other ways to
"release/kill" your license after an abort, but the above may suffice as a
first step.

Best regards,
Sheldon
CSI

----- Original Message -----
To: xansys@o...
Sent: Tuesday, December 21, 1999 8:41 PM

Hello All,

Typically we are installing ANSYS on Individual machines making each
machine a license server. This we are doing so because if multiple licenses
are loaded on a single machine and it serves as a server, in case of system
break down nobody could use ANSYS.
Hence My colleagues and my self find lot of problems with the Flexlm
license manager ANSYS is currently using. When the ANSYS run gets aborted
the license does not become free. When you try to invoke the license
manager it says you shall not be able to restart the license manager since
you re not administrator. you got to try many times to get ANSYS invoked.
Most of the times ANSYS says no licenses available and aborts the session.
Pro/Engineer by PTC uses a similar license manager. But they use a
tool called Pro/Flush. When a run gets aborted, one can run this application
which frees all the unused and frozen lines. May be ANSYS INC. also should
think in those lines and facilitate users to come out of this embarrassing
situation.


Posts possibly associated with message #7155AuthorDateScore
7153License Manager problems in ANSYSVenkateswarlu Gattineni1999/12/21 
7155Re: License Manager problems in ANSYSSheldon Imaoka1999/12/22 
7158Re: License Manager problems in ANSYSSheldon Imaoka1999/12/22