Operating System - OpenVMS
1826496 Members
2903 Online
109692 Solutions
New Discussion

License PAK Identification

 
SOLVED
Go to solution
Douglas Fisher
Advisor

License PAK Identification

Our Site has been accumulating VMS licenses for about 20 systems since 1982. I just discovered they are in a real mess and have decided to sort them out.

Is there a document that correlates the info on the PAK to the exact purpos of the license?

An affermative answer would make my day.

Thank you
17 REPLIES 17
Karl Rohwedder
Honored Contributor

Re: License PAK Identification

I'm, not sure, if I understand your question. The 'product name' on the PAK identifies to licensed product. Some products are collections of a whole bunch of single products, e.g. NET-APP-SUP licenses.

You may issue LIC LIS/FU on each of your systems and compare the output with your paper PAK's to sort things out.

regards Kalle
Douglas Fisher
Advisor

Re: License PAK Identification

Thank you,

Yes, that is the question. I need to know what NET-APP-SUP,DCPS-PLUS,DCPS-OPEN,DCPS-DC,
...on and on licenses me to do.

Or possibly the Authorization Number can point me to the exact function of the license?

Thanks Again
Doug
Hoff
Honored Contributor

Re: License PAK Identification

There's no central list of PAKs that I'm aware of. I've tossed a list of the core licenses into the FAQ a while back. And yes, digging up the names for the products based on the PAK itself can be a bit, um, daunting.

The DCPS* PAKs are the DECprint licenses for older releases. Some time ago, DECprint got rolled into base OpenVMS; you no longer need a license for it on current releases. Once upon a time, there were multiple PAKs (3?), depending on just how much of DCPS you planned to use.

The NET-APP-SUP* are the various NAS licenses. The details on what is included in each are in the HP NAS SPDs, SPDs which are over at
http://h18000.www1.hp.com/info/spd/

In the likely event that you hit some PAKs that are not listed in the FAQ or elsewhere, post away, and I or others can try to translate them into product names. I'll add the DCPS PAKs into the FAQ.

http://www.hoffmanlabs.com/vmsfaq/

Stephen Hoffman
HoffmanLabs
EdgarZamora
Trusted Contributor

Re: License PAK Identification

The authorization key will not give you any info on the software product. Your software license certificates (the actual paper license) should have a brief description of the software in the product name field. Of course this won't help with bundled software like NAS and EIP.

Here is a link to a webpage that describes the different fields in the license pak.

http://licensing.hp.com/swl/view.slm?page=pak

And here is a link to a description of the certificate:

http://licensing.hp.com/swl/view.slm?page=cert

Here is a link for the NAS SPD's. You will find the contents of the NAS packages here.

http://h18000.www1.hp.com/products/quickspecs/soc_archives/80794.html

Your best bet for identifying licenses that you can't figure out would be to post them here.
John Gillings
Honored Contributor

Re: License PAK Identification

To identify what the group PAKs do, use:

$ SEARCH SYS$UPDATE:*LMF*.COM

For example:

$ search sys$update:*lmf*.com net-app-sup-250

******************************
SYS$COMMON:[SYSUPD]VMSINSTAL_LMFGROUPS.COM;1

$ vmi$lmf_grp_1 :== NET-APP-SUP-250/ACAS-RT/CDA-RT/DCPS-PLUS/DECPS-DC/DMQ-RTO/DQS/DVNETEND/DW-MOTIF/DW-MOTIF-UI-CESKY/DW-MOTIF-UI-DE
UTSCH/
$ vmi$lmf_grp_2 :== NET-APP-SUP-250/DW-MOTIF-UI-ESPANOL/DW-MOTIF-UI-FRANCAIS/DW-MOTIF-UI-ITALIANO/DW-MOTIF-UI-MAGYAR/DW-MOTIF-UI-POL
SKI/
$ vmi$lmf_grp_3 :== NET-APP-SUP-250/DW-MOTIF-UI-RUSSKIJ/DW-MOTIF-UI-SLOVENSKY/DW-MOTIF-UI-SVENSKA/FORMS-RT/OBB-RT/P25A/P25B/
$ vmi$lmf_grp_4 :== NET-APP-SUP-250/P25C/RDB-RUNTIME/RDB-SERVER/RSM-CLIENT/RTR-CL/UCX/UCX-IP-APPL/UCX-IP-RT/VMSCLUSTER/

Conversely, you can find out which group PAKs include a product by searching for that product. For example:

$ search sys$update:*lmf*.com dvnetend

******************************
SYS$COMMON:[SYSUPD]VMSINSTAL_LMFGROUPS.COM;1

$ vmi$lmf_grp_1 :== NET-APP-SUP-250/ACAS-RT/CDA-RT/DCPS-PLUS/DECPS-DC/DMQ-RTO/DQS/DVNETEND/DW-MOTIF/DW-MOTIF-UI-CESKY/DW-MOTIF-UI-DE
UTSCH/
$ vmi$lmf_grp_16 :== NET-APP-SUP-200/ACAS-RT/DCPS-OPEN/DCPS-PLUS/DMQ-RTO/DMQ-RTO-V/DVNETEND/DVNETEXT/DW-MOTIF/DW-MOTIF-UI-CESKY/
$ vmi$lmf_grp_20 :== NET-APP-SUP-150/ACAS-RT/DMQ-RTO/DVNETEND/DW-MOTIF/DW-MOTIF-UI-CESKY/DW-MOTIF-UI-DEUTSCH/DW-MOTIF-UI-ESPANOL/

