Online Expert Day - HPE Data Storage - Live Now
April 24/25 - Online Expert Day - HPE Data Storage - Live Now
Read more
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

pathworks licenses

robert70
Valued Contributor

pathworks licenses

I have recently migrated Pathworks 6.0c
to 7.3B
I had 400 units of license pwlmxxxca07.03 with he old pathworks - these work with the new install also
I have requested a temp set of licenses from HP which give me another 3000 licenses until 21-dec-10 - 60 day

In a few weeks i will be receiving another 13 pwlmxxxca07.03 licenses to give me a total of 4+13 = 17 users

i cant seem to be able to get both the temp licenses and the current 4 licenses available on pathworks at the same time?

I either get the temp license only........

View Actions Options Help │
│ List of License Products │
│┌Product────────────Total────In Use─────Avail─────Alert──────────────────────┐│
││PWLMXXXCA07.03 3000 1 2999 0


or i get the 400 units of old license


cant seem to get them both available via admin/lice at the same time?
do the temp licenses override any live ones?

13 REPLIES
Brad McCusker
Respected Contributor

Re: pathworks licenses

Hello Robert70,

Ah, PATHWORKS licensing - I don't miss dealing with those issues. PATHWORKS is probably the only product that has a seperate book dedicated to licensing. Ugh.

Is this the only server in your network? If so, turn off the darn license server, it just complicates matters. But, if you insist on using the license server, read on...

I think your problem is that the licenses haven't synched yet (they may have synched by now, if you let things sit over night). Check out section 3.5.2 in this book: http://h71000.www7.hp.com/doc/82final/documentation/pdf/adsrv_gd_manage_lic.pdf.

Essentially, you need to set PWRK$LsLmfSynchMinutes to cause a synchronization to happen at a more convenient time than 12:01 AM (the default).

That logical name, and other logicals you can have fun with, are documented in the license startup routines, i.e. PWRK$LICENSE_S_START.COM and PWRK$LICENSE_R_START.COM.

If that doesn't work, let us know and we can dig deeper.

Brad McCusker
Software Concepts International
www.sciinc.com
Brad McCusker
Software Concepts International
Brad McCusker
Respected Contributor

Re: pathworks licenses

Robert,

One more thing - You might have to combine the licenses. I'm a little vague on this point, I just don't recall the specifics.

$ LICENSE MODIFY /COMBINE

Brad McCusker
Software Concepts International
www.sciinc.com
Brad McCusker
Software Concepts International
Kelly Stewart_1
Frequent Advisor

Re: pathworks licenses

Robert,

What are the exact commands or menu options you are using to register, load, and enable the PAKs?

We do that part with LICENSE commands in a command file. It registers all the PAKS, then does a single LICENSE LOAD PWLMXXXCA7.02 (in our case) with no qualifiers. However I have a vague memory that in some circumstances, you need to LOAD each PAK individually with the /AUTH qualifier.

By the way, you're lucky to be getting new PAKs at all. For our last Pathworks upgrade, it took about a year for HP to actually make the PAKs for us.
robert70
Valued Contributor

Re: pathworks licenses

thanks Brad

"Is this the only server in your network?"

No it isnt we have 2 - one on our live box one on our test box -


"If so, turn off the darn license server"

if i do that I cant connect my PC to shares on the Alpha? Is there another way to do that ?


robert70
Valued Contributor

Re: pathworks licenses

brad
i get this when im trying to combine -

$license modify/combine pwlmxxxca07.03
%license-w-ambig, information provided was ambiguous; multiple licenses were found for pwlxxxca07.03
Hoff
Honored Contributor

Re: pathworks licenses

>if i do that I cant connect my PC to shares on the Alpha? Is there another way to do that ?

Probably not the answer you want...

Shut down the PATHWORKS Server, and migrate to and use the (free) HP CIFS package to serve the shares?

At least you're then tussling with somewhat more current and rather more widely-used software (CIFS is Samba), and tussling with what HP indicates is the replacement path for PATHWORKS Server.

And there are no licensing servers nor PAKs with CIFS.

Given you have HP support, get the CIFS 1.2 kit and whatever is the current patch.
Hoff
Honored Contributor

Re: pathworks licenses

>$license modify/combine pwlmxxxca07.03
%license-w-ambig, information provided was ambiguous; multiple licenses were found for pwlxxxca07.03

Add /AUTH=target-pak-auth-string-here

http://h30266.www3.hp.com/odl/i64os/opsys/vmsos84/4584/4584pro_005.html
Brad McCusker
Respected Contributor

Re: pathworks licenses

