openvms-x86-INSTOE

[rodprince]

I recently download x86vms-openvms-v0902-3. I started to rebuild our system image from scratch. While a little bit time consuming, its good to run thru all my documented steps, polish up any confusing steps so that others in the company could do it next time.

I going thru my steps, and I started to load all the licenses that we use for dev/prod. We don't use many, kind of simple over all. I loaded the OpenVMS-x86-BOE license when I installed VMS. I tend to load the Pascal, C, C++ and VaxSet licenses when I am ready to push the kits to the system and install them. So I load the pak for them, do a $show lice to make sure I am ready to start install things and I see something extra.

I am sure, I did not load the OpenVMS-X86-INSTOE pak at any point, since I don't have any info for this product. Will it be an issue if its terminated?

Code: Select all

$show lice
------- Product ID -------- ---- Rating ----- -- Version --
Product Producer Units PCL Activ Version Release Termination
C VSI 0 0 1 0.0 (none) 30-APR-2025
CXX-V VSI 0 0 1 0.0 (none) 30-APR-2025
OPENVMS-X86-BOE VSI 0 1 0 0.0 (none) 30-APR-2025
OPENVMS-X86-INSTOE VSI 2 1 0 0.0 (none) 1-DEC-2024
PASCAL VSI 0 0 1 0.0 (none) 30-APR-2025
VAXSET VSI 0 1 0 0.0 (none) 30-APR-2025
%SHOW-I-TERMIMM, 1 license has terminated or will terminate in 30 days
BBIRCH::SYSTEM$

Rod

[arne_v]

https://docs.vmssoftware.com/vsi-openvm ... ion-guide/

last 2 lines of section 1.4.1.

[dgordon]

When I was originally asked to develop the feature that eventually became the INSTOE, I intended to automatically remove it on the next reboot after it expired. The eventual delivery mechanism, which didn't require adding any new files to the base OS made it easier to simply document the safe removal. One problem with automatic removal of a short-term license is that if for any reason the system rebooted with a bad date, the only way to recover the deleted PAK is by reinstalling the OS.

At the same time, however, we also fixed one of the issues that prompted the creation of the installation license in the first place. We expanded the copy & paste buffer on the x86 console so that it was possible to c&p an entire PAK at once. The installation license also permits the system to autoconfigure via DHCP, another possibly useful feature.

Note that the INSTOE is only installed during a fresh installation of V9.2-3 (and later), not during an upgrade. On upgrade, we figure you already have a working license data base and don't need a silly 5-day license to get started.

[hb]

This is the way it works: You get something for free, even if you do not want or need it.

... One problem with automatic removal of a short-term license is that if for any reason the system rebooted with a bad date, the only way to recover the deleted PAK is by reinstalling the OS.

You can still log into VMS from the console and register your BOE PAK. But if the INSTOE PAK is really needed, it is very likely that someone will figure out how to do it without reinstalling the OS.
I think rebooting with a bad date is a rare case. No need to add something to the OS is probably the main reason to implement it this way. Unfortunately the installer seems to have no option. And yes, that would require a change somewhere else. The best would have been ... OK, just dreaming.

At the same time, however, we also fixed one of the issues that prompted the creation of the installation license in the first place. We expanded the copy & paste buffer on the x86 console so that it was possible to c&p an entire PAK at once. The installation license also permits the system to autoconfigure via DHCP, another possibly useful feature.

The change to make "the creation of the installation license" easier is not limited to the installation and/or creation of the license PAKs. It affects any paste on the x86 console. If you (have to) use the console, you can now paste more data before getting a "SYSTEM-W-DATAOVERUN, data overrun". I'm not sure if this is important or if this is covered in the release notes.

Note that the INSTOE is only installed during a fresh installation of V9.2-3 (and later), not during an upgrade. On upgrade, we figure you already have a working license data base and don't need a silly 5-day license to get started.

Note that INSTOE is only installed (during...) on the target system disk. You can not use it at installation time to (auto)configure your network (via DHCP).