On 2020-07-21 03:38:46 +0000, Bob Wilson said:
The 32-bit VAX source code control environment was made common across
the various OpenVMS development environments, including migrating to
the use of VDE across the 32- and 64-bit environments. That
development environment was originally a mixed-architecture VAX and
Alpha cluster for 32-bit (STAR::) and a mixed-architecture Alpha and
Itanium cluster for 64-bit (EVMS::). That work toward common source
code control tooling was not tied to an OpenVMS release, but was an
incremental process that happened through the V6.2 timeframe.
VDE itself was portable, and able to build and operate VDE itself on
all three architectures. The build tooling remained separate from the
source code control tooling, as Bob mentions.
In addition to porting the source code control environment around, I've
also ported the 64-bit OpenVMS build environment around for
tool-testing purposes, and that port took a few days to get
mostly-working on a testing-configured AlphaServer system.
The source code control and VDE environment was a PCSI kit, starting
around Y2K. See VDE on the OpenVMS Freeware for details. AFAIK, the
build environment was not packaged.
Approximately nobody was working with the 32-bit build environment
after V7.3, save for building incremental fixes. Source code control
was still active, as were targeted builds for patches. I don't recall
if there were any full builds after V7.3 shipped, but there would not
have been very many of those.
The source code control tool VDE itself was under source control in a
VDE library, as well as a separate VDE library containing the
regression test suite and the pieces necessary for testing Rdb database
upgrades, and for testing VDE database changes.
Results disks were used for new builds with new results disks, and for
building fixes that didn't necessitate running a complete system build.
Getting a build would require either a results disk, or manually
recreating a results disk. This'll be part of the difficulty that Bob
mentions about restarting the older 32-bit builds.
Parts of the hardware environment were on DSA-class storage through the
early V6 range (and using host-based RAID-1 HBVS shadowing and
software-toggling RA disks between clusters was common), was then
stored on HSJ for a while—had a *wonderful* time with an HSJ-triggered
Rdb database corruption—and the database storage was then migrated to
EVA storage, IIRC. EVA was massively faster than the HSJ storage. The
32-bit and 64-bit environments remained separate, the rest of the
hardware used moved around.
Beyond the rest of the mess, the 32-bit layered products including
TCP/IP Services—which really shouldn't be a layered product—or its
replacement VSI IP stack, will have to be rebuilt to get anywhere with
the 32-bit environment.
The OpenVMS source listings CD that David is referencing in the quoted
text above are expurgated listings. There are facilities and files
omitted from that. And components such as the checked-in compilers and
tools were not included in that. Nor the build procedures, for that
matter.
And circling back to the original discussion, I expect that a fair
portion of the hobbyist interest in the 32-bit OpenVMS VAX will drop
off for a lot of folks as the OpenVMS x86-64 native environment becomes
available to hobbyists, too. But HPE are the folks y'all want to
discuss this with, if y'all want legitimate HPE OpenVMS VAX V7.3
hobbyist licenses past the end of 2021. Or buy licenses from HPE,
before they stop selling those. And if they're offering NAS PAKs for
the same price, ask for the upper-tier NAS PAKs and not the lower-tier
PAKs.
--
Pure Personal Opinion | HoffmanLabs LLC