A    LMF Messages

This appendix lists and explains the messages you might encounter as you use the LMF software. The messages are listed in alphabetical order, and, where appropriate, a course of action is recommended to correct the error that caused the message.

A.1    Accessing Licensed Software

You might encounter the following messages when attempting to access software that provides full support for LMF:

Attempted usage exceeds active license units

You tried to access an activity-licensed product, but the number of units available is less than the license unit requirement for the current processor. This message indicates that the maximum number of simultaneous users of the product has been reached.

Contact your system manager to determine if the maximum number of simultaneous users can be increased. Alternatively, wait until the number of users of the product falls below the maximum and try to access the product again.

License is invalid for this version of the product

You tried to access a product but the version number on the license is lower than the version number of the product you are trying to use.

Contact your system manager. Your system manager might need to install an earlier version of the product or contact Digital for a new Product Authorization Key (PAK).

No license found for this product

You tried to access a product that does not have a valid license in the kernel cache.

Contact your system manager.

A.2    Using the lmf Utility

You might encounter the following messages when using the lmf utility:

"ALPHA" option missing from PAK entry

You attempted to register a PAK for an availability license that does not contain the ALPHA Key Option. Your system requires this Key Option.

Contact your Digital representative to obtain a new PAK that contains the ALPHA Key Option.

A license for product cannot be disabled

You tried to disable a license for the product specified.

Certain licenses cannot be disabled; for example, the license created by LMF from information in the /upgrade file.

A license for product cannot be issued

You tried to issue a license for the product specified.

Certain licenses cannot be issued; for example, the license created by LMF from information in the /upgrade file.

A license that has been cancelled cannot be enabled

You tried to enable a license that passed its cancellation date.

If you want to enable the license, you should change the cancellation date. For more information, see Section 2.8.

A license that has terminated cannot be enabled

You tried to enable a license that passed its termination date.

You should delete licenses that are passed their termination date from the license database. For information about deleting a license, see Section 2.9.

Activity charge has changed - reboot to load new license for product producer.dD The activity charge has changed for the product specified. This might happen if the license type has changed, for example, from an activity to an availability license, or if the model of system hardware has changed.

Reboot your system to fully reset the kernel cache.

"Activity Table Code" amended - protected field

You changed the Activity Table Code field.

The activity table code should be changed only by using the amend command with a suitable Product Authorization Amendment (PAAM).

"Activity Table Code" - invalid format

The activity table code you entered for the license either does not match a valid License Unit Requirement Table code or is not of the form CONSTANT=integer.

When you register the license, you must enter the activity table code exactly as it appears on the Product Authorization Key (PAK).

"Activity Table Code" missing from PAK entry

You did not enter an activity table code for the license.

When you register the license, you must enter all the data from the Product Authorization Key (PAK).

Ambiguous command string.dD The string used as an abbreviation for a command is ambiguous.

When you enter a command, you must use enough letters to distinguish it from other commands.

"Authorization Number" amended - protected field

You changed the Authorization Number field.

The authorization number should never be changed because it helps to uniquely identify each license.

"Authorization Number" missing from PAK entry

You did not enter an authorization number for the license.

When you register the license, you must enter all the data from the Product Authorization Key (PAK).

"Availability Table Code" amended - protected field

You changed the Availability Table Code field.

The availability table code should be changed only by using the amend command with a suitable Product Authorization Amendment (PAAM).

"Availability Table Code" - invalid format

The availability table code you entered for the license either does not match a valid License Unit Requirement Table code or is not of the form CONSTANT=integer.

When you register the license, you must enter the availability table code exactly as it appears on the Product Authorization Key (PAK).

"Availability Table Code" missing from PAK entry

You did not enter an availability table code for the license.

When you register the license, you must enter all the data from the Product Authorization Key (PAK).

Cannot unload this many users

You specified too many users with the unload command.

Reissue the unload command with a lower number of users. To remove all the license units for the product from the kernel cache, specify zero (0) as the number of users.

"Checksum" amended - protected field

You changed the Checksum field.

The checksum should be changed only by using the amend command with a suitable Product Authorization Amendment (PAAM).

Checksum does not validate

When you attempted to register a license, the checksum did not validate the license information you entered. The checksum contains, in encrypted form, all the license information from the Product Authorization Key (PAK). If you enter inaccurate license information, you receive this message.

Carefully review all license information on the PAK. When you register the license, you must enter all the information exactly as it appears on the PAK.

"Checksum" missing from PAK entry

You did not enter a checksum for the license.

When you register the license, you must enter all the data from the Product Authorization Key (PAK).

Combine product-authorization-number with product-authorization-number.dD The two licenses shown have been combined to form a single license in the kernel cache.

Error adding to kernel cache

A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error closing file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error closing license database filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error closing LURT file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error closing temporary file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error closing the history file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error creating license database filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error creating the history file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error determining SMM

A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error locking license database filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error locking the history file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error no entry in LURT for this SMM

The model of your system hardware does not appear in the License Unit Requirement Table.

Contact your Digital representative.

Error opening file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error opening license database filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error opening LURT file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error opening temporary file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error opening the history file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error reading kernel cache

A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error reading license database filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error reading LURT file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error reading the history file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error renaming temporary file filename to license database filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error setting the number of cpus

A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error unlocking license database filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error unlocking the history file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error updating kernel cache

A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error writing to license database filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error writing to the history file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Error writing to temporary file filename.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

Failed to create process for editor

A system error occurred, causing the lmf utility to exit with a nonzero error status.

"Hardware-Id" amended - protected field

You changed the Hardware I.D. field.

The hardware I.D. should be changed only by using the amend command with a suitable Product Authorization Amendment (PAAM).

