From: seamans@nlm.nih.gov (James R. Seamans)
Newsgroups: comp.sys.sun.admin
Subject: Sun Floating License for compilers
Keywords: compiler
Date: 31 Jul 92 14:37:23 GMT
Reply-To: seamans@nlm.nih.gov
Organization: National Library of Medicine

Not really sure where to post this but....


Well, I think it is about time to start a war....

I have recently received our SunPro Professional C 2.0 which includes
the SparcWorks Tools.  These tools are to be used with the coming
Solaris 2.0 Operating System, when ever.  Included in the package was
the C compiler with sbrowser for SunOS 4.1.x.


The problem I'm having, is when I read how the Floating Licensing Server
is to work under Solaris 2.0.


I quote from "Installing on Solaris 2.0 SPARCworks and SPARCcompiler,
	Part No. 800-7333-10 Revision A, July 1992."

page 29

	"SPARCCompiler and SPARCworks programs use network-based floating
	(also called concurrent usage) licenses, so that you may not need
	to purchase a license for every individual user.  When a user
	invokes a compiler or tool, a license, if one is available, is
	automatically checked out."


I'm happy with that statement, we are a small development group of 2 to 8
people who might use the development tools and compiler once a week.  I
would probably be using it on a daily basis.  To give you an idea of usage,
no one has used the compiler for two weeks. So this floating license is a
real help to us to cut cost in this branch.  There are many groups of this
type in our building who would have a license for their branch.

I now quote from "Licensing White Paper, SunPro, July 28, 1992"

	Question:

	"With previous releases of your products, I needed to license each
	potential user, regardless of whether or not the software was used
	from a single server or had little simultaneous use. How does the new
	release differ?"

	Answer:

	"SunPro's new product releases incorporating network licensing
	provide cost saving flexibilty because now you only need licenses
	for the maximum number of simultaneous user. However, you should
	expect to need a full license for each full-time developer.
	Infrequent users may be adequately supported by sharing licenses."

Yeah, Great!!!

	Question:

	"After I quit using s SPARCompiler or SPARCworks, how quickly are my
	licenses available for use by another user?"

	Answer:

	"For SPARCompilers, the time is 15 minutes.  The 15 minute linger
	prevents you from losing access to the compiler in the middle of a
	build because the compiler is invoked multiple times over multiple
	files in creating your executable. For SPARCworks, the license is
	available immediately after you have quit the last tool.  Therefore,
	in a eight-hour day as many as 32 users could access a single license
	of a SPARCompiler -- making the license of the infrequently used
	product very cost effective."



"HI Boys And Girls Can You Say IBM".

The 15 minute linger is unecessary and a hindrance to the use of the
compiler and development of programs.  There is no mention of the orginal
user being able to re-use the compiler after he releases.  Does this mean
that the linger time is forced on all users of the compiler?  Think very
carefully about this -- you use the compiler for 26 seconds.  It is now
locked out for everyone for the next 15 minutes.  If the original user can
re-use the compiler in this 15 minute period, then the queue of other users
can be longer than anticipated until the 15 minute value has been satisfied.

This idle time should be adjustable by the adminstrator to efficiently
manage the usage of the comiler.  It should not be dictated by SunPro or any
other provider.  Come on Sun this needs to be changed.

This is a very silly game Sun is playing and smells as if the upper
management of Sun just moved over from IBM.

I believe we will be looking for other vendors to supply out compiler needs.


Disclaimer applies - I speak for myself and represent myself...etc....

Jim Seamans        seamans@nlm.nih.gov
National Library of Medicine - National Institutes of Health
Bldg 38A RM 712 8600 Rockville Pike Bethesda, MD   20894
(voice) 301 496-4441   (fax) 301 402-0118