· Oct 11, 2021

Every time we use the command "job" a new license is consumed?

We have in our company a task that use many times a job command, and we receive this message "<LICENSE ALLOCATION EXCEEDED>". I thought that a new license is consumed only when we acess with another IP address the database.

Can anyone explain this to me?

Discussion (4)1
Log in or sign up to continue

The license-mechanic is a little bit complicated:

  • users are identified by  username@  (as mentioned already)
  • every new process consumes a license slot over its lifetime
  • each user gets a set of license slots  (typically 25)
  • once this limit (25) is exceeded ALL 25 slots are converted to normal (non-licenses)

As a consequence, a request for license number 26 consumes 25 additional licenses for that user !!
And these licenses come back to in the license slot mode only if ALL processes of that user are terminated
So using a single user (e.g. from CSP) is rather risky in that relation

$system.License.Login()  may help you cross that limit.
from docs:

This function will relinquish a license if the session/process is already holding
one under a different identifier and it will obtain a new one on the behalf of the
user ID provided.

If the MAXCONNECTIONS connection limit per user is exceeded,
the usual transition to one-license-unit-per-connection
will apply to this user identifier.