From:	SMTP%"lionel@quark.enet.dec.com" 13-AUG-1994 21:19:58.12
To:	EVERHART
CC:	
Subj:	Re: LMF question

From: lionel@quark.enet.dec.com (Steve Lionel)
X-Newsgroups: comp.os.vms
Subject: Re: LMF question
Date: 9 Aug 1994 14:07:44 GMT
Organization: Digital Equipment Corporation, Nashua NH
Lines: 61
Distribution: world
Message-Id: <3282jg$q6d@jac.zko.dec.com>
Reply-To: lionel@quark.enet.dec.com (Steve Lionel)
Nntp-Posting-Host: quark.zko.dec.com
X-Newsreader: mxrn 6.18-20
To: Info-VAX@CRVAX.SRI.COM
X-Gateway-Source-Info: USENET


In article <gurman-0808942238260001@arrowroot.gsfc.nasa.gov>, 
gurman@uvsp.gsfc.nasa.gov (Joseph B. Gurman) writes:
|>In article <325u08$bgs@jac.zko.dec.com>, lionel@quark.enet.dec.com (Steve
|>Lionel) wrote:
|>
|>> In article <1994Aug4.112042.1@titan.arc.ab.ca>, falk@titan.arc.ab.ca writes:
|>> |>   I just received a license PAK with AVAILABILITY TABLE CODE: I.
|>> |>All the documentation I can find (Grey wall and white wall) lists
|>availability
|>> |>codes A,B,C,D,E,F.  Can anybody tell me what "I" means?
|>> 
|>> It means that the PAK is usable for layered products either on either
|>VAX or AXP
|>> systems.  For example, here's what SHOW LICENSE/CHARGE displays on an
|>> OpenVMS AXP V6.1 system (the display on a VAX systems is not quite so
|>                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|>> descriptive):
|>  ^^^^^^^^^^^
|>> 
|>> Type: A, Units Required: 20     (VAX/VMS Capacity or OpenVMS Unlimited
|>or Base)
|>> Type: B, * Not Permitted *      (VAX/VMS F&A Server)
|>> Type: C, * Not Permitted *      (VAX/VMS Concurrent User)
|>> Type: D, * Not Permitted *      (VAX/VMS Workstation)
|>> Type: E, * Not Permitted *      (VAX/VMS System Integrated Products)
|>> Type: F, * Not Permitted *      (VAX Layered Products)
|>> Type: G, * Not Permitted *      (Reserved)
|>> Type: H, Units Required: 1050   (Alpha Layered Products)
|>> Type: I, Units Required: 1050   (Layered Products)
|>
|>    Far be it from me to disagree with Steve Lionel, who supports this
|>group so well, but:
|>
|>$ sh lic /char
|>VMS/LMF Charge Information for node UVSP
|>This is a VAXstation 4000-90, hardware model type 376
|>Type: A, * Not Permitted *      (VMS Capacity)
|>Type: B, * Not Permitted *      (VMS Server)
|>Type: C, * Not Permitted *      (VMS Concurrent User)
|>Type: D, Units Required: 100    (VMS Workstation)
|>Type: E, Units Required: 50     (System Integrated Products)
|>Type: F, Units Required: 10     (Layered Products)
|>Type: G, * Not Permitted *      (VMS Reserved)
|>Type: H, * Not Permitted *      (Alpha Layered Products)
|>Type: I, Units Required: 10     (Layered Products)

What's your disagreement?  I get the same display on my VS4000-60 running
OpenVMS VAX V6.1 and the AXP display is more informative.  For example,
on AXP, types A-F specify "VAX" (though type A can be used for either
architecture).  Can you tell from the VAX display what the difference is
between types F and I?  You can from the AXP display.
-- 

Steve Lionel                      Mail: lionel@quark.enet.dec.com
DEC Fortran Development           WWW:  http://www.digital.com/info/slionel.html
Digital Equipment Corporation     
110 Spit Brook Road, ZKO2-3/N30
Nashua, NH 03062-2698             "Free advice is worth every cent"

For a summary of Digital's Internet services, send mail to info@digital.com

