Problem:
The output of the Apptrack "License List" and "License Summary" is sometimes confusing.
Resolution:
In Apptrack the first menu item is "1. License List". This shows the properties of all licenses installed in Apptrack, with a sequence number for each, and separated by lines of hyphen characters, for example:
--------------------------------------------
00001
.
.
.
--------------------------------------------
00002
.
.
.
All licenses in Apptrack are "runtime" licenses, i.e. they give permission for COBOL programs to run. This is in contrast to Server Express licenses, also known as "compiler" or "development" licenses, which allow the COBOL compiler to be used, and which are installed into the separate LMF license manager, and administered using a separate utility named "mflmadm" (not Apptrack).
There are two main types of runtime licenses in Apptrack. The first is Developer Usage runtime licenses. In the Apptrack License List (and also in the Apptrack menu item "2. License Summary"), these are labeled as ** Developer Usage. They are automatically installed into Apptrack each time a "compiler" license is installed into the LMF license manager. The rationale is that software developers using the COBOL compiler will need some runtime licenses for testing and debugging.
These Developer Usage runtime licenses are strictly for use by developers who are testing and debugging; they should not be used as runtime licenses for production. For each one "compiler" license installed in the LMF, 5 Developer Usage licenses are automatically installed into Apptrack, so each developer has permission to run 5 COBOL processes simultaneously during testing.
Installing one "compiler" license in the LMF causes several separate entries to appear in the Apptrack License List. There will be some duplicate and redundant entries, and they sometimes cause confusion. There will be more than one **AS Developer Usage entry, plus one **ES Developer Usage entry associated with the same serial number from the parent LMF "compiler" license. Consider this sample output:
----------------------------------------------------------
00001
Version of Server Express (Model 1)
License units: 00005 **AS Developer Usage
Duration: Unlimited
60000001234TG
03030 10000 05CA8 61B0. ....
--------------------------------------------
00002
Version of Server Express (Model 1)
License units: 00005 **AS Developer Usage
Duration: Unlimited
60000001234TG
03030 B0000 05CA8 61B0. ....
--------------------------------------------
00003
Version of Server Express (Model 1)
License units: 00005 **AS Developer Usage
Duration: Unlimited
60000001234TG
03060 B0000 05CA8 61B0. ....
--------------------------------------------
00004
Version of Server Express (Model 1)
License units: 00001 **ES Developer Usage
Duration: Unlimited
60000001234TG
03050 10000 01CA8 61B0. ....
--------------------------------------------
There are three **AS Developer Usage entries and one **ES Developer Usage entry, all showing the same serial number 60000001234TG . The serial number 60000001234TG is from the parent "compiler" license installed in the LMF. The three **AS Developer Usage entries each show "License units: 00005", but this does not mean there are 5 X 3 = 15 AS Developer Usage licenses, instead the **AS Developer Usage entries are duplicate and redundant, and the duplicates should be ignored. They represent the same 5 overall AS Developer Usage licenses. In this example there are 5 total AS Developer Usage licenses and one ES Developer Usage license.
In the Apptrack License List, when you see a group of Developer Usage entries all associated with the same serial number, the duplicate entries should be ignored.
The second type of license in Apptrack is a production runtime license. In the Apptrack License List, any license that does not say "Developer Usage" is a production runtime license. These licenses show association with a particular COBDIR directory location, for example:
--------------------------------------------
00005
/opt/microfocus/cobol
Version of Server for COBOL
License units: Unlimited CPUs: 002
Duration: Unlimited Server
60000001234TG
04038 1003E 828A7 79E0. ....
The directory location (/opt/microfocus/cobol in this example) reflects the value of the COBDIR environment variable at the time the license was originally installed. The license becomes associated with that particular COBDIR. Model 1 licenses will work only with that particular COBDIR. But Model 2 licenses, though they may show association with a particular COBDIR, will actually work with any COBDIR location. To change the COBDIR with which a particular license is associated, un-install the license, then exit out of Apptrack, set the COBDIR environment variable to the desired location, then go back into Apptrack and re-install the license.
On the menu item "2. License Summary", usage information is listed in 3 columns. The first column indicates the number of instances of that license that are installed. The second column (labeled "Sys") shows licenses that were placed in use within the last 30 seconds. This is significant for Model 1 "standard" licenses, because they will be freed up only after 30 seconds has passed, even if the life of the COBOL process is less than 30 seconds. So, if a COBOL process uses a Model 1 standard license and only runs for 10 seconds, the license will continue to be reserved for another 20 seconds before being released. Model 1 "transaction" licenses, and all Model 2 licenses, are not subject to this 30-second timeout. The third column (labeled "In Use") displays licenses that are currently in use. Unlike the "Sys" column, licenses are counted in this column only when the underlying process is running.
#COBOL
