======================================================================= VMS Software, Inc. OpenVMS ECO Kit Release Notes ======================================================================= 1 KIT NAME: VMS842L1I_UPDATE-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1: To be installed by all customers. This installation rating serves as a guide to which customers should apply this remedial kit. Reference the attached Disclaimer of Warranty and Limitation of Liability Statement. 2.2 Reboot Requirement: A reboot is required after installing this kit. VMS Software, Inc. strongly recommends that a reboot be performed immediately after kit installation to avoid system instability. If you are installing this kit in a VMScluster, any systems that share the same system disk with the installing system must also be rebooted in order to make use of the new images. 2.3 Version(s) of OpenVMS to which this kit may be applied: VSI OpenVMS for Integrity Servers V8.4-2L1 2.4 EFI boot environment impact: This kit includes an updated Itanium Primary Boot (IPB) image, which is copied into the EFI boot environment partition on the system disk. The EFI update is done automatically by the kit installation, and does not require the manual intervention which was needed in previous kits. Should a catastrophic error cause this update to fail, the disk could be rendered unbootable. Although it is always recommended to backup the system disk prior to installing patch kits, it is vitally important to do so when the boot partition is modified. The procedure which performs the update has recovery capability for any detectable error conditions, but a power failure at just the wrong time during installation (for example) may leave the hardware unable to correctly access the required boot context. In such an extreme case, the disk would need to be restored from a backup. 3 KITS SUPERSEDED BY THIS KIT: None 4 KIT DEPENDENCIES: None NOTE: This kit will be a prerequisite for future patch kits that update VSI OpenVMS for Integrity Servers V8.4-2L1. 5 CONSOLIDATION OF PREVIOUSLY RELEASED PATCH KITS 5.1 Summary of included patch kits The VMS842L1I_UPDATE-V0100 kit is a consolidated roll-up of previously released patch kits for VSI OpenVMS for Integrity Servers V8.4-2L1. The VSI OpenVMS operating system content from all of the following kits is included in the VMS842L1I_UPDATE-V0100 kit: VMS842L1I_ACME-V0100 VMS842L1I_ACMESHR-V0100 VMS842L1I_AUDIT-V0100 VMS842L1I_AUTOGEN-V0100 VMS842L1I_BASRTL-V0100 VMS842L1I_CLUCONFIG-V0100 VMS842L1I_CMIDRIVER-V0100 VMS842L1I_CSMACD-V0100 VMS842L1I_DCL-V0200 VMS842L1I_DEBUG-V0200 VMS842L1I_ERRFMT-V0100 VMS842L1I_F11X-V0100 VMS842L1I_FIBRESCSI-V0200 VMS842L1I_FIBRESCSI-V0400 VMS842L1I_IMGACT-V0200 VMS842L1I_INSTALL-V0100 VMS842L1I_LAN-V0500 VMS842L1I_LCKMGR-V0100 VMS842L1I_LDAP-V0300 VMS842L1I_MDDRIVER-V0100 VMS842L1I_MULTIPATH-V0100 VMS842L1I_NOTARY-V0200 VMS842L1I_PEDRIVER-V0100 VMS842L1I_PRCMGT-V0100 VMS842L1I_PRTSMB-V0100 VMS842L1I_RMS-V0300 VSI OpenVMS patch kits are generally cumulative and contain all content from previous versions of that kit. The exception is VMS842L1I_FIBRESCSI-V0200, which is a prerequisite for the VMS842L1I_FIBRESCSI-V0400 kit. This was due to the complexity of the introduction of 16Gb Fibre Channel support included in VMS842L1I_FIBRESCSI-V0200. Future FIBRESCSI patch kits will once again be completely cumulative. They will contain all the content from any previous FIBRESCSI kits and will automatically update the EFI boot environment if necessary. 5.2 Summary of included release notes The release notes from each of the consolidated kits is included within the VMS842L1I_UPDATE-V0100 kit and will be available for reference after the kit installation. Release notes from prior superseded kits are also included. Because any of these older release notes may come from kits which have been superseded, the image identification and checksum information may not match an image currently on the system disk. This means the correct image and checksum information is contained in the release notes for the particular patch kit which provided the latest version of that file or image. Note that the newest version of a file or image may come from some patch kit which is not included in this consolidation at all, depending on the kit installation order on your system over time. Note: The VMS842L1I_SMIOBJSHR-V0100 kit was superseded by the VMS842L1I_FIBRESCSI-V0200 kit. This is the only superseded kit contained within this consolidated kit which changed name. Any others were superseded by newer versions of the same kit name. The release notes are text files which may be read with an editor or by using the TYPE command. The release notes included in this kit are: SYS$HELP:VMS842L1I_UPDATE-V0100.RELEASE_NOTES (this file) SYS$HELP:VMS842L1I_ACME-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_ACMESHR-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_AUDIT-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_AUTOGEN-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_BASRTL-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_CLUCONFIG-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_CMIDRIVER-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_CSMACD-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_DCL-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_DCL-V0200.RELEASE_NOTES SYS$HELP:VMS842L1I_DEBUG-V0200.RELEASE_NOTES SYS$HELP:VMS842L1I_ERRFMT-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_F11X-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_FIBRESCSI-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_FIBRESCSI-V0200.RELEASE_NOTES SYS$HELP:VMS842L1I_FIBRESCSI-V0300.RELEASE_NOTES SYS$HELP:VMS842L1I_FIBRESCSI-V0400.RELEASE_NOTES SYS$HELP:VMS842L1I_IMGACT-V0200.RELEASE_NOTES SYS$HELP:VMS842L1I_INSTALL-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_LAN-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_LAN-V0400.RELEASE_NOTES SYS$HELP:VMS842L1I_LAN-V0500.RELEASE_NOTES SYS$HELP:VMS842L1I_LCKMGR-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_LDAP-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_LDAP-V0200.RELEASE_NOTES SYS$HELP:VMS842L1I_LDAP-V0300.RELEASE_NOTES SYS$HELP:VMS842L1I_MDDRIVER-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_MULTIPATH-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_NOTARY-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_NOTARY-V0200.RELEASE_NOTES SYS$HELP:VMS842L1I_PEDRIVER-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_PRCMGT-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_PRTSMB-V0100.RELEASE_NOTES SYS$HELP:VMS842L1I_RMS-V0300.RELEASE_NOTES SYS$HELP:VMS842L1I_SMIOBJSHR-V0100.RELEASE_NOTES 5.3 Accessing release notes prior to kit installation Release notes files may be extracted directly from the kit prior to installation for reference purposes. The following commands may be used to extract all or particular release notes files from this kit. For the PRODUCT EXTRACT commands below, you may use an optional /DESTINATION= qualifier to explicitly place the files in a specific location other than the current default directory. To extract all release notes files at once: $ PRODUCT EXTRACT RELEASE_NOTES VMS842L1I_UPDATE /VERSION=V1.0 To extract a particular release notes file: $ PRODUCT EXTRACT FILE VMS842L1I_UPDATE /VERSION=V1.0 - /SELECT= To display the names of all release notes files in the kit: $ PRODUCT LIST VMS842L1I_UPDATE /VERSION=V1.0 /SELECT=*.RELEASE_NOTES 6 NEW FUNCTIONALITY AND PROBLEMS ADDRESSED IN THIS KIT 6.1 Support for 16Gb Fibre Channel and Integrity i6 Servers 6.1.1 New Functionality This kit provides support for using 16Gb Fibre Channel. The associated required hardware is an HPE Integrity SN1000Q single or dual port 16Gb Fibre Channel Host Bus Adapter (HBA), HPE part numbers B9F23A and B9F24A. Because Integrity i6 Servers may only be ordered with 16Gb Fibre Channel HBAs, the functionality within this kit is required to access any SAN devices from an Integrity i6 Server. If you plan to use a 16Gb HBA to boot your system disk, then there are some additional actions required for the boot environment as described in Section 8.3 below. Your SAN Administrator will have to make any necessary adjustments to the fabric infrastructure to use 16Gb FC. 6.1.2 Improvements made since the VMS842L1I_FIBRESCSI-V0200 kit The 16Gb Fibre Channel support was originally provided by the VMS842L1I_FIBRESCSI-V0200 kit. The steps required to boot from 16Gb FC HBAs or access a SAN from an Integrity i6 Server have been simplified and clarified since that original kit. It is no longer necessary to manually update the EFI partition on the system disk after installing the 16Gb support. This kit now does that automatically. The special documentation provided for configuring the 16Gb HBAs on your system has been enhanced to make updating the UEFI Hardware Boot Environment easier. See Section 8.3 below for details. 7 IMAGES OR FILES REPLACED: o From VMS842L1I_ACME-V0100 [SYS$LDR]ACME.EXE Image name: "ACME" Image file identification: "X-5" Image build identification: "XE4H-H4N-000028" Link identification: "Linker I02-37" Link Date/Time: 30-SEP-2018 02:51:53.44 Image Checksum (MD5): 19150FCCE1CE865B9CA954E8449208F7 o From VMS842L1I_ACMESHR-V0100 [SYSLIB]VMS$VMS_ACMESHR.EXE Image name: "VMS$VMS_ACMESHR" Image file identification: "V1.0" Image build identification: "" Link identification: "Linker I02-37" Link Date/Time: 26-NOV-2017 19:16:26.90 Image Checksum (MD5): 96781A0C56FC76E1F75ED2274EB94BC7 o From VMS842L1I_AUDIT-V0100 [SYSEXE]AUDIT_SERVER.EXE Image name: "AUDIT_SERVER" Image file identification: "X-13" Image build identification: "XE4H-H4N-000015" Link identification: "Linker I02-37" Link Date/Time: 26-NOV-2017 19:16:08.45 Image Checksum (MD5): C3FD04D9A1FBF30322EB38939790A21E o From VMS842L1I_AUTOGEN-V0100 [SYSUPD]AUTOGEN.COM Checksum (MD5): 38EB1DC3FB21C095FE8A442617A8C5B3 [SYSHLP]SYSGEN.HLB Checksum (MD5): 1A4CC0533B73BEAC08EFDD7497217A7F o From VMS842L1I_BASRTL-V0100 [SYSLIB]DEC$BASRTL.EXE Image name: "DEC$BASRTL" Image file identification: "V01-038" Image build identification: "XE4H-H4N-000007" Link identification: "Linker I02-37" Link Date/Time: 24-JUN-2017 19:39:59.75 Image Checksum (MD5): B4F0CC78816A3AA49EB2B56442EF0721 o From VMS842L1I_CLUCONFIG-V0100 [SYSMGR]CLUSTER_CONFIG_LAN.COM Checksum (MD5): 88318595CD1E7BF33BBFE771E2449D6B o From VMS842L1I_CMIDRIVER-V0100 [SYS$LDR]SYS$CMIDRIVER.EXE Image name: "SYS$CMIDRIVER" Image file identification: "DW V8.4-2170116" Image build identification: "" Link identification: "Linker I02-37" Link Date/Time: 16-JAN-2017 23:35:21.00 Image Checksum (MD5): 75922C54ACF3EDDDEFE031FBA950B56F o From VMS842L1I_CSMACD-V0100 [SYS$LDR]SYS$LAN_CSMACD.EXE Image name: "SYS$LAN_CSMACD" Image file identification: "X-5" Image build identification: "XE4H-H4N-000007" Link identification: "Linker I02-37" Link Date/Time: 24-JUN-2017 19:40:32.11 Image Checksum (MD5): 9CEB6F1CEEFAD29F85CA8DA7FFDEC4AF o From VMS842L1I_DCL-V0200 [SYSEXE]CDU.EXE Image name: "CDU" Image file identification: "I01-11" Image build identification: "XE4H-H4N-000028" Link identification: "Linker I02-37" Link Date/Time: 30-SEP-2018 02:51:46.43 Image Checksum (MD5): 33C86861F1FFC30A4A260AAE4ECD9C78 [SYSEXE]DCL.EXE Image name: "DCL" Image file identification: "X-55" Image build identification: "XE4H-H4N-000028" Link identification: "Linker I02-37" Link Date/Time: 30-SEP-2018 02:51:46.40 Image Checksum (MD5): 102A11ED7A8BAB4B073585D23811A968 o From VMS842L1I_DEBUG-V0200 [SYSLIB]DEBUG.EXE Image name: "DEBUG" Image file identification: "V8.4-003" Image build identification: "XE4H-H4N-000028" Link identification: "Linker I02-37" Link Date/Time: 30-SEP-2018 02:51:55.74 Image Checksum (MD5): 142501CA1C4B7424F0BB0DCBFEC3442A [SYSLIB]DEBUGSHR.EXE Image name: "DEBUGSHR" Image file identification: "V8.4-003" Image build identification: "XE4H-H4N-000028" Link identification: "Linker I02-37" Link Date/Time: 30-SEP-2018 02:51:54.74 Image Checksum (MD5): 26DFD243FFCA576A04802C4E1F652E25 o From VMS842L1I_ERRFMT-V0100 [SYSEXE]ERRFMT.EXE Image name: "ERRFMT" Image file identification: "X-24" Image build identification: "XE4H-H4N-000016" Link identification: "Linker I02-37" Link Date/Time: 7-DEC-2017 22:04:08.63 Image Checksum (MD5): 4CD86301F8D6A07B15A8B2A9383DD273 o From VMS842L1I_F11X-V0100 [SYS$LDR]F11BXQP.EXE Image name: "F11BXQP" Image file identification: "XQP V842L1R E4H" Image build identification: "XE4H-H4N-000021" Link identification: "Linker I02-37" Link Date/Time: 13-MAY-2018 07:50:32.14 Image Checksum (MD5): D8595DF77309B878C43F37BB34290E3D [SYS$LDR]F11BXQP.STB Checksum (MD5): DC9692DE07281FABB3D0AAD6998ED523 [SYSEXE]VERIFY.EXE Image name: "VERIFY" Image file identification: "X-28" Image build identification: "XE4H-H4N-000021" Link identification: "Linker I02-37" Link Date/Time: 13-MAY-2018 07:50:33.97 Image Checksum (MD5): 61DB5505F806FDF7ECC025871DC45DC1 o From VMS842L1I_FIBRESCSI-V0200 [SYS$LDR]SYS$DKDRIVER.EXE Image name: "SYS$DKDRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000013" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:06:54.82 Image Checksum (MD5): 4364D9A572B53937E29943D178E756A7 [SYS$LDR]SYS$FGEDRIVER.EXE Image name: "SYS$FGEDRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000013" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:07:14.06 Image Checksum (MD5): 5F6CF63D8B522AFCCDC11BE8D4C00379 [SYS$LDR]SYS$PGADRIVER.EXE Image name: "SYS$PGADRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000013" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:07:09.74 Image Checksum (MD5): 344B0725D22C47650499765146169F54 [SYS$LDR]SYS$PGQBTDRIVER.EXE Image name: "SYS$PGQBTDRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000013" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:07:00.18 Image Checksum (MD5): 36F97AA5DB6262DB20B9AD1251C8A226 [SYS$LDR]SYS$PLATFORM_SUPPORT.EXE Image name: "SYS$PLATFORM_SUPPORT" Image file identification: "X-35" Image build identification: "XE4H-H4N-000013" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:06:57.26 Image Checksum (MD5): ECB5A02C8F11F3FCAE3D1B592759267B [SYSLIB]FC$SDA.EXE Image name: "FC$SDA" Image file identification: "X-43" Image build identification: "XE4H-H4N-000013" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:07:21.20 Image Checksum (MD5): 1A3265B52976DB6CC616718DAB026CFB [SYSLIB]IOGEN$CISS_CONFIG.EXE Image name: "IOGEN$CISS_CONFIG" Image file identification: "X-11" Image build identification: "XE4H-H4N-000013" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:06:25.52 Image Checksum (MD5): D4E1F6190972253032BA94B9AB0B3F40 [SYSLIB]IOGEN$PCI_CONFIG.EXE Image name: "IOGEN$PCI_CONFIG" Image file identification: "X-11" Image build identification: "XE4H-H4N-000013" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:06:27.56 Image Checksum (MD5): FAFCA6E8BFBEF84E952B6D977A7A0A46 [SYSLIB]SMI$OBJSHR.EXE Image name: "SMI$OBJSHR" Image file identification: "X40-A9" Image build identification: "XE4H-H4N-000013" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:06:55.37 Image Checksum (MD5): 4D6428595CCC768450D7584FA204338C [SYSEXE]IPB.EXE Image name: "IPB" Image file identification: "X-4" Image build identification: "" Link identification: "Linker I02-37" Link Date/Time: 19-SEP-2017 08:06:55.54 Image Checksum (MD5): 0802A9EF7436302A9EA50BC516F4A876 [SYSEXE]SYS$CONFIG.DAT Checksum (MD5): 55E42180622C8AAD183047F881EE79EC o From VMS842L1I_FIBRESCSI-V0400 [SYS$LDR]SYS$PGQDRIVER.EXE Image name: "SYS$PGQDRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000027" Link identification: "Linker I02-37" Link Date/Time: 23-SEP-2018 14:59:29.10 Image Checksum (MD5): 1BFF70DC7766069533C3FE6C2229258E [SYSLIB]HBA_VMS.EXE Image name: "HBA_VMS" Image file identification: "V1.0" Image build identification: "XE4H-H4N-000027" Link identification: "Linker I02-37" Link Date/Time: 23-SEP-2018 14:59:34.54 Image Checksum (MD5): 30184C20C461BA424A8FE9736317A413 [SYSHLP.EXAMPLES.SNIA]HBA_VMS.C Checksum (MD5): 7B5BA5CCB105AAFD24AEE2009BAA3A8D o From VMS842L1I_IMGACT-V0200 [SYS$LDR]IMAGE_MANAGEMENT.EXE Image name: "IMAGE_MANAGEMENT" Image file identification: "X-5" Image build identification: "XE4H-H4N-000009" Link identification: "Linker I02-37" Link Date/Time: 24-JUL-2017 22:15:25.34 Image Checksum (MD5): DEF8CBDE64BBA81B2FDE200CBD64CDAA [SYS$LDR]IMAGE_MANAGEMENT.STB Checksum (MD5): 1209EC039E5833ED285B5208983D1494 o From VMS842L1I_INSTALL-V0100 [SYSEXE]INSTALL.EXE Image name: "INSTALL" Image file identification: "X-35" Image build identification: "XE4H-H4N-000008" Link identification: "Linker I02-37" Link Date/Time: 19-JUL-2017 04:28:08.70 Image Checksum (MD5): FC013E66B299F19300A991C485A74F3A o From VMS842L1I_LAN-V0500 [SYS$LDR]SYS$ER57711.EXE Image name: "SYS$EW57711DRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:55.43 Image Checksum (MD5): 0478AAA91C51FDD5D92EE32FB8F3EA6D [SYS$LDR]SYS$ER57711_MON.EXE Image name: "SYS$EW57711DRIVER_MON" Image file identification: "X-5" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:55.74 Image Checksum (MD5): 5248EDC8E7B7D0087AF1F20C9966E810 [SYS$LDR]SYS$EW5700.EXE Image name: "SYS$EW5700DRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:51.66 Image Checksum (MD5): 1CFB1ED175A1D2EEC2437322D354ADBA [SYS$LDR]SYS$EW5700_MON.EXE Image name: "SYS$EW5700DRIVER_MON" Image file identification: "X-5" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:52.68 Image Checksum (MD5): 6BD72B88ADEE61665BA550022ACE22EC [SYS$LDR]SYS$EW57711.EXE Image name: "SYS$EW57711DRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:55.43 Image Checksum (MD5): 0478AAA91C51FDD5D92EE32FB8F3EA6D [SYS$LDR]SYS$EW57711_MON.EXE Image name: "SYS$EW57711DRIVER_MON" Image file identification: "X-5" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:55.74 Image Checksum (MD5): 5248EDC8E7B7D0087AF1F20C9966E810 [SYS$LDR]SYS$EWBE3.EXE Image name: "SYS$EWBE3DRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:56.06 Image Checksum (MD5): B4F7788C80A39B4E6B57369E2896824D [SYS$LDR]SYS$EWBE3_MON.EXE Image name: "SYS$EWBE3DRIVER_MON" Image file identification: "X-5" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:56.27 Image Checksum (MD5): DD7F498C0B358ACF015E81541DB951DD [SYS$LDR]SYS$LLDRIVER.EXE Image name: "SYS$LLDRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:56.52 Image Checksum (MD5): F4BCCD325A51E5B17FFE79005A1214D7 [SYSHLP]SDA.HLB Checksum (MD5): 15E2C1DABE3680EBB68CE0032B4152F0 [SYSEXE]LANCP.EXE Image name: "LANCP" Image file identification: "X-93A1" Image build identification: "XE4H-H4N-000025" Link identification: "Linker I02-37" Link Date/Time: 4-AUG-2018 13:24:49.86 Image Checksum (MD5): 8CF45615C7368D95A4BCA8016E8F0C33 o From VMS842L1I_LCKMGR-V0100 [SYS$LDR]LOCKING.EXE Image name: "LOCKING" Image file identification: "X-5" Image build identification: "XE4H-H4N-000007" Link identification: "Linker I02-37" Link Date/Time: 24-JUN-2017 19:40:27.88 Image Checksum (MD5): 1D2A8828E8D354415AD0DAE51F1E0626 [SYS$LDR]SYS$CLUSTER.EXE Image name: "SYS$CLUSTER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000007" Link identification: "Linker I02-37" Link Date/Time: 24-JUN-2017 19:40:17.36 Image Checksum (MD5): 1F83BF72B01C4A80AE1B694752E3D6D5 [SYS$LDR]SYS$CLUSTER_MON.EXE Image name: "SYS$CLUSTER_MON" Image file identification: "X-5" Image build identification: "XE4H-H4N-000007" Link identification: "Linker I02-37" Link Date/Time: 24-JUN-2017 19:40:19.76 Image Checksum (MD5): 82452C2A3D77A44422CD6D0D6A6193E4 o From VMS842L1I_LDAP-V0300 [SYSLIB]LDAP$SHR.EXE Image name: "LDAP$SHR" Image file identification: "LDAP V2.0-05002" Image build identification: "XE4H-H4N-000032" Link identification: "Linker I02-37" Link Date/Time: 24-FEB-2019 10:33:04.37 Image Checksum (MD5): B40F5724758F5D7C9CF946FFAB4EF542 [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE Image name: "LDAPACME$LDAP-STD_ACMESHR" Image file identification: "LDAP-STD V1.26" Image build identification: "" Link identification: "Linker I02-37" Link Date/Time: 24-FEB-2019 10:33:22.38 Image Checksum (MD5): 6EABEDA745C28CAD4A71B2D37715352E [SYSLIB]LDAPACME$LDAP-STD_ACMESHR_TRACE.EXE Image name: "LDAPACME$LDAP-STD_ACMESHR_TRACE" Image file identification: "STD_TRACE V1.26" Image build identification: "" Link identification: "Linker I02-37" Link Date/Time: 24-FEB-2019 10:33:22.67 Image Checksum (MD5): 73D4838044179E3C9990CCBA9336399E [SYSLIB]SYS$STARLET_C.TLB Checksum (MD5): 8630B3F3B3C229855D09026358D3AD36 o From VMS842L1I_MDDRIVER-V0100 [SYS$LDR]SYS$MDDRIVER.EXE Image name: "SYS$MDDRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000024" Link identification: "Linker I02-37" Link Date/Time: 15-JUL-2018 05:15:49.67 Image Checksum (MD5): 942313AD8E49CA4980A121C740E1421E o From VMS842L1I_MULTIPATH-V0100 [SYS$LDR]MULTIPATH.EXE Image name: "MULTIPATH" Image file identification: "X-5" Image build identification: "XE4H-H4N-000007" Link identification: "Linker I02-37" Link Date/Time: 24-JUN-2017 19:40:28.87 Image Checksum (MD5): 7FB257CA294D1C1F29BE7E8176C2A79B [SYS$LDR]MULTIPATH.STB Checksum (MD5): CB24C10B7B970768D8D93E31BA468ED4 [SYS$LDR]MULTIPATH_MON.EXE Image name: "MULTIPATH_MON" Image file identification: "X-5" Image build identification: "XE4H-H4N-000007" Link identification: "Linker I02-37" Link Date/Time: 24-JUN-2017 19:40:29.15 Image Checksum (MD5): 740C61C6F0A0A94F99559483DFD84FE8 [SYS$LDR]MULTIPATH_MON.STB Checksum (MD5): AE9C5AD2419126392E34C1B287EED715 [SYSEXE]SHADOW_SERVER.EXE Image name: "SHADOW_SERVER" Image file identification: "X-29" Image build identification: "XE4H-H4N-000007" Link identification: "Linker I02-37" Link Date/Time: 24-JUN-2017 19:40:16.64 Image Checksum (MD5): 37C2BC2028B4D5FA815EB8ED58B07493 o From VMS842L1I_NOTARY-V0200 [SYSEXE]VMS_NOTARY.EXE Image name: "VMS_NOTARY" Image file identification: "V1.3" Image build identification: "XE4H-H4N-000026" Link identification: "Linker I02-37" Link Date/Time: 30-AUG-2018 13:09:20.35 Image Checksum (MD5): 23182FF756003B9C03DF69A09810B86B [SYSLIB]VMS_NOTARY_SHR.EXE Image name: "VMS_NOTARY_SHR" Image file identification: "V1.3" Image build identification: "XE4H-H4N-000026" Link identification: "Linker I02-37" Link Date/Time: 30-AUG-2018 13:09:19.81 Image Checksum (MD5): BA498BE58CEFBEB0CF0FBF39534C0CB2 o From VMS842L1I_PEDRIVER-V0100 [SYS$LDR]SYS$PEDRIVER.EXE Image name: "SYS$PEDRIVER" Image file identification: "X-5" Image build identification: "XE4H-H4N-000018" Link identification: "Linker I02-37" Link Date/Time: 18-MAR-2018 04:33:43.46 Image Checksum (MD5): BB385FC134808BEFF3D5534BE10D9518 [SYS$LDR]SYS$PEDRIVER.STB Checksum (MD5): 45CB9D4AE914D2E797E3907AC9A81C8F [SYS$LDR]SYS$PEDRIVER_MON.EXE Image name: "SYS$PEDRIVER_MON" Image file identification: "X-5" Image build identification: "XE4H-H4N-000018" Link identification: "Linker I02-37" Link Date/Time: 18-MAR-2018 04:33:46.00 Image Checksum (MD5): 29C521204447DC0490252A98541356D5 [SYS$LDR]SYS$PEDRIVER_MON.STB Checksum (MD5): FB314E91948910FE5ACF97E643B1DCE4 o From VMS842L1I_PRCMGT-V0100 [SYS$LDR]PROCESS_MANAGEMENT.EXE Image name: "PROCESS_MANAGEMENT" Image file identification: "X-5" Image build identification: "XE4H-H4N-000021" Link identification: "Linker I02-37" Link Date/Time: 13-MAY-2018 07:50:43.49 Image Checksum (MD5): 29AA293AA1A8A743C9D61440A1206394 [SYS$LDR]PROCESS_MANAGEMENT.STB Checksum (MD5): 6E6345C5249A563857265BAB8110E412 [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE Image name: "PROCESS_MANAGEMENT_MON" Image file identification: "X-5" Image build identification: "XE4H-H4N-000021" Link identification: "Linker I02-37" Link Date/Time: 13-MAY-2018 07:50:45.54 Image Checksum (MD5): 5C8C69DE565465BDD0158EC5606657D4 [SYS$LDR]PROCESS_MANAGEMENT_MON.STB Checksum (MD5): 98FB4A422C07C4A814A0B85831EE8BE5 o From VMS842L1I_PRTSMB-V0100 [SYSLIB]SMBSRVSHR.EXE Image name: "SMBSRVSHR" Image file identification: "X-6" Image build identification: "XE4H-H4N-000028" Link identification: "Linker I02-37" Link Date/Time: 30-SEP-2018 02:51:26.34 Image Checksum (MD5): 9370E4FB144DA93582E0CA742081A7BB o From VMS842L1I_RMS-V0300 [SYS$LDR]RMS.EXE Image name: "RMS" Image file identification: "X-5" Image build identification: "XE4H-H4N-000028" Link identification: "Linker I02-37" Link Date/Time: 30-SEP-2018 02:51:53.75 Image Checksum (MD5): 6A996BAA69855EE1C3B80060A58C6D5D [SYS$LDR]RMS.STB Checksum (MD5): F80B576F2D579A5BD1F6F97763E501F7 Note: VMS Software, Inc. will only distribute kits in signed form. There is no need for most customers to compare file checksums for security or kit integrity reasons. However, some sites may require such checking even when using signed kits. The image or file checksums are supplied (in MD5 format) to provide comparisons to the extracted final kit files. To find a file checksum, use: $ CHECKSUM/ALGORITHM=MD5 filename $ SHOW SYMBOL CHECKSUM$CHECKSUM Note: Because a file or image may be replaced by multiple patch kits over time, a PCSI generation number is used to insure that the latest version of the file or image is preserved on your system during PRODUCT INSTALL of a patch kit. Should a particular kit installation discover a newer version of a file or image in place on the system disk, the following message will be displayed: %PCSI-I-RETAIN, file will not be replaced because file from kit has lower generation number This is a normal occurrence depending on the order of kit installation. The correct version of the file or image will remain on the system after the current kit installation. The %PCSI-I-RETAIN message is informational only and does not indicate a problem. 8 INSTALLATION INSTRUCTIONS 8.1 Compressed File This kit is provided as a self-extracting ZIPEXE file. To expand this file to the installable PCSI kit, execute the file image with the following command: $ RUN VMS842L1I_UPDATE-V0100.ZIPEXE 8.2 Installation Command Install this kit with the POLYCENTER Software Installation Utility by logging into the SYSTEM account, and typing the following at the DCL prompt: $ PRODUCT INSTALL VMS842L1I_UPDATE [/SOURCE=location of kit] The kit location may be a tape drive, CD/DVD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. This kit requires the use of /RECOVERY_MODE and /SAVE_RECOVERY_DATA and will automatically set them; they do not need to be present on the command line. User-selectable options for installation behavior and scripting are available in this kit, see Appendix A for further details. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 8.3 Additional Actions Required for System Disks using 16Gb FC HBAs If you plan on using a 16Gb Fibre Channel HBA as the boot path for your system disk, there are additional steps to perform to update the boot environment. These steps are not necessary if your system boots from a different adapter type or slower FC HBA. As Integrity i6 Servers may only be ordered with 16Gb adapters, these steps will be necessary for booting an i6 system from the SAN. 8.3.1 Updating the EFI Partition on the System Disk This kit will automatically update the EFI partition on the system disk with the necessary IPB.EXE image with VMS boot support, so that any Integrity system booting from this system disk can correctly utilize 16Gb Fibre Channel adapters. It is no longer necessary to use the UPDATE_IPB_IN_EFI procedure to manually update the EFI partition (which was required after installing the VMS842L1I_FIBRESCSI-V0200 kit). 8.3.2 Updating the UEFI Hardware Boot Environment To enable booting from a 16Gb FC HBA, you must update the hardware UEFI environment to enable the use of the new 16Gb HBA during boot. This step must be done for each system which will boot from the disk, once for each port on each 16Gb FC HBA. Each port must be enabled individually to allow the boot environment to use that port to find the system disk. To enable the 16Gb HBA ports within the UEFI environment, follow the instructions in the following PDF file, which is added to your SYS$UPDATE directory during installation of this kit. This file is provided in PDF format since it has several screen shots to help guide you through the necessary actions. Use your favorite browser or PDF viewer to access the file: SYS$UPDATE:ENABLING_16GB_FC_HBAS_FOR_BOOT.PDF Or, if you are accessing the file from a non-VMS machine, navigate using the disk and directory names explicitly, translating the file name syntax as necessary. For example: :[VMS$COMMON.SYSUPD]ENABLING_16GB_FC_HBAS_FOR_BOOT.PDF Note that this file has been significantly enhanced since the original version supplied with the VMS842L1I_FIBRESCSI-V0200 kit. This newer copy of the document will replace the older one on your system disk if you had previously installed that kit. If you have already enabled any 16Gb HBAs on your system from that time, then these steps do not need to be repeated. The VMS file name for this .PDF document is a carryover from the original VMS842L1I_FIBRESCSI-V0200 kit for compatibility. Internally, the .PDF document is now titled: VSI OpenVMS 16 Gb Fibre Channel HBA Configuration Guide 9 COPYRIGHT ******************************************************************** * * * VMS SOFTWARE, INC. CONFIDENTIAL. This software is confidential * * proprietary software licensed by VMS Software, Inc., and is not * * authorized to be used, duplicated or disclosed to anyone without * * the prior written permission of VMS Software, Inc. * * Copyright 2019 VMS Software, Inc. * * * ******************************************************************** 10 DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL VMS SOFTWARE, INC. BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH. 11 PATCH ID I64VMS-VMS842L1I_UPDATE-V0100--4 APPENDIX A - User-selectable control options and scripting considerations Controlling kit behavior for introductory questions --------------------------------------------------- Starting with this VMS842L1I_UPDATE-V0100 kit, the VSI ECO kit mechanism infrastructure for VSI OpenVMS patch kits has been enhanced to provide user-selectable control options for kit dialogue interaction and automated scripting capability. All future kits that support this functionality will include this appendix in their release notes. The general form of a VSI ECO patch kit, when using PRODUCT INSTALL, consists of three initial questions regarding these topics: 1. System disk backup: A reminder that VSI recommends backing up the system disk before installing patches, followed by a "Do you want to continue?" yes/no question, default = YES. 2. Reboot requirement: A summary of whether the kit being installed requires a system reboot, followed by a "Do you want to continue?" yes/no question, default = YES. 3. Archival of updated files: A description of saving an "_OLD" copy of each image or file updated by the kit, followed by a "Do you want to save "_OLD" copies of replaced files?" yes/no question, default = NO. Other questions may be asked later, depending on the target disk or system environment or other kit-specific requirements. Note: An initial "Do you want to continue?" question may be asked directly by the PCSI utility during any PRODUCT command -- this has nothing to do with the kit being used. To avoid that question, you must supply sufficient detail to uniquely identify the product you wish to use and specify /OPTIONS=NOCONFIRM on the PRODUCT command. Control options are available to customize the dialogue for the initial three kit questions. The controls are logical names, which may be defined in the process logical name table with a value of YES or NO. To modify the behavior of the VSI ECO patch kit regarding the initial questions, define one or more of the following logical names before issuing the PRODUCT INSTALL command. o To skip one or more of the questions, define the corresponding logical name shown here to YES: SKIP$BACKUP - Skip system backup awareness question. SKIP$REBOOT - Skip system reboot awareness question. SKIP$ARCHIVE_OLD - Skip question about saving "_OLD" files. This will take the default, which is NO. SKIP$INTRO - Skip all three of the above questions. o To specifically override the default for saving "_OLD" files, define this logical name to YES or NO: VSIKIT$ARCHIVE_OLD - Sets an answer for saving "_OLD" files behavior. This will skip the archive "_OLD" files question regardless of the above SKIP$* logical names. o Two additional logical names may be defined as YES to modify the amount of explanatory text displayed for each question: VSIKIT$VERBOSE - Shows all explanatory text for questions. VSIKIT$BRIEF - Skips some general details in the explanations. The default if neither name is defined is VERBOSE. If both names are defined to YES, VERBOSE overrides BRIEF. The BRIEF form is displayed for any questions that are skipped. For example, to skip all three questions but save an archive "_OLD" copy of each replaced file: $ DEFINE VSIKIT$ARCHIVE_OLD YES $ DEFINE SKIP$INTRO YES $ PRODUCT INSTALL Standard behavior for YES/NO questions asked during kit installation -------------------------------------------------------------------- Any YES/NO questions asked during kit installation now follow these rules: 1. Ctrl-Y issued while a question is being asked will force the current PRODUCT operation to terminate. This is completely safe to do while the initial three questions are being asked during PRODUCT INSTALL as no changes have yet been made to the target disk. 2. Some questions may ignore Ctrl-Y and ask for a specific answer, if aborting the current operation may have side effects. PCSI may trap Ctrl-Y directly for some PRODUCT operations. Ctrl-Y may be disabled during some sensitive kit processing. 3. The default YES/NO answer is automatically chosen if a kit is installed from a batch job, unless explicitly overridden by a logical name which provides the particular value, such as VSIKIT$ARCHIVE_OLD. Installing this kit from a batch job ------------------------------------ To install a kit from a batch job you will need to fully qualify the kit name so PCSI will have enough information to select the kit without asking for confirmation. For example, to install this kit: $ PRODUCT INSTALL VMS842L1I_UPDATE/VERSION=V1.0/OPTIONS=NOCONFIRM If the kit is located in a directory other than the current default directory, you will also need to add the qualifier: /SOURCE= For a batch job, any YES/NO question will automatically select the default answer. Use the control logical names explained above to modify the behavior if necessary. For the system disk backup and reboot questions, the batch behavior is identical to the default. For the save "_OLD" files question, define the VSIKIT$ARCHIVE_OLD logical name to YES if you want to save copies of the files, since the batch default is NO. Deprecated logical names from HPE patch kits -------------------------------------------- The three names listed below were used by older VSI OpenVMS patch kits for compatibility with HPE patch kit behavior. These old names continue to function, but VSI encourages you to modify any scripts you may have to use the new names shown instead: Old name New name --------------- -------------------- NO_ASK$BACKUP SKIP$BACKUP NO_ASK$REBOOT SKIP$REBOOT ARCHIVE_OLD VSIKIT$ARCHIVE_OLD