[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

316.0. "SYS$Lookup_License on V7.1 with multiple PAKs" by CPEEDY::KENNEDY (Steve Kennedy) Wed Mar 12 1997 20:31

    Previous to V7.1 I believe licenses of the same product-name were
    automatically combined. For example, SHOW LICENSE showed a single line
    with 150 units for product X if two PAKs for product-name X were
    registered, one for 100 units and one for 50 units. Also
    SYS$Lookup_License could be used to find out how many units for a
    particular product were available by simply using the product name.
    
    On V7.1 it seems that the default behavior has been changed so that
    license PAKs for the same product-name are no longer combined by
    default. To combine PAKs is seems you now need to use LICENSE MODIFY
    /COMBINE to set the option on the desired PAKs you wish to combine. 
    
    For uncombined licenses SHOW LICENSE will list each registered license
    PAK separately in the display. Also it seems SYS$Lookup_License only
    returns data associated with one of the registered license PAKs (at
    least that's the behavior with the way our code is currently written -
    it gets the units for only one of the two loaded PAKs).
    
    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?
    
    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?
    
    It is very common for our customers to have multiple PAKs for the same
    product. I'm trying to determine if there's a software solution to
    avoid having to have customers with multiple PAKs explicitly set the
    COMBINE option on all licenses and/or what we need to tell our
    customers to assure our software continues to work correctly on V7.1.
    
    If this information is available elsewhere, pleas point me at it and
    I'll be glad to chase it down myself.
    
    thanks,
    \steve

T.R	Title	User	Personal Name	Date	Lines
316.1	new combine rules for LMF V1.2	STAR::ABIS	I come in peace	`Thu Mar 13 1997 10:58`	55
	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
316.2	Thanks	CPEEDY::KENNEDY	Steve Kennedy	`Fri Mar 14 1997 16:24`	14
	I first noticed the problem with licenses not being combined with our field test license PAKs, which DO have termination dates - hence two different licenses with two different termination dates were not automatically combined, but could be combined (as I found). Since the PAKs we ship to customers don't normally have termination dates, I think most licenses our customers have will be combined automatically (the obvious exception is temporary licenses with terminatin dates). Thanks for the update/explanation Eric. \steve