When you purchase licenses for Sybase Adaptive Server products, you are issued a Sybase Software Asset Management Certificate. The certificate has the following information for each product:
Order Number
Feature Name
Feature Count
Software Version
Authorization Code
Product Description
This information is used by SySAM to build the license file, with new licensed features appended to the end of the file. If license keys are not working, it may be that the information entered on the License Entry application (lmgr) was typed incorrectly. In this case, you can check the license key in question (for example, ASE_HA) to make sure the information is correct. If an error was made, you can correct it using a text editor.
Here is a sample license key entry from a license.dat file with information on how to map the information in the license file to the information that appears on the Sybase Software Asset Certificate.
INCREMENT ASE_HA SYBASE 12.5 permanent 5A234B567C890\ OVERDRAFT=10000 ck=0 SN=30181-4
INCREMENT - indicates that the count of this license key will be added to the count of any other license keys for the same feature (all SYBASE license keys use INCREMENT).
ASE_HA - is the Feature Name entered.
SYBASE - identifies this license key as belonging to the SYBASE vendor daemon (case sensitive, must be uppercase).
12.5 - the Feature Version entered.
permanent - indicates this license has no expiration date (some license keys have a date instead.)
5 - is the Feature Count entered.
A234B567C890 - is the Authorization Code entered.
OVERDRAFT=10000 - indicates that you can check out more features than you are licensed for, but you will be warned that you have overused your license (case sensitive, must be uppercase)
ck=0 - the checksum (it is not used and is usually 0).
SN=30181-4 - the Order Number entered (case-sensitive, the SN part must be uppercase.)
Many of the fields in the license key are case sensitive; you must take care when editing a license key. The only time you should edit a license key is when the values have been entered incorrectly and the key is reported as invalid. Making any change to a license key that is valid makes the license key invalid.
The file is located in $SYBASE/$SYBASE_SYSAM/licenses/license.dat.
