======================================================================= VMS Software Inc. OpenVMS ECO Kit Release Notes ======================================================================= 1 KIT NAME: VMS842L1I_IMGACT-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1: To be installed by all customers. Note: The crash addressed by this kit can only be caused by specific privileged actions which are very uncommon. VMS Software Inc. recommends all customers install this patch as a preventative measure. 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-1H1 VSI OpenVMS for Integrity Servers V8.4-2 VSI OpenVMS for Integrity Servers V8.4-2L1 The same images in this kit are used for all of these OpenVMS versions. Once this kit is installed, the updated images will remain in place if the OpenVMS version is updated from any listed older version to any listed newer version. Therefore, it needs to be installed only once for these OpenVMS versions. 3 KITS SUPERSEDED BY THIS KIT: VMS841H1I_IMGACT-V0100 VMS842I_IMGACT-V0100 Note: There is no VMS842L1I_IMGACT-V0100 kit. The problem addressed in the above kits was corrected in OpenVMS V8.4-2L1. 4 KIT DEPENDENCIES: None 5 PROBLEMS ADDRESSED IN THIS KIT 5.1 System crash when exiting a TPU-based editor (TPU, EVE or LSE) 5.1.1 Problem Description INSTALL REPLACE (or INSTALL DELETE) of a TPU section file while one or more users have the section file open will crash the system when the last user of the replaced section file closes the editor. The crash footprint resembles: Bugcheck Type: SSRVEXCEPT, Unexpected system service exception CPU Type: HP BL890c i2 (1.73GHz/6.0MB) VMS Version: V8.4-2 Current Image: $1$DGA8030:[SYS0.SYSCOMMON.][SYSEXE]LSEDIT.EXE Failing PC: FFFFFFFF.80A71EC1 IMG$DEALLOCATE_ICB_C+00911 This example shows LSE. EVE and EDIT/TPU have the same issue. Note: INSTALL REPLACE and INSTALL DELETE require CMKRNL privilege. This is either issued directly by the system manager or a privileged user, or indirectly as a result of updating a layered product like LSE. This problem is specific to Integrity servers. There is no corresponding patch required for Alpha. 5.1.2 Images and/or Files Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE [SYS$LDR]IMAGE_MANAGEMENT.STB 5.1.3 Quix and/or Bugzilla cases reporting this problem: External Bugzilla 265 5.1.4 Release Version of OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 5.1.5 Workaround Do not INSTALL REPLACE or INSTALL DELETE TPU section files while users are active in the editor. Note that upgrading a layered product such as LSE may perform the INSTALL commands as part of the upgrade process. 6 PROBLEMS ADDRESSED FROM PREVIOUS KITS 6.1 Image activation fails with LOADER-F-NO_SUCH_IMAGE 6.1.1 Problem Description In certain cases the image activator issues the following error message for a file that does in fact exist: %DCL-W-ACTIMAGE, error activating image -CLI-E-IMGNAME, image file -LOADER-F-NO_SUCH_IMAGE, the requested image cannot be located 6.1.2 Images and/or Files Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE [SYS$LDR]IMAGE_MANAGEMENT.STB 6.1.3 Quix and/or Bugzilla cases reporting this problem: Field Test Bugzilla 195 External Bugzilla 213 6.1.4 Release Version of OpenVMS that contains this change: VSI OpenVMS for Integrity Servers V8.4-2L1 7 IMAGES OR FILES REPLACED: [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 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 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_IMGACT-V0200.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_IMGACT [/SOURCE=location of kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option enabled. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. The kit location may be a tape drive, CD, 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. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 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 2017 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_IMGACT-V0200--4