HP Integrity Virtual Machines 4.2.5: Release Notes

$! Format and print a UUID
$uuid = f$getsyi("system_uuid")
$len=f$len(uuid)
$if (len .eq. 32)
$then
$ part1 = f$fao("!AS",f$ext(24,8,uuid))
$ part2 = f$fao("!AS",f$ext(20,4,uuid))
$ part3 = f$fao("!AS",f$ext(16,4,uuid))
$ part4 = f$fao("!AS!AS",f$ext(14,2,uuid),f$ext(12,2,uuid))
$ part5 = f$fao("!AS!AS!AS!AS!AS!AS", -
f$ext(10,2,uuid),f$ext(8,2,uuid), -
f$ext(6,2,uuid),f$ext(4,2,uuid), -
f$ext(2,2,uuid),f$ext(0,2,uuid))
$ pr_uuid = f$edit("''part1'-''part2'-''part3'-''part4'-''part5'", -
"lowercase")
$
$ write sys$output "SYSTEM_UUID=''pr_uuid'"
4.4.7 Packaging OpenVMS Guests as Serviceguard Package Not Supported
There is no Serviceguard support for OpenVMS guests in Integrity VM V4.2.5.
4.4.8 TCP/IP and WBEM Services Not Started Automatically at Boot on OpenVMS
Guest
TCP/IP Services and WBEM Services do not start by default after an OpenVMS guest boots. You
must manually restart them or include the command in a startup script. You might see Utilization
Data for OpenVMS guests after a fresh installation or after rebooting and OpenVMS guest.
If the guest has been installed and booted for the first time, configure and start TCP/IP and WBEM
Provider Service manually. For subsequent reboots, starting of these services must be added in a
startup script, so that it starts automatically when a guest boots.
For information about setting up and configuring TCP/IP and WBEM Provider Services, see the
OpenVMS Documentation website.
54 Installing Guests