>And there are no licensing servers
>nor PAKs with CIFS

C'mon Hoff - think of all the fun he'd miss out on ;^)

I actually do agree with Hoff, if you can move to CIFs, do it.

Back to your issue however, you need to use something else to identify the license you are modifying, typically you would use the /AUTH qualifer.

Brad McCusker
Software Concepts International
www.sciinc.com
Brad McCusker
Software Concepts International
robert70
Valued Contributor

Re: pathworks licenses

THANKS ALL

i do this

$ license modify/combine/auth=***-**-**********-*-* PWLMXXXCA07.03

and then

$license UNLOAD PWLMXXXCA07.03

then

$license LOAD PWLMXXXCA07.03
%LICENSE-I-LOADED, DEC PWLMXXXCA07.03 was successfully loaded with 270000 units
%LICENSE-I-LOADED, DEC PWLMXXXCA07.03 was successfully loaded with 400 units
%LICENSE-I-LOADED, DEC PWLMXXXCA07.03 was successfully loaded with 30000 units

but when i go into the ADMIN/LICE still only showing the emergency licenses 300,000 units
the other 400 units (which will be the live license) not showing

we are going to upgrade to CIFS next year but this is just a temp upgrade phase
Brad McCusker
Respected Contributor

Re: pathworks licenses

Oh - regarding shutting down the license server.

If you do have multiple servers, then yes, the license server is needed to 'serve' licenses to the clients. The clients then use the single (100 unit) license they've been 'served' to connect to multiple different PATHWORKS servers. Just 100 units allows the client to connect to as many servers and he can find.

I assume you've only got one system running the license server and all of your PWLMXXXCA07.03 PAKs are loaded on that one server (and NONE are loaded on the other server)?

Another way to think of the license server is to consider the following example. Imagine you have two VMS systems (NOT clustered) and 10 clients. You want all 10 clients to be able to connect to shares on both servers. If you use "server based" licensing (which means you do NOT run the license server), you need 1000 units of PWLMXXXCA07.03 license on EACH server. A total of 2000 units. As each client connects to either machine, the License Registrar 'consumes' 100 units of license capacity on behalf of the client connection.

If you use "client based" licensing, you need to have 1000 units of PWLMXXXCA07.03 license loaded on the one server running the license server. When a client connects, if he hasn't already obtained a license from the license server, he requests the license which he then keeps in his cache (on the client). Now, each time he connects to a PATHWORKS share, he presents that cached license and is granted access. He presents the same license to any server he connects to. 10 clients in our example only need 10*100 units or 1000 units total.

Clear as mud?

Hard to belive we actually used to do DECUS session focused on this stuff, huh?

Brad McCusker
Software Concepts International
www.sciinc.com
Brad McCusker
Software Concepts International
robert70
Valued Contributor

Re: pathworks licenses

ITS WORKING NOW
i did the combine command as above but with the license pak that wasnt showing up on the ADMIN/LICE product list now i see 3004 licenses avaialble (eg my 4 real license and the 3000 emergency ones ) thats great have another 13 real licenses on order say when they arrive can presumably combine these with the 4 existing in the same way
cheers all for help
robert
Brad McCusker
Respected Contributor

Re: pathworks licenses

Robert,

A couple things.

To combine licneses, the following must be the same on each license:

Product name
Producer
Availability
Activity
Key Options: RESERVE_UNITS, USER, NO_SHARE (assigned node must match), ALPHA, or VAX_ALPHA
Product Token
Hardware-ID


Then you need to do the license /combine to each license PAK.

To see if they've combined, when you do the "$ license load pwlmxxxca07.03", you should see just one license load statement with the total number of units. If you don't see that, then, they didn't combine. You can also type "SHOW LICENSE PWLMXXXCA.07.03" to hopefully see one license with the total units.

Once they are combined (and I'm sorry to say I am not certain combining is still required), then you still need to tweak the "synch" logical I mentioned above to get them to show up in the license server.

Brad McCusker
Software Concepts International
www.sciinc.com
Brad McCusker
Software Concepts International
Hans Hosang
Frequent Advisor

Re: pathworks licenses

This all sounds a bit complicated.
The command
$ lic mod /combine PWLMXXXCA07.03
simply accepts the switch /all.
No need to do difficult things with /auth...

BUT, please remember that, if you combine, the expiration date of 21-dec-10 will also apply to the permanent licenses until you do a /nocombine (also with /all).

so, once you receive your new premanent licenses, do the /nocombine and unload the temp ones.

Hope this helps you out.
Hans Hosang.
OpenVMS -Windows - UNIX integration