<<< VAXAXP::NOTES$:[NOTES$LIBRARY]VMSNOTES.NOTE;1 >>> -< VAX and Alpha VMS - Digital Internal Use Only >- ================================================================================ Note 316.1 SYS$Lookup_License on V7.1 with multiple PAKs 1 of 1 STAR::ABIS "I come in peace" 55 lines 13-MAR-1997 10:58 -< new combine rules for LMF V1.2 >- -------------------------------------------------------------------------------- Welcome to LMF V1.2! This new behavior is discussed briefly in the V7.1 release of the LMF Utility Manual. But we went through about three different writers (TFSO's, project hopping, etc.) and the manual isn't as clear as I'd like it to be. LMF V1.2 and LMF V1.1 cannot combine two PAKs if the following fields are different: 1. Availability 2. Activity 3. Options: VAX_ALPHA, RESERVE_UNITS, USER, NO_SHARE 4. Product Token 5. Hardware ID LMF V1.2 will not, but may be forced to combine with modify/combine, if all the above fields are identical and the following fields are different: 6. version 7. release date 8. termination date 9. reserve list (one pak with, the other without) And if all the 9 fields listed above on the two paks are identical, LMF V1.2 will combine the paks (with or without modify/combine) by default. > My questions: > > 1) What happens when an OpenVMS system is upgraded to V7.1? Will all > registered licenses for the same product be not COMBINED by default? Since customer paks today have blank version, release date, and termination dates, unless they are fooling around with reserve lists, all the paks will continue to combine as they have done in LMF V1.1. > 2) Is it possible through the use of SYS$Lookup_License to see how many > total units are available for all licenses registered for a product if > the COMBINE option isn't specified on all the registered PAKs for the > same product? A while back, I gave the Pathworks folks some code that uses the LMF$_UNITS_IN_USE item to get the total units from an activity (concurrent use) license. I tested that on LMF V1.2 and it will continue to work. If the day does arrive that we ship paks with version/release/termination info, we may have to modify the Pathworks code. In addition to combination changes, LMF V1.2 will split large concurrent use licenses (greater than 2700 users) into smaller sublicenses. This had to be done because of limitations in the Lock Manager. Pathworks licenses found this limitation. In this situation, I added a little hook so that when LMF$_UNITS_IN_USE is being used, the total number of units returned will still be correct even for these split licenses. Eric LMF V1.2 Architect/Coder/Tester