History file locked - retrying ...

You tried to access the history file at the same time as another user.

The lmf utility will automatically grant you access to the history file as soon as the other user has finished with it.

Information provided was ambiguous; multiple licenses were found

You did not provide enough information for the command to identify an individual license for the product.

If you have two or more licenses with the same product name, you can distinguish them by specifying the producer and the authorization number.

Internal LMF error was encountered

A system error occurred, causing the lmf utility to exit with a nonzero error status.

Invalid argument string.dD The string specified was not recognized as a valid argument for the command.

For a complete description of the syntax of the LMF commands, see the lmf(8) reference page.

Invalid entry for availability/activity table code for product producer.dD The availability table code or activity table code names a nonexistent License Unit Requirement Table.

Contact your Digital representative.

Invalid LURT entry for product producer.dD The availability table code or activity table code names an invalid License Unit Requirement Table.

Contact your Digital representative.

"Issuer" amended - protected field

You changed the Issuer field.

The issuer should be changed only by using the amend command with a suitable Product Authorization Amendment (PAAM).

"Issuer" missing from PAK entry

You did not enter an issuer for the license.

When you register the license, you must enter all the data from the Product Authorization Key (PAK).

"Key Options" amended - protected field

You changed the Key Options field.

The key options should be changed only by using the amend command with a suitable Product Authorization Amendment (PAAM).

"Key Termination Date" amended - protected field

You changed the Key Termination Date field.

The key termination date should be changed only by using the amend command with a suitable Product Authorization Amendment (PAAM).

License already registered

You tried to register a license that is already in the license database.

License database locked - retrying ...

You tried to access the license database at the same time as another user.

The lmf utility will automatically grant you access to the license database as soon as the other user has finished with it.

License too small to load this many users

You specified too many users with the load command.

Reissue the load command with a lower number of users. To load all the license units for the product into the kernel cache, specify zero (0) as the number of users.

License unchanged

You left the editor, after you entered an amend or modify command, without making any changes to the existing license.

Missing arguments

You did not specify enough arguments with the command.

For a complete description of the syntax of the LMF commands, see the lmf(8) reference page.

Multiple licenses could not be combined for product producer.dD You tried to combine licenses, at least one of which has the NO_SHARE Key Option.

You cannot combine licenses that have the NO_SHARE Key Option. LMF will not combine licenses if any of the following fields are different: Issuer, Product Name, Producer, Product Token, Hardware I.D.

No entries in license database

You tried to list the contents of the license database, but the license database is empty.

No entry in the history file for this product

You specified a product name with the history command, but no LMF commands were recorded for this product. The history file records only the following LMF commands: register, enable, issue, cancel, delete, modify, and amend.

When you use the product argument, you must specify the product name exactly as it appears on the Product Authorization Key (PAK). If you use the from date argument, verify that the date you specify is not later than the date of the last command recorded for the product.

No entry in the kernel cache for this product

The product name you specified in the command does not have an entry in the kernel cache.

When you use the product argument, you must specify the product name exactly as it appears on the Product Authorization Key (PAK).

No entry in the license database for this product

The product name you specified in the command does not have an entry in the license database.

When you use the product argument, you must specify the product name exactly as it appears on the Product Authorization Key (PAK).

No valid license was found for this product

You tried to load an invalid license for a product.

Make sure that you entered the correct product name and that the license is not terminated, disabled, or canceled.

Not enough memory

A system error occurred, causing the lmf utility to exit with a nonzero error status.

Not enough units to load product producer.dD You tried to load a license for the product specified, but the license does not have enough license units for the current hardware system model.

For a full description of how to provide more license units, see Section 2.10.1.

"Number of Units" amended - protected field

You changed the Number of Units field.

The Number of Units field can either be changed by using the modify command on a license that has the MOD_UNITS Key Option or by using the amend command with a suitable Product Authorization Amendment (PAAM).

PAK not registered

You left the editor, after entering a register command, without saving the file.

Permission denied

You tried to execute an lmf utility command but are not logged in to the system as superuser (root login).

Log in to the system as superuser and reissue the command.

"Producer" amended - protected field

You changed the Producer field.

The producer should never be changed because it helps to uniquely identify each license.

"Product Name" amended - protected field

You changed the Product Name field.

The product name should never be changed because it helps to uniquely identify each license.

"Product Name" missing from pak entry

You did not enter a product name for the license.

When you register the license, you must enter all the data from the Product Authorization Key (PAK).

"Product Release Date" amended - protected field

You changed the Product Release Date field.

The product release date should be changed only by using the amend command with a suitable Product Authorization Amendment (PAAM).

"Product Token" amended - protected field

You changed the Product Token field.

The product token should be changed only by using the amend command with a suitable Product Authorization Amendment (PAAM).

The kernel cache is empty

You tried to list the contents of the kernel cache, but it is empty.

The license database file filename is corrupt - restore most recent backup

The license database file has been corrupted by some means and cannot be read by the lmf utility.

The license database is incompatible with this version of lmf

The license database was created by a version of LMF that is different from the one you are using. The version of LMF you are using cannot use the license database.

Contact your Digital representative.

The LURT file filename is corrupt - restore most recent backup

The License Unit Requirement Table has been corrupted by some means and cannot be read by the lmf utility.

Restore the named file from a system backup.

Unrecognized cpu for product producer.dD A system error occurred, causing the lmf utility to exit with a nonzero error status.

"Version" amended - protected field

You changed the Version field.

The version number should only be changed by using the amend command with a suitable Product Authorization Amendment (PAAM).

Warning creating new history file

The lmf utility has not found an existing history file and is creating a new one.

Warning creating new license database

The lmf utility has not found an existing license database and is creating a new one.