**************************** ECO SUMMARY INFORMATION **************************** Release Date: 9-APR-2009 Kit Name: VAXMSCP01_073.A Kit Applies To: OpenVMS VAX V7.3 Approximate Kit Size: 144 blocks Installation Rating: INSTALL_1 Reboot Required: Yes Special Install Instructions: No Superseded Kits: None Mandatory Kit Dependencies: None or later Optional Kit Dependencies: None. Checksums: VAXMSCP01_073.A-DCX_VAXEXE Checksum: 4059073137 VAXMSCP01_073.A-DCX_VAXEXE MD5 Checksum: 54FB31D99E6AF3170C4A81C7697BF2AB VAXMSCP01_073.A Checksum: 1919296464 VAXMSCP01_073.A MD5 Checksum: B7E33A05053986E502FA8C609FDEED81 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VAXMSCP01_073 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. This installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) 2.2 Reboot Requirement: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS VAX V7.3 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - None Page 2 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None. 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VAXMSCP01_073 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 "INVEXCEPTN, Exception while above ASTDEL" Bugcheck 5.2.1.1 Problem Description: An "INVEXCEPTN, Exception while above ASTDEL" system crash may occur if a tape is ANSI mounted and mount-verification begin. This crash is from an Alpha client to a VAX Server, but it may also occur on a VAX client to a VAX Server. Images Affected: - [SYSEXE]TMSCP.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases None. 5.2.1.2.2 PTR(s) 75-83-5 5.2.1.3 Release Version of OpenVMS that will contain this change: Not applicable Page 3 5.2.1.4 Work-arounds: None. 5.2.2 INVEXCEPTN Bugcheck 5.2.2.1 Problem Description: The system may crash in MSCP when, under extreme IO loads, the local device (the served device) is in mount verification for some period of time. Crash Information: ------------------ Crash Type : INVEXCEPTN Current Process : OPCOM Current Image : OPCOM CPU Type : 6000-410 SID : 0B000006 Signal Array cnt: 5 Exception par #1: 0000000C Exception par #2: 00000001 Exception par #3: 00093400 Exception PC : 8B695752 Exception PSL : 04080000 Failing Inst : CMPL Code Module : MSCP Offset : 1652 Images Affected: - [SYSEXE]MSCP.EXE 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases None. 5.2.2.2.2 PTR(s) 75-45-1940,75-66-163,75-66-1187 5.2.2.3 Release Version of OpenVMS that will contain this change: Not applicable Page 4 5.2.2.4 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYSEXE]MSPC.EXE (new image) Image Identification Information image name: "MSCP" image file identification: "X-72" link date/time: 25-AUG-2008 16:51:08.55 linker identification: "V11-38" image checksum: %X'4B133249' o [SYSEXE]TMSPC.EXE (new image) Image Identification Information image name: "TMSCP" image file identification: "X-42" link date/time: 25-AUG-2008 16:51:42.27 linker identification: "V11-38" image checksum: %X'4B133249' 7 INSTALLATION INSTRUCTIONS 7.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer "No" for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. Page 5 7.2 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable .PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VAXMSCP01_073.A-DCX_VAXEXE FTSV DCX auto-extractible compressed file for OpenVMS (VAX) FTSV V3.0 -- FTSV$DCX_VAX_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the Decompress into "(file specification)" question, either a or an alternate directory specification 7.3 Installation Command Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL VAXMSCP01_073 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty Page 6 of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. 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 HP 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.