OpenVMS x86 Community/Hobbyist License

Everything about buying, using, and managing OpenVMS systems not covered by other sections.

Topic author
medleyb
Visitor
Posts: 1
Joined: Wed Jan 04, 2023 5:46 pm
Reputation: 0
Status: Offline

OpenVMS x86 Community/Hobbyist License

Post by medleyb » Wed Jan 04, 2023 5:52 pm

This item is not present on the roadmap. I am running VMWare Workstation Player and was wondering when this will be available. Thank you.


sms
Master
Posts: 374
Joined: Fri Aug 21, 2020 5:18 pm
Reputation: 0
Status: Offline

Re: OpenVMS x86 Community/Hobbyist License

Post by sms » Tue Apr 30, 2024 11:48 am

Code: Select all

> [...] Unfortunately currently this node is unlicensed for 9.2-2 so no
> networking, etc.

   Is it really unlicensed for a VMS _version_, or is it unlicensed for
today's date?

> OpenVMS 9.2-2 vmdk.

   Copy the license data base from that system to the system with the
expired PAKs?  Look for: SYS$SYSTEM:LMF$LICENSE.LDB

   Worst case: generate PAKs from the VMDK .LDB (LICENSE ISSUE), and use
sys$update:vmslicense.com on the old system to register the
OPENVMS-X86-HAOE PAK, which I'd expect to enable networking, so you
could easily copy the whole LDB.

   When I've used LICENSE ISSUE in the old days, I was happier when I
made a copy of the LDB first, and used LICENSE <whatever> /DATABASE to
play with the copy.  LICENSE ISSUE gives you a PAK, but disables it in
the LDB.  You can re-ENABLE it, but this sort of fiddling can leave
annoying clutter in the LDB history.  With a copy of the LDB, you can
discard it (with all the evidence) when you're done.

Post Reply