license count, -n setting, watchdog and odbc connections

M

MaxarK

New Member
Hi all,

Just need to clarify what our understanding is for setting -n.

Running several databases, I'm mainly Workgroup licensed, so I start with -n set to the license count I've been given. Let's call it the base count.

  • I'm running watchdog on each database, since this uses up a seat in the user count can I bump up the base count by 1 for -n or is this the price we pay for WDOG?

  • On some databases I'm also connecting by ODBC - to do this I have a separate Client Networking license. However, when connected, it uses up another seat in the user count. In this case can I bump up the base count for -n by my extra Client Networking license count? Or is it tied to a Workgroup license?
Thanks for any feedback.
 
Thanks for your reply, Tom.

Disregarding the -n value for the moment, how about in the context of keeping within terms of the license? Are we entitled to have those extra concurrent connections based on each of the 2 points I mentioned above?

Regarding the -n values and why we're setting them low, we had an audit from Progress last year and they required us to back pay maintenance and continue paying for the maximum number of users that were ever recorded, per database, and they weren't interested in hearing about the type of connection at those peaks (training days, a dev might have been doing a performance test, site disbanded from dozens down to a couple of users for the past 10 years, etc). The cost was absolutely ridiculous so we're playing it safe by limiting connections. Do you suggest we limit users through other means?

Thanks!
 
OK thanks MaximMonin, will report it to the devs. I would still like to clarify the concurrent user count we're entitled to based on my original points with context of keeping within license terms.
 
Sorry I have found a reference to wdog and licensing and the KB article. Only interested in the Client Networking question now.

Thanks
 
_Licence._lic-validusers - it is max valid users count
_Connect - table to grab all current connection and split them on types.
 
-n is not related to licensed users. It never has been and never will be.

Most of these audits are mere "fishing expeditions".

If you (or anyone else) is ever subjected to an "audit" I very strongly suggest that you do not let the auditor set foot in your shop until they first define exactly what the terms of the audit are and exactly what it is that they will be counting. Then demand that they show you the license policy guide and explain how their methodology adheres to that policy (hint: -n does not figure into *any* of the published materials).

Sales people are only paid for new licenses. Their sole incentive is to find you liable for new licenses. If you let them in the door they will always find that you are out of compliance and in need of new licenses. Push back. Escalate. Demand to see the policy in writing, in advance so that you can conduct your own audit ahead of time. Be prepared to defend your position.

The mere act of demanding your rights usually stops the "audit" in its tracks because you are no longer the "easy money". Unfortunately far too many people just "roll over" and acquiesce to this nonsense. Of course they nurse a grudge against Progress for the sales person's malfeasance but the sales person doesn't care -- they've collected their commission and moved on.
 
A "user" is just that -- a user, sitting in a chair using an application.

Depending on your version of Progress and the license model chosen (concurrent users is one of several) there are many possible ways to count licenses. None of which involve -n.
 
-n is just the number of processes that can connect to a database ( which includes asynchronous page writers, the watchdog, your batch processes which run on the server, etc. ). There is absolutely no relation to the licenses bought - be they concurrent user ( up to Progress V9 ), registered client or named user or whatever.

There are two additional facts which you need to take into account when facing a Progress sales rep trying to convince you to buy more licenses:

  1. Progress does not have any license management built into their product. All they can do is count the processes which are connected to a database at a single point in time which is the data you will see in the infamous .lic file which will then be the basis for an audit. Some think this is on purpose ...
  2. Most Progress sales reps I met in the past did not understand Progress' licensing model. That means that they will always interpret it in favor of their commission regardless what's best for the customer. At this point I should note that I do know one of this rare species who does understand their licensing model and tries to use it not only in favor of his commission ...

HTH, RealHeavyDude.
 
Yes, ODBC users are still users. The Client Networking license is for the client end of the connection, not the database end.

Note that user <> session. Under the concurrent user license, a "user" is a "person" sitting at a "device". If such a person has six simultaneous connections open to the database on that device, it is still only one user. This is why -n is not effective for license management since it is counting connections, not users. Also, generally batch processes do not count as users unless there are more batch processes than people.
 
Thanks all for your replies, it's a lot more clear to me now.

Long story with the audit, Progress devs and sysadmins weren't consulted during the process so it was out of our hands. In fact our contract management people were angry at me for providing actual usage stats (to someone else in the organisation, after all was signed) that contradicted what they agreed to pay for.
 
You must log in or register to reply here.
Back
Top