I've noticed that my currently installed HP[E] SSL stuff
is old, so I sucked down the current (free) kits
(HP-I64VMS-SSL-V0104-0503-1 and HP-I64VMS-SSL1-V0100-2L-1).
A glance at the "HPE SSL1 Version 1.0-2H for OpenVMS
Installation Guide and Release Notes July 2016" shows an
interesting item among the "Software Prerequisites":
with patch kits:
VMS84A_MANAGE-V0200 or
VMS84I_MANAGE-V0200
These would seem to be beyond easy reach for a lowly
hobbyist like lowly me. I gather from:
http://h41379.www4.hpe.com/openvms/products/ssl/SSL102H_INSTALLATION_GUIDE.txt
that:
[...] The new manage patch kit - VMS84I_MANAGE-V0200 /
VMS84A_MANAGE-V0200 supplies a modified
VMS$
LPBEGIN-050_STARTUP.COM command procedure, which
ensure [sic] that HPE SSL1 V1.0 startup procedure is
invoked later than HP SSL V1.4 startup procedure.
I assume that I could deal with this by doing the "HPE
SSL1 V1.0 startup procedure" myself (after ensuring that the
"HP SSL V1.4 startup procedure" has been run, but if anyone
wanted to slip me the Alpha and IA64 versions of this
particular miracle patch, then I wouldn't object.
I hope that this patch access limitation is making loads
of money for someone. I'd hate to think that it was a
complete loser for _all_ concerned.