[Info-vax] I64 generic drive boot pointer w/o embedded GUID?

[Rod Regier]

Question:

Is it possible to create a setup on an Integrity server with an OpenVMS boot pointer that would work generically without requiring a specific GUID volume being present for the boot input?

Background:

On Alphaservers running OpenVMS it's possible to configure
or directly boot a "generic" mass storage device.

This makes it possible to setup a default boot pointer for a disk
without being concerned about the specific drive content.

This simplifies operations on servers at deployed customer sites
including cold spares.

On Integrity servers running OpenVMS the boot pointers have the volume content specific GUID encoded into the boot pointer which eliminates any possibility of generic volume boot support.

This makes it more complicated for customer site deployments including cold spares.

Obligatory quote from HPE docs:

NOTE: All EFI boot options embed the disk Globally Unique ID (GUID). Therefore, if you reinstall OpenVMS or restore a system disk from an image backup, you must first delete the old boot options and then add a new boot option. To delete a boot option, use the Delete Boot Option(s) option in the Boot Configuration menu (or Boot Option Maintenance Menu).

Obligatory disclaimer:  Yes, I realize dropping the GUID interlock has security consequences.