Community license issue with TCP/IP on x86

Having difficulties when installing the system? Your system runs slowly and requires some tweaking? You can get help here.
Post Reply

Topic author
dmccorm1
Contributor
Posts: 15
Joined: Fri Apr 14, 2023 4:33 pm
Reputation: 0
Status: Offline

Community license issue with TCP/IP on x86

Post by dmccorm1 » Fri Apr 14, 2023 7:13 pm

I've installed three licenses as you can see from the output of "license list" below:

Code: Select all

License Management Facility  V2.0

 License Database File:       SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB;1
 Created on:                  14-APR-2023
 Created by user:             SYSTEM
 Created by LMF Version:      V2.0

 -----------------------------------
 ABS-CLIENT-X86               VSI
 ABS-SERVER-X86               VSI
 DVNETEXT                     VSI
 
But when I run sys$manager:tcpip$config, it seems to think I have no license:

Code: Select all

        VSI TCP/IP Services for OpenVMS Core Environment Configuration Menu
 
        Configuration options:
 
                 1  -  Domain               No Client License
                 2  -  Interfaces
                 3  -  Routing              No Client License
                 4  -  BIND Resolver        No Client License
                 5  -  Time Zone
 
                 A  -  Configure options 1 - 5
                [E] -  Exit menu
 
Enter configuration option: 
Anyone know what I'm doing wrong?

Incidentally, is there a bit of a chicken-and-egg when it comes to installing licenses? You can't SFTP the license script into the VM until you're got TCP/IP up and running. But you can't do that without a license. I installed the three licenses above by painstakingly copying the license commands one at a time.

Added in 4 minutes 35 seconds:
Wait up...I've just figured it out. The license pak I need to install is OPENVMS-X86-BOE which apparently means "base operating environment". Sorry for the interruption!


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

Re: Community license issue with TCP/IP on x86

Post by sms » Fri Apr 14, 2023 10:57 pm

Code: Select all

> Incidentally, is there a bit of a chicken-and-egg when it comes to
> installing licenses? [...]

    Yes.  Various tricks can be employed, such as making a virtual disk
from the big DCL script, mounting it /FOREIGN, copying the data from the
virtual disk to a file, and straightening out the resulting file
attributes, so that VMS thinks it's text.  Manually putting in a few
critical PAKs is often easier.

> [...] painstakingly copying the license commands one at a time.

   It might be easier to try "@ SYS$UPDATE:VMSLICENSE.COM" for the
critical ones.  Usually the answers to its questions are easy enough to
extract/interpret from the commands.

   In the old days, when PAKs were distributed on paper, it was much
more commonly used.


reinhardtjh
Active Contributor
Posts: 39
Joined: Sun Feb 23, 2020 7:49 am
Reputation: 0
Location: Fort Worth, TX USA
Status: Offline

Re: Community license issue with TCP/IP on x86

Post by reinhardtjh » Sat Apr 15, 2023 12:16 am

Your problem is that you don't the right PAKS installed. You want either the "OPENVMS-X86-BOE" or "OPENVMS-X86-HAOE" PAKS which are the "Basic Operating Environment" and "High Availability Operating Environment" respectively. The HAOE is a superset of BOE which includes things like Volume Shadowing, RMS Journaling, VMSCluster (I think) and so on. None of which is required (usually) before you reboot and add the rest of the PAKS. Both include TCP/IP and DECnet and the basic license to log in and run as other than SYSTEM.

As Steven mentioned there can be a lot to enter by hand. My typical method is to pick a few critical ones to enter during the portion of the OpenVMS install when they ask if you want to install PAKS. In the case of x86, it's easy, pick one of the two above and you have enough to continue, reboot and set up either DECnet or TCP/IP or both.

What I usually do is once I have a running system, I open a file from the terminal session I have ( COPY TT: OPENVMS_PAKS.COM ) and then use the file transfer option of my emulator (ZOC V8) to copy the PAK file from my Mac to the OpenVMS system. When done a control-Z ^Z closes the file. Then I run the file with an @OPENVMS_PAKS.COM and I'm done. If you're careful you can cut and paste copy the file through your terminal as well, just watch out for buffer overruns and long lines.

The VSI Alpha PAK are easy in this respect also. YOu just have the ALPHA-SYSTEM and the ALPHA-LP PAKS and you're done. Integrity is easy, too. Same layout as x86 with a BOE and HAOE PAK. The old Compaq/HP PAKS for VAX were a pain in that each product had a separate PAK you had to enter. A few had more than one.
Last edited by reinhardtjh on Sat Apr 15, 2023 12:20 am, edited 1 time in total.
John H. Reinhardt
  • VMS user since 1981

User avatar

m_detommaso
Valued Contributor
Posts: 73
Joined: Thu Jun 06, 2019 6:57 am
Reputation: 0
Location: Brindisi (Italy)
Status: Offline
Contact:

Re: Community license issue with TCP/IP on x86

Post by m_detommaso » Sat Apr 15, 2023 2:31 am


Post Reply