Understanding product naming conventions - Assure_DB2_Data_Monitor_(DB2MON) - Assure_Elevated_Authority_Manager_(EAM) - Assure_Encryption - Assure_Monitoring_and_Reporting_(AMR) - Assure_Secure_File_Transfer - Assure_Secure_File_Transfer_ - Assure_Secure_File_Transfer_PGP - Assure_Secure_File_Transfer_with_PGP - Assure_Security_Multi-Factor_Authentication_(MFA) - Assure_System_Access_Manager_(SAM) - Required_for_All_Modules - assure_ioptimize - assure_itera - assure_mimix - 10.0

License Manager for IBM i Products

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure Security > Assure Encryption
Assure Security > Assure DB2 Data Monitor (DB2MON)
Assure MIMIX™ Software
Assure Security > Assure Monitoring and Reporting (AMR)
Assure Security > Assure Elevated Authority Manager (EAM)
Assure Security > Assure Security Multi-Factor Authentication (MFA)
Assure Security > Assure Secure File Transfer with PGP
Assure Security > Assure Secure File Transfer
Assure Security > Required for All Modules
Assure iOptimize
Assure iTERA
Assure Security > Assure System Access Manager (SAM)
Version
10.0
Language
English
Product name
Assure
Title
License Manager for IBM i Products
Copyright
2023
First publish date
1999

The terms and naming conventions used to identify the product provide a convenient means of referencing the level of software installed.

The following table shows the naming convention in use. This convention is indicated by V.U.SP.FX(R).

Table 1. Product naming convention for shipped software media

Identifier

Description

Version number

V.U.SP.FX(R), where V is the version number.

Example:

10.0.00.00 (initial version 10 release)

Update level

V.U.SP.FX(R), where U is the update level.

Examples:

•10.0.00.00 (initial version 10 release)

•10.1.00.00 (first major update of version 10)

Service pack (SP) 

V.U.SP.FX(R), where SP is the SP level.

Examples:

•10.0.01.00 (first SP release for version 10)

Cumulative fixes 

V.U.SP.FX(R), where FX is the cumulative fix level.

Examples:

•10.0.04.03 (third cumulative fix for the fourth SP on version 10)

Restricted fix

V.U.SP.FX(R), where (R) is the restricted fix. For software media, restricted fixes are always associated with a service pack. Otherwise the field is left blank.

Examples:

•10.0.04.03R (third available restricted fix for the fourth SP on version 10)

Note: When viewing the Precisely Installed Products display, R indicates that one or more restricted fixes have been applied to the indicated service pack level. Cumulative fixes for the service pack level may also be present. For example, 8.0.04.03R on this display indicates that the third cumulative fix as well at least one restricted fix for the fourth SP have been applied.

The following are descriptions of the product terminology used:

Version number

New version of a product. In order to install a product with a new version number, you must be current on maintenance.

Update level

New functionality available within the current version. In order to install a product with a new update level, you must be current on maintenance.

Service pack (SP)

A collection of product changes that are packaged together for the purpose of distribution. Installing a service pack brings all products up to the specified level. An SP is released approximately once per month.

Cumulative fixes

Changes to a service pack that correct a specific problem. Additional fixes are cumulative to ensure that they are applied to the correct service pack and in the correct order. These fixes are released on an as-needed basis only.

Restricted fix 

Changes to a specific service pack. Restricted fixes are not cumulative and may or may not be integrated into the next service pack. If two restricted fixes are available for the same service pack, the first restricted fix does not need to be applied before the second is installed. Restricted fixes are released on an as-needed basis only.

Note: Restricted fixes require caution and should only be applied with assistance from a Support representative.