======================================================================= VMS Software Inc. OpenVMS ECO Kit Release Notes ======================================================================= 1 KIT NAME: VMS842L2A_DCL-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: 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 OpenVMS to which this kit may be applied: VSI OpenVMS Alpha V8.4-2L2 3 KITS SUPERSEDED BY THIS KIT: None 4 KIT DEPENDENCIES: None 5 PROBLEMS ADDRESSED IN THIS KIT 5.1 SET COMMAND may construct command tables that cause a process crash 5.1.1 Problem Description After using SET COMMAND to add a command to your process command table or a command table file, certain malformed commands may later cause a process crash in DCL. The tests DCL performs to validate the command structures had an error that resulted in a corruption of internal process memory when checking the malformed command. This would then result in a process crash. DCL has been corrected to gracefully handle malformed command table entries. 5.1.2 Images and/or Files Affected: [SYSEXE]DCL.EXE 5.1.3 Quix and/or Bugzilla cases reporting this problem: Internal Bugzilla 1090 5.1.4 Release Version of OpenVMS that will contain this change: Next VSI OpenVMS Alpha release after V8.4-2L2 5.2 SET COMMAND may cause a process or image crash 5.2.1 Problem Description Malformed commands used as input for SET COMMAND may cause a subsequent process crash from DCL by producing a malformed command table. In addition, some malformed input to SET COMMAND may cause an image crash within CDU.EXE while building the command tables for use by DCL. Several missing limit checks were incorrectly allowing broken command tables to be produced. There was no problem with correctly defined commands, but building the malformed commands could cause an access violation in CDU or a subsequent process crash. The checks have been corrected so that valid tables are created or appropriate errors are returned. In particular, the documented limit of 255 qualifiers per VERB or SYNTAX statement is now enforced. In addition, SET COMMAND will now correctly reject a zero-byte file supplied through the /TABLE qualifier. 5.2.2 Images and/or Files Affected: [SYSEXE]CDU.EXE 5.2.3 Quix and/or Bugzilla cases reporting this problem: Internal Bugzilla 1088 5.2.4 Release Version of OpenVMS that will contain this change: Next VSI OpenVMS Alpha release after V8.4-2L2 5.3 F$LICENSE sometimes returns FALSE for a loaded license 5.3.1 Problem Description For a loaded license with a version number which is less than 7.1, but not zero, F$LICENSE("","") returns FALSE. For loaded licenses with version number 7.1 or higher, or 0.0 (no version number), F$LICENSE correctly returns TRUE. SHOW LICENSE correctly shows all these licenses as loaded. The behavior of F$LICENSE has been corrected to return TRUE for all validly loaded licenses regardless of version number. 5.3.2 Images and/or Files Affected: [SYSEXE]DCL.EXE 5.3.3 Quix and/or Bugzilla cases reporting this problem: Internal Bugzilla 995 5.3.4 Release Version of OpenVMS that will contain this change: Next VSI OpenVMS Alpha release after V8.4-2L2 5.4 RECALL/ALL may cause a process crash after using RECALL/INPUT 5.4.1 Problem Description After using RECALL/INPUT to load the recall buffer, a subsequent RECALL/ALL command may cause a process crash resulting in a display similar to the following and then the process is deleted: Improperly handled condition, bad stack or no handler specified. Signal arguments: Number = 0000000000000005 Name = 000000000000000C 0000000000000000 000000007FFC9CD1 000000007AF8AFA8 0000000000000012 For this problem to occur, the input file must be constructed with embedded NUL characters, which is not a valid command syntax. With this fix, DCL interprets the first NUL character as the terminator of the input line during a RECALL/INPUT command and does not fail during RECALL/ALL. 5.4.2 Images and/or Files Affected: [SYSEXE]DCL.EXE 5.4.3 Quix and/or Bugzilla cases reporting this problem: Internal Bugzilla 1054 5.4.4 Release Version of OpenVMS that will contain this change: Next VSI OpenVMS Alpha release after V8.4-2L2 5.4.5 Workaround Verify that any command line supplied to RECALL/INPUT does not contain any NUL characters. 6 PROBLEMS ADDRESSED FROM PREVIOUS KITS None 7 IMAGES OR FILES REPLACED: [SYSEXE]CDU.EXE Image name: "CDU" Image file identification: "A01-13" Image build identification: "XE80-F4N-000003" Link identification: "A13-04" Link Date/Time: 14-SEP-2017 17:02:07.45 Image Checksum (MD5): C767F8E6F5983A3B5858C186940AB0C5 [SYSEXE]DCL.EXE Image name: "DCL" Image file identification: "X-55" Image build identification: "XE80-F4N-000003" Link identification: "A13-04" Link Date/Time: 14-SEP-2017 17:02:07.42 Image Checksum (MD5): 1CD68AA32DD34FAC3992DFC5C0CE9CB3 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 VMS842L2A_DCL-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 VMS842L2A_DCL [/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. 8.3 Special Installation Instructions If this kit is being installed in a non-clustered environment, this section 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:CDU.EXE $ INSTALL REPLACE SYS$SYSTEM:DCL.EXE 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 AXPVMS-VMS842L2A_DCL-V0100--4