ECO NUMBER: ALPOPCO01_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPOPCO01_062 2 KITS SUPERSEDED BY THIS KIT: ALPOPCO01_070 for OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 only 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: None. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 4.2 Files patched or replaced: o [SYSEXE]OPCOM.EXE (new image) o [SYSEXE]REQUEST.EXE (new image) o [SYSEXE]REPLY.EXE (new image) 5 PROBLEMS ADDRESSED IN ALPOPCO01_062 KIT o On OPCOM restart, the log file was not restarted. o REQUEST did not accept a string with a length greater than 128 characters. -- COVER LETTER -- Page 2 4 January 1999 o OPCOM crashed with a SSRVEXCEPTN error. o Raising exceptions, while in kernel mode only, leads to a system crash (SSRVEXCEPT error) in the CLUSCOMM_COD_ALLOCATE module. 6 PROBLEMS ADDRESSED IN ALPOPCO01_070 KIT FOR OPENVMS V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 o FAILING_OPCOM and OPCOM are both running on the system. 7 KIT INSTALLATION RATING: The following kit 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) INSTALLATION RATING: INSTALL_3 : To be installed by customers experiencing the problems corrected. 8 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPOPCO01_062 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. NOTE: The images OPCOM.EXE, REPLY.EXE, and REQUEST.EXE are replaced during installation using INSTALL REPLACE. However, the OPCOM process should be stopped using the STOP OPCOM command. If this command fails, then STOP/ID= (pid is process ID) can be used instead. Next, the logical OPC$OPCOM_STARTED should be deassigned, which is done by using the command: DEASSIGN/SYSTEM/USER OPC$OPCOM_STARTED Once OPCOM is stopped (no OPCOM process is active), the following command will restart OPCOM: -- COVER LETTER -- Page 3 4 January 1999 @SYS$SYSTEM:STARTUP OPCOM No reboot is necessary after successful installation of the kit. Copyright (c) Compaq Computer Corporation, 1998 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer Corporation. 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 COMPAQ 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.