Choosing Codegen Version for Cleaning License
Due to the Sentinel RMS releases over the past years and resultant design changes, codegen license versions have changed. The lscgcln utility requires you to specify the codegen version, as shown in the screenshot below.
Figure 1: The Cleaning License Version
The codegen version may differ for client systems, standalone systems, and License Manager. It depends upon:
>The version of the client (licensing) library
>The version of the License Manager
>The type of persistence to be cleaned, such as commuter, time tampering and so on.
For example, for the given specifications,
>License Manager v 8.6.0 (or later)
>Application licensed with the v8.3.x client library
To clean the client-side persistence, specify codegen version 12. Similarly, to clean the License Manager-side persistence, specify codegen version 15.
Refer to the following table for the mapping of the product with the codegen version:
| Persistence Type | 9.2.x |
9.1.x |
9.0.x |
8.6.x (or Later) |
8.5.x | 8.4.x | 8.2.3. - 8.3.0 |
8.1.x - 8.2.2 |
8.0.x | 7.3.x | 7.3.0 | 7.2.x |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Network Trial (-p) | NA | NA | NA | NA | NA | NA | NA | NA |
v10 |
v9 | v8 | v7 |
| Standalone Trial (-p) | NA | NA | NA | NA | NA | NA | NA | NA | v10 | v9 | v8 | v7 |
| Commuter (-c) | v17 | v17 | v16 | v15 |
v14 |
v13 |
v12 |
v11 |
v10 | v9 | v8 | v7 |
| Network Time-tamper (-t) | v17 | v17 | v16 | v15 |
v14 |
v13 |
v12 |
v11 |
v10 | v9 | v8 | v7 |
| Standalone Time-tamper (-t) | v17 | v17 | v16 | v15 |
v14 |
v13 |
v12 |
v11 |
v10 | v9 | v8 | v7 |
| Grace (-g) | v17 | v17 | v16 | v15 |
v14 |
v13 |
v12 |
v11 |
v10 | NA | NA | NA |
| Network Revocation (-r) as in method 2 | v17 | v17 | v16 | v15 |
v14 |
v13 |
v12 |
v11 |
v10 | NA | NA | NA |
| Standalone Revocation (-r) as in method 3 | v17 | v17 | v16 | v15 |
v14 |
v13 |
v12 |
NA till 8.1.x v11 from 8.2.0 |
NA | NA | NA | NA |
| File Option (-f) | v17 | v17 | v16 | v15 |
v14 |
v13 |
v12 |
v11 |
v10 | v9 | v8 | v7 |