Add License Information (ADDPRDLICI)

The Add Product License Information (ADDPRDLICI) command adds license information to the product or feature. This command can be used before or after the product or options belonging to a feature are packaged using the Package Product Option (PKGPRDOPT) command, but before the product or options belonging to a feature are installed. If the product has keyed (*KEYED) compliance, a product license information handle is included in the completion message received from this command.

For more information about the Add Product License Information (QLZADDLI) API is also available in the API topic in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.

Restriction: This command is shipped with public *EXCLUDE authority.

Parameters

Keyword	Description	Choices	Notes
PRDID	Product ID	Character value	Required, Positional 1
RLS	Release level	Character value	Required, Positional 2
FEATURE	Feature	Character value, 5001	Optional
USGTYPE	Usage type	CONCURRENT, REGISTERED	Optional
COMPLIANCE	Compliance type	OPRACTION, WARNING, *KEYED	Optional
DFTUSGLMT	Default usage limit	0-999999, 1, *NOMAX	Optional
LICTRM	License term	VERSION, RELEASE, *MOD	Optional
MSGID	Feature message ID	Name, *BASEOPT	Optional
ALWLICRLS	Allow license release	NO, YES	Optional
VNDPWD	Vendor password	Simple name, *NONE	Optional
GRACE	Grace period	Element list	Optional
	Element 1: Number of days	0-999, 0
	Element 2: Allow for default usage limit	NO, YES

Top

Release level (RLS)

Specifies the version, the release, and the modification level of the product or feature to which the license information is being added.

The possible values are:

version-release-modification: Specify the version, release, and modification level of the product or feature where the license information is being added. The release level must be in the format VxRyMz, where valid values for x and y range from 0 through 9 and valid values for z range from 0 through 9 and A through Z

Feature (FEATURE)

Specifies the feature for which the license information is being added. The license information is added to all product loads with the specified product ID and feature.

5001: License information for the 5001 feature of the product specified on the PRDID parameter is added.
load-ID: Specify that the license information for the feature on the PRDID parameter associated with this number is to be added. Valid values range from 5001 through 9999.

Usage type (USGTYPE)

Specifies the type of license usage.

The possible values are:

*CONCURRENT: The usage limit is for the number of unique jobs accessing the product or feature at one time.
*REGISTERED: The usage limit is for the number of unique license users registered by the product or feature.

Compliance type (COMPLIANCE)

Specifies the action that must be taken when the usage limit is exceeded.

The possible values are:

*OPRACTION: The usage limit cannot be exceeded. If you attempt to use the product or feature after the usage limit has been reached, you are prevented from accessing the product or feature until the appropriate action is taken by the system administrator to increase the usage limit.
*WARNING: If you attempt to use the product or feature after the usage limit has been reached, you are allowed access. A warning message indicating that the usage limit has been exceeded is sent to the licensing information owner for notification.
*KEYED: A license key is required from the software provider to install or to increase the usage limit of the product or feature. The software provided can permit a grace period which allows the usage limit of a product or feature to be exceeded for n days before a new license key is required to allow additional users access to the product. If a new key with an increased usage limit is not installed prior to the end of the grace period, the usage limit of the product reverts back to the entitled usage limit.

Default usage limit (DFTUSGLMT)

Specifies the usage limit that is in effect the first time the product or feature is installed for a license term.

Note: For *KEYED compliance, this is the number of users that are able to use the product or feature before the license key is installed using the Add License Key (ADDLICKEY) command or Add License Key Information (QLZAADDK) API. To prevent any access to the product or feature without a key, the default usage limit should be set to 0.

The possible values are:

1: One user is allowed to access the product or feature.
*NOMAX: Any number of users are allowed to access the product or feature.
default-usage-limit: Specify the default usage limit number. The valid values range from 0 through 999&finespace.999.

License term (LICTRM)

Specifies which levels of the product or feature share license information.

The possible values are:

