[Info-vax] LMF$LURT.DAT layout

Wilm Boerhout w6.boerhout at planet.nl
Sun Mar 8 04:43:58 EDT 2009


VAXman- @SendSpamHere.ORG vaguely mentioned on 7-3-2009 13:25:
> In article <49b221e1$0$8985$703f8584 at news.kpn.nl>, Wilm Boerhout <w6.boerhout at planet.nl> writes:
>> Does anyone have the record layout of the License Unit Requirements 
>> Table file (SYS$SYSTEM:LMF$LURT.DAT)?
>>
>> Google tells me that the SAIC archives had a DCL to read the file, but 
>> as we all know...
> 
> I have all of those archives.  Sorry, I haven't gotten time yet to put
> them up on-line but I will get them up withing the next month.  Send me
> the URL Google returned and I will pull out and send the file you want.

Well, thanks to Mr VAXman, two modules have been retrieved. They show me 
how to extract the SMM numbers from SYS$LOADABLE_IMAGES:CPULOA.EXE with 
their human readable names, and how to tie these to license types in 
LMF$LURT.DAT.

However, my Alpha V8.3 LMF$LURT.DAT only has model numbers up to 1090, 
and certainly misses the 19xx numbers for let's say the GS80 Alpha's. 
Furthermore, CPULOA.EXE only contains names for VAX models.

So, exactly how was this mechanism transferred to Alpha? Or was it? It 
is not *necessary* for any system to contain this type of information 
about other systems. A system only has to look up it's own license 
information in the LURT. The information in CPULOA.EXE is redundant.

But, how does a GS80 (SMM 1967) find out how many license unit it needs? 
The info at licensing.hp.com must be present somewhere in the system, or 
so the documentation suggests ( 
http://h71000.www7.hp.com/doc/82final/4584/4584pro.html#index_x_9 )

/Wilm



More information about the Info-vax mailing list