Hopefully the format is self explanatory.

Note that this is the answer to the TECHNICAL question "what products will this PAK allow me to run?". This is NOT NECESSARILY the same answer as the same text as a LEGAL question. I'm told that in some cases, the LMF Group tables include products which are not included in the corresponding license agreement (in other words, OpenVMS will permit use of a product that you're not legally entitled to use). [on the other hand, I'd LOVE to see the HP lawyers trying to enforce it in a test case ;-)]

In the opposite direction, to find out what PAKs a particular product wants, start by issuing LICENSE UNLOAD commands against loaded PAKs until starting the product generates a NOLICENSE error. Then:

$ REPLY/ENABLE=LICENSE
$ DEFINE/SYSTEM/EXEC LMF$DISPLAY_OPCOM_MESSAGE "TRUE"

Then attempt to start the product. You'll see a list of NOLICENSE OPCOM messages in the order the product requests PAKs from LMF. The final message will be a repeat of (most likely) the first probe, and will name what is considered the "standard" PAK for the product.

Don't forget to DEASSIGN/SYSTEM/EXEC LMF$DISPLAY_OPCOM_MESSAGE after use. Leaving it defined can (will?) result in spurious NOLICENSE OPCOM messages
A crucible of informative mistakes
Solution

Re: License PAK Identification

I've some self-written documentation cross-referencing PAK to product and platform. If you like I will forward you a copy of it.
Wim Van den Wyngaert
Honored Contributor

Re: License PAK Identification

Douglas,

I have about 30 cm of licenses when I put them on a pile (only 15 years but for in total about 500 machines). But they are often related to systems/software long gone. But still the license is active on newer systems because of "transfers". So : a complete mess too.

If I want to clean this up, I will have to compare each page with all licenses on all systems. And what if some pages are missing ? And what about transfers for which I have no written authorization (but it may exist, who knows ?).

Good luck

Wim
Wim
Wim Van den Wyngaert
Honored Contributor

Re: License PAK Identification

BTW : who knows what "VAXCLUSTER_CONSOLE" (issued by DEC) means ? Google didn't find it.

Wim
Wim
Bart Zorn_1
Trusted Contributor

Re: License PAK Identification

VAXCLUSTER-CONSOLE if for Polycenter Console Manager. Probably obsolete now unless you are using PCM V1.6 or earlier.

Regards,

Bart Zorn
Wim Van den Wyngaert
Honored Contributor

Re: License PAK Identification

And how do I know that Bart ?

Better formulated : how do I know a license is not used on a system ?

When I do show lic/usage it says "unlimited license, no usage information". And it says this also for multinet that I do use.

Wim
Wim
Karl Rohwedder
Honored Contributor

Re: License PAK Identification

Brute force: unload the PAK and check the operator logfile for LICENSE messages...

regards Kalle
Bart Zorn_1
Trusted Contributor

Re: License PAK Identification

By default, you do not get any OPCOM message when a license is missing.

Funny thing is, that the License Management Utility Manual (for V8.3) states that you should not define the logical name
LMF$DISPLAY_OPCOM_MESSAGE.

When you do define this logical, you get the OPCOM messages. I tried it for TSM. It appears that the TSM image first tries DECMCC-EMS and DECMCC-SMS before trying the TSM license.

Regards,

Bart
Bart Zorn_1
Trusted Contributor

Re: License PAK Identification

Some more info:

The LMF$DISPLAY_OPCOM_MESSAGE should be defined in LNM$SYSTEM_TABLE, not in LNM$SYSCLUSTER_TABLE. Typical.

I also saw during this experiment that Pathworks Advanced server is looking for PWLMXXXCA08.00 up to PWLMXXXCA11.03 ! Expectations were high, apparently!

Bart
Douglas Fisher
Advisor

Re: License PAK Identification

Thanks to everyone who replied.
Your input has helped especialy in framing the task - much larger that I thought. If I find anything good I'll post it.
Douglas Fisher
Advisor

Re: License PAK Identification

Have a perspective on the task now.
Hoff
Honored Contributor

Re: License PAK Identification

The VAXcluster Console is better known as VCS. And yes, VCS evolved into POLYCENTER something or other, and departed DEC bound for CA during the great POLYCENTER product exodus.

Here's the old SPD:
h18002.www1.hp.com/info/SP2746/SP2746PF.PDF
Jan van den Ende
Honored Contributor

Re: License PAK Identification

Douglas,

from your Forum Profile:


I have assigned points to 13 of 27 responses to my questions.


Maybe you can find some time to do some assigning?

http://forums1.itrc.hp.com/service/forums/helptips.do?#33

Mind, I do NOT say you necessarily need to give lots of points. It is fully up to _YOU_ to decide how many. If you consider an answer is not deserving any points, you can also assign 0 ( = zero ) points, and then that answer will no longer be counted as unassigned.
Consider, that every poster took at least the trouble of posting for you!

To easily find your streams with unassigned points, click your own name somewhere.
This will bring up your profile.
Near the bottom of that page, under the caption "My Question(s)" you will find "questions or topics with unassigned points " Clicking that will give all, and only, your questions that still have unassigned postings.
If you have closed some of those streams, you must "Reopen" them to "Submit points". (After which you can "Close" again)

Do not forget to explicitly activate "Submit points", or your effort gets lost again!!

Thanks on behalf of your Forum colleagues.

PS. - nothing personal in this. I try to post it to everyone with this kind of assignment ratio in this forum. If you have received a posting like this before - please do not take offence - none is intended!

PPS. - Zero points for this.

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.