*VERSION: All VxRx levels of the product, where Vx is the version level and Rx is the release level, specified on the RLS parameter whose license term is also *VERSION share the same license information. When the version level of the product or feature changes, customers installing the new release must use the Change License Information (CHGLICINF) command for a compliance type of *WARNING or *OPRACTION, or the Add License Key (ADDLICKEY) command for a compliance type of *KEYED, to set the license information.
*RELEASE: All VxRx levels of the product, where Vx is the version level and Rx is the release level, specified on the RLS parameter whose license term is also *RELEASE share the same license information. When the version level or the release level of the product or feature changes, customers installing the new release must use the Change License Information (CHGLICINF) command for a compliance type of *WARNING or *OPRACTION or the Add License Key (ADDLICKEY) command for a compliance type of *KEYED to set the license information.
*MOD: Each level of the product or feature is licensed. No license information is shared between levels. Customers installing a new level of the product or feature must use the Change License Information (CHGLICINF) command for compliance type of *WARNING or *OPRACTION, or the Add License Key (ADDLICKEY) command for compliance type of *KEYED to set the license information.

Feature message ID (MSGID)

Specifies the message identifier of the message that describes the product feature. The message file for this message ID is specified in the product definition.

The possible values are:

*BASEOPT: There is no message describing this product feature. The message used for describing the base option of this product is used instead.
feature-message-id: Specify the message identifier of the message that describes this product feature.

Allow license release (ALWLICRLS)

Specifies whether a license that is previously requested can be released using the WRKLICINF command. When the license is released, the usage count is decreased. This value can only be specified for a registered license type.

If it is necessary for the product to be notified that a license has been released, *NO should be specified and the product must provide its own mechanism for releasing a license.

The possible values are:

*NO: A license cannot be released using the WRKLICINF command.
*YES: A license can be released using the WRKLICINF command.

Vendor password (VNDPWD)

Specifies the software vendor's password. This password is encrypted and stored with the product. It is used in validating Add License Key requests and must be the same password used to generate keys for this product and feature on the Generate License Key (GENLICKEY) command.

The possible values are:

*NONE: There is no vendor password needed for the Add License Key Information (ADDLICKEY) command.
vendor-password: Specify the vendor password. It must begin with an alphabetic character such as A through Z, $, # or @. It is then followed by no more than 9 alphanumeric characters such as A through Z, 0 through 9, $, # @ or _.

Grace period (GRACE)

Specifies the number of days after a product first exceeds its usage limit that you have to obtain a new license key. If a new license key is not obtained from the software vendor by the time the grace period is expired, no users over the usage limit are allowed to access the product or feature. When the usage limit is first exceeded, the date the grace period expires is calculated by adding the number of days in the grace period to today's date.

The possible number grace period days values are:

0: There is no grace period. The user is not allowed to exceed the usage limit.
grace-period: Specify the number of days in the grace period. Valid values range from 0 through 999.

The possible values for allowing for a default usage limit are:

*NO: The grace period is not allowed for use with the default usage limit. This means that you are not allowed to exceed the default usage limit before the license key is installed using the Add License Key command (ADDLICKEY) or Add License Key Information (QLZAADDK) API.
*YES: The grace period is allowed for use with the default usage limit. This means that you can exceed the default usage limit for the number of days in the grace period before the license key is installed.

Examples

Example 1: Adding Product License Information

ADDPRDLICI   PRDID(1MYPROD)  RLS(V5R2M0)

This command adds product license information to the product with product identifier 1MYPROD for release V5R2M0.

Example 2: Adding Product License Information for the V5R2M0 Release

ADDPRDLICI   PRDID(2MYPROD)  RLS(V5R2M0)  COMPLIANCE(*KEYED)
             VNDOWD(PRODUCTPWD)  GRACE(30 *YES)

This command adds product license information to the product with the product identifier 1MYPROD for release V5R2M0. This product supports keyed compliance. It can exceed its usage limit and default usage for 30 days.