For example, QLIC='/Users/simon/q' Licensing server for kdb+ On Demand ¶Īs well as a license key file, kdb+ On Demand also requires frequent contact with the KX licensing server. Like QHOME, QLIC points to a folder, not a file. You can use the environment variable QLIC to specify a different filepath. You do not have to keep the license key file there. The default location for the license key file is the QHOME folder. If you are sharing use of a commercial license, you will probably want to set the environment variable QLIC to the path of the license key file, as below. Note the license number ( #400 in the example) and quote it in any correspondence about the license. Restart your kdb+ session and note the change in the banner. (See installation instructions for your operating system.) Save a copy of the license key file ( k4.lic or kc.lic) in the QHOME folder. Designated ContactĮach KX customer designates to two technical people as the Designated Contacts for issues with kdb+, managing licenses and downloading software. Your Designated Contact sends a copy of the banner to to request a license file by return. An API key is a token that you provide when making API calls.

The banner at the top of the aborted session contains machine-configuration information but no license information. Request an On-Demand license key file Commercial ¶Īn unlicensed kdb+ session aborts: see above. General tip 2: When using serial numbers, you should be offline or block the internet connection for that. General tip: If the most recent version is not present in the database, try the closest older serial number. Do not add the word serial at the end of the query. License key files ( kc.lic) are distributed by email. Avoid using letters before the version number. If both are found, the kc.lic file is used. M64/ 2()core 8192MB tom mb13.local license key file is k4.lic, or kc.lic for kdb+ On Demand. Without one, kdb+ signals an error 'k4.lic and aborts. If you wish to begin using kdb+ commercially, please contact License key files ¶Īll 64-bit versions of kdb+ need a valid license key file to run. Your copy of kdb+ will need access to a valid license key file. Use of commercial kdb+ is covered by your license agreement with KX.

License key for file magic