======================================================================= VMS Software, Inc. OpenVMS ECO Kit Release Notes ======================================================================= 1 KIT NAME: VMS842L3I_LMF-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): VMSclusters 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: No reboot is necessary after installation of this kit. However there are additional steps that must be performed to use the images provided by this kit on all nodes of a VMSCluster using a common system disk. Refer to Section 8.3, "Special Installation Instructions", for required post-installation actions. 2.3 Version(s) of VSI OpenVMS to which this kit may be applied: VSI OpenVMS for Integrity Servers V8.4-2 VSI OpenVMS for Integrity Servers V8.4-2L1 VSI OpenVMS for Integrity Servers V8.4-2L3 The images and files in this kit apply to any of these VSI OpenVMS versions. Because patch kits are removed by PCSI during upgrades to newer OpenVMS versions, the kit will need to be reinstalled if an upgrade is done from an older listed version to any newer listed version. 3 KITS SUPERSEDED BY THIS KIT: None Note: There was no LMF V1.0 patch kit for VSI OpenVMS for Integrity Servers V8.4-2, V8.4-2L1, or V8.4-2L3. This kit is named V2.0 to allow a common patch version level across all current VSI OpenVMS versions which have equivalent functionality and defect repair. 4 KIT DEPENDENCIES: VMS842I_NOTARY-V0200 (if installing on V8.4-2) All VSI OpenVMS patch kits now require the Notary V2.0 patch kit for their respective version of VSI OpenVMS. This is to ensure correct validation regardless of the manifest version in use. VMS842L1I_UPDATE-V0100 (if installing on V8.4-2L1) All new patch kits for VSI OpenVMS for Integrity Servers V8.4-2L1 require the VMS842L1I_UPDATE-V0100 kit. None (if installing on V8.4-2L3) 5 PROBLEMS ADDRESSED IN THIS KIT 5.1 Add X86_64 support for mixed-architecture VMSclusters 5.1.1 Problem Description In VMSclusters, there must either be a single common license database or, in the case of multiple databases, the content of all databases must be identical. In a mixed-architecture VMScluster, the License Management Facility (LMF) on Alpha and IA64 nodes must be able to understand and process PAKs for OpenVMS x86-64. For V8.4-2 or V8.4-2L1 only: This kit includes the IA64_LMF.CLD command syntax definition file and updates DCLTABLES, modifying the behavior of the LICENSE command. Note that only processes created after the kit update will have the new LICENSE command definition. The LICENSE command syntax was included directly in V8.4-2L3. 5.1.2 Images and/or Files Affected: [SYSEXE]LMF.EXE [SYSEXE]SHOW.EXE [SYSMSG]LMF_MESSAGE.EXE [SYSUPD]IA64_LMF.CLD (if installing on V8.4-2 or V8.4-2L1) 5.1.3 VSI case identifier Jira UT-119, BO-1395 5.1.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.2 Update VMSLICENSE.COM for X86_64 5.2.1 Problem Description SYS$UPDATE:VMSLICENSE.COM has been updated to recognize the X86_64 keyword in the KEY OPTIONS field. Two pieces of syntax have been enhanced to avoid errors when manually entering PAKs. The first is double quotes in the TOKEN field, and the second is parentheses around the list in the KEY OPTIONS field. 5.2.2 Images and/or Files Affected: [SYSUPD]VMSLICENSE.COM [SYSMSG]VMSLICENSE_LANGUAGE.COM 5.2.3 VSI case identifier Jiras QTV-746, QTV-750 5.2.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.2.5 Workaround For PAKs supplied in command procedure format, simply execute the command procedure directly instead of using VMSLICENSE.COM. 6 PROBLEMS ADDRESSED FROM PREVIOUS KITS None 7 IMAGES OR FILES REPLACED: [SYSEXE]LMF.EXE Image name: "LMF" Image file identification: "X-28A1" Image build identification: "XFWL-C6E-000133" Link identification: "Linker I02-37" Link Date/Time: 27-SEP-2023 01:50:17.07 Image Checksum (MD5): BF4B22278E7D95994F42C249D9EB6AA0 [SYSEXE]SHOW.EXE Image name: "SHOW" Image file identification: "X-8" Image build identification: "XFWL-C6E-000133" Link identification: "Linker I02-37" Link Date/Time: 27-SEP-2023 01:50:59.66 Image Checksum (MD5): 6E7A9E2DFF8789469B1650302B6C86BB [SYSMSG]LMF_MESSAGE.EXE Image name: "LMF_MESSAGE" Image file identification: "X-15" Image build identification: "XFWL-C6E-000133" Link identification: "Linker I02-37" Link Date/Time: 27-SEP-2023 01:50:17.24 Image Checksum (MD5): 25C569F9081A121C193B8D865C21853E [SYSMSG]VMSLICENSE_LANGUAGE.COM File creation date and time: 27-SEP-2023 01:37:02.78 Checksum (MD5): 004CF2F7CF1F0F9A3CAED83B26785D79 [SYSUPD]VMSLICENSE.COM File creation date and time: 27-SEP-2023 01:37:02.12 Checksum (MD5): A0B58B897025E16024626BDB2A5AE334 [SYSUPD]IA64_LMF.CLD (V8.4-2 and V8.4-2L1 only) File creation date and time: 8-DEC-2020 14:51:55.74 Checksum (MD5): DEE41D689A414F93C94171115F4C3CD5 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 ensure 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 for download within a ZIP archive container file. The kit files may be extracted on any system with UNZIP and copied to your OpenVMS system, or extracted on your OpenVMS system directly. Assuming you have created an UNZIP symbol to invoke the UNZIP image, you can invoke UNZIP to unpack the kit on OpenVMS using the command: $ UNZIP VMS842L3I_LMF-V0200 This will extract the installable PCSI product kit file and its associated signed manifest (_VNC file), used for kit validation during PRODUCT commands. VSI strongly recommends always using the manifest to validate the kit content during any PRODUCT commands. This will occur automatically if the files are both contained in the same directory. Note regarding UNZIP tool availability: Most customers likely have already installed a set of ZIP and UNZIP tools on their VSI OpenVMS systems. Should you need these tools, a set of the Info-ZIP freeware ZIP and UNZIP tools for VSI OpenVMS is available for download on the web at this address: https://vmssoftware.com/products/zip-tools/ Note regarding previous use of self-extracting .ZIPEXE file kit distribution: In the past, VSI OpenVMS ECO patch kits were distributed within self-extracting .ZIPEXE images. VSI is moving away from this mechanism in favor of using just a ZIP archive directly. This has several advantages, including: o The ability to unpack the kit files on any system, not just the target architecture OpenVMS system. o No need to supply a separate manifest signature file for the kit distribution. The kit files within the new ZIP archives will always be signed for content validation during installation. o Avoids the need to manually validate the .ZIPEXE image against a separate manifest file. Should you require .ZIPEXE distribution due to procedural constraints, please contact VSI Support and we will arrange to supply the kit in this format for you. VSI strongly recommends using the ZIP mechanism going forward. 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 VMS842L3I_LMF [/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. The release notes for any kit may be extracted prior to kit installation using the PRODUCT EXTRACT RELEASE_NOTES command. User-selectable options for installation behavior and scripting are available in this kit, refer to 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 Special Installation Instructions Processes created after installing this kit will pick up the updated images. For interactive processes already logged in, a LOGOUT/LOGIN sequence will be necessary to use these images. If this kit is being installed in a non-clustered environment, the following steps may be ignored. In a VMScluster with a shared system disk, additional steps must be taken so that the other nodes which share the system disk will use the new images. Execute the following commands on each node that is sharing the system disk that has been updated: $ INSTALL REPLACE SYS$SYSTEM:SHOW.EXE $ INSTALL REPLACE SYS$SYSTEM:LMF.EXE $ INSTALL REPLACE SYS$MESSAGE:LMF_MESSAGE.EXE If this system disk is for V8.4-2 or V8.4-2L1, then also execute this additional command: $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE These same commands should be repeated for other systems sharing the system disk if this patch kit is removed via a PRODUCT UNDO PATCH operation. 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 2023 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-VMS842L3I_LMF-V0200--4 APPENDIX A - User-selectable control options and scripting considerations Controlling kit behavior for introductory questions --------------------------------------------------- This kit provides user-selectable control options for kit dialogue interaction and automated scripting capability as described here in this appendix. 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 a 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 VMS842L3I_LMF/VERSION=V2.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